SAP /DSD/RP_CUST_TABLE_OK_CODE_SET Function Module for NOTRANSL: Setzen des OK-Codes für die DSD-Zusatzdaten
/DSD/RP_CUST_TABLE_OK_CODE_SET is a standard /dsd/rp cust table ok code set 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: Setzen des OK-Codes für die DSD-Zusatzdaten 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 /dsd/rp cust table ok code set FM, simply by entering the name /DSD/RP_CUST_TABLE_OK_CODE_SET into the relevant SAP transaction such as SE37 or SE38.
Function Group: /DSD/RP_CUST
Program Name: /DSD/SAPLRP_CUST
Main Program: /DSD/SAPLRP_CUST
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function /DSD/RP_CUST_TABLE_OK_CODE_SET 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 '/DSD/RP_CUST_TABLE_OK_CODE_SET'"NOTRANSL: Setzen des OK-Codes für die DSD-Zusatzdaten.
EXPORTING
I_OK_CODE = "Generic Type
IMPORTING
E_FCODE_USED = "General Indicator
IMPORTING Parameters details for /DSD/RP_CUST_TABLE_OK_CODE_SET
I_OK_CODE - Generic Type
Data type: COptional: No
Call by Reference: Yes
EXPORTING Parameters details for /DSD/RP_CUST_TABLE_OK_CODE_SET
E_FCODE_USED - General Indicator
Data type: FLAGOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for /DSD/RP_CUST_TABLE_OK_CODE_SET 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_ok_code | TYPE C, " | |||
| lv_e_fcode_used | TYPE FLAG. " |
|   CALL FUNCTION '/DSD/RP_CUST_TABLE_OK_CODE_SET' "NOTRANSL: Setzen des OK-Codes für die DSD-Zusatzdaten |
| EXPORTING | ||
| I_OK_CODE | = lv_i_ok_code | |
| IMPORTING | ||
| E_FCODE_USED | = lv_e_fcode_used | |
| . " /DSD/RP_CUST_TABLE_OK_CODE_SET | ||
ABAP code using 7.40 inline data declarations to call FM /DSD/RP_CUST_TABLE_OK_CODE_SET
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