SAP BAPI_COPAPLANNING_GETDATA Function Module for Read CO-PA Planning Data
BAPI_COPAPLANNING_GETDATA is a standard bapi copaplanning getdata SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read CO-PA Planning Data 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 copaplanning getdata FM, simply by entering the name BAPI_COPAPLANNING_GETDATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: KE_BAPI_COPAPLANNING
Program Name: SAPLKE_BAPI_COPAPLANNING
Main Program:
Appliation area: K
Release date: 12-May-1999
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_COPAPLANNING_GETDATA 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_COPAPLANNING_GETDATA'"Read CO-PA Planning Data.
EXPORTING
OPERATINGCONCERN = "Operating Concern
TYPEOFPROFITANALYSIS = "Type of Profitability Analysis
TABLES
SELECTEDFIELDS = "Field List
SELECTION = "Selection
DATA = "Data
RETURN = "Messages
IMPORTING Parameters details for BAPI_COPAPLANNING_GETDATA
OPERATINGCONCERN - Operating Concern
Data type: BAPI1167-OPERATINGCONCERNOptional: No
Call by Reference: No ( called with pass by value option)
TYPEOFPROFITANALYSIS - Type of Profitability Analysis
Data type: BAPI1167-TYPEOFPAOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_COPAPLANNING_GETDATA
SELECTEDFIELDS - Field List
Data type: BAPI_COPA_FIELDOptional: No
Call by Reference: No ( called with pass by value option)
SELECTION - Selection
Data type: BAPI_COPA_SELECTIONOptional: No
Call by Reference: No ( called with pass by value option)
DATA - Data
Data type: BAPI_COPA_DATAOptional: No
Call by Reference: No ( called with pass by value option)
RETURN - Messages
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BAPI_COPAPLANNING_GETDATA 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_selectedfields | TYPE STANDARD TABLE OF BAPI_COPA_FIELD, " | |||
| lv_operatingconcern | TYPE BAPI1167-OPERATINGCONCERN, " | |||
| lt_selection | TYPE STANDARD TABLE OF BAPI_COPA_SELECTION, " | |||
| lv_typeofprofitanalysis | TYPE BAPI1167-TYPEOFPA, " | |||
| lt_data | TYPE STANDARD TABLE OF BAPI_COPA_DATA, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2. " |
|   CALL FUNCTION 'BAPI_COPAPLANNING_GETDATA' "Read CO-PA Planning Data |
| EXPORTING | ||
| OPERATINGCONCERN | = lv_operatingconcern | |
| TYPEOFPROFITANALYSIS | = lv_typeofprofitanalysis | |
| TABLES | ||
| SELECTEDFIELDS | = lt_selectedfields | |
| SELECTION | = lt_selection | |
| DATA | = lt_data | |
| RETURN | = lt_return | |
| . " BAPI_COPAPLANNING_GETDATA | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_COPAPLANNING_GETDATA
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 OPERATINGCONCERN FROM BAPI1167 INTO @DATA(ld_operatingconcern). | ||||
| "SELECT single TYPEOFPA FROM BAPI1167 INTO @DATA(ld_typeofprofitanalysis). | ||||
Search for further information about these or an SAP related objects