Identifying Problems with Change Notices (CNs)
This section describes common problems and possible causes that relate to CNs. A bulleted list of common problems follows. If you do not see the problem you are experiencing in the list, or the suggested course of action does not solve the problem, contact your system administrator.
• Can’t create a CN
• Can't see the CN in Oracle Applications, even though Windchill ESI indicates a successful transaction
• A Change Request is always created for an auto-generated Change Notice
Can’t create a CN
The following can cause this problem:
• Invalid or missing attributes
• Incorrect date format
• Incorrect or invalid ESITarget organizations assigned to part
• User is looking in wrong ESITarget organization(s) in Oracle Applications
• CN with that number already exists in Oracle Applications
• Invalid effectivity date(s) (cannot use dates in the past)
• Effectivity offset (middleware global variable) set incorrectly
• Serial or lot number passed in ESI response does not exist in Oracle Applications as a unit number.
• One or more BOM components have empty serial or lot effectivity and the effectivity control of the assembly has been set to Unit
• Effectivity priority has not been set appropriately in the file ESIORALookups.properties.
• An attempt is made to create a Unit effective BOM as a sub-assembly of a Date effective BOM.
Can't see the CN in Oracle Applications, even though Windchill ESI indicates a successful transaction
The CN Enabled flag (middleware global variable) is set incorrectly.
A Change Request is always created for an auto-generated Change Notice
With the preference Automatically Generate Change Notice set to Yes, and with the preference Change Notice without Change Request set to No, this is the expected behavior. To stop Change Requests from being created for auto-generated Change Notices, set the preference Change Notice without Change Request to Yes.