My Oracle Support Banner

WIP Mass Load - Job Requirements Are Exploded From BOM Definition On Unreleased Discrete Jobs Even Though ALLOW_EXPLOSION Is Set To "N" (Doc ID 2897854.1)

Last updated on APRIL 12, 2024

Applies to:

Oracle Work in Process - Version 12.2.10 and later
Information in this document applies to any platform.


Actual Behavior
ON WIP Massload, requirements on an unreleased discrete job are exploded from BOM definition even though allow_explosion is set to "N" in WIP_JOB_SCHEDULE_INTERFACE.

Expected Behavior
Requirements on an unreleased discrete job are not exploded from BOM definition when allow_explosion = N, bom_revision = NULL is set on WIP_JOB_SCHEDULE_INTERFACE.

Steps to Reproduce

  1. Create a discrete job for an item which BOM is not defined yet.
  2. Save the job then BOM Revision and BOM revision date is set to NULL.
  3. Add component items manually to the job.
  4. Define BOM for an assembly item.
  5. Using WIP Mass load, update some fields, like "Description" with allow_explosion = N, bom_revision = NULL.
  6. During WIP mass load, BOM Revision is updated and component is exploded from BOM definition.


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

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

In this Document

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