ISM_TMC_HH_FOR_STRUCTURE_GET SAP Function module

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

Associated Function Group: JVTMC_STRUCTURE
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM ISM_TMC_HH_FOR_STRUCTURE_GET - ISM TMC HH FOR STRUCTURE GET

CALL FUNCTION 'ISM_TMC_HH_FOR_STRUCTURE_GET' "
  EXPORTING
    in_knoten =                 " rjs0102-knoten1
    in_knotenart =              " rjs0102-knotenart1
    datum = SY-DATUM            " sy-datum
    in_land =                   " rjs0102-land1
  IMPORTING
    rfcsi_export =              " rfcsi
  TABLES
    hh_address =                " jvtmc_hh_adr
  EXCEPTIONS
    NO_HH_ADDRESSES_FOUND = 1   "
    NO_ADDRESSES_FOUND = 2      "
    INTERNAL_ERROR = 3          "
    WRONG_BADI_FILTER_OP_APPLIED = 4  "
    .  "  ISM_TMC_HH_FOR_STRUCTURE_GET

ABAP code example for Function Module ISM_TMC_HH_FOR_STRUCTURE_GET

The ABAP code below is a full code listing to execute function module ISM_TMC_HH_FOR_STRUCTURE_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_rfcsi_export  
 
 TYPE RFCSI
,
it_hh_address  
 
 TYPE STANDARD TABLE OF JVTMC_HH_ADR,"TABLES PARAM
wa_hh_address
 
 LIKE LINE OF it_hh_address
.



DATA(ld_in_knoten) = some text here


DATA(ld_in_knotenart) = some text here

DATA(ld_datum) = '20210129'.


DATA(ld_in_land) = some text here
 

"populate fields of struture and append to itab
append wa_hh_address to it_hh_address.
.

CALL FUNCTION 'ISM_TMC_HH_FOR_STRUCTURE_GET'
  EXPORTING
    in_knoten =                  ld_in_knoten
    in_knotenart =               ld_in_knotenart
    datum =                      ld_datum
    in_land =                    ld_in_land
  IMPORTING
    rfcsi_export =               ld_rfcsi_export
  TABLES
    hh_address =                 it_hh_address
  EXCEPTIONS
    NO_HH_ADDRESSES_FOUND =      1
    NO_ADDRESSES_FOUND =         2
    INTERNAL_ERROR =             3
    WRONG_BADI_FILTER_OP_APPLIED =    4
    .  "  ISM_TMC_HH_FOR_STRUCTURE_GET

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
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_rfcsi_export
 
 TYPE RFCSI ,
ld_in_knoten
 
 TYPE RJS0102-KNOTEN1 ,
it_hh_address
 
 TYPE STANDARD TABLE OF JVTMC_HH_ADR ,
wa_hh_address
 
 LIKE LINE OF it_hh_address,
ld_in_knotenart
 
 TYPE RJS0102-KNOTENART1 ,
ld_datum
 
 TYPE SY-DATUM ,
ld_in_land
 
 TYPE RJS0102-LAND1 .



ld_in_knoten = some text here 

"populate fields of struture and append to itab
append wa_hh_address to it_hh_address.

ld_in_knotenart = some text here
ld_datum = '20210129'.

ld_in_land = some text here