LXYRD_MOVE_LOCATIONS_GET SAP Function module - Get possible locations for movement activities

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

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

Pattern for FM LXYRD_MOVE_LOCATIONS_GET - LXYRD MOVE LOCATIONS GET

CALL FUNCTION 'LXYRD_MOVE_LOCATIONS_GET' "Get possible locations for movement activities
  EXPORTING
    iv_lyard =                  " lxyrd_yard    Yard
*   iv_ylccl =                  " lxyrd_ylccl   Location Class
*   iv_no_message =             " flag          General Flag
    ir_vhart =                  " lxhme_range_c4_t  Table type of a Range for a (4) Character Field
    it_lyact =                  " lyact_t       Activities
    it_hu_header =              " leint_yhu_header_t  HU table for Yard Management
  CHANGING
    ct_lyloc =                  " lyloc_t       Yard locations table
  EXCEPTIONS
    SERVICE_CANCEL = 1          "
    .  "  LXYRD_MOVE_LOCATIONS_GET

ABAP code example for Function Module LXYRD_MOVE_LOCATIONS_GET

The ABAP code below is a full code listing to execute function module LXYRD_MOVE_LOCATIONS_GET 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_ct_lyloc) = 'Check type of data required'.

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

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

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

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

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

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

CALL FUNCTION 'LXYRD_MOVE_LOCATIONS_GET'
  EXPORTING
    iv_lyard =                   ld_iv_lyard
*   iv_ylccl =                   ld_iv_ylccl
*   iv_no_message =              ld_iv_no_message
    ir_vhart =                   ld_ir_vhart
    it_lyact =                   ld_it_lyact
    it_hu_header =               ld_it_hu_header
  CHANGING
    ct_lyloc =                   ld_ct_lyloc
  EXCEPTIONS
    SERVICE_CANCEL =             1
    .  "  LXYRD_MOVE_LOCATIONS_GET

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_ct_lyloc
 
 TYPE LYLOC_T ,
ld_iv_lyard
 
 TYPE LXYRD_YARD ,
ld_iv_ylccl
 
 TYPE LXYRD_YLCCL ,
ld_iv_no_message
 
 TYPE FLAG ,
ld_ir_vhart
 
 TYPE LXHME_RANGE_C4_T ,
ld_it_lyact
 
 TYPE LYACT_T ,
ld_it_hu_header
 
 TYPE LEINT_YHU_HEADER_T .


ld_ct_lyloc = 'Check type of data required'.
ld_iv_lyard = 'Check type of data required'.
ld_iv_ylccl = 'Check type of data required'.
ld_iv_no_message = 'Check type of data required'.
ld_ir_vhart = 'Check type of data required'.
ld_it_lyact = 'Check type of data required'.
ld_it_hu_header = 'Check type of data required'.