Un-commoning a BOM

Oracle Support tells us (in Note 878976.1) that the system does not support this functionality, although an enhancement request has been logged.

We were in a situation where we had no choice but to un-common some BOMs. We found this script to be effective:

UPDATE bom_structures_b
SET common_organization_id     = NULL ,
common_assembly_item_id      = NULL ,
common_bill_sequence_id      = bill_sequence_id ,
source_bill_sequence_id      = bill_sequence_id
WHERE source_bill_sequence_id != bill_sequence_id

This script as written will un-common all BOMs. Obviously you can limit it to specific BOMs if you want to be more targeted.


Non-Reservable, Non-Nettable Locators

This is new functionality in R12 that we’ve been using at my current client. We wanted to create a “Putaway” locator in the stockroom that we could use for WIP job completions. Manufacturing would complete into this locator, then the Stockroom folks could transfer it from there to a more permanent storage.

We found that this worked well, but WIP Pick Release was allocating material from Putaway rather than the permanent storage location, so we wanted to make the Putaway locator non-reservable.

Using the new Material Status Definition form, we created an NRL status as below.

We then created the Putaway locator and assigned it this status.

Should work fine, right? Almost. There’s a “secret” profile option that has to be set before it all comes together:

I’m honestly not sure why this profile option exists. I can’t imagine a situation where a user would create additional material statuses and then not use them. I also can’t understand why Oracle would ship the application with this profile option set to null, and why null is interpreted as No. But that’s how it is…

Project Manufacturing

Oracle Project Manufacturing

I’ve been working with Support, Development and Product Management for the last few weeks to clarify some of the functionality around Project Manufacturing and how it integrates with other modules.

My client is using Advanced Supply Chain Planning, Work in Process and Inventory in a Project Manufacturing environment. We’ve seen that, by setting the Reservation Level to Planning Group in the ASCP options, we can use excess supply from other projects within the planning group for a particular project. When we release the job created from the Planner Workbench and pick release the components, the Component Pick Release function releases these materials from other projects within the planning group. Our issue comes when we try to transact the resulting Move Order and move the components into the staging subinventory. The Move Order Transaction fails because a project transfer is required during the move.

Strangely, if we navigate to the View/Update Allocations screen and transact from there, the move order processes successfully and the project transfer is effected.

Support told us that the error message is intentional and that our ability to process the transaction from the Allocations screen is a mistake. They intend to prevent this with a patch in the near future.

Project Manufacturing Development recommends that on-hand balances are reviewed for project ownership prior to running pick release and that project transfers are done were necessary before pick release is run. This is difficult for the client, as some WIP jobs include 200-300 components and a manual review would slow down the process considerably. They intend to continue to use the “backdoor” approach and avoid applying th patch that will stop them.

We understand that more than one customer has logged an enhancement request so that this functionality is available.