Delete Batch input Jobs,New or Incorrect from SM35
Hello,
I found too much entries in SM35 transaction, some are from year 2002. Can I delete these entries without problem? or this problem must be analized by functional area?
Thanks in advance.
Kind regards.
Kindly check with the <b>process owners</b> for the same. Keep a mail to the process leads depending on the transactions, get a confirmation and then proceed to delete incase of Production System.
Kind Regards
Eswar
Similar Messages
-
Tracking Deleted Batch Input Map from SM35
Dear All,
I want to find the details of deleted Batch Input Maps from SM35. e.g. if some one deletes a Batch Input Map from SM35 transaction then I need to find the details of the user along with date and time.
I tried finding the table but I could not. Please let me know if this is possible some way.
Regards,
lalitAFAIK this information is not stored in SAP database
(Check FM BDC_OBJECT_DELETE and include LSBDCF01 form DELETE_SESSION of FG SBDC)
You may ask system to store it in DBTABLOG "Log Records of Table Changes"
- (SE11) Activate the general logging for the table - the technical setting of
the table needs to be adjusted to "Log data changes". To check whether
it is activated for a table, use transaction AUT01.
- (RZ10/RZ11) You may also be required to set the profile parameter rec/client on.
Regards,
Raymond -
I am not able to open a batch input job using SM37
Hi Gurus,
I am not able to open a batch input job using SM37. I enter SM37 through a well authorized ID. May be there is a authorization issue or may be not. I check all the check boxes even then it is not possible. Please help me.Hi Amit Sharma,
If I am not wrong, the problem would be because you have not closed the job after creating it.
You must have used JOB_OPEN, JOB_SUBMIT but not JOB_CLOSE.
Job_Close is the FM which submits the created job to the background processing system.
Hope this resolves. If not, paste your code here so that we can have a look
Thanks,
Babu Kilari -
How to delete batch input session still in process since year 2000
Hi All,
in our productive system we have still batch input session in process from year 2000, and I would like to delete them, but how to do this, because the error message is "Unable to schedule session .....".
Thanks for your helpHi Olivier ,
Such error occurs when you are trying to run session in foreground and some error occurs with connection.
As such these session are not harmful in any way. You can request basis person to remove those sessions.
Regards,
Mohaiyuddin -
Hi,
I need to assess who and when have deleted the batch input sessions using SM35 tcode.Batch deletion can be viewved from SM21 system log where it also shows which user deleted the batch sessions. But if the number of entries are more then you may miss the messages in system log. So better you check the log for these deletions in regular intervels.
Regards,
Raju. -
RSBDCSUB - Batch Input - Job - Authorization
Dear All,
I want to execute session in background using the program RSBDCSUB, but I want to change the user of the session.
User A creates the Batch input (TC FB03), but doesn't have the authorization to modify an FI document.
User B has this authorization, and execute the BI.
There is no problem if user B execute the session online, but if he use RSBDCSUB, then the system keeps the authorization of user A. The idea is that the USER B creates a job running RSBDCSUB several times a day and we don't want to give the authorization to user A .
Do you know if there is a possibility to do it ?
Thanks for your help
Nathaliecreating a BI session usually is done with function module BDC_OPEN_GROUP.
One of the importing parameters is the USERID, usually filled with SY-UNAME (the user who executes the function module/report/transaction) but you could overwrite it with any other valid user. If you don't have a report parameter to set the user different from SY-UNAME you would have to modify the report.
Alternativly a report could be written that changes the user after the session is created. -
Deleting batch emails one at a time from your inbox
Unfortunately I receive between 200 to 400 emails a day. i recently upgraded to ISO 7 in hopes they added a way to bulk delete emails (the same option that is available for your trash emails). Unfortunately, you still need to delete them one at a time. I'm not sure if that is a safety feature so you don't accidentally delete all your emails, but I for one would love to have the option.
I have a pop 3 account, if anyone knows a different way I could achieve this, I would be grateful if you could advise me how to accomplish this. Thank you in advance for your help.Two suggestions:
1. From the screen that shows your inbox, click "Edit" at the upper right and then check all the emails in the screen. That might be about six emails. It might take three seconds or so to perform that action. Then either click "trash" in the lower right or scroll up and check off some more. This is a speedy way to delete those emails.
2. Use your email provider's junk mail filter to filter out those emails that you wish to ignore. -
Security authorizations - batch input session - deleting your own session
I know that S_BDC_MONI will allow you to delete Batch Input sessions (SM35), but it looks like it will allow you to delete whatever you put in BDCGROUPID, irrespective of whether it's your session or some one elses.
Is there anything in security, which will allow you to only delete your own sessions, other than having different session names for different people.Hi,
Execute the session in error mode only. If you are still facing the problem, you will have to execute it in foreground.
Regards,
Amit -
Batch input deleted by mistake - solution
Hi experts,
I have deleted by mistake my bacth input for the revaluation program SAPF100.
Do you know any solution to recover this batch input?
Thanks,
KarimHi,
For getting deleted batch input session discuss with BASIS team,
OR
Create once again batch input not an issue.
Regards,
Viswa -
Hi
Can any one tell me the what is the procecure to delete the batch input
thanks
samiDear Sami,
Go to SM35, select the session needs to be deleted, right click and choose delete.
Caution : need to be very much clear about the usage of session you are about to delete.
Assign points if helpful.
Cheers
Ashok kumar -
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 -
Hi Gurus,
We schedule background jobs to convert Planned order to a Production order using program PPBICO40. This program/job is generating batch input sessions, weekly we go to SM35 and delete these sessions manually. This is becoming a weekly maintenance task.
Would like to know is there a way to get rid of these sessions, without deleting them manually or is there any setting that the program PPBICO40 do not generate batch input sessions whenever it runs in the background. We are using 4.6c.
Thanks in advance
SriniHi,
There is noway to get rid of this. At least you need to give some inputs, then only the system will consider that particular inputs for the background job. You can create a variant, but eventhough you need to give some inputs.
Regards,
V. Suresh -
No batch input data for screen SAPMF02K 0101 for transaction XK02
Hello Friends,
I am Trying to change detaisl of Vendor using IDOC for T code XK02, I am getting an error in background
No batch input data for screen SAPMF02K 0101
Message no. 00344
When I execute in foreground it is working fine.
Diagnosis
The transaction sent a screen that was not expected in the batch input session and which therefore could not be supplied with data.
Possible reasons:
1. The batch input session was created incorrectly. The sequence of screens was recordly incorrectly.
2. The transaction behaves differently in background processing in a batch work process than when running in dialog (SY-BATCH is queried and changes the screen sequence).
3. The transaction has undergone user-specific Customizing and therefore certain screens may be skipped or processed differently, according to the current user. If the person who created a batch input session is not the same as the person now processing it, this problem may occur frequently.just info: as u seen in the 3rd point, if u r running onlien, its recorded on ur user id, but, where as for back ground, the user lke WF_BATCH.........so, for this user, the settings may b different from a dialog user, in terms of screen sequence, pop-ups. mandatory fields.
So, i guess, u r missing to populate a input field, which is mandatory. May be by suing sy-batch IF condition, u hv to change CTU_PARAMS values, like sy-batin = 'X'......actually, these day si dont hv SAP access, so, pls. check some terms in this response.
thanq -
Dear all,
I am uploading the bank statements using manual bank statements through Z transaction, Once uploaded system is generating the batch input session for the same.
When i run the batch input session system not clearing outgoing payment automatically based on the assignment field, as i have alreday mentioned the same assignment while posting the document and in the excel file.
I am getting the following message while running the batch input session.
No batch input data for screen SAPDF05X 3100
Message no. 00344
Diagnosis
The transaction sent a screen that was not expected in the batch input session and which therefore could not be supplied with data.
Possible reasons:
1. The batch input session was created incorrectly. The sequence of screens was recordly incorrectly.
2. The transaction behaves differently in background processing in a batch work process than when running in dialog (SY-BATCH is queried and changes the screen sequence).
3. The transaction has undergone user-specific Customizing and therefore certain screens may be skipped or processed differently, according to the current user. If the person who created a batch input session is not the same as the person now processing it, this problem may occur frequently.
System Response
None.
Procedure
For 1: Either re-create the session or process it in expert mode. Correct the batch input program.
For 2. It is very difficult to analyze this problem, particularly in the case that the screen sequence or the display-only options of fields differ according to whether the transaction is being processed in the background or as an online dialog. It could also be that this kind of transaction cannot run with batch input.
For 3: Have the creator of the session process it. If no error occurs now, then this is a program with user-specific Customizing.
Please let me know solution for the same.
Regards,
AnandHi,
This may not be a solution but may help you to isolate the problem
a) Are you able to load the bank statement for other banks without error ?
b) Try for the same bank in a different system .
c) If it is working for different bank then check the file format is the same for both the banks.
d) If it is working in different system check the ABAP code for any changes between the system,
e) Are you getting this message for all the line items or only for some line items ?
Regards
K.R -
RFBIBL00 No Batch Input Created after Executing
Hello,
After Executing SAP standard report - RFBIBL00, no batch input session has been created in SM35 in ECC 6.0 version. There is no error message but one message displayed as 'PRODPER not transferred.'First the issue was in the input file.
Second Number of lines was more and in the report it was set less.
Third in check only there will no Batch Input session generates.
Fourth to create input file use SAP standard procedure i.e sxda_tools.
Note : From ECC, SAP not supporting Batch Input Method.
Maybe you are looking for
-
Sorting order of pictures from Aperture in an iPod slideshow
I've recently got a video iPod and have transferred all my photos to it from Aperture. I found that it was necessary to create an album for every project in my Aperture library in order for the projects to show up on the iPod. Having got all my proje
-
When are the prices for the new Macbook Pro with Retina Display going DOWN!?
i want to buy it but it but its almost unafordable for me!!! please lower ir down for GODS SAKE!!!
-
Virtual shopping cart in iweb'09?
I would like to add a virtual shopping cart to my website-customers click on the check boxes and it adds it to a cart, the total is a quote only. I just want a simple cost calculator on my site. Is there a way to do this in iweb'09, or any html or so
-
Sharts and graphs with Dataminer in SQL DEVELOPER
How can I view the results of my worklofw diagrams in SQL Developer
-
How do i create mailboxes