SAP AIA9_VARIANT_PLANING_PBO Function Module for
AIA9_VARIANT_PLANING_PBO is a standard aia9 variant planing pbo 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 aia9 variant planing pbo FM, simply by entering the name AIA9_VARIANT_PLANING_PBO into the relevant SAP transaction such as SE37 or SE38.
Function Group: AIA9
Program Name: SAPLAIA9
Main Program: SAPLAIA9
Appliation area: A
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function AIA9_VARIANT_PLANING_PBO 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 'AIA9_VARIANT_PLANING_PBO'".
EXPORTING
I_OBJNR = "Object Number of Variant
I_VARNT = "Variant of Appropriation Request
IS_IMAK = "
IS_TKA01 = "Controlling Area
IS_TAIF1 = "
I_AKTYP = "Display/Change
CHANGING
C_FLG_CHANGE = "
EXCEPTIONS
DB_READ_FAULT = 1 NO_PROFILES = 2 CANT_FIND_FISCAL_YEAR = 3 CANT_READ_BPIN = 4 CANT_READ_PROFIL = 5
IMPORTING Parameters details for AIA9_VARIANT_PLANING_PBO
I_OBJNR - Object Number of Variant
Data type: IMAV-OBJNROptional: No
Call by Reference: No ( called with pass by value option)
I_VARNT - Variant of Appropriation Request
Data type: IMAV-VARNTOptional: No
Call by Reference: No ( called with pass by value option)
IS_IMAK -
Data type: IMAKOptional: No
Call by Reference: No ( called with pass by value option)
IS_TKA01 - Controlling Area
Data type: TKA01Optional: No
Call by Reference: No ( called with pass by value option)
IS_TAIF1 -
Data type: TAIF1Optional: No
Call by Reference: No ( called with pass by value option)
I_AKTYP - Display/Change
Data type: T020-AKTYPOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for AIA9_VARIANT_PLANING_PBO
C_FLG_CHANGE -
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
DB_READ_FAULT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_PROFILES -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
CANT_FIND_FISCAL_YEAR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
CANT_READ_BPIN -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
CANT_READ_PROFIL -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for AIA9_VARIANT_PLANING_PBO 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_objnr | TYPE IMAV-OBJNR, " | |||
| lv_c_flg_change | TYPE C, " | |||
| lv_db_read_fault | TYPE C, " | |||
| lv_i_varnt | TYPE IMAV-VARNT, " | |||
| lv_no_profiles | TYPE IMAV, " | |||
| lv_is_imak | TYPE IMAK, " | |||
| lv_cant_find_fiscal_year | TYPE IMAK, " | |||
| lv_is_tka01 | TYPE TKA01, " | |||
| lv_cant_read_bpin | TYPE TKA01, " | |||
| lv_is_taif1 | TYPE TAIF1, " | |||
| lv_cant_read_profil | TYPE TAIF1, " | |||
| lv_i_aktyp | TYPE T020-AKTYP. " |
|   CALL FUNCTION 'AIA9_VARIANT_PLANING_PBO' " |
| EXPORTING | ||
| I_OBJNR | = lv_i_objnr | |
| I_VARNT | = lv_i_varnt | |
| IS_IMAK | = lv_is_imak | |
| IS_TKA01 | = lv_is_tka01 | |
| IS_TAIF1 | = lv_is_taif1 | |
| I_AKTYP | = lv_i_aktyp | |
| CHANGING | ||
| C_FLG_CHANGE | = lv_c_flg_change | |
| EXCEPTIONS | ||
| DB_READ_FAULT = 1 | ||
| NO_PROFILES = 2 | ||
| CANT_FIND_FISCAL_YEAR = 3 | ||
| CANT_READ_BPIN = 4 | ||
| CANT_READ_PROFIL = 5 | ||
| . " AIA9_VARIANT_PLANING_PBO | ||
ABAP code using 7.40 inline data declarations to call FM AIA9_VARIANT_PLANING_PBO
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 OBJNR FROM IMAV INTO @DATA(ld_i_objnr). | ||||
| "SELECT single VARNT FROM IMAV INTO @DATA(ld_i_varnt). | ||||
| "SELECT single AKTYP FROM T020 INTO @DATA(ld_i_aktyp). | ||||
Search for further information about these or an SAP related objects