Then provide the Transport Request number and select the fields for the input selection.ĭataSource “1_CO_PA_COEP” created successfully. Generally, we use the naming convention for the COPA DataSource is: Īfter field selection, check & choose the InfoCatalog (F7) option for the DataSource generation. KEB0 –> define the DataSource with the necessary details as below.

SBIW –> Settings for Application-Specific DataSources (PI) –> Profitability Analysis –> Create Transaction Data DataSource –> Create a DatSource. Generating the COPA DataSource:īelow are the simple steps for generating the COPA DataSource.īasically COPA DataSource generation is a generic extraction and we can create the generic DataSource depending on the KPI’s for the Profitability Analysis. Therefore describing the such scenarios in this document. Initially we had generated the COPA DataSource using the standard procedure and while extracting the data in RSA3, unable to extract the data due to few issues at ECC R/3 back-end level. The main purpose is to extract the data and feed to a BODS interface. In one of the project we had implemented the COPA DataSource at ECC back-end. H ow to change the safety interval limit for COPA DataSource Transporting the Summarization Levels to the next level,Į. I ssues/Errors faced while extraction and building the Summarization Levels,Ĭ. Following is the Scenarios with explanation:ī. The article articulates the step by step procedure for the generation of the COPA DataSource at the ECC R/3 back-end level along with Delta mechanisms and talk about the few challenges faced while extracting the data during implementation.Ģ. SAP NetWeaver Business Warehouse (formerly BI) – SAP BW 3.5 & 7.x.

Base delta zero vs glassing