Description
You can use this report to transfer document info records from anexternal system to your SAP System. The program can create up to elevenlanguage-dependent descriptions, object links, and classification datafor each document. Transfer of long texts is also supported.
The program reads the sequential file you enter and processes the datain this file.
The sequential file can be on your SAP application server, thepresentation server, or an external application server. If the file ison 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 programcreates one or more batch input sessions, which you can processmanually later. If the "create session" report parameter has itsinitial value, all document info records are created online. In thiscase, only the document info records where errors occurred when theywere created are collected in batch input sessins. You can processthese sessions later.

Precondition
Before you can start this report, you must extract the document datayou want to transfer from the source system and write it to asequential file. To do this, you need to write a program in the sourcesystem which collects the data in the format required and generates thefile.
You must define a logical name for the sequential file in thecustomizing functions. This logical name is the reference to thephysical name. You can maintain the logical name when you start thereport, by calling online help (F1) on the Logicalfile name field.
The sequential file containing the BOM data should have the followingformat:

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

The session header contains general administrative data on the batchinput session to be created. All other records in the sequential fileare allocated to the current session, until the next session headeroccurs.

• One header record for each document info record (structure DRAW_BI,
record type 1)
The document header record contains data describing the document inforecord.

• For each document header record, you can have up to eleven records of
record type 2 which contain language-dependent descriptions (structureDRAT_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 theobject table of the linked object (for example, "MARA" for material,"EQUI" for equipment, and so on). Then fill out the key fields of theobject 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 theindicator for the standard class (Feld KSSK_BI-STDCL) can only be setto "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 (structureAUSP_BI) for each allocation record. These records contain the valuesof the individual characteristics of a class. If more than one value isassigned 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 alsoomit one or all of these record types. Records of type 3 must always bepreceded by a record of type Typ 2. Records of type 6 must alwaays bepreceded by a record of type 5. All type 3 records are allocated to theprevious type 2 record. This means that it is important which type 3records you put between which type 2 record. The same goes for recordsof 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 theBGR00-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 datein the session header, if there is one. This must always be transferredin internal format YYYYMMDD, such that YYYY is the year, MM is themonth and DD is the day.

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

Procedure
RESET N1
Extract the data to be transferred from the source system using theprogram written for this purpose, and write your data to a sequentialfile.
Start the transfer program in the SAP System.
Enter the logical file name for the physical path name under which thesequential 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 canchoose between your own application server, an external applicationserver, and the presentation server.
If the sequential file is to be read from an external applicationserver, enter the server name. You can display possible entries to helpyou.
Decide whether all BOMs to be transferred are to be collected insessions or only those that contain errors.
The result log for data transfer shows you which sessions, if any, werecreated.
Process the sessions to transfer the document info records to thesystem or to process the document info records with errors again.

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

Example
You can use report RCVBI005 to create a test file.