We would like a Preference "Set Initial Revision of Downstream Branch to Match Upstream Branch
* Some Customers Migrate into Windchill (CAD and Part Structures)
* Some Customers Start their Windchill Journey with only CAD/Part Structures
* Revisions of EBOMs could be Rev F and the same BOM could exist in MRP System as that Number at Rev F
Then they decide they would like to create MBOMs in Windchill.
MAPSB/BOM Transformer when you create a New Downstream Branch will only create at 1st Revision.
If EBOM was Rev 7 and had 10 Sub Assemblies at different Revisions
If Each was turned into a (New Downstream Branch) in the MBOM they all would reset to Revision A.
You would have to Leave MAPSB/BOM Transfomer - Revise them to the Correct Revision, Update Equivalence and Return to MAPSB/BOM Transformer
While - Yes Many companies are Fine with Number 1108600 Rev F (Design) and 1108600 Rev A (Manufacturing) and Keeping no Rev in the MRP System so that the MBOM can go in. Other companies get confused using same number and what? Rev A EBOM is to Rev B MBOM and Rev B EBOM is actually Rev E of MBOM. Not all customers work that way.
Similarly to CAD-Part Relationship. Many companies like to keep CAD Drawings and Windchill Parts at Same Revision. They can set a Preference "Set Revision for Part" and "Store New Parts with CAD Documents" so that CAD Components/Drawings and Windchill (Design View) Parts can have a matching Revision.
We are asking for a continuation of the Logic. When an EBOM reaches a Point of Development where a Manufacturing BOM is Necessary. We would like a Preference "Set Initial Revision of Downstream Branch to Match Upstream Branch" which would match Revision and maintain Equivalence.
PTC could also consider on the New Downstream Branch GUI to add Revision, so that a Revision could be select for the Downstream View.
Once Customer is up and running New Models starting Design Rev A and Manufacturing Rev A are generally fine. This seems to effect customer just beginning to use MPMLink (While having CAD in Windchill for a couple of decades) and that have existing Products in their MRP System.