SAP AIPA_BUDGPROC_INPUT_POST Function Module for









AIPA_BUDGPROC_INPUT_POST is a standard aipa budgproc input post 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 budgproc input post FM, simply by entering the name AIPA_BUDGPROC_INPUT_POST into the relevant SAP transaction such as SE37 or SE38.

Function Group: AIPA_FUNC_BP
Program Name: SAPLAIPA_FUNC_BP
Main Program: SAPLAIPA_FUNC_BP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1



Function AIPA_BUDGPROC_INPUT_POST 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_BUDGPROC_INPUT_POST'"
EXPORTING
IT_COVOB = "
I_VORGA = "
I_WRTTP = "
I_TRGKZ = "
* I_VERSN = '000' "
I_POSIT = "
* I_SGTXT = ' ' "
* I_FLG_BUDG_DIST = ' ' "Screens, display user entry
* I_FLG_COMPUTE_DELTA = ' ' "

TABLES
* T_OBJ_NO_UPD_BPTR = "
* T_OBJ_NO_UPD_BPHI = "
.



IMPORTING Parameters details for AIPA_BUDGPROC_INPUT_POST

IT_COVOB -

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

I_VORGA -

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

I_WRTTP -

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

I_TRGKZ -

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

I_VERSN -

Data type: BPGE-VERSN
Default: '000'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_POSIT -

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

I_SGTXT -

Data type: BPIN-SGTEXT
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_FLG_BUDG_DIST - Screens, display user entry

Data type: SY-DATAR
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_FLG_COMPUTE_DELTA -

Data type: SY-DATAR
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for AIPA_BUDGPROC_INPUT_POST

T_OBJ_NO_UPD_BPTR -

Data type: RAIP_OBJ
Optional: Yes
Call by Reference: Yes

T_OBJ_NO_UPD_BPHI -

Data type: RAIP_OBJ
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for AIPA_BUDGPROC_INPUT_POST 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_it_covob  TYPE IM_COVOB_TAB_TYPE, "   
lt_t_obj_no_upd_bptr  TYPE STANDARD TABLE OF RAIP_OBJ, "   
lv_i_vorga  TYPE BPGE-VORGA, "   
lt_t_obj_no_upd_bphi  TYPE STANDARD TABLE OF RAIP_OBJ, "   
lv_i_wrttp  TYPE BPGE-WRTTP, "   
lv_i_trgkz  TYPE BPGE-TRGKZ, "   
lv_i_versn  TYPE BPGE-VERSN, "   '000'
lv_i_posit  TYPE BPGE-POSIT, "   
lv_i_sgtxt  TYPE BPIN-SGTEXT, "   ' '
lv_i_flg_budg_dist  TYPE SY-DATAR, "   ' '
lv_i_flg_compute_delta  TYPE SY-DATAR. "   ' '

  CALL FUNCTION 'AIPA_BUDGPROC_INPUT_POST'  "
    EXPORTING
         IT_COVOB = lv_it_covob
         I_VORGA = lv_i_vorga
         I_WRTTP = lv_i_wrttp
         I_TRGKZ = lv_i_trgkz
         I_VERSN = lv_i_versn
         I_POSIT = lv_i_posit
         I_SGTXT = lv_i_sgtxt
         I_FLG_BUDG_DIST = lv_i_flg_budg_dist
         I_FLG_COMPUTE_DELTA = lv_i_flg_compute_delta
    TABLES
         T_OBJ_NO_UPD_BPTR = lt_t_obj_no_upd_bptr
         T_OBJ_NO_UPD_BPHI = lt_t_obj_no_upd_bphi
. " AIPA_BUDGPROC_INPUT_POST




ABAP code using 7.40 inline data declarations to call FM AIPA_BUDGPROC_INPUT_POST

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 VORGA FROM BPGE INTO @DATA(ld_i_vorga).
 
 
"SELECT single WRTTP FROM BPGE INTO @DATA(ld_i_wrttp).
 
"SELECT single TRGKZ FROM BPGE INTO @DATA(ld_i_trgkz).
 
"SELECT single VERSN FROM BPGE INTO @DATA(ld_i_versn).
DATA(ld_i_versn) = '000'.
 
"SELECT single POSIT FROM BPGE INTO @DATA(ld_i_posit).
 
"SELECT single SGTEXT FROM BPIN INTO @DATA(ld_i_sgtxt).
DATA(ld_i_sgtxt) = ' '.
 
"SELECT single DATAR FROM SY INTO @DATA(ld_i_flg_budg_dist).
DATA(ld_i_flg_budg_dist) = ' '.
 
"SELECT single DATAR FROM SY INTO @DATA(ld_i_flg_compute_delta).
DATA(ld_i_flg_compute_delta) = ' '.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!