• The item that is the header of the BOM exists in Oracle Applications before the BOM is created.

• You may send either an engineering BOM or a production BOM, but you cannot send both types of BOMs in one organization for a given assembly. Once you publish a BOM as either engineering or production you cannot change its usage, as there is a separate procedure in Oracle Applications to transfer an engineering BOM (prototype) to the production (manufacturing) department.

• You may send an alternate BOM to Oracle Applications but the master BOM (a BOM with alternate code =’’) must exist in that organization and be published first.

• It is assumed that alternate strings exist in Oracle Applications. Alternate strings are sent without transformation.

• One Oracle Applications BOM Business Object Interface (BOI) call can create multiple parent/child relationships.

• Multiple Oracle Applications API calls are necessary to create or change the same BOM in multiple organizations.

• Distribution target organization information is provided when creating and changing BOMs.

• All records in each call to the BOM BOI must be in the same organization.

• The BOM BOI can only process one BOM header at a time.

• BOM releases from Windchill will always be accompanied by a corresponding item (part) record for the BOM header.

• Parts can be created/changed in the same publishing transaction as a Create or Change BOM.

• The items that are the header and children of the BOM must exist in Oracle Applications in all organizations in which the BOM is being created.

• Standard BOMs can only have standard items as components.

• In Oracle Applications, BOM component information can be changed without modifying the revision of the BOM.

• If components on a Change BOM publishing transaction are to be changed or deleted, theWindchill ESI business logic must query Oracle Applications for the start effectivity date of those components. This is necessary even when the start effectivity date is sent from Windchill PDMLink.

• Only one level of a multi-level BOM can be processed per Oracle Applications BOM BOI call.

• For multi-level BOMs, it is not necessary that the subassemblies exist in Oracle Applications. It is only necessary that the part (that will become the subassembly) exists.

• Line Numbers will be 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 one Windchill ESI solution shall not release a BOM with line numbers as well as a BOM without line numbers.

• BOM revisions will be created using the Open Item Interface functionality.

• Where they differ, different views of a part are not associated to the same organization. Different views of the same part are not passed to Oracle Applications on the same CN.

• Windchill PDMLink sends the first character of a view version to theWindchill ESI EAI components. The EAI components do not filter view versions.

• Views are used inWindchill PDMLink to represent different functions of the same BOM.

• Identical components cannot be added to a BOM at different line numbers if the effective date range of the components overlaps.

• 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.