Reconcilation and Validations of ISU

[former_member663772]

Hi all,

The query i want to put up is regarding the reconcilation and validations of the migrated data during an IS-U cutover. The problem i am facing is that after consultation with the Business users of Finance department the reconcilation and validation strategy we have devised yet is based on the every months reconcilation reports such as Taxation,recovery and etc. I am not sure as to base my reconcilation and validation strategy just on the every month report. Will this suffice?

Please do give me some pointers on other approches to reconcilation and validations.

Cheers.

F.Hashmi

[former_member213733]

Well reconcilliation of cutover data is done in accordance with B/s received from the legacy .

The documents that are generated as initial upload are posted to initial upload account and the corresponding entry is posted to the reconcillation account .

At the end of B/S upload or FI cutover the intial upload account should be Zero '0'.

What are you actually looking at in recon. ? what are you looking in validations ?

Kindly elaborate more to comment further .

[former_member663772]

Thanks for such a quick response,

The recon i am looking for is regarding the open items, security, payments etc

The validations i am concerned about are of the micro level figures of each sample customers contract account.

A strategy document for such a scenario will be very helpful.

By the way i am wondering what is the usual strategy by B/S for reconcilation and validations in most ISU implementations.

[former_member213733]

Table TEMKSV stores the data for legacy migration that is done and what is the corresponding document that is generated in SAP .

Using the legacy key you can find out the object Key ( Document number ) of SAP .

Passing the same in various tables like DFKKOP , DFKKZP , FKK_SEC you can reconcile the amount .

In case if you are not using EMIGALL then you will have to play around with Tables and Reconcilliation key , DFKKSUM and DFKKSUMC .

It all depends on how you are doing the migration .

As i said earlier , it is the migration account ( initial upload account ) that has to be kept under scrutiny .

[former_member663772]

HI Trivedi ,

I know the TEMKSV tables and its functionality. For information I am using emigall. I can not make out ur comment:

it is the migration account ( initial upload account ) that has to be kept under scrutiny .

What i figure is that, using TEMKSV and DFKKSUM and DFKKSUMC .

i can have some confident recon.

Further please explain a little B/S working done on recon accounts

after go live. A step by step line of action would really help.

[former_member213733]

As i stated earlier , that initial upload account is the backbone of cutover migration .

In the end when all the data is being uploaded in the system , the balance of upload account should be zero '0' when you run the B/S .

What you can also do is you can create one new migration account ( initial upload account throuhg Emigall ) and where in you can match your control totals in the B/s . Generally there is 1 initial upload account that is created but you can create as per your requirement . so create a new initial upload account just for ISU migration and have the control totals in place .

On the other hand , the process remains in place of closing the recon key FPG4 , transferring the same to FI - FPG1 and transferring the same to COPA - FPG3 .

I would also advise you to create a report base of TEMKSV to (DFKKOP , ZP , FKK_SEC etc. ) so that at an instance you can put the legacy key as input and get the final status in you SAP database .

Hope it helps , revert if still having queries .