Why we do conversion?
To support legal requirements.SAP has implemented the SAP euro conversion back in 1998.Designed in collaboration with auditors & certified.. Used by severall thousand SAP customers.
Which data is principally converted
Customizing data
Master data
Transaction data
Customer specific data is considered
Search function for customer reports
Search function for Datadictionary
Ok now will jump to my field SAP Basis tasks
Main steps to follow are ....
Note no 534036
Data backup
Switch of archive logging
Adjust database parameters
Data backup
1.A backup before conversion is required to have a valid restore point,Also for documentation purposes before live conversion
2.Another backup after conversion is recommended to have a restore point after conversion incase the system must be restored at a later stage for reasons independent of the conversion..Only for live conversion.
System settings
1.Switch of archive logging
2.Adjust database parameters
3.SAP note 173993 contains general recomendations & best practices.
4.User lock for downtime-Specific functionality to lock users during conversion downtime,Determine and maintain users that should be excluded from being locked
IT IS CRUCIAL THAT NO CURRENCY RELEVANT SETTINGS ARE EVER TRANSPORTED BETWEEN CONVERTED & NON-CONVERTED SYSTEMS
ANALYSIS ----->SYSTEM SETTINGS----->CONVERSION
System settings is the part which we take care .
Note 534036 is the best one to follow for my SAP release.Normally there is a note 173993 Cluster : System settings during Euro LC changeover note belongs to 4.6C which is not our release so I went ahead with Note 534036.It gives an overview for system settings not direct for EURO-conversion, but I think it's a generally issue.
Well will put the main changes of the parameters below( well our SAP system is of 124 cup's & 7 application servers......So the changes are as below)We did 3 test runs so showing the difference of parameters between test run & production run
Comparing Test & Production
1. db_file_multiblock_read_count 32 32
2. Oracle sessions 300 800
3. Oracle Processes 200 1000
4. shared_pool_reserved_size 50M 524288000(500M)
5. shared_pool_size 500M 2634022912(2512M)
6. Redologs 500M 500M
7. undo_retention 172800 (48hrs) 43200 12hrs (48hrs)
8. pga_aggregate_target 209715200 838860800
9. db_writer_processes 5 12
10. REC/CLIENT =OFF (logging of changes in tables has been deactivated
11. tcp.nodelay=YES
12. Refresh of statistics
13. Spool retention(SAP_REORG_SPOOL should not run in the system)
We increased the table spaces as specified below. but this is independent of the total space of your database
Our database is of around 6 tera bytes. so we have to increase as below
14. DB Space(PSAPQAS) 200GB(need to increase after index rebuilds)
15. TEMP table space(PSAPTEMP) 110Gb
16. Undo space(PSAPUNDO) 250GB
17. Below are the indexes need to be created as per our system.
Create index COEP~3 with MANDT,KOKRS,BUKRS
Delete index as per EWUINDEX program(Tech team will do this)
Create index GLPCA~5 fileds RCLNT/RBUKRS
Create index ZJCISLNA~5 Fileds RCLNT/RBUKRS
For larger databases according to the following
Formula:Minimum number of batch processes = (DB size in GB / 75 GB + 1) Batch processes + 1 batch process from class A.
As per our business requirement.they need a backup system(new system) accessible after euro conversion(online with reporting facility) without any batch processes & no updates running so that no changes to the system will be possible...After few months of euro conversion again we got the request the need of few background & update & a few printers to be active for the users need later agreed on paying 200.00 euros for just the monthly backup of the system for 1 year..After that they are fine having that system offline.but that system needs to be available for next 10 years.
Just FYI the whole phases of EURO CONVERSION
We did 4 test runs before we move to production.The activities of the run
'ANALYZE' phase and activities post-shut down, pre-"conversion"
'FILL' phase
'GENERATION'
"CONVERSION" MOST CRITICAL PHASE (duration assigned - TEST1 run post SAP Optimizing -12 hrs, TEST2 run - 39 hrs, TEST3 run - 7 hrs)
'RECON' phase
COEP index deletion
GLPCA and other index recreation - SECOND CRITICAL Phase ( TEST1 run 26 hrs, TEST2 2nd run 15 hrs, TEST3 3rd run - 4 hrs)'POST' Phase
MODULE SPECIFIC ACTIVITIES
Custom program for Hyperion mapping
Validation
Well The final run was very fast.the whole euro conversion process is done comfortably in 2 days.
