SAP CY01_CAP_REQ_ASSIGN_EXT Function Module for NOTRANSL: Assigns a capacity requirements record completely to a person or









CY01_CAP_REQ_ASSIGN_EXT is a standard cy01 cap req assign ext 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: Assigns a capacity requirements record completely to a person or 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 cy01 cap req assign ext FM, simply by entering the name CY01_CAP_REQ_ASSIGN_EXT into the relevant SAP transaction such as SE37 or SE38.

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



Function CY01_CAP_REQ_ASSIGN_EXT 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 'CY01_CAP_REQ_ASSIGN_EXT'"NOTRANSL: Assigns a capacity requirements record completely to a person or
  EXPORTING
   IN_KBED_ENTRY =  "Object table capacity requirements records
*  KBEDD_IMP =  "Capacity requirements: dialog table for KBED

EXCEPTIONS
   NOT_A_PERSON = 1    NOT_AN_INDIVIDUAL_CAPACITY = 2    NO_DESTINATION_DEFINED = 3    AMBIGIOUS_DEFINITON = 4    INVALID_DESTINATION_CAP = 5    INVALID_DESTINATION_PERSON = 6    CAP_REQ_ALREADY_SPLIT = 7    SCHEDULING_ERROR = 8    PLANNING_CANCELLED = 9
.



IMPORTING Parameters details for CY01_CAP_REQ_ASSIGN_EXT

IN_KBED_ENTRY - Object table capacity requirements records

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

KBEDD_IMP - Capacity requirements: dialog table for KBED

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

EXCEPTIONS details

NOT_A_PERSON - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

NOT_AN_INDIVIDUAL_CAPACITY - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

NO_DESTINATION_DEFINED - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

AMBIGIOUS_DEFINITON - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

INVALID_DESTINATION_CAP - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

INVALID_DESTINATION_PERSON - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

CAP_REQ_ALREADY_SPLIT - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

SCHEDULING_ERROR - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

PLANNING_CANCELLED -

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

Copy and paste ABAP code example for CY01_CAP_REQ_ASSIGN_EXT 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_not_a_person  TYPE STRING, "   
lv_in_kbed_entry  TYPE CYKBED_TAB, "   
lv_kbedd_imp  TYPE KBEDD, "   
lv_not_an_individual_capacity  TYPE KBEDD, "   
lv_no_destination_defined  TYPE KBEDD, "   
lv_ambigious_definiton  TYPE KBEDD, "   
lv_invalid_destination_cap  TYPE KBEDD, "   
lv_invalid_destination_person  TYPE KBEDD, "   
lv_cap_req_already_split  TYPE KBEDD, "   
lv_scheduling_error  TYPE KBEDD, "   
lv_planning_cancelled  TYPE KBEDD. "   

  CALL FUNCTION 'CY01_CAP_REQ_ASSIGN_EXT'  "NOTRANSL: Assigns a capacity requirements record completely to a person or
    EXPORTING
         IN_KBED_ENTRY = lv_in_kbed_entry
         KBEDD_IMP = lv_kbedd_imp
    EXCEPTIONS
        NOT_A_PERSON = 1
        NOT_AN_INDIVIDUAL_CAPACITY = 2
        NO_DESTINATION_DEFINED = 3
        AMBIGIOUS_DEFINITON = 4
        INVALID_DESTINATION_CAP = 5
        INVALID_DESTINATION_PERSON = 6
        CAP_REQ_ALREADY_SPLIT = 7
        SCHEDULING_ERROR = 8
        PLANNING_CANCELLED = 9
. " CY01_CAP_REQ_ASSIGN_EXT




ABAP code using 7.40 inline data declarations to call FM CY01_CAP_REQ_ASSIGN_EXT

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.

 
 
 
 
 
 
 
 
 
 
 


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!