JIT_ESDINFO SAP (Item Data for EDI JIT Monitor) Structure details
Description: Item Data for EDI JIT Monitor
Structure field list including key, data, relationships and ABAP select examples
JIT_ESDINFO 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 "Item Data for EDI JIT Monitor" 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_JIT_ESDINFO TYPE JIT_ESDINFO.
The JIT_ESDINFO table consists of various fields, each holding specific information or linking keys about Item Data for EDI JIT Monitor data available in SAP. These include KDMAT (Material belonging to the customer), ARKTX (Short text for sales order item), VMENG (Confirmed quantity for availability check in SKU), VRKME (Sales unit).. 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 JIT_ESDINFO 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 |
| DOCNUM | IDoc number | EDI_DOCNUM | NUMC | 16 | EDI_DOCNUM | DCN | |||
| KDMAT | Material belonging to the customer | KDMAT | CHAR | 35 | IDNEX | ||||
| ARKTX | Short text for sales order item | ARKTX | CHAR | 40 | TEXT40 | ||||
| VMENG | Confirmed quantity for availability check in SKU | VMENG | QUAN | 15(3) | MENG15 | ||||
| VRKME | Sales unit | VRKME | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
| RDATUM | Planned Requirements Date | JIT_RDATUM | DATS | 8 | DATE | ||||
| RZEIT | Planned Requirements Time | JIT_RZEIT | TIMS | 6 | TIME | ||||
| EXSTI | Transmitted External Status Information | JIT_EXSTI | CHAR | 35 | TEXT35 | ||||
| ABLAD | Unloading Point | ABLAD | CHAR | 25 | TEXT25 | ||||
| FLDPO | Assembly location of parts group at customer site | JIT_FLDPO | CHAR | 20 | TEXT20 | ||||
| LIUMF | Components Groups Material (Delivery Scope) | JIT_LIUMF | CHAR | 18 | Assigned to domain | MATN1 | MATNR | ||
| IDNLF | Material Number Used by Vendor | IDNLF | CHAR | 35 | IDNEX | ||||
| EDATUM | Date of External Status | JIT_EDATUM | DATS | 8 | DATE | ||||
| EZEIT | External Status Time | JIT_EZEIT | TIMS | 6 | TIME | ||||
| CHNGLEV | Data Element Type CHAR Length 35 | CHAR35 | CHAR | 35 | CHAR35 | ||||
| PDATUM | Planned Shipping Date | JIT_PDATUM | DATS | 8 | DATE | ||||
| PZEIT | Planned Shipping Time | JIT_PZEIT | TIMS | 6 | TIME | ||||
| GRPIN | Grouping and Sequencing Information Components Group | JIT_GRPIN | CHAR | 20 | JIT_GRPIN | JIT_GRPIN | |||
| GRIND | Index for Grouping and Sequencing Information | JIT_GRIND | NUMC | 6 | JIT_GRIND | ||||
| LIUMF_EXTERNAL | Long Material Number for Field LIUMF | MGV_LIUMF_EXTERNAL | CHAR | 40 | MATNR_EXT | ||||
| LIUMF_VERSION | Version Number for Field LIUMF | MGV_LIUMF_VERSION | CHAR | 10 | MATNW | MATNR_VERS | |||
| LIUMF_GUID | External GUID for Field LIUMF | MGV_LIUMF_GUID | CHAR | 32 | MATNR_EGUID | ||||
| KDMAT_EXTERNAL | Customer Material | MGV_KDMAT_EXTERNAL | CHAR | 40 | MATNR_EXT | ||||
| KDMAT_VERSION | Customer Material | MGV_KDMAT_VERSION | CHAR | 10 | MATNW | MATNR_VERS | |||
| KDMAT_GUID | Customer Material | MGV_KDMAT_GUID | CHAR | 32 | MATNR_EGUID | ||||
| IDNLF_EXTERNAL | Material Number Used by Vendor | MGV_IDNLF_EXTERNAL | CHAR | 40 | MATNR_EXT | ||||
| IDNLF_VERSION | Material Number Used by Vendor | MGV_IDNLF_VERSION | CHAR | 10 | MATNW | MATNR_VERS | |||
| IDNLF_GUID | Material Number Used by Vendor | MGV_IDNLF_GUID | CHAR | 32 | MATNR_EGUID | ||||
| RTY01 | Type of Reference Number | JIT_REFTY | CHAR | 2 | Assigned to domain | JIT_REFTY | |||
| RFN01 | Reference Number / Reference Text for JIT Call | JIT_REFTX | CHAR | 25 | JIT_REFTX | ||||
| RTY02 | Type of Reference Number | JIT_REFTY | CHAR | 2 | Assigned to domain | JIT_REFTY | |||
| RFN02 | Reference Number / Reference Text for JIT Call | JIT_REFTX | CHAR | 25 | JIT_REFTX | ||||
| RTY03 | Type of Reference Number | JIT_REFTY | CHAR | 2 | Assigned to domain | JIT_REFTY | |||
| RFN03 | Reference Number / Reference Text for JIT Call | JIT_REFTX | CHAR | 25 | JIT_REFTX |
| Key field | Non-key field |
How do I retrieve data from SAP structure JIT_ESDINFO using ABAP code?
As JIT_ESDINFO 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 JIT_ESDINFO as there is no data to select.How to access SAP table JIT_ESDINFO
Within an ECC or HANA version of SAP you can also view further information about JIT_ESDINFO 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