Difference Between Cost and Account Based COPA

Hi
What is the difference between Cost and Account based COPA from a BI perspective ( both functionally and technically)
Thanks
Rashmi.

Hi Rashmi,
Greetings.
There is lot of reading material available on forums and help.sap.com
For start you can try with this:
Link:[http://help.sap.com/saphelp_46c/helpdata/en/7a/4c37ef4a0111d1894c0000e829fbbd/content.htm]
Thanks
Sachin

Similar Messages

Cost and account based copa

hi,
what is the difference for cost bases copa and account based copa?
thanks

In costing based COPA the values are captured at PGI where as in Account based copa teh values are captured at the time of Invoice.

Differences between Costing based COPA and Account based COPA

Hi,
I wanted to know the main differences between Costing based COPA and Account based COPA?
For which scenarios account based COPA used and for which scenarios costing based copa used.
please guide me
sateesh

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

Costing Based And Account based COPA - Need Assistance

Hello All,
In our project, with no other option we are planning to implement both costing based and account based COPA. I have been told that it is not recommended by SAP because for every entry there will two line items, one in cost based and another in account based (Correct me if I am wrong). But I could not understand why it is creating 2 line items in COPA. - Please help to understand this concept with an Example.
Thanks
PM

Hi
Costing based and account based COPA serve the same purpose... analyze profitability of the product ....
Costing based COPA should always be preferred over account based COPA, as it provides greater flexibility, some extra features, some extra planning mechanism and faster reports
Following are the point of differences between Costing based vs. Account based copa (ABC)
1. Account based copa uses transaction tables (COEP, BSEG) and hence affects performance of CO transactions.CBC takes values from CE1XXXX to CE4XXXX tables. XXXX means Operating Concern name.
2. Estimated / Statistical values not possible in ABC, say, calculating frieght upon invoice on a thumb rule basis to have better view of profitability per customer.. no valuation strategy in Accounts based COPA..
3. Reports based on line items not possible in ABC.. possible in CBC.
4 Actual Top Down distribution only available in CBC not in ABC .
5. Revaluation of actual data to plan data is not available in ABC
6. No key figure schemes are available in ABC
7. In ABC, settlement cost elements are used to settle values to prof segments unlike value fields in CBC
8. Production variance / COGS accounts shud be defined as cost element in ABC.
System creates a document for each type of COPA as it stores values in different tables and what you can do with this data also differs like you can do TOP down in Costing Based Copa..
Hence, you will have two COPA documents always......................
Fot further clarifications .. please revert back..
Regards
Sarada

Differance between the Cost based costing and Account based costing

Hi,
What is the Differance between the Cost Based Costing and Account Based Costing ?

You can check sap note 69384
COSTING-BASED PROFITABILITY ACCOUNT-BASED PROFITABILITY
ANALYSIS ANALYSIS
OBJECTIVE
o profitability and sales accounting
o evaluation of market segments (for example,
customers, product groups, sales areas) and corporate
units (for example, division, sales organization) with
regard to their profit or contribution margins
o calculation of profits procedures
- cost-of-sales accounting
- interim and reconciled sales report
- periodic and transaction-based allocation
- Profitability Analysis on the basis of full and
direct costs
o posted and costing-based values o account-based values
o can be reconciled with FI for o always reconciled with
account groups (revenues, sales FI on account level
deductions, costs of goods
Note 69384 - Information: Account-based Profitability Analysis
manufactured, and so on)
DATA STRUCTURES
o definition of operating concerns o definition of operating
with fixed characteristics and concerns with fixed and useruser-
defined characteristics defined characteristics
and value fields
o cumulative storage by posting o cumulative storage by
periods and weeks posting periods
o storage in operating concern o controlling area currency,
currency (as of Release 4.0 also company code currency
optional in company code currency and transaction currency
if req.)
o user-definable summarization levels
FUNCTIONS
o transfer of profit relevant o transfer of profit-relevant
business transactions from SD, FI activities from SD, FI, CO, MM
CO, MM (revenues, sales deductions (revenues, sales deductions and
and costs organized by value fields) costs organized by accounts)
o Derivation of characteristics from master
data or using derivation rules
o Realignments also for data that is already
posted
o Valuation
(Costs of goods manufactured, imputed
costs and sales deductions)
o sales and profit planning o profit planning
- flexible layout - flexible layout
- periodic distribution - periodic distribution
- valuation, revaluation - forecast procedure
- forecast procedure - top-down distribution
- top-down distribution - simulation
- simulation
o profit analysis by means of 'interactive drill-down
reporting'
- Report Painter
- object list/ranking lists, database schema
- drill-down
- key figure systems
- flexible hierarchies
- navigation between reports
- exception reporting
- ABC analyses
- Exporting (Excel, Winword, Mail)

Difference between costing and expenses

Hi,
what is the difference between 'Costing' and 'Expense' in terms of Sales Order and Customer Project ?
Thanks.

Hi Le,
Costing is genaral terma which is used for exact price of material ...and another charges over that comes in expanses...like Cost of Tansformer is 5000..and Freight charges on that is Rs. 200..here cost of transfer is 5000 and expense is 200 and overall price of transformer is 5200.........
Rewards the ponts if useful
Regards
Rama Shanker Sharma

Difference between element and identity based version

Can anybody tell me the difference between elment and identity based version of the Object with any example? which classes implement them?

Hunky322 wrote:
At first it struck me as odd, given how List, Set, and Map define equals, but the part the OP left off clears it up a bit: "..because element-based equality is not always well-defined for queues with the same elements but different ordering properties."This lineSo, you're saying you don't understand the following?
>
Queue implementations generally do not define element-based versions of the equals and hashCode methods but instead inherit the identity-based versions from Object because element-based equality is not always well-defined for queues with the same elements but different ordering properties.
>
Okay, here's the deal.
For a List, equals() is true if both Lists contain the same objects and in the same order. That's pretty straightforward, and it makes sense.
For a Set, equals() is true if both Sets contain the same objects. Order is not considered because Sets are not generally ordered. Again, this it straightforward.
So, you might think that Queue might define equals in a similar fashion--either if both Queues contain all the same elements, or if they contain all the same elements in the same order. However, this doesn't really work very well. Since ordering is an important part of a Queue, the ordering should be considered for equality. However, unlike Lists, two different Queues containing the same objects might define ordering differently. One might be a FIFO and the other might be a PriorityQueue, so how do you compare those two queues for equality?
There are no clear-cut rules for equality between two arbitrary Queues, so the Queue interface does not define an equals method that's related to the contents of the Queues.

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

Whats the difference between Cost and (%CPU)

whats the difference between Cost (%CPU) in the newest version of the explain plan and just Cost in the Older versions?

Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
PL/SQL Release 11.1.0.6.0 - Production
CORE 11.1.0.6.0 Production
TNS for 32-bit Windows: Version 11.1.0.6.0 - Production
NLSRTL Version 11.1.0.6.0 - Production
======================================================
i replaced this plan.....
create table PLAN_TABLE (
     statement_id      varchar2(30),
     timestamp      date,
     remarks      varchar2(80),
     operation      varchar2(30),
     options      varchar2(30),
     object_node      varchar2(128),
     object_owner      varchar2(30),
     object_name      varchar2(30),
     object_instance numeric,
     object_type varchar2(30),
     optimizer varchar2(255),
     search_columns number,
     id          numeric,
     parent_id     numeric,
     position     numeric,
     cost          numeric,
     cardinality     numeric,
     bytes          numeric,
     other_tag varchar2(255),
     partition_start varchar2(255),
partition_stop varchar2(255),
partition_id numeric,
     other          long,
     distribution varchar2(30));
for this one...
create table PLAN_TABLE (
statement_id varchar2(30),
plan_id number,
timestamp date,
remarks varchar2(4000),
operation varchar2(30),
options varchar2(255),
object_node varchar2(128),
object_owner varchar2(30),
object_name varchar2(30),
object_alias varchar2(65),
object_instance numeric,
object_type varchar2(30),
optimizer varchar2(255),
search_columns number,
id numeric,
parent_id numeric,
depth numeric,
position numeric,
cost numeric,
cardinality numeric,
bytes numeric,
other_tag varchar2(255),
partition_start varchar2(255),
partition_stop varchar2(255),
partition_id numeric,
other long,
distribution varchar2(30),
cpu_cost numeric,
io_cost numeric,
temp_space numeric,
access_predicates varchar2(4000),
filter_predicates varchar2(4000),
projection varchar2(4000),
time numeric,
qblock_name varchar2(30),
other_xml clob
);

Difference between ID and Role based Administration - Firefighter 5.3

In GRC AC 5.3 Firefighter, security guide, there are two sections for role design,
1. Firefighter Role based Administration
2. Firefighter ID based Administration
Can someone explain what is the difference between the two?
I have read the documentation, but it does not have a clear description of the
differences between the two.
Please help.
Thanks

HI Prakash,
Though both of them eventually achieve the same function, that is giving access rights to the user for a certain period under monitring these differ based on the following:
1. Firefighter Role based Administration
You identlfy a particular role as a firefighter role and give it to the user.
2. Firefighter ID based Administration
You create a separate user altogether and give the normal dialog user, the access to this user's authorization.
For the implication that both of these have and the differences or comparisons between using 1 & 2, I would suggest you do a bit of Mock testing for both of these. Also, there are a lot of posts related to this on the forum already, which you can refer to, for getting a more detailed idea on this topic. Unlimately, it depends on organization to organization which methodology they folow as per what suits them, according to features which both have. But generally what is preferred is Number 2.
Regards,
Hersh.

Main Difference Between EDI and IDOC Based On RFC

In IDOC ,RFC is Used to define the characteristics of communication links to a remote system on which a functions needs to be executed.
What About EDI ?

Hi Saurabh,
Check this..Hope it helps you.
EDI is nothing but Electronic data interchange. SAP will support EDI through Intermediate documents (IDOCS).
EDI (Electronic Document interchange) - EDI is the electronic exchange of business documents between the computer systems of business partners, using a standard format over a communication network.
EDI is also called paperless exchange.
Advantages:
Reduced Data entry errors
Reduced processing time
Availabilty of data in electonic form
Reduced paperwork
Reduced Cost
Reduced inventories and better planning
Standard means of communications
Better business process
EDI has two process
1. Outbound process
2. Inbound process
OP:
1.Application document is created.
2.IDOC is generated
3.IDoc is transferred from SAP to Operating system layer
4.Idoc is converted into EDI standards
5.Edi document is transmitted to the business partner
6.The Edi Subsystem report status to SAP
IP:
1.EDI transmission received
2.EDI document is converted into an IDOC
3.IDOC is transferred to the SAP layer
4.The application document is created
5.The application document can be viewed.
IDOC:
IDOC is a container that can be used to exchange data between any two process.
Each iDoc is assigned a unique number for tracking and future reference.
iDoc Consist of several segments,and segments contain several fields.
iDoc contains the following three type of records...
1.One Control Record.
2.One or many Data Record
3.One or many Status record.
PORT:
Port is used in the outbound process to determine the name of the EDI subsystem program,the directory path where the idoc file will be created at the operating system level,the idoc file names and the rfc desinations.
RFC Destination:
Used to define the characteristics of communication links to a remote system on which a functions needs to be executed.
Partner Profile:
Partner profile specified the various componets used in an outbound process ( Partner number,IDoc type,message type,Port,Process code),the mode in which it communicates with the subsystem(batch or immediate) and the person to be notified in case of errors.
Message Control
Used in pricing,account determination,material determination,and output determination.The message control component enables you to encapsulate business rules with out having to write abap programs.
Process:
Setup RFC destinations SM59
Port Destinations WE21
Partner Profile WE20
Message control NACE
Purchase Order ME21
Check IDOCs WE02,WE05
Explain to me about Idoc?
IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system.
IDocs are used for asynchronous transactions: Each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database.
Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions.
A large enterprise's networked computing environment is likely to connect many geographically distributed computers to the main database. These computers are likely to use different hardware and/or operating system platforms. An IDoc encapsulates data so that it can be exchanged between different systems without conversion from one format to another.
IDoc types define different categories of data, such as purchase orders or invoices, which may then be broken down into more specific categories called message types. Greater specificity means that an IDoc type is capable of storing only the data required for a particular transaction, which increases efficiency and decreases resource demands.
An IDoc can be generated at any point in a transaction process. For example, during a shipping transaction process, an IDoc may be generated that includes the data fields required to print a shipping manifest. After a user performs an SAP transaction, one or more IDocs are generated in the sending database and passed to the ALE communication layer. The communication
layer performs a Remote Function Call (RFC), using the port definition and RFC destination specified by the customer model.
The IDoc is transmitted to the receiver, which may be an R/3, R/2, or some external system.
Re,Manas

Differences between billing and accounting document with down paym. request

Hello to all
We are creating down payment request billing from one sales order with two sales order items that has different tax classification material.
The billing document is created correctly (with the same value for each item), not as the account document.
If you compare the value from the billing document to the account document is not the same. In the account document the system decreases the amount of the first item with the tax amount of the second item and the same for the second item (the amount of the second item decreases the amount of the second item with the tax amount of the first item).Then the tax amount of the two items is right.
If the two items have the same tax classification material, it works fine.
Can anyone help me?, is it a problem with the payment request billing?.
Thanks in advance.
Edited by: tonnetti pablo on Jan 8, 2008 9:46 AM

Hi,
The following Customizing settings have to be made for down payment processing:
Settings for the billing plan To activate the billing plan function, maintain the materials, for which you wish to process down payments, with item category group 0005 (milestone billing). This gives the item type TAO via item type determination. The item type TAO calls up the billing plan function.
You need to implement the following activities in the billing plan for down payments:
Maintain deadline category This determines the billing rule (percentage or value down payment) for the down payment request. The system assigns billing type FAZ (payment request) defined in the standard system with billing category P. (For the billing type FAZ there is the cancellation billing document type FAS in the standard system).
Maintain the deadline proposal Use the down payments that are due for the proposed deadlines.
Maintaining a Pricing Procedure with the Condition Type AZWR:
In the standard system the condition type AZWR is delivered for the down payment value already provided but which has not yet been calculated. You must include this condition type in the relevant pricing procedure before output tax.
Enter condition 2 (item with pricing) and the calculation formula 48 (down payment clearing value must not be bigger than the item value) for the condition type AZWR.
Before the condition AZWR you can create a subtotal with the base value calculation formula 2 (net value). If the condition AZWR is changed manually, you can get information on the original system proposal from the subtotal.
Maintain the printing indicator The pricing procedure can not be marked as a transaction-specific pricing procedure (field Spec.proc.) The condition type AZWR has the calculation type B (fixed amount) and the condition category E (down payment request / clearing).
Maintaining the Billing Document In the standard system there is the billing type FAZ (down payment request) and the billing type FAS for canceling . The down payment is controlled using the billing category P of the billing type. A billing type becomes a down payment request when the billing category P is assigned. You have to maintain blocking reason 02 (complete confirmation missing) for the billing documents and assign it to billing type FAZ.
Copying control Copying requirement 20 must be entered in copying control at item level for the down payment request. In the standard system the order type TA for copying control is set up according to the billing type FAZ for the item category TAO.
Copying requirement 23 must be entered in copying control at item level for down payment clearing. In the standard system the order type TA for copying control is set up according to the billing type F2 for the item category TAO.
Financial Accounting settings A prerequisite for down payment processing is that the account is assigned to the underlying sales document. To do this, change the field status settings in Customizing as follows:
Set reconciliation accounts (transaction OBXR) For the `received down payments and `down payment requests from
the G/L accounts you have selected, you should assign the field status definition G031.
Maintain accounting configuration (transaction OBXB) For the down payments (posting key ANZ in the standard system) and the output tax clearing (posting key MVA in the standard system), you must maintain the posting key.
You must also carry out a G/L account number assignment for the tax account.
Maintain the posting key (transaction OB41) For posting key 19, set the sales order as an optional field
Maintain the field status definition (transaction OB14) For field status variant 0001, field status group G031, set the
sales order as an optional field
Assign the company code to the field status variants (transaction OBC5)
Regards,
Siddharth.

Any difference between rfc4448 and rfc4665-based ethernet vpws?

thanks

Hello Karen,
both RFCs conform to the pseudowire service model defined in previous RFC 3985.
so regarding this aspect they share the same root. RFC 4448 is more focused on EoMPLS, RFC 4665 describes requirements in service provider networks to support point -to-point and point-to-mulitpoint (VPLS) services.
Hope to help
Giuseppe

Costing based and account based

HI All
Kindly let me know difference between costing based copa and accounting based copa with examples
Thanks & Regards
Phaneendra

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.
You can also use both of these types of CO-PA simultaneously.
(courtesy: help.sap.com)
It is strongly recommended, however, that you do not activate both types of CO-PA. The
major reason being is that you will have significant table size impacts. You must be careful
with account based CO-PA as this creates additional line items in the existing CO tables of
COEP (actual), COEJ (plan), COSP & COSS (summary records). Hence if you want to do any
cost center reporting, say, from any of these existing tables you will run the risk that
performance will be degraded by these additional and unnecessary records.
The only advantage of account based over costing based CO-PA is it's ability to
automatically reconcile back to FI, in much the same manner as you would reconcile
cost center accounting back to FI. However you don't have the flexibility in account
based CO-PA to perform valuations using product cost estimates etc. as you do in
costing based CO-PA. If the reason you were advised to turn on account based CO-PA
as well as costing based was to facilitate reconciliation, it is suggested that you look
at alternatives that won't have the same negative impacts that turning on account
based would have. In addition to the serious table space issues, it is not that easy to
turn on and off account based at will (especially in production).
Instead what you should look at doing is creating a series of reports that enable you to
reconcile costing based CO-PA back to CCA/PCA and FI, if this is required. The complexity
of the costing based functionality you have used will determine the complexity of the
reports that will be needed to reconcile back, but it can be done without turning on
account based CO-PA.

Difference Between Cost and Account Based COPA

Similar Messages

Maybe you are looking for