SAP LT Replication Server · Replication to Central Finance & S/4HANA

After an unplanned outage causes inconsistency between source and Central Finance target, how do you bring the systems back in sync without a full reload?

Sign in to see the full answer — free to start on the web.

This is one card from the KnowCard library. The full way to learn it — spaced-repetition review, progress tracking, and AI explanations — lives in the KnowCard app, free to start on the web. iOS & Android are coming soon.

Get started — it’s free

Already have an account? Sign in →

More in Replication to Central Finance & S/4HANA

When replicating to Central Finance, SLT does not use its normal table-based, table-to-table approach. What does it use to move data into S/4HANA instead?
On the Specify Transfer Settings screen for a Central Finance load, what value must the Application field be set to?
Where do you download the predefined Central Finance load/replication object template from, and what determines which version you pick?
For a non-SAP source loading into S/4HANA (Central Finance), where does the read module reside, compared with an SAP source?
In which SAP transaction are the source-table-to-target-function-module mappings maintained for a Central Finance replication?
In a Central Finance scenario, which SLT-side table tracks financial documents already posted to S/4HANA so they aren't posted twice?