FerryCNC
Member
JDE 8.9 to 8.12 DV upgrade is not picking standard objects while spec conversion and newly added objects of E812
Upgrading from 8.9 to 8.12
Environment:
Deployment Server - Windows 2003 R2 Server
Enterprise Server - Windows 2003 R2 Server
Database - SQL server (Resides on Enterprise Server)
Tool Release - 8.96.3.2
Problem Summary:
First we upgraded JD9 environment to PS812 environment and there was no issue, everything went fine. But when we upgraded DV9 environment, till table conversion it worked perfectly but specification merge process only merged those objects to DV812 which were Flagged as ‘C’ and ‘1’ option in Specification Merge Selection application against DV9 environment (our old release).
We tried following merge combination for few objects and Spec merge didn’t update them in F9861 table, F983051 is also showing only custom objects, no standard objects are updated.
Blank + 1
C + Blank
Both Blank
C + 2
Blank + 2
When we checked the include and Source folders in DV812 pathcode, system copied all the .h and .c files from DV9 to DV812 pathcode. It means system replaced the new DV812’s .h and .c files with DV9. it means in DV812 we have old .h and .c files, so many of the files will not work as they must have changed in E812 release.
In JDE_DV812, JDE812, database, we have B9 entry in release field for all the DV812 objects in most of the tables.
Conclusion-
Specification merge report R98700 only picking those records which have been selected in Specification Merge Selection as ‘C” and ‘1’.
During upgrade, system is also not copying E812 specific newly added objects.
<font color="black"> </font>
Please advice….
Upgrading from 8.9 to 8.12
Environment:
Deployment Server - Windows 2003 R2 Server
Enterprise Server - Windows 2003 R2 Server
Database - SQL server (Resides on Enterprise Server)
Tool Release - 8.96.3.2
Problem Summary:
First we upgraded JD9 environment to PS812 environment and there was no issue, everything went fine. But when we upgraded DV9 environment, till table conversion it worked perfectly but specification merge process only merged those objects to DV812 which were Flagged as ‘C’ and ‘1’ option in Specification Merge Selection application against DV9 environment (our old release).
We tried following merge combination for few objects and Spec merge didn’t update them in F9861 table, F983051 is also showing only custom objects, no standard objects are updated.
Blank + 1
C + Blank
Both Blank
C + 2
Blank + 2
When we checked the include and Source folders in DV812 pathcode, system copied all the .h and .c files from DV9 to DV812 pathcode. It means system replaced the new DV812’s .h and .c files with DV9. it means in DV812 we have old .h and .c files, so many of the files will not work as they must have changed in E812 release.
In JDE_DV812, JDE812, database, we have B9 entry in release field for all the DV812 objects in most of the tables.
Conclusion-
Specification merge report R98700 only picking those records which have been selected in Specification Merge Selection as ‘C” and ‘1’.
During upgrade, system is also not copying E812 specific newly added objects.
<font color="black"> </font>
Please advice….