SAP CY_GET_CAPACITY_HIERARCHY_2 Function Module for Determine capacity-related sub-hierarchy starting from a work center









CY_GET_CAPACITY_HIERARCHY_2 is a standard cy get capacity hierarchy 2 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determine capacity-related sub-hierarchy starting from a work center 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 cy get capacity hierarchy 2 FM, simply by entering the name CY_GET_CAPACITY_HIERARCHY_2 into the relevant SAP transaction such as SE37 or SE38.

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



Function CY_GET_CAPACITY_HIERARCHY_2 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 'CY_GET_CAPACITY_HIERARCHY_2'"Determine capacity-related sub-hierarchy starting from a work center
EXPORTING
ARBEITSPLATZID = "Work center from which the hierarchy is looked at.
HIERARCHIENAME = "Name of Hierarchy
HIERARCHIEWERK = "Task list where the hierarchy is agreed upon.
IRC65A = "
WERK = "

IMPORTING
ERC65A = "

TABLES
KAPART = "
KAPHIE = "

EXCEPTIONS
MISSING_PARAMETER = 1 NO_SUCH_HIERARCHY = 2
.



IMPORTING Parameters details for CY_GET_CAPACITY_HIERARCHY_2

ARBEITSPLATZID - Work center from which the hierarchy is looked at.

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

HIERARCHIENAME - Name of Hierarchy

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

HIERARCHIEWERK - Task list where the hierarchy is agreed upon.

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

IRC65A -

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

WERK -

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

EXPORTING Parameters details for CY_GET_CAPACITY_HIERARCHY_2

ERC65A -

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

TABLES Parameters details for CY_GET_CAPACITY_HIERARCHY_2

KAPART -

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

KAPHIE -

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

EXCEPTIONS details

MISSING_PARAMETER - Required parameters not specified

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

NO_SUCH_HIERARCHY - Hierarchy does not exist in the plant

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

Copy and paste ABAP code example for CY_GET_CAPACITY_HIERARCHY_2 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_erc65a  TYPE RC65A, "   
lt_kapart  TYPE STANDARD TABLE OF RCRKK, "   
lv_arbeitsplatzid  TYPE CRHD-OBJID, "   
lv_missing_parameter  TYPE CRHD, "   
lt_kaphie  TYPE STANDARD TABLE OF CYHIECAP, "   
lv_hierarchiename  TYPE CRHH-NAME, "   
lv_no_such_hierarchy  TYPE CRHH, "   
lv_hierarchiewerk  TYPE CRHH-WERKS, "   
lv_irc65a  TYPE RC65A, "   
lv_werk  TYPE CRHD-WERKS. "   

  CALL FUNCTION 'CY_GET_CAPACITY_HIERARCHY_2'  "Determine capacity-related sub-hierarchy starting from a work center
    EXPORTING
         ARBEITSPLATZID = lv_arbeitsplatzid
         HIERARCHIENAME = lv_hierarchiename
         HIERARCHIEWERK = lv_hierarchiewerk
         IRC65A = lv_irc65a
         WERK = lv_werk
    IMPORTING
         ERC65A = lv_erc65a
    TABLES
         KAPART = lt_kapart
         KAPHIE = lt_kaphie
    EXCEPTIONS
        MISSING_PARAMETER = 1
        NO_SUCH_HIERARCHY = 2
. " CY_GET_CAPACITY_HIERARCHY_2




ABAP code using 7.40 inline data declarations to call FM CY_GET_CAPACITY_HIERARCHY_2

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 OBJID FROM CRHD INTO @DATA(ld_arbeitsplatzid).
 
 
 
"SELECT single NAME FROM CRHH INTO @DATA(ld_hierarchiename).
 
 
"SELECT single WERKS FROM CRHH INTO @DATA(ld_hierarchiewerk).
 
 
"SELECT single WERKS FROM CRHD INTO @DATA(ld_werk).
 


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!