JITDIAHDIB SAP (Dialog Structure for Documentation Data Search in JIT) Structure details
Description: Dialog Structure for Documentation Data Search in JIT
Structure field list including key, data, relationships and ABAP select examples
JITDIAHDIB 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 "Dialog Structure for Documentation Data Search in JIT" 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_JITDIAHDIB TYPE JITDIAHDIB.
The JITDIAHDIB table consists of various fields, each holding specific information or linking keys about Dialog Structure for Documentation Data Search in JIT data available in SAP. These include MANDT (Client), JINUM (Call Number), CUSTO (JIT Customer), LIFNR (Vendor number at customer location).. 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)
SAP JITDIAHDIB 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 | Assigned to domain | MANDT | |||
JINUM | Call Number | JIT_ABNUM | NUMC | 10 | JITHD | JIT_ABNUM | |||
CUSTO | JIT Customer | JIT_CUSTO | CHAR | 4 | JITCU | JIT_CUSTO | |||
LIFNR | Vendor number at customer location | LIFNR_ED1 | CHAR | 17 | CHAR17 | ||||
KUNNR | Sold-to party | KUNAG | CHAR | 10 | VLPKM | ALPHA | KUNNR | VAG | |
KNREF | Customer description of partner (plant, storage location) | KNREF | CHAR | 30 | VLPKM | KNREF | KNREF | ||
ABRVW | Usage Indicator | ABRVW | CHAR | 3 | TVLV | ABRVW | |||
TZONE | Time zone of customer plant | JIT_TZONE | CHAR | 6 | TTZZ | TZNZONE | |||
FPROF | Determ.profile for comp.group | JIT_FPROF | CHAR | 8 | CJIT08 | CHAR8 | |||
VATYP | Proposal call type | JIT_VATYP | CHAR | 1 | JIT_ABTYP | ||||
MTCH | Logistical Matching of Delivery Confirmation | JIT_MTCH | CHAR | 1 | JIT_MTCH | ||||
IMPAC | Signal Monitor Active | JIT_IMPAC | CHAR | 1 | XFELD | ||||
MTMOD | Maintenance Mode Sequenced JIT Calls | JIT_MAINT_MODE | CHAR | 1 | JIT_MAINT_MODE | JIT_M_MODE | |||
CREHU | Creation of Handling Units | JIT_CRHU | CHAR | 1 | JIT_CRHU | ||||
DON_PROFIL | Control Profile for Summarized JIT Calls (SumJC) | JIT_DON_PROFIL | CHAR | 12 | CHAR12 | ||||
PRIID | Reference Numbers in Delivery IDoc | JIT_PRIID | CHAR | 1 | JIT_PRIID | ||||
NOPCK | Indicator: not relevant for picking | NO_PICKING | CHAR | 1 | XFELD | ||||
KUNWE | Ship-to party | KUNWE | CHAR | 10 | Assigned to domain | ALPHA | KUNNR | ||
LPROF | Control Profile for the Delivery Creation | JIT_LPROF | CHAR | 8 | CHAR8 | ||||
RNPID | Type of Reference Number in IDoc | JIT_RNPID | CHAR | 1 | JIT_RNPID | ||||
DLSLV | Split Level SumJC Delivery Grouping | JIT_DLSLV | CHAR | 1 | JIT_DLSLV | ||||
PRIVC | Reference Numbers in IDoc for Billing Document | JIT_PRIVC | CHAR | 1 | JIT_PRIVC | ||||
GIUPD | Status Update on Goods Issue Posting | JIT_GIUPD | CHAR | 1 | XFELD | ||||
NAME1 | Name 1 | NAME1_GP | CHAR | 35 | NAME | ||||
NAME2 | Name 2 | NAME2_GP | CHAR | 35 | NAME | ||||
NAME3 | Name 3 | NAME3_GP | CHAR | 35 | NAME | ||||
NAME4 | Name 4 | NAME4_GP | CHAR | 35 | NAME | ||||
STRAS | House number and street | STRAS_GP | CHAR | 35 | TEXT35 | ||||
LAND1 | Country Key | LAND1_GP | CHAR | 3 | Assigned to domain | LAND1 | C_LAND1 | ||
PSTLZ | Postal Code | PSTLZ | CHAR | 10 | PSTLZ | ||||
ORT01 | City | ORT01_GP | CHAR | 35 | TEXT35 | ||||
ORT02 | District | ORT02_GP | CHAR | 35 | TEXT35 | ||||
PERIV | Fiscal Year Variant | PERIV | CHAR | 2 | Assigned to domain | PERIV | |||
PRODN | External Call Number | JIT_PRODN | CHAR | 35 | TEXT35 | JITP_PRODN | H_JIT_PRODN | ||
SEQNR | External Sequence Number | JIT_SEQNR | CHAR | 35 | TEXT35 | ||||
VETYP | Additional Information 1 | JIT_VETYP | CHAR | 35 | TEXT35 | ||||
VEHID | Additional Information 2 | JIT_VEHID | CHAR | 35 | TEXT35 | ||||
TEXHD | Supplementary Text Exists | JIT_TEXHD | CHAR | 1 | XFELD | ||||
SSPEZ | Additional Information 3 | JIT_SSPEZ | CHAR | 35 | TEXT35 | ||||
NACHB | Repeat Order | JIT_NACHB | CHAR | 1 | XFELD | ||||
ABTYP | Call Type | JIT_ABTYP | CHAR | 1 | JIT_ABTYP | JITP_ABTYP | |||
ARCHI | Archiving status | JIT_ARCHI | CHAR | 1 | XFELD | ||||
DDATA | Documentation Data Available | JIT_DDATA | CHAR | 1 | XFELD | ||||
RANGE | Call is Part of a Summarized Range Call | JIT_RANGE | CHAR | 1 | CHECKBOX | ||||
REFTY1 | Type of Reference Number | JIT_REFTY | CHAR | 2 | CJIT15 | JIT_REFTY | |||
LEVTY1 | Additional Reference Text | JIT_LEVTY | CHAR | 1 | JIT_LEVTY | ||||
REFTX1 | Reference Number / Reference Text for JIT Call | JIT_REFTX | CHAR | 25 | JIT_REFTX | ||||
REFTY2 | Type of Reference Number | JIT_REFTY | CHAR | 2 | CJIT15 | JIT_REFTY | |||
LEVTY2 | Additional Reference Text | JIT_LEVTY | CHAR | 1 | JIT_LEVTY | ||||
REFTX2 | Reference Number / Reference Text for JIT Call | JIT_REFTX | CHAR | 25 | JIT_REFTX | ||||
REFTY3 | Type of Reference Number | JIT_REFTY | CHAR | 2 | CJIT15 | JIT_REFTY | |||
LEVTY3 | Additional Reference Text | JIT_LEVTY | CHAR | 1 | JIT_LEVTY | ||||
REFTX3 | Reference Number / Reference Text for JIT Call | JIT_REFTX | CHAR | 25 | JIT_REFTX | ||||
EDI_DOCNUM | IDoc number | EDI_DOCNUM | NUMC | 16 | EDI_DOCNUM | DCN | |||
MATIP | Material numbers ready for entry? | JIT_MATIP | CHAR | 1 | XFELD | ||||
SELKZ | Selection flag | SELKZ | CHAR | 1 | SELKZ | ||||
V_JINUM | Call Number | JIT_ABNUM | NUMC | 10 | Assigned to domain | JIT_ABNUM | |||
IBASE | IBase: Number of the Installed Base/IBase | IB_IBASE | NUMC | 18 | ALPHA | IB_INSTANCE | IIB | IBIBM |
Key field | Non-key field |
How do I retrieve data from SAP structure JITDIAHDIB using ABAP code?
As JITDIAHDIB 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 JITDIAHDIB as there is no data to select.How to access SAP table JITDIAHDIB
Within an ECC or HANA version of SAP you can also view further information about JITDIAHDIB 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