SAP CATT_CIF_RESOURCE_CHECK Function Module for NOTRANSL: Check resource existence in APO(used for CATT)









CATT_CIF_RESOURCE_CHECK is a standard catt cif resource check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Check resource existence in APO(used for CATT) processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for catt cif resource check FM, simply by entering the name CATT_CIF_RESOURCE_CHECK into the relevant SAP transaction such as SE37 or SE38.

Function Group: CIFT
Program Name: SAPLCIFT
Main Program:
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function CATT_CIF_RESOURCE_CHECK pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'CATT_CIF_RESOURCE_CHECK'"NOTRANSL: Check resource existence in APO(used for CATT)
EXPORTING
RES_NAME = "Capacity name
RES_PLANT = "Plant
RES_CATEGORY = "Capacity category
RES_CALENDAR = "Factory calendar ID
RES_NUMBER = "Capacity utilization rate (percent)
DESTINATION_NAME = "Logical Destination (Specified in Function Call)
* MANUAL_CHECK = 'X' "Generic Type
RES_TYPE = "Number of individual capacities

EXCEPTIONS
NOT_FOUND = 1 VALUE_ERROR = 2 PARAMETER_ERROR = 3 LOGICAL_SYSTEM_NOT_SET = 4 PLANT_NOT_EXIST = 5
.



IMPORTING Parameters details for CATT_CIF_RESOURCE_CHECK

RES_NAME - Capacity name

Data type: KAKO-NAME
Optional: No
Call by Reference: No ( called with pass by value option)

RES_PLANT - Plant

Data type: KAKO-WERKS
Optional: No
Call by Reference: No ( called with pass by value option)

RES_CATEGORY - Capacity category

Data type: KAKO-KAPAR
Optional: No
Call by Reference: No ( called with pass by value option)

RES_CALENDAR - Factory calendar ID

Data type: KAKO-KALID
Optional: No
Call by Reference: No ( called with pass by value option)

RES_NUMBER - Capacity utilization rate (percent)

Data type: KAKO-NGRAD
Optional: No
Call by Reference: No ( called with pass by value option)

DESTINATION_NAME - Logical Destination (Specified in Function Call)

Data type: ARFCCALLID-ARFCDEST
Optional: No
Call by Reference: No ( called with pass by value option)

MANUAL_CHECK - Generic Type

Data type: C
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

RES_TYPE - Number of individual capacities

Data type: KAKO-AZNOR
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

NOT_FOUND - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

VALUE_ERROR - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

PARAMETER_ERROR - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

LOGICAL_SYSTEM_NOT_SET - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

PLANT_NOT_EXIST - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for CATT_CIF_RESOURCE_CHECK Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

DATA:
lv_res_name  TYPE KAKO-NAME, "   
lv_not_found  TYPE KAKO, "   
lv_res_plant  TYPE KAKO-WERKS, "   
lv_value_error  TYPE KAKO, "   
lv_res_category  TYPE KAKO-KAPAR, "   
lv_parameter_error  TYPE KAKO, "   
lv_res_calendar  TYPE KAKO-KALID, "   
lv_logical_system_not_set  TYPE KAKO, "   
lv_res_number  TYPE KAKO-NGRAD, "   
lv_plant_not_exist  TYPE KAKO, "   
lv_destination_name  TYPE ARFCCALLID-ARFCDEST, "   
lv_manual_check  TYPE C, "   'X'
lv_res_type  TYPE KAKO-AZNOR. "   

  CALL FUNCTION 'CATT_CIF_RESOURCE_CHECK'  "NOTRANSL: Check resource existence in APO(used for CATT)
    EXPORTING
         RES_NAME = lv_res_name
         RES_PLANT = lv_res_plant
         RES_CATEGORY = lv_res_category
         RES_CALENDAR = lv_res_calendar
         RES_NUMBER = lv_res_number
         DESTINATION_NAME = lv_destination_name
         MANUAL_CHECK = lv_manual_check
         RES_TYPE = lv_res_type
    EXCEPTIONS
        NOT_FOUND = 1
        VALUE_ERROR = 2
        PARAMETER_ERROR = 3
        LOGICAL_SYSTEM_NOT_SET = 4
        PLANT_NOT_EXIST = 5
. " CATT_CIF_RESOURCE_CHECK




ABAP code using 7.40 inline data declarations to call FM CATT_CIF_RESOURCE_CHECK

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

"SELECT single NAME FROM KAKO INTO @DATA(ld_res_name).
 
 
"SELECT single WERKS FROM KAKO INTO @DATA(ld_res_plant).
 
 
"SELECT single KAPAR FROM KAKO INTO @DATA(ld_res_category).
 
 
"SELECT single KALID FROM KAKO INTO @DATA(ld_res_calendar).
 
 
"SELECT single NGRAD FROM KAKO INTO @DATA(ld_res_number).
 
 
"SELECT single ARFCDEST FROM ARFCCALLID INTO @DATA(ld_destination_name).
 
DATA(ld_manual_check) = 'X'.
 
"SELECT single AZNOR FROM KAKO INTO @DATA(ld_res_type).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!