J_1BCTE_DOC SAP (CT-e Document Header) Structure details
Description: CT-e Document Header
Structure field list including key, data, relationships and ABAP select examples
J_1BCTE_DOC 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 "CT-e Document Header" 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_DOC TYPE J_1BCTE_DOC.
The J_1BCTE_DOC table consists of various fields, each holding specific information or linking keys about CT-e Document Header data available in SAP. These include BUDAT (Posting Date in the Document), BLDAT (Document Date in Document), NFNET (Net Value including taxes), NFTOT (Total value including all taxes).. 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 or numeric)
SAP J_1BCTE_DOC 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 |
| XMLVERS | XML Version | J_1BNFEXMLVERSION | DEC | 4(2) | J_1BNFEXMLVERSION | ||||
| BUDAT | Posting Date in the Document | BUDAT | DATS | 8 | DATUM | ||||
| BLDAT | Document Date in Document | BLDAT | DATS | 8 | DATUM | ||||
| NFNET | Net Value including taxes | J_1BNFNET | CURR | 15(2) | WERTV8 | ||||
| NFTOT | Total value including all taxes | J_1BNFTOT | CURR | 15(2) | WERTV8 | ||||
| ACCESS_KEY | 0 | ||||||||
| REGIO | Region of Document Issuer | J_1BREGIO | CHAR | 2 | J_1BREGIO | ||||
| NFYEAR | Year of Document Date | J_1BYEAR | CHAR | 2 | J_1BYEAR | ||||
| NFMONTH | Month of Document Date | J_1BMONTH | CHAR | 2 | J_1BMONTH | ||||
| STCD1 | CNPJ Number of Document Issuer | J_1BSTCD1 | CHAR | 14 | J_1BSTCD1 | ||||
| MODEL | Model of Nota Fiscal | J_1BMODEL | NUMC | 2 | J_1BMODEL | ||||
| SERIE | Series | J_1BSERIES | CHAR | 3 | J_1BSERIES | ||||
| NFNUM9 | Nine-Digit Document Number | J_1BNFNUM9 | CHAR | 9 | J_1BNFNUM9 | ||||
| DOCNUM9 | Random Number in Access Key | J_1BDOCNUM9 | CHAR | 9 | J_1BDOCNUM9 | ||||
| CDV | Check Digit in Access Key | J_1BCHECKDIGIT | CHAR | 1 | J_1BCHECKDIGIT | ||||
| AUTHCODE | Protocol Number | J_1BNFEAUTHCODE | CHAR | 15 | J_1BNFEAUTHCODE | ||||
| AUTHDATE | Processing Timestamp - Date | J_1BAUTHDATE | DATS | 8 | DATUM | ||||
| AUTHTIME | Processing Timestamp - Time | J_1BAUTHTIME | TIMS | 6 | UZEIT | ||||
| SERV_TP | Service Type Indicator | J_1BCTE_SERV_TP | CHAR | 1 | J_1BCTE_SERV_TP | ||||
| REGIO_FR | STATE (State, Province, County) | REGIO | CHAR | 3 | Assigned to domain | REGIO | |||
| TXJCD_FR | Tax Jurisdiction | TXJCD | CHAR | 15 | Assigned to domain | TXJCD | TXJ | ||
| REGIO_TO | STATE (State, Province, County) | REGIO | CHAR | 3 | Assigned to domain | REGIO | |||
| TXJCD_TO | Tax Jurisdiction | TXJCD | CHAR | 15 | Assigned to domain | TXJCD | TXJ | ||
| MAIN_PRODUCT | Main Product Transported | J_1BCTE_MAIN_PROD | CHAR | 60 | CHAR60 | ||||
| TOTAL_REF_AMNT | Total Amount of Goods | J_1BCTE_REF_TOT_VAL | CURR | 15(2) | WERT8 | ||||
| MODETRANSPORT | Mode of Transportation | J_1BMODETRANSPORT | CHAR | 2 | J_1BMODETRANSPORT | ||||
| CTE_SERV_TAKER | CT-e Partner as Service Taker | J_1BCTE_SERVICE_TAKER | CHAR | 1 | J_1BCTE_SERVICE_TAKER | ||||
| CTE_TYPE | CT-e Type | J_1BCTTYPE | CHAR | 1 | J_1BCTTYPE | ||||
| RECEIVER_COLLECT | Receiver Collection Indicator | J_1BCTE_RCVR_WDW | CHAR | 1 | XFELD |
| Key field | Non-key field |
How do I retrieve data from SAP structure J_1BCTE_DOC using ABAP code?
As J_1BCTE_DOC 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_DOC as there is no data to select.How to access SAP table J_1BCTE_DOC
Within an ECC or HANA version of SAP you can also view further information about J_1BCTE_DOC 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