EXIT_SAPLLOI1_003 SAP Function module - User exit for current stock/requirements lists

EXIT_SAPLLOI1_003 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 EXIT_SAPLLOI1_003 into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM EXIT_SAPLLOI1_003 - EXIT SAPLLOI1 003

CALL FUNCTION 'EXIT_SAPLLOI1_003' "User exit for current stock/requirements lists
  EXPORTING
    message_type =              " edmsg-msgtyp
    segment_name =              " edidd-segnam
*   f_mdst =                    " e3mdstl
*   f_plse =                    " e3plsel
*   f_mdps =                    " e3mdpsl
  IMPORTING
    idoc_cimtype =              " edidc-cimtyp
  TABLES
    idoc_data =                 " edidd
    .  "  EXIT_SAPLLOI1_003

ABAP code example for Function Module EXIT_SAPLLOI1_003

The ABAP code below is a full code listing to execute function module EXIT_SAPLLOI1_003 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_idoc_cimtype  
 
 TYPE EDIDC-CIMTYP
,
it_idoc_data  
 
 TYPE STANDARD TABLE OF EDIDD,"TABLES PARAM
wa_idoc_data
 
 LIKE LINE OF it_idoc_data
.

 

SELECT single MSGTYP 
  FROM EDMSG 
  INTO @DATA(ld_message_type).



DATA(ld_segment_name) = some text here

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

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

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

"populate fields of struture and append to itab
append wa_idoc_data to it_idoc_data.
.

CALL FUNCTION 'EXIT_SAPLLOI1_003'
  EXPORTING
    message_type =               ld_message_type
    segment_name =               ld_segment_name
*   f_mdst =                     ld_f_mdst
*   f_plse =                     ld_f_plse
*   f_mdps =                     ld_f_mdps
  IMPORTING
    idoc_cimtype =               ld_idoc_cimtype
  TABLES
    idoc_data =                  it_idoc_data
    .  "  EXIT_SAPLLOI1_003

IF SY-SUBRC EQ 0.
  "All OK
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_idoc_cimtype
 
 TYPE EDIDC-CIMTYP ,
ld_message_type
 
 TYPE EDMSG-MSGTYP ,
it_idoc_data
 
 TYPE STANDARD TABLE OF EDIDD ,
wa_idoc_data
 
 LIKE LINE OF it_idoc_data,
ld_segment_name
 
 TYPE EDIDD-SEGNAM ,
ld_f_mdst
 
 TYPE E3MDSTL ,
ld_f_plse
 
 TYPE E3PLSEL ,
ld_f_mdps
 
 TYPE E3MDPSL .



SELECT single MSGTYP 
  FROM EDMSG 
  INTO ld_message_type.
 

"populate fields of struture and append to itab
append wa_idoc_data to it_idoc_data.

ld_segment_name = some text here
ld_f_mdst = 'Check type of data required'.
ld_f_plse = 'Check type of data required'.
ld_f_mdps = 'Check type of data required'.