CONVERSIONS & INTERFACES

SR KRISHNA
Conversions & interfaces

 SAP using companies in India 1945 - 2001 2002

 Mahindra & Mahindra Ltd. Purchased
Tata Motors SAP AG
 MRF. (Non SAP) (SAP)
 TVS Motors.
 Hindustan Unilever.
 Videocon.
Implemented
 Sony.
 Okaya Power Group. Accenture
 GMR Group. (SAP)

 Jindal Steel.
 Tata Steel.
 Reliance Infocomm Limited.
 SAP - System Data.

 Functional Consultants - Configuration Data or Organization Data.

 ABAP Developers - Create Programs to upload data ( Master & Transaction )

How to convert Data?

Non SAP Data / Legacy Data Flat File SAP Database

SAP Not Supported SAP Supported File

File Format. Format.

Conversion 1. DD.MM.YY Interface

1. DD-MM-YY
2. IND 2. IN
3. ENG 3. EN
4. $200 4. USD 200
5. Customer 5. Kunnr 1. Direct input.
C, Cobol, ABAP
2. Batch input.

3. LSMW.

4. BAPI.

5. ALE/IDOC
Flat File

 SAP supported file format, generally available in Notepad or Excel format.

 It contains SAP Compatible Data.

 It is generated as a result of Conversion program.

 Based on Data Format Flat files are 2 Types.

1. DAT Format. (IN SIVA 9291546326)
2. ASC Format. (INSIVA9291546326)

 Based on Availability Flat files are 2 Types.

1. Presentation server Flat file (Flat file located at Presentation server.) 2. Application server Flat file (Flat file located at Application server.)
 Presentation server Flat file

FLAT FILE / SAP

LOCAL FILE DATABASE

UPLOAD

DOWNLOA
D

 Read Data From File.  Write Data To File.

 Call function ‘UPLOAD’. 4.6B  Call function ‘DOWNLOAD’. 4.6B

 Call function ‘WS_UPLOAD’. 4.6C  Call function ‘WS_DOWNLOAD’. 4.6C

 Call function ‘GUI_UPLOAD’. 4.7EE  Call function ‘GUI_DOWNLOAD’. 4.7EE

 Application server Flat file (AL11)

SAP
DATABASE
DATA SET / SEQUENTIAL FILE

UPLOAD

DOWNLOA
D

 Read Data From File.  Write Data To File.

 Open Data Set. SYNTAX: Open DataSet ‘<File name>’ For <INPUT/OUTPUT> In <BINARY/TEXT>.  Open Data Set.

 Read Data Set. SYNTAX: Read DataSet ‘<File name>’ into <WA>.  Transfer. SYNTAX: Transfer <WA> to ‘<File name>’

 Close Data Set. SYNTAX: Close DataSet ‘<File name>’ .  Close Data Set.
Direct input Method

1. Used to upload Legacy data to SAP database.

2. SAP provided Built-in programs.

3. While Executing program system calls lot of Function modules.

4. If any error happens it Restart entire process.

SAP Provided Program Names
5. It Directly updates Target Database (It doesn’t process through screens)

 Dis:
Program Application
RMDATIND MM
1. Scope of Error data may be uploaded. RAALTD11 AM
RKEVEXT0 CO-PA
2. Proper Validations and Error handling is not possible.

3. Run always in Background Mode.

 TCODE : BMV0.

 Program : RBMVSHOW.
Batch input Method

1. Used to upload Legacy data to SAP database.  ADV:

2. It can be done by using 1. Data Upload through Tcodes.

 Call Transaction Method.
2. Error data may not be uploaded.
 Session Method.
 Recording Method. 3. Proper Validations and Error handling is possible.

4. Run Either Foreground or Background Mode.

Call Transaction Method Session Method

Used to upload less amount of data. Used to upload large amount of data.

It supports to upload data for only one Tcode at a time. Supports Multiple Tcodes at a time.

Error handling Explicitly using BDCMSGCOLL itab. Generates Log file for Error Records.

It supports both Asynchronous & synchronous updates. Supports only Synchronous update.

It supports both Foreground & Back ground Modes.

BDC using Call Transaction Method

Document Type Material Number Quantity Requested Plant

Presentation server Flat file

Presentation server Flat file

SE38

Database

ME51
Call Transaction Method
 BDC using Session Method

Document Type Material Number Quantity Requested Plant

Flat file

Flat File SE38

SM35

Recording - SHDB
RECORDING - System generated code
Session Method
LSMW (LEGACY SYSTEM MIGRATION WORK BENCH)

 SAP proprietary tool Used to upload Legacy data to SAP database.

1. with a few restrictions, it is also possible to migrate from SAP system to SAP system
2. Without Programming knowledge we can work with LSMW.
3. It is used by Functional consultants & End users also.
4. It is mainly used to upload MASTER DATA.
5. It is stored as a file with .LSMW extension. ( Not a Repository object )
6. Field Mapping is main concept behind LSMW.
7. As of SAP Web Application Server Release 6.20, the LSMW is integrated in the SAP system.
8. Therefore, if you are using a SAP system of this release or higher, you use the system-integrated LSMW 'out of the
box'.
9. Only for releases older than SAP Web AS 6.20, it is necessary to install the LSMW extra as add-on.
10. you have to install the standalone LSMW as add-on.
11. You can download the LSMW as add-on from the SWDC (Software Download Center) of the SAP Service Marketplace
12. It is mainly used to transfer very less amount of data. (<5000)

 There are 4 methods available in LSMW.

1. direct input method
2. recording method
3. BAPI method
4. ALE/IDOC method.
 LSMW - Recording Method

Dummy File

Flat File -- OX15

OX15

Execute TCODE - LSMW Create a New Project

Follow the 17 Steps

Finally view the DATA in - T880

 LSMW

 Execute Transaction LSMW.  Enter data as shown below.

 Click on create button.

 Specify project, sub project, object name and Enter.

 Click on continue or F8.

 STEP 1: Maintain Object Attributes

 Click on F8.

 Under choose and specify recording name as (ZRECORD).

 Click on save and continue with Request.
 And click on Recordings overview button.
 Click on BACK, again BACK.
 Now place the cursor on Recordings and click on create button.
 Now place the cursor on and click on
 Specify Recording name (ZRECORD) Short Description and click on continue.
push button. Finally SAVE and BACK..
 Specify TCODE (OX15) and click on continue.

 Click on
 LSMW

 Step 2: Maintain Source Structures

 Step 5: Maintain Field Mapping and Conversion Rules
 Click on continue or F8.
 Click on F8.
 Place the cursor on and click on create

 Specify Source Structure Name (COMPANY) Short description and click on continue.

 Click on SAVE and BACK.

 Step 3: Maintain Source Fields

 Now place the cursor on and click on table maintenance button.

 Enter the data as shown in fig..

 Click on save and back.

 Step 4: Maintain Structure Relations  Place the cursor on ZRECORD , click on Auto-Field Mapping.

 Click on F8 and SAVE & BACK.  Click on continue, SAVE & BACK.

 Step 6: Maintain Fixed Values, Translations, User-Defined Routines

 Click on F8 , SAVE & BACK.

 LSMW

 Step 7: Specify Files  Step 11: Convert Data

 Click on F8.  Click on F8 , F8 , BACK & BACK.

 Place the cursor on and click on add entry button  Step 12: Display Converted Data

 Specify the File Path & Name  Click on F8 , continue , BACK.

 Select Tabulator & continue.  Step 13: Create Batch Input Session

 SAVE & BACK.  Click on F8 , and click on & F8 , continue.

 Step 8: Assign Files  Step 14: Run Batch Input Session

 Click on F8 SAVE & BACK.  Click on F8 , & place the cursor on Session name (ZLS_OBJ)

 Step 9: Read Data

 Click on F8 , F8 , BACK & BACK.  Click on

 Step 10: Display Read Data  In the pop up specify the mode as

 Click on F8 , continue , BACK.  And click on

THANK YOU