COPA DATASOURCE ENHANCEMENT PDFJune 18, 2020
Basically, COPA will be used to evaluate the “Profitability” of an organization . If we have to add/delete fields from data source operating concern has to be. SAP copa datasource tcodes (Transaction Codes). BIW in IMG for OLTP tcode CMOD, Enhancements, Basis – Customer Enhancements · RSA7, BW Delta. Cost based is done mainly in manufacturing and production Industry.. Account based is done in Service Industries COPA datasources have 3.
|Published (Last):||22 January 2015|
|PDF File Size:||5.51 Mb|
|ePub File Size:||12.79 Mb|
|Price:||Free* [*Free Regsitration Required]|
Types of Profitability Analysis. This type of Profitability Analysis is primarily designed to let you analyze profit quickly for the purpose of sales management.
Darasource main features are, firstly, the use of value fields to group cost and revenue elements, and, secondly, automatic calculation of anticipated or accrual data valuation. The advantage of this method is that data is always up-to-date and therefore provides an effective instrument for controlling sales.
This type of Profitability Analysis enables you to reconcile cost and financial accounting at any time using accounts. In contrast to costing-based Profitability Analysis, this type uses cost and revenue elements, which gives you a unified structure for all of catasource. The system posts all revenues and costs to both Financial Accounting and Profitability Analysis at the same time and using the same valuation method.
COPA Datasource enhancement
Enhancejent means that the cost of sales is posted to Profitability Analysis at the point of goods issue. What is Operating Concern? Characteristics are the criteria in Profitability Analysis CO.
PA according to which you can analyze your operating results and perform differentiated sales and profit planning. Value fields are only required in costing-based Profitability Analysis. These are the fields that contain the currency amounts and quantities that you want to analyze in CO.
Prerequisites for creating OC: Crate Operating concern in KEA0. Assign the cost element group under a value field in KEI2. All the above settings were datasoource by FI Consultants. For each CO-PA specific field with a name consisting of five characters, the system generates a corresponding Info object in the back ground.
As in BI 7. Then we can delete that data source from BW and replicate as 7. All info objects will be remain there in the datasojrce. CO-PA data source cannot be enhanced.
Now that new field cannot be adjusted with the existing data source. Data source has to be deleted and recreated.
If you created the data source with the same as old data source name, no need to create transformations in BW newly. This Table contains Actual transaction data in detail level. Daily transactions, Invoices are captured in this table. All planned data, different estimates are stored in this table. This table holds Segment level data.
This is set up between the segment table and the line items. This is the segment table, which is located at a higher level. It is used to assign segment numbers to each combination of characteristic values. Steps To Create Operating Concern: Or KEA0 is the direct T-code. After saving we have to maintain the Data Structure, Click on the change button.
Assign the required characteristics to data structure. Assign the required value fields to data structure. Check, Save, Activate and go back. Operating Concern Activated Successfully. The CO-PA Model is basically based on following 4 tables once the Operating concern is created, these tables are created automatically. This is the segment tablewhich is located at a higher level.
BW Steps Going to Start. Creation of Data Source: Go to T-code KEB0 and specify the Data source name, choose the Create function, provide the relevant operating concern, and select Cos-based accounting.
Provide Short, Medium and long descriptions. Specify the field name for partitioning and double click on that field to initialize. Steps in BW side: Replicate Data source in RSA1.
BIBO Blog: CO-PA Data Source
Check the data in the Info cube. The following diagram is illustrating how the delta mechanism in CO. Some points to be noted regarding Delta: PA data source it will be generated automatically. Half an hour was chosen as the safety delta to overcome any time differences between the clocks on the different application servers. Transaction codes in CO-PA: Assigning company code to controlling area. Assigning Controlling area to Operating Concern. Creation of Cost element. Creation of Data Source. Display Detailed information about Data Source.
To check the TimeStamp. To see whether the delta pointer is enabled or not. Means the delta pointer was set at sales doc number, suppose if you start the next delta run, by that the system will the records from the sales document number on words.
In the above it is Showing the time stamp of last load when it was started. Why it is showing Time showing as Delta pointer??? The data is stored in cluster tables from where it is read when the initialization is run. Works based on timestamp criteria, so every delta will take records changed or modified after the timestamp of the last loaded record even if there is a safety interval.
From the intermediary the delta records are transferred to RSA7 queue.
COPA Datasource enhancement
COPA delta works based on timestamp. There will be a safety interval upper limit of 30 min, meaning the records posted in the last 30 min will not be loaded. When infopak is run records are written to delta queue from copa tables and updated to BW.
LO has a different mechanism of handling delta. Then the V3 jobs writes these records to the delta queue.