SAP Central Finance 1909 Functionalities
SAP S/4HANA 1909 is released on 20th September. This also makes available with SAP Central Finance (CFIN) 1909. Central Finance is in such a stage where features are added each time and also their are some key features missing like Asset accounting replication. However with 1909 SAP has tried to deliver more value for Non SAP source systems and features are added to the catalogue.
In this blog we are discussing only the features introduced in 1909 release. Any thing before that is available in previous blog – SAP Central Finance 1809 functionalities
Replication of Material Cost Estimates
This feature enables you to replicate material cost estimates from source system(s) to the Central Finance system. For a mixed costing, the material cost estimates are replicated together with the relevant procurement alternatives.
- Download the latest SLT content of version S/4HANA 1909. This content is available in SAP Note 2154420
- SAP Note 2800883 is implemented in the source system.
- Run transaction /AIF/CONTENT_EXTRACT and choose Deployment scenario SAP_AIF_0018 to execute.
- Use Monitoring and Error Handling (transaction /AIF/ERR) and select Namespace /FINCF and Interface
- Mappings are needed to be configured for
- Material Number
- Controlling Area
- Cost Center
- Cost Element
- Activity Type
- Cost Component Structure
- Cost Component Number
- Costing Variant
- Only material cost estimate (BZOBJ = 0) is supported for this replication.
- Cost estimate of configured material (KEKO-CUOBJID <> SPACE) is not supported for replication in current release.
- Pure additive costs (KEKO-KKZMA = ‘X’) is not supported for replication.
- Cost Estimates for a Product Cost Collector will not be replicated (KALKA <> 19).
- Deletion of cost estimates is not supported for replication in current release
Replication of Activity Rates
This feature enables you to replicate activity rates from source system(s) to the Central Finance system. If a primary cost component split exists for a certain activity rate, the activity rate is replicated together with the cost component split data.
Third-Party System Interface: Replication of Clearing Information
The following processes are supported for replicating clearing information via the third-party system interface:
- Complete clearing of one invoice with one payment
- Clearing of one invoice by down payment
- Partial clearing of one invoice by partial payment
- Clearing several invoices by payment
- Replicating and updating clearing information for residual items
- Clearing by credit memo
- Clearing of several invoices by one payment
- Update of withholding tax from original invoice
- Reverse payment and reset clearing
Third-Party System Interface: Replication of CO-PA Characteristics
In SAP S/4HANA you perform Profitability Analysis (CO-PA) in the Universal Journal using criteria based on which you analyze your operating results and perform sales and profit planning. A combination of values for these criteria in an Operating Concern is called a profitability segment. Examples for such criteria can be product, billing type (such as invoice), customer, sales organization. This feature enables you to transfer such criteria via the third-party system interface in Central Finance as name-value pairs.
The replication of CO-PA data is integrated into existing message handling with SAP AIF. The values for the COPA characteristics are mapped according the defined values in the key and value mapping. The third-party system interface has been enhanced with an additional structure and fields for the profitability segment data. It is added as a new staging table on the SAP LT Replication Server as you can see in the graphic below which shows the architecture of the third-party system interface in Central Finance.
Third-Party System Interface: Group Currency
In SAP S/4HANA journal entries can be posted in group currency which enables reporting in group currency. With this feature journal entries containing group currency information and amounts in group currency can be replicated via the third-party system interface of Central Finance. In the third-party system interface the staging tables and fields containing the financial accounting data have been enhanced to enable the replication of group currency information and amounts. The SAP note referenced in Installing Financial Data Structures on SAP LT Replication Server has an excel list attached to which you can refer for the structure and fields relating to the group currency.
Initial Load Optimizations
- Balance load – use profit center ledger or consolidation ledger (trading partner information) for Classic G/L If your source system operates on classic G/L you can define an alternative ledger from which balances are read during the extraction step of the initial load instead of ledger GLT0. For each company code and range of accounts you can specify either ledger 8A for profit center information (table GLPCT) or ledger 09 for trading partner information (table GLT3). As these ledgers are not compatible, you can choose only one. You make these settings in the IMG activity Specify Alternative Ledger for Balance Load for Classic G/L in your source system.
- Take document splitting information into account – Document splitting information is now replicated in the initial load of documents and open items, in addition to being replicated as part of ongoing replication.
- Different Fiscal year variant for non-leading ledger – If you want to replicate data to your Central Finance system and the leading ledger has a different fiscal year variant than the non-leading ledger, it is necessary to ensure that the initial load can load the balances into the correct periods. To enable this, you can install two SAP Notes (2764810 and 2764851) into the source system. These notes enable the system to align the different fiscal year variants of the leading and non-leading ledgers, ensuring all relevant data is replicated and assigned to the correct periods in the Central Finance system. The only restriction is that the periods of both ledgers must match, for example, they must both start on the same day of the month.
Monitor with Focused run (F-Run)
Focused Run addresses customers and partners with advanced needs in monitoring larger system landscapes. F-Run has a dashboard-based visualization, for example with systems.
Source – SAP.com and SAP help material