For partners that build or integrate commercially available applications and service solutions with the Oracle Cloud Platform
For partners that provide implementation or managed services around Oracle Cloud Applications
Process Work Definition does not require item structure to assign components to the operation, however business has a requirement to end date a component and add a new component with the future effectivity date. In discrete world, this is possible by changing these dates on the item structure but since process WD do not have item structure how can the user change the effectivity date of the components?
By component, I assume you were referring to an operation item (input item). So say the process work definition requires input item A until Nov 30, then input item A will be replaced by input item B starting Dec 1.
If this is the use case, then you can use operation effectivity to accomplish this. Create a new work definition version, create a new operation by duplicating the existing operation, delete input item A from the new operation, add input item B to the new operation, then delete the existing operation from the new work definition version. Hope this helps.
Hi Yuana,
Yes, that is helpful. If i create a new work definition version than I can simply delete and add the new input item in the existing operation as the effectivity is at the WD level not at the operation level but this will result in a lot of WD versions. The effective start and end date field is already there on the component assignment UI page but it is just not updateable. Do I need to log an Idea for this?
If you create a new work definition version, then delete and add the new input item to an existing operation, this change applies to all the wd versions where the operation is effective (not only to the new wd version).
The start date and end date fields in the Assign/Edit Operation Item UI apply only to items that come from an item structure. Since there's no reference to an item structure in a process wd, and input items are added as ad hoc items, start date and end date fields are not applicable.
The thought is to allow use of a formula, which is what represents an item structure in process manufacturing. This will be evaluated based on customers feedback. Feel free to log an idea in the mean time. Thanks.
That is an important information so I appreciate your help on this. I will open an Idea on this as this is an important process for client without which they will not be able to go live.
If you create a new work definition version, then delete and add the new input item to an existing operation, this change applies to all the wd versions where the operation is effective (not only to the new wd version).
The start date and end date fields in the Assign/Edit Operation Item UI apply only to items that come from an item structure. Since there's no reference to an item structure in a process wd, and input items are added as ad hoc items, start date and end date fields are not applicable.
The thought is to allow use of a formula, which is what represents an item structure in process manufacturing. This will be evaluated based on customers feedback. Feel free to log an idea in the mean time. Thanks.