J_1BNFE_INBOUND SAP (Inbound interface for NFE) Structure details
Description: Inbound interface for NFE
Related tables to J_1BNFE_INBOUND
Access table J_1BNFE_INBOUND
Structure field list including key, data, relationships and ABAP select examples
J_1BNFE_INBOUND 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 "Inbound interface for NFE" 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_1BNFE_INBOUND TYPE J_1BNFE_INBOUND.
The J_1BNFE_INBOUND table consists of various fields, each holding specific information or linking keys about Inbound interface for NFE data available in SAP. These include I_AUTHCODE (Protocol Number), I_CODE (Official Status Code), I_REGIO (Region of Document Issuer), I_NFYEAR (Year of Document Date).. 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_1BNFE_INBOUND 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 |
| I_DOCNUM | Document Number | J_1BDOCNUM | NUMC | 10 | Assigned to domain | J_1BDOCNUM | JEF | ||
| I_AUTHCODE | Protocol Number | J_1BNFEAUTHCODE | CHAR | 15 | J_1BNFEAUTHCODE | ||||
| I_CODE | Official Status Code | J_1BSTATUSCODE | CHAR | 3 | Assigned to domain | ALPHA | J_1BSTATUSCODE | ||
| I_REGIO | Region of Document Issuer | J_1BREGIO | CHAR | 2 | J_1BREGIO | ||||
| I_NFYEAR | Year of Document Date | J_1BYEAR | CHAR | 2 | J_1BYEAR | ||||
| I_NFMONTH | Month of Document Date | J_1BMONTH | CHAR | 2 | J_1BMONTH | ||||
| I_STCD1 | CNPJ Number of Document Issuer | J_1BSTCD1 | CHAR | 14 | J_1BSTCD1 | ||||
| I_MODEL | Model of Nota Fiscal | J_1BMODEL | NUMC | 2 | J_1BMODEL | ||||
| I_SERIE | Series | J_1BSERIES | CHAR | 3 | J_1BSERIES | ||||
| I_NFNUM9 | Nine-Digit Document Number | J_1BNFNUM9 | CHAR | 9 | J_1BNFNUM9 | ||||
| I_DOCNUM9 | Random Number in Access Key | J_1BDOCNUM9 | CHAR | 9 | J_1BDOCNUM9 | ||||
| I_CDV | Check Digit in Access Key | J_1BCHECKDIGIT | CHAR | 1 | J_1BCHECKDIGIT | ||||
| E_ERROR | Checkbox | XFELD | CHAR | 1 | XFELD | ||||
| I_MSGTYP | NF-e/CT-e: Type of Inbound Message | J_1BNFE_MESSAGE_TYPE | CHAR | 1 | J_1BNFE_MESSAGE_TYPE | ||||
| I_AUTHDATE | Processing Timestamp - Date | J_1BAUTHDATE | DATS | 8 | DATUM | ||||
| I_AUTHTIME | Processing Timestamp - Time | J_1BAUTHTIME | TIMS | 6 | UZEIT |
| Key field | Non-key field |
How do I retrieve data from SAP structure J_1BNFE_INBOUND using ABAP code?
As J_1BNFE_INBOUND 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_1BNFE_INBOUND as there is no data to select.How to access SAP table J_1BNFE_INBOUND
Within an ECC or HANA version of SAP you can also view further information about J_1BNFE_INBOUND 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