EXIT_SAPLJK00_002 SAP Function module - Determination of Optimum Delivery Viability Set

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

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

Pattern for FM EXIT_SAPLJK00_002 - EXIT SAPLJK00 002

CALL FUNCTION 'EXIT_SAPLJK00_002' "Determination of Optimum Delivery Viability Set
  EXPORTING
    auart =                     " jkak-auart
    poart =                     " jkap-poart
    drerz =                     " jkap-drerz
    processtype =               " jkd_processtype
*   old_state =                 " jkd_fields_to_opt
    merged_nodetab =            " jkd_merged_nodetab
    addresstab =                " jkd_addresstab
  IMPORTING
    deliver_data =              " jkd_merged_node
  EXCEPTIONS
    ERROR = 1                   "
    .  "  EXIT_SAPLJK00_002

ABAP code example for Function Module EXIT_SAPLJK00_002

The ABAP code below is a full code listing to execute function module EXIT_SAPLJK00_002 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_deliver_data  
 
 TYPE JKD_MERGED_NODE
.

 

SELECT single AUART 
  FROM JKAK 
  INTO @DATA(ld_auart).

 

SELECT single POART 
  FROM JKAP 
  INTO @DATA(ld_poart).

 

SELECT single DRERZ 
  FROM JKAP 
  INTO @DATA(ld_drerz).


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

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

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

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

CALL FUNCTION 'EXIT_SAPLJK00_002'
  EXPORTING
    auart =                      ld_auart
    poart =                      ld_poart
    drerz =                      ld_drerz
    processtype =                ld_processtype
*   old_state =                  ld_old_state
    merged_nodetab =             ld_merged_nodetab
    addresstab =                 ld_addresstab
  IMPORTING
    deliver_data =               ld_deliver_data
  EXCEPTIONS
    ERROR =                      1
    .  "  EXIT_SAPLJK00_002

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "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_deliver_data
 
 TYPE JKD_MERGED_NODE ,
ld_auart
 
 TYPE JKAK-AUART ,
ld_poart
 
 TYPE JKAP-POART ,
ld_drerz
 
 TYPE JKAP-DRERZ ,
ld_processtype
 
 TYPE JKD_PROCESSTYPE ,
ld_old_state
 
 TYPE JKD_FIELDS_TO_OPT ,
ld_merged_nodetab
 
 TYPE JKD_MERGED_NODETAB ,
ld_addresstab
 
 TYPE JKD_ADDRESSTAB .



SELECT single AUART 
  FROM JKAK 
  INTO ld_auart.


SELECT single POART 
  FROM JKAP 
  INTO ld_poart.


SELECT single DRERZ 
  FROM JKAP 
  INTO ld_drerz.

ld_processtype = 'Check type of data required'.
ld_old_state = 'Check type of data required'.
ld_merged_nodetab = 'Check type of data required'.
ld_addresstab = 'Check type of data required'.