Creating and Updating Process Plans
The following lists assumptions related to creating and changing process plans:
• In Windchill the process plan number is different from the BOM part number. However, routings in Oracle Applications are referred to and identified by their item number.
• Publication of the following associated objects is not supported:
◦ Sequences
◦ Suboperations
◦ Work instructions
◦ Tooling
◦ Process Materials
◦ Skills
◦ Control Characteristics
• The Operation Number sent from Windchill is not mapped to the operation sequence number in Oracle Applications. However, the Operation Label from Windchill is.
• In ECN centric mode, before creating a Routing revision, the Routing must exist. For this reason, the EAI components first create an empty routing and then process everything using the ECO.
• In ECN centric mode, changing an operation label is not supported. Attempting this would cause the middleware to throw an exception.
• If a part is allocated to an operation in Windchill, the BOM associated to the routing that holds the operation is also updated in Oracle Applications.
• The middleware will throw an exception under the following conditions:
◦ A process plan is published without associating any part of it, or with multiple parts associated to it.
◦ A tooling, skill or process material is published.
◦ Department (Workcenter) resources and their associations are not in sync with Oracle Applications.
◦ If a routing and the associated BOM exist in Oracle Applicationsto avoid an exception the BOM must be sent with the process plan for any subsequent publication.
• If you publish a process plan, then all associated BOMs and parts will also be published.