COPA assessments

Hey All
Is there any way to reverse the signs in COPA assessments. For eg. FI has a balance of $100 which is to be assessed to COPA. When assessed the COPA gets the same value $100. Can I make some setting to change it to $100- in COPA. The record type here is D and VF is Sales rebates which has transfer +/- indicator checked in KE4i. For record type "F" postings to this VF i get the reverse signs in COPA which is correct. I want the same thing for assessments in COPA

Hi Ankur
You cannot reverse costs while allocating from CCA to COPA... Most of the values in COPA are updated as absolute values i.e. without a +/- sign.. Only exception is Reversals, Cr memo....
So, you let the assessment happen with +ve sign.. Post the assessment amount to a separate Value Field...In your report definition in KE34/35, you can subtract this amount using the Formula....
Eg: System updates Sales revenue 100 USD and Sales rebates allocated by you as 10 USD... You need to show net revenue as 100-10 = 90.. which is possible in report definition
What you are trying is Sales revenue as 100 USD and update the allocated amount as -10... If you achieve this, you would use formula in report painter as 100+ (-10) = 90....
Hence, the end result would be the same...
Regards
Ajay M

Similar Messages

Company code and operating concern currency in COPA

Dear experts,
I have one controlling area and one operating concern for indian and foreign entitiy with INR as currency for controlling area and one operating concern.
but outside india i have sgd as company code currency.
So i ticked company code currency in operating concern.so while posting revenue in billing .system store in company code as well as operating concern currency.
But all my expenses for outside india entity will store(cost center) in company code currency 'SGD' and controlling area currency 'INR'.
while doing copa assesssment cycle- whether system will store data in copa table in SGD and INR or only INR as operating concern currency.
i need report on operating concern currency as well as company code currency.
regards
Raman Rana

Hi,
If you have ticked 'company code ccy' in KEA0 then all COPA postings (including COPA assessments) will happen in both currencies i.e. company code ccy and operating concern ccy.
regards
Waman

FI-COPA Reconciliation variance

Dear Experts,
After we run all our cycles we noted that we have variance in the net income between FI & COPA ,can you advise the steps should be follow to trace this variance
Please advise

Hi
there is no standard way of doing this... Depends largely on how you have designed the system.. But a broad outline can be as below
1. Check whether all your P&L accounts are cost elements where required.. GLs like change in WIP, COGS need not be..
2. Check any PGI done but billing not done
3. After period end closing, check if any under/over absorption is there in cost centers... If you are executing KEU5 (COPA assessments), this problem can be over come
4. reconcile your sales revenue in FI-GL and in COPA... SD Billing doc no is updated in both FI and COPA docs
5. Similarly, reconcile COGS...
6. Check if you have reset value/qty fields to zero incase of Dr and Cr memos.. else, in COPA the COGS and Qty also gets adjusted proportionately during dr and cr memo
7. Check if your report matches with KE24 or you would have entered some chars in selection screen which is resulting in filtering of data
Regards
Ajay M

S_ALR_87013148

Hi
When I execute the S_ALR_87013148 report following is message.
No suitable summarization level with data exists
Message no. KN424
Please explain what is summarization level.
thanks

Hi
In COPA, COPA Assessments and COPA Reports are read from Summarised records and not line items.
Hence you need to set up Summarization levels in COPA
Config Steps:
1. You can have SAP provide you the propsed Summarization level by TCode KEDVP
2. Or you can manually create the Summarization levels by TCode KEDV
3. Run Tcode KEDU to create Summarization levels
Regards,
Suraj

KEU3 - Iterative Indicator

Hello -
is there a way to process copa assessment iteratively like there is in cost center to cost center assessments?
your help is greatly appreciated!
Emmas

Hi
In cost center assessments, iterativeness is reqd reason being, one cost center may give as well as receive service to/from the same cost center
In COPA assessments, that is not the case.. you assess sales & admin costs to COPA usually, where in the receiver is customer/product/region/etc... This does not need iterative ness at all
Regards
Ajay M

Assessments to COPA

Hi COPA experts,
In COPA Point of view, when and which situation are Assessments are used.
And
I am using costing based COPA. I am assigned the all condition types to value field.
According all the revenues flow from SD module to COPA.
My doubt is there any alternative way to flow the values from SD module to COPA without assigning the condition types to value fields
Regards
Venkat

Actually, the "second option" is when you distribute costs collected on cost centers to CO-PA.
It is called cost center assessment to profitability analysis.
1) you post costs to cost center (for instance: sales force costs)
2) you define assessment cycles through KEU1 / KEU2 / KEU3
3) you distribute costs (1) to CO-PA using assessment cycles (2) with transaction KEU5.
As you see this process is not connected with SD functionality. It rather uses values from CO-PA
as a basis for cost center assessment.
Best regards,
Mark

CCA Assessments to COPA(KEU5)

Hi All,
If i want to allocate my indirect costs from Cost centers to COPA using assessments and receiver rules is Variable portions and Value Field/Key figure is "Revenue" or Gross Sales.
What is the step by step process for this? How system will allocate costs to COPA, I mean on what basis? My receiving tracing factor Valuefield/Keyfield is "Revenue" or "Gross Sales" and No Scaling.
how system allocate costs from CCA to COPA?
Please explain me steps clearly and any help is appreciated.
Thanks,
Rau

Hiya,
This is basic math and you should be able to work it out on a test server creating your own examples.
Say your Tracing Factor is "Net Sales" and the New Sales to two (for the sake of simplicity) of the PSGs is:
PSG A: $ 1000
PSG B: $ 2000
In KEU5, in the tab "Receiver Tracing Factor", you need to mention the weighing factor for each combination of the Receivers. Assuming these are the only two receivers you defined and you allocated a weighing factor of 100 and 10 to each, the tracing factors are calculated as:
PSG A: Tracing Factor: 1000 * 100 = 100,000
PSG B: Tracing Factor: 2000 * 10 = 20,000
The Sender Tracing Factor is therefore: 100,000 + 20,000 = 120,000
Now, if you have $ 12,000 to assess to the two PSGs based on "Net Sales", the cycle will yield:
PSG A: = 12,000 * (100000 / 120000) = $ 10,000
PSG B: = 12,000 * (20000 / 120000) = $ 2,000
Total Assessed: $ 12,000
Hope this helps.
Cheers.

COPA Extraction

Hi Friends,
Im new2 BI7.
1)Plz provide detailed info on hw 2 go abt for COPA extraction.
2)I need 2 make Customer specific Datasources.So plz guide on this
3)Since my existing Copa reps r frm Report painter/Abap,they just drill down 2 multiple screen,,Is multiple drill down functionality possible in BI?If so plz provide details on hw to make sample drill report.
4)Wat are the crucial steps to take in Copa extraction.
Plz provide any links/ppts/pdf's.
It vll be highly appreciated.
Thanks & Regards.

CO-PA:
CO-PA collects all the OLTP data for calculating contribution margins (Sales, cost of sales, overhead costs)
CO-PA also has power reporting tools and planning functions however co-pa reporting facility is limited to
          Integrated cross-application reporting concept is not as differentiated as it is in BW.
     OLTP system is optimized for transaction processing and high reporting work load has negative impact on the overall performance of the system.
Flow of Actual Values:
During Billing in SD Revenues and Payments are transferred to profitability segments in Profitability Analysis at the same time sales quantities are valuated using standard cost of goods manufactured.
In Overhead cost controlling primary postings is made to objects in overhead cost controlling and assigned to relevant cost object. Actual cost of goods manufactured also assigned to cost objects and at the same time performing cost centers are credited
The Production Variances calculated for the cost objects i.e. the difference between the actual cost of the goods manufactured and the standard costs are divided into variance categories and settled to profitability segments (example production orders).
What are the top products and customers in our different divisions. This is one of the typical questions that can be answered with CO-PA Module.
Characteristics are the fields in an operating Concern according to which data can be differentiated in Profitability Analysis.
Each characteristic in an operating concern has a series of valid characteristic values.
Profitability is a fixed combination of valid characteristic values.
Characteristics:
Some Characteristics are predefined in Operating concern like Material, Customer, and Company Code. In addition to these fixed characteristics we can define up to 50 characteristics of our own. In most cases we will be able to satisfy our profitability analysis requirements with between 10 to 20 Characteristics.
Value Fields:
Key Figures like revenue, cost of goods sold, overhead costs are stored in value fields.
Organizational Structure:
The Value fields and Characteristics that are required to conduct detailed analysis vary from industry to Industry and between Individual Customers.
In CO-PA we can configure structure of one or more operating concerns in each individual installation.
An operating concern is an Organizational Structure that groups controlling areas together in the same way controlling areas Groups Companys together
Data Base Structures in CO-PA:
Actual Line Item table:      CE1xxxx
Plan Line Items: CE2xxxx
Line Item Contain some information at document level that most cases is too detailed for analysis example CO-PA Document Number, Sales document Number, Posting date.
CO-PA Maintains summarization of data used by all CO-PA functions like reporting, planning, assessments, settlements and so on.
Actual Line Item table:      CE1xxxx
Plan Line Items: CE2xxxx
Line Item Contain some information at document level that most cases is too detailed for analysis example CO-PA Document Number, Sales document Number, Posting date.
CO-PA Maintains summarization of data used by all CO-PA functions like reporting, planning, assessments, settlements and so on.
Segment Table: CE4xxxx
The Characteristics that describes the market are first separated from the rest of the line Items.
Each combination of characteristic vales is stored in profitability segment number. The Link between the profitability segment number and characteristic values is maintained in Segment Table.
Segment Level: CE3xxxx
The Value fields are summarized at profitability segment and period levels and stored together with these fields in Table CE3xxxx.
This table contains total values of the period for each Profitability segment number.
Storage Procedure:
We can compare an operating Concern associated by segment table and segment level to an Info cube. Info cube comprises Dimension Table Segment Table) and the fact table (Segment Level).
Unlike Fact table the segment level key contains other keys like processing type in addition to the key field from the segment table.
Characteristics in Info Cube correspond to characteristics (Or Attributes) in Info Cube.
Value fields can be regarded as a Key Figures.
Summarization level in Operating Concern have the same function as aggregates for an Info Cube, the difference is that aggregates for Info Cube are managed together with the Info Cube Itself while summarization levels are updated at regular intervals usually daily.
Line Items in CO-PA is comparable with Operational Data Store
Data Staging Overview:
To Provide Data Source for BW all CO-PA Data Sources must be generated in the Source System.
Data Sources can be defined at Operating Concern and client level.
Data Source contains the following Information
Name of the Operating Concern
Client
Subset of the Characteristics
Subset of the Value fields
Time Stamp which data has already been loaded in to BW.
Creating Data Source:
Since Data Source is always defined at operating concern and Client levels a standard name is always generated which starts with 1_CO_PA_<%CL>_<%ERK . We can change this name if necessary however the prefix 1_CO_PA is Mandatory.
Data Source-Segment Table:
Characteristics from the segment table are the characteristics that are maintained in transaction KEQ3.
By Default all characteristics are selected.
Data Source-Accounting Base:
When we generate CO-PA Data Source select accounting based option.
Fields KOKRS, BUKRS, KSTAR are compulsory.
There are no Characteristics available for line Items because accounting based data sources do not contain characteristics.
There are no value fields or calculated key figures available
KOKRS and PERIO must be selected as selection fields.
Hope it will helps you........

Copa flow of actual values

Hi all,
In our COPA, we have some value field that are linked to SD documents and assessments from cost center. The issue is that the SD documents and the assessed documents have different prefixes. Is it possible to match the prefix, so that the same prefix is used for both, the SD documents and the assessed documents?
Thanks
Anne

HI,
SAPNET note 33178 describes the +/- sign logic in CO-PA. In line with that note, I suggest to do not assign SD-values and CO-values to the same CO-PA value field.
If you REALLY want to change +/- signs you can do that in COPA005 enhancement project by multiplying values with -1 but I guess this reates more problems than it solves.
best regards, Christian

COPA Sign Handling

Hi I have gone through some threads already...and understood how sign handling works but I still have some questions.
My current setting +/- not turned on in KE4I
1) I have a sales deduction on a billing document that comes as a +ve value in COPA and IF I create a creditmemo for the same same sales deduction, -ve value flows to COPA. In reporting values from Billing and Values from Credit memo net off each other becasue of different signs.
Even If I turn on +/- in KE4I, it doesnt help cause the scenarios will be just oposite.
2) For the same sale deduction If I make a FI posting a +ve value flows to COPA as its an expense with CE category 12.
How can we achieve the consistancy across all sources. Under what circumstances having multiple value fileds help.
Thanks
KP

This is probably the most confusing part in SAP....
The way that I have caified it in my mind is that the system tries to keep the sign in COPA positive.
So for revenue (price) condition types, a CR in FI will be positive in COPA
For discount (Discount) condition types, a DT in FI will be positive in COPA
For direct postings, assessments and settlements, a DT in FI will be positive in COPA
Now for the exceptions:
For expense reimbursements - I have always only used it as part of accruals, then the +/- indicator needs to be on, and then the sign behaves like it does for revenues.
If a condition type can be either positive or negative, OR
if a condition type appears more than once in a pricing procedure, with differing signs,
then the +/- indicator also needs to be switched on.
What I am busy doing is building a spreadsheet with all possible combinations of condition class, poting in FI and =/- indicator, with postings that actually takes place. Hopefully I will understand it once I have a complete scenario.

About COPA Datasources

Hi Guys,
Can anybody please clear my doubts about like
            what is "Field Name for Partition",
            "Whar is the segment level"
            "What is segment table"
            "What is the Actual Item data"
            "What is the Plan Item Data"
            " Whow to set the delta for COPA Data Source
                     (setting up Time Stamp with limitation)
Thanks in advance
Peter

CO-PA collects all the OLTP data for calculating contribution margins ( Sales, cost of sales, overhead costs)
CO-PA also has power reporting tools and planning functions however co-pa reporting facility is limited to
Integrated cross-application reporting concept is not as differentiated as it is in BW.
OLTP system is optimized for transaction processing and high reporting work load has negative impact on the overall performance of the system.
In CO-PA we can configure structure of one or more operating concerns in each individual installation.
Actual Line Item table: CE1xxxx
Plan Line Items: CE2xxxx
Line Item Contain some information at document level that most cases is too detailed for analysis example CO-PA Document Number, Sales document Number, Posting date.
CO-PA Maintains summarization of data used by all CO-PA functions like reporting, planning, assessments, settlements and so on.
Segment Table: CE4xxxx
The Characteristics that describes the market are first separated from the rest of the line Items.
Each combination of characteristic vales is stored in profitability segment number. The Link between the profitability segment number and characteristic values is maintained in Segment Table.
Segment Level: CE3xxxx
The Value fields are summarized at profitability segment and period levels and stored together with these fields in Table CE3xxxx.
This table contains total values of the period for each Profitability segment number.
We can compare an operating Concern associated by segment table and segment level to an Info cube. Info cube comprises Dimension Table Segment Table) and the fact table ( Segment Level).
Unlike Fact table the segment level key contains other keys like Processing type in addition to the key field from the segment table.
Characteristics in Info Cube corresponds to characteristics( Or Attributes) in Info Cube.
Value fields can be regarded as a Key Figures.
Summarization level in Operating Concern have the same function as aggregates for an Info Cube, the difference is that aggregates for Info Cube are managed together with the Info Cube Itself while summarization levels are updated at regular intervals usually daily.
Line Items in CO-PA is comparable with Operational Data Store
Characteristics from the segment table are the characteristics that are maintained in transaction KEQ3.
By Default all characteristics are selected.
When we generate CO-PA Data Source select accounting based option.
Fields KOKRS, BUKRS, KSTAR are compulsory.
There are no Characteristics available for line Items because accounting based data sources do not contain characteristics.
There are no value fields or calculated key figures available
KOKRS and PERIO must be selected as selection fields.

Summarisation levels in copa

dear sap gurus,
can any explain me how summarisation levels in copa are useful.if any one has documentation on this pls forward to [email protected]
regards,
siva

Hi Sivasai
COPA summarization levels are defined to optimize the system performance. The uses which I could understand are as follows
1) You must have defined characteristics required in COPA reporting. Now u can summarize COPA reports at a particular characteristic level - System sums up the value fields and populates considers the summarized values at level chosesn for summarization
2) When u do create planning layouts - here u define layouts whereve u enter plan values for sales qty, values, costs etc at ind product level or at product hierarchy level. If u plan at hierarchy level u must hv defined the basis of distribution. This takes care of detailed planning. Now if u wish to transfer COPA sales plan values to SOP - u can either transfer at product level or total level. Here u can define separate summarization level so that system consdiers the plan values and posts to SOP
3) Similarly u can do this for cost center assessments too
4) Before u do summarization levels u need to execute programme RKETRERU in SE38. On running this programme the user defined levels are considered for summarization
Its an optional choice - depending on the number of products, complexity of planning, and other factors
Appreciate if someone in the forum can add their views on the above subject
Hope the above clarifies - pls assign points as a way to say thanks

CCA Overhead transfers to COPA

Hi All,
If i want to allocate my indirect costs from Cost centers to COPA using assessments and receiver rules is Variable portions and Value Field/Key figure is "Revenue" or Gross Sales.
What is the step by step process for this? How system will allocate costs to COPA, I mean on what basis? Any ideas.
Please explain me steps clearly and any help is appreciated.
Thanks,
Rau

Hi PV,
My receiving tracing factor Valuefield/Keyfield is "Revenue" or "Gross Sales" and No Scaling.
how system allocate costs from CCA to COPA?
Thanks,
Rau

FF downloaded some update and now I get error message saying update cannot be installed until I get rid of extra FF copies on computer-but I DON"T have any extra copies. I cannot even uninstall the only FF I now have!

I have a Toshiba laptop, Windows & Home Premium Edition operating system. I had FF 3.6.3 installed and up until 6:00 today it was sort of working properly. I find out later that my huasband cannot even open the browser, as every time he does, a dialog box opens up whcih says "UPdate cannot be installed. Please make sure no other copies of FF are running on computer, then restart FF to try again." But I do not have any other copies of FF. I really do not like it when FF auto installs stuff without my permission. Many times this stuff is downloaded and installed, only to raise havoc with my computer.

Try a smc reset:
http://support.apple.com/kb/HT3964

COPA reporting with open and closed projects

Dear All,
I am designing a COPA solution for an infrastructure providing company using project systems and posting to/settling out of projects on a monthly basis. Projects run for long periods and continually incurr costs and earn revenue untill they are closed. The requirement is to report by common characteristics (say customer group) and separately for open and closed projects. My issue is how to separate the line items of projects where status changed to closed (having posted with the status REL previously), from the open ones, without entering the projects individually in the selections screen.
Any ideas will be greatly appreciated.
Thanks,
Maddy

Dear Satya,
http://help.sap.com/saphelp_erp2005/helpdata/en/75/ee0bbd55c811d189900000e8322d00/content.htm
An item of a purchase requisition is only regarded as Closed if the requested order quantity has been included in a purchase order.
You can also set an item to Closed manually. <b>This item will then not be taken into account by the materials planning and control system.</b>
You can set the Closed indicator manually at the following points (it can later be cancelled if necessary):
When changing a purchase requisition, on the item detail screen
When creating a purchase order referencing a requisition, on the item detail screen of the PO
You can still create purchase orders by referencing a requisition if this indicator has been set in the requisition concerned.
The indicator can also be set in the case of automatic PO generation from purchase requisitions. On the initial screen of the requisition, you can specify that the requisition is to count as closed as soon as an associated purchase order has been generated, even if the complete quantity requested has not been ordered, for example (Set reqs. to "closed" indicator).
Analyses of Purchase Requisitions:
http://help.sap.com/saphelp_erp2005/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm (visit section under Reporting in Purchasing)
Hope this will help.
Regards,
Naveen.

COPA assessments

Similar Messages

Maybe you are looking for