on 01-14-2009 4:17 PM
When a new version of a document is created as a copy of the previous version, the PORDER object links are being copied to the new version along with the MARA links. This results in the PORDER record being in the DRAD table but not the DRAD_PORDER table, which ultimately shows the incorrect document version on production orders. This only happens when the document version is created in a source client and ALE'd to a target client. If we manually create a new document version using a template, we are OK. Our configuration is set up to not maintain object links via ALE.
Has anyone else had this happen, or have any ideas on where we can look?
Thank you,
Melissa
I think we found our problem. In configuration for defining the object links for a document type, we needed to uncheck the Obj Link Target Syst checkbox. (While still keeping the No Maint via ALE checked).
Regards,
Melissa
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
91 | |
7 | |
7 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.