ISM_PD_STREET_LOOKUP SAP Function module - Find Cons. Street in SAP Street Table JSTSTRPRO

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

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

Pattern for FM ISM_PD_STREET_LOOKUP - ISM PD STREET LOOKUP

CALL FUNCTION 'ISM_PD_STREET_LOOKUP' "Find Cons. Street in SAP Street Table JSTSTRPRO
  EXPORTING
    lookup_jst_str_cons =       " jst_str_cons  IS-M: Table for Street Consolidation
    lookup_valid_from = SY-DATUM  " gueltigvon  Valid From Date
    lookup_valid_to = '99991231'  " gueltigbis  Valid to Date
*   x_regard_manstr =           " xfeld
  IMPORTING
    found_jststrpro =           " jststrpro     IS-M/SD: Street File (Post)
    lt_str_sap =                " jststrprotab
    lt_messages =               " rjmsg_tab     IS-M/SD: Table - Transfer of Error Messages
    .  "  ISM_PD_STREET_LOOKUP

ABAP code example for Function Module ISM_PD_STREET_LOOKUP

The ABAP code below is a full code listing to execute function module ISM_PD_STREET_LOOKUP 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_found_jststrpro  
 
 TYPE JSTSTRPRO
,
ld_lt_str_sap  
 
 TYPE JSTSTRPROTAB
,
ld_lt_messages  
 
 TYPE RJMSG_TAB
.


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

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

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

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

CALL FUNCTION 'ISM_PD_STREET_LOOKUP'
  EXPORTING
    lookup_jst_str_cons =        ld_lookup_jst_str_cons
    lookup_valid_from =          ld_lookup_valid_from
    lookup_valid_to =            ld_lookup_valid_to
*   x_regard_manstr =            ld_x_regard_manstr
  IMPORTING
    found_jststrpro =            ld_found_jststrpro
    lt_str_sap =                 ld_lt_str_sap
    lt_messages =                ld_lt_messages
    .  "  ISM_PD_STREET_LOOKUP

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_found_jststrpro
 
 TYPE JSTSTRPRO ,
ld_lookup_jst_str_cons
 
 TYPE JST_STR_CONS ,
ld_lt_str_sap
 
 TYPE JSTSTRPROTAB ,
ld_lookup_valid_from
 
 TYPE GUELTIGVON ,
ld_lt_messages
 
 TYPE RJMSG_TAB ,
ld_lookup_valid_to
 
 TYPE GUELTIGBIS ,
ld_x_regard_manstr
 
 TYPE XFELD .


ld_lookup_jst_str_cons = 'Check type of data required'.
ld_lookup_valid_from = 'Check type of data required'.
ld_lookup_valid_to = 'Check type of data required'.
ld_x_regard_manstr = 'Check type of data required'.