This chapter covers the following topics:
Oracle Project Manufacturing enables you to enter project or project and task on various entities within Oracle Applications. The following table provides a list of these entities and cites the documentation where you find can detailed information.
| Product | Form/Window, Region | Documentation Reference |
|---|---|---|
| PJM | Project Parameters | Assigning Project Parameters, Oracle Project Manufacturing User's Guide |
| APS | Planner Workbench | Planner Workbench/User Interface, Oracle ASCP and Oracle GATP Server |
| INV | Stock Locator | Defining Stock Locators, Oracle Inventory User's Guide |
| INV | Transaction Type | Defining and Updating Transaction Types, Oracle Inventory User's Guide |
| INV | Move Orders (Projects/Tasks tab) | Oracle Inventory User's Guide |
| INV | Transaction Move Orders | Oracle Inventory User's Guide |
| INV | Transaction Interface, Other alternative region | Viewing and Updating Transaction Open Interface Activity, Oracle Inventory User's Guide |
| MRP | Forecast Entries | Defining a Forecast, Oracle Master Scheduling/MRP and Oracle Supply Chain Planning User's Guide |
| MRP | MDS Entries | Defining Schedule Entries Manually, Oracle Master Scheduling/MRP and Oracle Supply Chain Planning User's Guide |
| MRP | MPS Entries | Defining Schedule Entries Manually, Oracle Master Scheduling/MRP and Oracle Supply Chain Planning User's Guide |
| MRP | MPS Workbench, Implement | Implementing Planned Orders, Oracle Master Scheduling/MRP and Oracle Supply Chain Planning User's Guide |
| ONT | Sales Orders, Project Sales Orders (Line Items tab), Project alternative region |
Defining Sales Order Line Project Information, Oracle Order Management |
| ONT | Schedule, Schedule Sales Order), Project tab | Updating Lines to Schedule, Oracle Order Management |
| ONT | Sales Orders, Option Lines (Option) {Tools Menu>Show Line Details} | Choosing Options, Oracle Order Management |
| PO | Requisitions, Distribution (Distribution), Project alternative region | Entering Requisition Distributions, Oracle Purchasing User's Guide |
| PO | Requisitions, Preferences (Preferences), Project Information alternative region | Entering Requisition Preferences, Oracle Purchasing User's Guide |
| PO | Purchase Orders, Distribution (Distribution), Project alternative region) | Entering Purchase Order Distributions, Oracle Purchasing User's Guide |
| PO | Purchase Orders, Preferences (Preferences), Project Information alternative region | Entering Purchase Order Preferences, Oracle Purchasing User's Guide |
| PO | Releases, (Distribution), Project alternative region | Entering Release Distributions, Oracle Purchasing User's Guide |
| PO | Releases, Preferences | Oracle Purchasing User's Guide |
| PO | RFQ, More alternative region | Entering RFQ Lines, Oracle Purchasing User's Guide |
| PO | Quotations, More alternative region | Entering Quotation Lines, Oracle Purchasing User's Guide |
| QA | Collection Element, Plan | Collection Elements, Oracle Quality User's Guide |
| WIP | Discrete Job, Project alternative region | Defining Discrete Jobs Manually, Oracle Work in Process User's Guide |
| WIP | Pending Jobs and Schedules, Discrete region | Processing Pending Jobs and Schedules, Oracle Work in Process User's Guide |
| WIP | Work Order-less Completions | Performing Work Order-less Completions, Oracle Work in Process User's Guide |
| WSH | Release Sales Order | Oracle Shipping Execution User's Guide |
| WSH | Shipping Transactions (Lines and Containers tab) | Oracle Shipping Execution User's Guide |
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 the Organization Parameters. 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. |
This section describes purchase order return and delivery transactions and their related validations.
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 are validated against, and must exactly match, the project and task on the purchase order distribution line.
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 the Inventory setup (if 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 its inventory destination.
If you update the project and task on the receiving locator, they are validated against, and must exactly match, the project and task on the distribution line of the purchase order.
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 are validated against and must exactly match the project and task on the purchase order distribution line.
Note: You can not use a project locator for all the above transactions if the purchase order distribution does not have projects and tasks.
The system applies the Common Validation logic to the following transactions:
Miscellaneous Issue
Miscellaneous Receipt
Subinventory Transfer (used for transferring material from one subinventory to another for a given project task)
Project Transfer
Interorganization Transfer (Direct)
Internal Order Interorganization Transfer (Intransit)
Cycle Count Adjustment
Physical Count Adjustment
Project Move Orders (used for transferring material from one subinventory to another for a given project task with an optional approval cycle)
This section describes the validations in Work in Process.
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 are validated against and must exactly match the project and task 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 are validated against and must exactly match the project and task 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 are validated against and must either match the project and task 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 this 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 exactly match the project and task on the project discrete job.
Same project but different task, if the parameter PJM: Allow Cross Project Issues is set to Yes.
A different project with the same cost group and planning group association as the project on the project discrete job. The parameter PJM: Allow Cross Project Issues is set to Yes.
If you enter or update the project and task segments of the completion locator on a Return Assembly to WIP Transaction, they are validated against and must exactly match, the project and task 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 the profile PJM: Allow Cross Project Issues is set to Yes.
A different project with the same cost group and planning group association as the project on the project discrete job. The profile PJM: Allow Cross Project Issues is set to Yes.
When you perform a project work orderless 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 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.
Work orderless completions automatically backflush 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 can not use a project locator as a completion locator or supply locator for all the above transactions against a non-project (common) discrete job.
This section describes 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.
Oracle Project Manufacturing is not uptaking the Oracle Projects Validations API which necessitates approval for adding a child task. As a result, an unapproved child task may lead to the failure of the transaction during an import from Project manufacturing to Oracle Project. As a Project Manufacturing user, you should ensure that only an user with the appropriate function security creates the task using change document. Tasks created using change documents do not need approval. Should the user not have the function security to create the task, the task approval workflow should be set to auto approval.
See:
Creating Financial Tasks in a Change Document in Oracle Projects Fundamentals
Creating Financial Tasks in Oracle Project Management User Guide