ROXAX40259 SAP (Generated Table for View V_NFDOC) Structure details
Description: Generated Table for View V_NFDOC
Structure field list including key, data, relationships and ABAP select examples
ROXAX40259 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 "Generated Table for View V_NFDOC" 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_ROXAX40259 TYPE ROXAX40259.
The ROXAX40259 table consists of various fields, each holding specific information or linking keys about Generated Table for View V_NFDOC data available in SAP. These include DOCNUM (Document Number), NFTYPE (Nota Fiscal Type), DOCTYP (Document type), DIRECT (Direction of the movement).. 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 (Deep)
SAP ROXAX40259 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 |
MANDT | Client | MANDT | CLNT | 3 | T000 | MANDT | |||
DOCNUM | Document Number | J_1BDOCNUM | NUMC | 10 | Assigned to domain | J_1BDOCNUM | JEF | ||
NFTYPE | Nota Fiscal Type | J_1BNFTYPE | CHAR | 2 | J_1BAA | J_1BNFTYPE | |||
DOCTYP | Document type | J_1BDOCTYP | CHAR | 1 | Assigned to domain | J_1BDOCTYP | |||
DIRECT | Direction of the movement | J_1BDIRECT | CHAR | 1 | J_1BDIRECT | ||||
DOCDAT | Document date | J_1BDOCDAT | DATS | 8 | DATUM | ||||
PSTDAT | Posting date | J_1BPSTDAT | DATS | 8 | DATUM | ||||
CREDAT | Create date | J_1BCREDAT | DATS | 8 | DATUM | ||||
CRETIM | Creation time | J_1BCRETIM | TIMS | 6 | UZEIT | ||||
CRENAM | Name of the user | J_1BCRENAM | CHAR | 12 | USNAM | ||||
CHADAT | Change date | J_1BCHADAT | DATS | 8 | DATUM | ||||
CHATIM | Change time | J_1BCHATIM | TIMS | 6 | UZEIT | ||||
CHANAM | Name of the user | J_1BCHANAM | CHAR | 12 | USNAM | ||||
FORM | Form of Nota Fiscal | J_1BFORM | CHAR | 4 | J_1BAQ | J_1BFORM | |||
MODEL | Model of Nota Fiscal | J_1BMODEL | NUMC | 2 | J_1BMODEL | ||||
SERIES | Series | J_1BSERIES | CHAR | 3 | J_1BSERIES | ||||
SUBSER | Sub series | J_1BSUBSER | CHAR | 2 | J_1BSUBSER | ||||
NFNUM | Nota Fiscal Number | J_1BNFNUMB | NUMC | 6 | J_1BNFNUMB | ||||
ENTRAD | Nota Fiscal Entrada | J_1BENTRAD | CHAR | 1 | J_1BENTRAD | ||||
FATURA | Fatura | J_1BFATURA | CHAR | 1 | XFELD | ||||
ZTERM | Terms of Payment Key | DZTERM_BIW | CHAR | 4 | ZTERM | ||||
PRINTD | Printed | J_1BPRINTD | CHAR | 1 | XFELD | ||||
MANUAL | Created manually | J_1BMANUAL | CHAR | 1 | J_1BMANUAL | ||||
FOLLOW | Follow up activity made | J_1BFOLLOW | CHAR | 1 | XFELD | ||||
WAERK | SD Document Currency | WAERK | CUKY | 5 | TCURC | WAERS | FWS | ||
BELNR | Accounting Document Number | BELNR_D | CHAR | 10 | ALPHA | BELNR | BLN | ||
GJAHR | Fiscal Year | GJAHR | NUMC | 4 | GJAHR | GJAHR | GJR | ||
BUKRS | Company Code | BUKRS | CHAR | 4 | T001 | BUKRS | BUK | C_T001 | |
BRANCH | Business Place | J_1BBRANC_ | CHAR | 4 | J_1BBRANCH | J_1BBRANCH | |||
PARVW | Nota Fiscal Partner Function | J_1BPARVW | CHAR | 2 | J_1BAD | J_1BPARVW | PAR | ||
PARID | Partner ID (Customer, Vendor, Business Place) | J_1BPARID | CHAR | 10 | ALPHA | J_1BPARID | DEBI_KRED | ||
PARXCPDK | Indicator: Is the account a one-time account? | XCPDK | CHAR | 1 | XFELD | ||||
PARTYP | Nota Fiscal Partner Type | J_1BPARTYP | CHAR | 1 | J_1BPARTYP | ||||
CANCEL | Canceled | J_1BCANCEL | CHAR | 1 | XFELD | ||||
CANDAT | Cancellation Date | J_1BCANDAT | DATS | 8 | DATUM | ||||
SUBSEQ | Follow-On Document Exists | J_1BSUBSEQ | CHAR | 1 | XFELD | ||||
DOCREF | Reference to NF | J_1BDOCREF | NUMC | 10 | J_1BNFDOC | J_1BDOCNUM | |||
TRATY | Means-of-Transport Type | TRATY | CHAR | 4 | TVTY | TRATY | |||
TRAID | Means of Transport ID | TRAID | CHAR | 20 | TRAID | ||||
INCO1 | Incoterms (Part 1) | INCO1 | CHAR | 3 | TINC | INCO1 | |||
INCO2 | Incoterms (Part 2) | INCO2 | CHAR | 28 | INCO2 | ||||
SHPUNT | Shipping unit (especie) | J_1BSHPUNT | UNIT | 3 | T006 | CUNIT | MEINS | ||
ANZPK | Total number of packages in delivery | ANZPK | NUMC | 5 | ANZPK | ||||
SHPMRK | Mark of the shipping unit | J_1BSHPMRK | CHAR | 20 | TEXT20 | ||||
SHPNUM | Number of the shipping unit | J_1BSHPNUM | CHAR | 20 | TEXT20 | ||||
BRGEW | Gross weight | BRGEW_15 | QUAN | 15(3) | MENG15 | ||||
NTGEW | Net weight | NTGEW_15 | QUAN | 15(3) | MENG15 | ||||
GEWEI | Weight Unit | GEWEI | UNIT | 3 | T006 | CUNIT | MEINS | ||
ZFBDT | Baseline Date for Due Date Calculation | DZFBDT_BIW | DATS | 8 | DATUM | ||||
WITHA | Total withholding amount of Nota Fiscal | J_1BWITHAM | CURR | 15(2) | WERT8 | ||||
OBSERVAT | Legal Books Mod. 1 + 2: Header text for observations column | J_1BLBOBS | CHAR | 50 | J_1BLBOBS | ||||
VSTEL | Shipping Point/Receiving Point | VSTEL | CHAR | 4 | TVST | VSTEL | VST |
Key field | Non-key field |
How do I retrieve data from SAP structure ROXAX40259 using ABAP code?
As ROXAX40259 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 ROXAX40259 as there is no data to select.How to access SAP table ROXAX40259
Within an ECC or HANA version of SAP you can also view further information about ROXAX40259 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