Central Finance

PUBLIC

Document Version: SAP S/4HANA 1909 FPS02 – 2020-05-06

Central Finance

THE BEST RUN

Content

1 Central Finance............................................................. 4

1.1 Replication Scenarios in Central Finance.............................................6

1.2 Central Processes.............................................................7

1.3 System Landscape............................................................8

1.4 Postings Excluded from Transfer..................................................11

1.5 Conguring Your Central Finance Scenario.......................................... 12

Getting Started with Central Finance............................................12

Installing Central Finance....................................................20

Conguration in Central Finance System: Set Up Systems.............................27

Error Handling............................................................29

Data Mapping............................................................37

Conguration Consistency Check..............................................55

EC-PCA Postings..........................................................63

Material Cost Estimates Replication.............................................70

Activity Rates ............................................................71

Cost of Goods Sold Splitting in Central Finance.....................................75

Price Dierence Splitting in Central Finance.......................................77

Account Determination of Condition Types for Protability Analysis (CO-PA)................79

Replication of Commitments................................................. 80

Conguration in SAP Landscape Transformation Replication Server......................82

Initial Load.............................................................. 87

Replicate Individual Cost Objects and CO Documents................................119

Delete Replicated Documents................................................120

Comparison Reports.......................................................124

Activation of Clearing Transfer and Handling of Open Items........................... 129

Special Business Transactions: Additional Information...............................136

Additional Settings and Enhancements..........................................137

Display Information from Central Finance in the Source Systems.......................138

Accounting View of Logistics Information (AVL): Overview............................144

1.6 Central Payment............................................................150

Settings for Central Payment in Source Systems...................................153

Activation of Central Payment for Company Codes.................................153

Handling of Historical Open Items.............................................155

Guidance for Dependent Processes............................................156

Cross-System Process Control for Central Payment................................ 168

Down Payment Integration with SD.............................................171

P U B L I C

Central Finance

Content

Down Payment Integration with MM............................................175

SEPA Mandate Replication...................................................177

1.7 Central Tax Reporting........................................................ 184

Central Tax Reporting: Prerequisites............................................185

Conguration Consistency Checks.............................................186

Tax Reporting Based on Postings from the Initial Load...............................188

Overview of Supported Reports...............................................189

Deferred Tax.............................................................191

Withholding Tax..........................................................191

External Tax Calculation....................................................194

Input Tax from Parked Documents.............................................194

Support of Tax Reports in Mode “Update of Documents”.............................195

1.8 Central Projects (WBS) - Reporting Scenario........................................195

Central Projects (WBS) - Reporting Scenario: Conguration in Source System..............197

Central Projects (WBS) - Reporting Scenario: Conguration for SAP AIF..................199

Central Projects (WBS) - Reporting Scenario: Conguration in the Central Finance System

.....................................................................200

Central Projects (WBS) - Reporting Scenario: Check Settings for Replication of Projects...... 202

1.9 Third-Party System Interface to Central Finance: Process and Architecture..................203

Replicating Data Using the Third-Party System Interface to Central Finance............... 204

Installing Financial Data Structures on SAP LT Replication Server.......................213

Error Handling in SAP Application Interface Framework (SAP AIF).......................214

Conguring SAP Central Finance..............................................216

MDG Data Mapping....................................................... 216

Third-Party System Interface to Central Finance: Extensibility......................... 219

SAP Central Finance Transaction Replication by Magnitude for SAP S/4HANA..............220

1.10 Advanced Compliance Reporting: Country/Region-Specic Reports in Central Finance..........220

1.11 Read Access Logging Congurations in Central Finance................................ 231

Central Finance

Content

P U B L I C 3

1 Central Finance

With Central Finance, you can transition to a centralized SAP S/4HANA on-premise edition without disruption

to your current system landscape, which can be made up of a combination of SAP systems of dierent releases

and accounting approaches and non-SAP systems.

This allows you to establish a Central Reporting Platform for FI/CO with the option of creating a common

reporting structure. Additionally, selected nancial processes can be executed centrally in this system. To

prepare common reporting structures, you can map the dierent accounting entities (for example, account,

prot center, or cost center) in your source systems to one common set of master data in the Central Finance

system. You can then replicate nancial accounting and management accounting postings to your Central

Finance system.

In your SAP S/4HANA system, FI documents and CO postings are combined into one document; the universal

journal entry. In addition, all cost elements are part of the chart of accounts. Before you replicate CO postings

to the Central Finance system, you need to make sure that accounts are available for all cost elements. You can

also replicate certain cost objects (for example, internal orders) to the Central Finance system.

In a typical set-up, multiple source systems are connected to one System Landscape Transformation

Replication Server which in turn is connected to one Central Finance system.

P U B L I C

Central Finance

Where can I nd more information?

● https://help.sap.com/doc/b870b6ebcd2e4b5890f16f4b06827064/1909.002/en-US/

WN_OP1909_FPS02_EN.pdf [https://help.sap.com/doc/

b870b6ebcd2e4b5890f16f4b06827064/1909.002/en-US/WN_OP1909_FPS02_EN.pdf]

● https://help.sap.com/viewer/029944e4a3b74446a9099e8971c752b9/1909.002/en-US/

87c29fd0279242d68d889be7d501c3.html [https://help.sap.com/viewer/

029944e4a3b74446a9099e8971c752b9/1909.002/en-US/87c29fd0279242d68d889be7d501c3.html]

● Replication Scenarios in Central Finance [page 6]

● Getting Started with Central Finance [page 12]

● Central Tax Reporting [page 184]

● Central Payment [page 150]

● Third-Party System Interface to Central Finance: Process and Architecture [page 203]

● Central Projects (WBS) - Reporting Scenario [page 195]

 Note

Terminology: Journal Entry vs. Accounting Document

Please note that the following information applies only to English.

In SAP S/4HANA, the term journal entry replaced accounting document following a change in the

underlying nancial architecture. While the basic concept – the accounting record for a business

transaction – is the same, journal entries enable a true integrated accounting system.

Central Finance

P U B L I C 5

You may notice that you still see document or accounting document on the user interface and in the

documentation. Nevertheless, these accounting documents are actually journal entries since they are

based on the new architecture.

1.1 Replication Scenarios in Central Finance

Central Finance supports the following replication scenarios:

● FI/CO replication

The replication of FI postings encompasses a certain scope. For a list of postings that are not replicated to

Central Finance, see Postings Excluded from Transfer [page 11].

For more information about clearings and open items, see Activation of Clearing Transfer and Handling of

Open Items [page 129].

For information about further business transactions, see Special Business Transactions: Additional

Information [page 136].

Also see SAP Note 2184567 , which answers frequently asked questions about Central Finance.

● CO replication

Replication of CO postings that do not ow in via FI (for example, cost center allocation) (actuals only:

value types 04 and 11) – for supported business transactions, see SAP note 2103482 .

● Cost object replication

For additional information and scope, see SAP Note 2180924 .

● Commitment replication

Replication of commitments and commitment updates for purchase requisitions and purchase orders.

For additional information, see SAP note 2554827 .

● Replication of EC-PCA postings

For additional information, see Replication of EC-PCA Internal Postings [page 63].

● Replication of Material Cost Estimates

For additional information, see Material Cost Estimates Replication [page 70].

● Replication of Activity Rates

For additional information, see Replication of Activity Rates [page 71].

● Replication of projects

For additional information, see Central Projects (WBS) - Reporting Scenario [page 195].

● Replication of a dened subset of logistics data relating to sales orders and customers invoices within the

Accounting View of Logistics Information component.

For additional information, see Accounting View of Logistics Information (AVL): Overview [page 144].

The following features are also supported:

Replication of Document Changes

Changes to nancial documents (for example via transaction FB02) are replicated from the source system to

the Central Finance system.

Replication into Accounts Receivables and Accounts Payables

Financials postings update FI-AP/AR if postings or clearings on customer or vendor accounts are replicated.

For restrictions and more information, see Activation of Clearing Transfer and Handling of Open Items [page

129].

P U B L I C

Central Finance

Replication of Changes to Cost Objects, Depending on the Scenario Denition

Replication of changes to cost objects from the source systems to the Central Finance system is possible for

those with 1:1 cardinality in the scenario denition. The attributes marked as “Derive from Local” and “CO

relevant” can be replicated automatically in the Central Finance system, and the replication of common critical

statuses is supported.

Replication of Commitments

Commitment replication supports not only commitments from the creation of purchase requisitions and

purchase orders but also updates to commitments triggered by changes to purchase requisitions and

purchase orders, including goods issue and invoice receipt for the purchase order.

For detailed information about conguring Central Finance, see Getting Started with Central Finance [page

12].

1.2 Central Processes

Central Finance allows you to centralize the following processes in your SAP S/4HANA system:

Central Payment

Central Payment for SAP Central Finance allows you to make centralized payments and perform centralized

clearing activities in the Central Finance system instead of each source system. Please be aware that all

dependent processes based on open item management must take place in the Central Finance system (for

more information, see SAP Note 2346233 ).

It has the following main features:

● Activate Central Payment by company code.

● For company codes that are activated for Central Payment, the invoices posted in the source systems are

technically cleared. The invoices are replicated to the Central Finance system and are paid there.

● For company codes that are not activated for Central Payment, the invoices posted in source systems stay

open and are paid in the source systems. The invoices and payment or clearing documents are replicated

to the Central Finance system for reporting purposes. The replicated invoices are ruled out from the

payment or clearing transactions in the Central Finance system. This avoids duplicate payments (as

payments are to be processed in the source systems).

● Mandate replication between source systems and the Central Finance system is automated meaning that

SEPA direct debit is supported in the Central Finance system.

 Note

Central Payment for SAP Central Finance is released with functional restrictions, which are described in

SAP Note 2346233 . To activate this product, create an incident on component FI-CF-APR. Before

making productive use of the product, please make sure that you fully understand the restrictions and have

thoroughly tested the product so that you won’t be impacted by the restrictions.

Note also the restrictions relating to Central Tax Reporting (see below).

Central Finance

P U B L I C 7

Central Tax Reporting

Central Finance supports tax reporting out of the Central Finance system for a certain scope.

Please read the section Central Tax Reporting [page 184] which describes the supported scope.

Please also take into account the referenced SAP Notes which are required to support certain aspects of tax

reporting out of the Central Finance system.

For further information, see SAP Note 2509047 .

Central Projects (WBS) - Reporting Scenario

Central Finance supports the Central Projects scenario, where you are creating and editing projects in a source

system and want to do the project reporting on costs and revenues posted to WBS elements in the Central

Finance system.

For further information, see Central Projects (WBS) - Reporting Scenario [page 195]

1.3 System Landscape

Central Finance

The gure above illustrates the way in which Central Finance is used in conjunction with SAP Landscape

Transformation Replication Server (SAP LT Replication Server), SAP Master Data Governance (SAP MDG) and

error handling.

P U B L I C

Central Finance

SAP LT Replication Server

SAP LT Replication Server collects data written to databases in the source systems and feeds this data into the

corresponding Central Finance accounting interface.

The following replication scenarios are supported:

● Replication of FI/CO postings

● Replication of CO internal postings

● Replication of cost objects

● Replication of commitments

● Replication of EC-PCA postings

● Replication of material cost estimates

● Replication of activity rates

● Replication of a dened subset of logistics data from purchase orders, sales orders, customer invoices

(billing documents), supplier invoices (Accounting View of Logistics Information (AVL)

Please also check Replication Scenarios in Central Finance [page 6] for additional information about the

replication scenarios.

SAP LT Replication Server is also used for the initial load of CO internal postings and cost objects. The initial

load of FI data is managed via Customizing activities in the Central Finance system. You can access these

Customizing activities in the Implementation Guide (IMG) by starting transaction SPRO and then choosing

Financial Accounting Central Finance Central Finance: Target System Settings Initial Load Initial Load

Execution for Financial Accounting .

Central Monitoring and Alerting Capabilities

You can connect to your SAP LT Replication Server from an SAP Solution Manager system, enabling you to

monitor aggregated information on job, trigger, and table status.

For more information, see Conguration in SAP Landscape Transformation Replication Server [page 82].

Master Data Governance (SAP MDG)

Central Finance oers integration to Master Data Governance (MDG) to access available mapping information

there. Even if MDG is not in use, in the background Central Finance uses the MDG mapping tables that are

available without installing MDG. This does not require an MDG license. The MDG license is only required if the

MDG application is used. If you use MDG to distribute master data throughout your system landscape, it is

likely that MDG will already contain a lot of information on how master data maps to each other in the dierent

systems. This information can be accessed and does not have to be maintained again manually.

Dierent types of master data are mapped in dierent ways:

● Master data, such as G/L accounts, customers, and vendors, must be either mapped manually as part of

your Customizing or using SAP Master Data Governance.

Central Finance

P U B L I C 9

● Master data relating to cost objects, such as production orders and internal orders, is mapped using the

cost object mapping framework.

 Recommendation

To map master data, SAP suggests you use SAP MDG. If you are mapping short-living cost objects, you

should use SAP MDG in conjunction with the cost object mapping framework.

Master Data Consolidation

Master Data Consolidation enables you to determine an initial set for key mapping. For more information, see

the section Key Mapping in Conguration in Central Finance System: Mapping [page 39].

Document Relationship Browser

Using the Document Relationship Browser, you can see the document ow of an FI document. For example, you

can navigate back from an FI document to the original sales order. You can also search for the reposted FI

document using the company code, original document number, or scal year from the source system.

 Note

All business documents related to a transaction are available in the Document Relationship Browser,

provided the source system is an SAP system.

To navigate to the Document Relationship Browser, you can use the following transactions:

● Controlling Documents: Actual (KSB5), then choose Environment Relationship Browser

● Display Document (FB03), then choose Environment Document Environment Relationship

Browser

Drillback from Fiori App - Manage Journal Entries

To enable drillback to a source document from the Fiori app Manage Journal Entries you must carry out the

conguration settings described in the SAP Note 2507089 .

Error Handling

After the data is mapped, the system uses error handling functions to log the details of any errors encountered.

You can choose to make corrections and repost the item or process the item again after, for example, you

correct the mapping rule or adjust incorrect values in the document.

P U B L I C

Central Finance

SAP HANA

The internal accounting interface posts Financial Accounting (FI)/Management Accounting (CO) documents to

SAP HANA as a universal journal entry.

1.4 Postings Excluded from Transfer

Some postings cannot be transferred as part of the initial load and ongoing replication.

Postings Excluded from Transfer

CO-FI Postings and Clearings

A CO document in the source system triggers the creation of an FI document of the type CO-FI in the source

system. This document is not transferred to the Central Finance system. Instead, the replicated CO document

in Central Finance also triggers the creation of a document of the type CO-FI.

Note: CO documents should only be replicated if the G/L Reconciliation ag has not been set in the

customizing activity General Replication Settings (VCFIN_SOURCE_SET). This ag is only available in SAP ERP

source systems.

A clearing that attempts to clear a CO-FI posting of this type is transferred via the FI interface and the system

cannot identify which posting it is related to because the CO-FI posting itself doesn’t contain any information

about the corresponding source document. Therefore, subsequent processes such as CO-FI clearings will run

into errors.

The following types of posting are not transferred as part of the initial load and ongoing replication:

● Postings to CO-FI reconciliation ledger (GL Reconciliation Postings)

 Note

For ERP Source Systems. For the initial load only you should note that, if you have enabled replication

of CO postings, postings to CO-FI reconciliation ledger (GL reconciliation postings) will be transferred

via CO. Therefore, you must not set the GL Reconciliation Postings Transferred ag in the Customizing

activity General Replication Settings. For more information about this activity, see Conguration in

Source System: Initial Load [page 92].

● Year-end closing postings where the reference transaction (AWTYP) is GLYEC

● Clearings are not transferred as part of the initial load but you can activate the transfer of clearings via

ongoing replication. For more information see Activation of Clearing Transfer and Handling of Open Items

[page 129].

● Clearing resets are not transferred as part of the initial load but you can activate the transfer of clearing

resets via ongoing replication. For more information see Activation of Clearing Transfer and Handling of

Open Items [page 129].

● Recurring entries

● Sample documents

● Noted items (apart from downpayment requests and payment requests)

● Parked documents

Central Finance

P U B L I C 11

● Balance carryforward items

● Closing operations (These comprise processes and functions performed at the end of the scal year in

certain countries.)

 Note

Long texts - on both header and item level - and attachments are not replicated during the creation of

documents or when those documents are changed.

 Note

Transactional data that is stored in supplementary tables in the source system is not replicated to Central

Finance.

Therefore, processes that rely upon this supplementary data are not supported, for example, Nota Fiscal

(Brazil).

Documents created via ALE in the source system cannot be replicated correctly to the Central Finance system.

In the ALE scenarios, postings are processed in a simplied manner, which is not compatible with the Central

Finance scenario and could result in missing or inconsistent postings in the Central Finance system. Project

master data is an exception to this. For more information about Central Projects, see

Central Projects (WBS) -

Reporting Scenario [page 195].

1.5 Conguring Your Central Finance Scenario

1.5.1 Getting Started with Central Finance

The following chapters contain information explaining how to congure the dierent systems involved in your

Central Finance scenario.

Before you start conguring your systems, carefully read not only the information provided here, but also the

SAP Notes 2148893 - Central Finance: Implementation and Conguration and 2184567 - Central Finance:

Frequently Asked Questions.

In addition, ensure that you have installed the latest support package and apply the most recent notes on

component FI-CF and its subcomponents to avoid encountering problems which have already been solved.

1.5.1.1 Prerequisites

SAP ERP Releases for Source Systems

In Central Finance, you can use all SAP ERP releases as source systems that are still in maintenance starting

from SAP ERP 6.0. Instructions on how to implement Central Finance with these source system releases are

P U B L I C

Central Finance

available either as SAP Notes or are contained in the support packages for these systems. For releases SAP

R/3 4.6C to SAP ECC 5.0, contact SAP Product Management by creating an incident on the component FI-CF.

Replication from Third-Party Systems

For information about connecting non-SAP ERP systems to Central Finance, see SAP Note 2713300 .

For more information on conguration of the third-party system interface to Central Finance, see Third-Party

System Interface to Central Finance: Process and Architecture [page 203].

Licensing

Required Software

You must have a license for the following:

● Central Finance

Contact your SAP Account Executive to verify if you need to purchase this license.

Optional Software

● External Tax Calculation Engine

If you are using an external tax calculation engine in your source system, you should connect the same

external tax calculate engine to your Central Finance system. This is because after tax calculation, tax

checks are carried out in both systems.

● SAP BusinessObjects Analysis, edition for Microsoft Oce

In addition to classic SAP ERP reports such as nancial statements, cash ow, or protability reports, you

can use SAP BusinessObjects Analysis, edition for Microsoft Oce for reporting. SAP BusinessObjects

Analysis, edition for Microsoft Oce integrates with Microsoft Excel and helps you to gain insight into

business data and make intelligent decisions that impact corporate performance.

For more information about SAP BusinessObjects Analysis, see SAP Help Portal at http://help.sap.com

Analytics Business Intelligence Analysis .

Contact your SAP Account Executive to verify if you need to purchase a license.

Releases

The add-on DMIS 2011_1_700 (or higher depending on the release of the system) is installed on all source

systems and on the SLT server.

 Note

The minimum support package (SP) level for the steps described in this document is SP08.

For the Central Finance – Business Integration Scenario, SP09 is required.

Central Finance

P U B L I C 13

SAP S/4HANA Cloud as a Source System

● You can use an SAP S/4HANA Cloud system as a source system from which to replicate content to Central

Finance. You can nd more information in the SAP Best Practices Explorer, scope item https://

rapid.sap.com/bp/scopeitems/1W4

For more information, see the product assistance for SAP S/4HANA Cloud on the SAP Help Portal at

https://help.sap.com/viewer/p/SAP_S4HANA_CLOUD under Product Assistance <choose your

language> Finance Accounting and Financial Close Integration of SAP S/4HANA Cloud Source

System with Central Finance .

● You can replicate project master data from a SAP S/4HANA Cloud system as a source system to the

Central Finance (SAP S/4HANA on-premise) system.

For more information, see the product assistance for SAP S/4HANA Cloud on the SAP Help Portal at

https://help.sap.com/viewer/p/SAP_S4HANA_CLOUD under Product Assistance <choose your

language> Finance Accounting and Financial Close Replicating Project Data from SAP S/4HANA

Cloud to Central Finance

Authorizations

The authorization SAP_IUUC_REPL_REMOTE has been assigned to the RFC user in the source system.

The following authorizations have been assigned to the conguration user in the SAP LT Replication Server

system:

● SAP_IUUC_REPL_ADMIN

● SAP_MWB_PROJECT_MANAGER

Business Functions

You have activated the Central Finance (FINS_CFIN) business function in the Switch Framework (transaction

SFW5).

Web Dynpro Applications

For security reasons, the services delivered for Web Dynpro applications are delivered in an inactive state. You

must activate the services you want to use.

For Central Finance you need the service MDG_BS_WD_ID_MATCH_SERVICE.

To activate the services:

1. On the Maintain Services screen (transaction SICF), make sure that the hierarchy type SERVICE is

selected, enter the service name, and choose Execute.

2. Choose Service/Host Activate , to activate the service.

P U B L I C

Central Finance

 Note

You have to perform the procedure for each service that you want to activate.

Once you have activated a service it cannot be reset to inactive.

General Prerequisites

You have ensured that the Central Finance system contains harmonized organizational data and master data

for all the accounting entities that you intend to include in your accounting document.

You have created the master data which is needed to repost the existing FI and CO documents from the source

system.

You have completed the activities relating to mapping in Customizing of your Central Finance system under:

● Key Mapping

● Value Mapping

● Cost Object Mapping

Please note that (in contrast to SAP ERP source systems) cost elements are now G/L Accounts in SAP S/

4HANA. While attributes of cost elements can be maintained with certain validity dates, G/L Accounts are not

time-dependent. This is important to take into account during the initial load, if attributes of cost elements

have been changed during the time frame for which the initial load is being carried out.

G/L Account Mapping

Please be aware that inaccurate G/L account mapping will lead to errors during replication. Open-item

managed G/L accounts from the source system must be mapped to open-item managed G/L accounts in the

Central Finance system. This is required with the initial load if you require activation of Clearing Transfer, even

at a later stage.

If tax is included in your postings, you must ensure that the compatible tax category is congured in the

corresponding accounts.

Constraints

You cannot use Central Finance together with Amount Field Length Extension (AFLE). For details, please see

SAP Note 2643282 .

Central Finance

P U B L I C 15

1.5.1.2 Related Information

Planning Information

For more information about topics not covered in this guide, see the following content on the SAP Help Portal:

● SAP S/4HANA

● SAP Landscape Transformation Replication Server

Before you Start your Implementation

We strongly recommend that you read SAP Note 2148893 . This note provides additional information and

documentation about the installation and conguration of Central Finance and lists all relevant notes that need

to be implemented in either the source systems or the Central Finance system.

Also read SAP Note 2184567 – Central Finance: Frequently Asked Questions.

In addition, ensure that you have installed the latest support package and apply the most recent notes on

component FI-CF and its subcomponents to avoid encountering problems which have already been solved.

Make sure that you have the up-to-date version of each SAP Note, which you can nd at https://

support.sap.com/en/my-support/knowledge-base.html .

Upgrade Information

If you are upgrading either one of your source systems or your Central Finance system to a new release or

feature pack, you may need to perform manual activities in order to use the new functions that are delivered.

For information on these upgrade activities, see SAP Note 2713590 , which is updated regularly.

Important SAP Notes for Source Systems

When an FI or CO document is posted in the source system, additional data has to be stored temporarily and

sent to the Central Finance system. The following SAP note provides an overview of all the SAP notes that are

relevant for the source system and that contain the most recent information on the installation, as well as

corrections to the installation documentation, and need to be implemented in order to enable the document

transfer from the source systems to the Central Finance system using the SAP LT Replication Server. Before

P U B L I C

Central Finance

you start working with Central Finance, ensure that you have implemented all notes that are relevant for the

scope of your scenario:

SAP Note Number Title Description

2323494

Overview of Notes Relevant for

Source System

Collective note for notes relevant for source

systems

Important SAP Notes for the Central Finance System

 Note

We strongly recommend that you upgrade to the latest support package stack to ensure that your system

includes all the latest xes.

Staying on an older support package stack signicantly increases the risk of running into issues that have

already been solved. Upgrading to the latest support package stack also mitigates risk due to the

decreased need to implement SAP Notes and a reduction in the necessary manual activities related to note

implementation.

SAP Note Number Title Description

2217711

Currency Handling Fix of CO Posting in

Central Finance

Improvement for currency handling

2178157

Central Finance: Collective Note for

SAP Simple Finance on-premise edition

1503 SPS1508 – CO part

Relevant for Central Finance System

Contains corrections and improve

ments; shipped with SAP Simple Fi

nance, on-premise edition 1503 SPS

1508.

2179826

DDIC object for note 2178157 Relevant for Central Finance System

Contains information on objects re

quired for SAP Note

2178157 but not

supported by SNOTE

2229985

Unjustied syntax error for ABAP type

check for internal tables

Relevant for Central Finance System.

Contains information on how to prevent

syntax check errors.

2225086

Enabling Central Finance Business

Mapping without the Need to Set Up

System Landscape Directory (SLD)

Relevant for Central Finance System.

Contains information about dening

business systems in your Central Fi

nance scenario.

Central Finance

P U B L I C 17

SAP Note Number Title Description

2298936

Central Finance: Error Handling in AIF

for Simulation of Initial Load for CO

Documents and Cost Objects

Relevant for Central Finance System.

Contains information on using SAP AIF

as the error handling tool in Central Fi

nance to simulate the initial load of cost

objects mapping and CO postings.

2554827

Central Finance: Commitment Posting

on Purchase Requisition and Purchase

Order

Relevant for Central Finance System.

SAP Notes for SAP Application Interface Framework

 Note

See SAP Note 1530212 for information about the installation and setup of AIF.

To use SAP Application Interface Framework (AIF) with Central Finance you must have implemented SAP

Note 2213557 or the relevant support package for AIF.

The required AIF conguration settings are delivered with the SAP notes listed in the following table:

SAP Note Number Title Description

2196783

Central Finance: Error handling with

AIF

Mandatory for the following notes:

2202650

Central Finance: Error Handling in AIF

for Replication of FI Documents

Error Handling in AIF for Replication of

FI Documents

2202691

Central Finance: Error Handling in AIF

for Replication of CO documents and

Cost Objects

Error Handling in AIF for Replication of

CO documents and Cost Objects

Further Important SAP Notes

SAP Note Number Title Description

2223621

Central Finance: Interface for Business

Integration

Describes the steps involved in imple

menting the Central Finance Business

Integration Scenario

2224363

Repository Objects required for Note

2223621

Creation of repository objects (for ex

ample, database tables and structure)

for note 2223621

18 P U B L I C

Central Finance

2228844

Central Finance: Reversal of Active In

voice is not Transferred

The cancellation of an SD invoice in the

sender system is not transferred to the

Central Finance system.

2184391

Structure Label for Node of Table Type

Does Not Work

Mandatory for Central Finance

2179803

cic Functions to Views in /AIF/ERR

Mandatory for Central Finance

2213557

Implementation of BC Sets for AIF Error when activating BC set for AIF

2223801

SLT-Central Finance Enable the Central Finance Business In

tegration Scenario in SLT

2124481

SLT (2011 – SP08) – Correction 03 Relevant for SAP LT Replication Server

2154420

SAP LT Replication Server for SAP Cen

tral Finance

Relevant for SAP LT Replication Server

Contains information about new devel

opments for the SAP LT Replication

Server.

2180924

Supported scenarios in cost object

mapping framework

Contains information on the supported

scenarios of cost object mapping

framework.

2183951

Data Link: Field info get lost Relevant for SAP Application Interface

Framework

2178720

Error Handling: restricted to include

standard structure

Relevant for SAP Application Interface

Framework

Mandatory, if SAP AIF 702 SP02 is not

installed, otherwise error monitor in

SAP AIF will not work.

1946054

SAP Simple Finance, on-premise edi

tion: Transaction codes and programs -

Comparison to EHP7 and EHP8 for SAP

ERP 6.0

Relevant if one of your source systems

is an SAP Simple Finance system.

2103482

Features for Function Module

FINS_CFIN_CO_CENTRAL_POSTING

Function module

FINS_CFIN_CO_CENTRAL_POSTING is

the CO secondary posting interface

which can replicate CO documents

from source system to central system.

2225086

Enabling Central Finance Business

Mapping without the need to set up

Systems Landscape Directory

Relevant for Central Finance system

Central Finance

P U B L I C 19

Further Useful Links

The following table lists further useful links:

Content Location

Information about creating error messages

http://support.sap.com/incidents

SAP Notes search

http://support.sap.com/notes

SAP Software Distribution Center (software download and

ordering of software)

http://support.sap.com/swdc

SAP Analysis for Microsoft Oce

http://help.sap.com/boao

1.5.2 Installing Central Finance

This chapter gives you an overview of the process steps required to use Central Finance. It also provides

references to the documentation required for the process steps.

Before you start the installation process, read SAP Note 2184567 - Central Finance: Frequently Asked

Questions (FAQ), which is updated regularly.

In addition, ensure that you have installed the latest support package and apply the most recent notes on

component FI-CF and its subcomponents to avoid encountering problems which have already been solved.

Find Out More

This image is interactive. Hover over each section for a description. Click the highlighted sections for more

information.

● Data Mapping [page 37]

● Initial Load [page 87]

P U B L I C

Central Finance

● Error Handling [page 29]

● Comparison Reports [page 124]

1.5.2.1 Overview of Activities

The following is an overview of the tasks that you need to carry out in order to implement Central Finance.

Phase Topic Task System Responsible

More Informa

tion

Before You Start Support Package and

SAP Notes

Install the latest

support package

and apply the rele

vant SAP Notes on

component FI-CF

and its subcompo

nents

Source Systems

and Central Fi

nance System

System Adminis

trator

Related Informa

tion

Assign Authoriza

tions

Source

System/SAP

Landscape

Transformation

Server

System Adminis

trator

Prerequisites

Set Up Systems

(Central Finance:

Target System

Settings)

Activate Business

Function

FINS_CFIN

Central Finance

System

System Adminis

trator

Prerequisites

Congure Error

Handling

Application Con

sultant

Error Handling

Assign AIF Runtime

Conguration

Group to Replica

tion Object

Central Finance

System

System Adminis

trator

Set Up RFC Destina

tion for Source Sys

tems

Central Finance

System

System Adminis

trator

Conguration in

Central Finance

System: General

Settings

Dene Logical Sys

tem for Source and

Central Finance

Systems

Source Systems

and Central Fi

nance Systems

System Adminis

trator

Conguration in

Central Finance

System: General

Settings

Central Finance

P U B L I C 21

Phase Topic Task System Responsible

More Informa

tion

Maintain RFC As

signments and Set

tings for Source

Systems

Source Systems System Adminis

trator

Conguration in

Central Finance

System: General

Settings

Assign RFC Destina

tion for Displaying

Objects from

Source Systems

Central Finance

System

System Adminis

trator

Conguration in

Central Finance

System: General

Settings

Check Logical Sys

tem Assignment for

Central Finance Cli

ent

Central Finance

System

System Adminis

trator

Conguration in

Central Finance

System: General

Settings

Activate Tax Consis

tency Check for

Company Codes

Central Finance

System

Dene Decimal Pla

ces for Currencies

in Source Systems

Central Finance

System

System Adminis

trator

Dene Decimal Pla

ces for Currencies

in Source Systems

Central Finance

System

System Adminis

trator

Dene Handling of

Reconciliation Ac

counts per Com

pany Code

Central Finance

System

System Adminis

trator

General Prepara

tions

Carry out Customiz

ing activities for FI

and CO

Central Finance

System

Application Con

sultant

Create master data

in Central Finance

Central Finance

System

Application Con

sultant

Mapping (Cus

tomizing)

Dene Technical

Settings for All In

volved Systems

Central Finance

System OR Sys

tem Landscape

See Also

For more information, see SAP Note 2457869 .

Central Finance

P U B L I C 123

1.5.18 Comparison Reports

To ensure the correctness of the data that you have replicated from your source systems to your Central

Finance system, a number of comparison reports are available.

Use

The comparison reports help you, as a Central Finance user, to analyze the journal entries and the balances and

line items of G/L accounts for nancial accounting between the source and the Central Finance system. For

controlling you can analyze internal CO documents, credit or debit amounts per cost element and line items of

CO documents between the source and the Central Finance system. Additionally, you can analyze line items for

commitments in CO, balances for prot centers and SEPA mandates between the source system and the

Central Finance system. You can also trace the count and detailed data of sales orders, customer invoices,

purchase orders or supplier invoices that have been replicated with Accounting View of Logistics Information

(AVL) from the source system to the Central Finance system.

You can access the comparison reports in the SAP (Easy Access) Menu under Accounting Central Finance

Comparison Reports or Consistency Checks .

Features

In Central Finance you can initially check, whether all journal entries from nancial accounting (FI), all

controlling (CO) documents, all line items for commitments in CO, all prot center documents from the source

system have been posted in the Central Finance system as expected. Controlling documents are internal CO

documents that are transferred with the CO interface and posted to Central Finance. After this, you can go into

details and check, whether credit, debit amounts per G/L account or cost element are the same in the source

and the Central Finance system, or whether for all line items for selected general ledger (G/L) accounts or cost

elements in the source system, or for commitment line items for selected cost elements in the source system,

line items exist in the Central Finance system and total the same amount. You can also compare balances of

prot center documents and SEPA mandates between the source system and the Central Finance system. For

documents that have been replicated with AVL, you can trace the count of documents and you can check,

whether they have been transferred correctly.

You perform all comparison reports in the Central Finance system.

124

P U B L I C

Central Finance

Central Finance: Comparison Reports List

Application Area

Report Name Purpose Transaction

Accounting View of Logistics

(AVL)

AVL Sales Document You use this report to trace

the count and detailed data

(relating to all elds) of sales

documents that should have

been replicated from the

source system to the Central

Finance system and to check

whether they have been

transferred correctly.

FINS_CFIN_DFV_AV_SO

Accounting View of Logistics

(AVL)

AVL Billing Document You use this report to trace

the count and detailed data

(relating to all elds) of billing

documents that should have

been replicated from the

source system to the Central

Finance system and to check

whether they have been

transferred correctly.

FINS_CFIN_DFV_AV_CI

Accounting View of Logistics

(AVL)

AVL Supplier Invoice You use this report to trace

the count and detailed data

(relating to all elds) of sup

plier invoices that should

have been replicated from

the source system to the

Central Finance system and

to check whether they have

been transferred correctly.

FINS_CFIN_DFV_AV_SI

Accounting View of Logistics

(AVL)

AVL Purchasing Document You use this report to trace

the count and detailed data

(relating to all elds) of pur

chase orders that should

have been replicated from

the source system to the

Central Finance system and

to check whether they have

been transferred correctly.

FINS_CFIN_DFV_AV_PO

Financial Accounting Count of Journal Entries You use this report to check

whether all journal entries

(accounting documents)

from the source system have

been posted in the Central

Finance system as expected.

FINS_CFIN_DFV_FI_NUM

Central Finance

P U B L I C 125

Application Area

Report Name Purpose Transaction

Financial Accounting G/L Account Line Items You use this report to check

whether all FI line items for

selected G/L accounts and

document number in a

source system and the

Central Finance system total

the same amount.

FINS_CFIN_DFV_FI_DOC

Financial Accounting G/L Account Balances You use this report to check

whether the debit or credit

amount per G/L account is

the same in a source and the

Central Finance system.

FINS_CFIN_DFV_FI_BAL

Financial Accounting FI Clearing Status of Docu

ment Line Items

You use this report to check

whether the clearing sta

tuses of FI document line

items in the open item man

agement of the source sys

tem and those replicated to

the Central Finance system

are the same.

FINS_CFIN_DFV_CLR

Management Accounting Count of CO Documents You use this report to check

whether all internal control

ling documents (secondary

postings) that have been

transferred with the CO inter

face, have been posted in the

Central Finance system as

expected.

FINS_CFIN_DFV_CO_NUM

Management Accounting Line Items for Cost Elements You use this report to check

whether all CO line items for

selected cost elements and

document number in a

source system and the

Central Finance system total

the same amount.

FINS_CFIN_DFV_CO_DOC

Management Accounting Balances for Cost Elements You use this report to check

whether debit or credit totals

for cost elements used in

secondary postings are iden

tical in a source system and

the Central Finance system.

FINS_CFIN_DFV_CO_BAL

126 P U B L I C

Central Finance

Application Area

Report Name Purpose Transaction

Commitments Count of Line Items for Com

mitments in CO

You use this report to check

whether all commitment line

items have been posted in

the Central Finance system

as expected.

FINS_CFIN_DFV_CMTNUM

Commitments Line Items for Commitments

in CO

You use this report to check

whether for all line items for

commitments for selected

cost elements in the source

system, line items for com

mitments exist in the Central

Finance system and total the

same amount.

FINS_CFIN_DFV_CMTDOC

Prot Center Accounting Count of Prot Center Docu

ments

You use this report to check

whether EC-PCA documents

or balances are replicated to

the Central Finance system

correctly.

FINS_CFIN_DFV_PCA_CN

Prot Center Accounting Balances for Prot Centers

You use this report to check

whether EC-PCA balances in

the source system match the

corresponding balances in

the

Central Finance system.

FINS_CFIN_DFV_PCA_BA

SEPA Mandates SEPA Mandates You use this report to com

pare SEPA mandates be

tween a source system and

the Central Finance system.

CFIN_CPAY_SEPA_REC

Conguration Consistency

Check Report [page 55]

You use this report to check

whether conguration set

tings are consistent in the

source system and the

Central Finance system.

FINS_CFIN_CC

For more information, please display the report documentation of the system by calling up the transactions

listed above and click the Button, or if you are using Web GUI, access the documentation with More

Program Documentation .

The transactions are also part of the user role SAP_SFIN_CFIN_ACCOUNTANT which can be assigned to your

user.

Central Finance

P U B L I C 127

1.5.18.1 Business Process Monitoring in SAP Solution

Manager

Use

To check, whether the number of journal entries to be replicated from a source to the Central Finance system is

within a certain range expected, you can monitor the following two reports with Data Consistency Monitoring

which is part of Business Process Monitoring in the SAP Solution Manager:

● Central Finance: Comparison of FI Document Headers

● Central Finance: Comparison of CO Document Headers

This allows you to automate the manual evaluation of the results in the batch job spool list. It also oers you a

central alert inbox or notications being sent.

Prerequisites

● You have created a variant for the reports in the Central Finance system.

● You have scheduled a job for the reports in the Central Finance system.

● The Add-On ST-A/PI Version 01S Support Package 3 or higher (Solution Tools Application Plug-In) is

available with the Central Finance system.

How-to Set up Business Process Monitoring for the Comparison Reports

For general information about the set up procedure, please refer to the Setup Guides for the Business Process

Monitoring depending on your SAP Solution Manager release. Once you are performing the steps in the set up

procedure, you can nd the monitors for the reports by ltering for Application Area (Controlling or Financial

Accounting) or Data Consistency:

● Monitor ID: DCCFCODC

Monitor Name: Central Finance Reconciliation: CO Document Count

● Monitor ID: DCCFFIDC

Monitor Name: Central Finance Reconciliation: FI Document Count

As part of the set up, you ll in the following information:

● The name of the report variant

● The scheduling for the data collection

● The thresholds for alerting

● Optional settings for automatic notications or incidents creation

128

P U B L I C

Central Finance

See Also

● For more information about Business Process Monitoring in SAP Solution Manager, see Business Process

Operations.

● For more information about the set up procedure, see the Setup Guides for Business Process Monitoring on

https://wiki.scn.sap.com/wiki/display/SM/Business+Process+Monitoring .

1.5.18.2 Advanced Integration Monitoring in SAP Focused

Run

You can do the monitoring for the listed Central Finance comparison reports using SAP Focused Run:

Technical Report Name

Report Name Transaction

FINS_CFIN_DFV_FI_DOC_COUNT

You use this report to check whether all

journal entries (accounting documents)

from the source system have been

posted in the Central Finance system as

expected.

FINS_CFIN_DFV_FI_NUM

FINS_CFIN_DFV_CO_DOC_COUNT

You use this report to check whether all

internal controlling documents (secon

dary postings) that have been transfer

red with the CO interface, have been

posted in the Central Finance system as

expected.

FINS_CFIN_DFV_CO_NUM

FINS_CFIN_DFV_PCA_DOC_COUNT

You use this report to check whether

EC-PCA documents or balances are re

plicated to the Central Finance system

correctly.

FINS_CFIN_DFV_PCA_CN

FINS_CFIN_DFV_CMT_DOC_COUNT

You use this report to check whether all

commitment line items have been

posted in the Central Finance system as

expected.

FINS_CFIN_DFV_CMTNUM

For more information on how to congure these Central Finance comparison reports for use in SAP Focused

Run, you can read Advanced Integration Monitoring in SAP Focused Run: Central Finance .

1.5.19 Activation of Clearing Transfer and Handling of Open

Items

In the source system, open items can be cleared as part of a payment run or can be cleared manually.

Central Finance

P U B L I C 129

In the activity Activate Clearing Transfer for Source Systems - which is available as of release SAP S/4HANA

1809 FPS0 - you can activate the transfer of clearings from one or more source systems to your Central

Finance system.

 Note

The activation of clearing transfer is a prerequisite for Central Payment.

 Note

Before you activate clearing transfer for a logical sender system, you should be aware of the restrictions

described in SAP Note 2292043 .

You should make yourself familiar with these restrictions before you set up your target system as a Central

Finance system, even if you do not activate the transfer of clearings until a later point in time. This is

because some conguration settings (for example, currency settings relating to company codes) cannot be

changed later. For restrictions relating specically to currency settings that apply to the transfer of

clearings, see SAP Note

2863836 .

 Note

When you activate clearing transfer, the following clearing information in documents that have already

been technically cleared is not updated in the Central Finance system to match the information in the

source system:

● AUGDT: Clearing Date

● AUGCP: Clearing Entry Date

● AUGBL: Document Number of the Clearing Document

● AUGGJ: Clearing Fiscal Year

Prerequisites

Before you activate clearing transfer you must have installed SAP Note 2633841 in all the source systems

for which you want to activate clearing transfer.

Activation of Clearing Transfer Depending on Your Release

The table below lays out the ways in which clearing transfer can be activated, depending on the release of your

Central Finance system and the SAP notes that you have implemented in your source system.

For Central Finance systems on release SAP S/4HANA 1809 and higher, we recommend that you follow

scenario 1. That is, that you manually activate clearing transfer via the relevant IMG activity before the initial

load.

For scenario 2 you should note the following system behavior:

● Transaction FINS_MIG_CJ3 activates clearing transfer for all company codes within a client.

130

P U B L I C

Central Finance

● If you then, for any reason, you subsequently carry out a new initial load for one of more of these company

codes, remember that clearing transfer will already be active.

Scenario

Central Fi

nance System Source System

Activation Be

fore Initial

Load (CFIN

System)

Source System

Behavior Dur

ing Ongoing

Replication

Activation Af

ter Initial Load

(CFIN System) Comments

1 SAP S/4HANA

1809 FPS00

and higher

Contains clear

ing notes (pre

viously deliv

ered via pilot

note 2292043)

Possible via

IMG activity Ac

tivate Clearing

Transfer for

Source Sys

tems

Clearing docu

ments are also

replicated

Possible via

IMG using activ

ities:

Activate Clear

ing Transfer for

Source Sys

tems

and

Reopen Techni

cally Cleared

Items

Recommended

approach is to

activate clear

ing transfer be

fore the initial

load.

Lower than SAP

S/4HANA 1809

FPS00

Contains clear

ing notes (pre

viously deliv

ered via pilot

note 2292043)

Not possible

Clearing docu

ments are also

replicated

Possible with

FINS_MIG_CJ3

after the initial

load

Clearings are

not posted until

FINS_MIG_CJ3

has been exe

cuted

Lower than SAP

S/4HANA 1809

FPS00

Does not con

tain clearing

notes (cus

tomer must im

plement note

2292043)

Not possible

Clearing docu

ments are not

replicated

Possible with

FINS_MIG_CJ3

after the initial

load

Notes must be

implemented

4 SAP S/4HANA

1809 FPS00

and higher

Does not con

tain clearing

notes (cus

tomer must im

plement note

2292043)

Possible via

IMG activity Ac

tivate Clearing

Transfer for

Source Sys

tems

Clearing docu

ments are not

replicated

Possible via

IMG using activ

ities:

Activate Clear

ing Transfer for

Source Sys

tems

and

Reopen Techni

cally Cleared

Items

Notes must be

implemented

Prerequisites for Scenarios 1 and 4:

You have made the settings for the transfer of balances and documents in the activity General Replication

Settings in your source systems.

Central Finance

P U B L I C 131

1. In the activity Activate Clearing Transfer, dene the logical source systems for which you want to activate

clearing transfer.

If you have need to deactivate clearing transfer for a particular source system, you can do so in the activity

Deactivate Clearing Transfer (transaction FINS_CFIN_DEACT_CLR).

Note that deactivation is only possible if there are no open items in the Central Finance. Therefore, you can

only carry out this activity before you start the extraction step of the initial load.

2. Carry out the activity Extract Data for Initial Load.

Clearing Transfer for Customers Upgrading to SAP S/4HANA 1809, FPS00,

FPS1, FPS2

If you have upgraded your implementation of SAP S/4HANA from an earlier release to a SAP S/4HANA 1809

release but have not previously activated clearing transfer and want to do so in SAP S/4HANA 1809 FPS00,

FPS01, or FPS02 you should carry out the following activities in the order described here.

Prerequisites:

● You have made the settings for the transfer of balances and documents in the activity General Replication

Settings in your source systems.

● You have started the step Extract Data for the Initial Load.

1. In the activity Activate Clearing Transfer dene the logical source systems for which you want to activate

clearing transfer.

Note that you cannot deactivate clearing transfer because open items will already have been transferred to

the Central Finance system as part of the initial load.

2. Carry out the activity Reopen Technical Clearings.

This activity reopens items which have the status technically cleared in the target system so that they have

the same status as in the source system.

 Note

If you have not yet executed an initial load, then you can skip this activity because no documents will

have been posted.

3. Carry out the activity Monitor Reopening of Technically Cleared Items to check whether the activity

Reopen Technically Cleared Items has successfully processed all relevant documents.

 Note

The initial load does not transfer any clearings, even if you have activated clearing transfer.

Once you have activated clearing transfer, new open items are no longer technically cleared but reect the

clearing status of the item in the source system.

Restrictions

The following restrictions apply to the processing of clearing data in Central Finance:

132

P U B L I C

Central Finance

● Currency Congurations

The currency settings of the company codes and ledgers in the Central Finance system need to be set up

identically to those of the corresponding company codes and ledgers in the source systems. This includes

the Control Data settings for G/L accounts.

For a clearing posting transferred to Central Finance, the amounts of additional currencies are always

translated with the exchange rate of the current translation date. An open item, however, has to be cleared

with the exchange rate of the translation date when the open item was originally posted.

So, in the current scope of the functionality, the clearing would not balance to zero for each currency and

dierences would not be posted as an exchange rate dierence in case of additional or dierent local

currencies in the Central Finance system.

Example

Open items and clearings are transferred from company code A in the sender system to company code B

in the target system.

Company code A in the sender system has only one local currency.

Company code B in the target system has the same local currency as company code A and an additional

second local currency.

If the exchange rate of the second local currency is changed between when the invoice is posted and when

the corresponding clearing document is posted, the line item containing the resulting exchange rate

dierence for the second local currency will be missing in the clearing document in the target system.

 Note

If you create a company code in Central Finance (as of release S/4HANA 1610), by default the

controlling area currency type is created as a local currency in FI. If your source system does not use

the controlling area currency type as a local currency in FI you must also remove this setting in the

Central Finance system.

To check or change the setting, see the elds 1st FI currency, 2nd FI currency and 3rd FI currency in

the transaction FINSC_LEDGER for the company code in question.

You dene the currency type for the controlling area currency in transaction OX06.

● Foreign currency revaluations

If the source system is on classic General Ledger Accounting (classic G/L), foreign currency revaluations

are posted with a dierent logic than in S/4HANA or New General Ledger Accounting (New G/L). In classic

G/L, the foreign currency revaluation correction dierences can be stored in the open item (BSEG-BDIF*)

which was used to explain the balance of the corresponding balance sheet correction amount.

In S/4HANA the valuation dierences are not stored in the open item.

If the foreign currency revaluation is performed in the source system, the valuation dierences amount per

item cannot be transferred to the Central Finance system. As a consequence, the balance on the balance

sheet correction account can only be explained in the source system.

The same applies for Exchange Rate Gain/Loss Realized (BSEG-RDIF*), Realized Exchange Rate Gain/

Loss for partial payments and Penalty Charge Amounts (BSEG-PENLC*).

● Dierences in number of currency decimals between source system and Central Finance system

The Central Finance system needs to be congured in a way that at least as many decimals are dened for

a currency as maintained in the source system.

If more than one source system is connected, the Central Finance system needs to have as many decimals

set for each currency as dened in the source system with the highest number of decimals for this

currency (if the source system currency decimals are maintained dierent).

This is needed to prevent rounding dierences which would occur in the target system otherwise. These

rounding dierences could lead to lost open items if very small amounts are rounded to zero amount. This

would prevent subsequent clearings which reference these open items.

Central Finance

P U B L I C 133

Additionally, rounding dierences would lead to clearings which would not balance to zero and reset

clearings would also fail.

● Cross-Company postings from the Reconciliation Ledger (transaction KALC)

Osetting lines on company code clearing accounts resulting from postings of the reconciliation ledger

(transaction KALC) can be managed as open items in the source system.

Clearings of these open items cannot be transferred to the Central Finance system with the current

functional scope.

● Document splitting

The settings of document splitting need to be set up the same way in the source and Central Finance

systems. Replication into Central Finance with document splitting active from systems where document

splitting is inactive is not an out-of-the-box feature of the product.

For follow-up costs (such as cash discount, exchange rate dierences, or penalty interests) or closing

activities in FI (for example, revaluation of open items, Balance Sheet Supplement, Open Item Analysis)

splitting characteristics are derived by the clearing transaction or the closing transactions in the source

system. If the splitting conguration is set up dierently in the source system, characteristics might be

missing and the posting might be denied.

● Document summarization

The settings of document summarization need to be setup the same way in the source and Central Finance

systems.

This is currently essential because a later clearing document will only hold clearing data for cleared

document items known in the source system and not for additional items which may exist, if the document

summarization does not summarize some items in the target system which were summarized in the

source system.

If you used in the source system activity FI Summarization Dependent on the Object Type (transaction

OBCY) you can still use activity Enhanced Document Summarization in FI (transaction OBCYX) in the

target Central Finance System. Here you can congure the summarization also per Company Code which

should allow you to harmonize your conguration with the various source systems. (This would not work

though, if you have multiple logical systems with dierent summarization replicating into the same

Company Code).

You should be aware that if you add customer-specic elds to BSEG, e.g. via the coding-block (CI_COBL),

this may prevent the system summarizing BSEG in the same way as in the target. Because of this, elds

that you need for reporting that are added on line item level should be added to ACDOCA only, not to BSEG.

● Settlements of Advance Payment Transfer Postings in Real Estate Management

Clearings that result from settlements of advance payment transfer postings in Real Estate Management

(especially SAP transactions: RESCSE, RESCBC, RESRSE, RESRBCSINGLE, RESCSECO, RESCSETN) do not

clear in the Central Finance system. The postings are transferred but the clearing is not executed.

● Missing Open G/L-items from Initial Load

The Initial Load (FI) does not transfer open-item-managed G/L items that fall within the period of the

balance load.

A clearing that is transferred from the source system that clears a G/L item that fell into this period, cannot

be cleared as it does not exist. This limitation is resolved if SAP Notes 2396399 and 2397166 are

implemented before the extraction was performed.

● Clearing of Open Items Transferred by the Initial Load

Clearing of open items which have been transferred by initial load: only open items which have been

transferred after implementation of SAP note 2210341 (source system) can be cleared successfully. If

this note was not applied before transfer by the initial load, the resulting open items will not contain a

reference to their predecessor in their line items (BUZEI_SENDER) which makes a clearing processing

impossible in the target system.

● Postings from Loans Accounting (TR-LO-AC)

134

P U B L I C

Central Finance

Clearings from Loans Accounting do not clear in the Central Finance system.

The postings are transferred but the clearing is not executed.

● Open-Item Managed G/L Accounts

Clearing transfer can only work properly if open item-managed G/L accounts from the source system are

mapped to G/L accounts in the Central Finance system which are also open-item managed. Otherwise the

replicated clearing transactions run into error.

● Withholding Tax

If withholding tax is calculated at payment in the source system the withholding tax of the corresponding

invoice in Central Finance is not updated.

Related Information

Replicating Clearing Information Using the Third-Party System Interface [page 211]

1.5.19.1 Retrieve Missing Clearing Items

You use this report to retrieve missing items related to clearing and clearing resets.

In Central Finance, an AIF message may become stuck with the error message FINS_CFIN_AC_DOC051

Referenced document not yet posted (Comp.Code &1, F.Year &2, Document &3).

This message is issued when a reset clearing or a clearing document has been transferred to Central Finance

but it references an item which has not been transferred to Central Finance.

This can occur when the system processes clearing or reset clearing documents, which aect older items that

lay in the initial load period during which only balances are transferred.

To process these clearing or reset clearing documents it is necessary to retrieve the missing aected

document items afterwards.

To do so, you can use the report RFINS_CFIN_CORR_MISSING_CLRITM.

Settings

Under Transaction Selection, you must enter a value in the eld Logical Sender System to limit the number of

AIF messages to be processed.

When you run the report, the system identies all AIF messages that are stuck with the error message

FINS_CFIN_AC_DOC051 Referenced document not yet posted (Comp.Code &1, F.Year &2, Document &3).

You can also use the following parameters to lter the results:

● Company Code in Sender System

● AIF Message GUID

● Reference Procedure

Central Finance

P U B L I C 135

● Reference Document

● Reference Org. Unit

● Logical System

Under Settings for Execution, you can also choose to run the report in test mode.

If you choose test mode, no documents will be posted and the system only displays a list of all AIF messages

which reference missing items that need to be retrieved.

If you do not choose test mode, you need to specify a posting date under Settings for Execution. The system

then applies this posting date to the documents which are subsequently retrieved.

You can also dene a document type for the documents to be posted. If you do not dene a document type, the

system will retain the document type that the retrieved documents had in the source system.

Open items contained in the documents which are subsequently retrieved will be automatically set to

technically cleared in the Central Finance system.

In most cases, missing open items are referenced by a reset clearing.

After the missing items have been retrieved and the corresponding reset clearing AIF message has been

restarted, all referenced open items will automatically be reopened as soon as the reset clearing has been

processed.

In rare cases, the reset clearing may also be missing because it was processed before clearing transfer was

activated. This means that the rst AIF message which references the missing items will not be a reset clearing

but a clearing AIF message.

If this happens, run report RFINS_CFIN_REOPN_TECH_CLRD_DOC to reopen all technically cleared open items

which are referenced by the clearing AIF message.

1.5.20 Special Business Transactions: Additional Information

Cross-Company Code Postings with Document Splitting in the Target System

If you have activated document splitting in the target system, you should take into account the following

information regarding cross-company code postings.

To ensure that cross-company code postings are correctly replicated, all relevant company codes must be

activated for transfer, otherwise, only documents of the active company codes will be transferred. This is likely

to result in errors because the document splitter cannot determine the relevant split information from the

documents that are skipped due to inactive company codes.

Company Codes Belonging to the Same Tax Group

If you choose to work with initial load groups (as described under FI Initial Load Execution for All Company

Codes or for Selected Company Codes - Settings for the Initial Load of FI Documents [page 89]), we

recommend that you include in the same initial load group all company codes that belong to the same tax

group.

136

P U B L I C

Central Finance

Handling of Reversals

Reversed document not available in Central Finance system

When reversing transactions are posted in Central Finance via AIF the following issues may occur:

● If the reversal was posted as a reference-based reversal in the source system (processing via FM

AC_DOCUMENT_REVERSE), for example, a reversal posted via transaction VF11 or VF02 (SD invoice

reversal) or via BAPI_ACC_DOCUMENT_REV_POST, while the reversed document has never been replicated

into Central Finance, the transaction can't be posted. AIF displays error "Referenced document not yet

posted (Comp.Code &1, F.Year &2, Document &3)" (FINS_CFIN_AC_DOC051) in such cases.

● If the reversed document was not covered by the initial load of documents (or ongoing transfer) but was

posted via the initial load of open items, then the reversal document reverses just the open item document,

which does not appropriately reect the postings of the reversal document in the source system, because

dierent accounts are addressed (substitution account instead of reconciliation account).

For more information on how to deal with these reversals, see SAP Note 2338908 - Central Finance:

Processing of reversals for documents which are not available in the target system.

Posting of reversal in Central Finance system not possible

In some cases, a reversal document has been posted in the source system with transactions VF11 and FB08 or

via BAPI BAPI_ACC_DOCUMENT_REV_POST. However, posting of the replicated document in the Central

Finance system fails with an error message. For information on how to deal with this, see SAP Note 2354289

1.5.21 Additional Settings and Enhancements

1.5.21.1 Settings for Decimals and Currencies

In some cases, it may be necessary to make certain settings in Central Finance relating to decimals and

currencies.

Dene Decimal Places for Currencies in Source Systems

You carry out this activity in Customizing for Central Finance under Central Finance: Target System Settings

Set Up Systems .

In this activity you specify the number of decimal places that are dened for currencies in the source system, if

this number is dierent than in the Central Finance system. Note that this does not change the settings for

decimal places in either system but allows the Central Finance system to handle the dierent settings

correctly.

Central Finance

P U B L I C 137

If you need to dene accounts to which rounding dierences resulting from diering decimal settings are

posted, you can use transaction FINS_CFIN_DECACCDET.

 Note

You should bear in mind that several scenarios, such as Clearing Transfer, Central Tax, and Central

Payment, do not allow diering decimal settings. In particular, once ongoing replication has been started,

decreasing the number of decimals will lead to errors.

Especially for third-party systems: The data transferred using the third-party system interface for Central

Finance has to use the same currency keys including the number of decimals as dened in the Central

Finance system.

BAdI: Adjust Decimals

You carry out this activity in Customizing for Central Finance under Central Finance: Target System Settings

BAdIs: Central Finance .

The Business-Add-In BADI_FINS_CFIN_CURR_ADJ is used in the mapping step of the Central Finance

accounting document replication process in the target system.

It allows you to replace the SAP standard logic related to the general handling of dierences in the number of

decimal places for currencies between source systems and the Central Finance system.

1.5.22 Display Information from Central Finance in the

Source Systems

With SD document ow enhancement or side panel, you can retrieve information from Central Finance when

working in the source systems.

For details on SD document ow enhancement, see SD Document Flow Enhancement [page 139].

For details on side panel, see Side Panels in Central Finance [page 139].

138

P U B L I C

Central Finance

1.5.22.1 SD Document Flow Enhancement

You use the SD document ow enhancement to view details of a replicated document and its clearing status in

Central Finance when you are working in a source system.

Prerequisite

You have activated Central Payment. See details on congurating Central Payment in Settings for Central

Payment in Source Systems [page 153].

Features

In SD document ow, the system retrieves information relevant to the replicated documents from Central

Finance and displays the information as an entry below the corresponding source document entry.

The document information includes the document number in Central Finance, and the document's clearing

status.

 Note

For AR/AP documents in the source system, the status Technically Cleared is displayed in SD document

ow.

1.5.22.2 Side Panels in Central Finance

You can use side panels to display corresponding information from the Central Finance system when you are

working in a source system transaction.

Note that side panels can only run on classic SAP GUI transactions in (NetWeaver) Business Client. They

cannot be accessed from UI5 Fiori apps.

Central Finance

P U B L I C 139

1.5.22.2.1 Setting Up Side Panels

Context

To work with side panels, you must rst install and set up (NetWeaver) Business Client for Desktop version 3.5

PL5 or version 4.0 or higher. For more information, see SAP Business Client.

Note that side panels do not work if you simply use SAP Business Client to log on to your SAP Logon

connections. First you need to congure a Business Client connection for each system for which you want to

enable side panels. For information on how to do this, see Side Panel.

Set Up Roles

In the Central Finance system, copy the role menu from the role SAP_SFIN_CFIN_SP_MENU to all the roles in

the source systems from which you want to access the side panels.

For information on how to do this, see Remote Systems.

Set up an RFC connection from the source system to a Central Finance system. Since the side panels are based

on WebDynpro, a HTTP or HTTPS connection (type H) besides ABAP connection (type 3) is required.

Assign users in all systems for which the side panels should be displayed.

Since the side panels run on the Central Finance system, all users who you want to allow to see the side panels

when they are working in the source system must also have a user in the Central Finance system.

Create roles in the Central Finance system and add the authorization defaults for the following objects:

● Web dynpro application conguration FINS_CFIN_SP_ACDOC to use FI Document side panel

● Web dynpro application conguration FINS_CFIN_SP_MD to use Master Data side panel

● Transaction FINS_CFIN_SP_AIF to open AIF cockpit from side panel

It may be necessary to assign additional authorization objects to enable users to jump directly to the

transaction to display FI document data and master data.

Maintain organizational levels and assign users to the roles as required.

Basis Connections

We recommend that you either set up an SSO scenario using client certicates (see: X.509 Client Certicates)

or to use log on tickets (see Logon Tickets).

This ensures that the user does not have to manually log on to the Central Finance system when opening the

side panel.

Side panels that run on the Central Finance system need to retrieve some data from the source systems via

RFC. To enable this, you must congure an RFC connection and assign it to the Side Panel usage in

Customizing of Central Finance.

You do this in the activity Maintain Source Systems and RFC Assignments.

140

P U B L I C

Central Finance

Use the role SAP_SFIN_CFIN_SP_RFC as a template to assign the required authorizations for the RFC user in

the source systems.

Set Up Side Panels

The last step is to enable side panels in the Central Finance system and activate SAP GUI scripting in read-only

mode (at a minimum) in all systems for which you want to display side panels. For more information, see

Getting Started with Side Panel Congurations.

Side Panels and CHIPs

Two side panels and 13 CHIPs are delivered with Central Finance:

1. Side Panel: CFIN FI Document

1. FI Document – Header

2. FI Document - Entry View Items

3. FI Document - G/L View Items

4. FI Document – Account Mapping

5. FI Document - Clearing Status

6. FI Document - Cost Object

7. FI Document - Cost Center

8. FI Document – Customer

9. FI Document - Vendor

2. Side Panel: MD: CFIN Master Data

1. Master Data - Cost Center

2. Master Data - Customer

3. Master Data - G/L Account

4. Master Data - Vendor

Customizing

For each side panel there is one catalogue with the same name containing all the CHIPs for the side panel. You

can create your own side panels and add one or several of the provided CHIPs to it. You can also combine the

Central Finance CHIPs with other CHIPs on customized side panels. In addition, you can remove individual

CHIPs from the predened side panels via Customizing.

CHIPs for which no data can be retrieved from the current transaction screen are hidden.

In the menu role, you dene which side panel is shown for which transaction. The application alias of the folder

contains a list of transaction codes. All side panels assigned to the folder will open when accessing one of those

transactions. If more than one side panel applies to the same transaction the user can select the active side

panel from a dropdown.

Below is a list of the main transactions supported for each side panel and CHIP:

Side Panel CHIP Transaction Code in Source System

CFIN: FI Document FI Document-Header FB03/MIR4/VF03

FI Document-Line Items FB03/MIR4/VF03

FI Document-Clear Status FB03/MIR4/VF03

Central Finance

P U B L I C 141

Side Panel CHIP Transaction Code in Source System

FI Document-Account Mapping FB03/MIR4/VF03

FI Document-Customer Mapping FB03/MIR4/VF03

FI Document-Cost Center Mapping FB03/MIR4/VF03

FI Document-Vendor Mapping FB03/MIR4/VF03

FI Document-Cost Object Mapping FB03/MIR4/VF03

CFIN: Master Data G/L Account Master Data

FS00

Customer Master data

XD03

Vendor Master Data

XK03

Cost Center Master Data

KS03

These transactions need be maintained in the menu role, you can also add more transactions like FB02, FB03L

into the role to support more transactions.

The visual settings for each CHIP can also be changed from default via Customizing. You can access the

Customizing for a CHIP via the menu entry “Customize Form” of the tray menu of each CHIP.

Per default, the CHIPs expand to display all lines in table views. This setting can be overridden in Customizing

and you can choose to display a xed number of rows instead.

Personalization

Users can also override the default settings that control which CHIPs are shown on which side panel and what

the CHIPs look like via personalization.

Personalization is stored per user ID. For the table views in the CHIPs there is a button that allows you to access

personalization directly. Here, you can choose which columns to hide and in which order to display information.

Personalization can be reset at any time. The display then returns to the default dened in Customizing (if any)

or delivered as part of the standard conguration.

Links

Most CHIPs contain links. When the user clicks a link, the corresponding object is opened in a new transaction

window. For example, when you click the document number in the FI Document - Header CHIP, the

corresponding FI document will open. Depending on the link the object will be opened either in the source or in

the Central Finance system. You should bear in mind that the side panel for the newly opened transaction will

not work properly if you jump from one system to another. This is because the business client will always

consider the system that the user originally logged on to as the system of the main transaction. This means

that if you log on to the source system and then jump to a document inside the Central Finance system, the

side panel will still assume you are working in the source system and therefore will not be able to fetch the

corresponding document inside the side panel.

142

P U B L I C

Central Finance

1.5.22.2.2 CHIP Details

1. FI Document – Header

If you open this CHIP in the Central Finance system, it displays the corresponding sender document from

the source system.

If you open this CHIP in the source system, it displays the corresponding Central Finance document. If the

source transaction displays information about the MM invoice (business object BUS2081) or billing

document - SD invoice (business object VBRK), the CHIP fetches the corresponding FI documents based

on the reference information in eld AWKEY of table BKPF.

If there is more than one document that matches, the rst document will be displayed. In this case, there is

a dropdown list on top of the CHIP that lists all matching documents, allowing the user to change the

selection. If the user selects another document, all CHIPs on the same side panel that refer to the Central

Finance FI document will be refreshed with the corresponding data of the selected document. If the header

is not on the side panel, all CHIPs referring to the FI document always display only the rst matching

document.

If no Central Finance document can be found, the system refers to the AIF log for the source document. If

no source document number is available, the system will try to fetch the source document number for the

matching AWKEY in the source system rst. If there are AIF error messages for the source document they

will be displayed in the message area of the side panel and a button is displayed in the header CHIP to

enable the user to jump directly to the AIF cockpit to reprocess this document. If no information can be

retrieved from the error cockpit, an error message is displayed telling the user that there is no Central

Finance document for this source FI document.

Note that all CHIPs referring to FI documents only work if the document display is set to ALV Grid Control

in Transaction FB00 (Account Editing Options). For technical reasons, the screen elds that determine the

full key of the document to be displayed cannot be transferred to the side panel if you choose Classic

Display or ALV Classic List.

2. FI Document - Entry View Items

This CHIP displays all line items of the entry view for the document as selected in the Header. If you are

using the line item view in the main transaction, only those entry view items that correspond to the line

item that is shown in the main transaction are displayed. The connection on line item level between the

source and Central Finance systems is made in the eld BUZEI_SENDER eld in the table BSEG.

3. FI Document - G/L View Items

This CHIP displays all line items of the G/L view of the leading ledger for the document selected in the

header. Since there is no technical connection between line items in the entry view and line items of G/L

view this CHIP always shows all line items regardless of whether you are using the header or the line item

view in the main transaction. This CHIP is disabled when the user is working in the Central Finance system.

4. FI Document – Account Mapping

This CHIP displays the G/L accounts from the source document entry view that are mapped to the G/L

accounts of the corresponding line items of target document entry view. If the user is working in the line

item view in the main transaction, it only displays the account mapping for the selected line item.

5. FI Document - Clearing Status

This CHIP displays the line item mapping between the source and Central Finance systems and the

clearing status of the Central Finance document if opened from the source system or of the source

document if opened in the Central Finance system.

6. FI Document - Cost Object

This CHIP works in the same way as Account Mapping but for cost object data.

7. FI Document - Cost Center

This CHIP works in the same way as Account Mapping but for cost center data.

Central Finance

P U B L I C 143

8. FI Document – Customer

This CHIP works in the same way as Account Mapping but for customer data.

9. FI Document – Vendor

This CHIP works in the same way as Account Mapping but for vendors.

10. Master Data - Cost Center

This CHIP displays the master data for a cost center.

If the user is working in the line item view of an FI document in the main transaction, the system will fetch

the cost center of the corresponding line item in the document as selected in FI Document – Header. If (as

it is delivered in standard) the FI Document – Header is not on the same side panel as this CHIP, the

mapping of the rst matching document is always used. In most cases this should lead to the same result.

If you need to be able to choose from which document the mapping should be used, you must add the FI –

Document Header to the same side panel as the master data CHIPs.

If the user is not working in the line item view but there is a cost center on the screen, the system accesses

the mapping tool in the Central Finance system to get the mapped cost center. This scenario only works if

the user is working in the source system because there could be more than one source system with

dierent mappings and the master data side panels do not currently support the selection of multiple

mappings.

11. Master Data – Customer

Works in the same way as Master Data – Cost Center but for customer data.

12. Master Data - G/L Account

Works in the same way as Master Data – Cost Center but for G/L account data.

13. Master Data – Vendor

Works in the same way as Master Data – Cost Center but for vendor data.

1.5.23 Accounting View of Logistics Information (AVL):

Overview

You use the Accounting View of Logistics Information to replicate logistics data from your source systems to

the Central Finance system. This data is required in order to carry out operations and reporting in the Central

Finance system.

A dened subset of logistics information is replicated from a source system to the Central Finance system for:

● Sales orders (including pricing documents)

● Customer invoices (including pricing documents)

● Purchase orders

● Supplier invoices

If you use the CO-PA functionality during SD implementation, please note that:

● CO-PA master data is part of the dened subset for sales orders and is available in the AVL.

● CO-PA data for the customer invoice is replicated via the corresponding journal entry and is not available in

the AVL.

AVL uses separate tables to store a subset of logistics data in Central Finance.

Historical logistics data in the source systems can be transferred to Central Finance with the generic initial load

functionality of SLT. SLT content includes sample lters that allow you to restrict the transfer, for example, to a

specic time period or company code.

144

P U B L I C

Central Finance

Deletion Report

You use the deletion report to clean up the Accounting View of Logistics data. Logistics data in the source

system which is deleted or archived is marked with a status indicator D (deleted) or A (archived) in Central

Finance. If you want to clean up and physically delete the data in the Central Finance system, you can use this

report by selecting operation D (for deleted data) or A (for archived data). However, you should note that the

legal archiving of the documents must be executed in the original source system.

To access the deletion report, call transaction FINS_CFIN_AVL_DEL or execute the report

FINS_CFIN_AV_DOC_DELETE in the Central Finance system. For the details on the usage of this report, display

the report documentation by clicking the button.

Comparison Reports

You use the comparison reports to compare the AVL data in the Central Finance system with the data in the

source system. You can trace the number and detailed data (relating to all elds) of replicated logistics

transaction documents that should have been replicated to the Central Finance system and check whether

they have been transferred correctly.

To access the comparison reports, call transaction:

FINS_CFIN_DFV_AV_SO for AVL Sales Document

FINS_CFIN_DFV_AV_CI for AVL Billing Document

FINS_CFIN_DFV_AV_SI for AVL Supplier Invoice

FINS_CFIN_DFV_AV_PO for AVL Purchasing Document

Please note that you have to apply SAP Note 2799798 in the source system before using the comparison

reports.

Prerequisites

● You have maintained initial load objects and replication objects in SAP SLT for the Accounting View of

Logistics Information.

● You have congured the mapping entities needed for key mapping, value mapping, cost object mapping, or

CO-PA mapping. See more information in Conguration in Central Finance System: Mapping [page 39].

● You have applied SAP Note 2679506 , 2647022 and 2735582 for source systems.

Restrictions

● The AVL is only supported for source systems of SAP ERP 6.0 EhP3 and higher, including SAP S/4HANA

systems. (Replication of purchase orders is only supported for source systems of SAP ERP 6.0 EhP4 and

higher.)

Central Finance

P U B L I C 145

● Only one client per source system is supported in one SLT conguration.

● Data in the AVL (except purchasing documents and data for which a mapping relationship has been

maintained, for example CO-PA or WBS data) is not validated against the Customizing nor the master data

in the Central Finance system, which is dierent from General Ledger entries in the Central Finance

processing.

 Note

You can activate validation for purchasing documents in table CFIN_AV_IMP_CLS. Open the table in

transaction SE16 and set parameters as follows:

INTERFACE

IFNAME CLASS

IF_FINS_CFIN_AV_PO_V_ACC AV_PO CL_FINS_CFIN_AV_PO_V_ACC

Recommendation

You can choose whether to maintain business mapping or not. If you have maintained business mapping, use

the report FINS_CFIN_MAPPING to validate the consistency of mapping results.

 Note

(You can access this report using SAP Menu under Accounting Central Finance Mapping or using

transaction FINS_CFIN_MAP_MANAGE.)

To congure the AVL scenario in your landscape, carry out the following steps in the stated sequence:

1. AVL Scenario: Conguration in the Source Systems [page 146]

2. AVL Scenario: Conguration in the Central Finance System [page 147]

3. AVL Scenario: Conguration in SAP SLT [page 148]

1.5.23.1 AVL Scenario: Conguration in the Source Systems

Make sure you carry out the following congurations in the source systems as needed before using AVL.

● In order to enable the transfer of changes to sales orders, you must activate the business function

LOG_ESOA_OPS_2 in your source systems. You can check, whether the business function is activated using

transaction SFW5, and activate the business function using transaction SFW2.

● You are either working with the latest available support package or you have installed SAP Note 2647022

● If you use Project-ID as a CO-PA characteristic, you need to implement SAP Note 2679506 .

● If you are replicating purchase orders, you need to implement SAP Note 2735582 .

146

P U B L I C

Central Finance

1.5.23.2 AVL Scenario: Conguration in the Central Finance

System

Make sure you carry out the following congurations in the Central Finance system before using AVL.

Prerequisites

Make congurations for SAP AIF and Business Mapping as required.

Conguration for SAP AIF

You can monitor the initial load and replication processing of logistics data using the SAP Application Interface

Framework (SAP AIF). In SAP AIF, error messages are displayed if data could not be replicated to the Central

Finance system. You can correct errors in SAP AIF and then restart the processing of the data in the Central

Finance system.

Before using SAP AIF for logistics data, run transaction /AIF/CONTENT_EXTRACT in the Central Finance

system for the scenarios FINCF_AV_SO, FINCF_AV_CI, FINCF_AV_SI, FINCF _AV_PO. Use Monitoring and

Error Handling (transaction

/AIF/ERR), and select Namespace /FINCF and Interface AV_SO, AV_CI, AV_SI and

AV_PO.

To use the SAP AIF Error Handling for Accounting Views, you need to implement the latest SAP AIF content.

Please notice that SAP AIF content is only delivered via support packages, not via notes.

For details on using SAP AIF in error handling, see Error Handling in SAP Application Interface Framework (SAP

AIF) [page 214].

Business Mapping

In the AVL scenario, when you work with the mapping of master data, see details in Conguration in Central

Finance System: Mapping [page 39].

For other kinds of business mapping, you should note that:

● For the mapping of order number AUFNR, you should have dened cost object mapping in your Central

Finance system.

You do this in Customizing of Central Finance (transaction SPRO) under Financial Accounting Central

Finance

Central Finance: Target System Settings Mapping Dene Cost Object Mapping .

● If you are working with central projects, you should map WBS element PS_PSP_PNR.

● For the mapping of protability segment, only characteristics are mapped.

You do this in Customizing of Central Finance (transaction SPRO) under Financial Accounting Central

Finance

Central Finance: Target System Settings Mapping Dene CO-PA Mapping .

Central Finance

P U B L I C 147

1.5.23.3 AVL Scenario: Conguration in SAP SLT

In Central Finance, you use SAP SLT for the initial load and ongoing replication of logistics data from your

source systems to your Central Finance system. To enable this function, you need to make SLT relevant

congurations before using the Accounting View of Logistics Information.

Prerequisites

● You have successfully executed all the steps mentioned for the source and the Central Finance system.

● You must download the latest SLT content of version SAP S/4HANA 1909 FPS1 before you start to

congure SLT.

(This SLT content is available with SAP Note 2154420 .)

Restrictions

The RFC connections to the source systems are maintained with log-on data to the relevant client.

See general restrictions for AVL in Accounting View of Logistics Information (AVL): Overview [page 144].

For detailed information about working with SLT, see Conguration in SAP Landscape Transformation

Replication Server [page 82].

1.5.23.4 Central Accruals Management

Accounting view of logistics information (AVL) replicates operational data from source systems to the Central

Finance system, to support special processes with Central Finance.

Prerequisites

● Your Central Finance system release is SAP S/4HANA 1909 or higher.

● You have executed an initialization program (transaction: FINS_CFIN_INI_POSYS) in the Central Finance

system to process your historical data.

 Note

If you are on release SAP S/4HANA 1909, you need to apply SAP Note 2882950 before executing

the program.

On the basis of the purchase orders replicated by AVL, the Accrual Engine on the Central Finance system

calculates and posts the accruals automatically.

148

P U B L I C

Central Finance

Below you can see the functional architecture for the Purchase Order Accruals Integration with AVL scenario:

After AVL replicates purchase orders, you can perform the following activities:

● Transfer Purchase Orders to Accrual Engine

● Propose Periodic Amounts

● Review Manually Adjusted Periodic Amounts

● Approve Periodic Amounts

● Perform Periodic Posting Runs

Caution

● Purchase orders with account assignment of sales orders are not within the standard scope of Central

Accruals Management scenario.

● Before using deletion report (transaction FINS_CFIN_AVL_DEL), please check whether the balance of

purchase order accrual is zero.

For more details, see Purchase Order Accruals.

1.5.23.5 Central Statutory Reporting

Central Finance and Advanced Compliance Reporting (ACR) provide an end-to-end process of tax reporting by

delivering options to centralize tax reporting. AVL replicates the operational (logistics) data from the source

systems, which, together with the replicated nance data, enables ACR to do centralized tax reporting on the

Central Finance system. Within this integration,

● AVL provides operational data from source systems to the Central Finance system.

● Scope of data provisioning (replication) is use-case-driven, based on tax requirements. A subset of data

from purchase orders, sales orders, supplier and customer invoices is currently covered.

● Initial load, ongoing replication, error handling, key/value mapping, and data provisioning for the tax

reports via CDS views are supported.

Coverage for countries and supported tax reports will be extended following a localization roadmap. As of

today, selected countries and tax reports are already supported. See details in Advanced Compliance

Reporting: Country/Region-Specic Reports in Central Finance [page 220].

Central Finance

P U B L I C 149

1.6 Central Payment

Use

In a Central Finance scenario, Central Payment allows you to make centralized payments and perform

centralized clearing activities in the Central Finance system instead of each source system.

Journal entries are replicated from one or more source system(s) via the System Landscape Transformation

Server (SLT) to the Central Finance system and the resulting customer/supplier open items are automatically

technically cleared in the source system. This enables a centralized open item management in the Central

Finance system.

When Central Payment is activated for a specic company code, open-item processing of all customer and

supplier accounts for this company code is moved entirely to the Central Finance system.

All subsequent processes based on customer/vendor open items then have to take place in the Central Finance

system.

Prerequisites

● Consider the following before activating Central Payment:

○ Dene the company codes for which you want to activate Central Payment.

○ For company codes that are activated for Central Payment, the invoices posted in the source

systems are technically cleared. The invoices are replicated to the Central Finance system and are

paid there.

○ For company codes that are not activated, the invoices posted in the source systems stay open

and are paid in the source systems. The invoices and payments or clearing documents are

replicated to the Central Finance system for reporting purposes. The replicated invoices are ruled

out from the payment or clearing transactions in the Central Finance system. This avoids duplicate

payments (as payments continue to be processed in the source system.)

○ Consider the following for the point in time of activation:

○ Plan the cut-over date for period end (month-end or year-end) after the closing activities.

○ The period of withholding tax accumulation

○ The activation of tax consistency checks before the activation of Central Payment

○ Consider dependent processes regarding historical open items.

○ Process all error messages stuck in SAP Application Interface Framework (SAP AIF).

● If you are using the following functions, you can nd information on steps that you must take or

considerations that you must make before activating Central Payment in the documents listed below:

○ Reversal [page 157]

○ Foreign Currency Revaluation [page 157]

○ Balance Sheet Adjustment [page 158]

○ Individual Value Adjustment [page 158]

○ Flat-rate Value Adjustment [page 159]

○ Provisions for Doubtful Receivables [page 159]

150

P U B L I C

Central Finance

○ Correspondence - Payment Advice Notes [page 159]

○ Correspondence - Account Statements [page 160]

○ Correspondence - Balance Conrmation [page 160]

○ Collection Management [page 160]

○ Dispute Management [page 161]

○ Credit Management [page 161]

○ Handling of Value Added Tax (VAT) [page 162]

○ Handling of Withholding Tax (WHT) [page 163]

○ Cash Journal [page 163]

○ Intercompany Reconciliation Process [page 163]

○ Bank Accounting [page 164]

○ Foreign Trade Reporting (Germany) [page 164]

○ Dunning [page 164]

○ Balance Conrmation [page 165]

○ Item Interest Calculation [page 165]

○ Cash Management [page 166]

○ Year-end Balance Carryforward [page 166]

○ Bank Account Management [page 167]

○ Bill of Exchange [page 167]

Key Features

● The open items are replicated continuously to the Central Finance system and can be paid in the Central

Finance system.

● Central Payment enables standardized payment processes.

● Central Payment enables centralized accounts receivable processes like cash application, credit exposure

calculations, dunning, collections prioritization.

● Using Central Payment leads to reduced costs of bank connections.

● With Central Payment, that is, using the Central Finance (SAP S/4HANA) system to make payments, you

can also benet from these features:

○ Use an SAP standard interface to upload bank statements to a central platform.

○ Monitoring of bank communications and transactions

○ HANA optimization of payment proposal generation

○ Integration of the SAP Cloud Platform (SCP) with the latest SAP apps for accounts receivable

processes

○ Integration of Digital Payments

● Mandate replication between source systems and the Central Finance system is automated so that SEPA

direct debit is supported in the Central Finance system.

 Note

Central Payment for SAP Central Finance is released with functional restrictions, which are described in

SAP Note 2827364 . To activate Central Payment, create an incident on component FI-CF-APR to apply

for pilot note 2346233 . Before making productive use of Central Payment, please make sure that you

Central Finance

P U B L I C 151

fully understand the restrictions and have thoroughly tested Central Payment so that you won't be

impacted by the restrictions.

Steps for Activating Central Payment

1. Activate the Clearing Transfer Scenario in the Central Finance system.

For details on how to do that, please read Activation of Clearing Transfer and Handling of Open Items [page

129].

2. If you use SEPA payment methods, you can nd detailed information on the steps to take here: SEPA

Mandate Replication [page 177].

3. Run the consistency check report with the check group for Central Payment in the Central Finance system

and correct inconsistencies, if necessary. You can do this using the transaction FINS_CFIN_CC.

For details about the consistency check report, see Conguration Consistency Check [page 55].

4. Activate Central Payment in the Central Finance system.

1. Create an incident to activate Central Payment.

2. Switch on the central payment feature in the Central Finance system for a company code. Please note

when you activate Central Payment that the online tax checks are also activated.

For details, see Activation of Central Payment for Company Codes [page 153].

5. Make your conguration settings in the relevant source systems.

For details, see Settings for Central Payment in Source Systems [page 153].

6. Run the report to set historical open items to technically cleared in the source system. You can do this

using the transaction FIN_CFIN_TECH_CLR.

7. If you use down payments with the SD integration run the reports for historical down payments in the

Central Finance system:

1. Update down payments with sales order information by using transaction FINS_CFIN_SO_UPDATE.

2. Update the relationship between historical open down payments and sales orders by using transaction

FINS_CFIN_SDDPLG_UPD.

8. Make your conguration settings for payments in the Central Finance system.

See Also

In addition, you should also read the following information:

● Central Tax Reporting [page 184]

● Activation of Clearing Transfer and Handling of Open Items [page 129]

● Settings for Central Payment in Source Systems [page 153]

● Activation of Central Payment for Company Codes [page 153]

● Handling of Historical Open Items [page 155]

152

P U B L I C

Central Finance

1.6.1 Settings for Central Payment in Source Systems

Carry out the following activities to make congurations for Central Payment in source systems.

Prerequisite

You have applied SAP Note 2346233 .

 Note

This is an SAP Note that can be applied only upon request. Contact SAP by creating an incident on

component FI-CF-APR.

This SAP note also describes the functional restrictions of the product.

Procedure

Carry out the following activities in Customizing for Central Finance (transaction CFINIMG) under Central

Finance

Central Finance: Source System Settings Settings for Central Payment .

1. Dene Logical System for Central Payment System

In this activity, you dene one logical system for the target Central Payment client. A logical system

identies the client of the connected Central Payment systems in the accounting documents.

2. Set up RFC Destination for Central Payment System

In this activity, you dene technical parameters for RFC destinations. These parameters are used for

remote function calls (RFC) to other systems.

RFC connections are necessary for reading data from the connected Central Payment system back to the

source system.

3. Assign RFC Destination for Displaying Objects Central Payment System

In this activity, you assign RFC destination to the logical system for the connected Central Payment

system, in order to display objects from the Central Payment system.

4. Maintain RFC Assignments and Settings for the Central Payment System

In this activity, you maintain the settings for the Central Payment system (leading system) and RFC

assignments. These settings are used for remote function calls (RFC) from the source system into the

Central Payment system.

1.6.2 Activation of Central Payment for Company Codes

This topic includes information about how to activate Central Payment for company codes.

Central Finance

P U B L I C 153

Prerequisites

You have applied SAP Note 2346233 .

 Note

This is an SAP note that can be applied only upon request. Contact SAP by creating an incident on

component FI-CF-APR.

This SAP note also describes the functional restrictions of the product.

Preparation

You have carried out the Customizing settings for Central Finance under Financial Accounting Central

Finance Central Finance: Target System Settings .

Procedure

1. Switch on the Central Payment feature in the Central Finance system.

1. Launch transaction SE38 - ABAP Editor.

2. Enter FINS_CFIN_APAR_CPAY_SWITCH as the program and choose Execute ( F8 ).

2. Maintain the Customizing table for Central Payment in the Central Finance system.

1. Launch transaction CFIN_CPAY_CUST - Central Payment Customizing Table.

2. Choose New Entries ( F5 ).

3. In the Logical System eld, enter the logical name of your source system. In the Source Company Code

eld, enter a company code in the source system that you want to activate with the Central Payment

feature.

4. Repeat the previous step until you have added all the company codes.

5. Press Enter and check whether you have entered any company code by mistake. Delete the wrong

entries.

6.  Caution

After you save your changes, you cannot delete the entries any more.

Save your changes. The data is saved in the Central Finance system. It is also sent to the source

systems and saved in the CFIN_CPCTL table.

3. Manually check the Customizing data in the source systems.

1. Launch transaction SM30 - Call View Maintenance.

2. Enter CFIN_CPCTL in the Table/View eld and choose Display.

3. Compare the table content with the content that you have entered in the Central Finance system in

step 2.

4. Reconcile the Central Finance system and the source systems in the Central Finance system.

154

P U B L I C

Central Finance

1. Launch transaction CFIN_CPAY_CUST - Central Payment Customizing Table.

2. Choose Reconcile at the bottom on the table. The system then displays the comparison result of the

mapping relationship for company codes in the Central Finance system and your source systems, and

the comparison result of the mapping relationship in the Central Finance system and in Master Data

Governance.

3. Select the entries marked in red, which indicates inconsistency, and choose Sync to synchronize the

data.

1.6.3 Handling of Historical Open Items

Historical open items are open items which were created in the source system before Central Payment

activation and were replicated to the Central Finance system without being set to cleared in the source system.

Therefore, these items are open in the source system and in the Central Finance system.

To avoid double payment of these historical open items, you can have them cleared and paid in the Central

Finance system only, see details in Historical Open Items – Ensuring Payment and Clearing Takes Place in

Central Finance System [page 155]

 Note

If you're using the solution Historical Open Items – Ensuring Payment and Clearing Takes Place in the Source

System and want to switch to the solution Historical Open Items – Ensuring Payment and Clearing Takes

Place in Central Finance System, you need to:

● Perform all activities outlined in the solution Historical Open Items – Ensuring Payment and Clearing

Takes Place in Central Finance System successfully.

● Remove the payment block indicator from historical items in the Central Finance system using report

FINS_CFIN_APAR_HIST_OI_PRC.

● Remove the payment block reason in Customizing for Central Finance (transaction: CFINIMG) under

Central Finance: Target System Settings Central Payment Activate Central Payment for Company

Codes .

1.6.3.1 Historical Open Items – Ensuring Payment and

Clearing Takes Place in Central Finance System

With this solution, the historical open items are technically cleared in the source system and only open for

payment in the Central Finance systems.

In the scope of Central Payment, the historical open items refer to these open items which are on Accounts

Receivable (AR), Accounts Payable (AP), cash discount clearing accounts, deferred tax accounts, and bank

clearing accounts.

Central Finance

P U B L I C 155

Prerequisites

● You have applied SAP Note 2346233 to activate Central Payment.

● You have applied SAP Note 2727394 to apply this solution in the source system.

● You have applied SAP Note 2727396 to apply this solution in the Central Finance system.

Procedure

To set historical open items as technically cleared in the source system, you need to:

● Maintain the conguration of Dene Bank Clearing Accounts for Technical Clearing in the Customizing for

Central Finance (transaction: CFINIMG) under Central Finance: Source System Settings Settings for

Central Payment Handling of Historical Open Items in the source system.

● Execute the report Set Historical Open Items as Technically Cleared in the Customizing for Central Finance

(transaction:

CFINIMG) under Central Finance: Source System Settings Settings for Central Payment

Handling of Historical Open Items in the source system.

If you’re using Central Down Payment Integration with SD, take the following actions before setting historical

open items as technically cleared:

● Execute the report Update Down Payments with Sales Order Information in the Customizing for Central

Finance (transaction: CFINIMG) under Central Finance: Target System Settings Central Payment

Handling of Historical Open Items in the Central Finance system.

● Execute the report Update Relationship between Down Payments and Sales Orders in the Customizing for

Central Finance (transaction: CFINIMG) under Central Finance: Target System Settings Central

Payment Handling of Historical Open Items in the Central Finance system.

1.6.4 Guidance for Dependent Processes

After Central Payment has been activated, dependent processes relating to open items need to be performed

in the Central Finance system rather than source systems. You can run some of these dependent processes in

the Central Finance system in the same way as in a source system, while for others, you need to make some

manual corrections/adjustments.

Prerequisite

You have applied SAP Note 2346233 to activate Central Payment.

156

P U B L I C

Central Finance

1.6.4.1 Reversal

Source System:

● After Central Payment is activated, all documents that were posted in the source system before activation

of Central Payment still need to be reversed in the source system. The reversal document is then replicated

to the Central Finance system.

● If an item posted in the source system has been cleared/paid in the Central Finance system, the user

needs to manually reset the clearing in the Central Finance system before performing the reversal in the

source system.

Central Finance System:

All documents that are posted in the Central Finance system after activation of Central Payment need to be

reversed in the Central Finance system.

1.6.4.2 Foreign Currency Revaluation

After Central Payment activation, you need to perform foreign currency revaluation in the Central Finance

system.

If you are not using delta revaluation (valuation for balance sheet preparation), you can run the foreign

currency valuation in the Central Finance system as usual.

If you are using delta revaluation, the following steps need to be performed to ensure a proper valuation in the

Central Finance system for historical open items after Central Payment activation, no matter whether the

source system is using Classic General Ledger Accounting (Classic G/L) or New General Ledger Accounting

(New G/L):

● Ensure that all the documents to be valuated have been replicated to the Central Finance system (via initial

load or ongoing replication). This should be taken into account during the implementation of Central

Finance.

● Reset foreign currency valuations for all historical open items under this company code in the source

system before you activate Central Payment.

To do this, go to the SAP Easy Access screen in the source system and choose Accounting Financial

Accounting General Ledger Periodic Processing Closing Valuate Foreign Currency Valuation ,

and run report F.05 - Foreign Currency Valuation (for Classic G/L) or report FAGL_FCV - Foreign Currency

Valuation (New) (for New G/L).

 Note

Foreign currency valuation in the New G/L does not consider the results of the Valuation for Balance

Sheet Preparation function available with the Classic G/L. If the valuations are not reset, you may get

incorrect foreign currency values after the data replication.

● Redo foreign currency valuations for historical open items in the corresponding company code in the

Central Finance system. 

To do this, go to the SAP Easy Access screen in the source system and choose Accounting Financial

Accounting General Ledger Periodic Processing Closing Valuate Foreign Currency Valuation ,

and run the report FAGL_FC_VAL - Foreign Currency Valuation (New).

Central Finance

P U B L I C 157

Remark:

In case of Delta Revaluation = Valuation for Balance Sheet Preparation (no reversal on the 1st day of the next

month) and usage of the Strict Lowest Value revaluation method, the valuation results could be dierent

depending on the exchange rate history, because the Central Finance system does not consider historical

valuation runs which might have used a lower exchange rate.

1.6.4.3 Balance Sheet Adjustment

Before Central Payment is activated, you might run balance sheet adjustment in the following scenarios:

● Balance sheet adjustment for business area

○ Run in the source system only. The adjustment postings will then be replicated to the Central Finance

system.

○ Run in the Central Finance system only.

● Balance sheet adjustment for prot center

○ Run in the source system as well as the Central Finance system. (The adjustment posting in the source

system will not be replicated to the Central Finance system.)

○ Run in the Central Finance system only.

○ Additional scenarios

For example, prot center adjustment only in the source system. Refer to a migration project to get the

right prot center values for the Central Finance system.

After Central Payment is activated, for all the scenarios above, the balance sheet adjustment for business

area and prot center must be processed in the Central Finance system only.

To ensure that the balance sheet adjustment can run successfully after Central Payment is activated, you need

to:

● Deactivate the used balance sheet adjustments in the source system.

● Activate the corresponding balance sheet adjustment in the Central Finance system.

1.6.4.4 Individual Value Adjustment

The following items should be taken into consideration to ensure Individual Value Adjustment runs successfully

after Central Payment is activated:

● After Central Payment is activated, ensure that individual value adjustment (transaction F-21) is only

carried out in the Central Finance system.

● After Central Payment is activated, the reverse process (transaction FB08) of individual value adjustments

that were posted in the source system before Central Payment activation, is carried out in the source

system. The reversal document is replicated to the Central Finance system.

158

P U B L I C

Central Finance

1.6.4.5 Flat-rate Value Adjustment

After Central Payment has been activated, the process for Flat-rate Value Adjustment varies as below:

● If the valuation is generated in the source system, you can only check the information about the valuation

on the single open item in the source system. This information is not transferred to the Central Finance

system.

● If the valuation is generated in the Central Finance system, you can only check the valuation information on

the single open items in the Central Finance system.

1.6.4.6 Provisions for Doubtful Receivables

The following steps need to be performed to ensure the correct provision process for doubtful receivables for

historical open items in the Central Finance system after Central Payment activation, no matter whether the

source system is using Classic G/L or New G/L:

● Ensure that all the provision documents of the source system have been replicated to the Central Finance

system (through initial load or ongoing replication). This should be considered during Central Finance

implementation.

● Ensure that all the provision documents have been reversed for the cleared invoices in the source system

before Central Payment is activated.

● Reverse the provision documents for all historical open items in the source system before Central Payment

is activated.

Remark: To reverse the provision documents, you can make an oset posting manually via FB01 to the

provision account to make the balance zero. You should do the reversal before running the report

FIN_CFIN_APAR_SET_TECH_CLR to set historical open items as technically cleared in the source system.

● Redo the provision for the historical open items in Central Finance system before Central Payment

activation.

Remark: To redo the provision in the Central Finance system, you should keep the Key Date and Open Items

at Key Date the same as in the last run in the source system.

1.6.4.7 Correspondence - Payment Advice Notes

The following items should be taken into consideration to ensure that the Payment Advice Note process runs

successfully after Central Payment activation:

● After Central Payment is activated, payment advice notes for incoming payments have to be created in the

Central Finance system.

Shortly before you activate Central Payment, we recommend that you create payment advice notes in the

Central Finance system to ensure that they can be processed when payments arrive in the Central Finance

system.

● After Central Payment is activated, payment advice notes along with outgoing payments will be generated

in the Central Finance system.

Central Finance

P U B L I C 159

1.6.4.8 Correspondence - Account Statements

The following items should be taken into consideration to ensure that the account statement process runs

successfully after Central Payment is activated:

● Ensure that all FI documents for the customer or supplier can be replicated to the Central Finance system.

● The eld Bank Statement should have been maintained in the business partner master data for the

customer or supplier in the Central Finance system.

● The account statement process should run in the Central Finance system after the activation of Central

Payment.

1.6.4.9 Correspondence - Balance Conrmation

After Central Payment is activated, balance conrmation must be executed in the Central Finance system.

Please note that because only Down Payment Requests and Payment Requests are replicated, other noted

items are not included in the Balance Conrmation.

1.6.4.10 Collection Management

After Central Payment is activated, Collection Management needs to be handled dierently depending on the

scenario:

● If Collection Management was used in a stand-alone Collection Management system before Central

Payment was activated:

○ If Collection Management and Central Finance were running on the same system

After Central Payment has been activated, Collection Management is still performed in the Collection

Management (Central Finance) system. There is no need to connect other systems to the Collection

Management system.

○ If Collection Management and Central Finance were running on dierent systems

After Central Payment has been activated, you need to connect the Central Finance system to the

Collection Management system and disconnect the source systems, and do Collection Management

there.

● If Collection Management was used in one or more source system(s) before Central Payment was

activated:

○ After Central Payment is activated, you need to congure and process Collection Management in the

Central Finance system.

○ For the historical collection process in the source systems, you can leave historical collection objects

such as promises to pay, dispute cases, dunning history, notes, resubmissions, customer contacts, in

the source systems. If you need them for further processing in the Central Finance system, consider

starting a migration project to transfer the historical data to the Central Finance system and proceed

the Collection process.

● As Central Payment can be activated on a company code basis, the prerequisite for running Collections

Management in Central Finance is that one collection segment is assigned to one company code. This

160

P U B L I C

Central Finance

ensures that for those company codes which are not enabled for Central Payment the collection process

can still run in the source system.

For all scenarios above, you should be aware of following changes to the two functions for the SD billing

document in the Collection Worklist:

● If RFC connection to the source system has been enabled, you can navigate to the Billing Document in the

source system by double-clicking the Billing Doc Number or clicking the button Billing Document.

● The function Output Billing Document Again will be unavailable if the billing document is located in the

source system. You need to trigger the printing of the billing document in the corresponding source

system.

Caution

● Print out billing documents from worklist is not possible in the Central Finance system.

● The dunning history is not available from previous dunning runs in source systems.

1.6.4.11 Dispute Management

Before Central Payment is activated, Dispute Management can be run in either the source system or in the

Central Finance system (if clearing transfer is activated).

If Central Payment is activated, Dispute Management has to be implemented in the Central Finance system.

To ensure that the billing document in the source system can be linked to the dispute case in the Central

Finance system, add the following entry in the Customizing activity under Financial Supply Chain

Management

Dispute Management Dispute Case Processing Process Integration Dene Derivation of

Element Types .

Object Type

Logical System Element Type ID

VBRK Logical system of source system UDM_SPS_VBRK

If Dispute Management was run in the source system before Central Payment was activated, dispute cases

which are still open or in process in the source system might still exist after Central Payment has been

activated. If these dispute cases need further processing, they need to be migrated to the Central Finance

system in a customer-specic migration project.

1.6.4.12 Credit Management

Before Central Payment is activated, if the SAP Credit Management (FSCM) system is implemented together

with the Central Finance system:

● The Central Finance scenario replicates the FI documents from a source system to the Central Finance

system while credit exposure (open invoice) of FSCM is also updated on the FSCM system, which will cause

duplicate open invoices. To avoid the duplicate issue, we suggest ltering out the company code which has

activated Central Finance using BADI UKM_FILL~ FILL_FIELDS. See SAP Note 2839326 and

2833145 for details.

Central Finance

P U B L I C 161

● Be kindly informed that once the Central Finance system goes live, you need to rebuild the credit exposure

with type 200 Open Invoices (by default is 200) to clean up inconsistencies in credit exposure values. Run

transaction UKM_COMMITMENTS to delete incorrect credit exposure values and use report

UKM_TRANSFER_ITEMS to reconstruct the credit exposure values. See SAP Note 2576445 and 1124271

for details.

After Central Payment is activated, if the FSCM system is implemented together with the Central Finance

system:

● In the Central Payment scenario of Central Finance, the FI document in the source system is set to ALE-

extern. Then, the replicated FI document will not update the credit exposure with type 200 Open Invoice.

● We recommend you to run report FIN_CFIN_APAR_SET_TECH_CLR (transaction FIN_CFIN_TECH_CLR)

to set ALE-extern for the historical open items of FI documents. For FSCM function, if BADI

UKM_FILL~FILL_FIELDS was enhanced to lter out the company codes in the Central Finance scenario,

the BADI should be switched o/back or enhanced not to lter out company codes.

If the FSCM system is not implemented together with the Central Finance system (standalone or with source

system), please follow the SAP Credit Management conguration guidance to set up your system.

Please be informed that after activation of Central Payment, the payment history from source systems (such

as table KNB4) and dunning history from source systems (such as table KNB5) could be missing in the Central

Finance system. For the payment history, it depends on whether the indicator Record Payment History was set

on the business partner master data before Central Payment is activated. For the dunning history on master

data, it depends on when and how master data is replicated to Central Finance. If you need this data for

processes in Credit Management, please take this into consideration during your project and use a custom

solution if it is necessary to transfer the data.

1.6.4.13 Handling of Value Added Tax (VAT)

Before Central Payment is activated, the report for Advance Return for Tax on Sales/Purchases and payment

to the tax authority must be processed in the source system.

After Central Payment is activated, the process depends on whether the company is in a country where it is

legally required that short payments generate tax adjustment:

● If you are in a country where short payments to suppliers/from customers (such as cash discount) do not

generate tax adjustment, the report for Advance Return for Tax on Sales/Purchases can be run either in

the source system or the Central Finance system. While the payment to tax authority must be executed in

the Central Finance system.

● If you are in a country where short payments to suppliers/from customers (such as cash discount)

generate tax adjustment, both the report for Advance Return for Tax on Sales/Purchases and the payment

to tax authority must be executed in Central Finance system.

For historical open items on tax payable account, the payment to the tax authority must be processed in the

Central Finance system.

See Also

VAT Recalculation Check [page 187]

162

P U B L I C

Central Finance

1.6.4.14 Handling of Withholding Tax (WHT)

If you have activated Central Payment for a certain company code, you post journal entries with tax impact in

the Central Finance system that are not available in the source system. That is why you must also carry out tax

reporting in the Central Finance system.

Once Central Payment is active, withholding tax works without restrictions for countries where withholding tax

is posted at the time of invoice as well as for countries where withholding tax is posted at the time of payment.

This does not apply to accumulated WHT. Accumulation data is available in the Central Finance system only for

WHT at time of payment, not at point of invoice.

If you use accumulated WHT, you must make sure that you activate Central Payment before the next

accumulation period starts, whether this is a month, a calendar year, or a 12-month period starting on a

specic month. That way all information for calculating accumulated WHT is available in the Central Finance

system.

See Also

Withholding Tax [page 191]

1.6.4.15 Cash Journal

The following steps for cash journal closing need to be executed in the source system in order to transfer the

cash journal from a source system to the Central Finance system before Central Payment is activated:

● All documents in the cash journal need to have status posted, reversed or deleted. There must not be any

remaining documents with status saved (indicated as yellow trac lights).

● All checks must be submitted and the check lots must be posted.

● Balances in cash journal and G/L accounts must be equal (if you use several cash journals which post to

the same G/L account, you can use analysis report RFCJ14 to get an overview of the closing balance of the

cash journals; see details in SAP Note 2515460 .)

● The cash journal must be set to zero by a closing entry. This means that the remaining cash needs to be

removed from the cash journal in the source system and be paid into the new cash journal in the Central

Finance system.

● When all of the above listed conditions have been met, the cash journal in the source system can be closed

using FBCJC0. After that, no new entries can be added to the cash journal.

1.6.4.16 Intercompany Reconciliation Process

The following items should be taken into consideration to ensure that the Intercompany Reconciliation process

runs successfully after Central Payment is activated:

● Ensure that all the documents to be reconciled have been replicated to the Central Finance system

(through initial load or ongoing replication). This should be considered during Central Finance

implementation.

Central Finance

P U B L I C 163

● Run the Intercompany Reconciliation Process in the Central Finance system after Central Payment is

activated.

● All company codes involved in Intercompany Reconciliation must be activated for Central Payment.

1.6.4.17 Bank Accounting

All bank statements must be posted in the source system before activation of Central Payment (no pending

batch input sessions).

After activating Central Payment for specic company codes all your payments for these company codes will

be generated in the Central Finance system including your bank statements.

The historical bank statements are not available in the Central Finance system and can only be accessed in the

source systems.

1.6.4.18 Foreign Trade Reporting (Germany)

In Germany, companies have to report payables to and receivables from foreign customers/suppliers to the

German Central Bank. After Central Payment is activated, the Foreign Trade Report must be processed in the

Central Finance system.

The following reports are available:

● Report RFAWVZ5A - Foreign Trade Regulations Report Z5a and report RFAWVZ5P - Foreign Trade Regulations

Report Z5A, Page 2: Downloading Reporting Data to download the le.

To run the reports, start transaction SA38 and enter RFAWVZ5A or RFAWVZ5P as the program name.

● Report RFAWVZ40N - Z4 Reports for Foreign Trade Regulations on Basis of Receivables/Payables

The reports take into account the items of documents posted with the Central Bank Indicator, which will be

replicated from the source system to the Central Finance system. Please follow the rules of the State Central

Bank (SCB) and German Foreign Trade Regulations (AWV) to congure the indicator values. To use these

reports, please make sure the conguration of indicators is consistent between the source system and the

Central Finance system.

1.6.4.19 Dunning

Once Central Payment is activated, the dunning process must be run in the Central Finance system.

The dunning data of historical open items might contain incorrect values in the Central Finance system if

dierent dunning procedures are used in the source systems and the Central Finance system. Dunning level

and dunning key must be veried on item level and must be corrected manually if necessary. Dunning area and

dunning block are mapped, on the item level, from the source system to the Central Finance system. Manual

correction of dunning area and dunning block in historical open items is only necessary if you have changed

conguration of dunning area or dunning block since activating Central Payment.

164

P U B L I C

Central Finance

The eld Last Dunning Date in the customer master record controls the dunning frequency. After activation of

Central Payment, if this eld is empty, the next dunning level may be reached too early. This issue can be

prevented by organizational measures, by executing the dunning run in the usual interval (for example, if the

last run in the source system is on the 1st of January, the next run in the Central Finance system can be on 15th

of January).

The eld Highest Dunning Level will be set in the customer master record for the accountant's information.

After activation of Central payment, if this eld is empty in the Central Finance system and the accountant

needs to know about it, he/she needs to check in the source system. The eld will be lled again with the rst

dunning run in the Central Finance system.

1.6.4.20 Balance Conrmation

After Central Payment is activated, balance conrmation must be executed in the Central Finance system.

Note that only down payment requests and payment requests are replicated, so other noted items are not

included in the balance conrmation.

1.6.4.21 Item Interest Calculation

The following items should be taken into consideration to ensure that item interest calculation runs

successfully after Central Payment activation:

● Before Central Payment activation, item interest calculation is processed in the source system.

● After Central Payment has been activated, item interest calculation has to be performed in the Central

Finance system. To guarantee that the item interest calculation in the Central Finance system is based on

the correct values, the following steps must be performed:

○ Before you run the item interest calculation report, launch Prepare Item Interest Calculation in

Customizing of Finance (transaction

SPRO) under Financial Accounting Accounts Receivable and

Accounts Payable Business Transactions Interest Calculation Interest Calculation Global

Settings and deselect the indicator Post Interest.

○ Run the item interest calculation report (transaction FINTAP) to the same date you run it in the source

system.

○ Go back to the Customizing of Finance under Financial Accounting Accounts Receivable and

Accounts Payable Business Transactions Interest Calculation Interest Calculation Global Settings

Prepare Item Interest Calculation and select the indicator Post Interest.

Now the system is prepared to process the item interest calculation correctly in the Central Finance system.

See SAP Note 2184320 for details.

Central Finance

P U B L I C 165

1.6.4.22 Cash Management

After Central Finance implementation, Cash Management can be run in either a source system or the Central

Finance system.

If you run Cash Management in the Central Finance system, please consider the following:

● Clearing transfer must be activated for the source system.

● To transfer classic cash management data (such as purchase orders, sales orders) from the source system

to the Central Finance system, use standard IDoc message type CMSEND, CMREQU).

● There is a risk of double cash management items for FI postings (one item transferred via IDoc; one item

generated during FI document replication) in One Exposure (table FQM_FLOW) in the Central Finance

system. To avoid double postings in One Exposure, use the lters in the Intermediate Document (IDoc)

distribution model.

● For more information, see Cash and Liquity Management.

After Central Payment is activated, Cash Management must run in the Central Finance system as the payment

postings are only available in the Central Finance system. If you are using Payment History or Check

Cashing Time to calculate planning date, you need to be aware of the following:

● Payment History: If the indicator payment history record is set in customer master data of the source

system, payment history (table KNB4) will be considered when planning date is calculated for customers

(see SAP Note 24883 ). After Central Payment is activated, the payment history will only be updated in

the Central Finance system. As a result, the planning date can no longer be correctly calculated in the

source system.

● Check Cashing Time: It will be considered when planning date is calculated for vendors if the payment

method is a check payment method. Check cashing time can be maintained manually in vendor master

data or using report RFSRUE10 (see SAP Note 24883 ). However, in the scenario of Central Payment,

RFSRUE10 can only be run in the Central Finance system. As a result, the calculation of planning date is not

correct any more in the source system.

For the re-determination of planning date, the following is recommended:

● The planning date will be re-determined when FI documents are reposted in the Central Finance system,

only if the planning date is empty. To clear the planning date replicated from the source system before the

document creation, you can implement Central Finance BAdI BADI_FINS_CFIN_AC_INTERFACE. The

replicated FI documents will be created with re-determined planning date in the Central Finance system.

● Note that to ensure the payment history data can be fetched correctly in the process of planning date re-

determination, you are recommended to maintain the same payment history record for customer master

data in the source system and in the Central Finance system already at the preliminary phase Central

Finance implementation. Regarding the inuence of payment history, refer to SAP Note 24883 for

details.

1.6.4.23 Year-end Balance Carryforward

The following items should be taken into consideration to ensure the balance carryforward process runs

successfully after Central Payment activation:

166

P U B L I C

Central Finance

● After activating Central Payment, you need to run the balance carryforward process in the Central Finance

system.

● You also need to run the balance carryforward process in the source system (no matter whether this is an

ECC version or an SAP S/4HANA version), but the results in the source system and the Central Finance

system will not necessarily match.

1.6.4.24 Bank Account Management

After Central Finance implementation:

● House bank and house bank account should be the same in the source and the Central Finance systems if

they need to be assigned in the invoices.

● If you want to use dierent house banks and house bank accounts in the source and the Central Finance

systems, you need to dene your own corresponding mapping entities and maintain mapping entries.

After Central Payment activation:

● Bank Relationship Management and house bank-related conguration must be implemented in the Central

Finance system.

If bank account master data which is managed in the Central Finance system needs to be used in the

source system (assign house bank/house bank account in the document in the source system), you can

use the Execute Data Replication program (transaction DRFOUT) to replicate house banks, house

bank accounts, and bank accounts from the Central Finance system to the source systems. For more

details, see Replicate House Banks, House Bank Accounts, and Bank Accounts.

1.6.4.25 Bill of Exchange

Before Central Payment is activated, Bill of Exchange (BoE) processes run in the source system and relevant

documents are replicated to the Central Finance system.

After Central Payment has been activated, Bill of Exchange processes must be run in the Central Finance

system. To ensure that payment processes via BoE can run successfully in Central Finance, you need to apply

SAP Note 2288901 to map special G/L transactions of type "W" in the Central Finance system.

If payment processes via BoE have been executed in the source system before Central Payment activation,

open items from historical transactions may still exist in the Central Finance system after Central Payment

activation.

● For the standard BoE payment (transaction F-36/F110), the historical open items can be processed

without disruption in the Central Finance system.

● Other BoE processes such as the following can no longer be performed in the Central Finance system, after

implementation of SAP Note 2288901 :

○ BoE presentation (transaction FBWE)

○ BoE collection (transaction F-34)

○ Discounting (transaction F-33)

○ Forfaiting (transaction F-35)

Central Finance

P U B L I C 167

○ Reversal of liability(transaction F-20)

If you want to run these transactions in the Central Finance system, you must reverse the BoE processes in the

source system and then repost the documents directly in the Central Finance system.

1.6.5 Cross-System Process Control for Central Payment

With the activation of Central Payment, business processes are distributed across systems. Replicated invoices

are technically cleared in the source system and paid in the Central Finance system. This can lead to the

following challenges:

● The actual clearing status of an invoice is not available in the source system. It is only available in the

Central Finance system.

● Business processes that depend on the actual clearing status of invoices in the source system may be

impacted.

● The mechanisms that are used to lock and validate the clearing status in a standalone system cannot be

used in a cross-system scenario.

A new framework has been introduced to allow the smooth and consistent ow of business processes which

involve changes to documents and which are distributed across dierent systems where documents are

replicated between the systems. The new framework is called Cross-System Process Control (CSPC).

Within the Central Payment scenario, you can use the cross-system process control to implement the following

controls:

● For SD invoices, FI invoices and down payment requests, the system prevents that a reversal is posted

accidentally in the source system in the following cases:

○ The document has already been cleared in the Central Finance system.

○ The customer/vendor account is locked in the Central Finance system.

○ The corresponding replicated document is locked in the Central Finance system.

● Besides individual document reversal (FB08), the controls above are also available for cross-company

code reversal (FBU8).

 Note

The accidental reversal in the source system cannot be prevented when the corresponding replicated

document is locked by payment proposal or payment run in the Central Finance system.

168

P U B L I C

Central Finance

1.6.5.1 Activation of Cross-System Process Control for

Central Payment

To activate Cross-System Process Control (CSPC) for Central Payment, you need to carry out some

Customizing activities in both source and Central Finance systems.

Prerequisites

You have applied SAP Note 2346233 to activate Central Payment.

You have applied SAP Note 2815665 to apply this solution in the source system.

You have applied SAP Note 2819756 to apply this solution in the Central Finance system.

You have carried out Customizing activities in Settings for Central Payment in Source Systems [page 153].

System Release Requirement

Your source system release should be ECC 6.0 or higher.

Your Central Finance system release should be SAP S/4HANA 1709 FPS0 or higher.

Procedure

Carry out the following activities in the source system in Customizing for Central Finance (transaction

CFINIMG) under Central Finance Central Finance: Source System Settings Cross-System Process Control

(Source System) .

● Set up RFC Connections for Cross-System Process Control

In this activity, you dene technical parameters for RFC destinations. These parameters are used for

remote function calls (RFC) to other systems. You must dene these parameters for all systems for which

you want to use the CSPC scenario.

● Congure Remote Systems for Cross-System Process Control

In this activity, you dene the logical system (Central Finance system) and its RFC Destination for your

CSPC scenario, and activate the Process Type CPAY for the system.

 Note

The settings for the logical system and RFC destination should be the same as what you have dened

in Maintain RFC Assignments and Settings for the Central Payment. For more information, see Settings

for Central Payment in Source Systems [page 153].

Central Finance

P U B L I C 169

Carry out the following activities in the Central Finance system in Customizing for Central Finance

(transaction CFINIMG) under Central Finance Central Finance: Target System Settings Cross-System

Process Control (Target System) .

● Set up RFC Connections for Cross-System Process Control

In this activity, you dene technical parameters for RFC destinations. These parameters are used for

remote function calls (RFC) to other systems. You must dene these parameters for all systems for which

you want to use the CSPC scenario.

● Congure Remote Systems for Cross-System Process Control

In this activity, you dene the logical system (source system) and its RFC Destination for your CSPC

scenario, and activate the Process Type CPAY for the system.

 Note

The logical system you dene here should be the same as what you have maintained in the Central

Payment Customizing table. For more information, see Activation of Central Payment for Company

Codes [page 153].

1.6.5.2 Initialization of Cross-System Process Control for

Central Payment

After Cross-System Process Control (CSPC) has been activated for Central Payment, historical open items on

Accounts Payable (AP) and Accounts Receivable (AR) in the source system may still exist, which CSPC could

not process eectively. To ensure the smooth and consistent ow of business processes, you should run the

CSPC initialization program in the Central Finance system to cover all the historical open AP/AR items.

You need to execute this program for

● Company codes which have already been activated for Central Payment before CSPC activation, for which

historical open AP/AR items were created in the source system before CSPC activation.

● New company codes which have been activated for Central Payment after CSPC activation, for which

historical open AP/AR items were created in the source system before Central Payment activation.

 Note

Once you have activated CSPC, you should run the initialization report before you execute automatic

payment program and/or any payment transactions in the Central Finance system.

Prerequisites

● You have activated specic company codes for Central Payment.

● You have activated process type Central Payment (CPAY) in CSPC.

● The SLT replication is up and running.

170

P U B L I C

Central Finance

System Release Requirement

● Your source system release must be ECC 6.0 or higher.

● Your Central Finance system release must be SAP S/4HANA 1709 FPS0 or higher.

Procedure

1. Launch the activity Initialization of Cross-System Process Control in the Central Finance system. (IMG path:

in transaction CFINIMG, under Central Finance: Target System Settings Central Payment Cross-

System Process Control for Central Payment

)

2. Specify how many background jobs you want to use for the parallel processing of CSPC initialization.

3. Execute the program.

4. Go to the activity Initialization Status Monitor and check the processing results by package. (IMG path: in

transaction CFINIMG, under Central Finance: Target System Settings Central Payment Cross-System

Process Control for Central Payment )

 Note

If any error occurs after your rst run, we recommend that you x the errors rst and then execute the

CSPC initialization program again, in which case only the packages which contain errors will be triggered.

Related Information

Activation of Cross-System Process Control for Central Payment [page 169]

1.6.6 Down Payment Integration with SD

The integration of SD-related down payments into Central Finance allows you to do the following in your

Central Finance system, instead of in your source systems:

● Post down payments with reference to a down payment request replicated from a source system (request-

based)

● Post down payments with reference to a sales order from a source system (condition-based)

● Carry out clearing activities for down payments and invoices

Prerequisite

● You have activated Central Payment for the relevant company codes.

Central Finance

P U B L I C 171

● You have carried out Customizing activities in Settings for Central Payment in Source Systems [page 153].

● Your Central Finance system should be SAP S/4HANA OP 1809 or higher.

Features

Available options for creating down payments:

1. Condition-based down payments

○ Cash Receipts in Cash Journal

○ Post Customer Down Payments

○ Post Incoming Payments

○ Post General Document Entry

○ Bank Statements (including Manual/Electronic Bank Statement and Reprocess)

○ Incoming Check

○ Lockbox

○ Bill of Exchange

The down payments must be posted with reference to the sales order in the source system. This is only

possible if you select the sales order using the search help Sales Documents per Logistics Source System.

The following graphic shows the process and data ow between the source system and the Central Finance

system for the condition-based down payment integration with Sales and Distribution (SD).

A sales order is created in SD in the source system using conditions for down payment. The down payment

is received in the Central Finance system referring to the sales order of the source system. Relevant down

payment data is retrieved in the billing run from the Central Finance system:

2. Request-based down payments can be posted by the following transactions:

○ Bank Statements (including Manual/Electronic Bank Statement and Reprocess)

172

P U B L I C

Central Finance

○ Post General Document Entry

○ Post Customer Down Payments

○ Payment Run

○ Lockbox

○ Incoming Check

○ Bill of Exchange

The down payment requests are created in the source system in Financials or via milestone billing in SD.

The following graphic shows the process and data ow between the source system and the Central Finance

system for the request-based down payment integration with Sales and Distribution (SD).

A down payment request is created in SD in the source system and paid in the Central Finance system.

Relevant down payment data is retrieved in the billing run from the Central Finance system.

Document Navigation

During nal billing (VF01), a customer invoice is created in the source system which includes clearing of the

down payment line item. The line item eld invoice reference in the FI document in the source system is

lled in with the down payment document number retrieved from the Central Finance system. When you click

this eld, you can see the details for this down payment document in the Central Finance system.

SD Billing

During SD Billing, the system retrieves the down payment information from the Central Finance system using

the existing mapping to determine the values that apply in the source system. The values of the following elds

are retrieved:

● Company code

● Customer number

● G/L account

● Special G/L indicator

● Assignment

Central Finance

P U B L I C 173

● Tax code

● Business area

● Prot center

If you have mapped these elds with an N:1 relationship, the mapping will not be able to retrieve a unique value

that applies in the source system. You can use the report FINS_CFIN_APAR_MAPPING_REL or directly call

transaction FINS_CFIN_MAP_REL to check the mapping relationship. To correct the mapping relationship, see

Conguration in Central Finance System: Mapping [page 39].

 Note

● The down payments must be posted with reference to the sales order in the source system. For Value

Mapping, you can dene a default value that is applied when an N:1 mapping relationship exists. For key

mapping, the value of index one is selected as the default value.

● Two BAdIs (source system: BADI_FIN_CFIN_DP_MAP; Central Finance: BADI_FINS_CFIN_DP_MAP)

are provided to do the mapping from the Central Finance system to the source system.

Down Payment Item Clearing

Down payment item(s) will be cleared via clear customer account (F-32) after manual payment (F-28) or via

nal payment during automatic payment run (F110).

The line item eld Sales Document in the FI document in the Central Finance system is lled in with the sales

order from the source system, which is reference to the down payment.

Supported Fiori Apps

In the Central payment scenario, payment activities only happen in the Central Finance system. As the Central

Finance system is an SAP S/4HANA system, you can run the transactions either in the SAP GUI or in Fiori UI.

Fiori Apps support:

● Request-based SD down payments

● Transactions in the Central Finance system

● Transactions in a source system if the source system is an SAP S/4HANA system

Supported Fiori apps include:

Fiori App Transactions in GUI

Manage Customers Down Payment Requests F-29: Post customer down payment

Post Incoming Payments F-28: Post down payment/Post incoming payment

Clear Incoming Payments F-39: Clear customer down payment

F-32: Clear customer

Manage Automatic Payments

F110: Parameters for Automatic Payment

Manage Bank Statement FF67: Manual Account Statement

Reprocess Bank Statement Items FEBA_BANK_STATEMENT: Postprocessing Bank Statement

174 P U B L I C

Central Finance

Fiori App Transactions in GUI

Manage Check Deposits FF68: Manual Check Deposit Transaction

Reprocess Incoming Checks FEBA_CHECK_DEPOSIT: Postprocessing Check Deposit

Trans.

Manage Incoming Payment Files FLB2: Import Lockbox File

Upload Lockbox Files FLB2: Import Lockbox File

Manage Lockbox Batches FLB1: Postprocessing Lockbox Data

Reset Cleared Items FBRA: Reset cleared items

Manage Journal Entries FB08: Reverse document

Down Payment Integration with SD is released with functional restrictions, which are described in SAP Note

2474760 .

1.6.7 Down Payment Integration with MM

The integration of MM-related down payments into Central Finance allows you to do the following in your

Central Finance system, instead of in your source systems:

● Post down payments with reference to a down payment request replicated from a source system (request-

based).

● Carry out clearing activities for down payments and invoices separately.

Prerequisites

● You have activated Central Payment for specic company codes.

● You have carried out Customizing activities in Settings for Central Payment in Source Systems [page 153].

● Your Central Finance system should be SAP S/4HANA OP 1809 or higher.

Features

Available options for creating Request-based down payments:

● Post Vendor Down Payments

● Payment Run

● Post General Document Entry

Central Finance

P U B L I C 175

● Bank Statements (including Manual/Electronic Bank Statement and Reprocess)

● Outgoing Check

● Bill of Exchange

The down payment requests are created in the source system in MM or in FI process and they are replicated to

the Central Finance system.

Company codes that activate Down Payment Integration with MM can only be posted in the Central Finance

system with reference to a down payment request which is replicated from the source system. The

corresponding Purchase Order History in the source system will be updated after down payment has been

processed in the Central Finance system.

The following graphic shows the process and data ow between the source system and the Central Finance

system for the request-based down payment integration with Materials Management (MM).

A down payment request is created in MM in the source system and paid in the Central Finance system. Down

payment clearing as well as the nal payment are also done in the Central Finance system. The purchase order

history is updated by dierent transactions from both the source system and the Central Finance system.

Document Navigation

This function enables you to navigate from the Purch.doc. eld of an FI document in the Central Finance system

to the corresponding purchasing document in the source system.

176

P U B L I C

Central Finance

Down Payment Clearing

Integration of clearing down payment functionality with creation of supplier invoice is not supported in source

systems (MIRO integration via Business Function LOG_MMFI_P2P).

Clearing of the down payment with reference to the supplier invoice must be executed in the Central Finance

system after the journal entry of the supplier invoice is replicated to the Central Finance system.

Supported Fiori Apps

In the Central Payment scenario, payment activities only happen in the Central Finance system. As the Central

Finance system is an S/4HANA system, you can run the transactions either in the SAP GUI or in Fiori.

Supported Fiori apps include:

Fiori App

Transactions in GUI

Manage Journal entries FB08: Reverse document

Reset cleared items FBRA: Reset cleared items

Manage Automatic Payments F110: Parameters for Automatic Payment

Post Outgoing Payments F-48: Post Vendor Down Payment

Post Outgoing Payments F-53: Post Outgoing Payment

Post Outgoing Payments FBZ2: Post Outgoing Payment

Clear Outgoing Payments F-44: Clear Vendor (clear down Payment: Special G/L: A for

open item selection)

Clear Outgoing Payments F-54: Clear Vendor Down Payment

Down Payment Integration with MM is released with functional restrictions, which are described in SAP Note

2683870 .

1.6.8 SEPA Mandate Replication

This chapter includes information about how to enable SEPA mandate replication.

Prerequisites

You have applied SAP Note 1887572 .

Central Finance

P U B L I C 177

1.6.8.1 SEPA Mandate Replication: Conguration for the

Central Finance System

This topic includes information about the conguration for the Central Finance system.

Procedure

1. Launch the Customizing activity Enable SEPA for Applications under Financial Accounting Central

Finance

Central Finance: Target System Settings Central Payment SEPA , and then open the

Financial Accounting application. Enter the following parameter values:

Parameter Val.

ALE: Logical Name of the Consolidation System

ALE: Load Additional Data

FINS_CFIN_APAR_SEPA_LOAD

ALE: Unload Additional Data

FINS_CFIN_APAR_SEPA_UNLOAD

ALE: Filter Data

FINS_CFIN_APAR_SEPA_ALE_FILTER

2. Launch the Customizing activity Dene ALE Filter Object Types under Financial Accounting Central

Finance Central Finance: Target System Settings Central Payment SEPA to add the following ALE

object type:

ALE Object Type

Table Name Field Name

RECEIVER TBD06 RCVSYSTEM

3. Launch the Customizing activity Assign ALE Filter Object Types under Financial Accounting Central

Finance

Central Finance: Target System Settings Central Payment SEPA to assign this lter object

type to BAPIs, as shown below:

Obj. Type Method Filter object type

SEPAMANDAT SAVEREPLICA RECEIVER

4. Launch the Customizing activity Maintain Distribution Model under Financial Accounting Central

Finance Central Finance: Target System Settings Central Payment SEPA to add distribution models

for all source systems.

1. Switch to edit mode and then choose the Create Model View button.

2. Enter the required data and choose Continue.

3. Choose the model view that you have just created and then choose the Add BAPI button.

178

P U B L I C

Central Finance

4. Enter the data as follows and then choose Continue:

Field Value

Sender/client

<Logical system of the Central

Finance system>

Receiver/server

Obj. name/interface

SEPAMANDATE

Method

SAVEREPLICA

5. Select the model view and then choose Environment Generate Partner Proles .

6. Choose Execute.

7. Select the model view and then choose Edit Model View Distribute .

8. Log on to the corresponding source system and generate partner proles for the model view.

9. Repeat the steps above until you have added all the source systems.

5. In the same Customizing activity, add a lter group to the BAPI.

1. Expand the node for the distribution model and nd the receiver determination node under the BAPI

method. Double-click the receiver determination node.

2. Choose Create Filter Group.

3. Expand the lter group and double-click Receiver.

4. Add the logical system of the Central Finance system to the value list and choose Continue.

5. Choose Continue again to close the Change Filter dialog box.

1.6.8.2 SEPA Mandate Replication: Conguration for the

Source System

This topic includes information about the conguration for the source system.

Procedure

1. Launch transaction SM30 - Call View Maintenance, open the V_SEPA_CUST view, and then open the

Financial Accounting application. Enter the following parameter values:

Parameter

Val.

ALE: Logical Name of the Consolidation System

ALE: Load Additional Data

FIN_CFIN_APAR_SEPA_LOAD_SRC

Central Finance

P U B L I C 179

Parameter Val.

ALE: Unload Additional Data

FIN_CFIN_APAR_SEPA_UNLOAD_SRC

ALE: Filter Data

FIN_CFIN_APAR_SEPA_ALE_FILTER

Function Module for Settable Button 2

FIN_CFIN_SEPA_MIGRATE_BUTTON

2. Launch transaction BD95 - Specify ALE object types to add the following ALE object type:

ALE Object Type

Table Name Field Name

RECEIVER TBD06 RCVSYSTEM

3. Launch transaction BD96 - lter objects of receiver determin. to assign this lter object type to BAPIs, as

shown below:

Obj. Type Method Filter object type

SEPAMANDAT CREATE_ALE RECEIVER

SEPAMANDAT CHANGE_ALE RECEIVER

4. Launch transaction BD64 - Maintenance of Distribution Model to add distribution models for all source

systems.

1. Switch to edit mode and then choose the Create Model View button.

2. Enter the required data and choose Continue.

3. Choose the model view that you have just created and then choose the Add BAPI button.

4. Enter the data as follows and then choose Continue:

Field Value

Sender/client

Receiver/server

<Logical system of the Central

Finance system>

Obj. name/interface

SEPAMANDATE

Method

CREATE_ALE

5. Repeat the previous two steps to add another BAPI with method CHANGE_ALE.

6. Select the model view and then choose Environment Generate Partner Proles .

7. Choose Execute.

8. Select the model view and then choose Edit Model View Distribute .

9. Log on to the corresponding Central Finance system and generate partner proles for the model view.

5. In the same Customizing activity, add a lter group to the BAPI.

180

P U B L I C

Central Finance

1. Expand the node for the distribution model and nd the receiver determination node under the BAPI

method. Double-click the receiver determination node.

2. Choose Create Filter Group.

3. Expand the lter group and double-click Receiver.

4. Add the logical system of the source system to the value list and choose Continue.

5. Choose Continue again to close the Change Filter dialog box.

1.6.8.3 SEPA Mandate Replication: Conguring the SAP

Application Interface Framework

This topic includes information about integrating the IDoc transfer status into the Application Interface

Framework (AIF) in the Central Finance system. The integration enables the reprocessing of failed IDocs. The

AIF enables you to develop and monitor interfaces as well as execute error handling in a single framework that

resides in your SAP backend system.

Prerequisites

You have activated the business conguration set FINS_CFIN_AIF_SEPA using transaction SCPR20 - Activate

BC Sets.

Procedure

1. Dene AIF reprocessing action.

1. Launch transaction /AIF/REP_AC_DEF - AIF Reprocessing Action Denition.

2. Enter /FINCF as the namespace and choose Continue ( Enter ).

3. Fill out the view as follows:

Namespace

/FINCF

Repr. Action Name

RECREATE

Function Module

/AIF/RESTART_MSG

Namespace

/FINCF

2. Assign AIF reprocessing action.

1. Launch transaction /AIF/REP_AC_ASGN - AIF Reprocessing Action Assignment.

2. Fill out the dialog box that appears as follows and choose Continue ( Enter ).

Central Finance

P U B L I C 181

Namespace

/FINCF

Interface Name

ISEPA_CR

Interface Version

3. Add a new entry as follows:

Message Class

FINS_CFIN_APAR_MESSA

Message

021

Namespace

/FINCF

Repr. Action Name

RECREATE

Max Repr. Counter

3 (You can use another value.)

Min. Time in Seconds

2 (You can use another value.)

Max. Time in Seconds

3 (You can use another value.)

Intermediate Status

In Process (You can use another value.)

3. Dene IDoc interfaces.

1. Launch transaction /AIF/CUST - Customizing.

2. Launch the Dene Interface Determination for IDoc Interfaces Customizing activity under System

Conguration

Interface Determination .

3. Create three entries as follows in the Dene Determination Key node:

Basic Type

Message Type

SEPAMANDATE_CHANGE_ALE01 SEPAMANDATE_CHANGE_ALE

SEPAMANDATE_CREATE_ALE01 SEPAMANDATE_CREATE_ALE

SEPAMANDATE_SAVEREPLICA01 SEPAMANDATE_SAVEREPLICA

4. Select each of the three entries above and double-click the Assign Interfaces node.

5. Fill out the page that appears as follows:

For basic type SEPAMANDATE_CHANGE_ALE01:

Value Number

Namespace

/FINCF

Interface Name

ISEPA_CH

182 P U B L I C

Central Finance

Interface Version

For basic type SEPAMANDATE_CREATE_ALE01:

Value Number

Namespace

/FINCF

Interface Name

ISEPA_CR

Interface Version

For basic type SEPAMANDATE_SAVEREPLICA01:

Value Number

Namespace

/FINCF

Interface Name

ISEPA_SR

Interface Version

1.6.8.4 Migrating SEPA Mandates

This topic includes information about how to migrate SEPA mandates from the source system to the Central

Finance system.

Procedure

1. Launch transaction FSEPA_M4 - SEPA: List Mandates in source systems.

2. Enter the search criteria and choose Execute ( F8 ).

3. Select the SEPA mandates that you want to migrate and choose Migrate.

 Note

Only the mandates whose company code is activated with central payment can be migrated to the

Central Finance system.

1.6.8.5 Using the SEPA Mandate Reconciliation Tool

This topic includes information about how to use the SEPA mandate reconciliation tool in the Central Finance

system.

Central Finance

P U B L I C 183

Procedure

1. Launch transaction SE38 - ABAP Editor.

2. Enter FINS_CFIN_APAR_SEPA_REC as the program and choose Execute ( F8 ).

3. Enter the search criteria and choose Execute ( F8 ).

Result

The program displays the result of SEPA mandate reconciliation. You can then perform the following actions:

● Check the detailed comparison result for a mandate.

Double-click the icon for a mandate to display the comparison result for each eld of the mandate.

● Modify a mandate.

Double-click the icon for a mandate, select either the column for the source system or that for the Central

Finance system, and choose Modify ( F5 ). You are then navigated to the Change Mandate screen.

 Note

If a column contains no data, you cannot modify the column.

● Synchronize the data for one or more mandates.

Select the mandates whose data you want to synchronize and choose Synchronize. Enter a system from

which you want to retrieve data and choose Conrm ( Enter ). If any error occurs during the

synchronization, track the error in transaction WE02 - Display IDoc or /N/AIF/ERR - Monitoring and Error

Handling.

● Refresh the comparison result.

Choose Refresh to refresh the comparison result.

1.7 Central Tax Reporting

When FI and CO documents are replicated from source systems to a Central Finance system, tax-relevant data

is also replicated.

When Central Payment is activated, which is done on a company code basis, it becomes necessary for some

tax-relevant postings to be made in the Central Finance system. As a result, tax reporting must also be carried

out in the Central Finance system, based on the documents in the Central Finance system, whether they have

been replicated to the system from a source system or posted there directly.

This document describes both the checks that are available to ensure that the tax-relevant data posted in the

Central Finance system is accurate for the purposes of reporting tax and the tax-relevant reports that can be

run in a Central Finance system and the restrictions that apply to these reports.

 Note

Calculation of taxes from your SAP S/4HANA Central Finance system and any reporting based on this

calculation covers a certain scope and may not meet all of the requirements in your jurisdiction.

184

P U B L I C

Central Finance

You must check with your accounting or tax experts in order to make sure that the results generated by

Central Tax Reporting are fully compliant with your relevant jurisdictions' specic tax reporting

requirements.

For information on which tax reports are supported in Central Tax Reporting, see Overview of Supported

Reports [page 189].

1.7.1 Central Tax Reporting: Prerequisites

1.7.1.1 Before You Start

If you already have an active Central Finance system, your tax-relevant data may not be correct. Therefore,

before implementing Central Payment, it will either be necessary to reload all of your data with the tax checks

activated or to carry out certain clean-up activities. In order to do this we recommend that you engage a

consultant.

SAP Notes

See SAP Note 2509047 Central Finance: Required SAP Notes to support Tax Reporting out of the Central

Finance System for details about other SAP Notes that you need to take into account.

General Prerequisites

You must enable the enhanced tax checks (tax conguration consistency check and tax recalculation check)

far enough in advance so that payment-relevant open items that are transferred as part of ongoing replication

are posted with accurate tax data.

1.7.1.2 Tax Reporting in Source System

Before you start tax reporting out of a Central Finance system, you must have completed tax reporting from

your source system for periods for which only open items and balances are included in the initial load. For more

information, see Initial Load of Open Items.

1.7.1.3 Rounding of Tax Values

When tax is posted, the posted values must not be rounded. Therefore, the currencies involved in the

transaction must not have fewer decimal places in the Central Finance system than they do in the source

system.

Central Finance

P U B L I C 185

In the IMG activity Dene Decimal Places for Currencies in Source Systems you can identify currencies that have

dierent numbers of decimals in the source system and the target system. You must then ensure that each

currency in your Central Finance system has at least as many decimals as in the connected source systems.

If you are already working with an active Central Finance system and then decide to activate Central Payment

and your decimal settings for currencies do not fulll this requirement, it will be necessary to start your Central

Finance implementation again from the beginning.

1.7.2 Conguration Consistency Checks

To ensure that postings that are replicated to Central Finance are consistent for the purposes of reporting tax,

it is necessary to make sure that the tax-related conguration settings of the source systems match the

conguration settings in the Central Finance system.

For example, a tax code in the source system has the tax category “input tax”. In the Central Finance system,

the corresponding tax code (which may have been mapped) has the tax category “output tax”.

If this inconsistency were not detected, it would lead to errors in tax reporting from the Central Finance system.

In the IMG activity Activate Tax Consistency Check for Company Codes, you can activate or deactivate the tax

conguration consistency checks and tax recalculation checks for combinations of individual source company

codes and source systems.

1.7.2.1 Tax Conguration Consistency Checks

If customizing entities for which conguration does not match in the source and target system are involved in a

replicated FI/CO posting, the Central Finance system stops the posting.

The system issues an error message describing the error and telling you where you can correct it. To make the

correction, it may be necessary to introduce new customizing entities or add mappings.

Once the incorrect conguration has been corrected the AIF messages can be restarted so that the documents

are posted.

1.7.2.2 Customizing Entities Involved in the Checks

The following Customizing tables are involved in the checks:

● T001 (Company Code)

● T005 (Countries)

● T007A (Tax Keys)

● T007B (Tax Processing in Accounting )

186

P U B L I C

Central Finance

● T000F (Client-Specic FI Settings)

● TVAT001 (Customizing of Tax on Sales/Purchases - Control of Screen)

● TTXD (Description of Tax Jurisdiction Code Structure)

For the complete list, see SAP Note 2494127 .

During the replication of FI documents with withholding taxes to the Central Finance system, automatic checks

of the withholding tax conguration are executed.

The following Customizing tables are compared in the source and the Central Finance system for withholding

taxes:

● T059P (Withholding Tax Types)

● T059Z (Withholding Tax Codes)

● T001WT (Company Code Spec. Information per WHT Type)

● T001RWT (Rounding Rules for Company Code and WHT Type)

● T059MINMAX (Minimum and Maximum Amounts for WHT)

● T030 (Standard Accounts Table)

1.7.2.3 Install SAP System Landscape Transformation

Server Content

To enable the checks during posting, the source system conguration data is replicated via SLT into dedicated

target system conguration tables.

This required content is described in SAP Note 2494127 .

Additionally for withholding tax, you need to implement the required content in SLT as described in the SAP

note 2668261 .

1.7.2.4 VAT Recalculation Check

When postings are replicated to Central Finance, the system recalculates tax values based on the conguration

of the Central Finance system and compares the expected outcome with the replicated values to be posted and

issues an error if a signicant dierence is detected.

Prerequisites for this check:

● The tax code must be congured with the indicator Error Message for Invalid Tax Amount (eld label Check-

ID) set (T007A-PRUEF = ‘X’).

● In addition, an appropriate tolerance must be congured for the Tolerance Percentage Rate for Tax

Calculation. This tolerance percentage rate denes, for the tax code, the percentage rate which is accepted

as tolerance between a calculated value and a value which was replicated. This setting also applies to the

values which are entered for documents posted directly in the Central Finance system.

The Tolerance Percentage Rate for Tax Calculation must be set to check the value strictly, that is, as close to

zero as possible.

Central Finance

P U B L I C 187

 Note

The tolerance amount arises from the application of percentage rates to the amount determined by the

system. If the dierence between the tax value replicated and the value calculated by the system is

lower than the tolerance amount, the document is posted by the system and no warning or error

message is issued.

The following cases are excluded from tax recalculation:

Description Logical Constraint

Postings that originate from contract accounting BKPF-awtyp = 'FKKSU'

Postings that originate from sales and distribution BKPF-awtyp = 'VBRK'

Postings that originate from CRM-billing BKPF-awtyp = 'BEBD'

Postings with special G/L transaction type down payment

request and with tax code

BSEG-umsks = 'A' and BSEG-mwskz NE space

Cross-company posting BSEG-ktosl = 'BUV'

Summarization over tax jurisdiction code Structure of jurisdiction code specied for the schema of the

country and BSEG-TAXPS is initial

Posting with origin HR that have been split due to technical

reasons

BKPF-awtyp = 'HRPAY' and

BSEG-ktosl = 'HRA'

Postings that have been split with classical split logic BKPF-awtyp not in ('MKPF', 'RMRP', 'VBRK', 'WBRK',

'BEBD') and

BKPF-xsplit = 'X'

Initial load Transaction type = 'O'

1.7.3 Tax Reporting Based on Postings from the Initial Load

Initial Load of Documents

Reporting of deferred tax is not supported for documents that were transferred as part of the initial load of

documents.

Initial Load of Open Items

Open items are transferred without any tax information and without the other line items (income and expense).

Therefore, you should note the following:

● Central Finance does not support tax reporting for those periods of the initial load for which only balances

and open items are transferred.

For these periods, tax reporting must be done out of the source system and must be completed before you

start reporting taxes out of the Central Finance system.

188

P U B L I C

Central Finance

Central Payment must not be activated until this task has been completed.

● Reporting of deferred tax is not supported for open items that were transferred as part of the initial load of

open items and balances.

● If tax reporting is carried out based on selection via posting date (BUDAT) or tax reporting date (BKPF-

VATDATE) then, once you have transitioned to central tax reporting, you should not make retrospective

postings into the periods which were covered by the initial load of open items and balances only.

1.7.4 Overview of Supported Reports

This section describes the reports that are supported while also describing any relevant limitations.

For any reports that are not mentioned in this section, you should assume that they are not currently

supported.

For country/region-specic tax reports in Advanced Compliance Reporting which are supported in Central

Finance, see Advanced Compliance Reporting: Country/Region-Specic Reports in Central Finance [page

220].

1.7.4.1 Country-Specic Requirements

 Note

This document does not cover country-specic tax reporting capabilities.

Ocial Document Numbering (ODN)

Central Finance does not currently support the concept of ocial document numbering. Consequently, tax

reporting for countries where ocial document numbering is a legal requirement is not supported.

1.7.4.2 Core Tax Reports

Technical Name Description Remarks

RFUMSV00

Advance Return for Tax on Sales/

Purchases

Restrictions apply

RFUVDE00

Print Program: Advance Return for Tax

on Sales/Purchases (Germany)

Same restrictions apply as for

RFUMSV00

RFUMSV10

Additional List for Advance Return for

Tax on Sales/Purchases

Restrictions apply

Central Finance

P U B L I C 189

Technical Name Description Remarks

RFID_PTVPRADPRC00

Pro-Rata adjustments due to PR calcu

lation

Must be tested in the project

RFID_PTVPRADPRV00

Pro-Rata adjustments due to PR varia

tion

Must be tested in the project

RFUMSRVG00

VAT Refund Must be tested in the project

RFUMSV35

Tax Adjustment Must be tested in the project

RFASLM00

EC Sales List Restrictions apply

RFASLD20

EC Sales List in Data Medium Exchange

Format

Restrictions apply

Restrictions Applying to these Reports

● RFUMSV00 - Advance Return for Tax on Sales/Purchases

If the posting in question was triggered by a gift invoice from SD, business partner-related information will

be missing from the report.

● RFUVDE00 - Print Program: Advance Return for Tax on Sales/Purchases (Germany)

If the posting in question was triggered by a gift invoice from SD, business partner-related information will

be missing from the report.

Data from transfer posting of deferred tax will be missing.

● RFUMSV10 - Additional List for Advance Return for Tax on Sales/Purchases

○ To enable access to cross-company documents which are connected via BKPF-BVORG (number of the

cross-company code posting transaction) for documents from the initial load you must have

implemented SAP Note 2489200 before the initial load for those documents was carried out.

○ Some data related to accounts for Purchase Account Management (for example for IT and FR) may be

missing from the report.

○ Some data from FI Contract Accounting (FI-CA) and HR Payroll (HRPAY) may be missing from the

report.

● RFASLM00 – EC Sales List

Business partner-related information will be missing from the report.

Some data from FI Contract Accounting (FI-CA) and HR Payroll (HRPAY) may be missing from the report.

● RFASLD20 - EC Sales List in Data Medium Exchange Format

● Some data related to accounts for Purchase Account Management (for example for IT and FR) may be

missing from the report.

Some data from FI Contract Accounting (FI-CA) and HR Payroll (HRPAY) may be missing from the report.

190

P U B L I C

Central Finance

1.7.5 Deferred Tax

Two variants of deferred tax processing exist:

1. Old: Deferred Tax is represented by open items on related tax accounts only.

2. New: A separate database (table DEFTAX_ITEM) stores the data of invoices, payments, down payments,

tax transfer documents, and any other documents that are relevant for deferred taxes.

 Recommendation

We recommend that you use the new variant in your Central Finance system.

Central Finance does not currently support deferred tax with the initial load.

If you have activated Central Payment, deferred tax must not be active in your source systems. Instead

deferred tax must be processed in the Central Finance system only.

Potentially deferred tax could work in a greeneld scenario. However, this would need to be assured by

appropriate testing.

1.7.6 Withholding Tax

Withholding taxes are supported in the Central Finance scenario with some restrictions. Supported use cases

and current restrictions are explained below.

 Note

Please consider carefully which restrictions apply to your business processes and their impact in your

Central Finance scenario.

Premises

● If you have activated Central Payment for a certain source company code, you post documents centrally

with tax impact in the Central Finance system that are not available in the source system. That is why you

must also do the tax reporting in the

Central Finance system.

This applies to all taxes including withholding taxes.

● Central Finance supports Extended Withholding Tax only. In all source company codes, for which

withholding taxes shall be replicated to the Central Finance system, Extended Withholding Tax must be

activated in the respective source system.

● Withholding taxes are calculated in the source system and transferred to the Central Finance system

exactly as they are posted in the source system. They are not recalculated in the Central Finance system.

Please make sure that the withholding tax conguration in your source system(s) and the Central Finance

system is semantically the same, even if various Customizing codes are dierent and require mapping.

● Certicate numbers are always generated in the Central Finance system. For this reason, you need to make

all required settings for WHT certicate numbering in the Central Finance system.

Central Finance

P U B L I C 191

● Accumulation data for withholding taxes and localization is not supported as part of the standard product.

For more details, please read (Accumulated) Withholding Taxes and Central Payment [page 193].

● Implement the relevant SAP notes for the source system. You can nd a list of relevant SAP notes in SAP

note 2623514 .

See Also

● Use Cases for Replication of Withholding Taxes to Central Finance [page 192]

● Conguration Consistency Checks for Withholding Taxes (Ongoing Replication) [page 193]

● (Accumulated) Withholding Taxes and Central Payment [page 193]

1.7.6.1 Use Cases for Replication of Withholding Taxes to

Central Finance

In the following, the supported use cases for replicating withholding taxes to Central Finance are described. To

check exactly which elds are considered in the replication, you can refer to the ACCIT_WT structure.

● Withholding taxes posted at the time of invoice (ongoing replication)

Withholding taxes posted at the time of invoicing, are calculated in the source system and replicated to the

Central Finance system in real time as part of the FI document.

● Withholding taxes posted at the time of payment (ongoing replication)

○ Withholding taxes posted at the time of payment, are calculated in the source system and replicated to

the Central Finance system in real time as part of the FI document. The relevant withholding tax data

are replicated to the Central Finance system when an invoice is posted as well as when a payment is

posted. Additionally, the payment transaction updates the withholding tax data referring to the invoice

paid and the updated data are also transferred to Central Finance. If you have activated Central

Payment, withholding taxes at the time of payment are calculated and posted in the Central Finance

system only.

○ If you have activated Central Payment, withholding taxes at the time of payment are calculated and

posted in the Central Finance system only.

● Withholding taxes in reversal documents

When you reverse an invoice or a payment including withholding taxes in the source system, the respective

withholding tax data are reset both in the source system and the Central Finance system.

● Withholding taxes in the initial load of documents and open items

When you perform an initial load for documents or open items, withholding tax information is transferred

to the Central Finance system.

● Withholding taxes within document changes

When one of the withholding tax relevant elds in the FI document is changed in the source system, this

change is transferred to the Central Finance system. This might occur, for example, for the Withholding Tax

Base Amount eld.

192

P U B L I C

Central Finance

1.7.6.2 Conguration Consistency Checks for Withholding

Taxes (Ongoing Replication)

During the replication of FI documents with withholding taxes to the Central Finance system, the system

checks the withholding tax conguration.

For the list of Customizing tables that are compared in the source and the Central Finance system, see

Customizing Entities Involved in the Checks [page 186].

If the conguration of Customizing entities, like for example withholding tax types and withholding tax codes

does not match in the source and the Central Finance system, the posting is stopped. The system issues an

error message in SAP AIF, which describes the error and how to correct it. Once, you have corrected the

conguration, the SAP AIF message can be restarted and the document is posted in the Central Finance

system.

● Withholding tax checks are activated in the Central Finance system together with the VAT checks in the

IMG activity (Implementation Guide (IMG) Path: Financial Accounting Central Finance Central

Finance: Target System Settings

Set Up Systems Activate Tax Consistency Check for Company

Codes ).

See also, Conguration Consistency Checks [page 186].

● Additionally, you need to implement the required content in SLT as described in the SAP note 2668261 .

See also, Install SAP System Landscape Transformation Server Content [page 187].

1.7.6.3 (Accumulated) Withholding Taxes and Central

Payment

● If you use only withholding taxes (WHT) without accumulation, you can activate Central Payment and start

preparing your WHT reporting in the Central Finance system.

● If you use withholding taxes with accumulation and want to activate Central Payment, you should rst

analyze your business processes and decide carefully, whether and when the Central Payment function

shall be activated.

Accumulation data are not replicated to the Central Finance system. It depends on the tax types used, on

the point in time at which the accumulation is done, on whether Central Payment is active or not, whether

the accumulated withholding taxes are available in the Central Finance system. Below the scenarios

possible are listed.

Scenarios

● Central Payment is not active for the company code.

○ You can always perform withholding tax reporting in the source system.

○ Accumulation for WHT at the time of invoicing:

WHT is calculated and accumulated in the source system when the invoice is posted. Accumulated

withholding tax information for WHT at the time of invoicing is not available in the Central Finance

Central Finance

P U B L I C 193

system. If the accumulated values for WHT are required for the WHT reporting, it will not be complete

in the Central Finance system.

○ Accumulation for WHT at the time of payment:

WHT is calculated and accumulated in the source system when the payment is posted. Accumulated

withholding tax information for WHT at the time of payment is not available in the Central Finance

system. If the accumulated values for WHT are required for the WHT reporting, it will not be complete

in the Central Finance system.

● Central Payment is active for the company code.

○ You shall perform withholding tax reporting in the Central Finance system, starting with the month at

which you activate Central Payment.

○ Accumulation for WHT at the time of invoicing:

WHT is calculated and accumulated in the source system when the invoice is posted. Accumulated

withholding tax information for WHT at the time of invoicing is not available in the Central Finance

system. If the accumulated values for WHT are required for the WHT reporting, it will not be complete

in the Central Finance system.

○ Accumulation for WHT at the time of payment:

WHT is calculated and accumulated in the Central Finance system when the payment is posted.

Accumulated withholding tax information for WHT at the time of payment is available in the Central

Finance system. All WHT information at the time of payment including information about accumulated

WHT is in the Central Finance system, starting with the month (for monthly accumulation) or the year

(for yearly accumulation) at which you activated Central Payment.

○ If you activate Central Payment in the middle of the month or the middle of the year and you use

monthly or yearly accumulation, no information about accumulated WHT for the past part of the

month or year are available in the Central Finance system. Therefore, it is important that you activate

Central Payment at the beginning of a month or year, if you use monthly or yearly accumulated WHT to

be posted at the time of payment.

 Note

If you use accumulated WHT, you must make sure that you activate Central Payment before the

next accumulation period starts, being this a month, a calendar year or a 12-month period starting

on a specic month. That way all information for calculating accumulated WTH is available in the

Central Finance system.

1.7.7 External Tax Calculation

If you use an external tax calculation system that is called in your source system, you must use the same

external tax calculation system in your Central Finance system.

External tax calculation out of SD invoicing is not currently supported.

1.7.8 Input Tax from Parked Documents

Central Finance does not replicate parked documents.

194

P U B L I C

Central Finance

However, you can choose to run report RFPUMS00 in the source systems in which the parked documents were

originally posted. The generated GL postings, including taxes, will then be replicated to Central Finance.

1.7.9 Support of Tax Reports in Mode “Update of Documents”

Some tax reports can be run in the mode Update of Documents.

In this mode, only those tax items in which no date or time of an earlier run is noted are selected.

The date and time of the current run are then marked in the selected tax items, which prevents individual items

being reported twice in cases of organizational diculties.

Once the tax reporting process has transitioned from source to target system, the status of date eld (BSET-

STMDT – the date on which the tax return was made) in the source system will not be reected in the Central

Finance system. Therefore, when making selections you must take into account that the value of this date eld

may not be accurate for periods for which reporting has been done from the source system.

If you want to use the Update of Documents mode, you should initialize the Date of Tax Return and Time of Tax

Return elds (BSET-STMDT and BSET-STMTI) with a dummy date for the periods in question.

1.8 Central Projects (WBS) - Reporting Scenario

You are using a Central Finance scenario, where you are creating and editing projects in a source system and

want to do the project reporting on costs and revenues posted to WBS elements in the Central Finance system.

The Central Projects (WBS) - Reporting Scenario allows you to subsequently post FI documents (journal

entries) and CO documents with the account assignment to a work breakdown structure (WBS) element, and

use the project reporting in the Central Finance system for those postings.

The WBS elements are maintained in the project system in a source system. To keep this information also in

the journal entries (FI documents) that are replicated to the Central Finance system and allow the reporting in

the Central Finance system, the project denition and WBS elements created in a source system are replicated

in real-time to the Central Finance system. Also, changes to project denitions or WBS elements are replicated

continuously to the Central Finance system.

Central Finance

P U B L I C 195

Architecture for Replicating Project Data to Central Finance

For the replication of project data Application Link Enabling (ALE) is used. The Intermediate Document (IDoc)

for projects contains the project data for replication. With SAP Application Interface Framework (AIF), you can

monitor, whether project data have been replicated correctly.

 Note

WBS elements can have dierent identiers in the source system and the Central Finance system. Also, the

same identiers can be used in two dierent source systems. Therefore, the identiers are mapped to

identiers in the Central Finance system when the FI documents (journal entries) are posted. When a

project is replicated to the Central Finance system for the rst time, new identiers are derived for the

project and the WBS elements. During updates, changes are posted to the project names or WBS elements

in the Central Finance system.

Initial Load for Project Master Data

For the initial load of project master data, you can use the transaction CJAL in the source system in order to

replicate projects and WBS elements for the rst time. With this transaction the ALE replication is called and an

IDoc with projects and WBS elements is sent to the Central Finance system.

Constraints

● Re-posting projects with user changes in SAP AIF is not supported.

● You edit or change the projects in the source system. You cannot edit or change them in the Central

Finance system.

196

P U B L I C

Central Finance

● Once a project is released in the source system and thus replicated to the Central Finance system, you

cannot delete WBS elements anymore. You can enter a deletion ag in the source system and the system

status DLFL is replicated to the Central Finance system.

● Once the projects are replicated to the Central Finance system, the IDs of the project and the contained

WBS elements can no longer be changed neither in the source system nor in the Central Finance system.

● The WBS project structure only is replicated. Networks are not replicated.

● Customer enhancements to the project and WBS elements are not replicated, for example elds dened in

structure CI_PROJ.

See Also

To congure this scenario in your source systems and the Central Finance system, carry out the following steps

in the stated sequence:

1. Central Projects (WBS) - Reporting Scenario: Conguration in Source System [page 197]

2. Central Projects (WBS) - Reporting Scenario: Conguration for SAP AIF [page 199]

3. Central Projects (WBS) - Reporting Scenario: Conguration in the Central Finance System [page 200]

4. Central Projects (WBS) - Reporting Scenario: Check Settings for Replication of Projects [page 202]

For more information on projects and WBS elements, see Project System (PS).

1.8.1 Central Projects (WBS) - Reporting Scenario:

Conguration in Source System

To allow ongoing replication of projects between a source system and the Central Finance system, you create

an Application Link Enabling (ALE) distribution model in Customizing of the source system.

Prerequisites

● You have dened RFC connections from the source to the Central Finance system using transaction SM59.

● You have dened the business systems.

● For references to WBS elements in the FI or CO documents to be replicated correctly from the source to

the Central Finance system, you must have implemented the following SAP Notes in the source system:

○ SAP Note 2513048

○ SAP Note 2553477

How-To

Create ALE Distribution Model in the Source System

Central Finance

P U B L I C 197

1. Launch transaction BD64 - Display Distribution Model to add a distribution model for replicating project

data for the respective source system.

Alternatively, you can enter transaction SALE and then choose Modelling and Implementing Business

Processes Maintain Distribution Model and Distribute Views and execute the IMG activity.

2. Switch to edit mode and then choose the Create Model View button.

3. Enter the required data and choose Continue.

4. Choose the model view that you have just created and then choose the Add BAPI button.

5. Enter the data as follows and then choose Continue:

Field Value

Sender/client <Logical system of the source system>

Receiver/server <Logical system of the Central Finance system>

Obj.name/interface

WorkBreakdownStruct

Method

SaveReplica

6. Select the model view and then choose Environment Generate Partner Proles .

7. Choose Execute.

8. Select the model view and then choose Edit Model View Distribute .

 Note

To replicate only certain selected controlling areas and project proles, you can set an ALE lter, that

is, enter a list of controlling areas or project proles.

○ If you do not set an ALE lter, that is, you do not enter anything here, all projects and WBS

elements are replicated continuously.

○ If you set an ALE lter, only projects and WBS elements from the specied controlling areas and

project proles are replicated.

9. Go to the project model and expand the tree to the last node Receiver determination: no lter and double

click it.

10. Choose the Create Filter Group button and expand the new lter group.

11. Click on Controlling Area or Project Prole and add the respective values and save your entries.

12. In the source system, call transaction WE20 and create an entry for a new IDoc type in the Partner Prole.

The new IDoc type PROJECT02 allows you to replicate project data including custom elds for projects

from a source system to the

Central Finance system.

Field

Value

Partner No.

<Logical system of the Central Finance

system>

Partner Type

LS (Logical System)

Post Processing: Permitted Agent tab

Type US (User)

198 P U B L I C

Central Finance

Field Value

Agent

Language

EN (English)

Outbound Parameters tab

Message Type PROJECT

Basic Type PROJECT02

Result

You are nished with the conguration in the source system. The ALE model for replicating project data is

distributed, but the partner proles do not exist yet in the Central Finance system. These will only be available

after you have also nished the conguration in the Central Finance system.

1.8.2 Central Projects (WBS) - Reporting Scenario:

Conguration for SAP AIF

To enable your users to monitor messages for replicated projects and WBS elements in SAP AIF, you activate a

BC set in the Central Finance system.

How-To

1. Call up transaction SCPR20 - Business Conguration Sets: Activation.

2. Enter the BC-Set FINS_CFIN_AIF_PS and click on Activate BC Set (F7).

Result

After you have done this, you can use transaction /AIF/ERR - Monitoring and Error Handling with Name

Space /FINCF and Interface Name PS_OBJ to monitor AIF messages for replicated projects.

Next Step

It might be necessary to start transaction /AIF/DEL_STRUC_CACHE - Delete Structure Cache to display the

correct texts within the transaction /AIF/ERR with Name Space /FINCF and Interface Name PS_OBJ.

Central Finance

P U B L I C 199

See Also

About Error Handling [page 29]

1.8.3 Central Projects (WBS) - Reporting Scenario:

Conguration in the Central Finance System

To allow ongoing replication of projects between a source system and the Central Finance system, you create

an Application Link Enabling (ALE) distribution model and assign a process code in Customizing of the Central

Finance system.

The steps are as follows:

1. You create an Application Link Enabling (ALE) distribution model in the Central Finance system for sending

and receiving project data using transaction SALE or BD64.

2. You assign a process code for the Central Projects (WBS) - Reporting Scenario using transaction WE20.

3. You specify a new interface determination for IDoc interfaces within SAP Application Interface Framework

(SAP AIF).

Prerequisites

● You have dened the business systems.

● You have performed the Customizing for projects in the source and the Central Finance system and made

sure that the project conguration in the Central Finance system ts the project conguration in the source

systems.

You have ensured that the denition of the project mask dened in the Central Finance system does not

lead to inconsistencies with the project masks dened in the source systems.

● You have set the mapping action for the project and the WBS element to Obligatory.

You do this in Customizing of Central Finance (transaction SPRO) (SAP Reference IMG) under Financial

Accounting

Central Finance Central Finance: Target System Settings Mapping Dene Mapping

Actions for Mapping Entities .

● You have implemented the Business Add-In (BAdI) Enhance Processing of Project Data for project

identiers. For more information, see the documentation of the IMG activity under Customizing of Central

Finance (transaction

SPRO) under Financial Accounting Central Finance Central Finance: Target

System Settings BAdIs: Central Finance .

● You have performed the conguration settings for Central Finance.

You can nd the necessary settings in Customizing of Central Finance (transaction SPRO) under

Financial Accounting Central Finance Central Finance: Target System Settings Set Up Systems .

For detailed instructions, see the documentation of each Customizing (Implementation Guide) (IMG)

activity.

200

P U B L I C

Central Finance

How-To

Create ALE Distribution Model in the Central Finance System

1. Launch transaction BD64 - Display Distribution Model.

2. Select the model view which has been distributed from the source system and then choose Environment

Generate Partner Proles .

Field Value

Outbound Parameters Tick Pass IDoc Immediately

Inbound Parameters Tick Trigger Immediately

3. Choose Execute.

Assign Process Code for the Central Projects (WBS) - Reporting Scenario in Partner Prole

1. In the Central Finance system, enter transaction WE20.

2. To dene inbound parameter for the sending system, under Partner Proles Partner Type LS choose

the source system.

3. On the Post Processing: Permitted Agent tile under Inbound Paramters click on the Create Inbound

Parameter icon, that is, add a new entry.

4. In the Partner Proles: Inbound Parameters screen, enter the data as follows.

Field Value

Message Type

Project

Process Code

/FINS_CFIN_PS_PROJECT

Tick Cancel Processing After Syntax Error

Choose Trigger Immediately

Dene Interface Determination for IDoc Interfaces (SAP AIF)

1. In Customizing of SAP AIF (transaction /AIF/CUST) under System Conguration Interface

Determination

perform the Dene Interface Determination for IDoc Interfaces Customizing activity.

2. To create a new entry for interface determination, for Dene Determination Key choose New Entries in

change mode, enter the following and save your entries:.

Field

Value

Basic Type

PROJECT02

Message Type

PROJECT

Central Finance

P U B L I C 201

4. Select Assign Interfaces in the menu on the left-hand side and choose New Entries in change mode. Enter

the following and save your entries:

Field Value

Basic Type

PROJECT02

Message Type

PROJECT

Value Number

Namespace

/FINCF

Interface Name

PS_OBJ

Interface Version

Result

You are nished with the conguration in the Central Finance system. The ongoing replication of project data is

now enabled for the Central Projects (WBS) - Reporting Scenario with ALE/IDoc including custom elds for

projects.

1.8.4 Central Projects (WBS) - Reporting Scenario: Check

Settings for Replication of Projects

To ensure that the conguration settings for the replication of project data is complete, you can use the Central

Finance: Check Settings for Replications of Projects report in the Central Finance system.

The report checks, for example, the following conguration settings:

● Is the BC set FINS_CFIN_AIF_PS extracted?

● Is the right process code assigned in the Application Link Enabling (ALE) partner prole for the system

selected?

Transaction WE20, the inbound handling for the Intermediate Document (IDoc) that holds the project data,

needs to be assigned to the project code /FINS_CFIN_PS_PROJECT.

● Is the mapping action for the project ID and work breakdown structure (WBS) element set to Mapping

obligatory for the selected systems?

● Is no coding mask for projects dened?

● Is the IDoc type PROJECT02 dened as IDoc interface for SAP AIF?

Procedure

1. Call transaction SA38 - ABAP Program Execution.

202

P U B L I C

Central Finance

2. Enter FINS_CFIN_PS_CHECK as the program and choose Execute (F8) .

3. Enter the <logical system of the source system>, for example E10CLNT300, and choose Execute (F8).

Result

The report displays a log of the success, warning and error messages for the conguration settings determined

during the check. This allows you to easily nd out, which settings are not yet correct and leads you to the

respective conguration settings where you can make corrections.

For more information, please display the report documentation in the system by clicking the I-Button, or if you

are using Web GUI, access the documentation with More Documentation .

Next Step

If the check report does not display any errors, you can start the initial data transfer of projects from the source

system using transaction CJAL in the source system.

1.9 Third-Party System Interface to Central Finance:

Process and Architecture

This topic includes information about the process for replicating nancial accounting data from a third-party

source system to the SAP S/4HANA Central Finance system using the third-party system interface with staging

tables for business data structures on the SAP Landscape Transformation Replication Server (SAP LT

Replication Server).

Process

With this new interface, you can replicate nancial accounting data from a third-party system to a SAP S/

4HANA Central Finance system. You can transfer the following kind of documents:

● General journal entries (including source references, segment, prot center, division and trading partner)

● Documents with business partner, like customers and suppliers (including source references, segment,

prot center, division, trading partner, discount, payment information, product tax, withholding tax)

If you want to replicate journal entries with withholding taxes, you need to set up the Extended Withholding

Tax. You do this in Customizing (IMG: transaction SPRO) under Financial Accounting Financial Accounting

Global Settings Withholding Tax Extended Withholding Tax . The old Withholding Tax function is not

supported.

Central Finance

P U B L I C 203

 Caution

Withholding tax postings at the time of payment are not supported in the third-party system interface to

Central Finance.

After data replication, the SAP Application Interface Framework (SAP AIF) is triggered to control data

processing within the Central Finance system. Data processing includes key mapping and value mapping

provided by the SAP Master Data Governance (SAP MDG) framework and nally the update of the Central

Finance data base. Upcoming processing issues are collected. The monitoring of the FI document processing is

done by using SAP AIF. In SAP AIF, documents are displayed which have been replicated and posted in the

Central Finance system, and there are also error messages displayed, if documents could not be posted in the

Central Finance system. This allows you to correct errors and restart the posting of the corrected documents.

Building Blocks of the Third-Party System Interface to Central Finance

To check FI documents posted from a third-party system to a Central Finance system, you can use the

following reports. For more information, see the report documentation in the system:

● Comparison of FI Document Headers (transaction FINS_CFIN_DFV_FI_NUM)

● Comparison of FI Line Items (transaction FINS_CFIN_DFV_FI_DOC)

The following chapters contain information on how to install the staging tables for the third-party system

interface on the SAP LT Replication Server, and on how to congure each of the mentioned building blocks or

components, as the SAP LT Replication Server, the SAP AIF, SAP S/4HANA Central Finance, SAP MDG to

enable the usage of the third-party system interface. You nd also information on extensibility. The extraction

report as such is not part of this documentation nor is it delivered by SAP. Customers are responsible for

extracting data from a third-party system and lling the staging tables in SLT. To extract data from a third-party

system and ll the staging tables in SLT, customers can use SAP Central Finance Transaction Replication by

Magnitude for SAP S/4HANA [page 220].

1.9.1 Replicating Data Using the Third-Party System Interface

to Central Finance

204

P U B L I C

Central Finance

1.9.1.1 Upgrade of Third-Party System Interface to Central

Finance

Steps you need to perform for upgrading the Third-Party System Interface to Central Finance when upgrading

the Central Finance system to the highest SAP S/4HANA release or to the most recent support package.

Use

You are using the third-party system interface to Central Finance for replicating nancial accounting data from

a third-party source system to the Central Finance system.

Your Central Finance system is running on SAP S/4HANA and you need to upgrade your Central Finance

system to a higher release, for example from SAP S/4HANA 1610 to SAP S/4HANA 1709, or you are

implementing a new support package which contains new functions for the third-party interface.

Deactivate SAP SLT and the Replication of Accounting Data

For the upgrade of the SAP Landscape Transformation Replication Server (SLT) content of the third-party

interface to Central Finance, please perform the steps listed below:

1. Deactivate the replication of the data from the third-party system to the SLT staging tables

The third-party system needs to stop replicating accounting data to the third-party system interface. For

this step you might want to refer to the documentation of the third-party system.

2. Deactivate the SLT replication after all documents from SLT staging tables are replicated to Central

Finance

SLT needs to stop replicating accounting documents to Central Finance. After all accounting documents

have been replicated from SLT to Central Finance, you need to deactivate the SLT replication. You can stop

the run time objects in SAP SLT.

Central Finance

P U B L I C 205

Upgrade Systems - SAP SLT and Central Finance

Upgrading SAP SLT and upgrading Central Finance can run in parallel, if required.

Upgrading SAP SLT Content - Implement new content in SAP SLT

1. Start generation report to enhance the SLT staging tables (only new elds will be appended; old data

are still in the tables)

For details on the procedure, refer to the latest SAP note for the release or support package for the third-

party system interface. For example, in release SAP S/4HANA 1909, please refer to the SAP note 2713300

or for SAP S/4HANA 1809 and SAP S/4HANA 1709, FPS2, please refer to the SAP note 2610660 or

for SAP S/4HANA 1709, FPS1, please refer to the SAP note

2527831 .

2. Apply the new SLT content

For details on the procedure, refer to the latest SAP note for the release or support package for the third-

party system interface. For example, in release SAP S/4HANA 1909, please refer to the SAP note 2713300

or for SAP S/4HANA 1809 and SAP S/4HANA 1709, FPS2, please refer to the SAP note 2610660 or

for SAP S/4HANA 1709, FPS1, please refer to the SAP note

2527831 .

3. If needed, adjust your coding which is used to map data from a third-party system to SLT staging

tables

The report for extracting data from a third-party system is provided by SAP partners. For legal reasons,

SAP does not provide programs for third-party systems. As a partner, you might need to adjust the coding

of the report that extracts data from the third-party system, and you might need to adapt the mapping

between the third-party system and the staging tables.

Upgrading Central Finance

1. You upgrade your Central Finance system running on SAP S/4HANA to the release or support package with

the newest version of the third-party interface. For details, see the Ugrade Guide under Product

Documentation for SAP S/4HANA at https://help.sap.com/s4hana.

Activate SAP SLT and the Replication of Accounting Data

1. Activate SLT replication

You can start the run time objects in SAP SLT. For example, in release SAP S/4HANA 1909, please refer to

the SAP note 2713300 or for SAP S/4HANA 1809 and SAP S/4HANA 1709, FPS2, please refer to the

SAP note 2610660 or for SAP S/4HANA 1709, FPS1, please refer to the SAP note 2527831 .

2. Activate the replication from a third-party system to SLT

You need to activate the replication of accounting data in the third-party system. For details, you might

want to refer to the documentation of the third-party system.

See Also

For more information on SAP SLT, see the guides for the SAP LT Replication Server on the SAP Help Portal at

https://help.sap.com and search for SAP HANA Real-Time Replication.

206

P U B L I C

Central Finance

1.9.1.2 Third-Party System: Posting of Reversal Documents

The third-party interface to Central Finance allows you to transfer and post reversal documents from a third-

party system to the Central Finance system.

A reversal document must have a unique reference to the reversed document in the Central Finance system:

The semantic key BKPF-AWTYP and BKPF-AWKEY must be unique. The document from the third-party system

must be recognizable as reversal document and it must contain a reversal reason.

The following table shows an example of how the reference elds in Central Finance have to be lled:

Example: How to Fill Reference Fields for Posting Reversal Documents from a Third-Party System to Central Finance

Source: Company

Code

Source: Docu

ment Number

Source: Fiscal

Year

Central Finance:

Company Code

Central Finance:

Document Num

ber

Central Finance:

Fiscal Year

F999 100000000 (re

versed document)

2017 FX02 100000098 (re

versed document)

BELNR_SENDER =

100000000

AWREF =

100000000

AWREF_REV =

9999999999

2017

F999 9999999999 (re

versal document)

2017 FX02 100000099 (re

versal document)

BELNR_SENDER =

9999999999

AWREF =

9999999999

AWREF_REV =

100000000

2017

The third-party interface uses the function BAPI_ACC_DOCUMENT_REV_POST to ensure that all references

are lled correctly and the reversal and reversed documents are linked properly one to the other.

● If no document items are transferred, that means that only the document headers are transferred, the

third-party interface reverses the documents in Central Finance by using

BAPI_ACC_DOCUMENT_REV_POST. In the Central Finance system the document is reversed.

● Otherwise the interface assumes that the reversal document items are transferred and calls

BAPI_ACC_DOCUMENT_POST. In the Central Finance system an inverse posting is made.

Central Finance

P U B L I C 207

1.9.1.3 Settings for Replication of FI Documents with more

than 999 Line Items

Settings to enable replication of FI documents with more than 999 line items from a third-party source system

to a Central Finance system and the posting of those kind of documents in the Central Finance system.

Use

You need to replicate FI documents (journal entries) with more than 999 line items from a third-party source

system to the Central Finance system via the third-party interface for Central Finance. Such kind of FI

documents are split into several documents, so that they can be transferred and posted in the Central Finance

system.

The document split is supported for outgoing invoices, incoming invoices, G/L account postings and material

movement postings.

Prerequisites

To enable the document split for the replication of FI documents with more than 999 line items, the

prerequisites mentioned in the following SAP notes apply:

● SAP Note 1353125

● SAP Note 1497092

● SAP Note 1670486

● SAP Note 2078335

 Note

Only certain types of business transactions and not all countries due to legal constraints, mostly for tax

reporting, are supported. For details, please refer to the SAP notes mentioned above.

Settings

The document split can be activated by using some Business Add-Ins (BAdIs). The following table lists the

Business Add-Ins (BAdIs) required to activate the document split for dierent business processes:

BAdIs Required to Activate Document Split

Business Process Business Activity BAdI

Outgoing Invoice SD00 FI_BILL_ISSUE_SPLIT

208 P U B L I C

Central Finance

Business Process Business Activity BAdI

Incoming Invoice

RMRP FI_INVOICE_RECEIPT_SPLIT

Generic FI Posting RFBU FI_GL_POSTING_SPLIT

Outgoing Goods Movement RMWA No BAdI required

Incoming Goods Movement RMWE No BAdI required

The documents to be replicated and posted must fulll the following criteria:

Allowed Document Structures During Document Split

Business Activity

Credit Items

(CREDITM) Debit Items (DEBITM) Tax Items (PRDTAX)

Further Attributes

SD00 Not allowed Must exist May exist SALES_OR

DER_ITEM_NO

RMRP Must exist Not allowed May exist SALES_OR

DER_ITEM_NO

RFBU Not allowed Not allowed Not allowed None

RMWA/RMWE Not allowed Not allowed May exist LOGICAL_TRANSAC

TION

● For outgoing invoices, the eld SALES_ORDER_ITEM_NO must be lled with the line item number of the

original sales order.

● For incoming invoices, the eld SALES_ORDER_ITEM_NO must be lled with the line item number of the

original purchase order. This is copied automatically during ongoing replication into the purchase order

item number.

● For goods issues and goods receipts, the credit and debit items that belong to the same material line item

must have the same value in the eld LOGICAL_TRANSACTION. This ensures that the line items

belonging together are kept together in the same FI document. Note that this eld must be lled with

numbers only.

● If taxes are calculated on line item level, the eld PRDTAX_ITEM_GROUP must have the same value in the

product lines and the corresponding tax lines. Note that this eld must be lled with numbers only.

Check, Whether FI Documents are Posted Correctly in the Central Finance

System

To display the document in the Central Finance system, you can call transaction FB03. You can get the

document number from the SAP AIF message log. Choose the List of Split Documents button to navigate to the

documents that result from the document split.

Central Finance

P U B L I C 209

1.9.1.4 Replicating CO-PA Characteristics Using the Third-

Party System Interface

Replicating journal entries with values for characteristics for Protability Analysis (CO-PA) from a source

system which is a third-party system to the Central Finance system.

Use

Journal entries, such as outgoing invoices or credit memos, which contain values for Characteristics for

Protability Analysis (CO-PA) can be replicated from a source system, which is a third-party system, to the

Central Finance system via the third-party system interface for Central Finance. Fixed characteristics and their

values, as well as customer-dened characteristics and their values can be replicated. The journal entries are

then posted in the Central Finance system with the CO-PA assignments resulting from key and value mapping.

Prerequisites

● You are using account-based protability analysis in the Central Finance (SAP S/4HANA) system.

● The characteristics you dene are stored in a eld catalog. Using the function Maintain Operating Concern,

you can select characteristics from this eld catalog to dene your operating concerns. You can access this

function in Customizing under Controlling Protability Analysis Structures Dene Operating

Concern

Maintain Operating Concern .

Features

● For account-based protability analysis, the characteristics are transferred as name and value pairs. The

used eld names must correspond to the eld names dened as characteristics for the Operating Concern.

The operating concern is determined from the company code.

● The values are mapped according to the maintained key and value mappings.

For details on mapping, please see Introduction to Data Mapping [page 37].

● If a eld name is not part of the CO-PA structure which contains the name and value pairs for

characteristics that are to be replicated, an error message is issued and the journal entry is not posted in

the Central Finance system.

To enable posting for those kind of journal entries, you can congure the error message to an information

and warning message using transaction OBA5 in the Central Finance system.

For details about the structures, including the CO-PA structure, that you need to install on the SAP LT

Replication Server, see Installing Financial Data Structures on SAP LT Replication Server [page 213].

● If you are using the material number (18 characters) in the Central Finance (SAP S/4HANA) system, the

eld name to be used for material numbers is ARTNR. If you are using long material numbers (can be up to

40 characters) in the Central Finance (SAP S/4HANA) system, you must use the eld MATERIAL_NO to

transfer the long material number.

210

P U B L I C

Central Finance

1.9.1.5 Replicating Clearing Information Using the Third-

Party System Interface

Replicating clearing information from a source system which is a third-party system to the Central Finance

system

Business Background

In the Central Finance scenario, where the source system is a third-party system, journal entries, such as

invoices and payments, can be replicated from the third-party system to the Central Finance system via the

third-party system interface to Central Finance. The journal entries are then posted in the Central Finance

system. Together with the payments, also the clearing information is transferred through ongoing replication

from a third-party source system and posted in the Central Finance system.

In the third-party system interface the clearing information is stored in the CLRITM clearing item table and the

CLEARING_DATA and INVOICE_REFERENCE elds. In the clearing item table you must always enter a

reference, for example for a payment you enter as a reference the invoice ID that should be cleared with the

respective payment. In the CLRITM clearing item table you enter by the line the relationship between items

from invoices and payments. The clearing item table must contain all open items that will be used for clearing

in the current journal entry and the reference to the open items to be cleared from other journal entries.

● If a payment is used for more than one invoice, you must enter all open items which are cleared by this

payment in the CLRITM clearing item table.

● The clearing function is only triggered when both the CLRITM clearing item table and the CLEARING_DATA

eld on header level are lled.

● For partial payments, the INVOICE_REFERENCE and INVOICE_REFERENCE_ITEM elds must be lled with

the document number and the line item number of the invoice for which partial payments were made. The

elds are available on the CREDITM structure for supplier invoices or payments and the DEBITM structure

for customer invoices or payments.

● Internally, a clearing document is created for each clearing process. When a payment is reversed, the

clearing document is also reversed, and the invoice is no longer cleared.

● It is not possible to send only clearing information without a payment, for example for payments that were

already posted. Existing open items posted previously can be cleared using the automatic clearing

program (SAPF124, transactions F.13, F13E and F13L).

Prerequisites

You have implemented SAP note 2713300 :

● For details about how the structures look like, including the CLRITM clearing item table which you need to

install on the SAP LT Replication Server, see Installing Financial Data Structures on SAP LT Replication

Server [page 213] and the Excel le attached to this SAP note.

● For details and examples on how to ll the clearing item table and elds for the dierent clearing scenarios,

please read the PDF document attached to this SAP note.

Central Finance

P U B L I C 211

Use Cases for Replicating Clearing Information Using the Third-Party System

Interface

The following use cases 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

For down payments the invoice reference is empty.

● Clearing of one invoice by partial payment

Partial payments themselves do not carry clearing information. They are cleared together with the nal

payment of the corresponding invoice. The nal payment is entered as clearing document for both the

invoice and the partial payment. Posting these documents via the third-party system interface and clearing

them after that results in an additional clearing document. The partial payment item itself is created in the

third-party system and transferred via the third-party system interface.

The invoice reference must be lled for partial payments.

● Clearing several invoices by payment with discount

● Replicating and updating clearing information for residual items

A payment with residual items clears the full amount of the original invoice and creates a new open item

with the remaining amount. This remaining amount is then cleared with the nal payment.

● Clearing by credit memo

For clearing one invoice by a credit memo a separate clearing document is created which clears the invoice

by the credit memo.

● Clearing of several invoices by one payment

If a payment is used for more than one invoice, all open items which are cleared by this payment must be

entered in the CLRITM clearing item table.

● Update of withholding tax from original invoice

When a payment is made for an invoice which is relevant for withholding tax at payment time, the

withholding tax data of the invoice is updated after the clearing document is posted. In case of missing

withholding tax information, an error is issued before the payment is posted.

Since the Central Finance system does not recalculate the withholding tax, this information must also be

part of the incoming message.

● Reverse payment and reset clearing

The payment can be reversed by sending the reversal document where all amounts have a dierent sign

than in the reversed document. In addition the object key of the document to be reversed and the reversal

reason must be entered. It is not necessary to list the clearing items, as the system will reset the clearing

automatically.

Constraints

● Central payment scenarios are not supported for third-party systems.

● Withholding tax at the time of payment is not supported. You must run the withholding tax reporting in the

third-party source system.

212

P U B L I C

Central Finance

1.9.2 Installing Financial Data Structures on SAP LT

Replication Server

This chapter includes information about how to make the staging tables available on the SAP Landscape

Transformation Replication Server (SAP LT Replication Server). The staging tables represent structures (tables

and elds) for nancial accounting data.

Implement the SAP note 2713300 to make the staging tables and elds for nancial accounting data

available on the SAP LT Replication Server. Attached to the SAP note 2713300 is an Excel le that contains the

structure of the staging tables with all elds, eld names and explanations.

The table structure for the third-party interface looks like this:

● Staging Table: Document Header (/1LT/CF_E_HEADER)

Contains the elds for the header data of the accounting document to be replicated

● Staging Table: Accounting Items (/1LT/CF_E_ACCT)

Contains the elds for the item data of the accounting document to be replicated

● Staging Table: Debitor Item (/1LT/CF_E_DEBIT)

Contains the elds for the item data of the customer document to be replicated

● Staging Table: Creditor Item (/1LT/CF_E_CREDIT)

Contains the elds for the item data of the supplier document to be replicated

● Staging Table: Product Tax Items (/1LT/CF_E_PRDTAX)

Contains the elds of product tax data to be replicated

● Staging Table: Withholding Tax Items (/1LT/CF_E_WHTAX)

Contains the elds of withholding tax data to be replicated

● Staging Table: CO-PA Characteristics (/1LT/CF_E_COPA)

Contains elds for characteristics in protability analysis (CO-PA) to be replicated

● Staging Table: Clearing Items (/1LT/CF_E_CLRITM)

Contains elds for clearing information to be replicated

● Staging Table: Withholding Tax Items Within Clearing (/1LT/CF_E_CLRWHT)

Contains elds for withholding tax information within clearing to be replicated

● Staging Table: Customer Extensibility Header (/1LT/CF_E_EXTENT)

Contains the elds to include additional customer-specic data for the journal entry header

● Staging Table: Customer Extensibility Item (/1LT/CF_E_EXT_IT)

Contains the elds to include additional customer-specic data for the journal entry item

See Also

For more information, see the guides for the SAP LT Replication Server on the SAP Help Portal at https://

help.sap.com and search for SAP HANA Real-Time Replication.

Central Finance

P U B L I C 213

1.9.3 Error Handling in SAP Application Interface Framework

(SAP AIF)

Error Correction with SAP AIF

SAP AIF allows you to distribute messages to dierent users, use alerts, and carry out reporting. For Central

Finance, details about errors are displayed in SAP AIF, in the Central Finance namespace /FINCF.

You can do the monitoring of the FI document replication and processing by using the SAP Application Interface

Framework (SAP AIF). In SAP AIF, documents are displayed which have been replicated and posted in the

Central Finance system, and there are also error messages displayed, if documents could not be posted in the

Central Finance system. This allows you to correct errors and restart the posting of the corrected documents

again.

Before you Start

● To install the SAP AIF content for the third-party interface to Central Finance, start transaction /AIF/

CONTENT_EXTRACT in the customizing client of your SAP S/4HANA system. Enter the Deployment

Scenario SAP_AIF_0026. Leave the two ags No automatic registration and Test Mode empty, that is, do

not tick them o, and execute the transaction by pressing ( F8 ).

To transport your entries to other systems, insert the entries manually into a customizing request (choose

Add Transport).

● If you want to use the transactions Interface Monitoring (/AIF/IFMON) and Monitoring and Error Handling

(Web) (/AIFX/ERR_WEB) and receive alerts via email, you must rst make the following settings:

1. Assign the business user who is responsible for analyzing errors in AIF a user based on the role

template SAP_AIF_USER. For more information about role templates, see the Master Guide for SAP

AIF on the SAP Help Portal.

2. Register the user for the scenarios that you want to analyze the errors for.

You can register for using the SAP Menu under Cross-Application Components SAP Application

Interface Framework

Administration Conguration Recipients of a User or by using

transaction /AIF/RECIPIENTS.

Enter the name of the user and create a new entry for the following:

○ Namespace: /FINCF

○ Recipient for Alert: CFIN_RECIPIENT

○ Message Type: Application Error or Technical Error

○ Select the Include on Overview Screen checkbox.

Using AIF

From the Interface Monitor (transaction /AIF/IFMON), you should see the Central Finance - /FINCF node as

the top node of the tree. You can expand this node to see the dierent interfaces including the number of

214

P U B L I C

Central Finance

messages, warnings, and errors for each of the interfaces. By clicking on the number of errors, you can

navigate to display where and when the errors occurred and when you click on a posting you can display the

error messages for that posting.

Alternatively, you can use Monitoring and Error Handling (transaction /AIF/ERR) to view the details of the error.

You can also display the message structure for the replicated document and check the values that were

replicated. In most cases, documents cannot be posted because of an invalid mapping rule, missing

Customizing, or master data. Once the mapping, Customizing, or master data is corrected the document can

be reprocessed by clicking the Restart button.

 Note

To use Emergency Correction Mode in AIF, the authorization object /AIF/EMC must be assigned to your

user.

Depending on your Customizing settings, you can also change values directly in the SAP AIF tool. If you change

values using SAP AIF, you can repost the document with the changed values by choosing Repost with user

changes.

To change values directly in Monitoring and Error Handling:

1. Press return to make the Emergency Correction check box visible and select the check box.

2. Select the message in question.

3. Select the structure in which you want to change a value, for example, for FI, the Account Document Item

Information.

4. In the structure, double-click the eld you want to change. A pop-up window is displayed in which you can

change the value.

5. Choose Save.

6. Once you have changed all required elds, choose Repost with User Changes.

 Caution

If you choose the Restart button, you discard the manual changes.

For more information on SAP AIF, see the SAP Help Portal at https://help.sap.com/aif. For information about

authorizations, see the Security Information, which is also available at the above address.

 Caution

Making changes to posting data that has been transferred from a source system to the Central Finance

system can lead to serious inconsistencies. If errors have occurred in the Central Finance system during

posting, rst check whether it is necessary to make corrections to the posting data. If the errors have been

caused by incorrect or incomplete settings (for example, for conguration or mapping of attributes),

correct these settings and then restart message processing by clicking the Restart button. If the procedure

described above is not possible and you still want to continue with the Repost with User Changes action,

you should be aware that the document will be posted as shown. Note particularly that no values will be re-

mapped or re-derived. Use this function with caution and only in an emergency, because inconsistencies

can be created easily.

Central Finance

P U B L I C 215

Error Correction with SAP LT Replication Server

Severe technical errors, for example, connectivity problems between the systems, can be found in the

application log of the SAP LT Replication Server (transaction LTRC - SAP LT Replication Server - Cockpit).

1.9.4 Conguring SAP Central Finance

The following activities are carried out in Customizing for Central Finance (transaction SPRO) under Financial

Accounting Central Finance Central Finance: Target System Settings Set Up Systems : For detailed

information about each activity, see the system documentation.

1. Activate Central Finance Business Function

The business function Central Finance (FINS_CFIN) must be activated. If the business function has not

been activated, activate it in the Switch Framework (transaction SFW5).

2. Dene Logical System for Source and Central Finance Systems

In this activity, you dene one logical system for each connected source system client and one logical

system for the receiving

Central Finance client. A logical system identies the client of the connected

source systems in the accounting documents. Also for each third-party system you dene a logical system.

3. Check Logical System Assignment for Central Finance Client

In this activity, you check the logical system assignment for the Central Finance system client.

 Note

These settings cannot be transported. When a new system is being set up, these settings must be made

after the system installation has been completed.

 Note

If you want to replicate journal entries with withholding taxes, you need to set up the Extended

Withholding Tax. You do this in Customizing (IMG:transaction SPRO) under Financial Accounting

Financial Accounting Global Settings Withholding Tax Extended Withholding Tax . The old Withholding

Tax function is not supported.

 Caution

Withholding tax postings at the time of payment are not supported in the third-party interface.

1.9.5 MDG Data Mapping

This chapter is relevant only if you do the mapping in Central Finance by using the mapping functions of SAP

Master Data Governance (SAP MDG).

For some master data entities, it is possible to use SAP MDG for key and value mapping. The mapping is called

by SAP AIF.

216

P U B L I C

Central Finance

Prerequisites

● You have dened a business system for each third-party system. You do this in Customizing (transaction

SPRO) under Financial Accounting Central Finance Central Finance: Target System Settings

Mapping Dene Technical Settings for All Involved Systems .

● You have dened mapping actions per mapping entity. You do this in Customizing (transactionSPRO) under

Financial Accounting Central Finance Central Finance: Target System Settings Mapping Dene

Mapping Actions for Mapping Entities

● You have entered key and value mapping in your Central Finance system. You do this in Customizing

(transaction SPRO) under Financial Accounting Central Finance Central Finance: Target System

Settings

Mapping Dene Key Mapping ( or Dene Value Mapping . Alternatively, you can use the

Central Finance: Manage Mappings report (transaction FINS_CFIN_MAP_MANAGE).

Mapping Entities Supported by the Third-Party System Interface

The external representation of an accounting document does not provide all mapping-relevant context

information to do a correct mapping. The missing content is derived from the Central Finance system. This

leads to a mixture of source and target mapping meta data.

The third-party system interface supports the following mapping entities and the context elds. The context

elds company code and withholding tax type are part of the source journal entries. Other context elds are

derived from the Central Finance system as shown in the table below.

 Note

For mapping of context elds, that are derived from the Central Finance system, enter the value of the

context eld in Central Finance. For example, for mapping of cost centers, the context eld is the controlling

area. You enter the value of the target controlling area for both, the source controlling area and the target

controlling area:

Wrong Mapping

Source System

Source: Controlling

Area Source: Cost Center

Target: Controlling

Area Target: Cost Center

<business system for

third-party system>

<value of the source

controlling area>

<value of the source

cost center>

<value of the target

controlling area>

<value of the target

cost center>

Correct Mapping

Source System

Source: Controlling

Area Source: Cost Center

Target: Controlling

Area Target: Cost Center

<business system for

third-party system>

<value of the target

controlling area>

<value of the source

cost center>

<value of the target

controlling area>

<value of the target

cost center>

Central Finance

P U B L I C 217

Mapping Entities Supported by Third-Party System Interface to Central Finance

Mapping Entity

Structure

(FINS_CFIN_EX...) Field Context Field

Context Field Derived

by (Field (Table))

ACTIVITY_TYPE_ID ACCTITM_AIF COST_CENTER_ACTIV

ITY_TYPE

KOKRS (Controlling

Area)

Company Code

(TKA02)

BLART DOCHEADER_AIF DOCUMENT_TYP

BUKRS ACCTITM_AIF COMP_CODE

BUKRS DOCHEADER_AIF COMP_CODE

CUSTOMER_ID ACCTITM_AIF CUSTOMER

CUSTOMER_ID DEBITM_AIF CUSTOMER_ID

COST_CENTRE_ID ACCTITM_AIF COST_CENTER

KOKRS (Controlling

Area)

Company Code

(TKA02)

DZLSCH CREDITM_AIF PAYMENT_METHOD COUNTRY

Company Code (T001)

DZLSCH DEBITM_AIF PAYMENT_METHOD COUNTRY

Company Code (T001)

GENERAL_LEDGER_AC

C_MASTER_ID

ACCTITM_AIF GL_ACCOUNT

KTOPL (Chart of Ac

counts,

COMP_CODE

Company Code (T001)

COMP_CODE is not de

rived

MATERIAL_ID ACCTITM_AIF MATERIAL_NO

MDGCO_COUNTRY_COD

ACCTITM_AIF CUSTOMER_COUNTRY

MDGCO_DISTRIBUTIO

N_CHANNEL_CD

ACCTITM_AIF DISTRIBUTION_CHAN

NEL

MDGCO_DIVISION_CO

ACCTITM_AIF DIVISION

MWSKZ ACCTITM_AIF PRDTAX_CODE

TAX_KALSM (Costing

Sheet)

Country (T005)

MWSKZ PRDTAX_CODE

TAX_KALSM (Costing

Sheet)

Country (T005)

PLANT_ID ACCTITM_AIF PLANT

PROFIT_CENTRE_ID ACCTITM_AIF PROFIT_CENTER

KOKRS (Controlling

Area)

Company Code

(TKA02)

SUPPLIER_ID VENDOR_ID

218 P U B L I C

Central Finance

Mapping Entity

Structure

(FINS_CFIN_EX...) Field Context Field

Context Field Derived

by (Field (Table))

TXJCD ACCTITM_AIF PRDTAX_JURISDICTI

ON_CODE

TAX_KALSM (Costing

Sheet)

Country (T005)

TXJCD PRDTAX_AIF PRDTAX_JURISDICTI

ON_CODE

TAX_KALSM (Costing

Sheet)

Country (T005)

WITHT WITHTAX_AIF WITHHOLDING_TAX_C

ODE

COUNTRY

Company Code (T001)

WT_WITHCD WITHTAX_AIF WITHHOLDING_TAX_C

ODE

COUNTRY,

WITHHOLDING_TAX_T

YPE

Company Code (T001)

WITHHOLDING_TAX_T

YPE

is not derived

1.9.6 Third-Party System Interface to Central Finance:

Extensibility

The staging tables of the third-party system interface represent the journal entry that should be posted to the

Central Finance system. If the structures and elds that the third-party system interface to Central Finance

oers are not sucient to post all needed information from the third-party system to the Central Finance

system, the following structures allow you to send additional information:

● FINS_CFIN_EX_EXTENSION (structure name of the SAP AIF message)

Replication of customer-specic data for the journal entry header

● FINS_CFIN_EX_EXTENSION_ITM (structure name of the SAP AIF message)

Replication of customer-specic data for the journal entry item

The extension structures contain a eld of type STRING. This allows you to transfer complex structures in one

string. The whole journal entry including the extension structure can be accessed with the BAdI: Enhance

Processing of Posting Data from Third-Party Systems (BADI_FINS_CFIN_EX_INTF). The Business Add-In

(BAdI) provides two methods which are called at dierent points in time during the Map and Post Data process:

● Method MAP_TO_BAPI

You have to implement the general availability of the SAP AIF message within the BAdI. You do this by

assigning the SAP AIF message to the instance attribute MS_LAST_AIF_DOC.

● Method FILL_BAPI_MISSING_FIELDS

Here the implementation of extension elds is made.

You can nd the BAdI in Customizing of Central Finance under Financial Accounting Central Finance

BAdIs: Central Finance . You can only process journal entries from a third-party system with this BAdI.

Central Finance

P U B L I C 219

1.9.7 SAP Central Finance Transaction Replication by

Magnitude for SAP S/4HANA

SAP Central Finance Transaction Replication by Magnitude simplies the integration of certain third-party

systems into the Central Finance scenario.

The product enables and accelerates data load, data transformation, and data consolidation from third-party

source systems into the SAP S/4HANA Central Finance system. Furthermore, it supports the reconciliation of

data between the dierent servers in the Central Finance system landscape.

The product consists of three components:

● SAP Central Finance Transaction

With this component you can continuously transfer nancial accounting transactions from third-party

source systems into SAP S/4HANA Central Finance.

● SAP Central Finance Drill-Down

This component enables the drill-down from SAP S/4HANA Finance Fiori UIs to the original transactions in

the third-party source systems.

● SAP Central Finance SyncBack

If you have implemented Central Payment, this component makes it possible to clear the original invoice in

the third-party source system for the payments that have been posted in the Central Finance system.

 Note

The data from third-party source systems is transferred via the component SAP Central Finance

Transaction Replication into the SAP Landscape Transformation Replication Server (SAP SLT) staging

tables, which are already available in the third-party interface.

Further Information

● For more information, please refer to SAP note 2879750 . In this SAP note, you can also access a link to

the Partner Product Page for SAP Central Finance Transaction Replication by Magnitude for SAP S/4HANA

where you can nd the documentation which also includes a list of the supported third-party systems.

● If you encounter problems when installing, upgrading or running SAP Central Finance Transaction

Replication by Magnitude for SAP S/4HANA, report an incident using component XX-PART-MAG-STR.

1.10 Advanced Compliance Reporting: Country/Region-

Specic Reports in Central Finance

You can use the following country/region-specic reports from advanced compliance reporting in Central

Finance.

● For more information about advanced compliance reporting, see Advanced Compliance Reporting

220

P U B L I C

Central Finance

● If you are looking for more information on authorizations for the reports listed in this document, such as

business catalogs and business role templates, which you need to access the reports, check out this table:

Country/Region-Specic Reports.

Argentina

Report Category

Description

AR_VAT_DCL

Form 731

AR_PURCHASE_VAT_DCL

Purchase VAT

Australia

Report Category

Description

AU_VAT_DCL

GST Report/BAS Reporting

Austria

Report Category

Description

AT_BOP_L1

Balance of Payments – Form L1 (Cross Border Services)

AT_VAT_DCL_U1

Annual VAT Return - U1

AT_VAT_DCL_U30

Advance VAT Return - U30

AT_ECSL_DCL

EC Sales List

Belgium

Report Category

Description

BE_VAT_DCL

VAT Return

BE_WHT_28150

Withholding Tax

BE_BOP_F01DGS

Balance of Payments - F01DGS

BE_BOP_F01MER

Balance of Payments - F01MER

BE_BOP_F02CMS

Balance of Payments - F02CMS

BE_BOP_S03CCR

Balance of Payments - S03CCR

Central Finance

P U B L I C 221

Report Category Description

BE_SL_ANNUAL

Annual Sales Listing

BE_ECSL_DCL

EC Sales List

Canada

Report Category

Description

CA_GST_HST_RITC_RETURN

Goods and Services Tax/Harmonized Sales Text (GST/HST)

CA_QST_RETURN

Quebec Sales Tax (QST)

CA_PST_BC_RETURN

Provincial Sales Tax - British Columbia (PST-BC)

CA_PST_MB_RETURN

Provincial Sales Tax - Manitoba (PST-MB)

CA_PST_SK_RETURN

Provincial Sales Tax - Saskatchewan (PST-SK)

Colombia

Report Category

Description

CO_DIAN_1001

1001 Report Format: Payments in Accounts and Tax With

holding in Source – Paid

CO_DIAN_1003

1003 Report Format: Withholding Taxes - Payable

CO_DIAN_1005

1005 Report Format: Deductible Taxes on Sales to Be Paid

CO_DIAN_1006

1006 Report Format: Generated Taxes on Sales to Be Paid

and Consumption Tax

CO_DIAN_1007

1007 Report Format: Revenues in the Year

CO_DIAN_1008

1008 Report Format: Open Items of Balance Debtors on De

cember 31st

CO_DIAN_1009

1009 Report Format: Liability Balance on December 31st

CO_VAT_DCL

VAT Declaration

Denmark

Report Category

Description

DK_ECSL_DCL

EC Sales List

DK_VAT_DCL

VAT Return

222 P U B L I C

Central Finance

Egypt

Report Category Description

EG_VAT_DCL

VAT Return

Accounting View of Logistics Information (AVL): The following

AVL are used in this report; you must congure replication

for these views:

● AVL for Supplier Invoices

● AVL for Customer Invoices

● AVL for Sales Orders

You use AVL to replicate logistics data from your source sys

tems to the Central Finance system. These data are required

for central reporting. How AVL works in Central Finance and

how you congure replication for it, you can read in Account

ing View of Logistics Information (AVL): Overview [page

144].

France

Report Category

Description

FR_WHT_DAS2

Withholding Tax

FR_INV_OVERDUE

Overdue Invoices

FR_VAT_DCL

VAT Declaration

FR_BOP_ECO

Balance of Payments - Form ECO

FR_BOP_RTE

Balance of Payments - Form RTE

FR_ECSL_DCL

EC Sales List

Indonesia

Report Category

Description

ID_CASHFLOW

Cash Flow Statements

ID_VAT_RTN

VAT Return

ID_WHT_DCL_PPH_PASAL_15

Withholding Tax (PPh Pasal 15)

ID_WHT_DCL_PPH_PASAL_22

Withholding Tax (PPh Pasal 22)

ID_WHT_DCL_PPH_PASAL_2326

Withholding Tax (PPh 23 and PPh 26)

Central Finance

P U B L I C 223

Report Category Description

ID_WHT_DCL_PPH_PASAL_4

Withholding Tax (PPh Pasal Article 4(2))

Ireland

Report Category

Description

IE_WHT_DEDUCT_SUMM

Withholding Tax

IE_ECSL_DCL

EC Sales List

IE_RTD_DCL

Return Trading Details

IE_VAT_DCL

VAT Report

Italy

Report Category

Description

IT_VAT_DCL

VAT Return

IT_WHT_DCL_CU

Withholding Tax

Japan

Report Category

Description

JP_SCBR_PAYMENT

Central Bank Payment

JP_TRADECREDIT

Trade Credit Check

JP_VAT_RETURN

VAT Return

JP_WHT_BLUERETURN

Withholding Tax using Blue Return (Invoice-Based)

JP_WHT_WHITERETURN

Withholding Tax using White Return (Payment-Based)

Malaysia

Report Category

Description

MY_GAF

GST Audit File

MY_GST_03

Goods and Services Tax Return

224 P U B L I C

Central Finance

Report Category Description

MY_SST_02

Sales and Service Tax

Mexico

Report Category

Description

MX_ACCT_AUX

Auxiliary Report for Accounts

MX_ACCT_BAL_REP

Account Balance

MX_CHTACCTS_DCL

Chart of Accounts

MX_JE_DETAILS

Journal Entries Details

Bank Data: You must use Central Payments to generate the

bank data required for the report in Central Finance.

For more information on how to use Central Payments in a

Central Finance scenario and how to congure it, you can

read

Central Payment [page 150]

Accounting View of Logistics Information (AVL): The following

AVL are used in this report; you must congure replication

for these views:

● AVL for Supplier Invoices

You use AVL to replicate logistics data from your source sys

tems to the Central Finance system. These data are required

for central reporting. How AVL works in Central Finance and

how you congure replication for it, you can read in Account

ing View of Logistics Information (AVL): Overview [page

144].

MX_VAT_DCL

DIOT Report

MX_VAT_REP

VAT Declaration

MX_WHT_37A

Withholding Tax

Netherlands

Report Category

Description

NL_ECSL_DCL

EC Sales List

NL_VAT_DCL

VAT Return

Central Finance

P U B L I C 225

Philippines

Report Category Description

PH_CAS_CDJ

CAS - Cash Disbursement Journal

PH_CAS_CRJ

CAS - Cash Receipt Journal

Ocial receipt numbers are stored in a

separate database table (PARCT) which

is not synchronized to the target sys

tem. You can use the BAdI

PH_CAS_CRJ_ITEMS in the Central Fi

nance system to fetch or derive ocial

receipt numbers in order to ll the

Ocial Receipt Number column in the

CAS - Cash Receipt Journal report.

PH_CAS_GJ

General Journal

PH_CAS_GL

General Ledger

PH_CAS_PJ

Purchase Journal

PH_CAS_SJ

Sales Journal

PH_VAT_DCL

VAT Declaration - Monthly

If the elds ANLN1 (Asset Main Num

ber) and ANLN2 (Asset Sub-Number)

in the accounting documents are

empty, then the capital goods sched

ules in the report will not work.

PH_VAT_RTN

VAT Return - Quarterly

If the elds ANLN1 (Asset Main Num

ber) and ANLN2 (Asset Sub-Number)

in the accounting documents are

empty, then the capital goods sched

ules in the report will not work.

PH_VAT_SLI

Summary List of Importations

PH_VAT_SLP

Summary List of Purchases

PH_VAT_SLS

Summary List of Sales

PH_WHT_BIR2307

Withholding Tax

226 P U B L I C

Central Finance

Poland

Report Category Description

PL_CASHFLOW_DIRECT

Cash Flow Statement

PL_ECSL_DCL

EC Sales List

PL_TRIALBAL_LINEITM_CUST

Customer Balances and Line Items

PL_TRIALBAL_LINEITM_SUPLR

Supplier Balances and Line Items

PL_TRIALBAL_LINEITM_GLACCT

G/L Account Balances and Line Items

PL_OVERDUE_INV

Overdue Invoices

PL_VAT_DCL

VAT Return

Singapore

Report Category

Description

SG_VAT_DCL

Goods and Services Tax Return

SG_WHT_IR37

Withholding Tax Data Summary for IR37/S45

South Africa

Report Category

Description

RZA_VAT_DCL

VAT Declaration

RZA_VAT_REP

VAT Returns

RZA_BBBEE_CLFN

BBBEE Supplier Classication

South Korea

Report Category

Description

KR_VAT_REP

VAT Return

KR_WHT_DCL_BUSINESS_INCOME

Withholding Tax - Business Income

KR_WHT_DCL_OTHER_INCOME

Withholding Tax - Other Income

KR_CASHFLOW

Cash Flow Statement

KR_TRIALBALANCE

Trial Balance

Central Finance

P U B L I C 227

Spain

Report Category Description

ES_WHT_DCL_M190

Withholding Tax - Modelo 190

Switzerland

Report Category

Description

CH_VAT_DCL

VAT Return

228 P U B L I C

Central Finance

Taiwan, China

Report Category Description

TW_VAT_REP

VAT

The conguration for GUI Numbering for Taiwan, China

should be the same in both the source system and the Cen

tral Finance system. As a result, the ocial number is not re

generated in the Central Finance system – it is copied from

the source system.

Exception

Prerequisite: For an outgoing invoice, the Ocial Doc.

Number is set as Generate Ocial Document Number, with

date control, in Customizing for General Application

Functions under Cross-Application Document Numbering

Taiwan, China :

● Assign Document Class to Document Type

● Assign Document Class to Billing Type and Tax Code

● Assign Document Class to Accounting Document Type

and Tax Code

Business Scenario: The user wants to merge multiple invoi

ces oine into one FI document in the system.

In this scenario, the user must manually ll in the ocial 'to

number' in the eld Payment reference of one outgoing in

voice. The system cannot automatically update the NR sta

tus in the number group conguration for the 'to number'

that the user maintained manually in the FI document. The

user must modify the NR status (the last generated number)

conguration in both the source system and the Central Fi

nance system (in Customizing for General Application

Functions

under Cross-Application Document Numbering

Taiwan, China Maintain Number Ranges ), so that the

subsequently generated number would have no eect.

Thailand

Report Category

Description

TH_CASHFLOW

Cash Flow Statements

TH_VAT_RTN

VAT Return

TH_VAT_RTN_EXD

VAT Return - Extended

Central Finance

P U B L I C 229

Report Category Description

TH_VAT_PP36

VAT Return – PP36

TH_WHT_CUST_SUMRY

Customer Withholding Tax Summary

TH_WHT_50BIS

Withholding Tax - 50BIS

TH_WHT_PND2

Withholding Tax - PND2

TH_WHT_PND3

Withholding Tax - PND3

TH_WHT_PND53

Withholding Tax - PND53

TH_WHT_PND54

Withholding Tax - PND54

United Arab Emirates

Report Category

Description

AE_VAT_DCL

VAT Declaration

AE_FAF_DCL

FAF Audit Files

Accounting View of Logistics Information (AVL): The following

AVL are used in this report; you must congure replication

for these views:

● AVL for Supplier Invoices

● AVL for Customer Invoices

You use AVL to replicate logistics data from your source sys

tems to the Central Finance system. These data are required

for central reporting. How AVL works in Central Finance and

how you congure replication for it, you can read in Account

ing View of Logistics Information (AVL): Overview [page

144].

United Kingdom

Report Category

Description

GB_WHT_CIS300

Withholding Tax

GB_ECSL_DCL

EC Sales List

GB_VAT_DCL

VAT Return

GB_RCSL

Reverse Charge Sales List

230 PU B L I C

Central Finance

1.11 Read Access Logging Congurations in Central Finance

In Read Access Logging (RAL), you can congure which read-access information to log and under which

conditions.

SAP delivers sample congurations for applications.

The application log of the initial load may contain sensitive personal data, such as bank account information.

This sample conguration logs data in order to log access to this data.

In this sample conguration, elds are logged in combination with additional elds.

Technical Name of Conguration: CFIN_INITLOAD_APPLLOG

Description: Application Log for Central Finance Initial Load

Channel: Dynpro

Fields Logged in the RAL Conguration Application Log for Central Finance Initial Load

Description

Technical Name Value

To (Date) BALHDR-ALDATE

To (Time) BALHDR-ALTIME

From (Date) BALHDR-ALDATE

From (Time) BALHDR-ALTIME

User BALHDR-ALUSER

Object BALHDR-OBJECT FINS

Subobject BALHDR-SUBOBJECT FINS_CFIN_INITLOAD

OK Code $_F_CODE

Message $_MESSAGE

Central Finance

P U B L I C 231

Important Disclaimers and Legal Information

Hyperlinks

Some links are classied by an icon and/or a mouseover text. These links provide additional information.

About the icons:

● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your

agreements with SAP) to this:

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.

● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any

damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such

links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this

information.

Beta and Other Experimental Features

Experimental features are not part of the ocially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by

SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use

the experimental features in a live operating environment or with data that has not been suciently backed up.

The purpose of experimental features is to get feedback early on, allowing customers and partners to inuence the future product accordingly. By providing your

feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example Code

Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax

and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of

example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Gender-Related Language

We try not to use gender-specic word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.

Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any

advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within

the control or responsibility of SAP.

232

P U B L I C

Central Finance

Important Disclaimers and Legal Information

Central Finance

Important Disclaimers and Legal Information

P U B L I C 233

www.sap.com/contactsap

No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP SE or an SAP

aliate company. The information contained herein may be changed

without prior notice.

Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.

National product specications may vary.

These materials are provided by SAP SE or an SAP aliate company for

informational purposes only, without representation or warranty of any

kind, and SAP or its aliated companies shall not be liable for errors or

omissions with respect to the materials. The only warranties for SAP or

SAP aliate company products and services are those that are set forth

in the express warranty statements accompanying such products and

services, if any. Nothing herein should be construed as constituting an

additional warranty.

SAP and other SAP products and services mentioned herein as well as

their respective logos are trademarks or registered trademarks of SAP

SE (or an SAP aliate company) in Germany and other countries. All

other product and service names mentioned are the trademarks of their

respective companies.

Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.

THE BEST RUN