Profitability Analysis - Account based

Hello Expertise,
I was running COPA on Costing Based it was running sccessfully i was able to see the reflection in VF02.But now when i changed it to Accounting based i cannot see the reflection in VF02.
So please help me what extra settings i need to do for the reflection to be seen in VF02
Regards,
Khadeer

Hi,
See when i run the cycle from VA01 then VL01N and the VF01 the documents that got generated were
ACCOUNTING
PROFIT CENTER
CONTROLLING
PROFITTABILITY ANALYSIS
THIS IS WHEN I WAS RUNNING WITH COST BASED COPA.
Now when I set the COPA in KEKE to ACCOUNT BASED and also do the REQ change in KEA0 i.e mark only ACCOUNT BASED and regenerated again and Run the above cycle from VA01 to VL01n to VF01 the doc that got genrated
ACCOUNTING
PROFIT CENTER
CONTROLLING
I am not able to see the COPA during billing.
Regards,
Khadeer

Similar Messages

Costing-accounting based COPA then back to costing COPA

Dear all,
I would like asking about costing based-accounting based Profitablity Analysis.
In case, I used and activate both costing based and accounting based profitability analysis. Could i back only use costing based again, even the both copa document already posted?
I am worried if system avoid untick the indicator of accounting based and back to active flag=2. It is important i ask in this forum because we only have 1 server for development and sandbox.
Best regards,
Dewi

Hi Dewi
You will get message (warning):
Message no. KE107
Diagnosis
Operating concern XXXX is set up for both forms of Profitability Analysis (costing-based and account-based).
You have set an active indicator for only one form. Note that no data will be transferred to the form of Profitability Analysis that you did not activate. If this form is activated at a later point, the data posted up to that point will be missing.
You can change active flag (customizing request) any time.
Dejan

Account Based Profitability Analysis

Hi,
I am mapping characteristic fields of account based profitability analysis. I have been given fields such as KMLAND to map into BI fields.My question is how do i map the key figures. What fields in account based profitability analysis are key figures, are they value fields? Do i need a list field names of value fields to map it into BI.Some one mentioned something about cost elements.
Thanks
TJ

Hello Tee Jay,
Cost Element is a key field in ECC. That means its char. in BW. What are the infoobjects that you have in your DSO or cube n BI.
Do you have 0COSTELMNT or 0GL_ACCOUNT? If so, then you map Cost element field from SAP to one of the above char. in BW.
By Revenue, do you mean a value field in R/3? If so, it will have to be mapped to key figure in BI.
Hope that helps.

Profitable analysis and cost accounting doc

hi,
May i know why some of billing in vf03 only have cost accounting doc whereas some have both profitable analysis and cost accounting doc in document category when click accounting button.
thanks

Hi,
Please check the Sales Condition Types assigned to Value fields. May be some of your condition types are assigned to Value fields and some of are not. Go to KE4I.
Also check the PA Transfer Strcuture in KEI2, Whether relevant Cost Elements are assigned to Value Fields or not.
Regards,
Jigar

COST ELEMENTS IN ACCOUNT BASED COPA

Hi all,
1. I understand that all FI/GL accounts correspond to COST   ELEMENTS in COPA.
2. I also understand that there are NO value fields in an Account Based Profitability Analysis.So there is no VALUE FIELD to KEY FIGURE mapping.
3. My question is: how do we map each individual GL account into BI?
4. If we dont map each individual GL account, how do we report these accounts in BI?
This part of Account based has been very confusing. I have searched numerous posts, but they all have the same answers, none that explains how we handle the numeric fields of account based profitability analysis.
Cheers
TJ

You will have a KF lets say amount
In account based COPA your Cost and revenue elements will identify what does the value in this KF corresponds to.
your report will look something like below:
Ex:
Cost and Revenue Element #     Amount
800 - Revenues                     1,000,000
808 - Sales deductions             100,000
800 - 808 = Net Revenue            900,000
893 - Cost of Sales               90,000
231 - Price Difference              10,000
Total                               1,000,000
You may get amount from source system in 2-3 diff currencies like controlling area curr, transaction curr...
Sometimes range of accounts correspond to a value. Ex: Accounts 800-900 resemble revenue.
In such a case you may create Text node in hierarchy called revenue and use it in report (if no hierarchy available from the source system) or create selection in the report.,

Account based COPA datsource taking long time to extract data

Hi
We have created a Account based COPA datasource but it is not extracting data in RSA3 even though the underlying tables have data in it.
If the COPA datasource is created using fields only from CE4 (segment ) and not CE1 (line items ) table then it extracts data but tat too after very long time.
If the COPA datasource is created using fields from CE4 (segment ) and CE1 (line items ) table then it does not extarct any records and RSA3 gives a time out error..
Also job scheduled from BW side for extracting data goes on for days but does not fetch any data and neither gives any error.
The COPA tables have huge amount of data and so performance could be a issue. But we have also created the indexes on them. Still it is not helping.
Please suggest a solution to this...
Thanks
Gaurav

Hi Gaurav
Check this note 392635 ,,might be usefull
Regards
Jagadish
Symptom
The process of selecting the data source (line item, totals table or summarization level) by the extractor is unclear.
More Terms
Extraction, CO-PA, CE3XXXX, CE1XXXX, CE2XXXX, costing-based, account-based,profitability analysis, reporting, BW reporting, extractor, plug-in, COEP,performance, upload, delta method, full update, CO-PAextractor, read, datasource, summarization level, init, DeltaInit, Delta Init Cause and Prerequisites
At the time of the data request from BW, the extractor determines the data source that should be read. In this case, the data source to be used depends on the update mode (full initialization of the deltamethod or delta update), and on the definition of the DataSources (line item characteristics (except for REC_WAERS FIELD) or calculated key figures) and the existing summarization levels.
Solution
The extractor always tries to select the most favorable source, that is,the one with the lowest dataset. The following restrictions apply:
o Only the 'Full' update mode from summarization levels is
supported during extraction from the account-based profitability
analysis up to and including Release PI2001.1. Therefore, you can
only everload individual periods for a controlling area. You can
also use the delta method as of Release PI2001.2. However, the
delta process is only possible as of Release 4.0. The delta method
must still be initialized from a summarization level. The following
delta updates then read line items. In the InfoPackage, you must
continue to select the controlling area as a mandatory field. You
then no longer need to make a selection on individual periods.
However, the period remains a mandatory field for the selection. If
you do not want this, you can proceed as described in note 546238.
o To enable reading from a summarization level, all characteristics
that are to be extracted with the DataSource must also be contained
in this level (entry * in the KEDV maintenance transaction). In
addition, the summarization level must have status 'ACTIVE' (this
also applies to the search function in the maintenance transaction
for CO-PA data sources, KEB0).
o For DataSources of the costing-based profitability analysis,
30.03.2009 Page 2 of 3
SAP Note 392635 - Information: Sources with BW extraction from the CO-PA
data can only be read from a summarization level if no other
characteristics of the line item were selected (the exception here
is the 'record currency' (REC_WAERS) field, which is always
selected).
o An extraction from the object level, that is, from the combination
of tables CE3XXXX/CE4XXXX ('XXXX' is the name of the result area),
is only performed for full updates if (as with summarization
levels) no line item characteristics were selected. During the
initialization of the delta method this is very difficult to do
because of the requirements for a consistent dataset (see below).
o During initialization of the delta method and subsequent delta
update, the data needs to be read up to a defined time. There are
two possible sources for the initialization of the delta method:
- Summarization levels manage the time of the last update/data
reconstruction. If no line item characteristics were selected
and if a suitable, active summarization level (see above)
exists, the DataSource 'inherits' the time information of the
summarization level. However, time information can only be
'inherited' for the delta method of the old logic (time stamp
administration in the profitability analysis). As of PlugIn
Release PI2004.1 (Release 4.0 and higher), a new logic is
available for the delta process (generic delta). For
DataSources with the new logic (converted DataSources or
DataSources recreated as of Plug-In Release PI2004.1), the line
items that appear between the time stamp of the summarization
level and the current time minus the security delta (usually 30
minutes) are also read after the suitable summarization level
is read. The current time minus the security delta is set as
the time stamp.
- The system reads line items If it cannot read from a
summarization level. Since data can continue to be updated
during the extraction, the object level is not a suitable
source because other updates can be made on profitability
segments that were already updated. The system would have to
recalculate these values by reading of line items, which would
result in a considerable extension of the extraction time.
In the case of delta updates, the system always reads from line
items.
o During extraction from line items, the CE4XXXX object table is read
as an additional table for the initialization of the delta method
and full update so that possible realignments can be taken into
account. In principle, the CE4XXXX object table is not read for
delta updates. If a realignment is performed in the OLTP, no
further delta updates are possible as they would make the data
inconsistent between OLTP and BW. In this case, a new
initialization of the delta method is required.
o When the system reads data from the line items, make sure that the
30.03.2009 Page 3 of 3
SAP Note 392635 - Information: Sources with BW extraction from the CO-PA
indexes from note 210219 for both the CE1XXXX (actual data) and
CE2XXXX (planning data) line item tables have been created.
Otherwise, you may encounter long-running selections. For
archiving, appropriate indexes are delivered in the dictionary as
of Release 4.5. These indexes are delivered with the SAP standard
system but still have to be created on the database.

Reconciliation of costing based COPA and account based COPA

hi experts,
I want reconciliation statement of A/c based copa and costing based copa through SAP. we have not configured any account based copa reports. now we are manually doing the reconciliation. Please tell me the configuration.
Thanks & regards
jay

HI
Costing-based Profitability Analysis is the form of profitability analysis that groups costs and revenues according to value fields and costing-based valuation approaches, both of which you can define yourself. It guarantees you access at all times to a complete, short-term profitability report.
Account-based Profitability Analysis is a form of profitability analysis organized in accounts and using an account-based valuation approach. The distinguishing characteristic of this form is its use of cost and revenue elements. It provides you with a profitability report that is permanently reconciled with financial accounting
Regards,
Vijayanand Sankaran

COPA Costed and Account based

Hi Experts,
I have running In BW, PA Costed based, and now I need activate PA accounted based extractor.
a) does somebody have any doc or how-to papers, specific about COPA Accounted?
b) can will appear any issue or problem about my current PA costed based loads?
c) how can I see with pa model (costed or account based) is running in the R/3 instalation?
Thank you in adavance!

Hi,
Costing-based Profitability Analysis is the form of profitability analysis that groups costs and revenues according to value fields and costing-based valuation approaches, both of which you can define yourself. It guarantees you access at all times to a complete, short-term profitability report.
Account-based Profitability Analysis is a form of profitability analysis organized in accounts and using an account-based valuation approach. The distinguishing characteristic of this form is its use of cost and revenue elements. It provides you with a profitability report that is permanently reconciled with financial accounting
Hope this helps
Regards,
Aparna

Account Based COPA problems

Hi all,
I activated the Account Based COPA, but why customer & product (which is the fixed characteristics from SAP) can not be taken during the report execution.
Everytime I try to see a report with those characteristics it always come back as unassign field.
Can anyone help me regarding this problems?
Thanks.
Lea

Hi,
Costing-based Profitability Analysis is the form of profitability analysis that groups costs and revenues according to value fields and costing-based valuation approaches, both of which you can define yourself. It guarantees you access at all times to a complete, short-term profitability report.
Account-based Profitability Analysis is a form of profitability analysis organized in accounts and using an account-based valuation approach. The distinguishing characteristic of this form is its use of cost and revenue elements. It provides you with a profitability report that is permanently reconciled with financial accounting.
You can also use both of these types of CO‑PA simultaneously.
Hope this helps.
Rgds
Manish

Planning layout for account based CO-PA

Hi Gurus!
I want to create a new planning layout in profitability analysis to be able to maintain planned values directly in profitabilty analysis on cost element level.
But somehow there is no possibility to plan the value in comany code currency. When selecting costing based co-pa and then calling transaction KE16 -> create new layout, you are asked by the system whether you want to plan in Controlling Area currency or also in company code currency. But, when selecvting account based co-pa this is not possible. You can only choose controlling area currency.
Can somebody explain this?
Thanks

What's the reason to do this?

Customizing Monitor in Profitability Analysis

Hello SAP-team!
What functions are provided by the Customizing Monitor in Profitability Analysis?
ps: thanks to SAP-community!
Eugene

Hi,
Customizing monitor in Profitability analysis as follows..
General topics:
35288 Technical Documentation CO-PA
69384 Account-based Profitability Analysis
199467 New act assignment table as of Release 4.5
2. Master data:
a) Characteristics and value fields:
13377 Naming conflicts in characteristics and value fields
21207 Deleting a charctrstc/value field from an op.concern
40336 Maintaining foreign keys for characteristics
76493 Changing texts of characteristics or value fields
b) Characteristics derivation and submission of characteristics values
32719 Customer hierarchy in CO-PA
33968 SD/CO-PA: Characteristics from sales document tables
36557 SD/CO-PA: Transfer partner functions to CO-PA
62690 Product hierarchy in CO-PA
93652 Info: Variant configuration in CO-PA
134889 Info on derv. of char:Why not all flds avail.?
148609 Char.deriv.:deriv. rule vals miss.aft.upgrade&trnsp.
172740 Techn.docum.charct. derivtn as of Release 4.0
c) Valuation
40408 Valuation for record types 'B' and 'C'
62536 Valuation using conditions in Profitability Analysis
67240 Info: Valuation with material cost estimate
111232 INFO: Valuation for materials valuated separately
144337 INFO rounding differences: Valuation with costing
142628 Behaviour of user exit in periodic valuation
3. Actual data transfer:
20254 Values from SD are not transferred to CO-PA
37114 Incorrect setup/reversal of provisions
33178 +/- sign logic in CO-PA (SD/FI interface)
52849 Transfer of conditions with +/- signs
39635 Profitability segment by substitution exits
64768 FI/CO-PA: Problems with exchange rate differences
87704 Cost-of-goods-sold Reconciliation: FI to Co-PA
83702 Acct assignmt logic sales order proc. - REM
111309 Transfer of quantities into CO-PA
185826 Enhancement COPA0005
a) Correction of data inconsistencies
69370 Clearing data inconsistencies in CO-PA
70718 Correctn of data inconsistency for order recpt
140457 Correcting data inconsstncs in incoming orders
126937 Correction of billing data inconsistency
93051 Restructure of the segment level from line items
4. Planning:
67191 Useful tips on the CO Planning Processor
72110 KE11: Long runtimes/timeout
77476 Information: Top-down planning
124598 CO-PA Planning: FAQs
5. Information system:
21773 Performance in reporting (summarization data)
83204 Usage strategy for summarization levels
136216 Fast rollup for summ. levels for costing-based CO-PA
6. Tools:
134430 Euro conversion and CO-PA
19015 Termination during external data transfer
19410 Characteristic validation during external data transfer
44658 Error with batch input for KE21
40994 Transport Profitability Analysis (CO-PA) to 3.0
52636 CO-PA Customizing transport
128862 Transport Customizing CO-PA in 4.0A/B
131664 Transport of operating concern structures 4.0
144015 Client copy and CO-PA/EC-EIS
65999 Information: Supported ALE scenarios in CO-PA
94458 CO-PA Realignments: documentation
113050 Segment table repair after realignments
127334 Missing archiving of profitability segments
199959 Change assignmt for operating concern
67839 Generating parts of an operating concern environment
69829 Delete operating concern in Release 3.0
106314 Delete operating concern in Release 3.1
562043 - Transfer actual costs to Profitability Analysis
544241 - INFO:Customizing Monitor new fnc 'Report Overview'.
429517 - INFO: Currency translation Billing document -> CO-PA
428563 - Material cost estimate valuatn: Translaton for posting date
400237 - CO-PA INFORMATION: Line item in company code currency
199959 - Information: change assignmt for operating concern
199467 - Info: New act assignment table as of Release 4.5
185826 - Information: Enhancement COPA0005
172740 - Info.:Techn.docum.charct.derivtn as of Release 4.0
148609 - Char.deriv.:deriv.rule vals miss.aft.upgrade&trnsp.
144337 - INFO rounding differences: valuation with costing
144015 - CC-INFO: client copy and CO-PA/EC-EIS
142628 - Behaviour of user exit in periodic valuation
140457 - Info:Correcting data inconsstncs in incoming orders
136216 - Fast rollup for summ.levels for costing-based CO-PA
134889 - CO-PA Info on derv.of char:Why not all flds avail.?
134430 - Information: Euro conversion and CO-PA
131664 - INFO: Transport of operating concern structures 4.0
128862 - INFO: Transport Customizing CO-PA in 4.0A/B
127334 - Missing archiving of profitability segments
126937 - INFO: Correction of billing data inconsistency
124598 - Info: CO-PA planning: frequently asked questions
113050 - Segment table repair after realignments
111309 - INFO: Transfer of quantities into CO-PA
111232 - INFO: Valuation for materials valuated separately
106314 - Delete operating concern in Release 3.1
94458 - CO-PA Realignments: documentation
93652 - Info: Variant configuration in CO-PA
93051 - Restructuring the segment level from line items
83702 - INFO: Acct assignmt logic sales order proc. - REM
83204 - Usage strategy for summarization levels
77476 - Information: top-down planning
76493 - Changing texts of characteristics or value fields
75334 - INFO:Downloading CO-PA correctn package fm SAPSERV
72110 - KE11: Long processing times / timeout
70718 - INFO:Correctn of data inconsistency for order recpt
69829 - Delete operating concern in Release 3.0
69384 - Information: Account-based Profitability Analysis
69370 - INFO: Clearing data inconsistencies in CO-PA
67839 - Generating parts of an operating concern environment
67240 - Info: valuation with material cost estimate
67191 - Info: Useful tips on the CO Planning Processor
65999 - Information: Supported ALE scenarios in CO-PA
64768 - FI/CO-PA: Problems with exchange rate differences
62690 - Info: product hierarchy in CO-PA
62536 - Info: Conditions in Profitability Analysis
52849 - INFO: Transfer of conditions with +/- signs
52636 - INFO: CO-PA Customizing transport
44658 - Error with batch input for KE21
40994 - INFO:Transprt Profitability Analysis (CO-PA) to 3.0
40408 - Info: Valuation for record types "B" and "C"
40336 - Info: maintaining foreign keys for characteristics
39635 - Info: finding the profitability segment using a substitution
37114 - Incorrect setup/reversal of provisions
36557 - Info SD/CO-PA:transfer partner functions to CO-PA
35288 - Profitability Analysis: Technical Documentation
33968 - SD/CO-PA: Characteristics from sales doc tables
33178 - INFO: +/- sign logic in CO-PA (SD/FI interface)
32719 - INFO: Customer hierarchy in CO-PA
21773 - Performance in Reporting (Summarization data)
21207 - Deleting a charctrstc/value field from an op.concern
20254 - INFO: Values from SD not transferred to CO-PA
19410 - INFO: Char.validity check f.external data transfer
19015 - Termination during external data transfer
13377 - INFO: Naming conflicts in charactrst. & value flds.
Thanks
Prasada

How to Calculate Profitability Analysis ?

Hi
kishore
This is basically a part of Sales and Distribution Module . can u just revert me back with the Answer .
Regards
kishore

Dear kishore
Profitability Analysis (CO-PA) enables you to evaluate market segments, which can be classified according to products, customers, orders or any combination of these, or strategic business units, such as sales organizations or business areas, with respect to your company's profit or contribution margin.
The aim of the system is to provide your sales, marketing, product management and corporate planning departments with information to support internal accounting and decision-making.
Two forms of Profitability Analysis are supported: costing-based and account-based.
Costing-based Profitability Analysis is the form of profitability analysis that groups costs and revenues according to value fields and costing-based valuation approaches, both of which you can define yourself. It guarantees you access at all times to a complete, short-term profitability report.
Account-based Profitability Analysis is a form of profitability analysis organized in accounts and using an account-based valuation approach. The distinguishing characteristic of this form is its use of cost and revenue elements. It provides you with a profitability report that is permanently reconciled with financial accounting.
Thanks
G. Lakshmipathi

PA - Costing-Based and Account-Based

Hi All,
Please tell me what is Costing based PA and Account-based PA.
Thanks
Vinu

Hi,
Costing-Based Profitability Analysis
This type of Profitability Analysis is primarily designed to let you analyze profit quickly for the purpose of sales management. Its 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.
Account-Based Profitability Analysis
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 accounting.
The system posts all revenues and costs to both Financial Accounting and Profitability Analysis at the same time and using the same valuation method. This means that the cost of sales is posted to Profitability Analysis at the point of goods issue.
Regards,
Eli

Distributed Profitability Analysis from HCM system

We have a requirement to provide a distributed profitability analysis (PA) solution (account based) from our SAP HCM system (ECC6) to our backend SAP Finance system (ECC6).
Does anybody know whether this can be done?
I have found general information relating to distributed PA scenarios but none explicitly mention HCM as the source system.
For the scenarios I have found, it mentions using message type CODCMT as part of an ALE solution. Will this apply to HCM or have we got to look at alternatives such as (for example) bespoking the std IDoc solution for the posting of payroll results to include the PA data.
Any help would be greatly appreciated. Points will be allocated.
Regards
Ian

Hi
Posting a COPA document while delivery of goods (VL02N) is not a standard way of COPA value flows.
You can only transfer your billing values only at the time of VF02 and not at VL02N and even it is not logical
Because when you do post goods issue, at that point of time you are not accounting for any revenue. So it is not proper to flow the values into COPA and generate a document at goods issue
One more thing is that accounting entries are automatically generated during VL02N and you cant directly post on COPA using Direct Acct Assgn from FI/MM. It only works when you directly do an FI posting
Hope it gives u an idea
Regards
Ram

TESTING AB PROFITABILITY ANALYSIS

Hi all,
We have configured account based profitability analysis. I was told that there was some data in table COEP available for testing. How do i go about testing this data in BI?
Could some one give me step by step directions?
We are working on BI 7.0 thus have DTP and Transformatins.
Thanks

refer this doc:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/7a5ee147-0501-0010-0a9d-f7abcba36b14
you can also use the same solution once live for reconciliation...
alternatively....
if there are any account based PA report already developed in source system then use them to tie up records with BW...
you can carry out data load and check your data load records against those in table (if they are not many)..
Edited by: sam hennry on Feb 14, 2008 11:33 AM

Profitability Analysis - Account based

Similar Messages

Maybe you are looking for