Customer Data Not Populated Into Demantra Tables On Running Collect Shipment And Booking History (Doc ID 471824.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Demantra Demand Management - Version 7.1.1 and later
Information in this document applies to any platform.
***Checked for relevance on 03-Jul-2013***


Symptoms

On 7.1.1 in Production:
Find On an integrated EBS-Demantra instance, the Customer Data (Customer Name, Customer Number,
Site, Account, etc.) is not getting populated into Demantra tables after running the Data Collections (both Standard Data Collections and Collect Shipment and Booking History). This data is available on ODS in Collected Data on the ASCP side (Standard Data Collections puts the data into the MSC_*** tables so this part of the process is working fine).



STEPS
The issue can be reproduced at will with the following steps:
1. Go to responsibility Demand Management System Administrator > Collections > Oracle Systems
> Standard Collection. A 'Complete Refresh' or 'Target Refresh' can be chosen. (making the
parameter 'SUPPLIERS/ Customers/ Orgs' to 'Yes')
then,
2. Go to responsibility Demand Management System Administrator > Collections > Oracle Systems
> Shipment and Booking History

3. For checking the collected data:
Go to Advanced Supply Chain Planner responsibility > Collections > View Collected Data

Also, it has been verified from the backend that data has not been updated in t_src_sales_tmpl,
t_src_loc_tmpl, t_ep_item, t_ep_organization and t_ep_ebs_customer tables





Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms