Copied Objects (OMW) Corrupted

[Larry_Jones]

Recently on another thread Zoltan Gyimesi made the following statement: "...I have a suspicion (currently I can not prove it) that in some cases Object Copy will make the copied object less or more corrupted. I suppose, in some situation it can not evaluate correctly some reference in the Event Rule."

As of last Friday I believe I've encountered this situation where the behavior of a copied UBE (copied to a different name, PO template also copied) is just buggy. Some field values don't print (unless I delete and re-add the fields). Add and then delete a few lines of ER code and the Group headers don't print, etc.

I'm wondering how wide-spread is this behavior. Is anyone else encountering this problem in copied UBEs? How about Applications?

FYI I have not found anything in the Knowledge Garden re this problem.

TIA,

Larry Jones
[email protected]
OneWorld XE, SP 15.1
HPUX 11, Oracle SE 8.1.6
Mfg, Distribution, Financials

 

[Larry_Jones]

The below response was received from Adrian Oanta via E-Mail:
-------------------------------------------------------------
Hi Larry,

I'm not sure if your scenario is the same as mine, but I've encountered the following:
1. UBE R55A has PO T55A. Create a version for the UBE.
1.5 Check-in all objects.
2. I remove PO T55A and attach PO T55B to R55A.
3. Check-in R55A.
4. Copy R55A to R55B.

When I look at R55B, the attached PO is T55A(which is the old PO). If I look at R55A, the attached PO is T55B(which is correct). There is an integrity issue between RDA Spec and F9860.

A workaround for this (worked 100% of the time): before copying the object, check-out and check back in the template (checking out and checking back in the template will make update F9860 and make RDA Spec and F9860 in sync). Then copy.

Please let me know if what you see is similar. All it goes down to where does it take the specs from when doing a copy. If you need more details on this one, please send me an e-mail.

Adrian Oanta
---------------------------------------------------------------------
and my reply to Adrian ...
--------------------------
Adrian,

thx for the response. My situation is different in that my source object (R5542004) is 2 years old and refers to the correct template in both RDASPEC and F9860. I checked the template object in the new UBE (R5542005) and it correctly references its new template also.

Regards,

Larry Jones
[email protected]
OneWorld XE, SP 15.1
HPUX 11, Oracle SE 8.1.6
Mfg, Distribution, Financials