Introduction to SAP Central Finance Transaction Replication by insightsoftware for SAP S/4HANA

This topic introduces the key components of SAP Central Finance Transaction Replication by insightsoftware for SAP S/4HANA or Transaction Replication and associated concepts.

This topic introduces reconciliation reports and their related concepts.

Transaction

SAP Central Finance Transaction Replication by insightsoftware for SAP S/4HANA provides Transaction, a pre-built adapter. This adapter transfers and consolidates financial accounting transactions from third-party source systems into SAP S/4HANA. The system runs this process continuously.

You can also use Transaction to transfer General Ledger account, customer, and vendor balances from your source systems into SAP S/4HANA. The system bases these transfers on your company's accounting period.

Transaction provides five levels of Reconciliation reports. You can access these reports through SAP Fiori or SAP Analysis for Microsoft Office.

Drilldown

Drilldown is a pre-built adapter provided by SAP Central Finance Transaction Replication by insightsoftware for SAP S/4HANA that seamlessly transfers operational data from your source systems to the staging database, allowing you to access detailed source-specific information directly from SAP S/4HANA. This operational data encompasses sales orders, purchase orders, goods receipts, customer invoices, vendor invoices, and general ledger transactions.

SyncBack

SyncBack is a pre-built adapter provided by SAP Central Finance Transaction Replication by insightsoftware for SAP S/4HANA that automatically synchronizes payment data when the Central Payment feature is enabled. When payments are created for invoices in SAP S/4HANA, SyncBack automatically generates corresponding vendor payments and customer receipts, then applies them to the appropriate invoices in your source system.

Reconciliation Reports

Reconciliation reports provide information about changes to your transaction data. These changes occur as data moves through the stages of replication and transformation from a source system to SAP S/4HANA through SAP Central Finance Transaction Replication by insightsoftware for SAP S/4HANA. These reports help you identify the stage that contains incorrect or missing data that requires reconciliation.

Accounting Views of Logistics

Accounting Views of Logistics (AVL) refers to the set of views that the system creates to replicate logistics data from your source system into SAP S/4HANA. These accounting views help you carry out operations and reporting in the Central Finance system.

The system currently supports AVL for the following features:

• Customer Invoice (CI)
• Sales Order (SO)
• Purchase Order (PO)
• Supplier Invoice (SI)
• Goods Receipt Note (GRN) (Flat File Data only)

System Architecture

The architecture diagram shows the data flow for Transaction, Drilldown, SyncBack, Reconciliation, and AVL.

System Architecture (Cloud):

The following architecture diagram shows how Microsoft Dynamics 365 Finance and Operations functions as a source system.

Architecture Components

• ERP: The source systems or flat files that contain the financial transaction data.
• CDC: The schema that contains the change data capture (CDC)-related objects, such as the CDC tables. This schema resides in the same database as the source system. The system uses this schema to:
  • Store source-specific scripts related to extraction views with some validations
  • Capture incremental changes to the financial transaction data in your source system
  • Store staging tables to capture the invoices and corresponding payment information in SAP S/4HANA for SyncBack

  For information about the change data capture process, see CDC Process in Appendix F: Miscellaneous Tasks.

• SAP Data Services: The tool that helps you extract the source data from your source system, transform the data, and load it into the staging database.
• DMF and Azure SQL Database: You need the DMF to export the Transaction data and Master Data into Azure SQL Database. The system loads the exported data from here into the staging database.
• Staging Database: The staging database that contains two sets of staging tables for data processing. The system loads data from multiple source systems into initial staging tables, then performs document and large amount splitting before moving the data to FIN% tables for Transaction data replication and CF_E% tables for AVL data replication. These FIN% and CF_E% tables correspond to the SAP Landscape Transformation (SLT) Replication Server interface tables. The system performs final validations on these tables before data transfer. For information about the validations, seeTransaction Validations in Appendix F: Miscellaneous Tasks.
• SLT Replication Server: The SLT Replication Server to which the system loads data from the FIN% tables or the CF_E% tables in the staging database. For information about how to configure the SLT Replication Server tables for third-party systems, see SAP Help Portal.
• SAP S/4HANA: The Central Finance-enabled SAP system. For information about SAP S/4HANA, see the SAP S/4HANA documentation.
• ABAP Component: The ABAP component in SAP S/4HANA that imports the Drilldown and Reconciliation objects into SAP S/4HANA. The component includes SAP Fiori apps and Core Data Services (CDS) views.
• MTA Application: The MTA application deployed in the SAP HANA database through SAP HDI. The application helps create the database objects, such as schemas, views, and virtual tables, in the SAP HANA database. The virtual tables point to the data in the staging database through Smart Data Access (SDA).
• SyncBack: The SyncBack component that you can use to fully or partially clear the open customer/vendor invoices in your source system, if Central Payment is enabled.
• Reconciliation Levels: The various levels of Reconciliation reports that compare the transaction data during the various stages of transformation from your source system through SAP S/4HANA. The levels include:
  • Level 0: The report compares the raw source business documents with the final Central Finance results.
  • Level 1: The report shows how the source data moves to a set of initial staging tables in Stage 1 of the staging database with minimal transformations.
  • Level 2: The reports display how the data in the initial staging tables in Stage 1 of the staging database transforms and moves into the FIN% tables in the staging database.
  • Level 3: The reports compare the data in the FIN% tables and the interface tables in SAP Landscape Transformation (SLT) Replication Server.
  • Level 4: The reports compare the data in the interface tables in SLT Replication Server and SAP S/4HANA.
  • Level 5: The reports show how the data in the initial staging tables in Stage 1 of the staging database transforms and moves into SAP S/4HANA.

  For information about accessing reconciliation reports, see Comparison Reports for Third-Party Systems Guide.

• SAP Fiori: The SAP Fiori apps used for Drilldown or Reconciliation reporting.
• AVL Interfaces: The interfaces that the system calls from the SLT Replication Server after AVL data loads into them from third-party interfaces.

Core Concepts

The following sections define the supporting concepts associated with SAP Central Finance Transaction Replication by insightsoftware for SAP S/4HANA.

The following sections define the supporting concepts associated with reconciliation reports.

Source System

A source system refers to the system from which financial data transfers and consolidates into SAP S/4HANA.

Transaction Replication supports the following source systems:

• Oracle E-Business Suite
• JD Edwards EnterpriseOne
• Oracle PeopleSoft
• IFS Applications
• Microsoft Dynamics AX
• Microsoft Dynamics NAV
• Microsoft Dynamics SL
• Microsoft Dynamics GP
• Microsoft Dynamics 365 Finance and Operations
• Microsoft Dynamics 365 Business Central (on-premises and cloud)
• Epicor iScala
• Infor CloudSuite Industrial (SyteLine)
• Infor Baan
• Infor LN (on-premises)
• Workday
• QAD
• NetSuite
• Deltek Costpoint
• 1C:Enterprise
• SAP ERP Central Component (ECC) (Only for Reconciliation)
• Flat file data

Target System

The target system refers to the SAP S/4HANA system into which all standard database objects consolidate. These objects include BKPF, ACDOCA, and other relevant objects containing the master and transaction data.

Extraction Views

The extraction views refer to the set of views that the system creates based on the source tables. These views reside in the same database as the source system. The extraction views help obtain the information required to post the documents from your source system into SAP S/4HANA.

Staging Database

A set of staging tables exists in the staging database to collect financial transactions from different source systems. Basic validation checks complete before the system transfers the data to the interface tables in the SLT Replication Server. These checks include data type mismatch verification.

The staging database consists of two sets of staging tables:

• Stage 1: The data from multiple source systems first loads into a set of initial staging tables in the staging database with minimal transformations, such as document splitting and large amount splitting.
• Stage 2: The system then moves the data from the initial staging tables to the FIN% tables in the staging database with several transformations and validations. The FIN% tables for Transaction data replication and CF_E% tables for AVL data replication correspond to the SLT Replication Server interface tables

Reconciliation Objects

The reconciliation objects refer to a set of virtual tables, database views, CDS views, and SAP Fiori apps in SAP HANA and the SAP S/4HANA application.

Intercompany Transactions

Transaction Replication supports intercompany transactions for applicable source systems. For JD Edwards EnterpriseOne, it supports the detail and configured hub methods of intercompany transactions.