• ECOs can be created in Oracle Applications to manage changes to Items and/or BOMs.

• One Oracle ECO BOI invocation can create multiple BOM parent/child relationships.

• At least one revised item and/or BOM header will always accompany each ECO published from Windchill.

• If CNs are required by the distribution target system and not used in Windchill PDMLink,Windchill ESI Services will be configured to generate CNs.

• The Oracle Applications distribution target system requires no special configuration to support ECO processing for Windchill ESI. The "Change Order Types" configurable attribute shall be configured with (at least) its standard, Oracle-shipped default setting.

• Oracle Application's security configuration is sufficient to support Windchill ESI activities, including:

◦ ESISYS user account responsibilities

◦ ECO Profile Options

• ECO auto-numbering is not configured in the Oracle Applications system, sinceWindchill PDMLink will define ECO numbers.

• Multiple Oracle Applications ECO Business Object Interface (BOI) API invocations are necessary to create an ECO in multiple organizations.

• ECOs in Oracle Applications must not be associated with workflows and must not have an approval list. It is assumed that approvals and workflows are implemented and maintained in Windchill PDMLink.

• An administrator will schedule the Automatic Engineering Change Order Implementation concurrent program to run at predetermined intervals for all Windchill ESI -related organizations. This program will set the status of all recently-created (Scheduled) ECOs to Implemented based on effectivity.

• All records in one call to the ECO BOI must be in the same organization.

• All records on an ECO must, at a minimum, exist in the same Oracle target system(s) and organization(s) as their parent records.

• Windchill PDMLink must provide one or more distribution target organizations for the ECO and all the records it contains. IfWindchill PDMLink does not provide valid values for all required organization fields,Windchill ESI will not create the ECO.

• IfWindchill PDMLink does not supply an effectivity date for a given revised item or BOM header,Windchill ESI shall provide a suitable default effectivity date for the item and, if applicable, its children.

• An ECO must not already exist in the distribution target organization to which it is being published for creation.

• The Oracle Applications ECO BOI used to create BOMs can be used for BOMs with component line numbers and BOMs without line numbers.

• BOM Line Numbers are supported, but are not required. If the component line number is not passed from Windchill PDMLink, Oracle Applications will automatically assign a line number in the item sequence field. For any installation of Windchill ESI, all BOMs will be released either with line numbers or without line numbers. Any oneWindchill ESI solution shall not release a BOM with line numbers as well as a BOM without line numbers.

• Reference Designators and Substitutes do not have line numbers in Oracle Applications. Windchill ESI will not transfer the values in theseWindchill PDMLink fields to Oracle.

• It is assumed that all BOMs that are published using a single ECO are of the same usage. The middleware business logic looks up the change type code (that decides the assembly type of a BOM in Oracle Applications) using any one BOM. In Oracle Applications you cannot create one BOM in engineering (prototype) and the other BOM in production (manufacturing) department of the same organization using one ECO. Since an ECO is organization aware, you can create one BOM in engineering department of one organization and the other BOM in production department of another organization in Oracle Applications.