anunaya.mund
Member
So we have weird issue going on and I would really appreciate any advice I can get here.
Here are the Bullet points.
1. When we did a comparison in the c code between PD and PY, we found some mismatches,some objects were missing and some objects had code mismatches
2. We ignore objects in development or part of ongoing ESUs.
3. Even now, we were left with about a few missing objects and a few code mismatches, these code mismatches, were to do with SAR codes available in PY object source but missing in the PD objects's code.
4. So when I searched for those perticular SARs and related ESUs, weirdly in ESU logs it showed that the ESUs were applied success fully to all environments but somehow the SARs codes are missing in afew object, We verified omw loggings to see if any manual changes were made buit no luck.
5. So we dont know how this happened but we have this issue. Note- We used Beyond Compare to do the Dep server pathcode\source folder compare for this. So that showed us the n* and b* object differences but there must be other object types with similar issues.
6. So just re applying the ESU with forcemerging the objects might not be a good idea, as we dont what other objects from that ESu is affected.
7. Force merging all objects is also not feasible as the ESUs are fairly large and too many objects are there.
So any idea how we can fix this? get all obj. in sync? The reason for this is so that we can have reliable testing in PY.
We can do a full env. refresh including central objects from PD to PY, but thats another big no, no as it will make all our ESU etc applied logs and informations invalid.
So I am hoping I can get some directions from the JDE Gurus here...
Thank you.
Anu
Here are the Bullet points.
1. When we did a comparison in the c code between PD and PY, we found some mismatches,some objects were missing and some objects had code mismatches
2. We ignore objects in development or part of ongoing ESUs.
3. Even now, we were left with about a few missing objects and a few code mismatches, these code mismatches, were to do with SAR codes available in PY object source but missing in the PD objects's code.
4. So when I searched for those perticular SARs and related ESUs, weirdly in ESU logs it showed that the ESUs were applied success fully to all environments but somehow the SARs codes are missing in afew object, We verified omw loggings to see if any manual changes were made buit no luck.
5. So we dont know how this happened but we have this issue. Note- We used Beyond Compare to do the Dep server pathcode\source folder compare for this. So that showed us the n* and b* object differences but there must be other object types with similar issues.
6. So just re applying the ESU with forcemerging the objects might not be a good idea, as we dont what other objects from that ESu is affected.
7. Force merging all objects is also not feasible as the ESUs are fairly large and too many objects are there.
So any idea how we can fix this? get all obj. in sync? The reason for this is so that we can have reliable testing in PY.
We can do a full env. refresh including central objects from PD to PY, but thats another big no, no as it will make all our ESU etc applied logs and informations invalid.
So I am hoping I can get some directions from the JDE Gurus here...
Thank you.
Anu