Description
With this program, you can transfer BOMs with all their longtexts from a non-SAP system to the SAP System. The BOMs that you cancreate include document structures, equipment BOMs, material BOMs,standard BOMs, and functional location BOMs.
The program reads the specified sequential file and processes the datacontained in the file.

• The sequential file can be stored on an in-house application server, the
presentation server, or an external application server. In the lattercase, you must enter the name of the server. To select an applicationserver, you can use the possible entries function.

• If you want the data to be written to one or more batch input sessions,
which you can process at a later date, select 'Create session'.
If you do not select this parameter, all BOMs are created online. Onlythe BOMs that were created incorrectly are written to batch inputsessions.

Precondition
Before you can start the report, you must extract the required BOM datafrom the source system and write it to a sequential file. Todo this, you must run a program in the source system that compiles thedata in the required format and creates the file.
For the file created, you must define a logical file name in the IMGas a link to the physical file name. To define the logicalfile name, start the report, then choose the possible entriesfunction for the field Logical file name.
The system expects the BOM data to be transferred to have the followingformat in the sequential file:


• Record type 0: One session record (structure BGR00) per session

The session record contains general management data on the batch inputsession to be created. All further records of the sequential file up tothe next session record are allocated to the current session.

• Record type 1: One header record (structure BICSK)
per BOM to be created
The BOM header record contains the transaction code (for example, CS01'Create material BOM') and the header data.
In the BICSK-TCODE field of structure BICSK, you define the BOMcategory, which determines the transaction to be called. The followingentries are possible:
- CV11 for document structures
- IB01 for equipment BOMs
- CS01 for material BOMs
- CS51 for standard BOMs
- IB11 for function location BOMs

• Record type 2: One or more header long text records (structure
LTEXT_BI) per header record
Records of record type 2 are optional records.

• Record type 3: One or more alternative long text records
(structure LTEXT_BI) per header record
Records of record type 3 are optional records.

• Record type 4: One item record (structure BICSP) per item

All BOM item records up to the next header record or session record areallocated to the BOM header that was last read.

• Record type 5: One or more item long text records (structure
LTEXT_BI) per item record
Records of record type 5 are optional records.

• Record type 6: One sub-item record (structure BICSU) per sub-item

All BOM sub-item records up to the next item record, header record, orsession record are allocated to the BOM item that was last read.

Hote
Please note the following when you create a sequential file:


• Fields that are not to be filled must be transferred with their initial
value. The NODATA character defined in the BGR00-NODATA fieldcannot be used.

• If you want default values of the transactions to be reset, you
must transfer the reset character '!' to the fields concerned. Forexample, if you want to set the bulk material indicator, you must resetthe 'Relevant to costing' indicator if this indicator is set by defaultfor the transaction.

• Fields that contain a date must be transferred in external format as
defined in your user master. This does not apply to dates in sessionrecords. These dates must always be transferred in the internal formatYYYYMMDD. (YYYY stands for the year, MM for the month, an DD for theday.)

• If you enter decimal values in fields that contain quantities or
prices, you must use the decimal character defined in the your master.

How to proceed
RESET N1
Extract the data to be transferred from the source system using theprogram required and write the data to the sequential file.
Start the transfer program in the SAP System.
Enter the logical file name that belongs to the name of the physicalpath where the sequential file is stored.
To determine the path name, you can use the possible entries function.
Define the server from which the sequential file is to beimported. Possible servers are your in-house applicationserver, an external application server, and the presentation server.
If you want to import the sequential file from an external applicationserver, you must enter the name of the server. You can use the possibleentries function to do this.
Decide whether all the BOMs you want to transfer are to be collected inbatch input sessions, or whether only the incorrect ones are to becollected.
In the transfer log, check for any sessions created.
Process the sessions, either to transfer the BOMs to the SAP Systemor to correct the incorrect BOMs.

Output
The data transfer program writes a transfer log with the followinginformation:


• the errors that occurred during the transfer


• the BOMs that were transferred successfully


• the batch input sessions that were created