Migration scenario for simple finance (GL & AA)

[Former Member]

Dear Friends/experts,

   Please clarify my doubts regarding the following (urgent help is required)

1.   We have a ECC 6.0  on EHP 7.4 on top of SAP HANA DB system running on Classic GL and Classic AA (DEV system), We have started      copying Prod data into dev as beggining of the project
2.   In Dev we will activate (EA-FIN) component and then install Simple finance add on
3.   Run pre migration checks and migrate to General ledger on SFIN customizing settings ( no need of any new gl funcionality) DO post migration ativity in DEV and Migrate transaction data
4. Activate New AA, Run pre migration activity for NEW AA (period close activities ) and Migrate Chart of Dep during 1st of new period, Migrate Transaction Data
5. Migration of Bank accounts
6. Check for custom objects and apply if any fixes required

Now the major question is after DEV is complete.. how do I move forward with Acceptance ? (i.e) Transport all customising activities including SFIN/NewAA/Custom objects to Acceptance box Copy latest prod data and run migration program only for transaction data ? or

Rebuild the Acceptance as DEV? I am totally confused at this stage and could not proceed please throw some light into the landscape movement also for production scenario

[Former Member · Accepted solution]

Hi,

first of all you need to consider activation of activate EA-FIN as a small separate project and as a consequence perform testing.

Second, I recommend to read course AC100, here you can find all answers to your questions.

' Run pre migration checks' - this clause has to have Period end closing, reconcilation, FI-AA pre check reports and so on.

Acceptance has to be performed in    Test system.

E.g. you perform all tasks in Dev, then move all transports to Test and repeat all tasks(except installation), if no errors then move TRs to Productive and repeat all steps

[Former Member · Accepted solution]

Hi Aleksey..

     Thanks for the response ..

     So as per your inputs, we will do the baseline configurations required (pre migration activities) as part of SFIN migration in DEV for GL & AA and then run the migration program that will migrate customizing data and transaction data in DEV client and will that not generate any transports (I specifically mean migration programs regarding customizing data that needs to be moved to Acceptance )

So for UAT in acceptance we will move the customizing transports generated (baseline config as above along with clients custom objects) to Acceptance box and do I need to again have a production copy in A box and run migration programs again to verify if everything is working fine to get business sign off?

This part is not clear in AC 100 itself .. because i am unsure about what I will test in UAT is it only the fresh transaction data from logistics & Finance modules? or different from my understanding

Please throw some inputs into this..

[Former Member · Accepted solution]

Hi,

you need to perform all migration steps in Dev, including migration for transaction data, even if you don't have it there.

"So for UAT in acceptance we will move the customizing transports generated (baseline config as above along with clients custom objects) to Acceptance box and do I need to again have a production copy in A box and run migration programs again to verify if everything is working fine to get business sign off?"

- I didn't catch it... You can make copy of productive to test before moving TR's and installing SFIN, then perform pre check,  instal, move TRs and perform full migration cycle again.

'This part is not clear in AC 100 itself' - here you can find recommendation how to proceed migration, e.g. repeat repeat Copy productive, install SFIN, run migration until you have an error

[Former Member · Accepted solution]

The major concern is that if  (let us leave behind transaction data for now)... Do I need to repeat all Migration steps under migration cockpit  (i.e)          1). preparation and migration of customizing 2) Migration 3) Activities after migration in Development Box, Acceptance box, and Production box  ?

Will the activated components like EA-FIN & simple finance  along with baseline TP's & custom objects will move from DEV to  Acceptance to Prod?

or I again install activate & then migrate to SFIN separetely in Acceptance  & Production?

[Former Member · Accepted solution]

Hi,

1. Yes, even more... you need to repeat it (not only dev,test prod, but also test 1,test 2 and so on) till you have no any errors, issues...

2. EA-FIN you have to move because it's prerequisites for new FI-AA

[Former Member · Accepted solution]

Hi aleksey..

Apologies to bother too much ..  So as per your inputs my understanding is as follows Please correct if I am wrong.

1). I take a Prod copy and do a technical upgrade to HANA DB

2) . Activate EA-FIN and Install SFIN in only DEV, (this will be transported to QA/PROD)

3) . DO baseline customizing as required  (this will be transported as to QA/PRD)

4) . DO Pre migration activities, Migration and post migration activites in DEV/QA/PRD seperately

5). Move custom objects fromDEV to QA and to PRD without any changes if thay pass testing in            DEV /QA

6). Apply fixes only for required custom objects in DEV which were having errors

7) . Even if i encounter errors while running migration programs , can I rerun in same Dev/QA after             fixing it via applying notes /fixes

I hope these question will also help others who have similar concerns on SFIN migration,please correct if i am wrong.

[Former Member · Accepted solution]

Hi,

1 Yes (if you're on ehp7)

2. First you need perform Pre-checks,Consistency check,Custom code Closing,Reporting, then install SFIN

3. Yes

4. what is 'Pre migration activities'?.  Migration and post migration activites - yes

If you have errors, issues - fix it...

Then do the same in test, (of cause in some case  you need to transfer config and so on instead of doing it)..

Repeat these steps until you have errors...

And some remarks.

Before doing it, it's better to try it on sand box(copy of pro, but not included into your transport system) - to get high level understanding...

EA-FIN activation it's better to do and test before SFIN conversion.

[Former Member · Accepted solution]

Hi Aleksey ..Thanks once again for the valuable inputs.

As per your above statement in Point ...2. First you need perform Pre-checks,Consistency check,Custom code Closing,Reporting, then install SFIN

What are the pre checks to be considered ? anything specific

Answer to point 4 : these the steps in migration cockpit ..

The following is our approach for now

My client is in ECC 4.7 Using classic GL and old asset accounting running Costing based Copa & account based Copa, given the cost and licensing constraints we are planning to copy the Prod and do OSDB migration to ECC 6.0 ehp 7.XX on HANA DB in DEV client , activate EA-FIN, Install SFIN, Migrate to SFIN GL & New AA and controlling and then roll this out to QA & go live

we know we are bypassing the standard approach but don’t have any other option at the moment  (Client is not interested in using any new GL functionality)  Is this workable and will SAP support such migration incase in any issues?

[Former Member · Accepted solution]

Hi,

notes 1939592,2129306. If you're  starting with classic GL, then you need to reset bseg-bdiff before sfin intallation.

Then report fins_mig_precheck

[Former Member · Accepted solution]

One last question before I close this thread .

So SFIN migration cockpit programs are box dependent and will not generate any transports to be moved to other boxes (E.g from DEV --> QA --> PROD) and need to be repeated in D-->A-->P box while implementing simple finance add on, Only the Activation of EA-FIN and Installation of SFIN will take place in DEV and can be moved/copied to QA & PROD ?

Please let me know if my understanding is correct

[Former Member · Accepted solution]

Migration steps could be devided into several parts, e.g. preparation and migration.

In migration step there is migration of transaction data mostly(or master data), so you don't need TR, but in preparation step there are a lot of config(like fi-aa, gl and co), which should be move via TR

[Former Member · Accepted solution]

Are you referring to the above activity node (in pic) Preparations and migration of customizing that will create TR'S for all the Sub nodes while running /configuring in DEV?

or you referring to a different customizing requirements for FI-AA/CO/GL?  please clarify

I can understand that node Migration and activities after migration are box dependent and has to be done in DEV/QA/PROD ..

[Former Member · Accepted solution]

I refer to 'methodology' and not to IMG, but they are close. Mostly you don't need to find some config node in IMG, you need just to follow this Node(from your print screen), may be except currency revaluation resetting - there you need to create valuation method for that

'I can understand that node Migration and activities after migration are box dependent and has to be done in DEV/QA/PROD'

-yes

[Former Member · Accepted solution]

Thank you very much for your kind help, time taken and the patience to respond.. It helped me a lot,  ...