Steps to follow for Batch Input program generation

Steps to follow for Batch Input Program Generation

There are two alternatives for program generation:

With an automatic recording of the transaction/s: this should be the preferred alternative ever since transaction recorder is available (SHDB transaction); available from 4.0 version, or from 3.0A by applying a note.
Without an automatic recording of the transaction/s: this is an alternative for the case the transaction recorder (SHDB) is not available.

Alternative #1 (with automatic recording of transactions)

Use the transaction recorder (SHDB transaction) to record the transaction.

	Run the transaction for which you intend to generate the Batch Input program.
	From there click System/Status and write down the transaction code.
	From the command prompt, run: /NSHDB
	Enter recording name (it is advisable to use a name which identifies the transaction).
	Click on create button and enter the transaction code.
	When process finishes a tree with the recorded transaction/s will appear on the screen.
	Click on Save button to save the recording.
	Return to SHDB transaction. Enter the recording name you have just recorded and press <ENTER>.
	If you are on SAP below 4.0 (and a connection from BIG Code Generator to the SAP system is not possible):
	Click on Generate Program.
	Once in the source code, download it to the workstation.
	If you are on SAP 4.0 or later (and a connection from BIG Code Generator to the SAP system is not possible):
	Click on Generate Session.
	Reach transaction SM35 (from the command prompt run: /NSM35).
	Position the mouse-pointer over the session with the same name of the recording.
	From the "Utilities" menu choose the option "Export session".
		Select "File from Presentation server" and assign a path and a name to the "Physical file name" (for example C:\My Documents\TRANS_XK01).
		Execute by pressing execute button.
		Double-click on the name of the session to be exported.

In BIG import the session (or program) using the option "Import transaction" from Utilities tab, or otherwise if you are connected to the SAP system click 'Import transactions from SHDB recording).

Alternative #2 (without automatic analysis of transactions)

Manually analyze screens in SAP.
Manually enter the screens in "Transactions specification" in BIG using the following format:

TRANS	XK01
SAPLKMA1	0300
		BDC_OKCODE	'/00'
		SGTXT
		KNAME

In case of a field that should be repeated (a step-loop), enter a subindex for the field, for example SGTXT(1). Then, you should define a step-loop as indicated in "Step-Loops definition". If the screen contains a step-loop, you should have two OKCODEs, the first of them would indicate the page-down code or new-position-code, and the second one the OKCODE to leave the screen (see "Step-Loops definition" to clearly understand how the screen must be completed).

Common for both alternatives

If the input file is predefined, enter the name of the input-file fields in FILE SPECIFICATION area, and then drag the fields of the file area to PROGRAM SPECIFICATION area (yellow area). If the file is not predefined, check "Auto-fill" and in PROGRAM SPECIFICATION on the yellow area, type the name for each field you wish to fill, (FILE SPECIFICATION will be automatically completed).
Optional (if you cannot establish a connection to the SAP system):
- From "Utilities" tab, click "Generate text file with information about fields" (this will create a file C:\TABLE_FIELDS which will be used to interchange information with the SAP system).
- Run ZGETWIDTH program in SAP (previously you should upload this program from installation directory of this package).
- Then from "Utilities" tab, click "Import fields width".
Choose a program generation method (Call Transaction or session generators programs, and the source of data (client file, server file, database table).
Generate the program by clicking on "Generate program".
Optional. At any moment you may:
- Complete information regarding: functional responsible, technical responsible, interface description, notes and the current percentage completion of the development.
- Save the .BIG format file that you are generating