Structuring Rules for Document Transfer Files

Structuring Rules for Document Transfer Files

Field Contents and Formats

Fields where no entry is to be made should be copied with their initial value. Do not use any NODATA character defined in the BGR00-NODATA field.

If you want to remove a default field entry for the transaction, enter the delete character "!" in the field concerned.

Fields that contain a date should be copied in the external format defined in the user master record. An exception to this rule is the date entered in the session header, if there is any date here. This should always be copied 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 decimal values, always use the decimal point defined in the user master record.

Detailed Information for Each Structure

Structure BGR00:

Record type 0: one session record per session The session header contains general administrative data on the batch input session to be created. All records that follow the header in the sequential file are assigned to the current session, until the next header occurs in the file.

Structure DRAW_BI:

Record type 1: one header record for each document info record The document info record contains descriptive data.

Structure DRAT_BI:

You can enter up to eleven records of record type 2 containing language-dependent short texts (descriptions) for each document header record.

Structure LTEXT_BI:

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

Structure DRAD_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. In the second field, DRAD_BI-DOKOB, enter the object table (for example, MARA for materials, EQUI for equipment) for the linked object. Then fill out the key fields of the object in structure DRAD_BI in external format.

Structure KSSK_BI:

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

Structure AUSP_BI:

If you want characteristic values assigned for an allocation to a class, you can enter assigned value records of record type 6 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 records of type 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 2. Records of type 6 must always 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 record you put between which type 2 record. The same goes for records of types 5 and 6.