OIJ_EL_TICKET_H_STR SAP (Universal ticket table processing Structure) Structure details
Description: Universal ticket table processing Structure
Related tables to OIJ_EL_TICKET_H_STR
Access table OIJ_EL_TICKET_H_STR
Structure field list including key, data, relationships and ABAP select examples
OIJ_EL_TICKET_H_STR 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 "Universal ticket table processing Structure" 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_OIJ_EL_TICKET_H_STR TYPE OIJ_EL_TICKET_H_STR.
The OIJ_EL_TICKET_H_STR table consists of various fields, each holding specific information or linking keys about Universal ticket table processing Structure data available in SAP. These include MANDT (Client), TICKET_KEY (OIL-TSW: Ticket key), TICKET_VERSION (OIL-TSW: Ticket version), TICKET_PURPOSE (OIL-TSW: Ticket Purpose).. 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 OIJ_EL_TICKET_H_STR 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 | |||
TICKET_KEY | OIL-TSW: Ticket key | OIJ_EL_TKT_KEY | CHAR | 20 | ALPHA | OIJ_EL_TKT_KEY | |||
TICKET_VERSION | OIL-TSW: Ticket version | OIJ_EL_TKT_VERSION | NUMC | 3 | OIJ_EL_TKT_VERSION | OIJ_TKT_VERS | |||
TICKET_PURPOSE | OIL-TSW: Ticket Purpose | OIJ_EL_TKT_PURPOSE | CHAR | 1 | OIJ_EL_TKT_PURPOSE | OIJ_TKT_PURP | |||
TICKET_TYPE | OIL-TSW: Ticket type | OIJ_EL_TKT_TYPE | CHAR | 3 | TOIJ_TKT_TYPE | OIJ_EL_TKT_TYPE | OIJ_TKT_TYPE | ||
TICKETNR | OIL-TSW: External ticket number | OIJ_TKTNR | CHAR | 20 | Assigned to domain | ALPHA | OIJ_TKTNR | OIU | |
TKTSUBRC | OIL-TSW: Ticket process return code | OIJ_TKTRC | CHAR | 2 | OIJ_TKTRC | ||||
TPLST | Transportation planning point | TPLST | CHAR | 4 | TTDS | TPLST | TDP | ||
TSYST | Transport system | OIJ_TSYST | CHAR | 10 | OIJTS | OIJ_TSYST | OIW | ||
IDOC_NUM | IDoc number | EDI_DOCNUM | NUMC | 16 | EDI_DOCNUM | DCN | |||
ERDAT | Date on Which Record Was Created | ERDAT | DATS | 8 | DATUM | ||||
ERZEIT | Time of creation | OI0_ERTIM | TIMS | 6 | UZEIT | ||||
ERNAM | Name of Person who Created the Object | ERNAM | CHAR | 12 | USNAM | ||||
AEDAT | Changed On | AEDAT | DATS | 8 | DATUM | ||||
AEZEIT | Time of day the record was changed | OI0_AETIM | TIMS | 6 | UZEIT | ||||
AENAM | Name of Person Who Changed Object | AENAM | CHAR | 12 | USNAM | ||||
BLOIND | Blocking indicator | OIJ_BLOIND | CHAR | 1 | XFELD | ||||
DELIND | Deletion indicator | OIJ_DELIND | CHAR | 1 | XFELD | ||||
CARRIER | Transport system Carrier | OIJ_CARRNR | CHAR | 10 | Assigned to domain | ALPHA | LIFNR | ||
CONSIGNE | Consignee Partner | OIJ_CONSIGNEE | CHAR | 10 | ALPHA | OIJ_PARTNR | |||
INSPECTOR | Inspector | OIJ_INSPECTOR | CHAR | 10 | ALPHA | OIJ_PARTNR | |||
SHIPPER | Shipper | OIJ_SHIPNR | CHAR | 10 | Assigned to domain | ALPHA | LIFNR | ||
SUPPLIER | Location Partner | OIJ_PARTNR | CHAR | 10 | ALPHA | OIJ_PARTNR | |||
TRADER | Location Partner | OIJ_PARTNR | CHAR | 10 | ALPHA | OIJ_PARTNR | |||
EXTTKTNR | External Ticket Number | OIJ_RU_EXTTKTNR | CHAR | 10 | CHAR10 | ||||
TKTSTATUSRU | Ticket Approval Status | OIJ_RU_TKT_STATUS | CHAR | 1 | OIJ_RU_TKT_STATUS | ||||
CHANGENR | Change Number | OIJ_RU_CHANGENR | NUMC | 4 | NUM04 | ||||
DELIVERYTYP | Delivery Type | OIJ_RU_DELTYP | CHAR | 2 | OIJ_RU_DEL_TYP | CHAR2 | |||
DISPATCHTYP | Freight Shipment Type | OIJ_RU_DISPTYP | CHAR | 2 | OIJ_RU_DISP_TYP | CHAR2 | OIJ_RU_DT | ||
SENDSPEED | Delivery Speed | OIJ_RU_SENDSPD | CHAR | 2 | OIJ_RU_SEND_SPD | CHAR2 | |||
PAYMENTLOC | Payment Location | OIJ_RU_PMTLOC | CHAR | 2 | OIJ_RU_PMT_LOC | CHAR2 | |||
PAYMENTLOCTYP | Payment Location Type | OIJ_RU_PMTLOCTYP | CHAR | 1 | OIJ_RU_PMTLOCTYP | ||||
PAYMENTTYP | Payment Type | OIJ_RU_PMTTYP | CHAR | 2 | OIJ_RU_PMT_TYP | CHAR2 | |||
CARGOTYP | Freight Loading Type | OIJ_RU_CARGTYP | CHAR | 2 | OIJ_RU_CARG_TYP | CHAR2 | |||
SCALETYPE | Measurement Method | OIJ_RU_SCALE_TYPE | CHAR | 2 | OIJ_RU_SCALETYP | CHAR2 | |||
FREIGHT_VALUE | Declared Value of Freight | OIJ_RU_FREIGHT_VALUE | CURR | 13(2) | WERT7 | ||||
FREIGHT_WAERS | Currency Key | WAERS | CUKY | 5 | TCURC | WAERS | FWS | ||
RESPPARTY | Responsible Party for Loading | OIJ_RU_RESPPRT | CHAR | 2 | OIJ_RU_RESP_PRT | CHAR2 | |||
SEND_TGNL | Sender TGNL Code | OIJ_RU_SEND_TGNL | CHAR | 4 | OIJ_RU_PAR_TGNL | ||||
RECV_TGNL | Receiver TGNL Code | OIJ_RU_RECV_TGNL | CHAR | 4 | OIJ_RU_PAR_TGNL | ||||
UPDATEFLAG | Transaction type | TRTYP | CHAR | 1 | TRTYP |
Key field | Non-key field |
How do I retrieve data from SAP structure OIJ_EL_TICKET_H_STR using ABAP code?
As OIJ_EL_TICKET_H_STR 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 OIJ_EL_TICKET_H_STR as there is no data to select.How to access SAP table OIJ_EL_TICKET_H_STR
Within an ECC or HANA version of SAP you can also view further information about OIJ_EL_TICKET_H_STR 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