Information about Data Transfer and Batch Input

This document describes the batch-input method.

1. Tips

2. Tricks

3. What's new as of Release 4.0

4. What's new as of Release 4.6C

1. Tips
• The relevant transaction specifies the screen sequence for batch input.
• Batch input data is only available for visible screens.
• There is only one processing method for a transaction in batch input.
• A transaction ends successfully with:
- ABAP keyword COMMIT WORK.
- Return to main menu

• Batch input cannot be used with:

- ABAP keyword LEAVE TO TRANSACTION 'XXXX', where 'XXXX' can be any transaction
code.
- Starting a new transaction using OK code /nXXXX
- Deleting current session using OK code /I

• Transferring parameters using SPA/GPA:

- Does not function on a screen during batch input
- ABAP keywords SET PARAMETER and GET PARAMETER in ABAP programs do function

• The following OK code entries are possible in batch input:

- Function code is assigned to a function key (see right mouse button) For example:
F11 ("Save"), then utility field BDC_OKCODE = '/11',
F3 ("Back"), then utility field BDC_OKCODE = '/03'.
- Other function codes:
(See Menu Painter or position the cursor on a function in an application menu, click and
hold the left mouse button, and choose F1)

For example:
'UPDA' 4-character function code for "Save", then utility field BDC_OKCODE = 'UPDA'.
'BACK' 4-character function code for "Back", then utility field BDC_OKCODE = 'BACK',

• Field is a loop field

- The line index is added to the field name

For example: HUGO_IM_LOOP field in line 05, then BDCDATA-FNAM = HUGO_IM_LOOP(05).

• Setting the cursor in a screen in batch input

- Utility field BDC_CUSOR, specify field name
For example: Cursor on field HUGO, then BDC_CURSOR = HUGO.

1
 Information about Data Transfer and Batch Input

• Setting the cursor in a list using batch input

- Utility field BDC_CUSOR, specify line and column

For example: Cursor in line 10 and column 25, then BDC_CURSOR = '10/25'.

• Batch input (BI) menu

- To go to the BI menu, choose "System" -> "Services" -> "Batch input".
- With batch input running, you can:
Delete a running transaction OK code /bdel or BI menu
Call the next transaction /n -"-
Terminate batch input /bend -"-
Set the processing mode
Process in foreground OK code /bda or BI menu
Display errors only /bde -"-
Activate expert mode OK code /bdx or BI menu
Deactivate expert mode /bdy -"-

• Utility reports for batch input:

- RSBDCSUB - Process sessions outside transaction SM35
- RSBDCDRU - Print session contents (transactions and data)
- RSBDCLOG - Process logs
- RSBDCREO - Reorganize processed sessions that are still in the system
Reorganize logs (delete logs and shrink log file to actual size)

• Default screen size (see also SAP Note 11788)

-Batch input can only run everywhere if it is written for the default screen size (22 lines and 85
columns).
Exception: 'Large screens' (60 lines and 85 columns).
You can set the default size using the Customizing menu of SAPTEMU ("Windows" -> "Default size").

• Session has status "Processing", but is not running: The session was set to "Processing" due to a
system crash. You can reactivate this session using transaction SM35 and the RELEASE function
and can then process it without loss of data. (See also SAP Note 12222.)

• Processing batch input sessions

- Report RSBDCSUB
- Transaction SM35 and the PROCESS function
On the dialog box for processing, you can select:
Processing mode Meaning
Process foreground Transactions run visibly in dialog
Display errors only Transactions run invisibly in dialog expect when there is an
error; then visibly
Background Transactions are processed in the background

Additional Functions Meaning

Extended log All messages are logged
Expert mode Suppression of BI message 344 in dialog
Default screen size Automatic configuration of default screen size for dialog
processing

2
 Information about Data Transfer and Batch Input

• Batch input and update (see also SAP Note 33421)

- The update runs synchronously or locally
- Local update means update without "update task"
- Batch input method 'CALL TRANSACTION USING'
. Here you can decide whether to update:
- Synchronously 'UPDATE = S'
- Asynchronously 'UPDATE = A'
- Locally 'Update = L'

• Batch input in the background runs differently than in dialog processing (see SAP Note 33319)

• Batch input logs (see SAP Notes 18307 and 18319).

The logs are not stored in the database but in the SAP file system (in DIR_GLOBAL)

• Differences between R/3 batch input and R/2 batch input

- Table RMAC for screens no longer used.
- Batch input data, 'line/column' replaced with 'field name'.
- The special characters for 'Field does not exist' and the 'Reset characters' are no longer required.
- Creating a session: Differences between R/3 and R/2
R/3, function modules R/2, ABAP keywords
BDC_OPEN_GROUP DYNPRO D00001
BDC_INSERT TRANSFER DYNPRO
BDC_CLOSE_GROUP Program end

- Cursor can be set.

- A process log is generated during processing.
- No reorganization of batch input queue (BTCI).
Successfully processed transactions are deleted
Successfully processed sessions are deleted
- CALL TRANSACTION and CALL DIALOG support batch input.
- Dialog processing in correction mode

• Batch input can supply input-ready fields in lists

- Use the coordinate system as the field name
For example:
Field name HUGO_IN_LIST in line 06, column 14 and value = 'ABCDE'.
Then BDCDATA-FNAM = HUGO_IN_LOOP[06/14] or
BDCDATA-FNAM = [06/14] or
BDCDATA-FNAM = 06/14 and
BDCDATA-FVAL = ABCDE
Use the recording to obtain the field coordinates in lists.

2. Tricks

• Warning messages during batch input

- Warnings must be confirmed in the SAP System by choosing "Enter".
- In batch input, you do this by re-adding the screen to the batch input data. The screen must not
contain any fields in table BDCDATA and must be placed directly after the screen that generates
the warning.

3
 Information about Data Transfer and Batch Input

- The application must remove the warning, if necessary.

• Confirmation dialog boxes (Popup_to_confirm, see SAP Note 13882).

- Standard function modules, modal dialog boxes from the module pool SAPLSPO1.

3. What's new as of Release 4.0

• Batch input dialog processing: If a user chooses F3, F12, or F15 to cancel batch input, batch input
runtime displays a dialog box to confirm the termination (see SAP Note 16629).

• Transactions written with the list processor can run in batch input in the background (see SAP Note
19422).

• In batch input, you can choose how a transaction performs an update:

- Synchronous update (through update task)
- Local update (update through update task in the current work process (improved performance)
- When you create a session, you can pass parameter POST_LOCAL = 'X' to function module
BDC_INSERT so that the transaction updates locally.
This parameter is optional.

• Batch input recording

- You can record any transactions in the SAP System and create sessions or batch input programs
from the recordings.
- To call batch input recording:
On the initial screen of trans. SM35, choose "Recording".
Alternatively, call transaction SHDB.

• Importing or exporting sessions to file

- You can export a session from the system and save it to a file, which you can then edit or correct.
- You can import a session from a file you previously created using Microsoft Excel or other tools in
BDCDATA format.
- To call this function:
On the initial screen of trans. SM35, choose "Utilities" and then one of the following as
needed: "Import session” or "Export session"

• Easier session error analysis: Link from the incorrect transaction to the error message in the log.

4. What's new as of Release 4.6C

• New log overview transaction (SM35P) allowing you to:

- Display log contents
- Delete logs
- Analyze logs and sessions
- Reorganize logs and sessions
- Archive logs using the Archive Development Kit (ADK)
BDCLOGPROD is the archive object for batch input
- Call transaction SM35 ("Session Overview")
- Print log directory from ABAP List Viewer (ALV)
- Print log contents from ALV

4
 Information about Data Transfer and Batch Input

- Set initial view for "Log Selection"

• Utility reports for batch input:

- RSBDC_REORG - Same as old report RSBDCREO but with a new selection screen for
reorganizing processed sessions
Both reports are delivered in this release.

- RSBDCCKA - Checks whether a TemSe object exists for every APQL entry. Table APQL is the
log administration table and table TST01 is the TemSe file administration table. Both tables must
be consistent.

- RSBDCCKT - Checks whether an APQL entry exists for every BDCLG TemSe object.