SAP AIPA_READ_VALUES_PROFIT_DATA Function Module for
AIPA_READ_VALUES_PROFIT_DATA is a standard aipa read values profit 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 aipa read values profit data FM, simply by entering the name AIPA_READ_VALUES_PROFIT_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: AIPA_BUFFERS
Program Name: SAPLAIPA_BUFFERS
Main Program: SAPLAIPA_BUFFERS
Appliation area: A
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function AIPA_READ_VALUES_PROFIT_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 'AIPA_READ_VALUES_PROFIT_DATA'".
EXPORTING
I_OBART = "
* I_IMAK = "
* I_FLG_READ_VALUES = 'X' "
* I_KOKRS = "
* I_GNJHR_IQ = "
* I_OBJNR = "
* I_FLG_REQUESTS_ALONE = ' ' "
* I_AUTHFLG = "
* I_AUTHMSG = "
* I_FLG_RAISE_EXCEPTION = ' ' "
IMPORTING
E_AUTHRC = "
TABLES
* ET_RAIPWI = "
EXCEPTIONS
MISSING_AUTHORITY = 1
IMPORTING Parameters details for AIPA_READ_VALUES_PROFIT_DATA
I_OBART -
Data type: IMPS-OBARTOptional: No
Call by Reference: No ( called with pass by value option)
I_IMAK -
Data type: IMAKOptional: Yes
Call by Reference: No ( called with pass by value option)
I_FLG_READ_VALUES -
Data type:Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_KOKRS -
Data type: IMPR-KOKRSOptional: Yes
Call by Reference: No ( called with pass by value option)
I_GNJHR_IQ -
Data type: IMTP-GJAHROptional: Yes
Call by Reference: No ( called with pass by value option)
I_OBJNR -
Data type: IMPR-OBJNROptional: Yes
Call by Reference: No ( called with pass by value option)
I_FLG_REQUESTS_ALONE -
Data type:Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_AUTHFLG -
Data type: IM_AUTHFLG_TYPEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_AUTHMSG -
Data type: IM_AUTHMSG_TYPEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_FLG_RAISE_EXCEPTION -
Data type:Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for AIPA_READ_VALUES_PROFIT_DATA
E_AUTHRC -
Data type: IM_AUTHRC_TYPEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for AIPA_READ_VALUES_PROFIT_DATA
ET_RAIPWI -
Data type: RAIPWIOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
MISSING_AUTHORITY -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for AIPA_READ_VALUES_PROFIT_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_obart | TYPE IMPS-OBART, " | |||
| lv_e_authrc | TYPE IM_AUTHRC_TYPE, " | |||
| lt_et_raipwi | TYPE STANDARD TABLE OF RAIPWI, " | |||
| lv_missing_authority | TYPE RAIPWI, " | |||
| lv_i_imak | TYPE IMAK, " | |||
| lv_i_flg_read_values | TYPE IMAK, " 'X' | |||
| lv_i_kokrs | TYPE IMPR-KOKRS, " | |||
| lv_i_gnjhr_iq | TYPE IMTP-GJAHR, " | |||
| lv_i_objnr | TYPE IMPR-OBJNR, " | |||
| lv_i_flg_requests_alone | TYPE IMPR, " ' ' | |||
| lv_i_authflg | TYPE IM_AUTHFLG_TYPE, " | |||
| lv_i_authmsg | TYPE IM_AUTHMSG_TYPE, " | |||
| lv_i_flg_raise_exception | TYPE IM_AUTHMSG_TYPE. " ' ' |
|   CALL FUNCTION 'AIPA_READ_VALUES_PROFIT_DATA' " |
| EXPORTING | ||
| I_OBART | = lv_i_obart | |
| I_IMAK | = lv_i_imak | |
| I_FLG_READ_VALUES | = lv_i_flg_read_values | |
| I_KOKRS | = lv_i_kokrs | |
| I_GNJHR_IQ | = lv_i_gnjhr_iq | |
| I_OBJNR | = lv_i_objnr | |
| I_FLG_REQUESTS_ALONE | = lv_i_flg_requests_alone | |
| I_AUTHFLG | = lv_i_authflg | |
| I_AUTHMSG | = lv_i_authmsg | |
| I_FLG_RAISE_EXCEPTION | = lv_i_flg_raise_exception | |
| IMPORTING | ||
| E_AUTHRC | = lv_e_authrc | |
| TABLES | ||
| ET_RAIPWI | = lt_et_raipwi | |
| EXCEPTIONS | ||
| MISSING_AUTHORITY = 1 | ||
| . " AIPA_READ_VALUES_PROFIT_DATA | ||
ABAP code using 7.40 inline data declarations to call FM AIPA_READ_VALUES_PROFIT_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 OBART FROM IMPS INTO @DATA(ld_i_obart). | ||||
| DATA(ld_i_flg_read_values) | = 'X'. | |||
| "SELECT single KOKRS FROM IMPR INTO @DATA(ld_i_kokrs). | ||||
| "SELECT single GJAHR FROM IMTP INTO @DATA(ld_i_gnjhr_iq). | ||||
| "SELECT single OBJNR FROM IMPR INTO @DATA(ld_i_objnr). | ||||
| DATA(ld_i_flg_requests_alone) | = ' '. | |||
| DATA(ld_i_flg_raise_exception) | = ' '. | |||
Search for further information about these or an SAP related objects