ROIUPR_SSH SAP (Supply Source Header) Structure details
Description: Supply Source Header
Structure field list including key, data, relationships and ABAP select examples
ROIUPR_SSH 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 "Supply Source Header" 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_ROIUPR_SSH TYPE ROIUPR_SSH.
The ROIUPR_SSH table consists of various fields, each holding specific information or linking keys about Supply Source Header data available in SAP. These include MANDT (Client), DN_NO (Delivery network number), BUKRS (Company Code), VNAME (Joint Venture).. 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 ROIUPR_SSH 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 | |||
DN_NO | Delivery network number | OIU_DN_NO | CHAR | 20 | OIU_PR_DN | ALPHA | OIU_DN_NO | OIU_DN | H_OIU_PR_DN |
BUKRS | Company Code | BUKRS | CHAR | 4 | T001 | BUKRS | BUK | C_T001 | |
VNAME | Joint Venture | JV_NAME | CHAR | 6 | OIU_DO_JV | ALPHA | JV_NAME | JVV | |
WL_NO | Well ID number | OIU_WL_NO | CHAR | 15 | OIU_PR_WELL | ALPHA | OIU_WL_NO | OIU_WELL | H_OIU_PR_WELL |
WC_NO | Well Completion Number | OIU_WC_NO | CHAR | 5 | OIU_PR_WC | ALPHA | OIU_WC_NO | OIU_WC | H_OIU_PR_WC |
MP_NO | Measurement point number | OIU_MP_NO | CHAR | 20 | OIU_PR_MP | ALPHA | OIU_MP_NO | OIU_MP | H_OIU_PR_MP |
VT_CD | Volume Type Code | OIU_VL_TYPE_CD | CHAR | 2 | OIU_PR_VLTYP | OIU_VL_TYPE_CD | OIU_VL_TYPE | ||
EFF_FROM_DT | Effective from date | OIU_EFF_FROM_DT | DATS | 8 | DATUM | OIU_EFD | |||
EFF_TO_DT | Effective To Date | OIU_EFF_TO_DT | DATS | 8 | DATUM | OIU_ETD | |||
SSH_NO | Supply Source Nomber | OIU_SSH_NO | NUMC | 12 | OIU_SYS_NO | ||||
OIU_CRUSER | Name of Person who Created the Object | ERNAM | CHAR | 12 | USNAM | ||||
OIU_TIMESTAMP | UTC Time Stamp in Short Form (YYYYMMDDhhmmss) | TZNTSTMPS | DEC | 15 | TZNTSTMPS | ||||
DN_DE | Delivery network description | OIU_DN_DE | CHAR | 35 | OIU_TEXT35 | ||||
BUTXT | Name of Company Code or Company | BUTXT | CHAR | 25 | TEXT25 | ||||
VNAME_NM | venture name | OIU_VNAME_NM | CHAR | 35 | OIU_TEXT35 | ||||
WC_NM | Well name | OIU_WL_NM | CHAR | 35 | CHAR35 | ||||
VL_TYPE_DE | Volume Type Description | OIU_VL_TYPE_DE | CHAR | 50 | OIU_TEXT50 | ||||
XXDBACTION | Database Action Flag | OIU_DBACTION | CHAR | 1 | CHAR1 | ||||
REF_DN_NO | Reference delivery network number | OIU_DN_NO_REF | CHAR | 20 | Assigned to domain | ALPHA | OIU_DN_NO | OIU_DN_REF | |
REF_EFF_FROM_DT | Reference effective from date | OIU_EFF_FROM_DT_REF | DATS | 8 | DATUM | OIU_R_EFD | |||
REF_EFF_TO_DT | Effective To Date | OIU_EFF_TO_DT | DATS | 8 | DATUM | OIU_ETD | |||
REF_VNAME | Reference Joint Venture | OIU_JV_NAME_REF | CHAR | 6 | Assigned to domain | ALPHA | JV_NAME | OIU_R_JV | |
REF_BUKRS | Reference Company Code | REF_BUKRS | CHAR | 4 | Assigned to domain | BUKRS | RBU | ||
REF_WL_NO | Reference well ID number | OIU_WL_NO_REF | CHAR | 15 | Assigned to domain | ALPHA | OIU_WL_NO | OIU_R_WELL | |
REF_WC_NO | Reference well completion number | OIU_WC_NO_REF | CHAR | 5 | Assigned to domain | ALPHA | OIU_WC_NO | OIU_R_WC | |
REF_VT_CD | Reference volume type code | OIU_VL_TYPE_CD_REF | CHAR | 2 | Assigned to domain | OIU_VL_TYPE_CD | OIU_R_VL_TYPE | ||
REF_DN_DE | Delivery network description | OIU_DN_DE | CHAR | 35 | OIU_TEXT35 | ||||
REF_BUTXT | Name of Company Code or Company | BUTXT | CHAR | 25 | TEXT25 | ||||
REF_VNAME_NM | venture name | OIU_VNAME_NM | CHAR | 35 | OIU_TEXT35 | ||||
REF_WC_NM | Well name | OIU_WL_NM | CHAR | 35 | CHAR35 | ||||
REF_VL_TYPE_DE | Volume Type Description | OIU_VL_TYPE_DE | CHAR | 50 | OIU_TEXT50 | ||||
MP_DE | Measurement point description | OIU_MP_DE | CHAR | 35 | OIU_TEXT35 | OIU_MP_DE | |||
REF_MP_NO | Reference measurement point number | OIU_MP_NO_REF | CHAR | 20 | Assigned to domain | ALPHA | OIU_MP_NO | OIU_R_MP | |
REF_MP_DE | Measurement point description | OIU_MP_DE | CHAR | 35 | OIU_TEXT35 | OIU_MP_DE |
Key field | Non-key field |
How do I retrieve data from SAP structure ROIUPR_SSH using ABAP code?
As ROIUPR_SSH 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 ROIUPR_SSH as there is no data to select.How to access SAP table ROIUPR_SSH
Within an ECC or HANA version of SAP you can also view further information about ROIUPR_SSH 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