Can’t set effectivity in concurrent engineering

[MaGryz]

Hello,
Productstream is stuck.
When I try to set effectivity, I get the message:
“Operation cannot be performed because the item is currently associated with an open change order.”

How do I get this situation?

We have two assemblies which are using the same parts

Assembly1 include part1 and part2
Assembly2 include part1 and part2

There are two change orders for this assemblies and this parts:
ECO1 include assembly1 and part1
ECO2 include assembly2 and part2

When both of this change orders are in approved state, we can’t set effectivity for any of them because when we try to release assembly1, system try to release part2 but it is associated with an ECO2.

In approved state we can’t delete item from ECO.
We also can’t back ECO to work state.
System just stuck.

What we should do?

Marcin Gryz

[carrie.ruan]

Hi Marcin,

This is the current behavior as designed. Item's effectivity will be controlled by CO once it associated with an open change order. Set effectivity to assembly1 will affect part2, but part2 controlled by ECO2, so it cause that restriction message.

Please try the following two different workarounds to set effectivity to assembly1.

1. Release part2 in Item Master before associated it to ECO2. Then setting effectivity to assembly1 will work.

2. Delete the ECO2 which controls part2, and then setting effectivity to assembly1 will work.


Hope this is helpful.

Best Regards,
Carrie

[MaGryz]

Hi Carrie,

Regarding your propositions:
1. I describe existing situation, and your proposition is how to avoid this situation in the future. Now I can’t release part2 in Item Master, because it is controlled by ECO.
2. I can’t delete ECO2 in this state.

Best regards
Marcin Gryz

[Anonymous]

Hello Marcin

Long time since last time we met.

I have tested your problem and found different approaches. I tested on PS
2009

First I tested with using a direct Submit and approve by the Change
Administrator from Open to Approved state - and I could set effetivity for
both ECOs to get them closed.
This is probably not the workflow you used (sort of defies the purpose of an
ECO - not to do any changes), so I tested afterwards a more regular way of
sending an ECO through system.

I ran a regular ECO with Change Administrator submitting to Work state -
where a Responsible Engineer makes changes and submit for Review.
At this point I will stress that I use the setting as shown in
"Option.png"screen grab - which forces the Engineer to change LifeCycle
state of Item to "In Review" before submitting to Review.

Here I get the message that Part 2 is in another ECO and Life Cycle cannot
be changed - see the "Message.png" screen grab.

At this point the Engineer can report back that the Change is not posible -
and the second ECO can be cancelled - and therefor the problem can be
avoided.

So there must be something different in yoour workflow - but at least there
is an option to avoid getting into the problem another time.

For your current problem - I suggest you packup the database and contact
Autodesk Support to get the problem sorted out.

Not much help for the current problem here I'm afraid - but I hope it gave
you some ideas for avoiding getting into similar situation later.

Best regards

Uffe Bak
Customer Success Engineer
Data Management, Autodesk Manufacturing

[Anonymous]

Can you log this through Partner Center?

When you do, can you mark it for my attention?

Can you also get the latest copies of the backup and upload the databases to
the Support Cases FTP site. We do not need the filestore, just the Vault and
KnowledgeVaultMaster _dbbak files.


Best Regards

Richard Rankin
Autodesk Support

[carrie.ruan]

.

[carrie.ruan]

Hello Marcin,

There is an additional point about deleting an ECO. Could you please try to login client with Administrator role if the issue is in Productstream 2009?

Because there is an update about ECO deleting in PS 2009, System Administrator can delete any status ECO. An error dialog will pop up when Administrator role delete a Approve status ECO, please click ‘Detail >>’ button to expand that dialog to get 'Ignore restrictions (delete unconditionally)'checkbox, turn on the checkbox, then click Yes button, the ECO will be deleted.

If the ECO still can't be deleted by the Administrator, it may be a defect. Please follow Uffe Bak and Richard Rankin's suggestion.

Hope this is helpful.

Best Regards,
Carrie