OIJW_CREATE_WL_ENTRY SAP Function module - OIL-TSW: Create worklist entry

OIJW_CREATE_WL_ENTRY is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name OIJW_CREATE_WL_ENTRY into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: OIJW
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM OIJW_CREATE_WL_ENTRY - OIJW CREATE WL ENTRY

CALL FUNCTION 'OIJW_CREATE_WL_ENTRY' "OIL-TSW: Create worklist entry
  EXPORTING
    t_oijwl =                   " oijwl
*   g_print =                   " oijrd-worklist
  IMPORTING
    e_wlitem =                  " oijwl-wlitem
  EXCEPTIONS
    INPUT_MISSING = 1           "
    DB_ACCESS_ERROR = 2         "
    ENTRY_EXISTS = 3            "
    INTERVAL_NOT_FOUND = 4      "
    NUMBER_RANGE_PROBLEM = 5    "
    .  "  OIJW_CREATE_WL_ENTRY

ABAP code example for Function Module OIJW_CREATE_WL_ENTRY

The ABAP code below is a full code listing to execute function module OIJW_CREATE_WL_ENTRY including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_e_wlitem  
 
 TYPE OIJWL-WLITEM
.


DATA(ld_t_oijwl) = 'Check type of data required'.
 

SELECT single WORKLIST 
  FROM OIJRD 
  INTO @DATA(ld_g_print).

.

CALL FUNCTION 'OIJW_CREATE_WL_ENTRY'
  EXPORTING
    t_oijwl =                    ld_t_oijwl
*   g_print =                    ld_g_print
  IMPORTING
    e_wlitem =                   ld_e_wlitem
  EXCEPTIONS
    INPUT_MISSING =              1
    DB_ACCESS_ERROR =            2
    ENTRY_EXISTS =               3
    INTERVAL_NOT_FOUND =         4
    NUMBER_RANGE_PROBLEM =       5
    .  "  OIJW_CREATE_WL_ENTRY

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 5. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_e_wlitem
 
 TYPE OIJWL-WLITEM ,
ld_t_oijwl
 
 TYPE OIJWL ,
ld_g_print
 
 TYPE OIJRD-WORKLIST .


ld_t_oijwl = 'Check type of data required'.

SELECT single WORKLIST 
  FROM OIJRD 
  INTO ld_g_print.