Enterprise Resource Planning Blogs by Members
Gain new perspectives and knowledge about enterprise resource planning in blog posts from community members. Share your own comments and ERP insights today!
cancel
Showing results for 
Search instead for 
Did you mean: 
Former Member

In SAP S/4HANA Finance, accounting documents are posted using a common document number. The FI document for profit and loss (P&L) accounts still generates CO documents. To maintain consistency and CO compatibility views, the document type and document number Customizing settings are maintained for the internal CO postings and to assign the actual version of CO to the ledger. With the integration of FI and CO, there is no requirement for a reconciliation ledger going forward. In the past, any CO-related postings were updated in both the line item table (COEP) and totals table (COSP for primary/COSS for secondary). With SAP S/4HANA Finance, the totals tables are no longer required because data can be aggregated from the line item table, which is also used for reporting. This avoids data redundancy. All actuals data continue to be stored in the line item table COEP.

Two new tables—COSP_BAK and COSS_BAK—have been created to store planned data related to primary and secondary costs, respectively.

The Universal Journal has its own currency fields in FI while CO has its own cur- rency settings. The currency concept used separately in FI and CO has now been combined. You can enhance the journal entry by adding the coding block and Profitability Analysis (CO-PA) characteristics. Access to old data in tables is still possible via the compatibility views V_<table name>_ORI.

Cost Elements

Cost elements are no longer required in SAP S/4HANA Finance because they are created as G/L accounts using Transaction FS00 and are part of the chart of accounts. A new field for the cost element category has been introduced in the G/L master record. The default account assignment is maintained using Trans- action OKB9 and not in the traditional cost element master data. Customizing settings that require cost elements such as costing sheets or settlement profiles and the business transactions where cost elements are used will continue to be defined by the cost element category settings from the G/L master records. Cost element groups continue to be available in SAP S/4HANA Finance for grouping the accounts and for reporting purposes.

Allocations

With the introduction of the new Universal Journal in SAP S/4HANA Finance, all the CO postings are posted directly to the Universal Journal, Secondary cost elements are now part of G/L accounts in FI and don’t require separate assignment in CO.

CO-FI Reconciliation

G/L account mapping of CO real-time integration with the new G/L is now obsolete. Secondary cost elements are now created as G/L accounts and are part of the chart of accounts. On the configuration side, document types that you want to use for posting in CO need to be defined and require the indicator G/L to be set. These document types need to be linked to the CO business transaction via a variant. The fiscal year variants of all controlling areas used by an organization and their assigned company codes must be the same.

The following transactions are no longer available in SAP S/4HANA Finance,

  • KA01, KA02, KA03: Create/Change/Display Primary Cost Elements.
  • KA06: Create Secondary Cost Elements.
  • KK16, KK17: Cost Object Planning by Cost Element/Activity.
  • KK46, KK47: Cost Object Planning by Statistical Key Figure.
  • OMX2: Assign Currency Types to Material Ledger Type.
  • OMX3: Assign Material Ledger Types to Valuation Area.

Configuration change:

2 Comments
Labels in this area