Choose alternative BOM in batch input

Hi!
I'm starting using BOM alternative and I'm facing a problem. I have a batch input where I need to choose an alternative BOM, but the popup for choosing the alternative doesn't show up when in batch input mode.
Does anybody have a clue?
Regards.
Fabio Scaravelli

TAJUDDIN,
I think this thread is SD, because the transaction is VA01 (I forgot to mention it, sorry). The BOM usage is 5 (Sales and distribution).
I need to choose an alternative BOM among two ones. But when VA01 is ran in batch input mode, the popup for choosing the alternative doesn't show up and the first alternative is selected by default.
Regards.
Fabio Scaravelli

Similar Messages

How to create Alternative Bom by given inputs

Hi to all,
I need to create BOM with alternative number.
my inputs are
BOM Header
Material, plant, BOM usage, Alternate BOM, BOM status, Base Qty, Valid From, valid to
BOM Item
Item number, item category, component, component description, UOM, valid from, valid to, item ID, QTY
if i use CSAP_MAT_BOM_CREATE to create BOM , it will not create alternative number
if i use BAPI_MATERIAL_BOM_GROUP_CREATE , does my input value are enough to create alternative bom.
please can any one, put some light on it, i search SDN ,but i dont know how to create alternative bom with input provided.
i shall be thankful to you for this.
Regards
Pavneet Rana

Try the program-RCSBI010

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

Is there any BAPI for BOM creation? which does by RCSBI010 / Batch Input.

Hi Experts,
I need to Upload the extracted Excel-file(.txt) for BOM creation, so, pls, let me know that, Is there any BAPI for this purpose. In detail the requirement is that,
The suggested idea shuld work as like as pgm. RCSBI010
thanq
Edited by: Srinivas on Feb 14, 2008 6:18 PM

Hi Srinivas,
Try these Function Modules
CS_BI_BOM_CREATE_BATCH_INPUT - Create BOM Via Batch Input
CS_BI_BOM_CREATE_BATCH_INPUT1 - Create BOM Via Batch Input (Corrected Session Handling)
There are two BAPI's too, which can be used
ALE_MATERIAL_BOM_GROUP_CREATE
BAPI_MATERIAL_BOM_GROUP_CREATE - Creation of a material BOM group
Hoe this helps.
Edited by: Priyabrata Samanta on Feb 15, 2008 3:56 AM

General task list: component selection from BOM - possible in batch input?

Hi experts,
for the assignment of non-stock material to general task lists I have followed the advice from message[6115684|Re: General Task List Components;.
So what I have done is:
- Include non-stock material in BOM
- Assign BOM to general task list header
When clicking on the "Component selection" button in the task list components, I can select a component.
When entering the material number of the component directly though, I get an error: "Material type X and line item type L not compatible" (CO135).
I would like to upload the general task lists with a batch input recording, but I can't figure out how to select components.
Any thoughts?
Kind regards,
Andreas

Hello,
We have the same requirement to load tasklists (change & create). We are using the function modules EAM_TASKLIST_CREATE and EAM_TASKLIST_CHANGE. However, i cannot get a non-stock BOM item to process. Has anyone got this working?
Thanks,
Clay.
EDIT: Found the answer - simply fill in the fields for BOM on the component (STLTY, STLNR, STLKN, and STLAL).
Message was edited by: Clayton Mergen

Calling Batch input from Web Dynpro - any alternatives for table updates?

Hi!
I am asked to create a screen in Web Dynpro for the GJ30 transaction (JV Cutback mapping of WBS' elements). I created a remote enabled function module which call batch input for GJ30 . Testing the Function modules direclty goes fine, but not calling the function module from WD. then I get the same error message as when I once tried to call SAP GUI from Web Dynpro ( Call transaction /submit program).
My next step is to try to create a batch input session (instead of call transaction) and run it using rsbdcsub, and then check the result of the run. But maybe this will fail of the same reason as well, and I suppose this will make the user waiting longer for the response .
I read somewhere that Web Dynpro does not support batch Input. But what can you do when there are no standard BAPI's for the update you want to do in SAP ? We are not supposed to do direct table updates.
Anyone who have struggled with the same issues and found a solution??
regards, Tine

Hi,
as BDC is calling screens and in Webdynpro ABAP you cannot use SAP GUI sceeen, you are getting short dump.
Refer CNTL_SYSTEM_ERROR in webservices from r/3 system
Thanks,
Chandra

Component Allocation LSMW not working for materials having alternative BOMs

Hi Experts,
I have a requirement in Component allocation LSMW.
Component Allocation LSMW was created using a material which do not have an alternative BOM and the LSMW NOT working for materials having alternative BOMs. Currently iam using Batch Input Recording method in LSMW.Can any one suggest me is it possible by recording method in Lsmw. Because in transaction CA02 when we click the CompAlloc button in application tool bar we get a pop up screen with alternative BOM's, we have to choose any of them. If we choose any of the alternatie BOM in the pop up screen then it will be fixed always, but depending upon my flat file value of alternate BOM i need to pick the value. It is not static.
Can any one suggest me is there any BAPI for this requirement.
Your hel will be greatly appreciated.
Thanks & Regards,
Venkat.

Use BDC instead of LSMW, that will solve your problem.

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

Problems while creating a batch input

Hi Experts,
I tried to create a batch input program for the transaction CRMD_ORDER for some changes on to the configuration tab to enable the BOM to work. This cannot be done by the BAPIs. I have included the batch input program in a RFC enabled function module to do this job. I am getting the error control framework: fatal error - GUI cannot be reached and Runtime error RAISE_EXCEPTION has occured. This happens only in the mode N, if i re run the session with the other modes there are no problems.
I am call the function module through a method in the controller class.
Replies are highly appreciated.
Thanks in Advance.
Regards,
Suthagar

Hi Durai,
I tried that option too. Ufortunately the same error has happened. The problem is solved using 3 other function modules, by not using the BDC.
Appreciate your reply. Thanks!
Regards.
Suthagar

Creation of Batch Input for transaction C201

Hello,
Currently I am having a requirement to create a batch input session for tcode C201.
Following steps we need to perform using batch input session:
1. Go to tcode C201 and enter material and Plant.
2. Then click on choose template and give Mater Recipe option.
3. On next screen enter Recipe Group and Recipe.
4. After that it will go to Copy Master Recipe screen and then giving status it will open other tabs like Operations, Materials etc.
Now when I create recording, till step 3 it is continuing correctly. but when press enter after step 3 it goes to Create Mater Recipe instead of Copy..
I got one SAP note 142022 but dont know how to implement this in my case.
Can you please help me?
Thanks and Regards
Nishad

As [Note 142022 - Batch input and CATT in recipe|https://service.sap.com/sap/support/notes/142022] explain, you have to add one step in your batch input with BDC_OKCODE "=TOFF" on the first dynpro so C201 will always use old screens which are batch-input compatible. (First check [Note 365051 - OK code TON does not work when creating recipes|https://service.sap.com/sap/support/notes/365051] is implemented on your system)
SAPLCPDI 4000
BDC_CURSOR RC271-PLNNR
BDC_OKCODE =TOFF
Regards,
Raymond

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

Critical Issue: Availabilty check & alternative BOM selction issue

During the upgradation project I'm working facing the following critical issues:
1)While creating the sales order, system carries out the availability check in APO.In material master checking group Z5 is defined.
 Actually I want to know hw the system carries out the search in APO & what are the settings in R/3 or APO we have to make?
2)Suppose there are 3 alternative BOM's of a finished product.A requirement is while creating the sales order availabilty check should be carried out & system should check the availability of components on the required date.If the component is not avalable system should go & check the second alternative...third alternative until it gets the confirmation of component availability.
 How we can set this functionality & what are the prerequisites or customisation settings we needs to make?
 Would appreciate providing your inputs on this critical issue.
Thanks,
Nilesh

Before you understand how the APO Availability Checking concept works, I would suggest you understand about the regular R3 availability checking. As this is the core for the SD and APO GATP. Refer help.sap.com
Question 1:
Settings in R3: You have the ATP integration model in CFM1 transaction. You need to activate this just one time and never again. what this does is basically transfer all your availability checking customizing to APO.
All the settings for the Availability Checking group ( Z5, etc) are already maintained in R3 and they get transferred to APO by the integration model. You donot need to anything else.
Settings in APO:
If you are using Product Allocation Concept, You have to maintain the Check Instructions.... Otherwise there are no other settings in APO
Availability Check in APO :
( see the following blog for the requirements class( Name in R3) or check mode( Name in APO) determination http://solution-timezone-issue.blogspot.com/ )
The check mode and the business event( These are hardcode internally in R3 - For SD- A) are determined from the order and based on this in APO it follows the following order
(1) Reads the check instructions settings in APO
For example say the following have been determined from the SD Order : Check Mode 041 and Business Event A
Say we have maintained in APO that the first step is Availability Check and all the other two steps we havent maintained or left blank ( Product Allocation and Forecast)
Look for the customizing in APO
SPRO>APO>GATP>General Settings>Maintain Check Instructions ****
(2) Carries out availability Checking same as in R3 and no different
From the masterial master considers the availability checking group ( Ex: Z1) and the business event( SD transactions- A)
Very Important and the core of availability checking which is similar in R3 and APO***
Against these 2 combinations, the settings are checked which define what stock and in/outward movements are to be considered during the availability check
For customzing settings in APO
SPRO>APO>GATP>Maintain Check Control>
 For Customizing in R3
SPRO>Sales and Distribution>Basic Functions>Availability Check and transfer of requirements>Availability check with ATP logic or planning>Carry out control for availability check
This is the answer to your first question.
Your second question would need some time and I will try to answer it as well.
Hope this helps you..

Reg: Creation of BOM along with Alternative BOM

Hi Experts,
I have written the below code for creating BOM along with Alternative BOM, I'm getting the following error.
W BAPI1080 028
Error/warning when checking the structure of the BOM group with ID=
A BAPI1080 002
Basic data for (BOM) group available twice
A BAPI 001
No instance of object type BOMGroup has been created. External reference:
W BAPI1080 028
Error/warning when checking the structure of the BOM group with ID=
A BAPI1080 002
Basic data for (BOM) group available twice
A BAPI 001
No instance of object type BOMGroup has been created. External reference:
Please find the piece of code below.
SORT it_bom01 BY matnr idnrk posnr ASCENDING.
LOOP AT it_bom01 INTO wa_bom01.
 AT NEW matnr.
 CLEAR:
 it_bomgroup[],
 wa_bomgroup,
 it_variants[],
 wa_variants,
 it_items[],
 wa_items,
 it_matrel[],
 wa_matrel,
 it_itemas[],
 wa_itemas,
 it_return.
 ENDAT.
* Material BoM Group Header Data
 wa_bomgroup-bom_group_identification = 'IDENTIFICATION'.
 wa_bomgroup-object_type = 'BGR'.
 wa_bomgroup-object_id = 'ID'.
 wa_bomgroup-bom_usage = wa_bom01-stlan.
 wa_bomgroup-ltxt_lang = sy-langu.
 wa_bomgroup-technical_type = ' '.
* wa_bomgroup-bom_text = .
 wa_bomgroup-created_in_plant = wa_bom01-werks.
 APPEND wa_bomgroup TO it_bomgroup.
* Header Details of the different variants
 wa_variants-bom_group_identification = 'IDENTIFICATION'.
 wa_variants-object_type = 'BOM'.
 wa_variants-object_id = 'ID'.
 wa_variants-alternative_bom = wa_bom01-stlal.
 wa_variants-bom_status = wa_bom01-stlst.
 wa_variants-base_qty = wa_bom01-bmeng.
 wa_variants-valid_from_date = wa_bom01-datuv.
 wa_variants-alt_text = wa_bom01-alt_text.
 wa_variants-function = 'NEW'.
 APPEND wa_variants TO it_variants.
* Details of the items of the variants
 wa_items-bom_group_identification = 'IDENTIFICATION'.
 wa_items-object_type = 'ITM'.
 wa_items-object_id = 'ID'.
 wa_items-item_no = wa_bom01-posnr.
 wa_items-item_cat = wa_bom01-postp.
 wa_items-component = wa_bom01-idnrk.
 wa_items-comp_qty = wa_bom01-menge.
 wa_items-valid_from_date = wa_bom01-datuv.
 APPEND wa_items TO it_items.
* Details of the materials of the different variants
 CLEAR it_matrel.
 wa_matrel-bom_group_identification = 'IDENTIFICATION'.
 wa_matrel-material = wa_bom01-matnr.
 wa_matrel-plant = wa_bom01-werks.
 wa_matrel-bom_usage = wa_bom01-stlan.
 wa_matrel-alternative_bom = wa_bom01-stlal.
 APPEND wa_matrel TO it_matrel.
* Linking items to the corresponding variants
 CLEAR it_itemas.
 wa_itemas-bom_group_identification = 'IDENTIFICATION'.
 wa_itemas-sub_object_type = 'ITM'.
 wa_itemas-sub_object_id = 'ID'.
 wa_itemas-super_object_type = 'BOM'.
 wa_itemas-super_object_id = wa_bom01-matnr.
 wa_itemas-valid_from_date = wa_bom01-datuv.
 wa_itemas-function = 'NEW'.
 APPEND wa_itemas TO it_itemas.
 AT END OF matnr.
 CALL FUNCTION 'BAPI_MATERIAL_BOM_GROUP_CREATE'
 EXPORTING
 all_error = 'X'
 TABLES
 bomgroup = it_bomgroup
 variants = it_variants
 items = it_items
 materialrelations = it_matrel
 itemassignments = it_itemas
 return = it_return.
 CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
 LOOP AT it_return.
 WRITE:/ it_return-type, it_return-id, it_return-number,
 it_return-message.
 ENDLOOP.
 ENDAT.
ENDLOOP.
Thanks and Regards,
Abdur Rafique

Hi Sree,
I used your code, I removed the levels because, i have only one level 'the lineitems'. Please find the modified code below. I'm not able to create the BOM, it throws an error as "BOM is recursive". I checked the header and item contents before passing to FM, it is correct.
Please help me with the solution.
REPORT zbom_sdn.
TYPE-POOLS: truxs.
DATA: bom_header LIKE cad_bicsk,
 bom_item TYPE TABLE OF cad_bom_item WITH HEADER LINE,
 bom_sub_item TYPE TABLE OF cssubitem WITH HEADER LINE,
 dms_class_data TYPE TABLE OF cls_charac WITH HEADER LINE,
 sap_field_data TYPE TABLE OF rfcdmsdata WITH HEADER LINE,
 e_return LIKE cad_return-value,
 e_message LIKE message-msgtx,
 e_message_len LIKE cad_return-message_len.
DATA v_item TYPE i.
TYPES : BEGIN OF ty_data,
 matnr TYPE cad_bicsk-matnr," Material
 werks TYPE csap_mbom-werks," Plant
 stlan TYPE csap_mbom-stlan," BOM Usage
 datuv TYPE csap_mbom-datuv," Valid From
* posnr TYPE stpo_api03-item_no," Item Number
 idnrk TYPE stpo_api03-component," BOM Component
 postp TYPE stpo_api03-item_categ," Item category
 menge TYPE cad_bom_item-menge," Quantity
 bmeng TYPE stko_api01-base_quan," Base Qty
 stlst TYPE stko_api01-bom_status," BOM Status
 stlal TYPE csap_mbom-stlal," Alternative BOM
 alt_text TYPE stko_api01-alt_text," Alternative BOM text
 END OF ty_data.
DATA : it_data TYPE TABLE OF ty_data ,
 wa_data TYPE ty_data.
DATA: wa_raw TYPE truxs_t_text_data.
SELECTION-SCREEN BEGIN OF BLOCK b2 WITH FRAME TITLE text-001.
PARAMETER : p_file TYPE rlgrap-filename OBLIGATORY.
SELECTION-SCREEN END OF BLOCK b2.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
CALL FUNCTION 'KD_GET_FILENAME_ON_F4'
 EXPORTING
 program_name = syst-repid
 dynpro_number = syst-dynnr
 CHANGING
 file_name = p_file.
START-OF-SELECTION.
CALL FUNCTION 'TEXT_CONVERT_XLS_TO_SAP'
 EXPORTING
* I_FIELD_SEPERATOR =
 i_line_header = 'X'
 i_tab_raw_data = wa_raw " Work Table
 i_filename = p_file
 TABLES
 i_tab_converted_data = it_data[] " Actual Table
 EXCEPTIONS
 conversion_failed = 1
 OTHERS = 2 .
IF sy-subrc <> 0.
 MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
CLEAR: bom_header, bom_item, bom_sub_item.
REFRESH: bom_item, bom_sub_item.
DATA : v_lineitem TYPE sposn VALUE '0000',
 v_slineitem TYPE sposn VALUE '0'.
LOOP AT it_data INTO wa_data.
 CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
 EXPORTING
 input = wa_data-matnr
 IMPORTING
 output = wa_data-matnr.
* fill BOM header
 CLEAR bom_header.
 bom_header-matnr = wa_data-matnr. "'000000000200000016'.
 bom_header-stlal = wa_data-stlal. " Alternative Bom
 bom_header-werks = wa_data-werks. "'1000'.
 bom_header-stlan = wa_data-stlan. "'3'.
 bom_header-bmeng = wa_data-bmeng.
 bom_header-cadkz = 'X'.
 bom_header-stktx = wa_data-alt_text.
* bom_header-ztext = wa_data-text.
 bom_header-datuv = wa_data-datuv."'01.10.2010'.
* fill item
 v_lineitem = v_lineitem + 10.
 CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
 EXPORTING
 input = v_lineitem
 IMPORTING
 output = v_lineitem.
* bom_item-upskz = 'X'. " If We hav the Sub items Enable it.
 bom_item-idnrk = wa_data-matnr. "'000000000200000017'.
 bom_item-posnr = v_lineitem.
 bom_item-postp = wa_data-postp."'L'.
 bom_item-menge = wa_data-menge. "'1'.
* bom_item-fmeng = wa_data-fqty.
 APPEND bom_item.
 CLEAR: bom_item.
 AT END OF matnr.
 CALL FUNCTION 'CAD_CREATE_BOM_WITH_SUB_ITEMS'
 EXPORTING
 i_bom_header = bom_header
 i_auto_posnr = ''
 IMPORTING
 e_return = e_return
 e_message = e_message
 e_message_len = e_message_len
 e_bom_header = bom_header
 TABLES
 bom_item = bom_item
 bom_sub_item = bom_sub_item
 dms_class_data = dms_class_data
 sap_field_data = sap_field_data
 EXCEPTIONS
 OTHERS = 1.
 REFRESH bom_item.
 WRITE : e_message.
 ENDAT.
 CLEAR wa_data.
ENDLOOP.
Thanks and Regards,
Abdur Rafique

Clearing receivable items by batch input

HI all,
in account receivable scenario my question concerns automatically clearing items (program RFEBBU00 create a batch input session) by using reference field instead of document number. I am not able to do it by customizing.
Can you help me?
Regards
Federico

F.13 program SAPF124 is used for automatically clearing customer accounts.
You can choose the required field that shall be the criteria in IMG
SPRO>IMG>Financial Accounting>Accounts Receivable and Accounts Payable>Business Transactions>Open Item Clearing>Prepare Automatic Clearing.

LSMW for Vendor Master using Batch Input/Direct

Hi Folk,
I'm trying to create a LSMW for Vendor Master using Batch Input/Direct Input and in the step Create Batch Inout Session a error message appears:
Trans. 1 XK01: Acct already exists; general area not being processed.
Can somebody help me with this...........

Hi,
Check manually create vendor. Check with recording steps means strucutre creadred while you choose BDC recording option. With same data r u able to create vendor.
Regards
Md.MahaboobKhan

Choose alternative BOM in batch input

Similar Messages

Maybe you are looking for