SAP S/4HANA Finance: How to Activate and Use Additional Quantity Fields in Account-Based CO-PA

  • by Srikanth Vadlamudi, Manager, Deloitte Consulting LLP
  • August 12, 2016
Discover how to activate additional quantity fields in account-based Profitability Analysis (CO-PA) so that quantities are also included in reporting. These additional quantity fields are made available in the Controlling module (CO) line-item tables, CO-PA top-down distributions, and CO-PA assessment cycles.
Learning Objectives

After reading this article, you will know how to:

  • Define additional quantity fields
  • Implement the logic to fill the additional quantity fields and corresponding unit-of-measure fields in the Business Add-In (BAdI) FCO_COEP_QUANTITY for a specific controlling area
  • Display the additional quantity and unit-of-measure fields in CO-PA reports
Key Concept
In SAP S/4HANA Finance, up to three additional quantities can be defined per controlling area. Each additional quantity is assigned a dimension, such as length or mass. Optionally, a standard unit of measure can be assigned to each additional quantity in order to facilitate aggregation.

A new feature in SAP S/4HANA Finance allows you to activate additional quantity fields in account-based Profitability Analysis (CO-PA), which can then be used in reporting, CO-PA top-down distributions, and CO-PA assessment cycles. After activation, the additional quantity fields can be updated using the SAP-provided Business Add-In (BAdI) FCO_COEP_QUANTITY.

For example, an additional quantity field could be used in the wholesale and distribution industries, where it is common to store the quantity not just in a sales unit of measure, but also in a base unit of measure that is common across all product lines. This allows the quantities to be aggregated across product lines, producing common quantities that can then be used to drive cost allocations (e.g., top-down distribution in account-based CO-PA).

In this article, I present the configuration details for adding an additional quantity field without any dimension; the specifics of the Business Add-In (BAdI); and the implementation method. Through examples, I also explain how Profitability Analysis (CO-PA) reports are populated and I describe the implicit enhancement, which is needed to dynamically populate the quantity when the base unit of measure belongs to multiple dimensions.

Define Additional Quantity Fields

To activate additional quantity fields, follow IMG menu path Controlling > General Controlling > Additional Quantities > Define Additional Quantity Fields. Click the execute icon beside Define Additional Quantity Fields to display the screen in Figure 1.

Figure 1
Define additional quantity field details

For every controlling area, you can define up to three additional quantity fields. You’ll need to assign a dimension for each quantity field for a specified controlling area, i.e., an organizational unit in the SAP system that is similar to a company code. You can leave the field under Std. UoM (standard unit of measure) blank, or you can specify one when aggregation is desired in order to drive allocations or top-down distributions. For instance, you could specify KG for a quantity produced with a dimension such as MASS.

To enable consistent reporting of all posted quantities in a base unit of measure, irrespective of the dimension, I set up Additional Quantity Field 1, and I left the Std. UoM field blank. In Figure 1, you can see that I chose dimension AAAADL, which happens to be a dimensionless dimension, but SAP does provide it as an option for units such as PAC, EA, and PC. Please note that the Std. UOM is optional.


To activate BAdI FCO_COEP_QUANTITY according to your requirements, work with your ABAP developer. Here is how the BAdI was implemented in our example:



Programming logic: If the unit of measure (IS_COEP-MEINH) is different from the base unit of measure (MARA-MEINS), convert the unit to the base unit of measure.

After the conversion has been performed, the converted data and unit of measure should be stored in:

CV_QUANT1- Converted quantity

CV_QUNIT1- Unit of measure. (MARA-MEINS – Base UOM)

If the unit of measure (IS_COEP-MEINH) and the base unit are the same, then data should be directly updated in:

CV_QUANT1-QUANT1- Value / quantity (IS_COEP- MEGBTR)

CV_QUNIT1-QUNIT1- Unit of measure (IS_COEP-MEINH)

The sample code used for achieving the above logic is shown in Figure 2

Srikanth Vadlamudi

Srikanth Vadlamudi is an SAP-certified consultant in FI and Controlling (CO) modules with 11 years of experience implementing FI, CO, and Project Systems modules in chemical, automotive, manufacturing, consumer products and retail and distribution industries. He has global SAP implementation experience spanning North America, Europe, Asia, and Australia. As a team lead, he has successfully managed multiple projects in FI and CO, demonstrating experience in all phases of system implementation, including analysis, design, construction, testing, cutover, go-live, and production support. In addition, he has industry experience as a mechanical engineer, working for companies in plastic injection molding and sheet metal manufacturing.

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.