SAP CY01_SPLITTING_OK_CODE Function Module for NOTRANSL: Processes the ok code value for the splitting subscreens









CY01_SPLITTING_OK_CODE is a standard cy01 splitting ok code 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: Processes the ok code value for the splitting subscreens 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 splitting ok code FM, simply by entering the name CY01_SPLITTING_OK_CODE 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_SPLITTING_OK_CODE 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_SPLITTING_OK_CODE'"NOTRANSL: Processes the ok code value for the splitting subscreens
EXPORTING
OK_CODE_IMP = "OK code to process

IMPORTING
OK_CODE_EXP = "blank, if OK code was processed

EXCEPTIONS
NOT_A_PERSON = 1 NO_ASSIGNMENT = 2
.



IMPORTING Parameters details for CY01_SPLITTING_OK_CODE

OK_CODE_IMP - OK code to process

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

EXPORTING Parameters details for CY01_SPLITTING_OK_CODE

OK_CODE_EXP - blank, if OK code was processed

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

EXCEPTIONS details

NOT_A_PERSON - Capacity category is not a labor capacity

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

NO_ASSIGNMENT - Assignment is not allowed

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

Copy and paste ABAP code example for CY01_SPLITTING_OK_CODE 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_ok_code_exp  TYPE SYUCOMM, "   
lv_ok_code_imp  TYPE SYUCOMM, "   
lv_not_a_person  TYPE SYUCOMM, "   
lv_no_assignment  TYPE SYUCOMM. "   

  CALL FUNCTION 'CY01_SPLITTING_OK_CODE'  "NOTRANSL: Processes the ok code value for the splitting subscreens
    EXPORTING
         OK_CODE_IMP = lv_ok_code_imp
    IMPORTING
         OK_CODE_EXP = lv_ok_code_exp
    EXCEPTIONS
        NOT_A_PERSON = 1
        NO_ASSIGNMENT = 2
. " CY01_SPLITTING_OK_CODE




ABAP code using 7.40 inline data declarations to call FM CY01_SPLITTING_OK_CODE

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!