Import Parameters for Transferring Actual Data

The following parameters are not dependent on the area for which you want to transfer actual costs. These parameters are required to create a batch input session. You can ignore these parameters if you use a direct update for processing. If that is the case, you need to set up the ONLINE parameters.

Import Parameters for Function Modules for Transferring Actual Data

Parameter	Description
CLIENT	Client
HOLDDATE	Lock session until specified date
KEEP	Checkbox to keep the finished sessions in the session overview
MAPN_R	Session name
MAPN_E	Session name for session with incorrect data
MAPNAME	Session name
ONLINE	Checkbox for online processing (' ', A, E, N)
SORT_TAB	Sort checkbox
USER	User name

Import Parameters for Transferring Actual Data

The ONLINE parameter controls how actual data is transferred to the SAP system.

With a batch input session (blank space):

This is the default value.

Without a batch input session, by direct data transfer:
- Online (A)
  The data is transferred without a batch input session and can be seen by the user.
- Online for errors (E)
  The data is transferred without a batch input session and can seen by the user if an error occurs.
- In background (N)
  The data is transferred without a batch input session and cannot be seen by the user.

The SORT_TAB parameter is defaulted with X in the standard system. The SAP system checks the data for completeness and sets the EFLAG indicator depending on the results of its check. The error indicator can have the following values:

EFLAG = "0"
Data record is complete
EFLAG = "1"
Data record is incomplete
EFLAG = "2"
BUDAT, BLDAT incorrect, or no KOKRS

The SAP system then sorts the data according to posting date (BUDAT), document date (BLDAT), controlling area (KOKRS), and error indicator (EFLAG).

Note Note

If you have not set the sort indicator, you should transfer the data already sorted to the SAP system, otherwise many new screens are requested if the data changes, which has an adverse effect on system performance.

End of the note.

You create batch input sessions with a client (CLIENT) and for a user (USER). When you process a session, the SAP system runs an authorization check on the user. The authorizations of the user who created the session are valid. During the session run, the authorizations of the user who is running the session are valid.

When you activate the KEEP parameter, processed sessions are kept in the session overview. All other sessions are deleted.

The HOLDDATE parameter blocks sessions up until the date that you assign to this parameter. You cannot run blocked sessions. This is useful for preventing sessions that contain errors from being rerun, or if you have to run a session on a particular date.

The SAP system creates up to two sessions.

MAPN_R
Contains records with EFLAG = "0", complete data

MAPN_E
Contains records with EFLAG = "1", incomplete data

Records with EFLAG = "2" are not transferred to a session.

If you run a session with incomplete data, the SAP system issues an error message, after which you can make corrections.

Function modules that use the MAPNAME parameter create one session only.

To process a batch input session, choose Start of the navigation path System Next navigation step Services Batch input Edit End of the navigation path .

For more information on batch input sessions, see SAP library under Start of the navigation path Basis Next navigation step Kernel Components (BC-KRN) BC System Services Managing Batch Input Sessions Batch Input Sessions End of the navigation path .