Description
With this report, you can transfer variant BOMs without a longtext from a non-SAP system to the SAP System. One variant of the BOMmust already exist in the SAP System. You cannot use this report totransfer simple BOMs. For this purpose, use report RCSBI010.
This program reads the sequential file you specified and processes thedata contained in the file.

• The sequential file can be stored on an in-house application server,
the presentation server, or an external application server. In thelatter case, you must enter the name of the server. To select anapplication server, 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 them 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 IMG asa link to the physical file name. To define the logical file name,start the report, then choose the possible entries function for thefield 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 per session (structure BGR00)

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 variant BOM to be created
The BOM header record contains the transaction code (for example, CS01'Create material BOM') and the header data.
Structure BICSK contains the following material number fields:
BICSK-MATNR: material number of the variant BOM to be transferred
BICSK-VMTNR: material number of the BOM in the SAP System to which youwant to add the new BOM as a variant
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
The data for the document structure that exists in the SAP System mustbe contained in the fiels BICSK-VDKNR, BICSK-VDKAR, BICSK-VDKTL, andBICSK-VDKVR.
IB01 for equipment BOMs
The equipment number for the equipment BOM that exists in the SAPSystem must be contained in the field BICSK-VEQNR.
CS01 for material BOMs
The material number for the material BOM that exists in the SAP Systemmust be contained in the field BICSK-VMTNR.
IB11 for functional location BOMs
The number of the functional location for the functional location BOMthat exists in the SAP System must be contained in the fieldBICSK-VTPNR.

• Record type 2: 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 3: 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.

Notes
All the items of the variant BOMs concerned must be transferred to theSAP System. The transfer program reads the BOM variant that exists inthe SAP System and compares both variants to determine the non-variantparts. The BOM comparison is made on the basis of the entire BOMitem.
Please note the following information concerning the creation of thesequential 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. For example,if you want to set the bulk material indicator, you must reset the'Relevant to costing' indicator if this indicator is set by default forthe 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 be imported.Possible servers are your in-house application server, an externalapplication 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 System orto 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