My Oracle Support Banner

BOMPEXPL.EXPLODER_USEREXIT - BOM Explosion API Works Differently In SQL Vs. Concurrent Manager (Doc ID 1266317.1)

Last updated on JULY 03, 2017

Applies to:

Oracle Bills of Material - Version 12.0.6 and later
Information in this document applies to any platform.
BOMPEXPL.EXPLODER_USEREXIT
--Checked for Currency on 14-OCT-2014--

Symptoms

The BOMPEXPL.EXPLODER_USEREXIT API works correctly to populate values in the temporary table, BOM_EXPLOSION_TEMP, using an anoymous block in SQL*Plus.
The same however only produces 1 row if run as a concurrent request.

API Details
The public API BOMPEXPL.EXPLODER_USEREXIT is documented in the API list available on the "irep" delivered with the Oracle E-Business Applications in R12 and above. The R11i versions were available here: http://irep.oracle.com/index.html.

Steps: Working
1. Run SQL to call BOMPEXPL.EXPLODER_USEREXIT.
2. Query BOM_EXPLOSION_TEMP.
3. See many rows (more than 1).

Steps: Not Working
1. Run Concurrent Request to call BOMPEXPL.EXPLODER_USEREXIT.
2. Query BOM_EXPLOSION_TEMP.
3. See ONLY 1 row << there should be many.

Business Impact
Cannot complete report requirements as the data is not accurate.

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!


In this Document
Symptoms
Cause
Solution
References


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