This chapter covers the following topics:
This chapter details the procedures used to track and implement dispositions, using the Solutions Templates. These procedures include the various methods to initiate the disposition, assign dispositions, and set up automated execution of dispositions.
Process Flow for Disposition Lifecycle
Depending on the configuration chosen, the disposition tracking and execution system can exist independently or linked to the nonconformance tracking system. The disposition set of collection plans can be initiated via direct data entry or transaction association. See: Setup Steps for information on linking collection plans and associating them with transactions.
When the decision has been made to log a disposition, the disposition header plan is invoked; you are required to enter the disposition source. If you navigated to the disposition header from the nonconformance system, the nonconformance number and associated information is copied to the disposition header.
Rules can be set up to assign an owner to the disposition, based on the disposition source. If you set Default Values to YES, some elements are defaulted from the nonconformance master. Set Default Values to YES only when a nonconformance set of plans are associated with the disposition system.
The details on the disposition header include the disposition source, source reference identifier, item, disposition owner, the source owner, and respective e-mail addresses. Background actions automatically update Date Opened, Date Closed, and Days to Close.
When the disposition is logged, an e-mail or workflow notification is sent to the disposition owner and the source (nonconformance) owner.
After the disposition owner is notified about the disposition, the disposition uses the View Disposition and Update Disposition menu options within Oracle Quality to view and/or update the disposition.
The disposition owner reviews the disposition and other associated information such as nonconformance information, to understand the material disposition history. The owner makes the determination of what disposition and disposition actions need to be executed.
The disposition owner enters detail lines on the disposition, using the disposition details collection plan. The Default Values can be used to default information, based on the nonconformance master (explained in the previous step).
Using the details plan, the owner can break down the disposition quantity and assign separate disposition actions to appropriate personnel.
We will assume that a nonconformance was reported, during Work In Process (WIP) inspection, on a component for a disposition quantity of ten. The nonconformance review process determined that the component disposition involves reworking a quantity of five of the component, enabling the job to progress. A quantity of three will be returned to the vendor, and a quantity of two will be scrapped.
To model this disposition, the disposition owner needs to enter three lines within the disposition details plan:
1. The first line indicates that the first disposition of five will be REWORK, and the action is to create a rework job to rework the component (disposition action: WIP_REWORK_JOB).
2. The second line indicates that the disposition is Return to Vendor (RTV) for a quantity of three. Because the disposition was return to vendor for a nonconforming component in WIP, this requires a two-step process with two separate lines. The first line contains a RTV disposition and WIP_COMP_RETURN disposition action, enabling the component to return to a Material Review Board or quarantine subinventory. The second line contains a RTV disposition and MANUAL RTV disposition action. This requires that the RTV transaction is initiated within Oracle Inventory after the nonconforming component is returned to inventory.
Note: MANUAL RTV is not a seeded disposition action element value, however, you can easily add it. See: Setup Steps, Step 4.
3. Because performing a WIP component scrap is not automated, the component scrap of two needs to be entered as two separate lines. The first line contains the SCRAP disposition and WIP_COMP_RETURN disposition action. The second line contains the SCRAP disposition and INV_SCRAP_ISSUE disposition action. INV_SCRAP_ISSUE is an Inventory Account alias for inventory scrap.
Because each disposition can be executed by different people with different job functions, the owner assigns the disposition execution, using the Action Assigned to or Implementation By collection elements.
When the disposition action assignees and implementors receive an e-mail or workflow notification, they review the disposition actions to implement within the disposition details collection plan. The implementor may update the information on the disposition line to make any corrections to the current location or the condition of material to be dispositioned.
The implementation collection plans are primarily used to execute the automated disposition actions. If the disposition involves no automated execution, the implementor can update the disposition detail line with the disposition implementation.
When the implementor is ready to implement the automated disposition action, the disposition action value determines the WIP or Inventory disposition collection plan.
After navigating to the implementation plan, the implementor can use Default Values to default information from the nonconformance master, as discussed earlier. When ready to execute the disposition action, the implementor will update the Launch Action collection element to YES, after entering the necessary collection elements for disposition execution. See: Appendix E -Collection Plans for information on the collection elements that need to be entered for each of the disposition actions.
The following table lists the automated disposition actions and the implementation plans containing the collection elements for executing the disposition:
|Disposition Action||Implementation Collection Plan|
|Creation of Inventory Move Order (INV_MOVE_ORDER)||Inventory Disposition|
|Inventory Scrap (INV_SCRAP_AAI)||Inventory Disposition|
|Component return to inventory (WIP_COMP_RETURN)||In-Process Disposition|
|Component issue to job (WIP_COMP_ISSUE)||In-Process Disposition|
|Creation of Rework Job (WIP_REWORK_JOB)||In-Process Disposition|
|Add rework operation (WIP_REWORK_OP)||In-Process Disposition|
|Move to rework operation (WIP_MOVE_REWORK)||In-Process Disposition|
|Assembly Scrap (WIP_MOVE_SCRAP)||In-Process Disposition|
The automated disposition actions are processed when initiated from the disposition implementation collection plans. If the disposition implementation action initiated from the collection plan fails, manual intervention is required. The implementor would need to manually correct the transaction in the respective destination module, then resubmit the transaction. After the submitted transaction succeeds, the implementor should manually update the disposition status to SUCCESS, and notify the appropriate personnel.
Appendix E - Collection Plans for information on the collection elements that need to be entered for each of the disposition actions
The disposition owner reviews the disposition lines and, if they have successfully been implemented, closes the disposition lines. The disposition is closed when all lines are closed. The nonconformance owner and other personnel are notified via e-mail or workflow notification.