LSMW last step. Batch input????

Hi all,
I have successfully read the flat file and all the record is being read. The last step is batch input and its showing the record read and everything...
Now how do I go forward with the batch input and run it so that the respective data gets loaded to the transaction and to the database tables...
If possible, can you experts give me the steps so that I can run the batch input, the last step of the LSMW. Guys, I am really new to the SAP field, so please help me...
Waiting for your replies.
Thanks,
-Ken C

Have you gone through all these steps, particularly the bold ones?
 Maintain object attributes
 Maintain source structures
 Maintain source fields
 Maintain structure relations
 Maintain field mapping and conversion rules
 Maintain fixed values, translations, user-define
 Specify files
 Assign files
 Generate read program
 Display read program
 Read data
 Display read data
 Generate conversion program
 Display conversion program
 Convert data
 Display converted data
 Check converted data against customizing
 Create batch input session
 Run Batch Input session
 Analyze erroneous transactions
 Frame program for periodic data transfer
The last steps in bold and italics are the ones that will post the data.
Srinivas

Similar Messages

Background job terminated in LSMW last step

Experts:
When I run the last step in LSMW: 13 Start Direct Input Program,
I set a background job for Trans:BMV0,
But it goes an error:
"Job started
Step 001 started (program RMDATIND, variant....)
Could not open file xxxx.lsmw.conv
Job cancelled after system exception ERROR_MESSAGE"
could you tell me possible reasons for this error?thank you!

Ichecked the file assignment in step seven.
what file path and name did you define for the converted file? is this located on your PC or on the application server?
did you execute step 11?
did step 11 tell you that SAP had written xxx records to the conv-file?
The file path is on the application server
yes,I executed it.
Transactions Read:                9,066
Records Read:                    50,324
Transactions Written:             9,046
Records Written:                 50,228

LSMW Routing Standard Batch Input Create Batch Input Session

Hello All,
I am using LSMW for routing upload, using standard batch input method. Program RCPTRA01.
I am facing this quite peculiar problem.
I have tried first with separate text file for every source structure. Everything works fine till convert data step.
But when I go for 'Create Batch Input Session' it creates session for tables MAPL, PLKO, PLPO, PLMZ, PLMK. Other tables remain balnk (EAPL, PLFL, PLAB, PLFH, PLPH, PLFT, PLFV, PLWP). Because of this while running the session only the header and material assignment to task list get uploaded. Rest data, operation, MIC, component allocation do not get uploaded.
I have also tried for one text file for multiple structure. In that I face porblem for BDC creation. While debugging I faced th same thing in this also.
Could anyone please explain me the soution for this? Do I need to amend any progrm fior this?
Expecting lightning fast replies from Gurus....
Mimiri

Hello All,
I am awaiting your reply on this.......
Mimiri

Step by step batch input

Hi friends,
Please tell me about how to create a batch input from beginning to end.
How can I achieve the entry of the data?
sm35 or shdb is used to record the transaction steps?
One says sm35, the other says shdb?
Step by step?
Thanks in advance.

Hi,
BDC option
ABAP Runtime Environment (BC-ABA)
Batch Data Communication option.
BDC options define the processing mode for a batch input session.
Examples of modes used for processing sessions are:
     Display all records.
     Display for error dialogs only.
     Process session in the background.
     Process session on the screen.
Purpose
During data transfer, data is transferred from an external system into the SAP R/3 System. You can use data transfer when you:
     Transfer data from an external system into an R/3 System as it is installed.
     Transfer data regularly from an external system into an R/3 System. Example: If data for some departments in your company is input using a system other than the R/3 System, you can still integrate this data in the R/3 System. To do this, you export the data from the external system and use a data transfer method to import it into the R/3 System.
Implementation considerations
Before creating your own data transfer program, you should use the Data Transfer Workbench to find the data transfer programs that are delivered by SAP.
The Data Transfer Workbench
Purpose
The Data Transfer Workbench supports the automatic transfer of data into the R/3 System.
The Workbench is particularly useful for large amounts of data. It guarantees that data is transferred efficiently and ensures that data in the R/3 System is consistent.
Features
The Data Transfer Workbench provides the following functions:
     Integration of standard data transfer programs
     Registration and integration of your own data transfer programs
     Various techniques to load data into R/3.
The data is read from a transfer file in SAP format and loaded into the R/3 System using one of the techniques below:
     Administration and organization of data transfer projects
     Tools for analyzing the required SAP structures
     BAPI interface
     Batch input
     Direct input
Integration
SAP applications support the data transfer of numerous SAP business objects. The data transfer program specifies the data format definition that is necessary to import the data into the R/3 System. Adapt your conversion program for exporting the data from the external system to this definition.
Once the data has been exported, you can import it into your system using a generated data transfer program.
Features
     Data transfer from other, external systems
     Generation of data transfer programs
     Generation of function modules that can be used as an interface to the R/3 System
Initial Data Transfer
Prerequisites
Before you start the initial data transfer, you should have answered the following questions:
     Which business objects are to be transferred?
The objects to be transferred depend on the business applications you are using. If you are using sales and distribution processing, for example, you should transfer the material master records as well as the sales master records .
     How should the business objects be transferred?
Various techniques are available to load the data into the R/3.
Process Flow
The process of transferring data can be divided into the steps:
1.     Preparing the data transfer
     Analyzing and Cleaning Legacy Data
     Analyzing SAP Structures
     Developing Programs, Function Modules and BAPIs
     Creating a Program or FM for Data Extraction
     Creating a Mapping Program
     Registering Programs, Function Modules and BAPIs
1.     Executing the data transfer
     Organizing the Transfer in Projects
     Executing Data Transfer Runs, monitoring (CCMS) and processing (log)
     Checking transferred objects in R/3 using a function module or report (task type AUD).
The graphic below describes the steps involved in transferring the data:
ThThe The Data Transfer Workbench is an integrated project management for all the required steps involved in transferring data to your R/3 System.
You need to use programs or function modules for the various steps. SAP provides a range of BAPIs for loading data into R/3.
You could also carry out all the steps, except for loading the data via BAPIs, without using the Data Transfer Workbench.
In the first step you extract the existing data from a source system into a file and clean it there, if necessary.
To load data into R/3 you need a transfer file in an appropriate SAP format.
Using a mapping program you have to map the extracted data to the structures of the transfer file.
To load the data into the R/3 System one of the Techniques is used depending on the type of business object . I f more than one of these techniques is provided for a particular object type, you should read the documentation to find out what the different uses are .
Once you have created a project, you can start a run. The tasks of the run definition are processed in order.
After the data has been successfully loaded into the R/3 System, it can be checked here.
Result
You have transferred the data into the relevant R/3 application and checked it here.
Data Transfer
Purpose
During data transfer, data is transferred from an external system into the SAP R/3 System. You can use data transfer when you:
     Transfer data from an external system into an R/3 System as it is installed.
     Transfer data regularly from an external system into an R/3 System. Example: If data for some departments in your company is input using a system other than the R/3 System, you can still integrate this data in the R/3 System. To do this, you export the data from the external system and use a data transfer method to import it into the R/3 System.
Implementation considerations
Before creating your own data transfer program, you should use the Data Transfer Workbench to find the data transfer programs that are delivered by SAP.
Integration
SAP applications support the data transfer of numerous SAP business objects. The data transfer program specifies the data format definition that is necessary to import the data into the R/3 System. Adapt your conversion program for exporting the data from the external system to this definition.
Once the data has been exported, you can import it into your system using a generated data transfer program.
Features
     Data transfer from other, external systems
     Generation of data transfer programs
     Generation of function modules that can be used as an interface to the R/3 System
Data Transfer Methods
You can use the following methods to transfer data:
     Direct input: With direct input, the SAP function modules execute the consistency checks. However with batch input, these consistency checks are executed with the help of the screens. This means that direct input has considerable performance advantages.
     CALL TRANSACTION: Data consistency check with the help of screen logic.
     Batch input with batch input sessions : Data consistency check with the help of screen logic.
Difference between Batch Input and CALL TRANSACTION
If the direct input cannot be used for your task, this makes creating a data transfer program easier since the underlying transactions ensure that the data consistency checks are executed.
In the case of an error during the data transfer (if data records are inconsistent, for example), you can restart the transfer at the point in the program where the error occurred.
Batch input methods
With the batch input method, an ABAP program reads the external data that is to be entered in the R/3 System and stores the data in a "batch input session". The session records the actions that are required to transfer data into the system using normal SAP transactions.
When the program has generated the session, you can run the session to execute the SAP transactions in it. You can explicitly start and monitor a session with the batch input management function (by choosing System  Services  Batch input), or have the session run in the background processing system.
CALL TRANSACTION methods
In the second method, your program uses the ABAP statement CALL TRANSACTION USING to run an SAP transaction. External data does not have to be deposited in a session for later processing. Instead, the entire batch input process takes place inline in your program.
The information in Choosing Data Transfer Methods will help you decide which is the best data transfer method.
Data Transfer: Overview of Batch Input
Prerequisites
Before beginning the initial data transfer, you should answer the following questions:
     Which business objects are to be transferred?
The business objects to be transferred depend on the business applications that you will be using. If you are using sales and distribution processing, for example, you must transfer the material masters as well as the sales documents from your legacy system.
     How are the business objects to be transferred?
The data can be transferred either manually or automatically, using an SAP data transfer program or using your own transfer program.
Process flow
During the initial data transfer, data from the external system is converted into a sequential data transfer file and then transferred into the R/3 System using an SAP data transfer program. The data transfer file is the prerequisite for successfully transferring data as it contains the data in a converted format that is suitable for the R/3 System.
1.     Check to see if an SAP data transfer program (direct input, batch input or CALL TRANSACTION) exists for this data using the Data Transfer Workbench. Refer to the notes for this transfer program.
If no SAP data transfer program exists, proceed as follows:
2.     Determine the SAP transactions that a user would use to enter data records.
3.     Record these transactions using the batch input recorder. Ensure that you have filled all of the relevant fields with data.
4.     Use this data to generate a data transfer program.
5.     Display the Data Transfer Workbench and create your own data transfer object.
6.     Now follow the steps for transferring data using the Data Transfer Workbench.
The Transaction Recorder
Use
You can use the transaction recorder to record a series of transactions and their screens.
Features
You can use the recording to create
     Data transfer programs that use batch input or CALL TRANSACTION
     Batch input sessions
     Test data
     Function modules.
The recording can be executed several times. The screens are run in exactly the same way as they were run during the recording.
You can edit recordings that you have already made using an editor.
Activities
1.     To display the batch input initial screen, choose System  Services  Batch input Edit.
2.     Choose Recording. The system now displays the initial screen of the batch input recorder.
3.     Make a recording of the relevant transactions.
4.     Generate one or several of the objects named above.
Special features
     F1 -, F4 - and self-programmed F1 - and F4 help ( PROCESS ON HELP-REQUEST , PROCESS ON VALUE-REQUEST ) are not recorded. The same applies to all commands in the System and Help menus.
     Error and warning dialogs are not recorded. This means that only the OK code field and the field contents that lead to successful further processing in the current screen.
     " COMMIT WORK " in a transaction flow indicates the successful end of the transaction as regards batch input. The recording also ends successfully.
     " LEAVE TO TRANSACTION " in the course of a transaction indicates that it is not suitable for batch input. The recording is terminated.
     In ScreenPainter screens, movements in the scrollbar are not recorded. Use the function keys F21-F24 for positioning.
Recording Transactions
The recording forms the basis of generating data transfer programs, sessions, test data and function modules.
Procedure
1.     Display the initial screen of the batch input recorder.
2.     Assign a name to your recording.
3.     Choose Create.
4.     On the subsequent dialog box, enter the transaction code that you want to record and choose Continue.
The system displays this transaction.
5.     Execute the transaction in the usual way.
6.     When you have finished processing the transaction, the system displays an overview of the transaction and your input.
Choose Get transaction if no errors occurred while the transaction was being recorded.
If you do not want to keep the last recording that you made, go to the next step.
7.     Choose Next transac. If you want to record an additional transaction. Then continue from point 4.
8.     Save your recording when you have finished.
Recording
Once you have recorded the transaction, you can process it again later.
Procedure
1.     Display the initial screen of the batch input recorder (Transaction SHDB).
2.     Choose Overview.
The system displays an overview of all recordings.
3.     Position the cursor on the relevant recording and choose Execute.
4.     Choose one of the following processing modes:
A : Display all screens.
E : Display errors only. In the case of an error, the system displays the screen on which the error occurred. Once this error has been corrected, the system continues to process the recording until the next error occurs.
N : No display. The recording is not processed visibly.
5.     Choose the update mode:
A : Asynchronous update
S : Synchronous update
L : Local update
6.     You begin to process the recording when you choose Enter to exit the dialog box. When the recording is complete, the system displays a log that lists the name of the transaction, the system field SY-SUBRC and the system messages that were output.
Using the Recording Editor
The recording editor contains functions that you can use to edit your recordings.
Procedure
1.     Display the initial screen of the batch input recorder (Transaction SHDB).
2.     Choose Overview.
The system displays an overview of all recordings.
3.     Position the cursor on the relevant recording and choose Change.
4.     The following functions are available on the overview that the system displays:
Delete transaction from the recording: This deletes the selected transaction.
Add a new transaction to the recording: The transaction is added at the end of the recording.
Editing: You can edit the current recording.
If you choose Editing, proceed as follows:
5.     The system displays an editor where you can add and delete individual lines. You can also change the contents of these lines.
6.     If these editor functions are insufficient for your requirements, you can choose Export to download the recording onto your presentation host and use a PC editor to edit it there.
7.     Choose Import to import this file back into the R/3 System. Ensure that the file is still in the correct format.
8.     Choose Check to ensure that the edited version of the recording is still syntactically correct.
9.     Save your changes to the recording when you have finished editing it.
Generating Batch Input Sessions From the Recording
The data from the recording is transferred into batch input sessions that you can process for test purposes using the usual mechanisms.
Prerequisites
Before you can generate a batch input session, you must record the transactions through which the data is to enter the R/3 System. You use the batch input recorder to do this.
Procedure
1.     Display the initial screen of the batch input recorder (Transaction SHDB).
2.     Choose Overview.
The system displays an overview of all recordings.
3.     Position the cursor on the relevant recording and then choose Generate session.
4.     Enter a session name, a user with whose authorizations the session is to be processed, the identification whether the session is to be deleted once it has been processed and the processing date.
5.     Choose Continue to exit the dialog box.
You have generated a batch input session that uses the same data for the input fields that you entered when you created the recording. You can now process this as usual.
Generating Data Transfer Programs
Prerequisites
Before you can generate a data transfer program, you must record the transactions using which the data is imported into the R/3 System. You use the batch input recorder to do this.
Procedure
1.     Display the initial screen of the batch input recorder (Transaction SHDB).
2.     Choose Overview.
The system displays an overview of all recordings.
3.     Position the cursor on the relevant recording and choose Create program.
4.     On the following screen, specify a program name.
5.     You can also choose how the maintained field contents of the recorded screens are to be filled:
Transfer the values that were used during the recording. If you require a flexible data transfer, you must modify this program.
Set the parameters of the input values to be maintained and import these values from a data file. To set the parameters, the system creates a data structure and imports the data records from an external file into this data structure. The program assumes that the external file has been adapted to this data structure.
6.     If you have decided to set parameters for the input values to be maintained, it is useful if you create a test file when you generate the program. To do this, flag the checkbox and enter a name for the test file. For more information, see creating a test file.
7.     Choose Continue.
8.     The system displays the attribute screen of the program editor. Choose the relevant attributes here and save the program.
Result
You have now generated a data transfer program that you can use to import data into the R/3 System. The program can execute the data transfer using batch input or CALL TRANSACTION .
Generating Function Modules
Prerequisites
Before you can generate a data transfer program, you must record the transactions using which the data is imported into the R/3 System. You use the batch input recorder to do this.
Procedure
1.     Display the initial screen of the batch input recorder (Transaction SHDB).
2.     Choose Overview.
The system displays an overview of all recordings.
3.     Position the cursor on the relevant recording and choose Create function module.
4.     On the subsequent dialog box, enter a function module name, a function group and a short text for the function module. Exit the dialog box by choosing Continue.
The system automatically creates the function module.
Result
You have now generated a function module that you can use as an interface for your R/3 System. As well as information relevant for the data transfer, the function module's import interface has a parameter for each input field of the transaction recorded.
Using Function Modules
Prerequisites
The function module was generated from a recording made using the batch input recorder.
Procedure
1.     Cal the function module.
2.     Supply the generic interface of the function module:
CTU : Flag whether the data is to be transferred using batch input method CALL TRANSACTION USING . The system generates a batch input session if this flag is not set.
MODE : Processing mode:
A     Display all
E     Display only errors
N     No display
UPDATE : Update mode:
S     Synchronous
A     Asynchronous
L     Local update
GROUP : (If CTU is already specified): Name of the batch input session to be generated
USER : (If CTU is already specified): User with whose authorizations the session is to be processed
KEEP : Specifies whether this session is to be deleted once it has been processed
HOLDDATE : Specifies the earliest processing date for the error session
NODATA : Defines the NODATA character
3.     Supply the function module's special interface.
For each input field that was filled when you recorded the transactions, the system creates an import parameter. The recorded value is used as the default value for this import parameter.
Creating Test Files
To test the data transfer program that you have created, you can create a data record in a sequential file. This data record contains all the field contents from the recording that are relevant to the data transfer in the format required by the data transfer program. It is therefore useful if you align the format of your conversion program data file with the format of the test file.
Prerequisites
Before you can generate a data transfer program, you must record the transactions using which the data is imported into the R/3 System. You use the batch input recorder to do this.
Procedure
1.     Display the initial screen of the batch input recorder (Transaction SHDB).
2.     Choose Overview.
The system displays an overview of all recordings.
3.     Position the cursor on the relevant recording and choose Create test data.
4.     Enter a test file and exit the dialog box by choosing Continue.
You have now created a test file.
If the test file you have specified already exists, the system appends the new data record.
If you do not specify the path, the system archives the test file in the working directory of the current application server.
Executing the Data Transfer
Purpose
You generally use the Data Transfer Workbench to execute the data transfer. The following section describes how you transfer data directly using the batch input method.
Prerequisites
You require a data transfer program. This may be an SAP data transfer program, or you can create your own program.
Process flow
1.     Provide the data to be imported in a data file. Ensure that the data is in the correct format.
2.     If you are using a generated data transfer program, you can choose a data transfer method.
If you are only dealing with one data record, you can import this directly using a generated function module.
3.     Execute the data transfer program.
4.     Analyze the program and correct any errors that occur.
Writing Data Conversion Programs
The data conversion program is responsible for the following tasks:
     Converting the data that is to be transferred into the R/3 System as required by the SAP data structure or transactions that you are using.
If you are using an SAP batch input standard program, you must generate the data structure from the SAP standard data structure (see generating an SAP data structure).
If you develop your own batch input program, the data structure is determined by the R/3 System when the program is generated. Generate a test file from the recording and align the format of your conversion program with the format of the test file.
A conversion may be necessary for data type and length data type and length. The data type required by all standard SAP batch input programs is C, character data. You can find the required field lengths either in your analysis of the data declaration structure of the generated batch input program or in the data structures that you generate.
     The data is exported in SAP format to a sequential file. The batch input program in the R/3 System reads the data in from this file.
Process flow
The tasks involved in writing a data transfer program are shown in the diagram and list below.
Writing Data Conversion Programs
The data conversion program is responsible for the following tasks:
     Converting the data that is to be transferred into the R/3 System as required by the SAP data structure or transactions that you are using.
If you are using an SAP batch input standard program, you must generate the data structure from the SAP standard data structure (see generating an SAP data structure).
If you develop your own batch input program, the data structure is determined by the R/3 System when the program is generated. Generate a test file from the recording and align the format of your conversion program with the format of the test file.
A conversion may be necessary for data type and length data type and length. The data type required by all standard SAP batch input programs is C, character data. You can find the required field lengths either in your analysis of the data declaration structure of the generated batch input program or in the data structures that you generate.
     The data is exported in SAP format to a sequential file. The batch input program in the R/3 System reads the data in from this file.
Process flow
The tasks involved in writing a data transfer program are shown in the diagram and list below.
Selecting a Data Transfer Method
When you transfer data in ABAP, you have three options to submit the data for the data transfer. Only the first two methods can be recommended without reservation. The third method, by way of CALL DIALOG, is outmoded. CALL DIALOG is less comfortable than the other methods. You should use it only if you must.
     Use the CALL TRANSACTION USING statement
Summary: With CALL TRANSACTION USING, the system processes the data more quickly than with batch input sessions. Unlike batch input sessions, CALL TRANSACTION USING does not automatically support interactive correction or logging functions.
Your program prepares the data and then calls the corresponding transaction that is then processed immediately.
The most important features of CALL TRANSACTION USING are:
o     Synchronous processing
o     Transfer of data from an individual transaction each time the statement CALL TRANSACTION USING is called
o     You can update the database both synchronously and asynchronously
The program specifies the update type
o     Separate LUW (logical units of work) for the transaction
The system executes a database commit immediately before and after the CALL TRANSACTION USING statement
o     No batch input processing log
     Create a session on the batch input queue.
Summary: Offers management of sessions, support for playing back and correcting sessions that contain errors, and detailed logging.
Your program prepares the data and stores it in a batch input session. A session is a collection of transaction data for one or more transactions. Batch input sessions are maintained by the system in the batch input queue. You can process batch input sessions in the background processing system.
Your program must open a session in the queue before transferring data to it, and must close it again afterwards. All of these operations are performed by making function module calls from the ABAP program.
The most important aspects of the session interface are:
o     Asynchronous processing
o     Transfers data for multiple transactions
o     Synchronous database update
During processing, no transaction is started until the previous transaction has been written to the database.
o     A batch input processing log is generated for each session
o     Sessions cannot be generated in parallel
The batch input program must not open a session until it has closed the preceding session.
     Use the CALL DIALOG statement
Summary: Not recommended if you can enter data by way of sessions or CALL TRANSACTION USING.
Your program prepares data for a sequence of dialog screens, and calls a dialog module for immediate processing.
The most important aspects of the CALL DIALOG interface are:
o     Synchronous processing
o     Transfers data for a sequence of dialog screens
o     No separate database update for the dialog
A database update occurs only when the calling program executes a commit operation.
o     Shares LUW with calling program
o     No batch input processing log is generated
Executing Data Transfer Programs
Procedure
If you are using an SAP data transfer program, follow the procedure specified in the program documentation.
If you are using a generated data transfer program, proceed as follows:
1.     Start the data transfer program.
2.     Decide which batch input method you want to use for the data transfer.
a) CALL TRANSACTION USING:
You must specify the:
Processing mode: You use this parameter to specify whether processing should take place in the background or in dialog mode.
Possible values are:
A     Display all
E     Display only errors
N     No display
Update mode: This parameter determines how the data is to be updated:
Possible values are:
S     Synchronous
A     Asynchronous
L     Local update
Error session: Here you have the option to specify a session name for a batch input session in which data is to be written in the case of an error. You can use this to identify incorrect data records after the batch input program has run and to import the records into the R/3 System once you have corrected them.
If you are creating an error session, you must also specify:
User: Specify the user with whose authorizations the sessions are processed.
Keep session: This specifies whether or not the session should be deleted once it has been processed.
Lock date: Specify the processing date for the error session.
b) Generate session:
Session name: Specify a name for the batch input session to be generated.
User: Specify the user with whose authorizations the sessions are processed.
Keep session: This specifies whether or not the session should be deleted once it has been processed.
Lock date: Specify the processing date for the error session.
3.     Specify a character that is to be used as the NODATA character.
4.     Specify the path of the data file from which the data is to be imported into the R/3 System.
5.     Execute the program.
6.     If you have generated a session, or if errors occurred in CALL sTRANSACTION USING mode, you must now edit the generated sessions. You can find information on this in BC - System services in batch input sessions.
Batch Input Authorizations
You do not need special authorization - other than the ABAP run time authorization (authorization object S_PROGRAM - to run a program that creates batch input. Any user can create batch input sessions.
Starting processing for a session once it is in the queue is another matter, however. You can find more information on this in batch input sessions.
Creating a Session with BDC_OPEN_GROUP
Use the BDC_OPEN_GROUP function module to create a new session. Once you have created a session, then you can insert batch input data into it with BDC_INSERT.
You cannot re-open a session that already exists and has been closed. If you call BDC_OPEN_GROUP with the name of an existing session, then an additional session with the same name is created.
A batch input program may have only one session open at a time. Before opening a session, make sure that any sessions that the program closes any sessions that it previously had opened.
BDC_OPEN_GROUP takes the following EXPORTING parameters:
     CLIENT
Client in which the session is to be processed.
Default: If you don't provide a value for this parameter, the default is the client under which the batch input program runs when the session is created.
     GROUP
Name of the session that is to be created. May be up to 12 characters long.
Default: None. You must specify a session name.
     HOLDDATE
Lock date. The session is locked and may not be processed until after the date that you specify. Only a system administrator with the LOCK authorization for the authorization object Batch Input Authorizations can unlock and run a session before this date.
Format: YYYYMMDD (8 digits).
Default: No lock date, session can be processed immediately. A lock date is optional.
     KEEP
Retain session after successful processing. Set this option to the value X to have a session kept after it has been successfully processed. A session that is kept remains in the input/output queue until an administrator deletes it.
Sessions that contain errors in transactions are kept even if KEEP is not set.
Default: If not set, then sessions that are successfully processed are deleted. Only the batch input log is kept.
     USER
Authorizations user for background processing. This is the user name that is used for checking authorizations if a session is started in background processing. The user must be authorized for all of the transactions and functions that are to be executed in a session. Otherwise, transactions will be terminated with "no authorization" errors.
The user can be of type dialog or background. Dialog users are normal interactive users in the R/3 System. Background users are user master records that are specially defined for providing authorizations for background processing jobs.
Adding Data to a Session: BDC_INSERT
Use the BDC_INSERT function module to add a transaction to a batch input session. You specify the transaction that is to be started in the call to BDC_INSERT. You must provide a BDCDATA structure that contains all of the data required to process the transaction completely.
BDC_INSERT takes the following parameters:
     TCODE
The code of the transaction that is to be run.
     POST_LOCAL
Parameter to update data locally. If POST_LOCAL = X, data will be updated locally.
(refer to the keyword documentation of SET UPDATE TASK LOCAL for more information)
     DYNPROTAB
The BDCDATA structure that contains the data that is to be processed by the transaction.
DYNPROTAB is a table parameter in the function module.
Closing a Session: BDC_CLOSE_GROUP
Use the BDC_CLOSE_GROUP function module to close a session after you have inserted all of your batch input data into it. Once a session is closed, it can be processed.
Function Module BDC_CLOSE_GROUP
Exception parameters
Parameter     Function
NOT_OPEN     Client
QUEUE_ERROR     Internal use
BDC_CLOSE_GROUP needs no parameters. It automatically closes the session that is currently open in your program.
You must close a session before you can open another session from the same program.
You cannot re-open a session once it has been closed. A new call to BDC_OPEN_GROUP with the same session name creates a new session with the same name.
Processing Batch Input Sessions
When you create a batch input session, it remains in the batch input queue until it is explicitly started. Session processing can be started in two ways:
     An on-line user can start the session using the batch input menu options. (To access the batch input options, choose System  Services  Batch Input.)
     You can submit the background job RSBDCSUB to start a session in background processing. If several sessions have the same name, RSBDCSUB starts them all.
Its possible to coordinate the generation and execution of a session in the background processing system.
You can, for example, schedule both the batch input program and RSBDCSUB in the background. If you designate the batch input job as the predecessor for RSBDCSUB, then RSBDCSUB will be started automatically when the batch input job successfully completes.
Alternatively, you can schedule both the batch input program and RSBDCSUB as job steps in a single background job. In this case, however, RSBDCSUB is started even if the batch input program should terminate abnormally.
For detailed information about processing batch input sessions, see Managing Batch Input Sessions in the System Services guide.
Frequent Data Transfer Errors
The most frequent errors include:
     The BDCDATA structure contains screens in incorrect sequence.
     The BDCDATA structure assigns a value to a field that does not exist on the current screen.
     The BDCDATA structure contains a field that exceeds the specified length.
General guidelines
You should be aware of the following guidelines when you create sessions and call transactions or dialogs:
     You must provide data for all required fields on a screen.
     You can only specify the initial data for a screen. The system does not accept input as a response to a warning or an error message.
     If there is more than one possible screen sequence for a transaction or dialog, your program specifies the screen sequence for the transaction. You must transfer all screens that the dialog user sees to the selected screen sequence. This applies even if the screen itself is not used to input data.
Direct Input
To enhance the batch input procedure, the system offers the direct input technique, especially for transferring large amounts of data. In contrast to batch input, this technique does not create sessions, but stores the data directly. It does not process screens. To enter the data into the corresponding database tables directly, the system calls a number of function modules that execute any necessary checks. In case of errors, the direct input technique provides a restart mechanism. However, to be able to activate the restart mechanism, direct input programs must be executed in the background only. To maintain and start these programs, use program RBMVSHOW or Transaction BMV0.
Examples for direct input programs are:
Program     Application
RFBIBL00     FI
RMDATIND     MM
RVAFSS00     SD
RAALTD11     AM
RKEVEXT0     CO-PA
Pls reward points.
Regards,
Ameet

LSMW Routing- Standard Batch Input BDC_INSERT, screen .&. is invalid

Hello All,
I am preparing LSMW for routing upload along with inspection characteristics with standard batch input method.
At the time of 'Create batch input session' I am facing an error 'BDC_INSERT, screen .&. is invalid'.
I have checked the forums for the same issue but it wasn't fruitful. However I cam across one thread which mentions to ensures the data in falt file, which I did checke and confirmed.
What could be the reason?
Awaiting your replies...
Mimiri

Hello all.
I was facing the same problem.
To solve,I filled BI001-TCODE with 'QP01' (constant) in Maintain Field Mapping and Conversion Rules.
I know, this is a old question, but when I was searching I didn't find anything with this.
Regards.
Cássio Oliveira

Lsmw (batch input recording)

explain step by step procedure for uplodig master data through lsmw (batch input recording) method. please explain settings for auto field mapping in 5th step

Hi Neela,
These are the steps to be followed while doing a Batch Input Recording.
LSMW STEPS (Batch Input Recording)
1. Maintain Attributes:
Here you have to choose the second option and you can do the recording how this should work. Then assign the same to the Batch Input Recording name.
2. Maintain Source structure:
Create a structure name
3. Maintain Source field:
Create a structure like the Input File
eg:
Name - LIFNR
Description - Account number or Vendor Number
4. Maintain structure relations:
This will link the structure to the input file.
5. Maintain field mapping and conversion rules:
You can choose the Auto Filed Mapping under Extras Menu. Yopu can also do coding, depending upon the code you have written or assignment you have done the values will get picked up from the file and get processed.
6. Maintain field mapping and conversion rules:
If you have any fixed values you can define here.
7. Specify files:
Specify the input file path and type.
8. Assign files:
This will assign ur file to the Input file
9. Read Data:
This will read ur data from teh file.
10. Dispaly Read Data:
You can see the uploaded data
11. Convert Data
This will convert the data to the corresponding format for processing
12. Display Converted data:
13. Create batch input session
Here this will create a batch input session for processing
14. Run Batch Input session:
By clicking on the session and process (Back ground or Display Errors)
Refer the Below Links
http://www.sapbrain.com/TOOLS/LSMW/SAP_LSMW_steps_introduction.html
/people/hema.rao/blog/2006/09/14/lsmw--step-by-step
http://help.sap.com/bp_blv1500/BL_US/documentation/LSMW_EN_US.doc
http://esnips.com/doc/8e732760-5548-44cc-a0bb-5982c9424f17/lsmw_sp.ppt
http://esnips.com/doc/f55fef40-fb82-4e89-9000-88316699c323/Data-Transfer-Using-LSMW.zip
http://esnips.com/doc/1cd73c19-4263-42a4-9d6f-ac5487b0ebcb/LSMW-with-Idocs.ppt
http://esnips.com/doc/ef04c89f-f3a2-473c-beee-6db5bb3dbb0e/LSMW-with-BAPI.ppt
http://esnips.com/doc/7582d072-6663-4388-803b-4b2b94d7f85e/LSMW.pdf
http://help.sap.com/saphelp_erp2005/helpdata/en/e1/c6d30210e6cf4eac7b054a73f8fb1d/frameset.htm
Reward Points if Useful
Regards
Gokul

Criteria to use batch input method in lsmw

in lsmw we hav batch input method,direct input,idocs,bapis,what is the criteria to use them?

     Decide whether it makes sense to use this tool with respect to the data volume to be transferred. It may be easier to transfer very small data volumes into the SAP system manually. In the case of a very large data volume, batch input or IDoc techniques may cause extremely long runtimes. A rough landmark for estimating the required time: 10 000 records per hour where this value may vary considerably depending on the hardware available.
     Identify the transaction(s) in the SAP system via which you want to import the data into your SAP system. It may be relevant whether you need the data for statistical analysis or for further processing in the system.
     Run the relevant transaction in the SAP system manually with test data from the legacy system and see which fields must be filled. There may be required fields that do not correspond to data fields in the legacy system. In such a case, you should better assign a fixed value or establish an optional field for data transfer.
santhosh

LSMW Issue at step -Run Batch Input Session

Dear gurus,
While uploading service master through lSMW while processing the system prompts a message specifying "Buffertable not upto date" at Run Batch Input Session step .So please investigate what is missing/wrong.
Wirth regards,
Raj

I dont think that this has directly something to do with LSMW.
It is more related to the transaction your try to post in the batch input.
Search OSS with the error message number. I had seen some notes for number SE001, but your message is actually twice in the message table, and you did not tell the message number.
If it is message SE001, then you may find programm corrections in OSS.
Otherwise just log out and in again and try, or open a message at OSS yourself if the problem still persists

Lsmw step by step procedure using batch input method

hi,
lsmw step by step procedure using batch input method

Step-by-Step Guide for using BAPI in LSMW
Note! The screen prints in this article are from ECC 5.0. They may differ slightly in other versions.
Introduction:
This document details the usage of BAPI in LSMW. We have used the example of migration of the purchase order data into SAP.
Pre-requisites:
It is assumed that the reader of this article has the minimum knowledge required on the Business Object, BAPI, Message Types and IDoc Types.
Step-by-Step Procedure:
Details of the BAPI used in this scenario:
Business Object: BUS2012
Method: CreateFromData
Details of Message Type and Basic IDoc Type:
Message Type: PORDCR
Basic IDoc Type: PORDCR02
Lets have a look at the BAPI first, before proceeding to the LSMW:
1. Go to Transaction BAPI
2. Click on Search Button
3. Enter the value BUS2012 and select Obj.type(Technical Object Name
4. Press ENTER
5. Following screen appears:
6. On the left side of the screen, Expand the PurchaseOrder.
7. Select PurchaseOrder and double-click on the same for details.
Building LSMW using BAPI:
1. Go to Transaction LSMW.
2. Enter the Project, Subproject and Object information and click on CREATE.
3. Enter the descriptions for Project, Subproject and Object.
4. Now select Settings à IDoc Inbound Processing
5. IDoc Inbound Processing screen appears. Enter the required details as shown below:
6. Click on Activate IDoc Inbound Processing.
7. Click on Yes when prompted for Activate IDoc Inbound?
8. Hit on Back to return to the main screen.
9. Click on Continue (F8). Following Screen appears:
10. Select the Step 1 Maintain Object Attributes and select Execute.
11. Select the radio button Business Object Method and enter the following details:
Business Object: BUS2012
Method: CreateFromData
Hit ENTER
12. Save and click on BACK button. Following information message is displayed.
13. Now select step 2 Maintain Source Structures and click Execute.
14. In this step, we need to maintain the source structure. In our example, lets consider the example of a file with 2 structures Head and Item data as shown below:
Click on Create and name the source structure as HEADERDATA. Now select HEADERDATA and click on Create again to create the child structure. Following popup appears:
Select Lower Level and click on Continue. Enter the Item data structure name.
Click Save and hit BACK button to go to the main screen.
15. Select step 3 Maintain Source Fields and hit execute.
16. Enter the fields as shown below:
17. Click SAVE and return to main screen.
18. Select step 4 Maintain Structure Relations and click Execute.
Select E1PORDCR and click on CREATE RelationShip. Following screen appears:
Select HEADERDATA and hit ENTER
Similarly do the same for the structure E1BPEKKOA, E1BPEKPOC and E1BPPEKET.
Click Save and return to main screen.
19. Select the step Maintain Field Mapping and Conversion Rules and click on execute. Maintain the Field Mapping as seen below:
20. Select step 7 Maintain Source Files and provide the link for the test file created. (Create a test file with the same structure as defined earlier).
Save and return to main screen.
21. Select the step Assign Files and click on Execute.
Assign the file provided to the source structure. Here the same file is provided for both the structures.
Save and return to the main screen.
22. Select the step Read Data and click on Execute.
Click on Execute.
Return to the main screen.
23. Select the step Display read data and click on execute.
Click on the structure name to get the field level values.
24. Return to main screen and now select Convert Data.
25. Return to the main screen and select Display Converted data.
26. Return to main screen and select Start IDoc generation.
27. Now select the step Start IDoc Processing on the main screen.
28. Return to main screen and click on Create IDoc overview. Here the data record and status records of the IDoc could be viewed
It is given in screen shot.
http://www.****************
http://www.sapbrainsonline.com/TUTORIALS/TECHNICAL/LSMW_tutorial.html
http://www.sapbrain.com/TOOLS/LSMW/SAP_LSMW_steps_introduction.html
http://esnips.com/doc/8e732760-5548-44cc-a0bb-5982c9424f17/lsmw_sp.ppt
http://esnips.com/doc/f55fef40-fb82-4e89-9000-88316699c323/Data-Transfer-Using-LSMW.zip
http://esnips.com/doc/1cd73c19-4263-42a4-9d6f-ac5487b0ebcb/LSMW-with-Idocs.ppt
http://esnips.com/doc/ef04c89f-f3a2-473c-beee-6db5bb3dbb0e/LSMW-with-BAPI.ppt
http://esnips.com/doc/7582d072-6663-4388-803b-4b2b94d7f85e/LSMW.pdf
Reward points if useful.

Problem on last step of LSMW

Hi all,
i am new to LSMW, when i am transferring data from a notepad file through LSMW, in the last step i got the error that "Maintenance at plant level' and something '000000000000000' after that it close automatically,
plz forward me step by step lsmw.
Thanx in advance,

Hai
Check the Step by step process for LSMW
Using Tcode MM01 -- Maintain the source fields are
1) mara-amtnr char(18)
2) mara-mbrsh char(1)
3) mara-mtart char(4)
4) makt-maktx char(40)
5) mara-meins char(3)
the flate file format is like this as follows
MAT991,C,COUP,Srinivas material01,Kg
MAT992,C,COUP,Srinivas material02,Kg
AMT993,C,COUP,Srinivas material03,Kg
MAT994,C,COUP,Srinivas material04,Kg
MAT995,C,COUP,Srinivas material05,Kg
goto Tcode LSMW
give Project Name
     Subproject Name
     object Name
Press Enter -
Press Execute Button
It gives 13 radio-Button Options
do the following 13 steps as follows
1) select radio-Button 1 and execute
   Maintain Object Attributes
select Standard Batch/Direct Input
   give Object -- 0020
       Method -- 0000
   save & Come Back
2) select radio-Button 2 and execute
   Maintain Source Structures
   select the source structure and got to click on create button
   give source structure name & Description
   save & Come Back
3) select radio-Button 3 and execute
   Maintain Source Fields
   select the source structure and click on create button
   give
   first field
        field name    matnr
        Field Label   material Number
        Field Length 18
        Field Type    C
   Second field
        field name    mbrsh
        Field Label   Industrial Sector
        Field Length 1
        Field Type    C
   Third field
        field name    mtart
        Field Label   material type
        Field Length 4
        Field Type    C
   fourth field
        field name    maktx
        Field Label   material description
        Field Length 40
        Field Type    C
   fifth field
        field name    meins
        Field Label   base unit of measurement
        Field Length 3
        Field Type    C
save & come back
4) select radio-Button 4 and execute
   Maintain Structure Relations
   go to blue lines
      select first blue line and click on create relationship button
      select Second blue line and click on create relationship button
      select Third blue line and click on create relationship button
save & come back
5) select radio-Button 5 and execute
   Maintain Field Mapping and Conversion Rules
   Select the Tcode and click on Rule button there you will select constant
   and press continue button
   give Transaction Code : MM01 and press Enter
   after that
   1) select MATNR field click on Source filed(this is the field mapping) select MATNR and press Enter
   2) select MBRSH field click on Source filed(this is the field mapping) select MBRSH and press Enter
   3) select MTART field click on Source filed(this is the field mapping) select MTART and press Enter
   4) select MAKTX field click on Source filed(this is the field mapping) select MAKTX and press Enter
   5) select MEINS field click on Source filed(this is the field mapping) select MEINS and press Enter
finally
save & come back
6) select radio-Button 6 and execute
   Maintain Fixed Values, Translations, User-Defined Routines
   Create FIXED VALUE Name & Description as MM01
   Create Translations Name & Description as MM01
   Create User-Defined Routines Name & Description as MM01
   after that delete all the above three just created in the 6th step
   FIXED VALUE --MM01
   Translations --MM01
   User-Defined Routines --MM01
   come back
7) select radio-Button 7 and execute
   Specify Files
   select On the PC (Frontend) -- and click on Create button(f5)
                                  give the path of the file like "c:\material_data.txt"
                                  description : -
                                  separators as select comma radiao- button
   and press enter   save & come back
8) select radio-Button 8 and execute
   Assign Files
   Save & come back
9) select radio-Button 9 and execute
   Read Files
   Execute
   come back
   come back
10) select radio-Button 10 and execute
    Display Imported Data
    Execute and press enter
    come back
    Come back
11) select radio-Button 11 and execute
    Convert Data
    Execute
    come back
    Come back
12) select radio-Button 12 and execute
    Display Converted Data
    Execute & come back
13) select radio-Button 13 and execute
    Start Direct Input Program
   select the Program
   select continue button
go with via physical file
give the lock mode as 'E'
and execute
Regards
Sreeni

LSMW Error - Last step

Hello,
I created an LSMW for AS02 and all steps were carried out successfully (Display, convert shows the correct mapping).
The step (CREATE BATCH INPUT SESSION) shows this error :
BDC_INSERT, screen .&. is invalid
Message no. 00339
Diagnosis
Error creating a batch input session.
Why is that? This is the last step.
Any help is welcom
Regards
roger

Hi,
Select the session in SM35 and process this record in "Display only Error" mode. This will let you see where in AS02 the error is coming and help you identify the correction that is needed.
regards
Sreekanth

PO creation using LSMW through batch input method

Hi, I am new to working with LSMW and i have completed a project for creating purchase orders using the direct data input method. I need to do the same using batch input method, however in the maintain structure relationship step, it is only allowing me to assign one structure to the recording that i have done, however in po creation we need separate (nested) structure for header and line item, could anybody help me past this please?

Hi Rudra!
OK, now you just know, why you have only one line, not multiple PO item lines. To get a dynamic number of items, you need a complex program - just like standard direct input.
If you need a field, which is not part of this program, don't try to write your own program for batch input - it's just to much work before you have a good result.
You can use Bapi method instead with BAPI_PO_CREATE1. This can handle a lot of fields and there is some documentation available how to fill the Bapi.
If this looks to complicated in the first moment, think about creation of POs via direct input and a small batch recording to change your additional field(s) afterwards. (You can select EKPO table to generate list of 'wrong' migrated orders for input in LSMW.) Use field 'Item' in the bottom of ME22 to position your desired line in first screen line, just change one PO-line after one other (every time a 'save' -> no problem with different number of lines / PO).
Regards,
Christian

LSMW for routing with standard batch input

Hello All,
I am trying to prepare one LSMW for routing upload for PP module. Routing data contains header data, operation data and master inspection characteristics data.
I have created three source structures viz. material- task list header, task header data, operation and inspection.
Header has been assigned to target structure BIMPL- Batch Input Structure for Allocation of Mat. to Task Lists,
Task header data source structure has been assigned to BIPKO- Batch Input Structure for Task List Header,
Operation source structure has been assigned to target structure BIPPO- Batch input structure for task list operation,
and inspection source structure has been assigned to BIPMK- Inspection characteristics for batch input of task lists.
Every source structure has been identified with an identifier value of which have been set as H, I,J,K for all source structures resp.
The excel file has been prepared as follows,
H MATNR WERKS PLNNR PLNAL
H 100045 1000 50000043 1
H 100045 1000 50000043 2
I MATNR WERKS PLNNR PLNAL VALID_FROM USAGE STATUS
I 100045 1000 50000043 1 01012000 1 1
I 100045 1000 50000043 2 01012000 1 1
I have mentioned here the combination of first two structures only. But it contains data of other two source structures as well (for identifier J & K).
The data from the excel is copied to the flat file and same is specified in LSMW in the step 'Specify file'.
In 'Assign file' step the flat file is assigned to all the four source structure.
Now at the time of reading data system is throwing me an error as 'Ensure field sequence is correct for data for mutiple source structures' Message no. /SAPDMC/LSMW_OBJ_060026
How to overcome this?
<removed by moderator> answers will be greatly appreciated........
Mimiri
Edited by: Thomas Zloch on Jul 11, 2011 10:16 AM

Hello ,
have you maintained this check box for the key fields"
LSMW>Maintain Source fields>double click on fieds : MATNR WERKS PLNNR PLNAL
Selection Parameter for "Import/Convert Data"-->Tick this check box
regards

Problem at the last step in LSMW Direct I/P Method

Hi all ,
I am trying to create the ROUTING using LSMW direct input method .
After executing the last step (Start Direct Input ) .. I am getting the Following Information as errors .
               Data Transfer of Routings via Direct Input                                                                  1
    Error_di_exp         From    To      Obj   Index       Plnnr
E    2     2                             O     0000000001
E                           1     1      A     0000000001
E                           2     2      O     0000000001
C\ 045
   You cannot edit the task list object with activity type
C\ 045
   You cannot edit the task list object with activity type
Please let me where could be the problem .
Thanks for any suggestions .
Regards,
Raj

go to CA01 and try loading one routing manually and you will understand whats the error.
discuss activity type restrictuing to be laoded with Functional consultent.

LSMW Batch Input Recording for Create BOM

Dear All,
I want to do LSMW for Creating BOM using Batch Input Recording,
I know that i have to make 2 time Recording, first for the BOM Header and second for the BOM item
For the BOM header i have done it, but for the BOM item i got some trouble with the item number (POSNR),
when i run the LSMW, for the first item (item 0010) was success, but for the item 0020, it can't work and i got error
message " NO BATCH INPUT FOR SAPLCSDI 0150"
How is the recording step by step for BOM Item so the Item number can increase well?
Very need your help,
Regards,
Marufat

Hello Santosh,
Thanks for the reply,
I already check in SM35 where i also thought that the main problem is about adding the new item number,
but when i tried to do repeat recording, i can not find any entry for adding the line item, so the line item after 0010 cannot be input
Is there any solution?
Regards,
Marufat

LSMW last step. Batch input????

Similar Messages

Maybe you are looking for