SAP ADK0_READ_RA_DATA Function Module for NOTRANSL: Lese Erg.Erm. Daten passend zu dynamischen Posten

Search SAP Function Modules

ADK0_READ_RA_DATA is a standard adk0 read 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: Lese Erg.Erm. Daten passend zu dynamischen Posten 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 read ra data FM, simply by entering the name ADK0_READ_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_READ_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_READ_RA_DATA'"NOTRANSL: Lese Erg.Erm. Daten passend zu dynamischen Posten
  EXPORTING
   OBJNR =  "Object number
   VERSN =  "Version
   GJAHR =  "Fiscal Year
   PERIO =  "Period
*  VRGNG = ' ' "CO Business Transaction

TABLES
   ET_RA1 =  "Internal RA Structure

EXCEPTIONS
   MESSAGE_TYPE_A = 1    MESSAGE_TYPE_E = 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_READ_RA_DATA

OBJNR - Object number

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

VERSN - Version

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

GJAHR - Fiscal Year

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

PERIO - Period

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

VRGNG - CO Business Transaction

Data type: COSBA-VRGNG
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for ADK0_READ_RA_DATA

ET_RA1 - Internal RA Structure

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

EXCEPTIONS details

MESSAGE_TYPE_A -

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

MESSAGE_TYPE_E -

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

Copy and paste ABAP code example for ADK0_READ_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.

ABAP code using 7.40 inline data declarations to call FM ADK0_READ_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.

Search for further information about these or an SAP related objects