SAP Database

LSMW - Legacy System Migration Workbench

The Legacy System Migration Workbench is an SAP-based tool that supports You when transferring data from non-SAP systems (”Legacy Systems”) to SAP systems1 once or periodically. The tool supports conversion of data of the legacy system in a convenient way. The data can then be imported into the SAP system via batch input, direct input, BAPIs or IDocs. Furthermore, the LSM Workbench provides a recording function that allows to generate a “data migration object” in an entry or change transaction.

Documents to get you started on LSMW:
Quick Reference Guide on LSWM
Examples:
Processing IDOC (Powerpoint)
Customer Adress via BAPI
Material Master IDOC
Open Items via Direct Input
Customer Master Creation & Some LSMW Exercises.

SAP R/3 System Design, Analysis and Implementation of Performance Tuning

The Purpose of this article is to draw attention to a more global view of performance problems in a complex client/server environment such as an R/3 system. This article was motivated by the observation that a large number of performance problems are caused by the unreflected use of certain performance guidelines beyond their range of validity. We want to adress ABAP developers who have already dealt with performance problems.

Download the document on Performance Tuning, Best Practices in Performance Tuning & Performance Analyzing tools, Database Access & Internal table Optimization.

Well, I know we have already talked about finding user exits in the program and also we have a program to find out the user exits in a given Program/Transaction. But, how many times have you searched in SPRO for the user exits. Just go to SPRO –> SAP Reference IMG –> Find (user exits). You will be amazed with the list of other places containing user exits.

There are 2 statements which allow to write ICON’s on the report output. We need to have INCLUDE <ICON> or INCLUDE<LIST> statement in the program.

Eg: WRITE <ICON-NAME> as ICON. ” will give the desired icon on the list output.

BADI stands for Business Add-in. BADI’s are an enhancement concept which uses ABAP objects. Totally a object oriented method to enhance classes, interfaces, methods.

You need to first define a BADI to enhance a SAP application program. The developer needs to create an interface for the BADI. An Adapter class is created from this that will implement the interface. Developers need to create an instance of the adaptor class in the SAP Application program and create method calls as required.

An Append Structure or a customizing include can be used to add fields to the Table. Append structures are created by adding fields to the end of a table while customizing includes are specified by the SAP Developer in advance to allow for the customer to create new fields.

The Modification assistant is a tool used to simplify the upgrade process as it relates to modifications. The Modification assistant can be triggered through the ABAP Editor and it will assist in logging modifications for any changes that are made to the system.

The Modification assistant provides support for modification made through the ABAP Editor, Screen Painter, Menu Painter, Text Element maintenance, Function Builder and ABAP Dictionary.

Quick Viewer (SQVI)

Quick Viewer is a comprehensive tool for defining reports in different forms such as basic lists, statistics, or ranked lists. The Quick viewer is basically used for generating basic lists and is very userful for beginners who was to analyze data between two or more different tables.

Here is a PDF file to teach you step by steps instructions for Quick Viewer.

COPYRIGHT: SAPDB.INFO

Function Module exits exist in some SAP application programs to allow a customer to add some functionality to the SAP Program. Search the SAP application program for the search string “CALL CUSTOMER” to check if any function module exists.

Copyright: SAP Database

Authorization Object are a group of fields used to check if an particular transaction/events/steps can be executed or not.

AUTHORITY-CHECK is the statement used in the ABAP program to perform the authorization check by passing a authorization object. All the relevant fields must be addressed or you have to use the keyword DUMMY to bypass the check and you can have a maximum of 10 fields defined in the authorization object.

To create the authorization object use the transaction SU21. Refer the ABAP Keywords to know more about it.

COPYRIGHT: SAP Database