SAP REGUH_CPD_DATA Function Module for
REGUH_CPD_DATA is a standard reguh cpd data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 reguh cpd data FM, simply by entering the name REGUH_CPD_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: F028
Program Name: SAPLF028
Main Program: SAPLF028
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function REGUH_CPD_DATA 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 'REGUH_CPD_DATA'".
EXPORTING
I_BSEC = "One-Time Account Data
* I_KOART = ' ' "Account type
* I_KONKO = ' ' "
IMPORTING Parameters details for REGUH_CPD_DATA
I_BSEC - One-Time Account Data
Data type: BSECOptional: No
Call by Reference: No ( called with pass by value option)
I_KOART - Account type
Data type: BSEG-KOARTDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_KONKO -
Data type: BSEG-LIFNRDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for REGUH_CPD_DATA 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_i_bsec | TYPE BSEC, " | |||
| lv_i_koart | TYPE BSEG-KOART, " SPACE | |||
| lv_i_konko | TYPE BSEG-LIFNR. " SPACE |
|   CALL FUNCTION 'REGUH_CPD_DATA' " |
| EXPORTING | ||
| I_BSEC | = lv_i_bsec | |
| I_KOART | = lv_i_koart | |
| I_KONKO | = lv_i_konko | |
| . " REGUH_CPD_DATA | ||
ABAP code using 7.40 inline data declarations to call FM REGUH_CPD_DATA
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 KOART FROM BSEG INTO @DATA(ld_i_koart). | ||||
| DATA(ld_i_koart) | = ' '. | |||
| "SELECT single LIFNR FROM BSEG INTO @DATA(ld_i_konko). | ||||
| DATA(ld_i_konko) | = ' '. | |||
Search for further information about these or an SAP related objects