Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Batch Input Session

Former Member
0 Kudos

Hi,

What are the problems in processing the Batch Input Session. and how is batch input session is different from processing on line..?

Thanks in Advance..

Regards

Rai..

1 ACCEPTED SOLUTION

Former Member
0 Kudos

hi

Refer to following links

https://www.sdn.sap.com/irj/sdn/advancedsearch?query=problemsinbatchinputsession&cat=sdn_all

https://www.sdn.sap.com/irj/sdn/advancedsearch?query=processing+batchinput+session&cat=sdn_all

https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=problemsprocessingbatchinput+session&adv=false&sortby=cm_rnd_rankvalue

reward if helpful...

regards.

3 REPLIES 3

Former Member
0 Kudos

hi

Refer to following links

https://www.sdn.sap.com/irj/sdn/advancedsearch?query=problemsinbatchinputsession&cat=sdn_all

https://www.sdn.sap.com/irj/sdn/advancedsearch?query=processing+batchinput+session&cat=sdn_all

https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=problemsprocessingbatchinput+session&adv=false&sortby=cm_rnd_rankvalue

reward if helpful...

regards.

Former Member
0 Kudos

Hi Rai,

The SAP System offers two primary methods for transferring data into the System from other SAP Systems and non-SAP Systems. These two methods are collectively called "batch input" or "batch data communication."

Batch Input Method

Batch input method is a type of data transfer method. It is used for bulk data transfer; it is one of the primary ways by which data can transferred into the R/3 System. This method is not for near real-time data transfers.

There are various typical uses of batch input. One of the ways includes the one-time import of data. This import of data is from a legacy system into a newly installed R/3 System. In addition to it, another typical use is for periodic (i.e. hourly, daily..., and so on) transfers of data. These transfers are from external systems or legacy systems which are still in use into R/3 system where all enterprise data is consolidated.

The R/3 applications deliver different programs for batch input, which are ready to be used. However, in some cases a customer has to write his or her own batch input program. This is required in order to convert the concerned data from a legacy System or from a proprietary format into an R/3 data format.

The process flows for a batch input are discussed below.

Data Transfer Decision-Making: It is with a decision to transfer data from an external source into R/3 that the process of batch input begins. It is probable that the external source may be a legacy system that is being replaced. A one-time bulk data transfer is foreseen in this regard. Alternatively, the external source may be an external system that is to remain in use. In this case, a regularly recurring bulk data transfer is foreseen.

Setting up Batch-Input for Data Transfers: If R/3 standard one-time or regular data transfers are required, then by means of customizing settings in the R/3 Customizing System in SAP ASAP set up will occur. You must set up custom batch input procedures by hand, which means the system administrator must schedule the data conversion program that creates the batch input session. The system administrator and the batch input programmer must determine the following: how frequently data is made available from the external system, how frequently the conversion program should run, and whether the conversion program runs in R/3 (ABAP program) or in a host system (external program).

Processing Batch Input Sessions: When a batch input session is processed, then the actual transfer of data into R/3 takes place. Little attention is required in processing of batch input sessions by the system administrator. Usually, the starting of batch input sessions is automated by the system administrator. If necessary, the administrators can also start batch input session explicitly from transaction SM35.

Checking Batch Input Sessions: For a system administrator the routine activity is to check daily or more frequently in transaction SM35 whether all batch input sessions have been completed successfully. It is the schedule for running batch input sessions on which the schedule for checking sessions depends upon. For doing this check the R/3 System provides easy-to-use batch input management tools.

Analyzing Errors: It is the duty of the system administrator to analyze the problem if one or more transactions in a session end in errors. Usually, the assistance of the affected data entry specialist or department for this analysis will be needed by the system administrator. In the situation where the problem was caused by incorrect data conversion or incorrect generation of the batch input session then the programmer who wrote the data conversion program may also need­ to be involved.

check the link :

http://help.sap.com/saphelp_40b/helpdata/en/fa/097015543b11d1898e0000e8322d00/content.htm

Thanks

Murugan.B

Former Member
0 Kudos

HI,

PROBLEMS:- i) If the user forgets to opt for keep session then the session will be automatically removed from the session queue(log remains). However if session is processed we may delete it manually. ii)if session processing fails data will not be transferred to SAP database table.

sessions can not run fast and not in parallel

thanks

shankar

reward me if usefull