SAP ADK0_ADD_RA_DATA Function Module for NOTRANSL: Addiere Ergebnisermittlungsdaten zum Objekt passend zu DP
ADK0_ADD_RA_DATA is a standard adk0 add ra data 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: Addiere Ergebnisermittlungsdaten zum Objekt passend zu DP 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 adk0 add ra data FM, simply by entering the name ADK0_ADD_RA_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: ADK0
Program Name: SAPLADK0
Main Program: SAPLADK0
Appliation area: K
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ADK0_ADD_RA_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 'ADK0_ADD_RA_DATA'"NOTRANSL: Addiere Ergebnisermittlungsdaten zum Objekt passend zu DP.
EXPORTING
RA_UPDATE = "Update Results Analysis Data?
COMMIT_WORK = "COMMIT WORK?
OBJNR = "Object number
VERSN = "Version
* STATUS_UPDATE = ' ' "Character 1 Field
TABLES
IT_RA1 = "Internal RA Structure
EXCEPTIONS
MESSAGE_TYPE_E = 1 MESSAGE_TYPE_A = 2
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_SAPLADK0_001 Customer-Specific Postprocessing: CO Subkey Dynamic Items Results Analysis
EXIT_SAPLADK0_002 Customer-Specific Postprocessing of Results Analysis with Dynamic Items
EXIT_SAPLADK0_003 Customer-Specific Use of DI to Results Analysis Transfer Interface (Stock)
EXIT_SAPLADK0_004 Customer-Specific Use of DI to Results Analysis Transfer Interface(billed)
IMPORTING Parameters details for ADK0_ADD_RA_DATA
RA_UPDATE - Update Results Analysis Data?
Data type: KKALKKAG-ABGRUPDATEOptional: No
Call by Reference: No ( called with pass by value option)
COMMIT_WORK - COMMIT WORK?
Data type: KKALKKAG-COMMITWORKOptional: No
Call by Reference: No ( called with pass by value option)
OBJNR - Object number
Data type: COSBA-OBJNROptional: No
Call by Reference: No ( called with pass by value option)
VERSN - Version
Data type: COSBA-VERSNOptional: No
Call by Reference: No ( called with pass by value option)
STATUS_UPDATE - Character 1 Field
Data type: KKACHR1Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ADK0_ADD_RA_DATA
IT_RA1 - Internal RA Structure
Data type: ADK0_RA1Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
MESSAGE_TYPE_E -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
MESSAGE_TYPE_A -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ADK0_ADD_RA_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: | ||||
| lt_it_ra1 | TYPE STANDARD TABLE OF ADK0_RA1, " | |||
| lv_ra_update | TYPE KKALKKAG-ABGRUPDATE, " | |||
| lv_message_type_e | TYPE KKALKKAG, " | |||
| lv_commit_work | TYPE KKALKKAG-COMMITWORK, " | |||
| lv_message_type_a | TYPE KKALKKAG, " | |||
| lv_objnr | TYPE COSBA-OBJNR, " | |||
| lv_versn | TYPE COSBA-VERSN, " | |||
| lv_status_update | TYPE KKACHR1. " SPACE |
|   CALL FUNCTION 'ADK0_ADD_RA_DATA' "NOTRANSL: Addiere Ergebnisermittlungsdaten zum Objekt passend zu DP |
| EXPORTING | ||
| RA_UPDATE | = lv_ra_update | |
| COMMIT_WORK | = lv_commit_work | |
| OBJNR | = lv_objnr | |
| VERSN | = lv_versn | |
| STATUS_UPDATE | = lv_status_update | |
| TABLES | ||
| IT_RA1 | = lt_it_ra1 | |
| EXCEPTIONS | ||
| MESSAGE_TYPE_E = 1 | ||
| MESSAGE_TYPE_A = 2 | ||
| . " ADK0_ADD_RA_DATA | ||
ABAP code using 7.40 inline data declarations to call FM ADK0_ADD_RA_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 ABGRUPDATE FROM KKALKKAG INTO @DATA(ld_ra_update). | ||||
| "SELECT single COMMITWORK FROM KKALKKAG INTO @DATA(ld_commit_work). | ||||
| "SELECT single OBJNR FROM COSBA INTO @DATA(ld_objnr). | ||||
| "SELECT single VERSN FROM COSBA INTO @DATA(ld_versn). | ||||
| DATA(ld_status_update) | = ' '. | |||
Search for further information about these or an SAP related objects