Skip to Content
Author's profile photo Tammy Powlas

Preview of Smart Accounting Part 2 – FI-CO is Changing Reporting

Part 1 of this webcast is here Preview of New Smart Accounting Part 1

Please note that the usual legal disclaimer applies that things in the future are subject to change.

Reduce Redundancy


Figure 1: Source: SAP

Today Janet said there are times you can’t close the books because not sure what is right.

On the right of Figure 1 the aggregates are removed.


Figure 2: Source: SAP

Figure 2 shows there are no BSIS BSIK, GLT0 tables as the summary tables in FI gone

There are 4 main tables listed in Figure 2.


Figure 3: Source: SAP

Figure 3 shows there are now views with the same names now instead of tables

Core data service view – CDS – what used to be GLT0 – instead of read from aggregates

This is to avoid any “disruption” you may have when writing custom reports or code.

Why Account – based CO-PA


Figure 4: Source: SAP

Account based is as granular as general ledger, according to Janet

Cost of Goods Sold or COGS is usually used for the costing based for components

  • Put in config to allow break out by account
  • Will look at the same for price differences
  • Revisit assessments and settlements

Account based CO-PA provides an explanation of the statement


Figure 5: Source: SAP

Figure 5 shows a P&L statement in SAP BusinessObjects Analysis, edition for Microsoft Office

It shows you can pull in CO-PA dimensions

Janet said this is not a drilldown but extending the document


Figure 6: Source: SAP

HANA view to pull relevant fields, embedded BW – to create hierarchies to roll up a structure


Figure 7: Source: SAP

Figure 7 suggests using HANA to explain WIP or “work in progress”

CO  has detail on WIP – costs, orders, etc – know in detail

When a document posts in FI it is hidden in assignment field as production order x

  • Impossible to program on this
  • With HANA can read assignment field
  • Read WIP accounts, look for postings in period close and look at the assignment field to read details to explain what was behind WIP


Figure 8: Source: SAP

On the left is the old way of doing things.

On the right you can see select is moved to HANA


Figure 9: Source: SAP

In closing, Janet Salmon said there is one financial document with none of the aggregates and views

Janet said they will have to do something similar with projects (PS) as some point

My take:

This should simplify reporting out of FI-CO and I found it interesting to use Analysis Office for a P&L statement (I would’ve expected Crystal Reports).

Assigned Tags

      1 Comment
      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member

      i'm hoping SAP continues to support ODBO (Simba SDK) thus making BEx optional rather than mandatory for spreadsheet (pivot table) reporting.