Constituent Product for a Combination Product is not Mapped Correctly to License (Doc ID 2855214.1)

Last updated on MARCH 14, 2022

Applies to:

Goal

Incorrect data is populated in CONS_LICENSE_ID field of CASE_PMOA_CONS_RELATION table when the constituent product has multiple device licenses for the same country and the license with the least LICENSE_ID in the Product configuration had no data in the License number field.

The expectation is that CONS_LICENSE_ID in the CASE_PMOA_CONS_RELATION table is populated with the data from the Product configuration for which the license number matches with the Combination Product configuration in Flexible code list.

This affects the data population of the element Brand name in eVAERS report.

Steps to Repeat:

1. Create a product with three licenses
2. Create one device license with a blank license number (create this one first so that it has a lower license_id key)
3. Create a second device license with a license number populated (such as "ABC")
4. Create one drug license
5. Configure a single-entity combination product using the newly created license with "ABC" populated as the constituent product and the drug as the primary product
6. Create a case with the combination product
7. Note that the CASE_PMOA_CONS_RELATION table populates the license_id for the constituent product as the device license with a blank, which is not expected since the user explicitly entered the license number "ABC"

Solution

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