SAPFree worksheetPDF, Excel, Word exportSAP ECC and S/4HANA

SAP CO-PA Value Field Mapping Worksheet: Conditions to Value Fields

In costing-based profitability analysis, every number that appears in a CO-PA report comes from a value field. This worksheet records the design decision for each one: where it comes from, the sign it takes and what it adds to the margin. It is built to sit in a blueprint before configuration starts.

Download:

Value field	Description	Source type	Source reference	Sign (+1 or -1)	Sample amount	Signed result
						$100,000
						-$6,500
						$2,200
						-$61,000
						-$1,800
						-$4,300

Contribution margin

$28,600

Revenue (sum of signed results)

$28,600

Value fields mapped

Costing-based CO-PA stores value fields per operating concern; names must start with VV for amounts. Condition types such as PR00, K007, KF00 and VPRS are common SAP SD delivered keys, but check your own pricing procedure. Assignment is maintained in KE4I (conditions) and in the PA transfer structure for costs.

CO-PA design review

Optional: have your value field map reviewed against your pricing procedure and settlement design.

Optional. The tool and every export work without this. No spam.

How to use the worksheet

List each planned value field with a short description, the type of source (billing condition, cost of goods sold, variance, overhead or settlement), the exact condition type or cost element, and a sign. Enter a sample amount to see the signed result and the contribution margin total. If the margin is wrong in the test, your sign or source is probably wrong. Export to Excel for the design workshop.

How CO-PA gets the data

Value fields are filled when billing documents are posted (SD conditions mapped in KE4I), when cost of goods sold is determined (condition VPRS or a CO-PA costing run), and when orders and overheads are settled into CO-PA with a settlement profile. The transfer structure for settlement maps cost elements or origins to value fields. In S/4HANA, margin analysis uses the Universal Journal and the account-based model, with costing-based available as an additional view.

Design guidance

Keep value fields at a level that finance actually uses: revenue, deductions, COGS, variances, freight and a few overheads. Splitting cost into dozens of fields makes reports slow and hard to read. Plan quantity fields as well (sales quantity, weight). Decide early which fields roll up to contribution margin 1 and which to margin 2, as these groupings are reports and not fields.

Common mistakes

Mapping the same condition type to two value fields, so revenue is counted twice. Forgetting to map freight or rebate conditions, so they are missing from margin. Mixing sign conventions between SD and CO sources. Adding a field after go-live and not reposting history. Using value fields for data that belongs in characteristics.

Frequently Asked Questions

What is a value field in CO-PA?

A value field is an amount or quantity column in the operating concern, such as revenue or cost of goods sold. Together with characteristics like customer or product, it forms the data that profitability reports are built on.

Do value fields exist in account-based CO-PA?

Account-based CO-PA reads from G/L accounts and cost elements and does not use value fields. They exist in costing-based CO-PA, which stores values per operating concern and supports non-account views such as valuation at different costs.

Where do I map billing conditions to value fields?

Condition types are assigned to value fields in transaction KE4I, which uses the pricing procedure condition types. Settlement of orders into CO-PA uses a different mapping through the PA transfer structure.

Why does my margin differ from the G/L?

Costing-based CO-PA values at standard or other costs and includes statistical items, so it does not need to equal the P&L accounts. Reconciliation reports compare the two and explain the difference by category.

If you want to test a CO-PA design against actual billing and settlement data before you configure it, Netray can help build a read-only analysis of your current margin structure.

Talk to an Expert Explore More Free Tools

Related Tools

SAP

More SAP tools

See all

Back to All Tools