Symptom:As CPS customer, we do have access to your 3.0 version but unfortunately we are not authorized to use the Data Dictionary Information System.
Since we are currently preparing a BOM transfer for version 3.0, we would like know what the transfer structures for this procedure look like (BICSK, BICSP, BICSU, ...) in version 3.0.
Send us these structures by FAX, if possible.
Cause and prerequisites SolutionBelow, you will find the requested information. ===============================================BOM subitem:
Name Cat. Length Meaning
BICSU-STYPE CHAR C 1 Record type for batch input
BICSU-XLINE NUMC N 4 Line index for internal
BICSU-EBORT CHAR C 20 Installation point subitem
BICSU-UPMNG CHAR C 17 Subitem quantity
BICSU-UPOSZ CHAR C 4 Subitem number
BICSU-UPTXT CHAR C 40 Subitem text
BOM item:
Name Cat. Length Meaning
BICSP-STYPE CHAR C 1 Record type for batch input
BICSP-XLINE NUMC N 4 Line index for internal
BICSP-UPSKZ CHAR C 1 Indicator: Subitem
BICSP-AUSKZ CHAR C 1 Selection indicator (
BICSP-ALPOS CHAR C 1 Indicator: Alternative
BICSP-AUSCH CHAR C 6 Component scrap in
BICSP-AVOAU CHAR C 6 Operation scrap (BTCI)
BICSP-BEIKZ CHAR C 1 Material provided indicator
BICSP-CADPO CHAR C 1 CAD indicator
BICSP-EKGRP CHAR C 3 Purchasing group
BICSP-ERSKZ CHAR C 1 Spare part indicator
BICSP-FMENG CHAR C 1 Fixed quantity
BICSP-IDNRK CHAR C 18 BOM component
BICSP-LIFNR CHAR C 10 Account number of vendor
BICSP-LIFZT CHAR C 3 Delivery time in days
BICSP-MATKL CHAR C 9 Material group
BICSP-MEINS UNIT C 3 Component unit of measure
BICSP-MENGE CHAR C 18 Component quantity (BTCI)
BICSP-NETAU CHAR C 1 Oper. scrap net indicator
BICSP-NFMAT CHAR C 18 Follow-up material
BICSP-NLFZT CHAR C 3 Follow-up time (BTCI)
BICSP-PEINH CHAR C 6 Price unit (BTCI)
BICSP-POSNR CHAR C 4 BOM item number
BICSP-POSTP CHAR C 1 Item category (bill of material
BICSP-PREIS CHAR C 14 Price (BTCI)
BICSP-POTX1 CHAR C 40 BOM item text
BICSP-POTX2 CHAR C 40 BOM item text
BICSP-PSWRK CHAR C 4 Withdrawal plant
BICSP-REKRS CHAR C 1 Indicator: Recursiveness
BICSP-RFORM CHAR C 2 Formula key
BICSP-ROANZ CHAR C 17 No. of var.-size items (BTC
BICSP-ROAME UNIT C 3 Unit of no. of var.-sized items
BICSP-ROKME UNIT C 3 Component unit of measure
BICSP-ROMEI UNIT C 3 Unit of var.-sized item dimens.
BICSP-ROMEN CHAR C 17 Variable-size item qty (BTCI)
BICSP-ROMS1 CHAR C 17 Size 1 (BTCI)
BICSP-ROMS2 CHAR C 17 Size 2 (BTCI)
BICSP-ROMS3 CHAR C 17 Size 3 (BTCI)
BICSP-RVREL CHAR C 1 Relevancy for sales/distribution
BICSP-SAKTO CHAR C 10 Cost element
BICSP-SANFE CHAR C 1 Indicator: In-production rejection
BICSP-SANIN CHAR C 1 Indicator: Plant maintenance
BICSP-SANKA CHAR C 1 Costing indicator
BICSP-SANKO CHAR C 1 Indicator: Construction
BICSP-SANVS CHAR C 1 Indicator: Relevancy for S&D
BICSP-SCHGT CHAR C 1 Indicator: Bulk material
BICSP-SELAL CHAR C 2 Alternative BOM
BICSP-SELID CHAR C 18 BOM component
BICSP-SELPO CHAR C 4 BOM item number
BICSP-SELSB CHAR C 10 Sort string
BICSP-SORTF CHAR C 10 sort string
BICSP-STKKZ CHAR C 1 Indicator: PM assembly
BICSP-STKTX CHAR C 40 Alternavtive BOM part
BICSP-STLAL CHAR C 2 Alternative BOM
BICSP-STLKZ CHAR C 1 Indicator: Assembly of
BICSP-VERTI CHAR C 4 Distribution key for
BICSP-WEBAZ CHAR C 3 Processing time for maint.
BICSP-WAERS CHAR C 5 Currency key (BTCI)
BICSP-DOKAR CHAR C 3 Document type
BICSP-DOKNR CHAR C 25 Document number
BICSP-DOKVR CHAR C 2 Document version
BICSP-DOKTL CHAR C 3 Document part
BICSP-EWAHR CHAR C 3 Usage probability
BICSP-EKORG CHAR C 4 Purchasing organization
BICSP-LGORT CHAR C 4 Issue storage location for
BICSP-CLASS CHAR C 18 Class number
BICSP-KLART CHAR C 3 Class type
BICSP-POTPR CHAR C 1 Resulting item
BICSP-ALPGR CHAR C 2 Alternative item grouping
BICSP-ALPST CHAR C 1 Alternative item strategy
BICSP-ALPRF NUMC N 2 Ranking order
BOM header:
Name Cat. Length Meaning
BICSK-STYPE CHAR C 1 Record type for batch input
BICSK-TCODE CHAR C 4 Transaction code
BICSK-AENNR CHAR C 12 Change number
BICSK-BMEIN UNIT C 3 BOM base unit of measure
BICSK-BMENG CHAR C 17 Base quantity (BTCI)
BICSK-CADKZ CHAR C 1 CAD indicator
BICSK-DATUB CHAR C 10 Date valid to (BTCI)
BICSK-DATUV CHAR C 10 Date valid from (BTCI)
BICSK-EMENG CHAR C 17 Required quantity (BTCI)
BICSK-EQUNR CHAR C 18 Equipment number
BICSK-EXSTL CHAR C 18 BOM group
BICSK-LABOR CHAR C 3 Laboratory/eng./design off.
BICSK-LOEKZ CHAR C 1 Deletion flag for BOM
BICSK-LOSBS CHAR C 17 Lot size to (BTCI)
BICSK-LOSVN CHAR C 17 Lot size from (BTCI)
BICSK-MATNR CHAR C 18 Material number
BICSK-SELAL CHAR C 2 Alternative BOM
BICSK-SERGE CHAR C 30 Manufacturer serial number
BICSK-STKTX CHAR C 40 Alternative BOM text
BICSK-STLAL CHAR C 2 Alternative BOM
BICSK-STLAN CHAR C 1 BOM usage
BICSK-STLBE CHAR C 4 Authorization group for BOM
BICSK-STYPE CHAR C 1 Record type for batch input
BICSK-TCODE CHAR C 4 Transaction code
BICSK-AENNR CHAR C 12 Change number
BICSK-BMEIN UNIT C 3 BOM base unit of measure
BICSK-BMENG CHAR C 17 Base quantity (BTCI)
BICSK-CADKZ CHAR C 1 CAD indicator
BICSK-DATUB CHAR C 10 Date valid to (BTCI)
BICSK-DATUV CHAR C 10 Date valid from (BTCI)
BICSK-EMENG CHAR C 17 Required quantity (BTCI)
BICSK-EQUNR CHAR C 18 Equipment number
BICSK-EXSTL CHAR C 18 BOM group
BICSK-LABOR CHAR C 3 Laboratory/eng./design off.
BICSK-LOEKZ CHAR C 1 Deletion flag for BOM
BICSK-LOSBS CHAR C 17 Lot size to (BTCI)
BICSK-LOSVN CHAR C 17 Lot size from (BTCI)
BICSK-MATNR CHAR C 18 Material number
BICSK-SELAL CHAR C 2 Alternative BOM
BICSK-SERGE CHAR C 30 Manufacturer serial number
BICSK-STKTX CHAR C 40 Alternative BOM text
BICSK-STLAL CHAR C 2 Alternative BOM
BICSK-STLAN CHAR C 1 BOM usage
BICSK-STLBE CHAR C 4 Authorization group BOM
You will find the standard batch input for creating bills of material in Customizing under Production -> Master data -> Bill of material -> Tools -> Data transfer -> Transfer data now.
The Implementation Guide contains a short description.
For more information on the file structure, refer to the conversion program. Since transaction SE38 is currently not available, refer to the program documentation below:
Description:
With this report, you can take over bills of material from an external system into the SAP System. In this case, the system supports the creation of document lists, equipment lists, materials lists, standard object lists and functional location BOMs.
The program reads the specified sequential file and processes the data contained in it.
The sequential file can be located on your own application server, the presentation server or an external application server.
For the latter case you have to specify the corresponding server name. A possible entries pushbutton is available to determine all available application servers. If you set the report parameter 'Create session' to "X" , one or more batch input sessions are created for the data which you can later process manually. If the report parameter 'Create session' is initial, all bills of material are created online. In this case, only the bills of material for which errors occurred during its creation are collected in batch input sessions. They can be reprocessed afterwards.
Preconditions
Before you can start this report, you must have extracted the BOM data to be copied from the source system and written to a sequential file. To do this, you must implement a program in the source system which lists data in the predefined format and creates the file.
It is required that the BOM data to be copied is available in the format specified below in the sequential file:
One session record for each session (structure BGR00, record type 0)
The session record contains general administrative data on the batch input session to be created. All other records of the sequential file up to the next session record are allocated to the current session.
One header record for each bill of material to be created (structure BICSK, record type 1).
In addition to the transaction code (for example, CS01 Create Material BOMs), the BOM header record contains header data.
With field BICSK-TCODE in structure BICSK, you determine the type of the bill of material and thus the SAP transaction to be called. You can enter the following values into this field:
- CV11 for document structures
- IB01 for equipment BOMs
- CS01 for material BOMs
- CS51 for standard BOMs
- IB11 for functional location BOMs
One item record for each item (structure BICSP, record type 2).
All BOM item records up to the next header record or session record are allocated to the BOM header read before.
One subitem record for each subitem (structure BICSU, record type 3)
All BOM subitem records up to the next item record, header record or session record are allocated to the BOM item read before.
Note
When you create a sequential file, you have to consider the following:
Fields that are not to be filled have to be transferred with their initial values.
If default values of the transaction are to be cancelled, a reset character "!" is to be transferred in the corresponding field. If you, for example, want to set the indicator for bulk material, you have to cancel the costing indicator if this indicator is set as a default by the transaction. Fields which contain a date are to be transferred in the external format according to the default values in the user master record. This does not include the date possibly entered in the session record. This date is always to be transferred in the internal format YYYYMMDD. In this case, YYYY stands for a four-digit year, MM for month and TT for day.
If you enter decimal values in fields which contain quantities or prices, the decimal point defined in the user master record is always to be used as decimal point. Procedure Extract the data to be transferred from the source system using the corresponding program and write the data into the sequential file in this case.
Start the conversion program in the SAP System. Enter the absolute path name under which the sequential file is to be found. A possible entries pushbutton with which a local file manager can be started is available to determine the path name. You have to consider that you can only access the file structure that exists on the presentation server via the file manager.
Determine the server from which the sequential file is to be imported. In this case, you can distinguish between your own application server, an external application server and the presentation server. If you want to import the sequential file from an external application server, you have to specify the server name. A possible entries pushbutton is also available here. Furthermore, you have to determine whether all bills of material to be copied or only the incorrect bills of material are to be collected in sessions. Refer to the log file of the data overview for a list of the created sessions.
Process the sessions to copy the bills of material into the system or reprocess the incorrect bills of material. Output
At the end, the data transfer program issues a log which lists all error situations that occurred when processing and the bills of material that were copied successfully. The log displays the possibly created sessions which can be processed afterwards. Example
Additional key words Batch input