SAP OIJ_FILL_IREF_FOR_SPWOBJECT Function Module for Fill internal OIJ_EL_DOC_I_REF for an SPW object & date range
OIJ_FILL_IREF_FOR_SPWOBJECT is a standard oij fill iref for spwobject SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Fill internal OIJ_EL_DOC_I_REF for an SPW object & date range 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 oij fill iref for spwobject FM, simply by entering the name OIJ_FILL_IREF_FOR_SPWOBJECT into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIJ_EL_B
Program Name: SAPLOIJ_EL_B
Main Program: SAPLOIJ_EL_B
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OIJ_FILL_IREF_FOR_SPWOBJECT 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 'OIJ_FILL_IREF_FOR_SPWOBJECT'"Fill internal OIJ_EL_DOC_I_REF for an SPW object & date range.
EXPORTING
I_LOCID = "Location ID
* I_TSYST = "Transport system
I_MATNR = "Material Number
* I_CHARG = "Batch / Valuation type
PI_RD_ITEM_DATE_LO = "Date and Time, Current (Application Server) Date
PI_RD_ITEM_DATE_HI = "Date and Time, Current (Application Server) Date
* IV_BYPASSING_BUFFER = "boolean variable (X=true, -=false, space=unknown)
* IV_REFRESH_BUFFER = "boolean variable (X=true, -=false, space=unknown)
TABLES
* IT_VBTYP_SEL = "Selection structure for OIJ_EL_VBTYP
ET_OIJ_EL_DOC_I_REF = "Document item reference to nomination
EXCEPTIONS
NO_ENTRY_FOUND = 1 WRONG_INPUT = 2
IMPORTING Parameters details for OIJ_FILL_IREF_FOR_SPWOBJECT
I_LOCID - Location ID
Data type: OIJ_LOCIDOptional: No
Call by Reference: Yes
I_TSYST - Transport system
Data type: OIJ_TSYSTOptional: Yes
Call by Reference: Yes
I_MATNR - Material Number
Data type: MATNROptional: No
Call by Reference: Yes
I_CHARG - Batch / Valuation type
Data type: OIJ_CHARGOptional: Yes
Call by Reference: Yes
PI_RD_ITEM_DATE_LO - Date and Time, Current (Application Server) Date
Data type: SY-DATUMOptional: No
Call by Reference: Yes
PI_RD_ITEM_DATE_HI - Date and Time, Current (Application Server) Date
Data type: SY-DATUMOptional: No
Call by Reference: Yes
IV_BYPASSING_BUFFER - boolean variable (X=true, -=false, space=unknown)
Data type: BOOLEANOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_REFRESH_BUFFER - boolean variable (X=true, -=false, space=unknown)
Data type: BOOLEANOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for OIJ_FILL_IREF_FOR_SPWOBJECT
IT_VBTYP_SEL - Selection structure for OIJ_EL_VBTYP
Data type: ROIJ_VBTYP_SELOptional: Yes
Call by Reference: Yes
ET_OIJ_EL_DOC_I_REF - Document item reference to nomination
Data type: OIJ_EL_DOC_I_REFOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_ENTRY_FOUND - No entry found
Data type:Optional: No
Call by Reference: Yes
WRONG_INPUT - Wrong input
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for OIJ_FILL_IREF_FOR_SPWOBJECT 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 OIJ_LOCID, " | |||
| lt_it_vbtyp_sel | TYPE STANDARD TABLE OF ROIJ_VBTYP_SEL, " | |||
| lv_no_entry_found | TYPE ROIJ_VBTYP_SEL, " | |||
| lv_i_tsyst | TYPE OIJ_TSYST, " | |||
| lv_wrong_input | TYPE OIJ_TSYST, " | |||
| lt_et_oij_el_doc_i_ref | TYPE STANDARD TABLE OF OIJ_EL_DOC_I_REF, " | |||
| lv_i_matnr | TYPE MATNR, " | |||
| lv_i_charg | TYPE OIJ_CHARG, " | |||
| lv_pi_rd_item_date_lo | TYPE SY-DATUM, " | |||
| lv_pi_rd_item_date_hi | TYPE SY-DATUM, " | |||
| lv_iv_bypassing_buffer | TYPE BOOLEAN, " | |||
| lv_iv_refresh_buffer | TYPE BOOLEAN. " |
|   CALL FUNCTION 'OIJ_FILL_IREF_FOR_SPWOBJECT' "Fill internal OIJ_EL_DOC_I_REF for an SPW object & date range |
| EXPORTING | ||
| I_LOCID | = lv_i_locid | |
| I_TSYST | = lv_i_tsyst | |
| I_MATNR | = lv_i_matnr | |
| I_CHARG | = lv_i_charg | |
| PI_RD_ITEM_DATE_LO | = lv_pi_rd_item_date_lo | |
| PI_RD_ITEM_DATE_HI | = lv_pi_rd_item_date_hi | |
| IV_BYPASSING_BUFFER | = lv_iv_bypassing_buffer | |
| IV_REFRESH_BUFFER | = lv_iv_refresh_buffer | |
| TABLES | ||
| IT_VBTYP_SEL | = lt_it_vbtyp_sel | |
| ET_OIJ_EL_DOC_I_REF | = lt_et_oij_el_doc_i_ref | |
| EXCEPTIONS | ||
| NO_ENTRY_FOUND = 1 | ||
| WRONG_INPUT = 2 | ||
| . " OIJ_FILL_IREF_FOR_SPWOBJECT | ||
ABAP code using 7.40 inline data declarations to call FM OIJ_FILL_IREF_FOR_SPWOBJECT
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_pi_rd_item_date_lo). | ||||
| "SELECT single DATUM FROM SY INTO @DATA(ld_pi_rd_item_date_hi). | ||||
Search for further information about these or an SAP related objects