BICSK SAP (Batch Input Structure for BOM Header Data) Structure details
Description: Batch Input Structure for BOM Header Data
Structure field list including key, data, relationships and ABAP select examples
BICSK is a standard SAP Structure so does not store data like a database table does. It can be used to define the fields of other actual tables or to process "Batch Input Structure for BOM Header Data" Information within sap ABAP programs.
This is done by declaring abap internal tables, work areas or database tables based on this Structure. These can then be used to store and process the required data appropriately.
i.e. DATA: wa_BICSK TYPE BICSK.
The BICSK table consists of various fields, each holding specific information or linking keys about Batch Input Structure for BOM Header Data data available in SAP. These include TCODE (Transaction Code), AENNR (Change Number), BMEIN (Base unit of measure for BOM), BMENG (Base quantity (BTCI)).. See below for full list along with technical details, documentation, text table, check tables, foreign key relationships, conversion routines, relevant tcodes and example ABAP select code etc. .
Delivery Class:Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Can be enhanced (character-type)
SAP BICSK structure fields - Full list of fields found in SAP data dictionary
Field | Description | Data Element | Data Type | length (Dec) | Check table | Conversion Routine | Domain Name | MemoryID | SHLP |
STYPE | Batch Input Interface Record Type | STYPE_BI | CHAR | 1 | CHAR1 | ||||
TCODE | Transaction Code | TCODE | CHAR | 20 | Assigned to domain | TCODE | TCD | ||
AENNR | Change Number | AENNR | CHAR | 12 | Assigned to domain | AENNR | AENNR | AEN | |
BMEIN | Base unit of measure for BOM | BASME | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
BMENG | Base quantity (BTCI) | BASMN_BI | CHAR | 17 | CHAR17 | ||||
CADKZ | CAD Indicator | CADKZ | CHAR | 1 | XFELD | ||||
DATUB | Valid to date (BTCI) | DATUB_BI | CHAR | 10 | CHAR10 | ||||
DATUV | Valid-From Date (BTCI) | DATUV_BI | CHAR | 10 | CHAR10 | ||||
EMENG | Required quantity (BTCI) | EMENG_BI | CHAR | 17 | CHAR17 | ||||
EQUNR | Equipment Number | EQUNR | CHAR | 18 | Assigned to domain | ALPHA | EQUNR | EQN | EQUI |
EXSTL | BOM group | EXSTL | CHAR | 18 | EXSTL | CSG | |||
LABOR | Laboratory/design office | LABOR | CHAR | 3 | Assigned to domain | LABOR | |||
LOEKZ | Deletion flag for BOMs | LOKNZ | CHAR | 1 | XFELD | ||||
LOSBS | To lot size (BTCI) | LOSBS_BI | CHAR | 17 | CHAR17 | ||||
LOSVN | From lot size (BTCI) | LOSVN_BI | CHAR | 17 | CHAR17 | ||||
MATNR | Material (BTCI) with Conversion MATN2 | MATNR_BI | CHAR | 40 | MATN2 | MATNR_EXT_CONV | |||
SELAL | Alternative BOM | STALT | CHAR | 2 | ALPHA | ALTNR | |||
SERGE | Manufacturer serial number | SERGE | CHAR | 30 | CHAR30 | ||||
STKTX | Alternative BOM Text | STKTX | CHAR | 40 | TEXT40 | ||||
STLAL | Alternative BOM | STALT | CHAR | 2 | ALPHA | ALTNR | |||
STLAN | BOM Usage | STLAN | CHAR | 1 | Assigned to domain | STLAN | CSV | ||
STLBE | Authorization group for bills of material | STLBE | CHAR | 4 | BEGRU | ||||
STLST | BOM status (BTCI) | STLST_BI | CHAR | 2 | CHAR2 | ||||
VMTNR | Material (Variant) (BTCI) with Conversion MATN2 | VMTNR_BI | CHAR | 40 | MATN2 | MATNR_EXT_CONV | |||
WERKS | Plant | WERKS_D | CHAR | 4 | Assigned to domain | WERKS | WRK | H_T001W_C | |
ZTEXT | BOM text | CSTEXT | CHAR | 40 | TEXT40 | ||||
REVLV | Revision Level | REVLV | CHAR | 2 | NUMCV | REVLV | RVS | ||
TPLNR | Functional Location | TPLNR | CHAR | 30 | Assigned to domain | TPLNR | TPLNR | IFL | IFLM |
DOKAR | Document Type | DOKAR | CHAR | 3 | Assigned to domain | DOKAR | CV2 | ||
DOKNR | Document number | DOKNR | CHAR | 25 | Assigned to domain | ALPHA | DOKNR | CV1 | |
DOKTL | Document Part | DOKTL_D | CHAR | 3 | DOKTL | CV4 | |||
DOKVR | Document Version | DOKVR | CHAR | 2 | DOKVR | CV3 | |||
VBELN | Sales Order | CS_VBELN | CHAR | 10 | Assigned to domain | ALPHA | VBELN | AUN | |
VBPOS | Sales order item | CS_VBPOS | NUMC | 6 | Assigned to domain | POSNR | APO | ||
STOBJ | Standard object | STOBJ | CHAR | 18 | CHAR18 | ||||
VDKNR | Document (variant) | VDKNR | CHAR | 25 | Assigned to domain | ALPHA | DOKNR | CV1 | |
VDKAR | Document type (variant) | VDKAR | CHAR | 3 | Assigned to domain | DOKAR | CV2 | ||
VDKTL | Document part (variant) | VDKTL | CHAR | 3 | DOKTL | CV4 | |||
VDKVR | Document version (variant) | VDKVR | CHAR | 2 | DOKVR | CV3 | |||
VEQNR | Equipment (variant) | VEQNR | CHAR | 18 | Assigned to domain | ALPHA | EQUNR | ||
VTPNR | Functional location (variant) | VTPNR | CHAR | 30 | Assigned to domain | TPLNR | TPLNR | IFL | IFLM |
PSPNR | WBS element BI BOMs | CS_PSPNR_BI | CHAR | 24 | CHAR24 | ||||
OITXT | Object management record description | CC_OITXT | CHAR | 40 | CC_TEXT40 |
Key field | Non-key field |
How do I retrieve data from SAP structure BICSK using ABAP code?
As BICSK is a database structure and not a table it does not store any data in the SAP data dictionary. The ABAP SELECT statement is therefore not appropriate and can not be performed on BICSK as there is no data to select.How to access SAP table BICSK
Within an ECC or HANA version of SAP you can also view further information about BICSK and the data within it using relevant transactions such asSE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).
Search for further information about these or an SAP related objects