ROIJEV_IO SAP (I/O Structure for Vehicle~Berth Master Data Events) Structure details
Description: I/O Structure for Vehicle~Berth Master Data Events
Structure field list including key, data, relationships and ABAP select examples
ROIJEV_IO 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 "I/O Structure for Vehicle~Berth Master Data Events" 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_ROIJEV_IO TYPE ROIJEV_IO.
The ROIJEV_IO table consists of various fields, each holding specific information or linking keys about I/O Structure for Vehicle~Berth Master Data Events data available in SAP. These include CLIENT (Client), APP_AREA (Application area), OBJECT_ID (Object ID), EVENT_NR (Master Data Event number).. 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 ROIJEV_IO 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 |
| CLIENT | Client | MANDT | CLNT | 3 | T000 | MANDT | |||
| APP_AREA | Application area | OI0_APPAREA | CHAR | 10 | OI0_APPAREA | ||||
| OBJECT_ID | Object ID | OIG_OBJID | CHAR | 20 | OIG_OBJID | ||||
| EVENT_NR | Master Data Event number | OI0_EVNR | NUMC | 8 | OI0_EVNR | ||||
| TYPE | Master Data Event Type | OI0_EVTYPE | CHAR | 4 | TOI0EV | OI0_EVTYPE | OI0_EVTYP | OI0_EVTYPE | |
| DRIVERCODE | TD driver number | OIG_DRVNMR | CHAR | 10 | OIGD | ALPHA | OIG_DRVNMR | DNO | |
| CPARID | Location Partner | OIJ_PARTNR | CHAR | 10 | ALPHA | OIJ_PARTNR | |||
| RPART | OIL-TSW: Role partner type | OIJ_RPART | CHAR | 2 | OIJRRPART | OIJ_RPART | |||
| LOC_ID | Location ID | OIJ_LOCID | CHAR | 10 | OIJLOC | OIJ_LOCID | OIX | ||
| DOC_TYPE | TD - event document type | OIG_EVDCTY | CHAR | 1 | Assigned to domain | OIG_EVDCTY | |||
| DOC_NUMBER | TD Assigned document number | OIG_ASGDOC | CHAR | 10 | ALPHA | OIG_ASGDOC | |||
| UPDFLAG | Transaction type | TRTYP | CHAR | 1 | TRTYP | ||||
| EV_SEQ | TD - event sequence number | OIG_EVSEQ | CHAR | 4 | ALPHA | OIG_EVSEQ | |||
| STATUS | Master Data Event Status | OI0_EVSTAT | CHAR | 1 | OI0_EVSTAT | ||||
| PSTDTF | TD Event: Planned Start Date - From | OIG_PSTDTF | DATS | 8 | DATUM | ||||
| PSTTMF | TD Event: Planned Start Time - From | OIG_PSTTMF | TIMS | 6 | UZEIT | ||||
| PSTDTT | TD Event: Planned Start Date - To | OIG_PSTDTT | DATS | 8 | DATUM | ||||
| PSTTMT | TD Event: Planned Start Time - To | OIG_PSTTMT | TIMS | 6 | UZEIT | ||||
| PEDDTF | TD Event: Planned End Date - From | OIG_PEDDTF | DATS | 8 | DATUM | ||||
| PEDTMF | TD Event: Planned End Time - From | OIG_PEDTMF | TIMS | 6 | UZEIT | ||||
| PEDDTT | TD Event: Planned End Date - To | OIG_PEDDTT | DATS | 8 | DATUM | ||||
| PEDTMT | TD - event planned - 'end time to' | OIG_PEDTMT | TIMS | 6 | UZEIT | ||||
| CRE_DATE | Date on Which Record Was Created | ERDAT | DATS | 8 | DATUM | ||||
| CRE_TIME | Entry time | ERZET | TIMS | 6 | UZEIT | ||||
| CRE_NAME | Name of Person who Created the Object | ERNAM | CHAR | 12 | USNAM | ||||
| CHA_NAME | Name of Person Who Changed Object | AENAM | CHAR | 12 | USNAM | ||||
| CHA_DATE | Changed On | AEDAT | DATS | 8 | DATUM | ||||
| CHA_TIME | Time last change was made | AEZET | TIMS | 6 | UZEIT | ||||
| ASTDTF | TD - Actual Start Date of Event (From) | OIG_ASTDTF | DATS | 8 | DATUM | ||||
| ASTTMF | TD - Actual Start Time of Event (From) | OIG_ASTTMF | TIMS | 6 | UZEIT | ||||
| ASTDTT | TD - Actual Start Date of Event (To) | OIG_ASTDTT | DATS | 8 | DATUM | ||||
| ASTTMT | TD - Actual Start Time of Event (To) | OIG_ASTTMT | TIMS | 6 | UZEIT | ||||
| AEDDTF | TD Event actual end date from | OIG_AEDDTF | DATS | 8 | DATUM | ||||
| AEDTMF | TD Event actual end time from | OIG_AEDTMF | TIMS | 6 | UZEIT | ||||
| AEDDTT | TD Event actual end date to | OIG_AEDDTT | DATS | 8 | DATUM | ||||
| AEDTMT | TD Event actual end time to | OIG_AEDTMT | TIMS | 6 | UZEIT | ||||
| LONGTEXT | TD - event long text indicator | OIG_EVLT | CHAR | 1 | OIG_EVLT | ||||
| EV_TEXT | Text Line | TDLINE | CHAR | 132 | TDSTXLLINE | ||||
| APP_AREA_TEXT | Description of Application Area | OI0_APAREADESC | CHAR | 40 | OI0_EVDESCR | ||||
| STATUSTEXT | TD - event status text | OIG_EVSTXT | CHAR | 60 | AS4TEXT | ||||
| TYPE_TEXT | Master Data Event Type Text | OI0_EVDESCR | CHAR | 40 | OI0_EVDESCR |
| Key field | Non-key field |
How do I retrieve data from SAP structure ROIJEV_IO using ABAP code?
As ROIJEV_IO 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 ROIJEV_IO as there is no data to select.How to access SAP table ROIJEV_IO
Within an ECC or HANA version of SAP you can also view further information about ROIJEV_IO 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