Central Finance Configuration.pdf

Central Finance 2020
Configuration &
User Guide
SAP and other SAP products as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP
affiliate company) in Germany and other countries.
© 2021 SAP SE or an SAP affiliate company. All rights reserved.
This document is prepared by referring to the SAP Central Finance 2020 Exercise book and is
prepared as a quick reference for
Application Consultant
Development Consultant
Solution Architect
SAP and other SAP products as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP
affiliate company) in Germany and other countries.
© 2021 SAP SE or an SAP affiliate company. All rights reserved.
Prepared by Jeetendra Singh
SAP Certified – SAP S/4 Finance Consultant
SAP Certified – Central Finance Consultant

1.Set Up and Configure Central Finance
Steps Details
Check Business
Function
Activation
SPRO>SIMG>Activate Business Function
1.On the Switch Framework: Change Business Function Status screen, in the Business Function area,
select the ENTERPRISE_BUSINESS_FUNCTIONS node.
2.On the Switch Framework: Change Business Function Status screen, search for the business function
FINS_CFIN. Check if it is activated (yellow light bulb).
Check AIF
runtime
configuration
group assignment
to replication
object.
SPRO->Financial Accounting → Central Finance → Central Finance: Target System Settings → Set Up
Systems → Assign AIF Runtime Configuration Group to Replication Object.

You can specify separate runtime configuration groups for the replication objects available in central
finance (FI/CO postings, CO internal postings, and cost objects).
If no runtime configuration groups are defined in this activity, the data is processed using the default
configuration, in which a separate background job is run for each AIF message.
Check the RFC
destinations set
up for source
system.
Systems → Set up RFC Destinations for Source System.
In this activity, you check the technical parameters for RFC destinations. These parameters are used
for remote function calls (RFC) to other systems.
RFC connections are needed for the initial load of posting data from the connected source systems to
central finance, and to navigate to accounting documents in the source systems.

Define logical
system for source
system and
central finance
system.
Systems → Define Logical System for Source System and Central Finance System
In this customizing activity, you check if the logical systems are defined for the connected source
systems.

A logical system identifies the client of the connected source systems in the accounting documents.
Assign RFC
Destination for
Displaying
Objects from
Source Systems
Systems → Assign RFC Destination for Displaying Objects from Source System
In this customizing activity, you check RFC destinations to logical systems for each connected source
system.
Check the logical
system
assignment for
Systems → Check Logical System Assignment for Central Finance Client.

the central
finance client.
In this customizing activity, you check the logic system assignment for the central finance system
client.
Define Decimal
Places for
Currencies in
Source Systems
Systems → Define Decimal Places for Currencies in Source Systems
In this activity, you check the number of decimal places for currencies in the source system, and check
if they are defined differently than in the central finance system.
The number of decimal places for currencies in both the source and central finance systems, is
maintained in the IMG activity: Set Decimal Places for Currencies.
This activity is usually part of the general setup of the system.
In the standard setup, if this activity contains no settings.
This means that all currencies are assumed to have the same number of decimal places in both source
and central finance system.

2.Check the Mapping Settings
Value Mapping:
Sender systems may be configured differently, so that (Customizing) codes are not identical and need to be
mapped.
For this, value mapping can be maintained. Typical entities that fall under value mappings include the following:
Mapping Entity Descr. Global Data Type
Accounting Principle ACCOUNTING_PRINCIPLE
Document Type BLART
Posting Key BSCHL
Company Code BUKRS
Payment Method DZLSCH
Ledger Group FAGL_LDGRP
Tax procedure FINS_CFIN_TAX_KALSM
Functional Area FKBER
Grant GRANT
Business Area GSBER
Credit Control Area KKBER
Controlling Area KOKRS
Dunning Area MABER
DistributionChannelCode MDGCO_DISTRIBUTION_CHANNEL_CD
DivisionCode MDGCO_DIVISION_CODE
InventoryValuationTypeCode_V1 MDGCO_INV_VALUATION_TYPE_CD_V1
MaterialRequirementsPlanningABCClassificationCode MDGCO_MRP_ABC_CLASS_CODE
MeasureUnitCode MDGF_MEASURE_UNIT_CODE

NielsenRegionCode MDG_BP_NIELSEN_REGION_CODE
MaterialTypeCode MDG_BS_MATERIAL_TYPE_CODE
CashDiscountTermsCode MDG_FND_CASH_DISC_TERMS_CODE
IndustryClassificationSystemCode MDG_FND_IND_CLASS_SYSTEM_CODE
Tax on sales/purchases code MWSKZ
Task List Type PLNTY
Ledger RLDNR
BOM Usage STLAN
Special G/L Indicator UMSKZ
Sales Office VKBUR
Sales Group VKGRP
Steps Details
Check the
technical settings
for business
systems.
Mapping uses the term business system to identify the source systems and the central finance
system.
The business system corresponds to what you usually maintain in the system landscape directory
(SLD) of SAP NetWeaver.
SPRO->Financial Accounting → Central Finance → Central Finance: Target System Settings → Mapping
→ Define Technical Settings for All Involved Systems

Check the
mapping actions
for mapping
entities.
In this Customizing activity, you define for each mapping entity and, if necessary for each source
business system, the mapping action.
SPRO->Financial Accounting → Central Finance → Central Finance: Target System Settings → Mapping
→ Define Mapping Actions for Mapping Entities
Check code list
assignments to
elements and
systems.
For Value mapping, In this Customizing activity, you can assign code lists to elements and systems and
this is required for each global data type (GDT) that is to be mapped.
Check if value
mapping is
maintained
In this Customizing activity, you can configure mapping from system-internal code values to code
values on external code lists. The mapping is configured at field level.

The Internal Code Value column represents the target(CFIN system) value.
The External Code Value column represents the source values.

3.Configure MDG Mapping
Key Mapping:
Identifiers for instances of business objects may be different in the sender systems and the Central Finance system, making it
necessary to define mapping between these identifiers.
For example, in the sender system a customer might have the ID 4711 but in the Central Finance system the same customer has
the ID 8912. Therefore, if an invoice for this customer is to be posted into Central Finance, the system needs to translate the
customer ID in the document from 4711 to 8912.
The IDs of the following business objects are typical examples for key mappings:
Business Object Business Object ID Data Element
Activity Type Activity Type ID (ERP) LSTAR
Company Company ID VBUND
Cost Center Cost Center ID (ERP) KOSTL
Cost Element Cost Element ID (ERP) KSTAR
Customer ERP Customer Number (ERP) KUNNR
Purchasing Organization ERP Purchasing Functional Unit (ERP) EKORG
General Ledger Account General Ledger Account Master ID (ERP) SAKNR
Material Material ID (internal format) (ERP) MATNR
Tax Jurisdiction Code Tax Jurisdiction (ERP) TXJCD
Plant Plant ID (ERP) WERKS
Profit Center Profit Center ID (ERP) PRCTR
Production Version Production Version ID of Material (ERP) VERID
Sales Organization Sales Functional Unit ID VKORG
Statistical Key Figure Statistical Key Figure ID (ERP) STAGR
Vendor ERP Vendor Number LIFNR
Steps Details
Define key
mapping (ID
mapping)
SPRO-Financial Accounting → Central Finance → Central Finance: Target System Settings → Mapping
→ Define Key Mapping → Create and Edit Key Mapping

The first row is already filled in with the supplier and the system, from the Object Selection header.
In the second row, enter the source business system ID ZMECLNT800 and the vendor ID CF01. Choose
Save.

4. Use the MDG Mapping Tool
Steps Details
Generate
mapping template
In the CFIN system, enter transaction code FINS_CFIN_MAP_MANAGE in the command field
After entering the File name at the file location, press Execute (F8).
Check if the message Template for CSV file generated. You can now enter your mappings

Fill the template file:
Upload Mappings In the CFIN system, enter transaction code FINS_CFIN_MAP_MANAGE in the command field
Note the error in the test run, correct the CSV file and re-upload

Test run is successful.
Execute the update run. (Uncheck the test run)
Display mappings

Filter for the target company code CF01
Below are the list of the CF01 mapped G/L accounts from Source ZMECLNT800 to the target system.
Download
Mappings

Mapping can be downloaded using Download Mapping Option.
Delete Mappings To delete G/L accounts mapping, use CSV file with the values as per the template.

Tax Procedure
Mapping
In the target system, open transaction FINS_CFIN_MAP_MANAGE
Create a CSV file with the following details

Upload these mappings to the target system
Then can see these mappings once available in the system

5.Cost Object Framework Mapping
Steps Details
Check Cost Object
Mapping Scenario
In the CFIN; go to SPRO->IMG->Financial Accounting → Central Finance → Central Finance: Target
System Settings → Mapping → Cost Object Mapping → Define Cost Object Mapping → Define
Scenarios for Cost Object Mapping
Source Characteristics:
Central Characteristics:

Derive From Local:
The fields flagged as Derive From Source will be replicated from the source system as they are.
For the fields without the flag, the value from the mapping rule will be applied in the target system.
Derived from Source System
Indicates if a central cost object characteristic can be derived from a source cost object characteristic with
the same characteristic name.
Use
Based on the scenarios you have created for cost object mapping and which source cost object is mapped
to a central cost object, the system enters the relationship between the source cost object and the central
cost object in an assignment table.
If you have not selected this checkbox, the system determines the characteristics of the central cost object
based on the characteristic mapping table and adds the central cost object characteristic into the mapping
table.
Check mapping
rules for cost
object mapping.
In the CFIN:
Go to SPRO->IMG->Financial Accounting → Central Finance → Central Finance: Target System Settings
→ Mapping → Cost Object Mapping → Define Cost Object Mapping → Define Mapping Rules for Cost
Object Mapping Scenarios
As Derived From Local is not flagged for AUART so order type is explicitly mapped from Source to
Target.
In the CFIN:
→ Mapping → Cost Object Mapping → Define Cost Object Mapping → Define Mapping Rules for Cost
Object Mapping Scenarios

As Derived From Local is not flagged for AUART so order type is explicitly mapped for Source to Target
In the below example, order type 0450 from the source system is mapped to order type 0400 of
target system.
All internal orders with type 0450 in the source system, will be replicated in the target system with
order type 0400.
6.Smoke Test for Cost Object Mapping
Smoke Test Objective:
Simulate cost object mapping and management accounting (CO) document replication by executing the necessary checks,
without actually creating the cost object mapping or posting the CO document.
This Customizing activity is optional. It should help you to find missing Customizing and master data before the actual
transaction posting takes place.
Note: This Customizing activity should be distinguished from the activity Simulation for Initial Load, which is used for
simulation of initial load data with high data volume. This activity is not intended for initial load and handles a relatively
small number of records (999 maximum).
Requirements
You have already performed the necessary steps for cost object mapping and CO document replication, such as master data
creation and MDG settings.
Activities
1. Select source system from which you want to perform the simulation.
2. Enter maximum number of records for simulation (999 maximum).
3. Select a smoke test option, for example, Cost Object Mapping or CO Document Replication. Further selection criteria are
displayed depending on your choice of the simulation option.

o If Cost Object Mapping is selected, enter further selection criteria related to Cost Object Mapping. Note that Object
Category is mandatory.
o If CO Document Replication is selected, enter further selection criteria related to CO Document Replication. Note
that Sender Controlling Area is mandatory.
4. Specify the user who created the source system entry or the date when the entry is created, if necessary.
All the steps are to be performed in the target central finance system.
Steps Details
Smoke Test for
Cost Object
Mapping and CO
Document
Replication
→ Initial Load → Initial Load Preparation for Management Accounting → Smoke Test for Cost Object
Mapping and CO Document Replication

On the Select Cost Objects screen, select all entries and click the Replicate button in the left part of
the screen menu.

Smoke Test Result window, check the outcome with all the passed or failed cost objects.
CO Document Smoke Test

CO Document Smoke Test Result, analyze and correct the errors
7. Enhance Mapping Entities
Objective:
In this Customizing activity, you enhance and change the set of mapping entities and dependent fields.
Define Mapping Entities
If you need to map new ID types or codes you can configure a new mapping entity. Customer-defined mapping entities must start
with Y or Z.
A mapping entity defines mapping for either an object identifier or a code:

1. Define a Mapping Entity for Object Identifier Mapping
Choose New Entry to create a new line in view Define Mapping Entities. Make the following entries:
o In the Object ID field, use value help to choose the object ID you want to map.
o Mapping Entity = Object ID
Use the customer namespace Y* or Z*. (It's just a naming convention to use the Object ID here. If you use a standard Object
ID, you still need to adhere to the customer namespace for the mapping entity.)
o If the object identifier has a complex key structure, also enter the ID Field Name using the value help.
o If the object identifier has context fields, enter also ID Context 1 and, if applicable, ID Context 2 using the value help.
o Save your entries.
If you need to introduce a new Object Identifier beforehand, follow the instructions documented in Enhanced Business Mapping,
chapter Introduce a new Business Object Identifier:
2. Define a Mapping Entity for Code Mapping
Choose New Entry to create a new line in view Define Mapping Entities. Make the following entries:
o Select the appropriate Type (Data Element or Structure) from the list box.
o Enter the Global Data Type you want to map. Use the value help for your convenience.
o Mapping Entity = Global Data Type
(It's just a naming convention to use the GDT here. If you use a standard GDT, you still need to adhere to the customer
namespace for the Mapping Entity.)
If you need to introduce a new GDT for code mapping beforehand, follow the instructions documented in Enhanced Business
Mapping, chapter Introduce a new Global Data Type (GDT).
2. Define Mapped Fields (SAP System)
Here you can check the standard assignment of fields to mapping entities delivered by SAP. This view is read-only.
3. Define Mapped Fields (Customer System)
Here you can define the fields which you want to map as a mapping entity:
o Choose the mapping entity you want the field to belong to on view Define Mapping Entity.
o Enter the Structure to which the field to be mapped belongs.
o Press Enter.
o Define the Field Name of the field to be mapped.
o If required by the underlying structure, you also have to specify the Context Field 1 and, if applicable, Context Field 2.
Definitions made here override definitions delivered by SAP.
Steps Details
Define new
mapping entities.
In the CFIN System;
SPRO->IMG->Financial Accounting → Central Finance → Central Finance: Target System Settings →
Mapping → Advanced Settings → Define Mapping Entities (Enhanced Configuration)

8. Report to Check CFIN Configuration Consistency
Objective:
Compare system configuration between the source and target systems.
In this Customizing activity, you compare configuration settings in one source system and the Central Finance system,
in order to check whether these settings are consistent between the source system and the Central Finance system.
The object mapping is already completed before the comparison is carried out. The report can be run immediately or in
the background for one or more company codes.
This enables you to detect and solve inconsistencies in the configuration settings between the source and the Central
Finance system before you start the initial load or before the ongoing replication of documents starts.
Requirements
You have authorization to access the relevant configuration settings (IMG activities) in the source system.
Activities
To execute the configuration consistency check, you must specify the following data:
• one source logical system
• check groups
• source company code(s)
Note that if you leave the company code field empty, all organizations for which Central Finance is active will be
checked.
Steps Details
Compare system
configuration
between the
source and target
system
In the target CFIN system, enter transaction /NFINS_CFIN_CC

Analyze the Consistency check report related to G/L Accounts:
Analyze the Profit Center Assignment

9. Perform the Initial Load of AUFK (Cost Object)
Steps Details
Check if
SLO is
unlocked.
Use the program DMC_ANWDG_MWB_ACCESS to check the data.
On the MWB: Control access for applications screen, select the line SLO and check Workbench access = 'X':
Check if
the initial
load has
started.
Go to transaction LTRC to access the Replication Server Cockpit.(Note : If SLT server is on CFIN box LTRC
execute on CFIN box else on SLT system)

Check the
status of
AUFK
replication
1. In the SAP Easy Access Menu select SAP Menu → Cross-Application Components → SAP
Application Interface Framework → /AIF/IFMON – Interface Monitor
2. In the Error handling screen you will find all details of the replication for example errors and
success messages.

10. Check the Initial Load Settings
Objective:
The settings required for initial load of the FI/CO objects.
Steps 1 and 2 are to be performed on the target system.
Step 3 is to be done on the sender system.
Steps Details
1.Check the
logical
system
SPRO->IMG->Financial Accounting → Central Finance → Central Finance: Target System Settings → Initial
Load → Initial Load Settings → Choose logical Systems
Choose the active logical source systems for the initial load.
Central Finance uses the logical systems defined in this activity to upload data from the corresponding
source systems.
The initial load of financial postings (in contrast to the initial load of cost objects and CO postings)
does not use SAP System Landscape Transformation Server to transfer data; instead the data is retrieved
using RFC calls to the source system.
The logical system has been defined in the activity Define Logical System for Source and Central Finance
Systems.
The standard package size in this activity is 50.
Can specify for each logical system which package size is used during the initial load steps
Simulate Mapping,
Simulate Posting,
and Post Initial Load Data.
Note that you define the package size for the step Extract Data for Initial Load in the source system in the
Customizing activity General Replication Settings.

Add the systems for which you want to execute the initial load.
The initial load is performed for all systems that are configured in this activity.
In some cases, you might not want to perform the extraction of initial load data for all source systems at the same
time, but instead to perform the extraction of initial load data for each system, one system after the other. There are
two ways to do this:
• Maintain this activity for one system, perform the extraction of the initial load data, perform a delta run by
choosing Start New Run, set the Initial Load Finished indicator (in the source system in the Customizing
activity General Replication Settings), and only then maintain this activity for the next system. Make sure
that you do not start the extraction of the initial load data for the next system before the extraction of the
initial load data has been completed successfully for the preceding system.
• Configure separate initial load groups for each system. Customizing activity Define Initial Load Groups.
2.Check
clearing and
substitution
accounts.
Define the migration clearing account and the substitution accounts to be used for postings during the initial
load.
SPRO->IMG->Financial Accounting → Central Finance → Central Finance: Target System Settings → Initial
Load → Initial Load Settings → Define Clearing and Substitution Accounts
Migration Clearing Account:
Must define one migration clearing account for each company code for which postings are to be loaded into
the Central Finance system.
While balances are being posted, this account is used for offsetting postings.
Once the initial load is complete, the balance should automatically be zero.

Define Substitution Accounts
For each reconciliation account and each open item managed account you must define one substitution
account.
• In the first step of the initial load, all balances related to reconciliation accounts are transferred to
their assigned substitution accounts.
• In a second step, open items are posted to the reconciliation accounts, while the offsetting entries
are posted to the substitution account.
• Once the initial load is complete, the balances of the substitution accounts should automatically be
zero.
Instead of simply entering single accounts, you can also enter a range (from - to) of accounts. If you enter a
range, the system takes into account and substitutes all accounts within the range.
Note that the from and to accounts that you define must be in ascending order and must not overlap with
other ranges or single values.
3.Maintain
configuration
settings in
Use the maintenance view VCFIN_SOURCE_SET in the source system

the source
system.
Or follow below SPRO path
Click on New Entries:
Make the settings necessary for both the initial load of data from your source system to your Central
Finance system and for the continued replication of this data once the initial load is complete.
This activity is a prerequisite for transferring data from your system to the Central Finance system
and is where you specify the company codes for which data is transferred.
Note
You must carry out this activity in your productive system. This activity only allows so-called “current
settings”, meaning that it is not possible to transport these settings from another system.
For each company code for which you want to transfer data you define:
• The level of detail of the data that you want to transfer to the Central Finance system. You do this
by choosing a specific period and fiscal year.
• The number of periods for which the financials data should be retained in the transfer table of the
source system.

• Whether the initial load is complete.
Enter the company code for which you want to transfer data and make the following settings.
• Balances:
In the Start – Balances field, enter the year starting from which you want the system to transfer
balances. The system always takes the balances starting from the first fiscal period of that year.
• Documents:
In the Start – Documents field, enter the year starting from which you want the system to transfer
documents and in the Period – Documents field, enter the first period of that year starting from which
you want the system to transfer documents.
• When the initial load has been completed for a company code, select the Initial Load
Finished checkbox
• GL Reconciliation Checkbox:
o GL Reconciliation Postings Transferred
o In this field you define whether GL reconciliation postings triggered in CO should be
replicated to the Central Finance system during initial load.
o You should only set this flag if secondary costs are not transferred during initial load.

11. Initial Load Groups
Objective:
Initial load groups are used to separate the initial load in central finance into groups, to which you
have assigned company codes.
Steps Details
1.Define the initial
load groups.
In the Customizing
Initial Load → Initial Load Execution for Financial Accounting → Initial Load Execution for Selected
Company Codes → Define Initial Load Groups
You use initial load groups to separate the initial load in Central Finance into groups to which you
have assigned company codes.
You can carry out the initial load in the following ways:
• To execute the initial load for all maintained source systems and company codes at the same time
you do not need to use initial load groups.
• To execute the initial load for a group of company codes, you must first define initial load groups.
It is not possible to mix these methods.
If you execute an initial load using one method and afterwards decide you want to use the alternative
method you must first delete the initial load data.
Note:
A combination of logical system and company code can only be assigned to one initial load group at a
time.
Note that a combination of logical system and company code can only be assigned to one initial load
group at a time.

12.Perform an Initial Load and Trouble Shoot Errors in
FI/CO
Pre-requisite:
In the Source System: VCFIN_SOURCE_SET should be maintained for Initial Load Company code.
Loading of the CFIN_ACCHD table must be started in the SLT.
Can be achieved using Data Provisioning option in the LTRC transaction

Below diagram, Current Phase should be initial load for CFIN_ACCHD object.
All the below steps are to performed in the target system.
FINS_CFIN_LOAD_GRP_E: Execute Initial Load by Load Group
FINS_CFIN_LOAD_GRP_M: Monitor Initial Load by Load Group
Steps Details
1.Extract data for
the initial load.
This step of the initial load is a prerequisite for productive use.
It transfers the FI documents to the central finance system in intermediate database tables.
Go to SPRO->IMG->Financial Accounting → Central Finance → Central Finance: Target System
Settings → Initial Load → Initial Load Execution for Financial Accounting → Initial Load
Execution for Selected Company Codes → Execute Initial Load for Initial Load Group

1. Monitoring
Data
Extraction
Note:
Monitoring of the Execution is not possible until not run the Initial Load Extraction.

Note:
The Extracted document are stored in the table CFIN_ACCHD / CFIN_ACCIT.

2. Start Mapping
Simulation
• Mapping Simulation
This can be used to identify missing mappings before you start the actual initial load.
Nothing is posted in this step, but you can still see error messages in the initial load monitor,
as you would during the actual initial load.
Monitor mapping Simulation

2.Monitor Mapping
Simulation
To check detail of these 213 errors, double click on the 213
Click on Show Error Overview, Number of Occurrences shows, type of errors.
To check each error details, double click on each error lines, will get the details about
these errors.

3.Perform Posting
Simulation
This helps to find missing customization settings and master data before the actual postings is
performed.
Monitor Posting Simulation

3.Monitor Posting
Simulation
Execution for Selected Company Codes → Monitor Initial Load for Initial Load Group
4.Start Posting Start Posting
This step links the CO document lines and their corresponding FI document lines.
It also posts the resulting document to accounting.
The report tries to post as many documents as possible.
If there are dependencies between documents, the packages have to be executed several
times.

4. Monitor Posting
Monitor Postings:
Execution for Selected Company Codes → Monitor Initial Load Execution for Initial Load Group
Troubleshoot errors
in the Initial Load
To solve the mapping errors with respect to ERP Customer Number
Go to FINS_CFIN_MAP_MANAGE
1. Generate template file for the mapping Entity Customer_ID and the source system
ZMECLNT800

2. Upload template file with the mapping for the customer CF01
3. Display Mapping to make sure that CF01 from source system is mapped to the target
system.

4. As we can see Error are reduced from 213 to 176 by correcting one mapping error.
Similarly, we can solve other errors and successfully post all the remaining documents.
13. Compare Actual and Expected CO Posting
Steps Details
Compare
actual and
expected CO
postings
Go to
SPRO->IMG->Financial Accounting → Central Finance → Central Finance: Target System
Execution for Selected Company Codes → Compare Actual and Expected CO Postings in
Central Finance
Prerequisite:
The step of the initial load that posts documents to central finance has been completed successfully.
Objective:
After initial load of FI/CO done, compare the actual postings in management accounting (CO) with the expected
postings.
Outcome:
Compare the actual lines of the CO documents with the expected lines and, if necessary, make a manual posting in CO
equal to the difference.

14. Prepare for Initial Load of CO Postings
Objective:
The preparation steps required before the initial load of management accounting (CO) postings.
In this Customizing activity, you can complete the preparation required before the initial load of
management accounting (CO) postings takes place.
You can use this activity for the following:
1. Converting CO-PA line items and characteristics into the key-value pair structure in
the CFIN_COPA table
2. Storing references of the original documents for the reposting documents using
the RKU3 business transaction
3. Modifying the CFIN_CO_ADD table, moving elements from the COKEY table into
the CFIN_CO_ADD table
Prerequisite:
The following prerequisites must be met before this step is executed:
1. The initial load of cost objects is complete.
2. The initial load of financial accounting (FI) postings is complete.
3. You have not performed the initial load of the CO postings.
Steps Details

1.Monitor the
initial load of CO
postings.
Go to SPRO->IMG->Financial Accounting → Central Finance → Central Finance:
Target System Settings → Initial Load → Initial Load Preparation for Management
Accounting → Prepare for and Monitor the Initial Load of CO Postings
Activities
• Verify the list of source systems in which you want to perform the initial load
preparation.
• Enter the number of background jobs that run in parallel during initial load
preparation.
If you do not specify any number, the system will run a fixed number of jobs (10 jobs is
the default) in the background.
• Click the Execute Run button to start the preparation.
Depending on the status, the system performs the following activities for the logical
system:
• Not Started
The system schedules the preparation for the first time.
• Aborted
The system restarts the current aborted jobs.
• Finished and Delta Run Required
The system reschedules a delta run.
• Finished
Preparation is complete and no further action is required.
• In Process
There are jobs currently running so no further action is allowed.
• In Process and Error Occurred
There are jobs currently running so no further action is allowed.
15. Perform a Smoke Test for CO Document Replication

Objective:
Simulate management accounting (CO) document replication by executing the necessary checks, but
without actually posting the CO document.
This Customizing activity is optional. It should help you to find missing Customizing and master data
before the actual transaction posting takes place.
Note: This Customizing activity should be distinguished from the activity Simulation for Initial Load,
which is used for simulation of initial load data with high data volume. This activity is not intended
for initial load and handles a relatively small number of records (999 maximum).
Steps Details
1.Perform a
smoke test for
cost object
mapping and
CO document
replication.
Go to
Initial Load Preparation for Management Accounting → Smoke Test for Cost Object Mapping and CO
Document Replication

Can check the error here and can implement necessary steps to successfully post.
16.Perform an Initial Load of COBK
All steps are to be performed on the SLT system.
Steps Details
1.Check if
replication
objects
are
created.
a) In the SLT system, go to transaction SE38.
b) On the ABAP Editor: Initial screen, in the Program field, enter IUUC_REPL_PREDEF_OBJECTS.
In the lower section, ensure that the radio button is set to Source Code. Press Execute (F8).

2.Check if
the initial
a. Go to transaction LTRC to reach the replication server cockpit.
b. On the SAP LT Replication Server Cockpit: Overview screen, in the Mass Transfer ID field, enter
the 009.

load is
started
c. On the SAP LT Replication Server Cockpit: Overview screen, in the Configuration Name column
(which is CFIN), double-click Active (Running).
d. On the SAP LT Replication Server Cockpit CFIN (009) screen, check the Participating Objects
tab. In the lower part of the tab, verify the current status of the database tables.
Can start Initial Load/Replication by using Data Provisioning
Check status of the Initial Load/Replication in the Participating Objects tab.
e. Leave the transaction.

17. Troubleshoot Errors at the Initial Load (CO)
Objective:
After the initial load of FI postings, the initial load of CO-internal postings can be run. This activity is
performed via SLT, and the basis of replication is the COBK/COEP tables.
You use monitoring and error handling to get a structured overview of the messages that are
generated during data processing in the SAP Application Interface Framework.
Steps Details
Post a CO
Document
1. In the source system, go to: Accounting → Controlling → Cost Center Accounting → Actual
Postings → Manual Reposting of Costs or enter transaction KB11N.
2. On the Set Controlling Area screen, enter the value 1000.
3. On the Enter manual reposting of primary costs screen, enter the information from the
table above.
4. Note the number of the document created.
2.Prepare for
monitoring
In the target system, navigate to: SAP Easy Access → Cross-Application Components → SAP Application
Interface Framework → /AIF/ERR – Monitor and Error Handling or transaction /n/AIF/ERR

and error
handling the
initial load of
CO postings.
3.Create
Missing Cost
Center
In the target system, go to accounting → Controlling → Cost Center Accounting → Master Data → Cost
Center → Individual Processing → Create.
Alternatively, you could use the transaction KS01 to perform this task.

4.Check the
AIF monitor.
In the target system, again navigate to: SAP Easy Access → Cross-Application Components →
SAP Application Interface Framework → /AIF/ERR – Monitor and Error Handling or transaction /n/AIF/ERR

Finally, CO Document is posted successfully:
18.Execute Comparison and Reconciliation Reports
Objective:
The reconciliation reports that need to be executed after the initial load.
There are FI Reports and CO Reports.
These reports are run on the target system.
Steps Details
1.Comparison of FI
Document
Headers
Program FINS_CFIN_DFV_FI_DOC_COUNT to perform the comparison.
This report displays, for a specified company code, fiscal year, and posting date in the
source system:
• Total number of financial accounting documents posted in the source system
• Total number posted in the Central Finance system
• Number of journal entries with errors

• Number of journal entries which can be displayed in the error correction tool
(AIF)
You execute this report in the Central Finance system and can use it to check whether all
journal entries from the source system have been posted in the Central Finance system
2.Comparison of FI
Balances
Use the report FINS_CFIN_DFV_FI_BAL_COMPARE.
This report shows the debit balance, the credit balance, the balances total, and the
currencies of your general ledger (G/L) accounts in the source system, and in the Central
Finance system, for a specified fiscal year or posting period.
You execute this report in the Central Finance system and can use it to check whether
G/L account balances in the source system match the corresponding balances in the
Central Finance system.
The report compares the debit and credit amounts for selected G/L accounts in a
selected period of time and displays the following for each G/L account and month:
• Debit amount
• Credit amount
• Account balanced
Note:
The report works best if you restrict the selection as much as possible. In this case you
need to tick the Shows Errors Only field.

If you don’t chose this option, you can decide whether you want to see also the rows
with zero balances or not by ticking the Accounts with zero balance field.
3.Comparison of FI
Line Items
Use the program FINS_CFIN_DFV_FI_DOC_COMPARE to perform the comparison.
Note:
You use this report to compare line items on your general ledger (G/L) accounts in the
source system with line items on your G/L accounts in the Central Finance system for a
selected period of time.
You execute this report in the Central Finance system and can use it to check whether all
line items for selected general ledger (G/L) accounts in the source system and the Central
Finance system total the same amount.
The report displays details of the line items in the source system and the Central Finance
system, such as the document number, fiscal, year, G/L account, currency, and reference
key.
Note:
The report lists the details of the line item in the source system and Central Finance
system, such as the document number, fiscal year, G/L account, amount, currency, and
reference key, for the selected fiscal year or posting period.

4.Comparison of
CO Documents
Header
Program FINS_CFIN_DFV_CO_DOC_COUNT
5. Comparison of
CO Balances
Program FINS_CFIN_DFV_CO_BAL_COMPARE
6.Comparison of
CO Line Items
Program FINS_CFIN_DFV_CO_DOC_COMPARE
19.Check Real-Time Replication Settings
Objective:
Check if the real time replication settings in the source and target systems.
Steps Details
1.Check
Initial Load
Finished
Indicator for
FICO
replication
Enter SM30 in the sender system command filed
and enter maintenance view VCFIN_SOURCE_SET.
Set the indicator Initial Load Finished for the company code CF01 for current year.
Verify the status in Current action for the line with database table AUFK on the Overview tab
Table at SAP LT Replication Server Cockpit: CFIN (009).
2.Cost
Object AUFK
Replication
SAP LT replication server cockpit is needed to perform this task.
Choose the LTRC transaction for replication server cockpit and use the Mass Transfer ID 009

Verify the status in Current action for the line with database table AUFK on the Overview tab
3.COBK
replication
SAP LT replication server cockpit is needed to perform this task.
Choose the LTRC transaction for replication server cockpit and use the Mass Transfer ID 009
Verify the status in Current action for the line with database table COBK on the Overview tab
20. Check Real-Time Replication of a Cost Object
Objective:
The real time replication of the cost objects. The cost object used is Internal Order.
Steps Details
1.Create an Internal
Order in the source
system
In the source system navigate to
SAP Easy Access->Accounting->Controlling->Internal Orders->Special Functions-> KO01 - Create

2.Check the real Time
replication in the Target
System
In the target system, SAP Easy Access → Cross-Application Components → SAP Application
Interface Framework → /AIF/IFMON – Interface Monitor
On the /AIF/IFMON look for CO_OBJ/1 and click the checkered flag in the Success column

Can notice that the internal order 400258 is successfully replicated to the target system.
After clicking we get details of the target internal order created from the source
object.
Go to Target system, SAP Easy Access → Accounting → Controlling → Internal Orders → Master
Data → Special Functions → Order → KO03 Display
Enter Internal order 400053 and see the Order Type.
As defined in the Cost Object mapping framework Source order type 0450 is mapped to 0400
order type.

21. Check Real-Time Replication of a FI Document
Objective:
To check how FI document is replicated from the source system to the target system in real-time.
Steps Details
1.Post a
vendor
invoice in the
Source
System
In the source system; navigate to
SAP Easy Access → Accounting → Financial Accounting → Accounts Payable → Document Entry → FB60
— Invoice

2.Check the
replication
status in AIF
In the target system; navigate to
SAP Easy Access → Cross-Application Components → SAP Application Interface Framework →
/AIF/IFMON – Interface Monitor
Or transaction /AIF/IFMON
Look up the line Accounting Document – AC_DOC/2 and click the checkered flag in column Success.
Document CF01 1900000016 2022 posted successfully

Main point to notice is whether the G/L accounts are correctly mapped or not.
FINS_CFIN_MAP_MANAGE for the G/L accounts
Source document:
Target Document:

22.Check Real-Time Replication of CO Documents
Steps Details
1.Post a CO document In the source system, navigate to:
SAP Easy Access → Accounting → Controlling → Cost Center Accounting → Actual Postings →
Manual Reposting of Costs → KB11N
2.Check the replication
status in AIF
In the target system, navigate to:
SAP Easy Access → Cross-Application Interface Framework → SAP Application Interface
Framework → /AIF/IFMON – Interface Monitor
Look up the line Controlling Document – CO_DOC/1 and click the checkered flag in Success

Carefully readd the log message:
Source management accounting doc: 0200159741
Target Management accounting doc: 0200007807
Target financial accounting doc: 2300000001
KB13N in the target:
Financial accounting document type is 'CO'
23. Reverse and Repost
Steps Details
1.Post a
Vendor
Invoice
In the Source System, navigate to
SAP Easy Access Menu → Accounting → Financial Accounting → Accounts Payable → Document entry →
FB60 - Invoice

2.Check
the
replication
status in
AIF
In the target system, navigate to
SAP Easy Access Menu → Cross-Application Interface Framework → SAP Application Interface Framework →
/AIF/IFMON – Interface Monitor
Click on the successful entries

Replicated document in the target system is CF01 1900000017 2022
3.Check
the
replicated
document
in the
target
In the target system, go to
SAP Easy Access → Accounting → Financial Accounting → General Ledger → Document → Display or
transaction FB03
Check the document header. You can view information about the source (sender) document on the lower
part of this window.
Check the reprocessing status code in the Header. It should be empty.
Check the cost centre in the line item. It should be CF01_C1.
4.Check
the
existing
mapping
and
change the
key
mapping
This step is about the mapping that must be changed so that you can post accounting documents from
sender systems to the Central Finance system with the right objects.
If identifiers for instances of business objects are different in the sender systems than in the target system,
you must define the mapping between these identifiers.
In the target system, enter transaction SPRO and
go to Financial Accounting → Central Finance → Mapping → Define Key Mapping → Create and Edit Key
Mapping
Or transaction MDG_KM_MAINTAIN in the command field.

Create Key Mapping
5.Run the
program
to
reverse in
target
In the target system, enter transaction FINS_CFIN_CREV.
Alternatively, you can use program RFINS_CFIN_REVERSAL_REPOST .

Check if reversible is possible for the poste documents, reversal possible filed should contain yes
6.Reverse
and
repost
Click Execute F8

Select the line related to your document and click Execute.
You will notice that the status changes from Reversal possible to No and the message stating the following is
displayed: Reversal and reposting initiated; AIF message created.
A batch job is now scheduled.
Message similar to this is displayed: Job /AIF/FINCF_ZCF_00000000XX HHMMSSSS release for run
0000000XXk
7.Check
the new
posted
document
status in
AIF
SAP Easy Access → Cross-Application Interface Framework → /AIF/IFMON – Interface Monitor
CF01 1900000018 2022 is the reversed document and CF01 1900000019 2022 is the reversed document
posted for the source document CF01 1900000001 2022

Reference document confirms this
8.Check
the
reversed
and the
new
posted
document
in Central
Finance
Reverse document 1900000018 2022 via FB03.
Cost center is CF01_C1
Reposted document 1900000019 2022 via FB03

Header status of the initial posted document 1900000017 2022 in CF01
9.Incorrect
mapping is
done in
the above
steps
Source controlling area is 1000 not A000.
So need to correct this mapping in the target transaction MDG_KM_MAINTAIN
Now correct mapping is updated

Now go to Transaction
FINS_CFIN_CREV
Check whether the reverse and repost of the incorrect document 1900000019 2022 CF01 is allowed or not

Check the AIF/IFMON
Reversed document
Reposted Document
FB03:
Reversed doc 1900000020 2022 with incorrect mapped cost center

Reposted doc: 1900000021 2022
Correct Cost center is updated as per the new mapping in the target system.
24. Set Up CO-PA and Replication of Source CO-PA
Document
Steps Details
1.Validate CO-PA
configuration in
source system
In the source system, identify the controlling area and operating concern that are assigned to your
company code

In the SPRO, IMG
Enterprise Structure → Definition → Financial Accounting → Edit → Copy → Delete, Check Company
Code
Or transaction EC01

2.Validate the CO-
PA configuration
in the target
system
In the target system, identify the controlling area and operating concern that are assigned to your
company code
In the SPRO, IMG
Enterprise Structure → Definition → Financial Accounting → Edit → Copy → Delete, Check Company
Code
Or transaction EC01

3.Display CO-PA
characteristics
and Value fields
in the Source
System
In the Source system,
SPRO->IMG-> Controlling → Profitability Analysis → Structures → Define Operating Concern →
Maintain Operating Concern
Or Transaction KEA0
You may find differences between characteristics defined in the source system and the Central Finance
system. This is because it is possible that not all characteristics from the source system are relevant in
the Central Finance system.

4.Display CO-PA
characteristics
and Value fields
in the target
system
In the target system,
SPRO->IMG-> Controlling → Profitability Analysis → Structures → Define Operating Concern →
Maintain Operating Concern
Or Transaction KEA0

5.Validate CO-
PA
Characteristics
mapped in the
Target System
To define CO-PA mapping in the target system, navigate to
SPRO->IMG->Financial Accounting → Central Finance → Central Finance Target System Settings →
Mapping → CO-PA Mapping → Define CO-PA Mapping

6.Post FI
document with
the CO-PA
characteristics
1.Post FI customer invoice in the source system
Transaction FB70

Double Click on Profit Center to enter Profit Segment Data

2.Post Cost of Sales through Financial Accounting in the source system
Transaction FB50

3.Display the document in the AIF on the central finance system
Error in the CFIN system

To solve this error, follow below IMG path or Transaction KEKE
Click on Restart to reprocess the Error messages in /AIF/IFMON

Error is corrected with the below details
To get new document posted in the target system, pass source system posted document as reference
document in the ACDOCA table in the CFIN system
In target system source accounting document are replicated as 1800000004 and 0100000004
document number.
Use FB03 to check Profitability segment characteristics for each of the documents and with this
validate the CO-PA mappings.

25. Set up and Configure Central Payments
Steps Details
1.Create
the House
Bank for
Central
Payment's
company
code.
In the target system enter FBZP transaction code and create House Bank for the company code CF00
Steps Details

Click on Bank Accounts
Bank Account is created

2.Tax
Consistency
Check
Activation
In the target system, check tax code activation for the company code CF00.
Navigate to SPRO->IMG->Financial Accounting → Financial Accounting → Central Finance → Central
Finance: Target System Settings → Set Up Systems ->Settings for Accounting Document Replication→
Activate Tax Consistency Check for Company Codes

Note:
Once you activate the tax consistency check system will ask for following tables to be loaded to the
system:
• FINS_CFIN_T000F
• FINS_CFIN_T001
• FINS_CFIN_T005
• FINS_CFIN_T007A
• FINS_CFIN_T007B
• FINS_CFIN_TTXD
To update these tables in the target, the objects must be loaded in SLT and left in replication.
3.Central
Payment
Activation
In the Target system proceed with the Central Payment activation for the company CF00
you specify the company codes in source systems for which you want to activate central payment
Navigate to
SPRO->IMG->Financial Accounting → Financial Accounting → Central Finance → Central Finance: Target System Settings → Central
Payment → Activate Central Payment for Company Codes

Make a note that as we activate the Central Payment for the Source system,
all open items are technically cleared in the source and so we need to ensure that relevant items are open
in the target system.

Error:
Resolve:
In the Source system , go to transaction CFINIMG( Central Finance Customization Menu)
Enter the company code CF00 in the General settings.

Now in the target system, Central Payment activation is successful.
4.Activate
Clearing
Transfer for
Source
Systems
In the target system execute the Activate Clearing Transfer for Source Systems.
With this activity we can activate the transfer of clearings from one or more logical sender systems to your
Central Finance system.
But before activating this , we should be aware of the restriction described in the SAP note 2292043 and
make sure SAP Note 2633841 is installed
in all the source systems for which you want to activate clearing transfer.

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
Navigate to :
SPRO->IMG->Accounting → Central Finance → Central Finance: Target System Settings → Clearing
Transfers → Activate Clearing Transfer for Source Systems

To see whether clearing transfer is active for a logical sender system,
go to the activity Maintain RFC Assignments and Settings for Source Systems and check the status in the
column Clearing Transfer.
If you have activated clearing transfer by mistake, you can deactivate it in the
transaction FINS_CFIN_DEACT_CLR.
5.Reopen
Technically
Cleared
Items
Can reopen items which have been technically cleared in the target system but which are still open in the
source system.
The system only reopens items from logical sender systems for which you have activated clearing transfer
in the activity Activate Clearing Transfer.
Note:
You do not have to carry out this activity if you have not yet executed an initial load because no documents
will have been posted.
SPRO->IMG->Financial Accounting → Central Finance → Central Finance: Target System Settings → Clearing
Transfers → Reopen Technically Cleared Items
Or transaction FINS_MIG_CJ3

6.Monitor
the
reopening
of
technically
cleared
items
Monitor whether the activity Reopen Technically Cleared Items has successfully processed all relevant
documents.
In the target system go to:
SPRO->IMG->Financial Accounting → Central Finance → Central Finance: Target System Settings → Clearing
Transfers → Reopen Technically Cleared Items
Or Transaction FINS_MIG_MONITOR_CJ3
26. Real Time Replication and Payment of a Vendor
Invoice in the Target System
Steps Details

1.Post a
Vendor
Invoice
In the source System, use Transaction FB60 - Vendor Invoice Postings
2.Check the
replication
status in AIF
Go to Transaction /AIF/IFMON in the target system, click on the success checker flag
And note down the document number posted successfully
Maintain Mapping
Click on Restart

Error solved
Click on the checkered flag to see successfully posted documents
3.Check the
replicated
document in
the target
system
In the target system
Transaction FB03 or SAP Easy Access->Accounting → Financial Accounting → General Ledger → Document
→ Display
4.Check if
the
document is
cleared in
the source
system
In the source system ,
go to FB03 transactions or SAP Easy Access->Accounting → Financial Accounting → General Ledger →
Document → Display

Double click on the vendor line item to see the clearing status:
clearing status is cleared with the ALE-extern legend
5.Create a
payment
proposal in
the target
system
In the target system go to ;
SAP Easy Access->Accounting → Financial Accounting → Accounts Payable → Periodic Processing → F110 –
Payments
Enter Parameters

Click in Status tab and save the data first
Click on the Proposal button

6.Execute
the payment
proposal
Execute the payment by clicking the Payment Run button on the top left menu on the page

7.Check the
vendor
account
FBL1N

We can see that vendor CF08 is cleared in the target system. And clearing is done by the payment
document: 2000000000
27. Real-Time Replication and Clearing of a Customer
Invoice in the Target System
Steps Details
1.Post a
Customer
Invoice
In the source System, use Transaction FB70 - Customer Invoice Postings
or SAP Easy Access->Accounting → Financial Accounting → Accounts Receivable → Document
entry → FB70 – Invoice

2.Check
the
replication
status in
AIF
Go to Transaction /AIF/IFMON in the target system, click on the success checker flag
And note down the document number posted successfully.
If error, analyze the error and implement relevant solution(s).

Maintain Mapping
Click on Restart
Error solved

Click on the checkered flag to see successfully posted documents
3.Check
the
replicated
document
in the
target
system
Transaction FB03 or SAP Easy Access->Accounting → Financial Accounting → General Ledger →
Document → Display
You can analyze the sender document details also.
4.Check if
the
document
is cleared
in the
source
system
In the source system ,
go to FB03 transactions or SAP Easy Access->Accounting → Financial Accounting → General
Ledger → Document → Display

Double click on the customer line item to see the clearing status:
clearing status is cleared with the ALE-extern legend
5.Clear
the
customer
invoice in
the target
system
In the target system go to ;
SAP Easy Access->Accounting → Financial Accounting → Accounts Receivable → Document entry
→ F-28 – Incoming Payments
Enter Relevant data; than Click on Process Open Items

If the line items appear active (The account balance amount is not assigned), click Select All Items
and the deactivate all items.
Select the invoice to be paid and click Activate.
The not assigned amount should be zero

Click on Post,
6.Check
the
Customer
account
In the target system,
Enter Transaction FBL5N or
SAP EASY Access->Accounting → Financial Accounting → Accounts Receivable → Account →
FBL5N - Display/Change Line Items

We can see that customer CF08 is cleared in the target system. And clearing is done by the
incoming payment document: 1400000000
28. 3rd-Party SLT Load/Replication Procedure
Steps Details
1.Load
3rd-Party
Documents
and enable
Replication
In the SLT system , use Transaction LTRC - SAP LT Replication Server Cockpit
Click Mass Transfer 00G – CFIN_3P (Central Finance 3rd-Party Interface).

Default Tab = Participating Objects.
Click Data Provisioning Button and enter table name /1LT/CF_E_HEADER.
Select Radio button Start Replication and Click Continue.

2.Monitor
Table Load
until
complete
Remain in Participating Objects tab & Click Refresh Entries (F8) button periodically until
Current Phase = Replication &
Details = Waiting for Changes.
3.Confirm
3rd-Party
Documents
transfer to
AIF
open Transaction /n/AIF/IFMON, expand node Central Finance - /FINCF
and confirm entries exist for Interface Accounting Document - External Interface - AC_DOC_EX/2
We can check the error and successfully posted entries

4.Check
the newly
posted
document
in Central
Finance
In the CFIN system, FB03 or go to
SAP Easy Access → Accounting → Financial Accounting → General Ledger → Document → Display
Check the document header.
You can see information about the source (sender) document on the lower part of this window.
Fields are Sender Log Sys. and Sender Doc.No.

29. Setup Transaction Replication from 3rd Party
Systems
Background
With Central Finance, you can also integrate third-party systems into your system landscape.
The corresponding journal entries from third-party systems are then replicated via the following
third-party system interfaces.
The process is carried out in 2 steps:
As part of the first step, data is extracted from a third-party system and the staging tables are
populated in SLT.
In the next step, the staged data is then passed on the CFIN accounting interface and lands up in AIF.
Customers are responsible for extracting data from a third-party system and filling the staging tables
in SLT.
Steps Details
1.
Validate Data
in Staging
Tables for
Third-Party
System
Validate the data in the staging tables for the third-party system in the Central Finance system.
Check the contents of the /1LT/CF_E_* tables.
Below are the list of 3rd Party staging tables:
Table
1. /1LT/CF_E_HEADER
2. /1LT/CF_E_ACCT
3. /1LT/CF_E_DEBIT
4. /1LT/CF_E_CREDIT
5. /1LT/CF_E_PRDTAX
6. /1LT/CF_E_WHTAX
7. /1LT/CF_E_COPA
8. /1LT/CF_E_CLRITM
9. /1LT/CF_E_CLRWHT
10. /1LT/CF_E_EXTENT
11. /1LT/CF_E_EXT_IT
Check the data of the header table: /1LT/CF_E_HEADER

2.
Check the
mapping
action and
mappings
maintained
for G/L
accounts
between
source and
target
systems.
In the CFIN system,
Go To
SPRO->Financial Accounting → Central Finance → Central Finance: Target System Settings →
Mapping → Define Mapping Actions for Mapping Entities

Now via transaction code: /nFINS_CFIN_MAP_MANAGE
30. Setup Transaction Replication for Purchasing Base
Logistic Data
Background
Accounting View of Logistics ( AVL) Information is used to replicate logistics data from your source
systems to Central Finance system via SLT.
A defined subset of logistics information is replicated from a source system to the dedicated tables
of Central Finance system.
In addition to sales orders and customer invoices, replication of pricing documents (only for sales
order) and supplier invoices in AVL scenario is supported.
Below is list of business documents replicated from source to target system through AVL
• Purchase Order
• Supplier Invoice
• Sales Order

• Customer Invoice
This data is required in order to carry out operations and reporting in the Central Finance system.
Note:
Please note AVL allow to replicate Purchase Order and associate Invoice to specific Table meant for
AVL only (Mention below).
AVL will not populate Logistic Document in actual Logistic Table in Central Finance System for e.g.,
Purchase Order replicate to CFIN_AV_PO_ROOT not EKKO in Target System.
Some of business process in Central Finance System require underlying logistic data for e.g., SAP
Document and Compliance Reporting, Central Accrual Management. AVL method replicate logistic
data (e.g., PO, IR) to specific table to support above process
AVL provides a platform to consume logistic data even though the Target S/4 HANA system does not
have complete logistic modules.
Solutions like Document and compliance reporting, Central Accrual engine rely on AVL data for
further reporting including logistic elements.
AVL logistic documents can only be replicated in certain specific cases e.g. a Purchase Order which is
invoiced can only be replicated through AVL
Following tables are involved in Central Finance for AVL
Replicated Business Object AVL Table in Central Finance Source System Table
AVL Purchasing Document CFIN_AV_PO_ACC EKKN
CFIN_AV_PO_ITEM EKPO
CFIN_AV_PO_RO EKBE
CFIN_AV_PO_ROACC EKBE_MA
CFIN_AV_PO_ROOT EKKO
CFIN_AV_PO_SCH EKET
AVL Supplier Invoice
CFIN_AV_SI_ACCAS RBCO
CFIN_AV_SI_GLACC RBCO
CFIN_AV_SI_ITEM RSEG
CFIN_AV_SI_ROOT RBKP

Steps Details
1.
Create a Purchase
Order (PO) in the
source system
In the source SAP system, create a PO using ME21N transaction code for company code CFAV
Standard PO NB created under the number 4500017236
2.
Create Goods
receipt
To perform this step in the source system, go to
SAP Easy Access → SAP Menu → Logistics → Material Management → Inventory Management →
Goods Movement → Goods Receipt → For Purchase Order or transaction code MIGO
Use PO created in the step1 above with storage location Z001.
Material document 5000000010 posted

3.
Create Invoice
Receipt
In the source system go to ,
SAP Easy Access → SAP Menu → Logistics → Material Management → Logistic Invoice Verification →
Document Entry → Enter Invoice
Or MIRO
For the PO number 4500017236 and storage Location Z001 do the Invoice Receipt
Document no. 5105608732 created
4.
Display Documents
in AIF
In the CFIN System,
navigate to SAP Easy Access → Cross-Application Components → SAP Applicaction Interface
Framework → Interface Monitor
Or /n/AIF/IFMON
Look up the line Accounting View of Purchase Order - AV_PO/1
and click the checkered flag in the column Success to check the replicated document in Central
Finance.

Validate the source PO values in the document
To validate Invoice, Accounting View of Supplier Invoice - AV_SI/1
Source supplier Invoice 5105608732 is replicated
5. In the CFIN system, enter the transaction FINS_CFIN_DFV_AV_PO
Enter the source system PO and Logical system details.

Check the posted
Purchase Order
6.
Check the posted
Supplier Invoice
In the CFIN system,
Enter the transaction FINS_CFIN_DFV_AV_SI

Central Finance Configuration.pdf

Central Finance Configuration.pdf

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (20)

Semelhante a Central Finance Configuration.pdf

Semelhante a Central Finance Configuration.pdf (20)

Último

Último (20)

Central Finance Configuration.pdf