Tutorials/LSMW/TCode/Index.1.jpg' alt='Sap Lsmw Error Log Download' title='Sap Lsmw Error Log Download' />Enhance LSMW Effectiveness using ABAP code. This document explains, how to apply the ABAP code to LSMW objects to meet the business requirements, Data Validations, Error Summary Report and to navigate through the LSMW transaction, and find the areas where we can write our own ABAP code detailed by an example. Introduction. The LSM Workbench is an SAP tool that supports single or periodic data transfer from non SAP to SAP system. Sap Lsmw Error Log Download' title='Sap Lsmw Error Log Download' />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 Standard Batch Direct Input, Batch Input Recording, BAPI or IDOC Methods. Many times there could be an instance to validate migrating data through coding. This can be achieved through ABAP code in LSMW to enhance the functionality. This document explains how to apply the ABAP code to LSMW objects to meet the business requirements, Data Validations, Error summary report and how to navigate through the LSMW transaction to find the areas where we can write our own ABAP code by detailed example. ABAP Coding areas inside LSMWABAP code can be inserted in two areas in the LSMW transaction. User Defined Routines. Field Mapping and Conversion Rules. The first area is the administration screen for user defined routines. ABAP code that is written here is done so in the form of a subroutine, and can be reused by all LSMW objects within the project in which the user defined routine was created. This is ideal for creating code that has the potential for being used by other objects within a project. For example. The second area in which we can insert ABAP code is in the maintain field mapping and conversion rules step of the LSMW. When ABAP code is inserted there, it applies only to objects in which it was inserted and cannot be reused by other objects. An example of this would be writing code that performs a specific data check applicable only to the Infotype for which the object was created. View Processing areas. The processing areas in Field Mapping and Conversion rules step are not visible by default. We need to activate these areas by selecting the required processing area from Extras Layout option as shown below. Now all the processing areas will available as shown below. Events Processing Areas. ABAP coding can be inserted at specific processing times. The SAP Community is the quickest way for users to solve problems, learn more about SAP solutions, and invent new ways to get things done. Using LSMW direct method i have uploaded few longtexts Po text, basicdata text,inspection text. Where to check the error log after running direct input methodMy. This document explains, how to apply the ABAP code to LSMW objects to meet the business requirements, Data Validations, Error Summary Report and to navigate through. Hi All, I have a new project of entirely extraction of all master datas OM, PA TM and also Payroll details from SAP and need to upload the same in a new upgraded. Global Functions. The LSM Workbench provides a series of functions that can be used in any position of the ABAP coding. To insert Global function in coding, select Insert Global Function as shown below. Example with Sample Code. Lets take a simple example to change the employee First and Last Name. This is not a business requirement indeed, but, taking into consideration a simple scenario, for a better understanding, is explained in the following section. This example mainly will help you to write the custom code in LSMW. This LSMW is to change the Employees First and Last Name in Infotype 0. Personal Data. Based on the Person ID, the program picks up the PERNR from the Infotype 0. Active, Inactive, Withdrawn and so on and updates all PERNRs in the respective Infotype 0. Employees First Name and Last Name. Points to be taken into consideration Validate whether the provided Person ID is valid i. Econometrics Book By Gujarati Pdf. Person ID specified in the flat file exists in the system or not. This is handled in BEGINOFTRANSACTION processing block. If the Person ID is invalid, the record is sent to the error Internal Table and further process is skipped. This is also handled in BEGINOFTRANSACTION processing block. Then the Error Person IDs will be downloaded to a spread sheet once the conversion is done. This is handled in ENDOFPROCESSING processing block. Based on the input data file Person ID, the program should pick up the PERNRPERNRs from the Infotype 0. PERNRs. This is handled in ENDOFRECORD processing block. This processing block is called for all available PERNR for the Person ID and additional records are inserted to output records LSMW buffer. Maintain Object Attributes. Maintain Source Structures. Maintain Source Fields. Input File Assume USER0. XYZXYZ is an invalid Person ID. Maintain Structure Relations. Maintain Field Mapping and Conversion Rules. Select Change Mode. Double click on GLOBALDATA block, ABAP Editor will be opened. This is like TOP INCLUDE, declare the required variables, structures and internal tables here. Double click on BEGINOFPROCESSING block this block will trigger Convert data step execution once. Declare Selection Screen related statements like Parameters, Select options etc here. This will be appeared in Convert Data step selection screen. Output Double click on BEGINOFTRANSACTION block this block will trigger every new transaction, say for example if the input data file contains 1. Declare the Validation logic here. Here the select query checks the Person ID is exist in the system or not. If it is not exist, error table is updated and the particular entry is skipped for further processing using skiptransaction global function. If it is exist, All PERNRs Active, Inactive if any against the Person ID will be stored in LTPERNR table. In every source structure BEGINOFRECORD and ENDOFRECORD routines are available. These routines executes before and after the conversion rules at each structure level. For eg, endofrecord can be used to call transferrecord as many times as the particular structure is required to be inserted. This routine is used in many business cases like extend a Material to multiple plants etc. Double click on ENDOFRECORD block this block will trigger after applying the conversion rules for a source structure. The first transferrecord statement is default. Here additional transferrecord statement is used to insert multiple records for the same Person IDs PERNR. Double click on ENDOFPROCESSING block this block will trigger end of every new transaction. Write the code to download and display the error records as shown below. Specify Files. 7. Assign Files. 8. Read Data. Execute the step to read the data from flat file. Convert Data. Execute the step, here additional selection parameter ERRPATH is available to select the error file download path This is declared in BEGINOFPROCESSING block. Execute. Screen shot of downloaded Excel file 1. Continue with the processing Create batch input session and Run batch input Session to update the valid PERNRs. Debugging LSMW Code. We can debug LSMW object by putting a hard or soft breakpoint. In Maintain Field Mapping and Conversion Rules, We can code BREAK POINT at the very first field where ever we need to debug. Then the program execution will break when it reaches there. We can also put soft breakpoints in the system generated code. To view the generated code, select Display Conversion Program step and execute. If this step is not visible, Go to Extras User Menu and activate. Thanks,Ramanathan Maniraman. Project Lead, SAP Practicei. GATE Global Solutions Ltd.