SAP Function Modules

comments icon Comments

SIC_BAS_CALL_SERVICE SAP Function module - Call services for indexing with TREX







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

Associated Function Group: SIC_BAS_ADDRESS_INDEXING
Released Date: Not Released
Processing type: Remote-Enabled
remote enabled module settings


Pattern for FM SIC_BAS_CALL_SERVICE - SIC BAS CALL SERVICE 





CALL FUNCTION 'SIC_BAS_CALL_SERVICE' "Call services for indexing with TREX
  EXPORTING
    iv_appl_object_type =       " sic_s_appl_object_type  Unique identification of application and object type
    iv_node_name =              " sic_node_name  Node name
    iv_service_name =           " sic_service_name  Name of a service
*   iv_profile =                " sic_service_profile  Service Profile
    iv_index =                  " sic_index_main-index_object  Index object for SES or Catalog for MDM
    iv_index_objecttype =       " sic_index_object_type  Type of the indexed object
    iv_use_queueserver = '  '   " trex_rfc-flag  Indicator
*   iv_destination =            " sic_index_main-destination  RFC Destination for SES or Catalog for MDM
*   iv_update_flag =            " ad_updflag    Address transfer structure change flag
    it_field_list =             " addatalist    Initial duplicate index transfer table
  IMPORTING
    et_messages =               " sic_t_service_message  Table type for structure SIC_S_SERVICE_MESSAGE
    .  "  SIC_BAS_CALL_SERVICE

ABAP code example for Function Module SIC_BAS_CALL_SERVICE





The ABAP code below is a full code listing to execute function module SIC_BAS_CALL_SERVICE 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_messages    TYPE SIC_T_SERVICE_MESSAGE
.




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

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

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

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

SELECT single INDEX_OBJECT 
  FROM SIC_INDEX_MAIN 
  INTO @DATA(ld_iv_index).


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


DATA(ld_iv_use_queueserver) = some text here
 

SELECT single DESTINATION 
  FROM SIC_INDEX_MAIN 
  INTO @DATA(ld_iv_destination).


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

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

CALL FUNCTION 'SIC_BAS_CALL_SERVICE'
  EXPORTING
    iv_appl_object_type =        ld_iv_appl_object_type
    iv_node_name =               ld_iv_node_name
    iv_service_name =            ld_iv_service_name
*   iv_profile =                 ld_iv_profile
    iv_index =                   ld_iv_index
    iv_index_objecttype =        ld_iv_index_objecttype
    iv_use_queueserver =         ld_iv_use_queueserver
*   iv_destination =             ld_iv_destination
*   iv_update_flag =             ld_iv_update_flag
    it_field_list =              ld_it_field_list
  IMPORTING
    et_messages =                ld_et_messages
    .  "  SIC_BAS_CALL_SERVICE

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_messages  TYPE SIC_T_SERVICE_MESSAGE ,
ld_iv_appl_object_type  TYPE SIC_S_APPL_OBJECT_TYPE ,
ld_iv_node_name  TYPE SIC_NODE_NAME ,
ld_iv_service_name  TYPE SIC_SERVICE_NAME ,
ld_iv_profile  TYPE SIC_SERVICE_PROFILE ,
ld_iv_index  TYPE SIC_INDEX_MAIN-INDEX_OBJECT ,
ld_iv_index_objecttype  TYPE SIC_INDEX_OBJECT_TYPE ,
ld_iv_use_queueserver  TYPE TREX_RFC-FLAG ,
ld_iv_destination  TYPE SIC_INDEX_MAIN-DESTINATION ,
ld_iv_update_flag  TYPE AD_UPDFLAG ,
ld_it_field_list  TYPE ADDATALIST .




ld_iv_appl_object_type = 'Check type of data required'.
ld_iv_node_name = 'Check type of data required'.
ld_iv_service_name = 'Check type of data required'.
ld_iv_profile = 'Check type of data required'.

SELECT single INDEX_OBJECT 
  FROM SIC_INDEX_MAIN 
  INTO ld_iv_index.

ld_iv_index_objecttype = 'Check type of data required'.

ld_iv_use_queueserver = some text here

SELECT single DESTINATION 
  FROM SIC_INDEX_MAIN 
  INTO ld_iv_destination.

ld_iv_update_flag = 'Check type of data required'.
ld_it_field_list = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name SIC_BAS_CALL_SERVICE or its description.


   
 

SIC_BAS_CALL_SERVICE - Call services for indexing with TREX
SICJIT_SAVE_SETTINGS - Save settings for a user
SICJIT_GET_SETTINGS - Get default settings for user
SICJIT_GET_DATA - Collection of data for JIT Internet scenario
SICJIT_GET_AUTHORITIES - Get JIT authorities for a vendor
SICHER_TRANS - Edits Collateral in the Overview Structure