Account based vs Costing Based - size

[Former Member]

We are currently debating whether to implement Costing Based or Account Based COPA.

One of the important point to consider is the size of the database.

In the quicksizer tool - is the tool based on Account based or Costing based? How much of a size difference is there between the two different approaches? Is there a rule of thumb for the relationship between the two.

Regards

Piet

[ajaycwa1981 · Accepted solution]

Hi Piet

If you are on S4 Hana or Sfin, go with ABCopa

otherwise, go with CBCOPA

Ajay Maheshwari

[Former Member · Accepted solution]

We are not currently on either of those, will be using COPA on HANA, but most everybody will sooner or later end up on S4 HANA.

ONE of the items under consideration during the decision process between Accounting based and Costing based is the influence on database size.

[ajaycwa1981 · Accepted solution]

Hi Piet

ABCOPA stores records in the same coep table. So it is known to slowdown your Copa as well as Cca reports

Additionally, you don't get split of Cogs as per cost components and split of variances in Abcopa

All these drawbacks have been addressed in Sfin

Size of data generated by both is same. Only difference is that the Cbcopa stores its data in separate set of tables which improves performance and it gets you split of cogs and variances

Ajay M

[sanilbhandari · Accepted solution]

Hi Piet

If you are on a green field project and COPA is a major ask from a business, i believe S/4 HANA Finance addresses major gaps which do not exist in AB COPA in ECC. Refer the link:

If however, you are on ECC, the data for AB COPA is stored in COEP, so it does have an impact on your other CO line item reports. However, basic functionalities like COGS break up and variance postings are not addressed in AB COPA and it makes sense to go in for costing based COPA from a functionality perspective.

From a sizing decision perspective, it does not make much of a difference whether you decide to go in for AB COPA or CB COPA. The sizing comes into play if you activate both in ECC.

Thanks & regards

Sanil Bhandari

[Former Member]

Hi..

To select accounting-based co-pa or costing-based co-pa regardless of SAP Business Suite and SAP S/4HANA, you can consider the below function like automatic valuation function.

Costing‑based CO‑PA can valuate incoming sales orders or billing documents to automatically determine anticipated sales deductions or costs.

Costing‑based CO‑PA can use automatic valuation to calculate planned revenues, sales deductions and costs of goods manufactured based on the planned sales quantity in CO-PA planning.

But Accounting-based CO-PA don’t support t automatic valuation function.

[Former Member]

Follow up question:

Another area of concern, is the influence on the FAGLFLEXT table.

Can we have a (much) more summarised FI document in Costing based vs Acc based? So that if we do decide to make use of accounting based, we will force an explosion in FAGLFLEXT because of the additional detail?

Thanks

[ajaycwa1981]

Hi Piet

I think no.

Faglflext will only offer you fields like PC, Business area etc. It won't have the Copa characteristics like sales org, distribution channel, product etc

Ajay M

[Former Member]

One of my consultants are adamant that it if we use Costing based, we will have the ability to reduce FI postings greatly.

E.g. we need to record sales from vending machines, which holds up to 40 different products, and therefor 40 different Costing Based COPA documents. He is hoping that using Finance summarisation we can keep the FI doc to about 4 lines - Revenue, one or two rebates and the AR posting.

[ajaycwa1981]

Hi Piet

in Copa it will be as many docs as the no of products involved.

you can summarize the doc in FI, but make sure it does not negatively impact Copa. In Copa you can summarize at product level, but if the products are different, it will be new Copa doc

Ajay M

[Former Member]

If a customer  is using CBCOPA today in EHP7 and has agreed to start using ABCOPA in SFin/SCORE. Is it possible to migrate the historical CBCOPA data to new ABCOPA or ABCOPA will start afresh in SFIN/SCORE ? This means customer loses the comparison with previous year