Description
This report is used to copy changes to BOMs from an external system tothe SAP System. Changes to document structures, equipment BOMs,material BOMs, standard BOMs, and functional location BOMs aresupported.
The program reads the sequential file you enter and processes the datacontained in it.

• The sequential file can be on your own application server, the
presentation server, or an external application server. If the file ison an external application server, enter the server name. You candisplay possible entries to help you select one of the availableapplication servers.

• If you want the system to write the data to one or more batch input
sessions, which you can process manually later, select the reportparameter "Create session".
If you leave the "Create session" parameter with its initial value, allBOMs are changed online. In this case, only the BOMs that were changedincorrectly are collected in batch input sessions. You can processthese sessions later.

Note
The input data must contain all items that are to be in thetarget system on the key date.
The report compares the items in the input file with the items in thetaget system BOM on the key date, which you include in the BOM headerof the input file. All items that are not included in the input fileare deleted.
IF you want to transfer several historical change statuses forone BOM you must process each change status individually:
For each historical change status create an individualBatch-Input-Folder and load it into the SAP System. Only after a folderhas been posted in the SAP System can you create the next folder forthe next change status.

Precondition
Before you can start this report, you must extract the BOM data to becopied from the source system and write the data to a sequential file.To do this, you must implement a program in the source system thatcollates the data in the required format and creates the file.
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:


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

The session header contains general administrative data on the batchinput session. All records are assigned to the current session headeruntil the next session header in the sequential file.

• Record type 1: one session record (structure BICSK) for each BOM
to be changed
The BOM header record contains the transaction code (such as CS02Change Material BOM) and the header data.
In field BICSK-TCODE in structure BICSK, you define the BOM categoryand therefore the SAP transaction to be called. You can enter thefollowing values in this field:
CV12 for document structures
IB02 for equipment BOMs
CS02 for material BOMs
CS52 for standard BOMs
IB12 for functional location BOMs

• Record type 2: one item record (structure BICSP) per item

All BOM item records are assigned to the current BOM header recorduntil the next BOM header record or session header in the sequentialfile.

• Record type 3: one sub-item record (structure BICSU) per
sub-item
All BOM sub-item records are assigned to the current BOM item recorduntil the next BOM item record, BOM header record or session header inthe sequential file.

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


• Fields that are not filled out are transferred with their initial
values. Do not use any NODATA character defined in the BGR00-NODATA
field.

• If you do not want default values for the transaction to be entered in
these fields, enter the delete character "!" for transfer. For example,if you want to set the indicator for bulk materials, you need to deletethe indicator for relevancy to costing, if this is a default value forthe transaction.

• If field values are to be deleted, you need to copy the delete symbol
"!" to the corresponding field.

• Fields that contain a date are to be transferred in external format
according to the settings in the user master record. The exception isany date entered in the session header. This is always transferred ininternal format YYYYMMDD. YYYY is the year, MM is the month and DD isthe day.

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

Procedure
RESET N1
Extract the data to be copied from the source system using the programwritten for this purpose, writing the data to a sequential file.
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 transfer log tells you which sessions, if any, have been created.
Process the sessions in order to transfer the changes to BOMs to theSAP System and to modify any BOMs containing errors.

Output
Once the data program has run, you see a log with the followinginformation:


• all the errors that occured during processing


• all the BOMs that were copied successfully


• all the sessions, if any, that have been created