J_1UF_N1_S1T_EXT SAP (Section Data Extended with Grouping Keys) Structure details
Description: Section Data Extended with Grouping Keys
Related tables to J_1UF_N1_S1T_EXT
Access table J_1UF_N1_S1T_EXT
Structure field list including key, data, relationships and ABAP select examples
J_1UF_N1_S1T_EXT 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 "Section Data Extended with Grouping Keys" 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_1UF_N1_S1T_EXT TYPE J_1UF_N1_S1T_EXT.
The J_1UF_N1_S1T_EXT table consists of various fields, each holding specific information or linking keys about Section Data Extended with Grouping Keys data available in SAP. These include IBLNR (Physical Inventory Document), LGORT (Storage Location), RESPNAME1 (Name of Person Responsible), RESPNAME2 (Name of Person Responsible).. 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 J_1UF_N1_S1T_EXT 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 |
| GR_KEY | 0 | ||||||||
| IBLNR | Physical Inventory Document | IBLNR | CHAR | 10 | ALPHA | BELNR | IBN | ||
| LGORT | Storage Location | LGORT_D | CHAR | 4 | LGORT | LAG | |||
| RESPNAME1 | Name of Person Responsible | J_3R_RESPNAME | CHAR | 80 | TEXT80 | ||||
| RESPNAME2 | Name of Person Responsible | J_3R_RESPNAME | CHAR | 80 | TEXT80 | ||||
| RESPPOS | Position of the Responsible Person | J_3R_RESPPOS | CHAR | 40 | TEXT40 | ||||
| N12_DOC_DATE | Document Date | J_3R_DOCDATE | DATS | 8 | DATS | ||||
| N18_SEQNUM | Sequence Number | J_1UF_SEQNUM | CHAR | 6 | TEXT06 | ||||
| N19_ASSET_DESC | Asset Description and Additional Description | J_1UF_ASSET_DESC | CHAR | 100 | TEXT100 | ||||
| N20_AA_QUANT | Accounting Quantity | J_1UF_AA_QUANT | QUAN | 13 | |||||
| N21_AA_PRICE | Price | J_1UF_PRICE | CURR | 17(2) | |||||
| N22_AA_AMNT | Accounting Value | J_1UF_AA_AMNT | CURR | 17(2) | |||||
| N23_IR_QUANT | Stocktaking Quantity | J_1UF_IR_QUANT | QUAN | 14(2) | |||||
| N24_IR_PRICE | Price | J_1UF_PRICE | CURR | 17(2) | |||||
| N25_IR_AMNT | Stocktaking Value | J_1UF_IR_AMNT | CURR | 17(2) | |||||
| N26_DIFF_Q | Quantity Difference | J_1UF_DIFF_QUANT | QUAN | 14(2) | |||||
| N27_DIFF_PR | Price | J_1UF_PRICE | CURR | 17(2) | |||||
| N28_DIFF_AMNT | Value Difference | J_1UF_DIFF_AMNT | CURR | 17(2) | |||||
| WAERS | Currency Key | WAERS | CUKY | 5 | Assigned to domain | WAERS | FWS | ||
| MEINS | Base Unit of Measure | MEINS | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
| MATNR | Material Number | MATNR | CHAR | 18 | Assigned to domain | MATN1 | MATNR | MAT | S_MAT1 |
| FYEAR | Fiscal Year | GJAHR | NUMC | 4 | GJAHR | GJAHR | GJR | ||
| PERIOD | Fiscal Period | MONAT | NUMC | 2 | MONAT | ||||
| COUNTEDQUAN | Quantity | MENGE_D | QUAN | 13(3) | MENG13 | ||||
| LGORT | Storage Location | LGORT_D | CHAR | 4 | Assigned to domain | LGORT | LAG | ||
| MBLNR | Number of Material Document | MBLNR | CHAR | 10 | ALPHA | BELNR | MBN | ||
| ZEILE | Item in Material Document | MBLPO | NUMC | 4 | MBLPO | POS | |||
| VGART | Transaction/Event Type | VGART | CHAR | 2 | Assigned to domain | VGART | |||
| DMBTR | Amount in Local Currency | DMBTR | CURR | 13(2) | WERT7 | ||||
| MTART | Material Type | MTART | CHAR | 4 | Assigned to domain | MTART | MTA |
| Key field | Non-key field |
How do I retrieve data from SAP structure J_1UF_N1_S1T_EXT using ABAP code?
As J_1UF_N1_S1T_EXT 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_1UF_N1_S1T_EXT as there is no data to select.How to access SAP table J_1UF_N1_S1T_EXT
Within an ECC or HANA version of SAP you can also view further information about J_1UF_N1_S1T_EXT 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