My Oracle Support Banner

Costs Are Not Collected Correctly When Using Task Autoassignment Rules (Doc ID 363388.1)

Last updated on MARCH 20, 2018

Applies to:

Oracle Project Manufacturing - Version 11.5.10.2 and later
Information in this document applies to any platform.

Symptoms

On 11.5.9 in Production:
Costs are not kept in the correct task according to Task AutoAssignment Rules



STEPS
Example BOM
Assembly1
-> Comp1
-> Comp2
-> Comp3
Example WBS
Project1
->Task1
->Task2
->Task3
->Task4
Task AutoAssignment Rules
Default Task = Task4
Comp2 = Task2
Comp3 = Task3
Assembly1 = Task1
1. From Oracle Work In Process, Create Discrete Jobs for Assembly1, Comp2.
2. From Oracle Work In Process, Issue WIP Material to Comp2 Discrete Job.
3. From Oracle Project Manufacturing, Costs are collected and imported to projects.
4. From Oracle Project Manufacturing, Expenditure Inquiry, WIP Material cost shows under Task2.
5. From Oracle Work In Process, Complete Discrete Job for Comp2.
6. From Oracle Work In Process, Issue Comp2 to Discrete Job for Assembly1
7. From Oracle Project Manufacturing, Costs are collected and imported to projects.
8. From Oracle Project Manufacturing, Expenditure Inquiry, WIP Material cost is moved from Task2
to Task1.


The costs are moved from the Rotor task to the Unit Assembly task. Expect the Rotor Assembly costs
to stay at the Rotor Task.

.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.