SAP AIP1_GET_VALUES_SINGLE Function Module for
AIP1_GET_VALUES_SINGLE is a standard aip1 get values single 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 aip1 get values single FM, simply by entering the name AIP1_GET_VALUES_SINGLE into the relevant SAP transaction such as SE37 or SE38.
Function Group: AIP1
Program Name: SAPLAIP1
Main Program: SAPLAIP1
Appliation area: A
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function AIP1_GET_VALUES_SINGLE 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 'AIP1_GET_VALUES_SINGLE'".
EXPORTING
* I_INDEX = "
* I_OBJNR = "
* I_AUTHFLG = "
* I_AUTHMSG = "
* I_FLG_RAISE_AUTH_EXCEPTION = ' ' "
IMPORTING
E_OBART = "
E_OBJNR = "
E_AUTHRC = "
TABLES
* T_BPGE = "
* T_BPJA = "
* T_RAIMACT = "
* T_RAIPWI = "
EXCEPTIONS
NOT_FOUND = 1 MISSING_AUTHORITY = 2
IMPORTING Parameters details for AIP1_GET_VALUES_SINGLE
I_INDEX -
Data type: SY-TABIXOptional: Yes
Call by Reference: No ( called with pass by value option)
I_OBJNR -
Data type: IMZO-OBJNROptional: 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_AUTH_EXCEPTION -
Data type:Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for AIP1_GET_VALUES_SINGLE
E_OBART -
Data type: IMPS-OBARTOptional: No
Call by Reference: No ( called with pass by value option)
E_OBJNR -
Data type: IMZO-OBJNROptional: No
Call by Reference: No ( called with pass by value option)
E_AUTHRC -
Data type: IM_AUTHRC_TYPEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for AIP1_GET_VALUES_SINGLE
T_BPGE -
Data type: BPGEOptional: Yes
Call by Reference: No ( called with pass by value option)
T_BPJA -
Data type: BPJAOptional: Yes
Call by Reference: No ( called with pass by value option)
T_RAIMACT -
Data type: RAIMACTOptional: Yes
Call by Reference: No ( called with pass by value option)
T_RAIPWI -
Data type: RAIPWIOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
MISSING_AUTHORITY -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for AIP1_GET_VALUES_SINGLE 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_t_bpge | TYPE STANDARD TABLE OF BPGE, " | |||
| lv_e_obart | TYPE IMPS-OBART, " | |||
| lv_i_index | TYPE SY-TABIX, " | |||
| lv_not_found | TYPE SY, " | |||
| lt_t_bpja | TYPE STANDARD TABLE OF BPJA, " | |||
| lv_e_objnr | TYPE IMZO-OBJNR, " | |||
| lv_i_objnr | TYPE IMZO-OBJNR, " | |||
| lv_missing_authority | TYPE IMZO, " | |||
| lv_e_authrc | TYPE IM_AUTHRC_TYPE, " | |||
| lv_i_authflg | TYPE IM_AUTHFLG_TYPE, " | |||
| lt_t_raimact | TYPE STANDARD TABLE OF RAIMACT, " | |||
| lt_t_raipwi | TYPE STANDARD TABLE OF RAIPWI, " | |||
| lv_i_authmsg | TYPE IM_AUTHMSG_TYPE, " | |||
| lv_i_flg_raise_auth_exception | TYPE IM_AUTHMSG_TYPE. " ' ' |
|   CALL FUNCTION 'AIP1_GET_VALUES_SINGLE' " |
| EXPORTING | ||
| I_INDEX | = lv_i_index | |
| I_OBJNR | = lv_i_objnr | |
| I_AUTHFLG | = lv_i_authflg | |
| I_AUTHMSG | = lv_i_authmsg | |
| I_FLG_RAISE_AUTH_EXCEPTION | = lv_i_flg_raise_auth_exception | |
| IMPORTING | ||
| E_OBART | = lv_e_obart | |
| E_OBJNR | = lv_e_objnr | |
| E_AUTHRC | = lv_e_authrc | |
| TABLES | ||
| T_BPGE | = lt_t_bpge | |
| T_BPJA | = lt_t_bpja | |
| T_RAIMACT | = lt_t_raimact | |
| T_RAIPWI | = lt_t_raipwi | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| MISSING_AUTHORITY = 2 | ||
| . " AIP1_GET_VALUES_SINGLE | ||
ABAP code using 7.40 inline data declarations to call FM AIP1_GET_VALUES_SINGLE
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_e_obart). | ||||
| "SELECT single TABIX FROM SY INTO @DATA(ld_i_index). | ||||
| "SELECT single OBJNR FROM IMZO INTO @DATA(ld_e_objnr). | ||||
| "SELECT single OBJNR FROM IMZO INTO @DATA(ld_i_objnr). | ||||
| DATA(ld_i_flg_raise_auth_exception) | = ' '. | |||
Search for further information about these or an SAP related objects