My Oracle Support Banner

Demantra Shipment Booking History Collection does not Limit the CTO Levels Data to Only Collected ORG Data (Doc ID 2757700.1)

Last updated on MARCH 04, 2021

Applies to:

Oracle Demantra Demand Management - Version 12.2.5 and later
Information in this document applies to any platform.

Symptoms

On : 12.2.5 version, LoadData

ACTUAL BEHAVIOR
---------------
 

When running Demantra collection Shipment and Booking History for only 2 Organizations , the BIIO_CTO_LEVEL and BIIO_CTO_POPULTION staging tables are populated with other organizations, not only those 2 selected.

The t_src_sales_tmpl and biio_cto_data are populated only for those 2 organization selected.
 

EXPECTED BEHAVIOR
-----------------------
The BIIO_CTO_LEVEL and BIIO_CTO_POPULTION tables to be populate with respect to two organizations levels only.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Enable only 2 organizations to be collected
2. Run Shipment and Booking History collections
3. Check data

 

Changes

 

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
Changes
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.