KCR01_GET_IPPE_RESOURCE SAP Function module

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

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

Pattern for FM KCR01_GET_IPPE_RESOURCE - KCR01 GET IPPE RESOURCE

CALL FUNCTION 'KCR01_GET_IPPE_RESOURCE' "
* EXPORTING
*   i_key_date = SY-DATLO       " sy-datum
*   i_object_number =           " j_objnr
*   i_controlling_area =        " kokrs
*   i_cost_center =             " kostl
*   i_activity_type =           " lstar
*   i_business_process =        " co_prznr
  IMPORTING
    i_ippe_guid_tab =           " kcr_guid_16_tab
  EXCEPTIONS
    NOT_FOUND = 1               "
    CONTROLLING_AREA_MISMATCH = 2  "
    .  "  KCR01_GET_IPPE_RESOURCE

ABAP code example for Function Module KCR01_GET_IPPE_RESOURCE

The ABAP code below is a full code listing to execute function module KCR01_GET_IPPE_RESOURCE 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_i_ippe_guid_tab  
 
 TYPE KCR_GUID_16_TAB
.


DATA(ld_i_key_date) = '20210129'.

DATA(ld_i_object_number) = '20210129'.

DATA(ld_i_controlling_area) = '20210129'.

DATA(ld_i_cost_center) = '20210129'.

DATA(ld_i_activity_type) = '20210129'.

DATA(ld_i_business_process) = '20210129'.
.

CALL FUNCTION 'KCR01_GET_IPPE_RESOURCE'
* EXPORTING
*   i_key_date =                 ld_i_key_date
*   i_object_number =            ld_i_object_number
*   i_controlling_area =         ld_i_controlling_area
*   i_cost_center =              ld_i_cost_center
*   i_activity_type =            ld_i_activity_type
*   i_business_process =         ld_i_business_process
  IMPORTING
    i_ippe_guid_tab =            ld_i_ippe_guid_tab
  EXCEPTIONS
    NOT_FOUND =                  1
    CONTROLLING_AREA_MISMATCH =    2
    .  "  KCR01_GET_IPPE_RESOURCE

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
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_i_ippe_guid_tab
 
 TYPE KCR_GUID_16_TAB ,
ld_i_key_date
 
 TYPE SY-DATUM ,
ld_i_object_number
 
 TYPE J_OBJNR ,
ld_i_controlling_area
 
 TYPE KOKRS ,
ld_i_cost_center
 
 TYPE KOSTL ,
ld_i_activity_type
 
 TYPE LSTAR ,
ld_i_business_process
 
 TYPE CO_PRZNR .


ld_i_key_date = '20210129'.
ld_i_object_number = '20210129'.
ld_i_controlling_area = '20210129'.
ld_i_cost_center = '20210129'.
ld_i_activity_type = '20210129'.
ld_i_business_process = '20210129'.