SAP BAPI_COPAQUERY_GETACC_ACTDATA Function Module for BAPI COPAQuery.GetAccountBasedActualData









BAPI_COPAQUERY_GETACC_ACTDATA is a standard bapi copaquery getacc actdata SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for BAPI COPAQuery.GetAccountBasedActualData 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 bapi copaquery getacc actdata FM, simply by entering the name BAPI_COPAQUERY_GETACC_ACTDATA into the relevant SAP transaction such as SE37 or SE38.

Function Group: KE_BAPI_COPAQUERY
Program Name: SAPLKE_BAPI_COPAQUERY
Main Program:
Appliation area: K
Release date: 27-May-1999
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAPI_COPAQUERY_GETACC_ACTDATA 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 'BAPI_COPAQUERY_GETACC_ACTDATA'"BAPI COPAQuery.GetAccountBasedActualData
  EXPORTING
   OPERATINGCONCERN =  "Operating concern from which data is to be read
   CONTROLLINGAREA =  "Controlling area
   VALUATIONTYPE =  "Valuation view
   MAXRECORDS =  "Maximum number of records to be returned

TABLES
   SELECTION =  "Input: Selection criterion for data
   SELECTEDFIELDS =  "Input: Fields to be returned
   RESULTDATA =  "Output: selected (aggregated) data
   RETURN =  "Output: Messages
.



IMPORTING Parameters details for BAPI_COPAQUERY_GETACC_ACTDATA

OPERATINGCONCERN - Operating concern from which data is to be read

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

CONTROLLINGAREA - Controlling area

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

VALUATIONTYPE - Valuation view

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

MAXRECORDS - Maximum number of records to be returned

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

TABLES Parameters details for BAPI_COPAQUERY_GETACC_ACTDATA

SELECTION - Input: Selection criterion for data

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

SELECTEDFIELDS - Input: Fields to be returned

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

RESULTDATA - Output: selected (aggregated) data

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

RETURN - Output: Messages

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

Copy and paste ABAP code example for BAPI_COPAQUERY_GETACC_ACTDATA 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_selection  TYPE STANDARD TABLE OF BAPI_COPA_SELECTION, "   
lv_operatingconcern  TYPE BAPI1168-OP_CONCERN, "   
lt_selectedfields  TYPE STANDARD TABLE OF BAPI_COPA_FIELD, "   
lv_controllingarea  TYPE BAPI1168-CO_AREA, "   
lt_resultdata  TYPE STANDARD TABLE OF BAPI_COPA_DATA, "   
lv_valuationtype  TYPE BAPI1168-VALUATION_TYPE, "   
lt_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_maxrecords  TYPE BAPI1168-NUM_OF_RECORDS. "   

  CALL FUNCTION 'BAPI_COPAQUERY_GETACC_ACTDATA'  "BAPI COPAQuery.GetAccountBasedActualData
    EXPORTING
         OPERATINGCONCERN = lv_operatingconcern
         CONTROLLINGAREA = lv_controllingarea
         VALUATIONTYPE = lv_valuationtype
         MAXRECORDS = lv_maxrecords
    TABLES
         SELECTION = lt_selection
         SELECTEDFIELDS = lt_selectedfields
         RESULTDATA = lt_resultdata
         RETURN = lt_return
. " BAPI_COPAQUERY_GETACC_ACTDATA




ABAP code using 7.40 inline data declarations to call FM BAPI_COPAQUERY_GETACC_ACTDATA

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 OP_CONCERN FROM BAPI1168 INTO @DATA(ld_operatingconcern).
 
 
"SELECT single CO_AREA FROM BAPI1168 INTO @DATA(ld_controllingarea).
 
 
"SELECT single VALUATION_TYPE FROM BAPI1168 INTO @DATA(ld_valuationtype).
 
 
"SELECT single NUM_OF_RECORDS FROM BAPI1168 INTO @DATA(ld_maxrecords).
 


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!