J_1BCTE_S_BADI_HEADER SAP (BAdI CT-e header data) Structure details
Description: BAdI CT-e header data
Related tables to J_1BCTE_S_BADI_HEADER
Access table J_1BCTE_S_BADI_HEADER
Structure field list including key, data, relationships and ABAP select examples
J_1BCTE_S_BADI_HEADER 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 "BAdI CT-e 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_J_1BCTE_S_BADI_HEADER TYPE J_1BCTE_S_BADI_HEADER.
The J_1BCTE_S_BADI_HEADER table consists of various fields, each holding specific information or linking keys about BAdI CT-e header data data available in SAP. These include CTE_STRT_LCT (Jurisdiction Code of the Point of Origin), CTE_END_LCT (Jurisdiction Code of the Final Destination), MAIN_PRODUCT (Main Product Transported), RCVR_WDW (Receiver Collection Indicator).. 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: Cannot Be Enhanced
SAP J_1BCTE_S_BADI_HEADER 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 |
SERV_TP | Service Type Indicator | J_1BCTE_SERV_TP | CHAR | 1 | J_1BCTE_SERV_TP | ||||
CTE_STRT_LCT | Jurisdiction Code of the Point of Origin | J_1BCTE_SJCD | CHAR | 15 | J_1BTXJUR | J_1BTXJCD | |||
CTE_END_LCT | Jurisdiction Code of the Final Destination | J_1BCTE_EJCD | CHAR | 15 | J_1BTXJUR | J_1BTXJCD | |||
MAIN_PRODUCT | Main Product Transported | J_1BCTE_MAIN_PROD | CHAR | 60 | CHAR60 | ||||
RCVR_WDW | Receiver Collection Indicator | J_1BCTE_RCVR_WDW | CHAR | 1 | XFELD | ||||
PLN_DT_DLV | Estimated Delivery Date | J_1BCTE_PLN_DT_DLV | DATS | 8 | DATUM | ||||
FTL_IND | Full Truck Load Indicator | J_1BCTE_FTL_IND | CHAR | 1 | XFELD | ||||
VOL_TRANSP | Transported Volume | J_1BCTE_VOL_TRANSP | DEC | 13(3) | |||||
VOL_UNIT | Volume Measure Unit | J_1BCTE_VOL_UNIT | UNIT | 3 | T006 | CUNIT | MEINS | ||
TOTAL_REF_AMT | Total Amount of Goods | J_1BCTE_REF_TOT_VAL | CURR | 15(2) | WERT8 | ||||
TRANSP_MODE | Mode of Transportation | J_1BCTE_TRANSPTN_MODE | CHAR | 1 | J_1BCTE_TRANSPTN_MODE |
Key field | Non-key field |
How do I retrieve data from SAP structure J_1BCTE_S_BADI_HEADER using ABAP code?
As J_1BCTE_S_BADI_HEADER 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 J_1BCTE_S_BADI_HEADER as there is no data to select.How to access SAP table J_1BCTE_S_BADI_HEADER
Within an ECC or HANA version of SAP you can also view further information about J_1BCTE_S_BADI_HEADER 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