J_1BNFE_INVALID SAP (Electronic Nota Fiscal: Invalid Status Actions) Table details
Dictionary Type: Table
Description: Electronic Nota Fiscal: Invalid Status Actions
Description: Electronic Nota Fiscal: Invalid Status Actions
ABAP Code to SELECT data from J_1BNFE_INVALID
Related tables to J_1BNFE_INVALID
Access table J_1BNFE_INVALID
Related tables to J_1BNFE_INVALID
Access table J_1BNFE_INVALID
Table field list including key, data, relationships and ABAP select examples
J_1BNFE_INVALID is a standard SAP Table which is used to store Electronic Nota Fiscal: Invalid Status Actions data and is available within R/3 SAP systems depending on the version and release level.
The J_1BNFE_INVALID table consists of various fields, each holding specific information or linking keys about Electronic Nota Fiscal: Invalid Status Actions data available in SAP. These include DOCNUM (Document Number), COUNTER (NF-e: Counter for Table J_1BNFE_INVALID), DOCSTA (Document Status), SCSSTA (System Communication Status).. 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: A - Application table (master and transaction data)Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Can be enhanced (character-type or numeric)
SAP J_1BNFE_INVALID table 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 |
| MANDT | Client | MANDT | CLNT | 3 | Assigned to domain | MANDT | |||
| DOCNUM | Document Number | J_1BDOCNUM | NUMC | 10 | Assigned to domain | J_1BDOCNUM | JEF | ||
| COUNTER | NF-e: Counter for Table J_1BNFE_INVALID | J_1B_NFE_COUNTER | NUMC | 5 | NUM05 | ||||
| DOCSTA | Document Status | J_1BNFEDOCSTATUS | CHAR | 1 | J_1BNFEDOCSTATUS | ||||
| SCSSTA | System Communication Status | J_1BNFESCSSTATUS | CHAR | 1 | J_1BNFESCSSTATUS | ||||
| CONTING | Document Posted under Contingency | J_1BCONTINGENCY | CHAR | 1 | XFELD | ||||
| CANCEL | Canceled | J_1BCANCEL | CHAR | 1 | XFELD | ||||
| ACTION_DATE | Date of Change to Document | J_1BNFE_ACTION_DATE | DATS | 8 | DATUM | ||||
| ACTION_TIME | Time of Change to Document | J_1BNFE_ACTION_TIME | TIMS | 6 | UZEIT | ||||
| ACTION_USER | User Who Made Change to Document | J_1BNFE_ACTION_USER | CHAR | 12 | USNAM | ||||
| 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 | ||||
| AUTHCOD | Protocol Number | J_1BNFEAUTHCODE | CHAR | 15 | J_1BNFEAUTHCODE | ||||
| CODE | Official Status Code | J_1BSTATUSCODE | CHAR | 3 | Assigned to domain | ALPHA | J_1BSTATUSCODE | ||
| MESSAGE_TYPE | Message Type of Message in NF-e Log | J_1B_NFE_MESSAGE_TYPE | CHAR | 1 | CHAR1 | ||||
| MESSAGE_ID | ID of Messages in the NF-e Log | J_1B_NFE_MESSAGE_ID | CHAR | 20 | Assigned to domain | ARBGB | |||
| MESSAGE_NO | Message Number of Message in NF-e Log | J_1B_NFE_MESSAGE_NO | CHAR | 3 | Assigned to domain | MSGNR | |||
| CONTING_S | Switched to Contingency | J_1BCONTINGENCY_NFE_SWITCHED | CHAR | 1 | XFELD | ||||
| MSSTAT | Status from Messaging System | J_1BNFE_MS_STATUS | CHAR | 1 | J_1BNFE_MS_STATUS | ||||
| AUTHDATE | Processing Timestamp - Date | J_1BAUTHDATE | DATS | 8 | DATUM | ||||
| AUTHTIME | Processing Timestamp - Time | J_1BAUTHTIME | TIMS | 6 | UZEIT |
| Key field | Non-key field |
How do I retrieve data from SAP table J_1BNFE_INVALID using ABAP code
The following ABAP code Example will allow you to do a basic selection on J_1BNFE_INVALID to SELECT all data from the tableDATA: WA_J_1BNFE_INVALID TYPE J_1BNFE_INVALID.
SELECT SINGLE *
FROM J_1BNFE_INVALID
INTO CORRESPONDING FIELDS OF WA_J_1BNFE_INVALID
WHERE...
How to access SAP table J_1BNFE_INVALID
Within an ECC or HANA version of SAP you can also view further information about J_1BNFE_INVALID 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