This chapter covers the following topics:
The following paragraphs contain project manufacturing validations. Types of validations are as follows:
The system validates the project and task segments of a locator based on the value of the Project Control Level parameter you set up in Organization Parameter. The following table describes the validation logic:
| Project Control Level | Project Segment | Task Segment |
|---|---|---|
| Null | Cannot enter any value. | Cannot enter any value. |
| Project | Optional. | If Project is entered, Task is optional. If Project is not entered, Task cannot be entered. |
| Task | Optional. | If Project is entered, Task is mandatory. If Project is not entered, Task cannot be entered. |
The following explains purchase order transactions, including deliveries, returns, and adjustments.
When you perform a Purchase Order Delivery transaction for a project purchase order, the system defaults the project and task from the distribution line of the purchase order to the receiving locator.
If you define Item Transaction Defaults for receiving locators for specific items in Inventory set up (provided these are physical locators), the system concatenates the default locator with the project and task references from the purchase order distribution line when it is received into inventory.
If you update the project and task on the receiving locator, they must match the project and task exactly on the distribution line of the purchase order.
When you perform a Purchase Order Return transaction, the system defaults the project and task from the purchase order distribution line to the from locator.
If you update the project and task segments of the from locator on a purchase order return, they must match the project and task exactly on the purchase order distribution line.
When you perform a Purchase Order Adjustment transaction, the system defaults the project and task from the purchase order distribution line to the locator.
If you update the project and task segments of the locator on a purchase order adjustment, they must match the project and task exactly on the purchase order distribution line.
Note: You cannot use a project locator for all the above transactions if the purchase order distribution does not have project and task.
The system applies the Common Validation logic to the following transactions:
Miscellaneous Issue
Miscellaneous Receipt
Subinventory Transfer
Locator Transfer
Interorganization Transfer (Direct)
Internal Order Interorganization Transfer (Intransit)
Cycle Count Adjustment
Physical Count Adjustment
Validations performed in Work In Process include discrete job completion and materials information.
When you create a project discrete job (either manually or from the Planner Workbench), the system defaults the project and task from the project discrete job to the project and task segments of the completion locator. If you have assigned a completion locator (common locator) to the routing, the system concatenates the common locator segments with the project and task to create a project locator.
When you update the project and task on the Project Discrete Job, the system re-defaults the project and task segments of the Completion Locator.
If you update the project and task segments of the Completion Locator, they must match the project and task exactly on the Project Discrete Job header. They cannot be null.
When you perform a Completion Transaction, the system defaults the Completion Locator from the Project Discrete Job header.
If you update the project and task segments of the Completion Locator, they must match the project and task exactly on the Project Discrete Job header. They cannot be null.
When you define a project discrete job for an item that has a bill of material, the bill is copied to the project discrete job. If the components are hard pegged (their pegging attribute is set to either Hard Pegging or End Assembly/Hard Pegging), then the system defaults the project and task from the project discrete job header to their supply locator. If you have assigned supply locators (common locator) on the bills of material, the system concatenates the supply locators with the project and task to create a project locator.
If you update the project and task on the project discrete job, the system re-defaults the project and task segments of any hard pegged components.
If you update the project and task segments of the supply locator for any components of a project discrete job, they must either match the project and task exactly on the project discrete job or be null.
If the components are soft pegged, (their pegging attribute is set to either Soft Pegging or End Assembly/Soft Pegging) the system does not default the project and task segments to the supply locators. You can optionally override the default and assign the project and task to the supply locator. The system validates the project and task against the project and task from the project discrete job header.
The system validates the supply locator for a Component Issue Transaction for a project discrete job. The supply locator must satisfy one of the following criteria:
No project/task reference on the supply locator.
The project and task on the supply locator must match the project and task exactly on the project discrete job.
Same project but different task, if you check the parameter Allow Cross Project Issues in the PJM Organization Parameters window.
A different project with the same planning group association but not necessarily the same cost group as the project on the project discrete job if you check the parameter Allow Cross Project Issues in the PJM Organization Parameters window.
If you enter or update the project and task segments of the completion locator on a Return Assembly to WIP Transaction, they must match the project and task exactly on the project discrete job.
If you enter or update the project and task segments of the supply locator on a Component Return, they are validated and must satisfy one of the following criteria:
No project/task reference on the supply locator.
The project and task on the supply locator must exactly match the project and task on the project discrete job.
Same project but different task, if you check the Allow Cross Project Issues parameter.
A different project with the same planning group association but not necessarily the same cost group as the project on the project discrete job, if you check the Allow Cross Project Issues parameter.
When you perform a project work order-less completion, you must specify the assembly, quantity, project, or project and task, and other information. If you have set up a default completion locator on the routing, the system defaults it in the transaction for the transaction. If you have not set up a default completion locator, you can specify one for the transaction. When the transaction is saved, the system defaults the project and task from the transaction to the completion locator. The project and task information on the transaction and the locator segments project and task must match.
When you perform a work order-less completion against a project flow schedule, the system defaults the project and task information from the flow schedule into the project and task fields and into the project and task segments in the locator. If you enter or update the project and task segments of the locator on the Work order-less completion transaction, they must match the project and task exactly on the project flow schedule
Work order-less completion automatically backflushes all operation pull, assembly pull, and push components. The system builds the supply locators for the components by concatenating the supply locator from the item and the project or project and task you specify.
Note: You cannot use a project locator as completion locator or supply locator for all the above transactions against a non-project (common) discrete job.
Validations in shipping include, validating pick release.
When you perform Pick Release for a project sales order, the system ensures that you can only pick release from the project locators that have the same project and task as the sales order line, unless you are in a Warehouse Management organization.
When you select Allow Cross Project Pickwave Allocation in the Project Parameters page, pick release is allowed from project locators that have different project and tasks for the sales order. While the Rule Engine takes precedence, the Allow Cross Project Pickwave Allocation check box has to be enabled for the Rule Engine to work with allocation from different projects and tasks.
Note: The Allow Cross Project Pickwave Allocation check box in the Project Parameters page does not control cross project allocation in non-WMS Organizations.
Related Topics
See Setting Up Picking Rules in the Oracle Warehouse Management User's Guide
Overview of Pick Release, Oracle Shipping Execution User's Guide
Completing Discrete Jobs, Oracle Work in Process User's Guide
Overview of Building Discrete Jobs, Oracle Work in Process User's Guide
Project Jobs, Oracle Work in Process User's Guide
Approving Physical Inventory Adjustments, Oracle Inventory User's Guide
Approving Cycle Count Adjustments, Oracle Inventory User's Guide
Performing Miscellaneous Transactions, Oracle Inventory User's Guide
Transferring Between Subinventories, Oracle Inventory User's Guide
Inter-Organization Transfers, Oracle Inventory User's Guide
Receiving Transactions, Oracle Purchasing User's Guide