Skip to Content
Jan 11 at 11:42 AM

Legacy data transfer during fiscal year before GO live 1/4: how to migrate correct posting dates

25 Views Last edit Jan 11 at 11:43 AM 2 rev

Hi community,

Let me explain the issue that we have.

The Go live of our S4C implementation is delayed from 1st of January to 1st of April. The migration key date will eventually be set to 31st of March. This means that all the records of the Migration objects (customer open items, vendor open items, GL balance op items) will have posting date 31/03.

Since it is not possible to adjust the posting dates , how can we simulate as if the journal entries of GL account balances are posted in the correct month ( January - Febr - March)?

The following are possibles solution that we are thinking about:

1) Migrate object historical balance:

Problem: only for reporting purposes no postings are generated. These balances will be reversed automatically on the predefined migration key date in order to have a zero balance.

2) Upload general journal entries:

Extract all GL accounts and open GL items from legacy system for January, Febr and March and upload via the app 'Upload general journal entries'. This will create multiple journal entries with multiple line items per entry.

Problem: When migrating the object 'FI-G/L account balance and open/line item. We must make sure that the already uploaded GL account balances via the app 'Upload general journal entries' are not added in the migration object 'FI-G/L account balance and open/line item' on 31st of March. Is this correct?

If someone encountered same issues when migrating during fiscal year. Please advice on what the best approach would be to have the posting date of the GL items on the correct period and not on migration key date.

Kind regards,