• Only one primary business object can be created or changed from a single Windchill ESI response message from Windchill PDMLink. For example, if the Windchill ESI response message from Windchill PDMLink is for parts, only one part can be created or changed during that transaction. However, if the response message is meant to create or change a BOM, multiple parts can be created or changed during the transaction.

• Item records will be created in zero or more inventory organizations. They will be created in at least the Item Master Organization.

◦ If Windchill users publish a part only to the Master Organization, the master organization must be explicitly selected as the distribution target.

◦ If Windchill users publish a part to other organizations, they may or may not select the Master Organization as one of the distribution targets. If the Master Organization is not selected, and the part does not exist in that organization, theWindchill ESI business logic will optionally attempt to create it there as well, depending on the ESIORAControlAttributesMaster configuration flag setting.

• Item records can be changed in zero or more inventory organizations.

◦ There is a configuration flag (set at install) in theWindchill ESI business logic to determine if the Windchill attributes are controlled at the master level. If they are, the changes must occur at the master organization as well as any inventory organization. The changes made to attributes controlled at the master level will be propagated to the inventory organizations.

◦ If you plan to have some of the Attributes controlled at the master level and some at the organization level, you must set the ESIORAControlAttributesMaster configuration flag to true.

• The Oracle Applications concurrent program for Item Import exists and has not been modified. The TIBCO process calls the concurrent program, therefore the concurrent program does not have to be scheduled in Oracle.

• Oracle instances will have only one Item Master Organization as recommended by Oracle in the Oracle Inventory User's Guide 11i.

• Items exist in the organization in which they are to be updated.

• Windchill PDMLink and Oracle Applications data match before the item is updated in Oracle Applications.

• The context is set to the site in Windchill PDMLink so that part numbers are unique within an instance of Windchill PDMLink.

• It is assumed that all UOM (unit of measure) that are being passed to Oracle Applications are appropriately mapped (using ESIORALookup.properties) and in sync with Oracle Applications UOMs. Oracle Applications does not throw an exception if the UOM is sent as a blank. Instead it assigns the default UOM (EA) to the item. UOM creation and mapping definition is a one-time process that must be carried out during the implementation phase and before production. This ensures that all UOM in Windchill have appropriate lookup entries in the ESIORALookup.properties file.

• ESI services can be configured to process control characteristics that are associated to a part. However, these are not published to Oracle Applications.