Create Document Info Records via Batch Input

Description

You can use this report to transfer document info records from an external system to your SAP System. The program can create up to eleven language-dependent descriptions, object links, and classification data for each document. Transfer of long texts is also supported.

The program reads the sequential file you enter and processes the data in this file.

The sequential file can be on your SAP application server, the presentation server, or an external application server. If the file is on an external application server, you need to enter the server name. You can display the possible entries and select an application server.

If you set the "create session" report parameter to "X", the program creates one or more batch input sessions, which you can process manually later. If the "create session" report parameter has its initial value, all document info records are created online. In this case, only the document info records where errors occurred when they were created are collected in batch input sessins. You can process these sessions later.

Requirement

Before you can start this report, you must extract the document data you want to transfer from the source system and write it to a sequential file. To do this, you need to write a program in the source system which collects the data in the format required and generates the file.

You must define a logical name for the sequential file in the customizing functions. This logical name is the reference to the physical name. You can maintain the logical name when you start the report, by calling online help (F1) on the Logical file name field.

The sequential file containing the BOM data should have the following format:

One session header per session (structure BGR00, record type 0)

The session header contains general administrative data on the batch input session to be created. All other records in the sequential file are allocated to the current session, until the next session header occurs.

One header record for each document info record (structure DRAW_BI, record type 1)

The document header record contains data describing the document info record.

For each document header record, you can have up to eleven records of record type 2 which contain language-dependent descriptions (structure DRAT_BI).

For each document description, you can have any number of records of record type 3 which contain lines of long text (structure LTEXT_BI).

For each document header record, you can have any number of records of record type 4 which contain object links to the document info record (structure DRAD_BI). In the second field, DRAD_BI-DOKOB, enter the object table of the linked object (for example, "MARA" for material, "EQUI" for equipment, and so on). Then fill out the key fields of the object in structure DRAD_BI in external format.

For each document header record, you can have any number of records of record type 5 which contain allocations to classes (structure KSSK_BI). These classes can have different class types. Please note that the indicator for the standard class (Feld KSSK_BI-STDCL) can only be set to "X" for one class per class type.

If you want characteristic values assigned for an allocation to a class,you can enter assigned value records of record type 6 (structure AUSP_BI) for each allocation record. These records contain the values of the individual characteristics of a class. If more than one value is assigned to a characteristic, you need a record for each value.

You can send record of types 2, 4, and 5 in any order. You can also omit one or all of these record types. Records of type 3 must always be preceded by a record of type Typ 2. Records of type 6 must alwaays be preceded by a record of type 5. All type 3 records are allocated to the previous type 2 record. This means that it is important which type 3 records you put between which type 2 record. The same goes for records of types 5 and 6.

Note

When you create your sequential file, please note the following points:

Fields which are not to have an entry must be transferred with their initial values. If a NODATA character is defined in the BGR00-NODATA field, do not use it.

If you want to delete default field values for the transaction, enter the delete character "!" in the fields concerned.

Fields containing a date must be transferred in external format as per the settings in your user master record. The only exception is the date in the session header, if there is one. This must always be transferred in internal format YYYYMMDD, such that YYYY is the year, MM is the month and DD is the day.

If fields for quantities or prices contain decimals, use the decimal point defined in your user master record.

Procedure

1. Extract the data to be transferred from the source system using the program written for this purpose, and write your data to a sequential file.

2. Start the transfer program in the SAP System.

Enter the logical file name for the physical path name under which the sequential file is stored.
To help you find the path name, you can display possible entries.

Decide which server the sequential file is to be read from. You can choose between your own application server, an external application server, and the presentation server.
If the sequential file is to be read from an external application server, enter the server name. You can display possible entries to help you.

Decide whether all BOMs to be transferred are to be collected in sessions or only those that contain errors.

3. The result log for data transfer shows you which sessions, if any, were created.

4. Process the sessions to transfer the document info records to the system or to process the document info records with errors again.

Output

At the end of the data transfer program, a log is output. This contains a list of all the errors which occurred during processing and a list of the document info records which were transferred successfully. The log also shows you which sessions have been created to be processed again later, if any.

Example

You can use report RCVBI005 to create a test file.