FSBP_FSCAA_OBJ_ST2RANGE_CONV SAP Function module

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

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

Pattern for FM FSBP_FSCAA_OBJ_ST2RANGE_CONV - FSBP FSCAA OBJ ST2RANGE CONV

CALL FUNCTION 'FSBP_FSCAA_OBJ_ST2RANGE_CONV' "
* EXPORTING
*   iv_partner_category =       " bu_type
*   iv_partner_role =           " bu_role
*   is_central_data =           " bapibus1006_central_search
*   is_address_data =           " bapibus1006_addr_search
*   is_other_search_data =      " fsbp_fscaa_str_search_data
  IMPORTING
    et_search_ranges =          " bussrch_selopt_t
    .  "  FSBP_FSCAA_OBJ_ST2RANGE_CONV

ABAP code example for Function Module FSBP_FSCAA_OBJ_ST2RANGE_CONV

The ABAP code below is a full code listing to execute function module FSBP_FSCAA_OBJ_ST2RANGE_CONV 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_et_search_ranges  
 
 TYPE BUSSRCH_SELOPT_T
.


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

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

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

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

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

CALL FUNCTION 'FSBP_FSCAA_OBJ_ST2RANGE_CONV'
* EXPORTING
*   iv_partner_category =        ld_iv_partner_category
*   iv_partner_role =            ld_iv_partner_role
*   is_central_data =            ld_is_central_data
*   is_address_data =            ld_is_address_data
*   is_other_search_data =       ld_is_other_search_data
  IMPORTING
    et_search_ranges =           ld_et_search_ranges
    .  "  FSBP_FSCAA_OBJ_ST2RANGE_CONV

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_et_search_ranges
 
 TYPE BUSSRCH_SELOPT_T ,
ld_iv_partner_category
 
 TYPE BU_TYPE ,
ld_iv_partner_role
 
 TYPE BU_ROLE ,
ld_is_central_data
 
 TYPE BAPIBUS1006_CENTRAL_SEARCH ,
ld_is_address_data
 
 TYPE BAPIBUS1006_ADDR_SEARCH ,
ld_is_other_search_data
 
 TYPE FSBP_FSCAA_STR_SEARCH_DATA .


ld_iv_partner_category = 'Check type of data required'.
ld_iv_partner_role = 'Check type of data required'.
ld_is_central_data = 'Check type of data required'.
ld_is_address_data = 'Check type of data required'.
ld_is_other_search_data = 'Check type of data required'.