My Oracle Support Banner

Records Remain in Table MSD_ST_ITEM_RELATIONSHIP With Process_flag=5 After Being Loaded Into Final Table MSD_ITEM_RELATIONSHIPS (Doc ID 2445191.1)

Last updated on AUGUST 19, 2019

Applies to:

Oracle Demand Planning - Version 12.2.4 and later
Information in this document applies to any platform.

Symptoms

On : 12.2.4 version, Planning Server in PROD

Users load data via legacy into staging table msd_st_item_relationships. They launch the DP Pre-Processor which then launches workers and these records are processed into msd_item_relationships table successfully. However the records at the end of the concurrent requests are still shown in the staging table with process_flag=5 even though concurrent request MSCPDCP: Planning Data Collection - Purge Staging Tables was part of the concurrent requests launched and completed successfully


EXPECTED BEHAVIOR
-----------------------
Expected the records to be purged from the staging tables after successfully being processed into the final table

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Load data into staging table msd_st_item_relationships
2. Launch DP Pre-Processor program with parameter Item, Categories and Level
3. All concurrent requests are successfully completed
4. Records remain in the staging table with process_flag = 5 even though concurrent request MSCPDCP: Planning Data Collection - Purge Staging Tables was run

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.