non-transferable part type in Agile

All the parts(types) except documents created in Agile will be transferred to our ERP and other downstream systems for SCM and forecast purposes.

Currently, our engineers are using document category to represent the sub-assembly that shouldn’t be sent over to downstream system but is on EBOM of the part, this is to satisfy the only rule “EBOM should match with Drawing” on BOMs.

Though this is bad practice but the architecture team didn’t have a way out at the time.

Due to new changes in our application landscape we’re registering all the Documents in Agile in a different system and as part of revamp we want to correct this approach.


Looking for ideas and best-practices to correct the wrong doing.

Agile User Asked on July 21, 2022 in Product Collaboration.
Add Comment
0 Answer(s)

Your Answer

By posting your answer, you agree to the privacy policy and terms of service.