SAP AIS2_EXTERN_UPDATE_CO Function Module for









AIS2_EXTERN_UPDATE_CO is a standard ais2 extern update co 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 ais2 extern update co FM, simply by entering the name AIS2_EXTERN_UPDATE_CO into the relevant SAP transaction such as SE37 or SE38.

Function Group: AIS2
Program Name: SAPLAIS2
Main Program: SAPLAIS2
Appliation area: K
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function AIS2_EXTERN_UPDATE_CO 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 'AIS2_EXTERN_UPDATE_CO'"
  EXPORTING
*  I_BUDGET_ACTIVITY = 'KBUD' "
*  I_BUDGET_ACTIV_SUP_RET = ' ' "
*  I_COMMIT_DATA = ' ' "
*  I_DELTA_AMOUNTS = 'X' "
*  I_ROLLUP_DATA = 'X' "
*  I_CHECK_PLAN_DATA = 'X' "
*  I_APPLICATION =  "

 IMPORTING
   E_ERRORS_FOUND =  "

TABLES
   IT_BPAK =  "
*  IT_RETURN =  "

EXCEPTIONS
   NO_UPDATE = 1
.



IMPORTING Parameters details for AIS2_EXTERN_UPDATE_CO

I_BUDGET_ACTIVITY -

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

I_BUDGET_ACTIV_SUP_RET -

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

I_COMMIT_DATA -

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

I_DELTA_AMOUNTS -

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

I_ROLLUP_DATA -

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

I_CHECK_PLAN_DATA -

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

I_APPLICATION -

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

EXPORTING Parameters details for AIS2_EXTERN_UPDATE_CO

E_ERRORS_FOUND -

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

TABLES Parameters details for AIS2_EXTERN_UPDATE_CO

IT_BPAK -

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

IT_RETURN -

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

EXCEPTIONS details

NO_UPDATE -

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

Copy and paste ABAP code example for AIS2_EXTERN_UPDATE_CO 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_it_bpak  TYPE STANDARD TABLE OF BPAK, "   
lv_no_update  TYPE BPAK, "   
lv_e_errors_found  TYPE OAX, "   
lv_i_budget_activity  TYPE BPIN-VORGA, "   'KBUD'
lt_it_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_i_budget_activ_sup_ret  TYPE FLAG, "   SPACE
lv_i_commit_data  TYPE BPIN-CHECK, "   SPACE
lv_i_delta_amounts  TYPE BPIN-DELTA, "   'X'
lv_i_rollup_data  TYPE BPIN-ROLLUP, "   'X'
lv_i_check_plan_data  TYPE BPIN-CHECK, "   'X'
lv_i_application  TYPE BPIN-APPLIK. "   

  CALL FUNCTION 'AIS2_EXTERN_UPDATE_CO'  "
    EXPORTING
         I_BUDGET_ACTIVITY = lv_i_budget_activity
         I_BUDGET_ACTIV_SUP_RET = lv_i_budget_activ_sup_ret
         I_COMMIT_DATA = lv_i_commit_data
         I_DELTA_AMOUNTS = lv_i_delta_amounts
         I_ROLLUP_DATA = lv_i_rollup_data
         I_CHECK_PLAN_DATA = lv_i_check_plan_data
         I_APPLICATION = lv_i_application
    IMPORTING
         E_ERRORS_FOUND = lv_e_errors_found
    TABLES
         IT_BPAK = lt_it_bpak
         IT_RETURN = lt_it_return
    EXCEPTIONS
        NO_UPDATE = 1
. " AIS2_EXTERN_UPDATE_CO




ABAP code using 7.40 inline data declarations to call FM AIS2_EXTERN_UPDATE_CO

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 BPIN INTO @DATA(ld_i_budget_activity).
DATA(ld_i_budget_activity) = 'KBUD'.
 
 
DATA(ld_i_budget_activ_sup_ret) = ' '.
 
"SELECT single CHECK FROM BPIN INTO @DATA(ld_i_commit_data).
DATA(ld_i_commit_data) = ' '.
 
"SELECT single DELTA FROM BPIN INTO @DATA(ld_i_delta_amounts).
DATA(ld_i_delta_amounts) = 'X'.
 
"SELECT single ROLLUP FROM BPIN INTO @DATA(ld_i_rollup_data).
DATA(ld_i_rollup_data) = 'X'.
 
"SELECT single CHECK FROM BPIN INTO @DATA(ld_i_check_plan_data).
DATA(ld_i_check_plan_data) = 'X'.
 
"SELECT single APPLIK FROM BPIN INTO @DATA(ld_i_application).
 


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!