Change Notices
Windchill ESI allows you to publish Change Notices (CNs) created within Windchill ESI to a distribution target such as Oracle Applications. Publishing CNs from Windchill ESI also includes the publishing of all part, BOM, process plan and operation objects that are listed (the item process is used to maintain item attributes other than part revisions). By enabling this capability in Windchill ESI, users can also create and change parts, BOMs, process plans and operations when publishing the CN.
Windchill ESI creates all ECOs in Oracle Applications so that they have object revisions and BOM objects listed on them. When processing the ECO in Oracle Applications, Windchill ESI initially sets the status of each ECO to Scheduled in Oracle. An administrator should schedule the Automatic Engineering Change Order Implementation concurrent program to run at predetermined intervals for all ESI-related organizations. This program sets the status of all recently-created (Scheduled) ECOs to Implemented based on effectivity. This is a critical processing step, as it makes the ECOs effective. For more information, see the Windchill Enterprise Systems Integration Administration Guide - Oracle Applications.
When you associate various attributes to a CN in Windchill PDMLink, Windchill ESI passes the attributes to the EAI software components. The following attributes are passed (the list consists of both attributes of the resulting objects and those of the CN itself):
• Number (Change Number)
• Description (Change Number Description)
• Part Number / Assembly Part Number
• Part Version / Assembly Part Version
• Part Start Effectivity Date / Assembly Part Start Effectivity Date
• Component Part Number
• Component Line Number
• Component Quantity
• Component Operation Sequence Number
• Reference Designator
• Substitute Component
• Distribution Targets
• Serial Number Effectivity Start Number
• Serial Number Effectivity End Number
• Lot Number Effectivity Start Number
• Lot Number Effectivity End Number
• Process plan (Routing) part number
• Operation Label
• Department for the Operation
• Resource Number for the operation
• Scheduled Flag for Resources
• Usage Rate for Resources
|
|
Note the following:
• While all attributes listed are passed, not all of the attributes are CN attributes. The rest are attributes on the objects being changed and are listed in their respective sections. For example, the Part Number attribute will be listed in the Part element section of the response file.
• When using the CN-centric mode of publishing data, with the distribution target attribute Publish Related Documents when Publishing a Change Notice set to Yes, documents associated to objects in the Change Notice are published as well.
• Documents, and CAD document structures, and option sets that reside as resulting objects in the Change Notice are always published.
|
Once the CN data has been published by Windchill ESI Services, the EAI software components map the Windchill CN attributes to Oracle Applications ECO attributes. The following table shows the mapping of Windchill CN attributes to Oracle Applications ECO attributes.
Windchill PDMLink and Windchill MPMLink CN to Oracle Applications ECO Attribute Mapping
|
Windchill PDMLink CN Attribute
|
Oracle Applications ECO Attribute
|
|
Number (CN Number)
|
ECO Name
|
|
Name (CN)
|
ECO Description
|
|
Description
|
Reason for Change
|
|
Part Number / Assembly Part Number
|
Revised Object Name
|
|
Part Version / Assembly Part Version
|
New Revised Object Revision
|
|
Part Start Effectivity Date / Assembly Part Start Effectivity Date
|
Start Effective Date
|
|
Component Part Number
|
Component Object Name
|
|
Component Line Number
|
Object Sequence Number
|
|
Component Quantity
|
Quantity per Assembly
|
|
Reference Designator
|
Reference Designator Name
|
|
Substitute Component
|
Substitute Component Name
|
|
Distribution Target
|
Organization
|
|
Reason for Change Description
|
Description
|
|
Component Operation Sequence Number
|
Object Operation Sequence Number
|
|
Start Serial Number Effectivity / Start Lot Number Effectivity
|
From Unit Number
|
|
End Serial Number Effectivity /End Lot Number Effectivity
|
To Unit Number
|
|
Process plan (Routing) Part Number
|
Revised Object Name
|
|
Operation Label
|
Operation Sequence Number
|
|
Department for the Operation
|
Department
|
|
Resource Number
|
Resource
|
|
Scheduled flag for resources
|
Scheduled flag
|
|
Usage rate for resources
|
Usage Rate
|
The attribute Distribution Target in Windchill PDMLink identifies the distribution target in which the CN should be created. The EAI software components use this information to communicate with the correct target data source and pass organization information to it.
Some attributes that are passed from Windchill PDMLink are passed to the distribution target from the EAI software components without transformation; however, there are a few attributes that contain values that are either modified or cross-referenced by the EAI software components.
Windchill PDMLink passes the Start Effectivity Date in the format YYYY-MM-DD 24HH:MM:SS. Windchill ESI assumes that the time zone is configured across Windchill PDMLink, TIBCO, and Oracle Applications.
The Action (relative to the CN) for CN Headers, Revised Objects (Parts), Revised Items (BOM Headers), and Process Plans is cross-referenced in the EAI software components. The table below shows the possible available Windchill PDMLink action values and the corresponding Oracle Applications values that are passed from the EAI software components to Oracle Applications.
Windchill Action Value (Relative to the CN) to Oracle Applications Transaction Type Value Mapping
|
Windchill Action Value
|
Oracle Applications Transaction Type Value (Database Value)
|
|
Added CNs, Parts, BOMs, Process Plans
|
Create (CREATE)
|
|
Changed Parts, BOMs, Process Plans
|
Update (UPDATE)
|
|
|
By design, Windchill ESI does not support Update or Delete transaction types for an ECO. Windchill PDMLink may only publish new (Create) CNs.
|
The absolute Action for Revised Components, Reference Designators, Substitutes and Operations is cross-referenced in the EAI software components. The following table shows the possible available Windchill PDMLink action values and the corresponding Oracle Applications Add-Change-Delete (ACD) Type values that are passed from the EAI software components to Oracle Applications.
Windchill Absolute Action Value to Oracle Applications Add-Change-Delete (ACD) Type Value Mapping
|
Windchill Action Value
|
Oracle Applications Add-Change-Delete (ACD) Type Value (Database Value)
|
|
Added BOM Components, Substitutes, Reference Designators, Operations
|
Create (1)
|
|
Changed BOM Components, Operations
|
Update (2)
|
|
Deleted BOM Components, Substitutes, Reference Designators, Operations
|
Delete (3)
|
|
|
By design, Windchill PDMLink does not support Changed Substitutes or Changed Reference Designators. The same result is accomplished via Delete and Create actions.
|
There are some attributes that are required within Oracle Applications to create or change ECOs that are not provided by Windchill PDMLink. In these instances, Windchill ESI defaults the values in the EAI software components prior to passing the data to Oracle Applications. The following table lists the Oracle Applications ECO attributes that are defaulted in Windchill ESI and their defaulted values.
Oracle Applications ECO Default Values
|
Oracle Applications ECO Attribute
|
Default Value
|
|
ECO Header Change Type Code
|
Product Change (Prod Chg)
|
|
ECO Header Approval Status Type
|
Approved
|
|
Revised Component Operation Sequence Number
|
1 (1)
|
|
ECO Header Status
|
Scheduled (4)
|
