SAP OIJU_READ_RDHEAD Function Module for OIL-TSW: Read Rundown header
OIJU_READ_RDHEAD is a standard oiju read rdhead SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for OIL-TSW: Read Rundown header processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for oiju read rdhead FM, simply by entering the name OIJU_READ_RDHEAD into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIJU
Program Name: SAPLOIJU
Main Program: SAPLOIJU
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:
![](https://www.se80.co.uk/training-education/wp-content/uploads/2019/07/normal-function-module.png)
Function OIJU_READ_RDHEAD pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'OIJU_READ_RDHEAD'"OIL-TSW: Read Rundown header.
EXPORTING
I_LOCID = "Location ID
I_TSYST = "Transport system
I_MATNR = "Material number
* I_CHARG = "Batch / Valuation type
* I_SOCNR = "Tank
I_SPTYPE = "Stock Projection type
IMPORTING
T_OIJ_RDHEAD = "OIL TSW : Stock Projection header shadow table
EXCEPTIONS
LOCID_AND_TSYST_INITIAL = 1 MATERIAL_INITIAL = 2 SPTYPE_INITIAL = 3 NO_ENTRY_FOUND = 4
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLOIJU_001 OIL-TSW: Customer exit for editing rundown plant book inventory
EXIT_SAPLOIJU_002 OIL-TSW: Customer exit for editing rundown plant SOP data
EXIT_SAPLOIJU_003 OIL-TSW: Customer exit for editing rundown plant statistical movement data
IMPORTING Parameters details for OIJU_READ_RDHEAD
I_LOCID - Location ID
Data type: OIJLOC-LOCIDOptional: No
Call by Reference: No ( called with pass by value option)
I_TSYST - Transport system
Data type: OIJTS-TSYSTOptional: No
Call by Reference: No ( called with pass by value option)
I_MATNR - Material number
Data type: OIJRD-MATNROptional: No
Call by Reference: No ( called with pass by value option)
I_CHARG - Batch / Valuation type
Data type: OIJ_RDHEAD-CHARGOptional: Yes
Call by Reference: No ( called with pass by value option)
I_SOCNR - Tank
Data type: OIJ_RDHEAD-SOCNROptional: Yes
Call by Reference: No ( called with pass by value option)
I_SPTYPE - Stock Projection type
Data type: OIJ_RDHEAD-SPTYPEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for OIJU_READ_RDHEAD
T_OIJ_RDHEAD - OIL TSW : Stock Projection header shadow table
Data type: OIJ_RDHEADOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
LOCID_AND_TSYST_INITIAL - Both Location and Transport System are Blank
Data type:Optional: No
Call by Reference: Yes
MATERIAL_INITIAL - Material is Blank
Data type:Optional: No
Call by Reference: Yes
SPTYPE_INITIAL - Stock Projection type is Blank
Data type:Optional: No
Call by Reference: Yes
NO_ENTRY_FOUND - No Entry Found
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for OIJU_READ_RDHEAD Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.DATA: | ||||
lv_i_locid | TYPE OIJLOC-LOCID, " | |||
lv_t_oij_rdhead | TYPE OIJ_RDHEAD, " | |||
lv_locid_and_tsyst_initial | TYPE OIJ_RDHEAD, " | |||
lv_i_tsyst | TYPE OIJTS-TSYST, " | |||
lv_material_initial | TYPE OIJTS, " | |||
lv_i_matnr | TYPE OIJRD-MATNR, " | |||
lv_sptype_initial | TYPE OIJRD, " | |||
lv_i_charg | TYPE OIJ_RDHEAD-CHARG, " | |||
lv_no_entry_found | TYPE OIJ_RDHEAD, " | |||
lv_i_socnr | TYPE OIJ_RDHEAD-SOCNR, " | |||
lv_i_sptype | TYPE OIJ_RDHEAD-SPTYPE. " |
  CALL FUNCTION 'OIJU_READ_RDHEAD' "OIL-TSW: Read Rundown header |
EXPORTING | ||
I_LOCID | = lv_i_locid | |
I_TSYST | = lv_i_tsyst | |
I_MATNR | = lv_i_matnr | |
I_CHARG | = lv_i_charg | |
I_SOCNR | = lv_i_socnr | |
I_SPTYPE | = lv_i_sptype | |
IMPORTING | ||
T_OIJ_RDHEAD | = lv_t_oij_rdhead | |
EXCEPTIONS | ||
LOCID_AND_TSYST_INITIAL = 1 | ||
MATERIAL_INITIAL = 2 | ||
SPTYPE_INITIAL = 3 | ||
NO_ENTRY_FOUND = 4 | ||
. " OIJU_READ_RDHEAD |
ABAP code using 7.40 inline data declarations to call FM OIJU_READ_RDHEAD
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8."SELECT single LOCID FROM OIJLOC INTO @DATA(ld_i_locid). | ||||
"SELECT single TSYST FROM OIJTS INTO @DATA(ld_i_tsyst). | ||||
"SELECT single MATNR FROM OIJRD INTO @DATA(ld_i_matnr). | ||||
"SELECT single CHARG FROM OIJ_RDHEAD INTO @DATA(ld_i_charg). | ||||
"SELECT single SOCNR FROM OIJ_RDHEAD INTO @DATA(ld_i_socnr). | ||||
"SELECT single SPTYPE FROM OIJ_RDHEAD INTO @DATA(ld_i_sptype). | ||||
Search for further information about these or an SAP related objects