SAP Function Modules

ISU_GET_CLUSTER SAP Function module







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

Associated Function Group: ECDEREG01
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM ISU_GET_CLUSTER - ISU GET CLUSTER





CALL FUNCTION 'ISU_GET_CLUSTER' "
  EXPORTING
    x_keydate =                 " sy-datum
*   x_contract =                " ever-vertrag
*   x_instln =                  " eanl-anlage
*   x_premises =                " evbs-vstelle
*   x_division =                " ever-sparte
*   x_own_supply_id =           " c
  IMPORTING
    y_distributor =             " isudr_sprov_contract
    yt_suppliers =              " isudr_sprov_contract_tab
    y_premises =                " evbs-vstelle
    y_division =                " ever-sparte
    y_account =                 " fkkvkp1-vkont
    y_partner =                 " ekun_ext-partner
    y_account_data =            " fkkvkp1
    y_partner_data =            " ekun_ext
    y_partner_name =            " c
    y_service_addr_lines =      " eadrln
    y_service_addr_data =       " eadrdat
    y_service_addr_isudata =    " isu_reg0
    y_int_ui =                  " euitrans-int_ui
    y_own_supply_id =           " c
  EXCEPTIONS
    NOT_FOUND = 1               "
    INVALID_PARAMETERS = 2      "
    INVALID_SUPPLY_ID = 3       "
    .  "  ISU_GET_CLUSTER

ABAP code example for Function Module ISU_GET_CLUSTER





The ABAP code below is a full code listing to execute function module ISU_GET_CLUSTER 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_y_distributor  TYPE ISUDR_SPROV_CONTRACT ,
ld_yt_suppliers  TYPE ISUDR_SPROV_CONTRACT_TAB ,
ld_y_premises  TYPE EVBS-VSTELLE ,
ld_y_division  TYPE EVER-SPARTE ,
ld_y_account  TYPE FKKVKP1-VKONT ,
ld_y_partner  TYPE EKUN_EXT-PARTNER ,
ld_y_account_data  TYPE FKKVKP1 ,
ld_y_partner_data  TYPE EKUN_EXT ,
ld_y_partner_name  TYPE C ,
ld_y_service_addr_lines  TYPE EADRLN ,
ld_y_service_addr_data  TYPE EADRDAT ,
ld_y_service_addr_isudata  TYPE ISU_REG0 ,
ld_y_int_ui  TYPE EUITRANS-INT_UI ,
ld_y_own_supply_id  TYPE C .

DATA(ld_x_keydate) = '20210129'.

SELECT single VERTRAG
FROM EVER
INTO @DATA(ld_x_contract).


SELECT single ANLAGE
FROM EANL
INTO @DATA(ld_x_instln).


SELECT single VSTELLE
FROM EVBS
INTO @DATA(ld_x_premises).


SELECT single SPARTE
FROM EVER
INTO @DATA(ld_x_division).

DATA(ld_x_own_supply_id) = '20210129'. . CALL FUNCTION 'ISU_GET_CLUSTER' EXPORTING x_keydate = ld_x_keydate * x_contract = ld_x_contract * x_instln = ld_x_instln * x_premises = ld_x_premises * x_division = ld_x_division * x_own_supply_id = ld_x_own_supply_id IMPORTING y_distributor = ld_y_distributor yt_suppliers = ld_yt_suppliers y_premises = ld_y_premises y_division = ld_y_division y_account = ld_y_account y_partner = ld_y_partner y_account_data = ld_y_account_data y_partner_data = ld_y_partner_data y_partner_name = ld_y_partner_name y_service_addr_lines = ld_y_service_addr_lines y_service_addr_data = ld_y_service_addr_data y_service_addr_isudata = ld_y_service_addr_isudata y_int_ui = ld_y_int_ui y_own_supply_id = ld_y_own_supply_id EXCEPTIONS NOT_FOUND = 1 INVALID_PARAMETERS = 2 INVALID_SUPPLY_ID = 3 . " ISU_GET_CLUSTER
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 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_y_distributor  TYPE ISUDR_SPROV_CONTRACT ,
ld_x_keydate  TYPE SY-DATUM ,
ld_yt_suppliers  TYPE ISUDR_SPROV_CONTRACT_TAB ,
ld_x_contract  TYPE EVER-VERTRAG ,
ld_y_premises  TYPE EVBS-VSTELLE ,
ld_x_instln  TYPE EANL-ANLAGE ,
ld_y_division  TYPE EVER-SPARTE ,
ld_x_premises  TYPE EVBS-VSTELLE ,
ld_y_account  TYPE FKKVKP1-VKONT ,
ld_x_division  TYPE EVER-SPARTE ,
ld_y_partner  TYPE EKUN_EXT-PARTNER ,
ld_x_own_supply_id  TYPE C ,
ld_y_account_data  TYPE FKKVKP1 ,
ld_y_partner_data  TYPE EKUN_EXT ,
ld_y_partner_name  TYPE C ,
ld_y_service_addr_lines  TYPE EADRLN ,
ld_y_service_addr_data  TYPE EADRDAT ,
ld_y_service_addr_isudata  TYPE ISU_REG0 ,
ld_y_int_ui  TYPE EUITRANS-INT_UI ,
ld_y_own_supply_id  TYPE C .

ld_x_keydate = '20210129'.

SELECT single VERTRAG
FROM EVER
INTO ld_x_contract.


SELECT single ANLAGE
FROM EANL
INTO ld_x_instln.


SELECT single VSTELLE
FROM EVBS
INTO ld_x_premises.


SELECT single SPARTE
FROM EVER
INTO ld_x_division.

ld_x_own_supply_id = '20210129'.

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 ISU_GET_CLUSTER or its description.