cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

problem with OOB ESI configuration is sending un-released child parts with Assy

SOLVED
Highlighted
Aquamarine

problem with OOB ESI configuration is sending un-released child parts with Assy

Hi everyone,

We are implementing ESI to send the wtpart information to Oracle.

Its all working great so far with the exception of one problem.

When a revised version of a  Assembly wtpart is sent to Oracle (ERP) on the workflow, the ESI code is also sending all the child parts to Oracle at whatever version they are at. This is fine if all the child parts are also Released on the workflow (change object) together. The problem is that if at anytime a child part is revised from Released to In Work to the next Version then that un-official version would also be sent to Oracle (for ESI code).

Assembly Ver. B "In Work" > Ver. B "Released = sent to Oracle

Part1 Ver. B "Released = sent to Oracle (ignored as it already was published when Released)

Part2 Ver.C "In Work" = sent to Oracle when Assembly is sent.

Does anyone know if there is a setting that can be configured to only:

Send the wtparts on the workflow to Oracle

Send only the official "Released" state parts to Oracle (Assembly and all child parts at Released).

1 ACCEPTED SOLUTION

Accepted Solutions

Re: problem with OOB ESI configuration is sending un-released child parts with Assy

Its a setting at the site level / Managed Distribution.

View solution in original post

1 REPLY 1

Re: problem with OOB ESI configuration is sending un-released child parts with Assy

Its a setting at the site level / Managed Distribution.

View solution in original post