Enterprise Resource Planning Blogs by SAP
Get insights and updates about cloud ERP and RISE with SAP, SAP S/4HANA and SAP S/4HANA Cloud, and more enterprise management capabilities with SAP blog posts.
cancel
Showing results for 
Search instead for 
Did you mean: 
Wagnerfr
Active Participant

With the TOP Simplification List Items approach we want to start a S/4HANA SCN Blog series to provide more information about dedicated simplification items. Simplification items where we assume that any customer project has to deal with. The following S/4HANA SCN Blog is collecting these TOP Simplification Items with the links to the dedicated S/4HANA blogs.

The TOP Simplification List Items

Within this blog we want to provide additional information regarding the Simplification Item:

FIN - Technical Changes in Controlling



Description

With SAP S/4HANA, on-premise edition 1511 several general data model simplifications have been made to Controlling area. Those are:

  • Actual data (value type = 04) that was formerly in COEP (CO line item table) is now in ACDOCA (universal journal)
  • Statistical data (value type = 11) is stored in additional columns in ACDOCA (universal journal) and in COEP for compatibility access
  • Totals tables for primary costs (COSP) and secondary costs (COSS) are replaced by views
  • Actual data for long running orders and projects that were in COSP_BAK and COSS_BAK (back up for former totals tables) is now in ACDOCA
  • Value types other than 04 and 11 continue to be stored in COEP, COSP_BAK and COSS_BAK (examples include planned costs and target costs)
  • Table header COBK is updated as before
  • Compatibility Views such as V_COEP and V_COEP_ORI provide access to data as before

Business Impact

  • No impact on the standard SAP business processes
  • Existing CO programs such as allocations and settlements are gradually being adjusted to read the universal journal directly
  • Views aggregate data on the fly allowing select statements in SAP coding and customer coding to work as before
  • It might be required to adapt Custom Code if fields have been added to the totals table or CO line item table.
  • Write statements and customer DDIC objects must be adapted according to the instructions in the Note 1976487
  • Replace access via compatibility views with direct access to ACDOCA for value types 04 and 11 (see Note 2185026)

Recommended Action

  • Check existing totals tables and line item table to determine whether fields have been added
  • Adjust access to read from ACDOCA directly

For more details see the PPT attached to the following SAP Note:

http://service.sap.com/sap/support/notes/2270404