SV4.1 to SV5.0 SP2 System upgrade MOD300 object problems
I create a SV50 Sp2 system in VM's and have the SV4.1 system from the customer in VM's too.
I made a full backup of the system in SV4.1 as stated in 2PAA113553-600_-_en_System_800xA_4.1_to_5.0_SP2_Upgrade.
I imported the full backup into SV50 Sp2 and except for graphic elements, that we don't care about, everything seems good.
Problem comes with MOD300 objects: MOD_UNIT objects are not imported into Control Structure. In Functional Structure, there are lots of LOOP objects under MOD_UNIT objects that are imported under NO parent into the Functional Structure, all spread out, and MOD_UNIT object do not appear.
Making some test, discovered that making an export of Control Structure without dependencies and then import it into SV50, MOD_UNIT objects are imported but not if the export is done with dependencies. Might be wrong dependencies in this object? How and which ones should I check before import?
My overall question is: is there a procedure to upgrade a 800xA for MOD300 system, some pre-requisites before doing full backup? Should I do the export/import manually between systems?
Thanks for your expertise.
Try to run the consistency check in all the structures, before exporting or before doing the FullBackup, maybe a dependency is not consistent and have some not visible errors.
No particular requirements are out of the System 4.1 to 5.0 SP2 Upgrade Manual.
Please let us know your outcome.