
A Trading Partner identifies the other company involved in an intercompany transaction. The field VBUND helps distinguish group-company transactions from external business and supports intercompany reconciliation and financial consolidation.
Reliable Trading Partner reporting starts with company configuration and consistent customer, supplier, and G/L account master data. A missing or incorrect partner can leave balances difficult to reconcile or eliminate at group close.
Read more: SAP Trading Partner Configuration and Master Data — Part I
By Ross Christoph

SAP outsourced manufacturing connects subcontracting procurement with component consumption and manufacturing cost analysis. The Outsourced Manufacturing business function (LOG_MM_OM_1), introduced with SAP ERP 6.0 Enhancement Package 4 (EHP4), added capabilities for timely consumption and integration with Cost Object Controlling.
Scope: This article develops Ross Christoph’s original 2015 implementation note. The EHP4 functionality is discussed in its SAP ERP context, with references to related SAP S/4HANA on-premise documentation. The appropriate design depends on your installed release, integration landscape, and process requirements.
Read more: SAP Outsourced Manufacturing: EHP4 and LOG_MM_OM_1
By John Jordan
SAP Product Cost Controlling troubleshooting often starts with two questions: why did a costing run reuse an existing cost estimate, and why do detailed CO reports show unexpected values? This article explains both issues and points you to the relevant SAP Notes.
This is Tip 100 from 100 Things You Should Know About Controlling with SAP, second edition, by John Jordan. The examples describe classic SAP ERP Controlling behavior; check the applicable SAP Note and your system release before applying the guidance.
Read more: SAP Product Cost Controlling FAQs: Costing Runs and Reports
SAP Material Ledger has two main functions:
Carry inventory in up to two additional valuations and actual costs, as we explain in detail below:
Read more: SAP Material Ledger - Excerpt: 100 Things You Should Know About Controlling with SAP
By Paul Ovigele
Explore five SAP Financial Accounting (FI) and Controlling (CO) tips in this webinar by Paul Ovigele. The session covers report usability, master data maintenance, G/L account settings, secondary cost elements, and financial transaction worklists.
Watch the recording below. This webinar is useful for SAP finance users, support teams, and consultants reviewing practical ways to improve everyday processes.
By Paul Ovigele
Reconciling SAP costing-based CO-PA to the general ledger helps finance teams explain differences between profitability reports and the income statement. The task requires a clear understanding of value fields, G/L accounts, valuation, and the timing of postings.
This article introduces the reconciliation challenge discussed in Reconciling SAP COPA to the General Ledger by Paul Ovigele. The original book introduction is supplemented here with practical checks and SAP S/4HANA Margin Analysis context.
Adapted from work by John Jordan and Janet Salmon
The SAP cost component structure groups a product cost estimate into categories such as raw materials, packaging, labor, and overhead. The valuation variant determines which prices and activity rates SAP uses, and the cost component structure determines where the resulting costs appear in the split.
In a multilevel bill of material (BOM), SAP uses costing levels to determine which materials to cost first. This guide explains how to review the cost component structure in transaction OKTZ and trace costs from a lower-level assembly into a finished product.
Read more: SAP Cost Component Structure: Configuration and Cost Rollup
By Sydnie McConnell
Historical case study, originally published September 9, 2014. This account describes Woodward’s SAP ECC and SAP BPC 10.0 project at that time. The S/4HANA context section below provides a current terminology update.
At Woodward, our project to implement SAP Business Planning and Consolidation (BPC) 10.0 for SAP NetWeaver was part of a roadmap to unify financial reporting across the company while retaining multiple ERP systems.
The project began with two sites already using SAP ERP Financials and SAP Business Warehouse (BW). We had both forms of SAP Profitability Analysis (CO-PA) activated, but our detailed reporting relied on costing-based CO-PA. When we designed the BPC data load, we revisited account-based CO-PA.
Read more: SAP CO-PA and BPC at Woodward: Costing-Based vs. Account-Based

SAP Accounting powered by SAP HANA introduced significant changes to financial accounting and management accounting by simplifying data structures and enabling more flexible reporting.
Originally introduced in 2014, the solution was part of SAP's transition toward simplified financial data structures and was followed by SAP Simple Finance and the subsequent evolution of SAP S/4HANA Finance.
This article, originally written by Janet Salmon, answers frequently asked questions about SAP Accounting powered by SAP HANA, including its architecture, reporting capabilities, deployment options, and business benefits.
Historical context: The discussion reflects SAP technology and implementation options available in 2014. Since then, SAP S/4HANA Finance has introduced the Universal Journal, further integrating Financial Accounting (FI) and Controlling (CO).
The original technical explanations remain valuable for understanding the evolution of SAP Finance.
I've been working with the first accounting customers to validate and implement SAP Accounting powered by SAP HANA.
SAP Accounting powered by SAP HANA became available on August 1, 2014. This article explains how the solution differed from earlier SAP accounting architectures and shares what I learned from early customer implementations.
Read more: SAP Accounting Powered by SAP HANA: FAQs and S/4HANA Evolution
By Paul Ovigele

Quantity fields in SAP costing-based Profitability Analysis (CO-PA) give sales and contribution margin reports the context needed to interpret revenue and costs. Sales quantities, production quantities, and measures such as net weight must be mapped to the appropriate quantity value fields.
This guide covers three sources: sales documents using KE4M, manufacturing order settlement using a PA transfer structure, and direct FI postings. Quantity value fields are defined with the relevant quantity attribute, as illustrated by the original KEA6 configuration examples.
SAP S/4HANA scope: These value-field mappings apply to costing-based CO-PA. SAP documents that Margin Analysis does not use value fields. The screenshots below are historical SAP GUI examples from Paul Ovigele’s original article; availability and settings depend on the release and process. For a related S/4HANA topic, see Margin Analysis extensibility and custom characteristics.
Read more: Updating Quantity Fields in SAP Costing-Based CO-PA