BDC_OPEN_GROUP - ooxxvv/MySAPnotes GitHub Wiki
BDC_OPEN_GROUP
- Open batch input session for adding transactions
一般說明
Use the BDC_OPEN_GROUP function module to do the following 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.
EXPORTING
IMPORTING
- 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 SAP System. Background users are user master records that are specially defined for providing authorizations for background processing jobs.
{{{#!comment
TABLES
EXCEPTIONS
Attributes
Methods
Code
{{{#!abap }}} }}}