SAP OIJW_PROTOCOL Function Module for OIL-TSW: Create worklist entry
OIJW_PROTOCOL is a standard oijw protocol 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: Create worklist entry 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 oijw protocol FM, simply by entering the name OIJW_PROTOCOL into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIJW
Program Name: SAPLOIJW
Main Program: SAPLOIJW
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function OIJW_PROTOCOL 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 'OIJW_PROTOCOL'"OIL-TSW: Create worklist entry.
EXPORTING
* I_ACT = "
* I_DATUM = "
* I_MODUL = "
* I_TEXT = "
* I_RC = "
* I_WLITEM = "
* I_TSYST = "
* I_LOCID = "
* I_MATNR = "
* I_NOMTK = "
* I_NOMNR = "
* I_NOMIT = "
EXCEPTIONS
INPUT_MISSING = 1
IMPORTING Parameters details for OIJW_PROTOCOL
I_ACT -
Data type: OIJWL-WLRCOptional: Yes
Call by Reference: No ( called with pass by value option)
I_DATUM -
Data type: OIJWL-DATUMOptional: Yes
Call by Reference: No ( called with pass by value option)
I_MODUL -
Data type: TFDIR-FUNCNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_TEXT -
Data type: OIJERRLOG-MSGV1Optional: Yes
Call by Reference: No ( called with pass by value option)
I_RC -
Data type: OIJWL-WLRCOptional: Yes
Call by Reference: No ( called with pass by value option)
I_WLITEM -
Data type: OIJWL-WLITEMOptional: Yes
Call by Reference: No ( called with pass by value option)
I_TSYST -
Data type: OIJWL-TSYSTOptional: Yes
Call by Reference: No ( called with pass by value option)
I_LOCID -
Data type: OIJWL-LOCIDOptional: Yes
Call by Reference: No ( called with pass by value option)
I_MATNR -
Data type: OIJWL-MATNROptional: Yes
Call by Reference: No ( called with pass by value option)
I_NOMTK -
Data type: OIJWL-NOMTKOptional: Yes
Call by Reference: No ( called with pass by value option)
I_NOMNR -
Data type: OIJWL-NOMNROptional: Yes
Call by Reference: No ( called with pass by value option)
I_NOMIT -
Data type: OIJWL-NOMITOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
INPUT_MISSING -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for OIJW_PROTOCOL 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_act | TYPE OIJWL-WLRC, " | |||
| lv_input_missing | TYPE OIJWL, " | |||
| lv_i_datum | TYPE OIJWL-DATUM, " | |||
| lv_i_modul | TYPE TFDIR-FUNCNAME, " | |||
| lv_i_text | TYPE OIJERRLOG-MSGV1, " | |||
| lv_i_rc | TYPE OIJWL-WLRC, " | |||
| lv_i_wlitem | TYPE OIJWL-WLITEM, " | |||
| lv_i_tsyst | TYPE OIJWL-TSYST, " | |||
| lv_i_locid | TYPE OIJWL-LOCID, " | |||
| lv_i_matnr | TYPE OIJWL-MATNR, " | |||
| lv_i_nomtk | TYPE OIJWL-NOMTK, " | |||
| lv_i_nomnr | TYPE OIJWL-NOMNR, " | |||
| lv_i_nomit | TYPE OIJWL-NOMIT. " |
| CALL FUNCTION 'OIJW_PROTOCOL' "OIL-TSW: Create worklist entry |
| EXPORTING | ||
| I_ACT | = lv_i_act | |
| I_DATUM | = lv_i_datum | |
| I_MODUL | = lv_i_modul | |
| I_TEXT | = lv_i_text | |
| I_RC | = lv_i_rc | |
| I_WLITEM | = lv_i_wlitem | |
| I_TSYST | = lv_i_tsyst | |
| I_LOCID | = lv_i_locid | |
| I_MATNR | = lv_i_matnr | |
| I_NOMTK | = lv_i_nomtk | |
| I_NOMNR | = lv_i_nomnr | |
| I_NOMIT | = lv_i_nomit | |
| EXCEPTIONS | ||
| INPUT_MISSING = 1 | ||
| . " OIJW_PROTOCOL | ||
ABAP code using 7.40 inline data declarations to call FM OIJW_PROTOCOL
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 WLRC FROM OIJWL INTO @DATA(ld_i_act). | ||||
| "SELECT single DATUM FROM OIJWL INTO @DATA(ld_i_datum). | ||||
| "SELECT single FUNCNAME FROM TFDIR INTO @DATA(ld_i_modul). | ||||
| "SELECT single MSGV1 FROM OIJERRLOG INTO @DATA(ld_i_text). | ||||
| "SELECT single WLRC FROM OIJWL INTO @DATA(ld_i_rc). | ||||
| "SELECT single WLITEM FROM OIJWL INTO @DATA(ld_i_wlitem). | ||||
| "SELECT single TSYST FROM OIJWL INTO @DATA(ld_i_tsyst). | ||||
| "SELECT single LOCID FROM OIJWL INTO @DATA(ld_i_locid). | ||||
| "SELECT single MATNR FROM OIJWL INTO @DATA(ld_i_matnr). | ||||
| "SELECT single NOMTK FROM OIJWL INTO @DATA(ld_i_nomtk). | ||||
| "SELECT single NOMNR FROM OIJWL INTO @DATA(ld_i_nomnr). | ||||
| "SELECT single NOMIT FROM OIJWL INTO @DATA(ld_i_nomit). | ||||
Search for further information about these or an SAP related objects