Batch Input Overview Screen

Hi All,
Some of my Mlis mirrors posting files uploaded are not found in the Batch input Overview screen . For example, files named KJCFS3101, KJCDM2701, and all named KJCDM**** .How can I retrieve them.
Brgds
Asha Banu A

Hi Chakra,
Please explain your requirement further.
1. A program creates SM35 sessions. A periodic job is defined for that.
2. Another program or a person processes those sessions.
3. A third one should be scheduled to run right after that.
If my assumption is true, I have some questions about it. How are the sessions processed? Are they manually processed or are they scheduled in batch processing?
I have a couple of scenarios in mind.
Scenario 1.
1. One program creates the sessions and also processes them by using RSBDCSUB program. This program will be scheduled as step 1 of the job.
2. Program 2 will be scheduled as step 2 of the job.
Scenario 2.
1. One program creates the sessions. This will be step 1 of the job.
2. RSBDCSUB will be scheduled as step 2.
3. Program 2 will be scheduled as step 3.
Scenario 3.
1. One program takes of creating the sessions, then submitting the RSBDCSUB to process and then submits the program2. You can then schedule one job for this one program.
If you can give more details of your requirement may be I can help.
Regards,
Srinivas

Similar Messages

No batch input data screen SAPLSDH4 0200

Hi,
While doing Check deposit transaction, i got the below error
" No batch input data screen SAPLSDH4 0200". When i press enter, it is going to FS01 screen and showing the customer number as * =D.xxxx (customer number)* and a dialogue box is appeared, in that search item and customer number is displayed. When i press enter, it is not accepting. When i clear it and press enter, it is showing all customers. I have selected the customer which i gave at the time of customizing and press enter. Then it is showing the "OK code" again selected ok.. Then the batch process competed. But when i go to SM35, i cant able to see the session again.
I dont understand why this problem is coming. But the posting were done properly. Can anyone explain me what exactly the problem with this transaction.
Regards
Sabera

Hi,
These error normally comes if the screen control branches out to different view or a screen.If a session is created for error logs, process the session in foreground mode and see at which point the OK CODE branches out to this particular screen. you also need to debug the particular record which is failing to see if its a data related issue or any particular field value is being wrongly processed. If your program is not creating any session for error logs i request you to generate a session for error logs or else if you are using call transaction ,run it in MODE 'A' to check whats happening.It's quite common to come accross such issues while developing a BDC.

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

FLB2 - Lockbox Screen Error: "No Batch Input for screen SAPDF05X 3100"

I'm not familiar with Lockbox processing ... was asked to help debug an error & not having much luck doing so.
When processing a file via FLB2, we have one customer for which the postings work fine. For another customer, however, we get an error:
"Accounts receivable posting Error: (00 344) No batch input data for screen SAPDF05X 3100."
I've checked multiple Notes & postings on SDN, still at a loss and getting no closer troubleshooting within the system.
Can anyone offer ideas of what to check?
Thanks,
John

Hi,
I believe the problem should be in the input file. There should an error in the file. Can you create a one line item file for the Customer and processs it. If the Lockbox is working for one Customer it should work for all Customers. Secondly, check whether Lockbox is maintained for the Customer in the master data.
Thanks
Murali.

No Batch Input for Screen 0300

Hello
I am doing an inter-company asset transfer using ABT1(Call Transaction).
However for few assets its giving me the error as 'No Batch input found for screen' '0300' even though
the message type in MESSTAB table is 'S'.And one I run the program again for same asset it works   properly.
    PERFORM 450_DYNPRO USING:
               'X' 'SAPLAMDP_OLD' '0100',
               ' ' 'RAIFP1-BLDAT' L_SYDATE,          " Document Date
               ' ' 'RAIFP1-BLART' 'AA',              " Document Type
               ' ' 'RAIFP1-BUDAT' L_PSTDAT,          " Posting Date
               ' ' 'RAIFP1-TRAVA' P_VAR,             " Transfer Variant
               ' ' 'RAIFP1-BZDAT' L_BZDAT,           " Asset Value Date
Posting Specifications
               ' ' 'RAIFP2-BUKRS' PWA_ASSET-BUKRS,    " From Company
               ' ' 'RAIFP2-ANLN1' PWA_ASSET-ANLN1,    " Asset
               ' ' 'RAIFP2-ANLN2' '0000',             " Sub Asset No
To
            ' ' 'RAIFP3-BUKRS' P_BUKRTO,              " To Company from i/p screen
               ' ' 'RAIFP3-XNANL' 'X',                " New Asset
Revenue
               ' ' 'RAIFP2-XERBW' 'X',                " NBV from area button
               ' ' 'RAIFP2-AFABE' '01',               " Default 01
               ' ' 'BDC_OKCODE' '/00',                " Enter
*Second Screen
               'X' 'SAPLAIST'    '2110',
               ' ' 'ANLZ-KOSTL' P_KOSTL,        " Cost Center
               ' ' 'BDC_OKCODE' '=DETA'.         " Push additional data
Enter allocations tab Common for ABT1 and AS11 transaction
    PERFORM 450_DYNPRO USING:
      'X' 'SAPLAIST'    '1000',
      ' ' 'BDC_OKCODE' '=TAB03',          " Go to Allocations tab
      'X' 'SAPLAIST'    '1000',
      ' ' 'ANLA-GDLGRP' P_GDLGRP,          " Enter value for eval. Grp 5
      ' ' 'BDC_OKCODE' '=TAB08'.
In the screen create
    PERFORM 450_DYNPRO USING:
      'X' 'SAPLAIST'    '1000',
      ' ' 'BDC_OKCODE' '=RW'.              " Go back to Second screen
    PERFORM 450_DYNPRO USING:
      'X' 'SAPLAIST'    '2110',
      ' ' 'BDC_OKCODE' '=CREA',            " Create the transaction
   'X' 'SAPMSSY0'    '0120',
   ' ' 'BDC_OKCODE' '=&ONT',
Save the transaction
      'X' 'SAPLAMDP_OLD' '0100',
      ' ' 'BDC_OKCODE' '=SAVE'.
Could anyone pls help in knowing me whats the problem?
Thanks and Regards

I think U need to handle screen 0300 .. and need to pass
data ('No Batch input found for screen' '0300' )

Batch-input and screens

Hi,
I have one program, that calls VA03 and print Billing document immediately.
Now they want stop batch-input at Issue output screen, and after they fill the options that want and continue the program.
Can you tell me if it is possible?? And if yes,what is the soluction for this?
Thanks ina advance.
All ideas are welcome.

I found one solution.
Batch-input code:
t-code = 'VA03'.
REFRESH bdcdata.
PERFORM bdc_dynpro      USING 'SAPMV45A' '0102'.
PERFORM bdc_field       USING 'BDC_OKCODE' 'DRCK'.
PERFORM bdc_field       USING 'VBAK-VBELN' tab-vbeln.
PERFORM bdc_dynpro      USING 'SAPLVMSG' '0200'.
PERFORM bdc_field       USING 'BDC_OKCODE' '=OPTS'.
CALL TRANSACTION 'VA03' USING bdcdata MODE 'E'
                        UPDATE 'S'
                        MESSAGES INTO messtab.
Thank you by all helps.
Ana

XK01 -- Batch Input Program Screen Sequence Issue

Guyz,
I created a recording in shdb for xk01 and generated the program from shdb itself and modified the program (both selection screen & processing logic).... suprisingly, when i execute the program, screen sequence is different when compared to the sequence from shdb recording..... i even downloaded the BDCTABLE contents during debugging and compared with recording in SHDB which is fine....
any pointers ?
after filling lifnr, bukrs & account group on initial screen of xk01, usually NAME & ADDRESS details screen comes up in online and SHDB recording, but during program execution in 'ALL SCREEN' & 'SYNCHRONOUS' mode (call transaction), i'm getting first screen (as expected) but its skipping NAME & ADDRESS details screen and thus my program getting stuck?
appreciate your pointers.....
thanks

On the first screen, you have to set a check-box that is normally hidden:
 perform dynpro
 tables bdcdata
 using:
 'X' 'SAPMF02K' '0105', "Create Vendor: Initial Screen
 ' ' 'RF02K-BUKRS' '0001',
 ' ' 'RF02K-KTOKK' 'ZZZZ',
 ' ' 'USE_ZAV' 'X'. "<=======Here
This will cause the program to use the screen in Central Address Management.
I also think you will probably use screen 0100 rather than 0105 that I have used above.
Rob
Message was edited by:
 Rob Burbank

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

No batch input data for screen for VF01

Hi All,
Iam trying to to create billing document using BDC for VF01 with sales order. For single line item it is working fine and that to in Mode 'A'. But while creating invoices using multiple sales orders , Iam getting the following error.
No batch input data for screen 'SAPMV60A' '0102' . Error - 0344.
Kindly help me as I was strucked here.
My code .
 PERFORM bdc_dynpro USING 'SAPMV60A' '0102'.
 PERFORM bdc_field USING 'BDC_CURSOR'
 'KOMFK-VBELN(01)'.
 PERFORM bdc_field USING 'BDC_OKCODE'
 '/00'.
 PERFORM bdc_field USING 'KOMFK-VBELN(01)'
 gwa_bdc-vbeln.
 PERFORM bdc_dynpro USING 'SAPMV60A' '0104'.
 PERFORM bdc_field USING 'BDC_CURSOR'
 'VBRK-FKART'.
 PERFORM bdc_field USING 'BDC_OKCODE'
 '/00'.
 PERFORM bdc_dynpro USING 'SAPMV60A' '0104'.
 PERFORM bdc_field USING 'BDC_CURSOR'
 'VBRK-FKART'.
 PERFORM bdc_field USING 'BDC_OKCODE'
 '=SICH'.
 REFRESH messtab[].
 CALL TRANSACTION 'VF01' USING bdcdata
 OPTIONS FROM wa_options
 MESSAGES INTO messtab.
Please <removed by moderator> help.
Thanks ,
Srikanth.A
Edited by: Thomas Zloch on Sep 15, 2011 1:47 PM

Hi Jurgen
LOOP AT git_bdc INTO gwa_bdc.
 refresh messtab[].
 PERFORM bdc_dynpro USING 'SAPMV60A' '0102'.
 PERFORM bdc_field USING 'BDC_CURSOR'
 'KOMFK-VBELN(01)'.
 PERFORM bdc_field USING 'BDC_OKCODE'
 '/00'.
 PERFORM bdc_field USING 'KOMFK-VBELN(01)'
 gwa_bdc-vbeln.
 PERFORM bdc_dynpro USING 'SAPMV60A' '0104'.
 PERFORM bdc_field USING 'BDC_CURSOR'
 'VBRK-FKART'.
 PERFORM bdc_field USING 'BDC_OKCODE'
 '/00'.
 PERFORM bdc_dynpro USING 'SAPMV60A' '0104'.
 PERFORM bdc_field USING 'BDC_CURSOR'
 'VBRK-FKART'.
 PERFORM bdc_field USING 'BDC_OKCODE'
 '/00'.
 PERFORM bdc_dynpro USING 'SAPMV60A' '0104'.
 PERFORM bdc_field USING 'BDC_CURSOR'
 'VBRK-FKART'.
 PERFORM bdc_field USING 'BDC_OKCODE'
 '=SICH'.
 REFRESH messtab[].
 CALL TRANSACTION 'VF01' USING bdcdata
 OPTIONS FROM wa_options
 MESSAGES INTO messtab.
Error message population....
REFRESH bdcdata[].
ENDLOOP.
Thanks,
Srikanth.A

Batch Determination in Production Order Component Overview Screen on the basis of FIFO, Thickness, Grade, width etc.

I am facing a difficult scenario. Pl. help me out. In my Business Process I am assigning Batches in Production Order Component Overview Screen. Here I am assigning relevant batches to BOM Components manually, My Management want SAP to suggest batches automatically on FIFO basis, thickness, grade, width & first batches should automatically assign to Production order. Can you pl. tell me how to configure this scenario.
Or can I pull stock overview screen at Production Order Component screen to assign relevant batch to BOM Components
Once batches assigned in Production Order component screen cannot be changed. It can be changes by specific persons only.

Hi,
Automatic Batch Determination for production order components is possible by configuration.
You can also refer below discussions to map your scenario.
Batch determination in production order | SCN
Automatic Batch Determination in Production order
Regards,
Naresh

No batch input data for screen SAPMSSY3 0131 in Sales order IDOC

I am processing Sales order IDOCS in status 64 using RBDAPP01 .Some of them error out to status 51 with the message -
No batch input data for screen SAPMSSY3 0131 .
I know the standard IDOC inbound process tries to simulate the posting in a BDC like process.
Now, I went to we19 and the screen hangs up in a pop up in the partners tab with partner type 'WE' and my shipto (which is actually filled in the IDOC), missing..upon repeatedly hitting enter, it goes thru and an idoc is posted in status 53. But still unable to get through the root of this issue.
Any, insight will help.

Hi,
I think the pop-up is generated through and user-exit for which recording is missing. This is why your idoc stays in status 64...
Handle the screen recording in the user exit IDOC_INPUT_ORDERS
user exit routine
PERFORM customer_function_dynpro.
FORM CUSTOMER_FUNCTION_DYNPRO.
CALL CUSTOMER-FUNCTION '002'
    EXPORTING DXVBAK   = XVBAK
              DVTCOMAG = VTCOMAG
              DLAST_DYNPRO = LAST_DYNPRO
              DXMESCOD = IDOC_CONTRL-MESCOD
    TABLES    DXBDCDATA = BDCDATA
              DXVBAP    = XVBAP
              DXVBEP    = XVBEP
              DYVBEP    = YVBEP
              DXVBADR   = XVBADR
              DYVBADR   = YVBADR
              DXVBPA    = XVBPA
              DXVBUV    = XVBUV
              DIDOC_DATA = IDOC_DATA
              DXKOMV    = XKOMV
              DXVEKP    = XVEKP
              DYVEKP    = YVEKP
    EXCEPTIONS
              USER_ERROR = 01.
Regards,
Krishnakumar

Error in LSMW for MM41 - "No batch input data for screen SAPLMGMW 0100"

I'm trying to create an LSMW for MM41 to create new Retail articles en Mass. This will be used to only create the Basic view as other LSMW's already exist to maintain the other views. I've created the Recording and setup the LSMW already. My data is read correctly from the source file. When I execute the batch session it fails with the following error - "No batch input data for screen SAPLMGMW 0100".
I assume the fields in MM41 screen are not setup for batch processing. Could someone with more knowledge or experience in SAP Retail please confirm my assumption and explain where this is setup or provide an alternative to creating new articles en Mass via MM41? The direct input method is more suited for MM01 and not MM41.
Regards
Fawaaz

Hi Guys,
Thanks so much for all the prompt responses. My issue is now resolved.
The issue, I'm sure, was my default settings in the MM41 screen which the recording probably took into account or the batch program didn't like. I deleted my recording and created a new one but before I started the recording, I went into the MM41 screen and removed all default values AND view selections. I made my Basic view selection constant in my recording and also in my field mapping. My LSMW for MM41 is now working perfectly.
Just to answer some of the questions above, my LSMW was Reading and Converting the data in my source file fine. When I display the Read and Converted data, it shows the data fields in the correct place.
Thanks again.
Regards
Fawaaz

"no batch input data for screen SAPLMR!M 6220 in BDC while holding Invoice

Hi
     I am facing a problem while uploading Invoice data and to hold the data in miro transaction I am getting the error
     "no batch input data for screen SAPLMR!M 6220 " . It is for non PO data only I am facing this problem using BDC.
     But for Po based Invoice I am getting Invoice number while holding the Invoice. I am Using SHBDB to record the
      transaction   details
    Please give me some solution regrading this.
Samir

Krish ,
            I am doing it in same transaction MIRO for both PO and NON-PO. I am able to generate an Invoice number while holding   the Invoice For NON-PO taking vendor as invoice Party .While I am recording it in SHDB and trying to use the
same in my BDC Programe it is throughing this error and also by testing the program which has been generated by the
SHDB trnasaction i am getting the same Error . Is there any diferrent trnasaction that is used to hold NON_PO invoice ?
Where Invoice number will be generated automatically ?

No batch input data for screen SAPMSSY3 0131

Dear All,
I have developed a report where i need to upload (old and new)incoterms,payment terms,document type and update in the table ekko with my new values (incoterms,payment terms and document type).
Problem :For this report i have uploaded the excel sheet and values are getting uploaded into my internal table.but when using bapi_agreement_maintain to update the ekko table ,in return table its showing No batch input data for screen SAPMSSY3 0131.
Anyone please give the reason/solution to solve the problem.
Regards,
Bhavani.

Hi,
screen SAPMSSY3 0131 is the debugging screen so if you have any break-points in any of the transactions remove the breakpoint and check.
Basically this BAPI is calling a transaction to execute a transaction in no dialog mode so if you have break-points in any of those program you will face this issue.
Regards,
Himanshu

Error: No batch input data for screen SAPMZVKDIALOGDEMO 1000 Help Needed

Hi Experts!
I wrote a program for BDC. I am attaching the code herewith. When i am trying to process the session in SM35, i was getting the error: No batch input data for screen SAPMZVKDIALOGDEMO 1000. Can anyone please tell me, what am i doing wrong.
Thanks.
REPORT zvkbdcdemo01.
DATA: bdc_tab LIKE bdcdata OCCURS 6 WITH HEADER LINE.
DATA: session LIKE apqi-groupid VALUE 'Session #1'.
CALL FUNCTION 'BDC_OPEN_GROUP'
EXPORTING
 client = sy-mandt
* DEST = FILLER8
 group = session
* HOLDDATE = FILLER8
* KEEP = FILLER1
 user = sy-uname
* RECORD = FILLER1
* PROG = SY-CPROG
* IMPORTING
* QID =
* EXCEPTIONS
* CLIENT_INVALID = 1
* DESTINATION_INVALID = 2
* GROUP_INVALID = 3
* GROUP_IS_LOCKED = 4
* HOLDDATE_INVALID = 5
* INTERNAL_ERROR = 6
* QUEUE_ERROR = 7
* RUNNING = 8
* SYSTEM_LOCK_ERROR = 9
* USER_INVALID = 10
* OTHERS = 11
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
PERFORM fill_bdc_tab.
CALL FUNCTION 'BDC_INSERT'
EXPORTING
 tcode = 'ZVKTR001'
* POST_LOCAL = NOVBLOCAL
* PRINTING = NOPRINT
* SIMUBATCH = ' '
* CTUPARAMS = ' '
TABLES
 dynprotab = bdc_tab
* EXCEPTIONS
* INTERNAL_ERROR = 1
* NOT_OPEN = 2
* QUEUE_ERROR = 3
* TCODE_INVALID = 4
* PRINTING_INVALID = 5
* POSTING_INVALID = 6
* OTHERS = 7
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
CALL FUNCTION 'BDC_CLOSE_GROUP'
* EXCEPTIONS
* NOT_OPEN = 1
* QUEUE_ERROR = 2
* OTHERS = 3
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
*& Form fill_bdc_tab
* text
FORM fill_bdc_tab.
REFRESH bdc_tab.
PERFORM populate_bdc_tab USING:
'1' 'SAPMZVKDIALOGDEMO' '1000',
' ' 'SFLIGHT-CARRID' 'LH',
' ' 'SFLIGHT-CONNID' '0400',
' ' 'SFLIGHT-FLDATE' '07/07/2007',
' ' 'SFLIGHT-PRICE' '1982',
' ' 'SFLIGHT-CURRENCY' 'EUR',
' ' 'SFLIGHT-PLANETYPE' 'A310-300',
' ' 'BDC_OKCODE' 'CREA'.
ENDFORM. "fill_bdc_tab
*& Form POPULATE_BDC_TAB
* text
* -->FLAG text
* -->VAR1 text
* -->VAR2 text
FORM populate_bdc_tab USING flag var1 var2.
CLEAR bdc_tab.
IF flag = '1'.
 bdc_tab-program = var1.
 bdc_tab-dynpro = var2.
 bdc_tab-dynbegin = 'X'.
ELSE.
 bdc_tab-fnam = var1.
 bdc_tab-fval = var2.
ENDIF.
APPEND bdc_tab.
ENDFORM. "POPULATE_BDC_TAB

This normally means that you are trying to insert data on a screen for which a particular field is not available.
So check screen number, screen fields and report name. In case of screen fields, use F1, F9 (technical information), and check the name of the screen field for batch processing (all the way at th bottom of the pop-up). This can differ from actual name of the screen field.
If all this is ok, try to create a recording of the transaction with SM37.

Batch Input Overview Screen

Similar Messages

Maybe you are looking for