SAP CORU_S_GET_CUST Function Module for Get Customizing OPK0 from Function Group CORU_S
CORU_S_GET_CUST is a standard coru s get cust SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get Customizing OPK0 from Function Group CORU_S 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 coru s get cust FM, simply by entering the name CORU_S_GET_CUST into the relevant SAP transaction such as SE37 or SE38.
Function Group: CORU_S
Program Name: SAPLCORU_S
Main Program: SAPLCORU_S
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CORU_S_GET_CUST 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 'CORU_S_GET_CUST'"Get Customizing OPK0 from Function Group CORU_S.
IMPORTING
E_TCORUSSDEF = "Customizing for Single Screen Entry of a Confirmation
EXCEPTIONS
NOT_FOUND = 1
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLCORU_S_001 QM: Create Notif. from Confirmation of Production Order
EXIT_SAPLCORU_S_100 Transfer Data from SAPLCORU_S to Customer-Defined Screen
EXIT_SAPLCORU_S_101 Return Data from Customer-Defined Screen to SAPLCORU_S
EXPORTING Parameters details for CORU_S_GET_CUST
E_TCORUSSDEF - Customizing for Single Screen Entry of a Confirmation
Data type: TCORUSSDEFOptional: No
Call by Reference: Yes
EXCEPTIONS details
NOT_FOUND - No Entry Found
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CORU_S_GET_CUST 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_found | TYPE STRING, " | |||
| lv_e_tcorussdef | TYPE TCORUSSDEF. " |
|   CALL FUNCTION 'CORU_S_GET_CUST' "Get Customizing OPK0 from Function Group CORU_S |
| IMPORTING | ||
| E_TCORUSSDEF | = lv_e_tcorussdef | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| . " CORU_S_GET_CUST | ||
ABAP code using 7.40 inline data declarations to call FM CORU_S_GET_CUST
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