SAP APO_BAPI_DETERMINEUPDATEFLAGS Function Module for Determine Update Indicator for a Value Table









APO_BAPI_DETERMINEUPDATEFLAGS is a standard apo bapi determineupdateflags SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determine Update Indicator for a Value Table processing and below is the pattern details for this FM, 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 apo bapi determineupdateflags FM, simply by entering the name APO_BAPI_DETERMINEUPDATEFLAGS into the relevant SAP transaction such as SE37 or SE38.

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



Function APO_BAPI_DETERMINEUPDATEFLAGS 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 'APO_BAPI_DETERMINEUPDATEFLAGS'"Determine Update Indicator for a Value Table
  EXPORTING
*  STRUCTURE_UPDATETABLE =  "Tabellenname (obsolet)
*  WA_UPDATEINFORMATION =  "(obsolet)
*  WA_VALUES =  "
*  PARAMETER =  "Parametername

 IMPORTING
   WA_UPDATEINFORMATIONS =  "

CHANGING
*  INITIAL_VALUES =  "Sheet Information

TABLES
*  VALUES =  "
*  UPDATEINFORMATION =  "
*  FILTER =  "

EXCEPTIONS
   STRUCTURE_NOT_FOUND = 1
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLAPO_BAPI_GEN_001 User Exit for Method 'ReceivePlanningResults' of Object IF10506

IMPORTING Parameters details for APO_BAPI_DETERMINEUPDATEFLAGS

STRUCTURE_UPDATETABLE - Tabellenname (obsolet)

Data type: X030L-TABNAME
Optional: Yes
Call by Reference: Yes

WA_UPDATEINFORMATION - (obsolet)

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

WA_VALUES -

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

PARAMETER - Parametername

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

EXPORTING Parameters details for APO_BAPI_DETERMINEUPDATEFLAGS

WA_UPDATEINFORMATIONS -

Data type: ANY
Optional: No
Call by Reference: Yes

CHANGING Parameters details for APO_BAPI_DETERMINEUPDATEFLAGS

INITIAL_VALUES - Sheet Information

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

TABLES Parameters details for APO_BAPI_DETERMINEUPDATEFLAGS

VALUES -

Data type:
Optional: Yes
Call by Reference: Yes

UPDATEINFORMATION -

Data type:
Optional: Yes
Call by Reference: Yes

FILTER -

Data type:
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

STRUCTURE_NOT_FOUND - Struktur nicht gefunden

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for APO_BAPI_DETERMINEUPDATEFLAGS 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_values  TYPE STANDARD TABLE OF STRING, "   
lv_initial_values  TYPE APOLOADERSHEETINFOTAB, "   
lv_structure_not_found  TYPE APOLOADERSHEETINFOTAB, "   
lv_structure_updatetable  TYPE X030L-TABNAME, "   
lv_wa_updateinformations  TYPE ANY, "   
lt_updateinformation  TYPE STANDARD TABLE OF ANY, "   
lv_wa_updateinformation  TYPE ANY, "   
lt_filter  TYPE STANDARD TABLE OF ANY, "   
lv_wa_values  TYPE ANY, "   
lv_parameter  TYPE PARAMETER. "   

  CALL FUNCTION 'APO_BAPI_DETERMINEUPDATEFLAGS'  "Determine Update Indicator for a Value Table
    EXPORTING
         STRUCTURE_UPDATETABLE = lv_structure_updatetable
         WA_UPDATEINFORMATION = lv_wa_updateinformation
         WA_VALUES = lv_wa_values
         PARAMETER = lv_parameter
    IMPORTING
         WA_UPDATEINFORMATIONS = lv_wa_updateinformations
    CHANGING
         INITIAL_VALUES = lv_initial_values
    TABLES
         VALUES = lt_values
         UPDATEINFORMATION = lt_updateinformation
         FILTER = lt_filter
    EXCEPTIONS
        STRUCTURE_NOT_FOUND = 1
. " APO_BAPI_DETERMINEUPDATEFLAGS




ABAP code using 7.40 inline data declarations to call FM APO_BAPI_DETERMINEUPDATEFLAGS

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 TABNAME FROM X030L INTO @DATA(ld_structure_updatetable).
 
 
 
 
 
 
 


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!