4.11.2 Additional Function for BAPI/IDoc
If the LSMW object is based on a BAPI or an IDoc, further selection parameters are displayed on the data conversion program selection screen:
Convert Data: Further Selection Parameters for BAPI/IDocs
If you select Create file, a file is created during data conversion.
If you select "Create IDocs directly", IDocs are collected during data conversion and submitted for IDoc creation in packages. The package size can be determined using parameter "Number of IDocs per package". The default value is 50.
4.12 Display Converted Data
See section 4.10.1.
4.13 Import Data
The steps displayed by the program depend on the selected object type:
• Standard batch input or recording:
 Generate batch input session
 Run batch input session
• Standard direct input:
 Start direct input session
• BAPI or IDoc:
 Start IDoc creation
 Start IDoc processing
 Create IDoc overview
 Start IDoc postprocessing
5.17.1. Import Data with Batch Input
4.13.1.1 Generate Batch Input Session
In this step, the standard batch input program belonging to the object is directly called. The name of the file with the converted data is already proposed.
The batch input sessions to be generated are named after the LSMW object.
4.13.1.2 Run Batch Input Session
The program goes to SAP standard transaction SM35. However, only the batch input sessions for the selected object are displayed.
Note: If you used the name of the object in other projects or subprojects as well, batch input sessions from these objects may also be displayed.
4.13.2 Import Data with Direct Input
4.13.2.1 Start Direct Input Session
Depending on the object type, either the standard direct input program belonging to the object is called or you can select a direct input program or a direct input transaction.
4.13.3 Import Data with BAPI or IDoc Technique
Data stored in a file by means of the IDoc technique is generally imported in two steps. You can call these steps in LSM Workbench:
• Start IDoc creation. First, the file of the converted data is read. The "information packages" contained are stored in the SAP database in IDoc format. It is, however, not stored in the database of the corresponding application. The system assigns a number to every IDoc. Then the file of the converted data is deleted.
• Start IDoc processing. The IDocs created in the first step are submitted to the corresponding application program. This application program checks the data and posts it in the application’s database, if applicable.
Note: Step "Start IDoc creation" is not performed, if you selected option "Create IDocs directly" during data conversion.
Whether the second step is automatically initiated depends on the settings of the ALE-EDI customizing.
One essential setting is made in the so-called partner agreement (for a partner and a message type, see section 4.2). This agreement specifies whether the IDocs are to be processed immediately or by means of a background program.
Note #1: Partner agreements automatically created by the LSM Workbench are set as follows: "Initiation by background program". (You can manually change this setting at any time.)
Note #2: During the processing of inbound IDocs, so-called work items are created in the standard program. This are elements of the SAP workflow that are usually not required during data migration. For information on how – and with which consequences – the creation of work items can be suppressed see Note no. 149368.
Note #3: CD-ROM "Interface Adviser" provided by SAP contains useful information that helps to increase performance in connection with IDoc processing. Follow the path  Technology  Interfaces  Background processing  Import  ALE/IDoc  Performance.
You can do the following in addition to these two processing steps:
Create IDoc overview: This displays a „status overview which allows to display individual IDocs with the "drill-down" technique.
Bluesky
