SAP OIJU_READ_OIJRDNOM Function Module for Read OIJRDNOM / buffered









OIJU_READ_OIJRDNOM is a standard oiju read oijrdnom SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read OIJRDNOM / buffered 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 oijrdnom FM, simply by entering the name OIJU_READ_OIJRDNOM 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): Normal Function Module
Update:



Function OIJU_READ_OIJRDNOM 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_OIJRDNOM'"Read OIJRDNOM / buffered
EXPORTING
* IV_LOCID = "Location ID
* IV_TSYST = "Transport system
IV_MATNR = "Material number
IV_DATE = "Date and time, current (application server) date
* IV_DATE_HI = "Date and time, current (application server) date
* IV_NOMTK = "Nomination (technical) Key
* IV_BYPASS_BUFFER = "Single-character flag

TABLES
CT_OIJRDNOM = "OIL-TSW: Rundown item / nomination X-ref table

EXCEPTIONS
NO_ENTRY_FOUND = 1
.




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_OIJRDNOM

IV_LOCID - Location ID

Data type: OIJ_LOCID
Optional: Yes
Call by Reference: Yes

IV_TSYST - Transport system

Data type: OIJ_TSYST
Optional: Yes
Call by Reference: Yes

IV_MATNR - Material number

Data type: MATNR
Optional: No
Call by Reference: Yes

IV_DATE - Date and time, current (application server) date

Data type: SY-DATUM
Optional: No
Call by Reference: Yes

IV_DATE_HI - Date and time, current (application server) date

Data type: SY-DATUM
Optional: Yes
Call by Reference: Yes

IV_NOMTK - Nomination (technical) Key

Data type: OIJ_NOMTK
Optional: Yes
Call by Reference: Yes

IV_BYPASS_BUFFER - Single-character flag

Data type: CHAR1
Optional: Yes
Call by Reference: Yes

TABLES Parameters details for OIJU_READ_OIJRDNOM

CT_OIJRDNOM - OIL-TSW: Rundown item / nomination X-ref table

Data type: OIJRDNOM
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NO_ENTRY_FOUND - No entry found

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for OIJU_READ_OIJRDNOM 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_iv_locid  TYPE OIJ_LOCID, "   
lt_ct_oijrdnom  TYPE STANDARD TABLE OF OIJRDNOM, "   
lv_no_entry_found  TYPE OIJRDNOM, "   
lv_iv_tsyst  TYPE OIJ_TSYST, "   
lv_iv_matnr  TYPE MATNR, "   
lv_iv_date  TYPE SY-DATUM, "   
lv_iv_date_hi  TYPE SY-DATUM, "   
lv_iv_nomtk  TYPE OIJ_NOMTK, "   
lv_iv_bypass_buffer  TYPE CHAR1. "   

  CALL FUNCTION 'OIJU_READ_OIJRDNOM'  "Read OIJRDNOM / buffered
    EXPORTING
         IV_LOCID = lv_iv_locid
         IV_TSYST = lv_iv_tsyst
         IV_MATNR = lv_iv_matnr
         IV_DATE = lv_iv_date
         IV_DATE_HI = lv_iv_date_hi
         IV_NOMTK = lv_iv_nomtk
         IV_BYPASS_BUFFER = lv_iv_bypass_buffer
    TABLES
         CT_OIJRDNOM = lt_ct_oijrdnom
    EXCEPTIONS
        NO_ENTRY_FOUND = 1
. " OIJU_READ_OIJRDNOM




ABAP code using 7.40 inline data declarations to call FM OIJU_READ_OIJRDNOM

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 DATUM FROM SY INTO @DATA(ld_iv_date).
 
"SELECT single DATUM FROM SY INTO @DATA(ld_iv_date_hi).
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!