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

Last updated on JULY 03, 2023

Applies to:

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 in the Integration Repository delivered with the Oracle E-Business Applications in R12 and above.
Refer to <Note 1187585.1> - How to access Oracle IntegrationRepository
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.

Changes

Cause

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