SAP FICO Migration to S/4HANA: Master Data, Open Items, Testing and Cutover Basics

Finance migration is a reconciliation exercise

A migration can finish technically while leaving finance with duplicate items, incorrect due dates or balances assigned to the wrong supplier. Define what must agree before loading data: the transition scope, cutoff, source records, target mapping and reconciliation level. Then test how the migrated information behaves in a real finance process.

The example below follows supplier open items because they make these controls visible. The same discipline applies to other data objects, but each object has its own prerequisites and supported scope.

Core concepts to learn

Build a practice scenario

1. Step 1: List each source object, owner, target object, cutoff and required prerequisite.
2. Step 2: Reconcile source supplier totals and individual invoices before building the load file.
3. Step 3: Rehearse a valid invoice, credit memo and rejected reference; retain target document numbers.
4. Step 4: Compare target results, resolve exceptions and obtain the agreed go/no-go decision.

Use sample, authorised or fictional data. Do not publish credentials, business data, account numbers or customer information in a portfolio. If a task has financial, security or production impact, include a review or approval step before any change.

What good work looks like

First decide what kind of transition is happening

A new implementation, a system conversion and a selective data transition are different projects. In a new implementation, the team establishes a target system and migrates agreed business data. A system conversion transforms an existing SAP ERP system to S/4HANA through a guided technical process. Selective transition combines choices about which configuration and data to retain or transform. Do not treat a spreadsheet upload checklist as a complete conversion plan.

SAP’s transition guidance distinguishes these routes. The migration cockpit is relevant to supported data migration scenarios; it is not the tool that performs every technical conversion activity. Confirm the target edition, release, supported migration objects and project approach before choosing templates. Public Edition instructions should not automatically be applied to an on-premise or Private Edition system.

A fictional supplier open-item reconciliation

Consider a company moving its agreed opening balances at a month-end cutoff. Supplier A has an unpaid invoice of Rs 80,000. Supplier B has an unpaid invoice of Rs 35,000 and a credit memo of Rs 5,000. The simplified payable total is Rs 110,000: 80,000 plus 35,000 minus 5,000. Taxes, exchange differences and special transactions are excluded from this teaching example.

Keep the three open items separate. Loading only a net amount of Rs 110,000 would lose the invoice references, due dates and supplier-level information needed for payment and clearing. Reconcile the source item count, supplier balances and overall total against the target. The debit and credit signs must follow the selected migration object’s documented conventions, rather than a guessed spreadsheet convention.

If the target total is Rs 115,000, investigate whether the credit memo was omitted. If the total matches but Supplier A shows Rs 70,000 and Supplier B Rs 40,000, the overall agreement hides an allocation error. A useful reconciliation therefore works at several levels: company code, currency, supplier and individual reference. Finance signs off both the amounts and their meaning.

Master data must support the items you load

Build a mapping register before loading transactions. Record each legacy supplier identifier, intended target business partner, company-code assignment, payment terms and accountable owner. Include the status of duplicate records and blocked or obsolete accounts. Do not merge two suppliers merely because their names look similar; the business owner must establish that they represent the same party.

For each migration object, review prerequisite objects, required fields and post-processing checks. SAP’s Public Edition learning material explains that available objects depend on activated business processes and that predecessor requirements matter. A technically accepted file is only one checkpoint. Verify that the resulting data can be displayed and used in the expected process by an appropriately authorised user.

Keep a separate schedule for general-ledger balances, receivable and payable open items, and assets. Determine which object is responsible for each amount, including any migration offset accounts. Otherwise the team may load a subledger amount and also include it in an overlapping balance load. Follow the selected object’s scope rather than manually posting to reconciliation accounts to make totals agree.

Test a business outcome, not just an upload status

Use a small rehearsal with known expected results. Start with one ordinary invoice, one credit memo and one deliberately invalid reference. Check the accepted records, rejected records, mapping decisions and target document numbers. Correct the invalid record through the agreed route, then verify that the repeat run does not duplicate records already migrated.

Next test the business process using the migrated items. Can the authorised finance user find the invoice, see the expected due date and select it in the intended payment or clearing workflow? Does a relevant report reconcile to the agreed opening balance? Record the exact selection criteria, especially company code, currency, ledger and key date. A screenshot without its selection scope is weak evidence.

Cutover decisions and the first days after go-live

A cutover plan needs a source posting cutoff, final extraction time, responsible owners, upload sequence and reconciliation checkpoints. Specify how late source transactions will be handled. If a supplier payment is posted after the final extraction but before the source is frozen, an invoice might appear open in both the migration file and the target even though it has already been paid.

Define a go/no-go decision with named reviewers and an evidence pack. A rollback decision needs a tested technical and business plan; deleting a migration file is not a rollback after transactions have been posted. During initial support, track each discrepancy with its amount, document references, business impact and owner. Separate mapping defects from new operational errors.

Does successful migration mean all historical documents were copied?

No. The transition route and agreed object scope determine what is transferred. Document the retention and access plan for historical records separately.

What should a beginner deliver?

Create a fictional source register, mapping sheet, rejected-record log and signed-off reconciliation example. Explain one case where the total agrees but individual items are wrong. That demonstrates a stronger control mindset than showing only a green upload status.

Official SAP references

• SAP transition approaches
• SAP Public Edition migration procedure
• SAP G/L balance and open-item object scope

Frequently asked question

What should a beginner practise after learning SAP FICO S/4HANA migration?

Build one small, documented exercise that uses the concepts safely, validate the result, and explain the decisions and limitations. Repeating this cycle makes learning more reliable than collecting disconnected tutorials.