ROIJNOMI_LDS_UPD SAP (OIJNOMI_LDS Update structure) Structure details
Description: OIJNOMI_LDS Update structure
Related tables to ROIJNOMI_LDS_UPD
Access table ROIJNOMI_LDS_UPD
Structure field list including key, data, relationships and ABAP select examples
ROIJNOMI_LDS_UPD 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 "OIJNOMI_LDS Update 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_ROIJNOMI_LDS_UPD TYPE ROIJNOMI_LDS_UPD.
The ROIJNOMI_LDS_UPD table consists of various fields, each holding specific information or linking keys about OIJNOMI_LDS Update structure data available in SAP. These include MANDT (Client), PEGTYPE (Pegging type), PEGID (Pegging identifier), BRTHSEQ (Berth Assignment Sequence 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 or numeric)
SAP ROIJNOMI_LDS_UPD 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 | |||
PEGTYPE | Pegging type | OIJ_PEGTYPE | CHAR | 2 | TOIJ_PEGTYPE | OIJ_PEGTYPE | |||
PEGID | Pegging identifier | OIJ_PEGID | CHAR | 20 | ALPHA | OIJ_PEGID | |||
BRTHSEQ | Berth Assignment Sequence Number | OIJ_LDSEQ | NUMC | 5 | NUMC5 | ||||
NOMTK | Nomination (technical) Key | OIJ_NOMTK | CHAR | 20 | Assigned to domain | ALPHA | OIJ_NOMTK | ||
SHIPLDSEQ | Load/Discharge Sequence sent from ship | OIJ_SHIPLDSEQ | NUMC | 5 | NUMC5 | ||||
SCHEDMAT | Scheduled material | OIJ_SMATNR | CHAR | 18 | Assigned to domain | MATN1 | MATNR | ||
LDMAT | Loaded/Discharged Material | OIJ_MATNR | CHAR | 18 | MARA | MATN1 | MATNR | ||
LDQUAN | Loaded/Discharged Material Quantity per Berthing Line | OIJ_SCHQUAN | QUAN | 13(3) | MENG13 | ||||
LDUOM | Loaded/Discharged Material UOM | OIJ_LDUOM | UNIT | 3 | T006 | CUNIT | MEINS | ||
ACTUALQTY | Actual posted quantity | OIJ_ACTQTY | QUAN | 13(3) | MENG13 | ||||
ACTUALUOM | Actual posted quantity Unit of Measure | OIJ_ACTUOM | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
BERID | Berth identifier | OIJ_BERID | CHAR | 20 | OIJBER | ALPHA | OIJ_BERID | ||
TANKID | SOC: Storage object characteristic segment number | OII_SOCNR | CHAR | 20 | OIISOCK | OII_SOCNR | |||
LIGHTLOC | Lightering Location Identifier | OIJ_LIGHTLOCID | CHAR | 10 | OIFSPBL | ALPHA | OIF_PBLNR | ||
LIGHTVESSEL | Lightering Vessel Identifier | OIJ_LIGHTVESS | CHAR | 10 | OIGV | ALPHA | OIG_VHLNMR | ||
LIGHTNOM | Lightering Nomination Identifier | OIJ_LIGHTNOM | CHAR | 20 | OIJNOMH | ALPHA | OIJ_NOMTK | ||
LDFRDATE | Berth Scheduling Start Date | OIJ_BERTHSTR | DATS | 8 | DATE | ||||
LDFRTIME | Berth Scheduling Start Time | OIJ_BERTHSTRT | TIMS | 6 | TIME | ||||
LDTODATE | Berth Scheduling End Date | OIJ_BERTHEND | DATS | 8 | DATE | ||||
LDTOTIME | Berth Scheduling End Time | OIJ_BERTHENDT | TIMS | 6 | TIME | ||||
LDSYSTID | Loading system | OIJ_LSYST | CHAR | 10 | OIJTS | OIJ_TSYST | |||
TARGETQTY | Minimum quantity that must be in a loading system | OIJ_TARQTY | QUAN | 13(3) | MENGE | ||||
TARGETQTYUOM | Target quantity UoM | OIJ_TARQTYUOM | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
METERNO | GMM: Number of general meter | OII_GMMNR | CHAR | 20 | Assigned to domain | ALPHA | OII_GMMNR | OIJ | |
STMETER | start meter reading for Load/Discharge scheduling | OIJ_STMETER | NUMC | 12 | NUMC12 | ||||
ENDMETER | Load/Disch. end meter reading of a tank | OIJ_ENDMETER | NUMC | 12 | OII_MCOUNT | ||||
DIPDATE | Tank dip date with local time at tank loc. | OII_DIPDAT | DATS | 8 | DATS | ||||
DIPTIME | Time of tank dip (local time of tank location) | OII_DIPZEIT | TIMS | 6 | TIMES | ||||
ENDGAUGEVAL | Load/Disch. end dip reading of a tank | OIJ_ENDDIP | QUAN | 13(3) | MENGE | ||||
ENDGAUGEUOM | First UoM of start gauge value | OIJ_STDIPUOM1 | UNIT | 3 | T006 | CUNIT | MEINS | ||
VSL_ARRDRAFT | Ship Arrival Draft sent from ship | OIJ_ARRDRAFT | QUAN | 13(3) | MENGE | ||||
VSL_DEPDRAFT | Ship Departure Draft sent from ship | OIJ_DEPDRAFT | QUAN | 13(3) | MENGE | ||||
DRAFTUOM | UoM of draft of a ship | OIJ_DRF_UOM | UNIT | 3 | T006 | CUNIT | MEINS | ||
VSL_TXDEADWGT | Ship Deadweight sent from the ship | OIJ_SHIPDWEIGHT | QUAN | 13(3) | MENGE | ||||
DEADWGTUOM | UoM of deadweight of a ship | OIJ_DWEIGHTUOM | UNIT | 3 | T006 | CUNIT | MEINS | ||
TICKETNO | OIL-TSW: External ticket number | OIJ_TKTNR | CHAR | 20 | Assigned to domain | ALPHA | OIJ_TKTNR | OIU | |
FLUSHFLAG | Flush/Push to Ship flag for a loading system | OIJ_FLUSHFL | CHAR | 1 | OIJ_FLUSHFL | ||||
LDIND | Load/Discharge indicator | OIJ_LDIND | CHAR | 1 | OIJ_LDIND | ||||
LIGHTNOMIT | Lightering Nomination item number | OIJ_LIGHTNOMIT | NUMC | 10 | OIJNOMI | OIJ_ITEM | |||
SCHED_TST_FROM | Scheduled / Acceptance / Pipe Batch Start Timestamp | OIJ_SCHED_F | DEC | 15 | TZNTSTMPS | ||||
SCHED_TST_TO | Scheduled / Acceptance / Pipe Batch End Timestamp | OIJ_SCHED_T | DEC | 15 | TZNTSTMPS | ||||
UPD_FLAG | Update flag | OIJ_UPDATEFLAG | CHAR | 1 | CHAR1 |
Key field | Non-key field |
How do I retrieve data from SAP structure ROIJNOMI_LDS_UPD using ABAP code?
As ROIJNOMI_LDS_UPD 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 ROIJNOMI_LDS_UPD as there is no data to select.How to access SAP table ROIJNOMI_LDS_UPD
Within an ECC or HANA version of SAP you can also view further information about ROIJNOMI_LDS_UPD 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