SAP HANA Accounting: FI and CO Line Items | Part II
SAP Controlling Conference attendees participating in a presentation

Search Posts

By Janet Salmon

SAP Accounting powered by SAP HANA brought Financial Accounting (FI) and Management Accounting (CO) closer together. In Part II, Janet Salmon explains the logical document, the connection between FI and CO line items, secondary cost elements, and CO-PA reporting dimensions.

Historical context: The following transcript excerpt comes from Janet’s Controlling 2014 plenary session. References to “the first version,” “at the moment,” and “going forward” describe the SAP Simple Finance roadmap at that time. Architecture and limits discussed here should be read in that historical context.

Janet Salmon presenting at the SAP Controlling Conference
Janet Salmon presenting at the SAP Controlling Conference.

Why Connect Financial Accounting and Controlling?

New users have traditionally struggled to understand the way SAP separates Financial Accounting and Management Accounting when their previous systems treated the two as one. A payroll account flows from the profit and loss statement into cost center accounting while retaining the account information. In costing-based profitability analysis (CO-PA), however, revenue is represented in a value field, and a cost of goods sold account can become multiple value fields depending on the cost components involved.

Janet’s plenary session explores how SAP Accounting powered by SAP HANA, part of SAP Simple Finance, addressed these challenges and how the convergence of internal and external reporting requirements affected SAP Controlling. Her explanation follows, with the transcript wording preserved.

The Logical Document and Primary Cost Elements

The first version of SAP Accounting powered by HANA, works with this idea of a logical document. What the logical document does is, it leaves these 2 big line items tables, the same. I still have an FI line item and I still have a CO line item, but we're tying them together. Going forward, we'll actually take that and make it into one big physical document. As a mental picture to take with you, when we typically taught people, what's CO? We sit there and we say, "Well, if you look at your FI accounts, you've got your balance sheet accounts and you've got your profits and loss accounts. Then, those profit and loss accounts that you want to see in CO, create another record for them, it's called the Primary Cost Element. Then we'll record things like payroll by cost center, material expenses by order, revenue by COPA dimension. It's really just, more detail of what you have in the other one. 

Allocations, Settlements, and FI Documents

At the moment what we're doing is, we're tying those 2 line items together. Going forward, we'll make that into one record, with everything in that one record. Then of course what happens then is, all the funny business of this CO starts. All those settlements, allocations, where I need creating sender/receiver relationships, and moving costs. For example, from my team to a product group or whatever. Now, with the new GL, we already have the ability to tell FI, what had happened there, you know? "I've made an allocation, I've taken costs off my marketing cost center, and I've assigned it to my product groups. I've taken costs off my production cost center, and assigned it to a production order." Every time those cross a barrier, whether it's a profit center, a business area, a functional area or a company code, we create an FI document for it. 

Secondary Cost Elements and Line-Item References

Going forward, we'll actually just treat secondary cost elements as a special type of account. It was a one-to-one reference. You can imagine that some of these documents got pretty big, you know? There's a limit of 999 line items in FI. If it was a payroll and you had a pretty substantial payroll, you could end up with 4, 5, 6 FI documents with reference to CO documents. What we've done in the new scenario is, we've actually taken that link, the thing that held the 2 together, and made it available at line item level. We can really go line item per line item through the document and say, "These are the payroll costs for this cost center. These are the material costs for this order" and so on. What's changed these references procedure, object key, logical system? This is something you don't usually have to worry about. It's our problem, unless you have problems in interfacing. We've actually moved those down a layer. We've put them into the CO table, so that we can tie the 2 documents together.

Bringing CO-PA Dimensions into Reporting

The other thing we've done is, we've actually tied in the COPA table. This is the COPA Dimensions. All the things in your operating concern that say, "I'm going to report by product, by product group, by region, by product hierarchy", and so on. We basically bring the 2 together. It means, essentially when we're reporting, we're doing a hunting and gathering process that looks at the FI document and says, "Which of these are PNL items?" We're looking at the CO line item table and saying, "Which of these are primary cost elements?" We're looking at the COPA table and saying, "Which dimensions do you assign to?" When we've done that, we can do ... We've had to extend the CO table, to bring those things together. Those of you who are very familiar with this, you'll notice quite a major change. 

Read the Complete Transcript and Continue the Series

Need Help Connecting SAP Finance and Controlling?

ERPCorp helps finance teams review FI and CO integration, profitability reporting, Product Costing, and period-end processes.

Explore ERPCorp SAP Consulting

SAP Controlling Learning Resources

Explore practical sessions and connect with SAP Finance and Controlling experts at the SAP Controlling Conference. For available session recordings and other learning resources, explore ERPCorp Membership.