Tuesday Aug 14, 2012

I am running EBS Collections: Legacy Systems > Shipment and Booking History -Self Service to load DemHistory.dat sample data.
Only t_src_sales_tmpl table is populated, but t_src_item_tmpl and t_src_item_tmpl are not populated. This is expected, as I do
not have the same items and locations on EBS as this is sample data.

As per Implementation guide, Prior to launching this collection, complete ASCP collections for the legacy instance. I followed
document 402222.1 and downloaded QATempate. It includes many .dat files such as Category.dat, item.dat ....

Questions:
1. Would you please advise if I need to load each set of *.dat file in order to load Booking&shipments data? Or only specific .dat
files like TradingPartner.dat and Item.dat?

2. It seems the sample data from TradingPartner.dat does not match what in DemHistory.dat sample file. Is this expected?

1. User needs to load the dat files required for the reference data only.
2. I am not sure about this question. Does he mean that the example given in TradingPartner.dat and DemHistory.dat do not match ?
If yes, then ok.

For the actual data load, they need to load the customer and sites first, and then load sales data for them using DemHistory.dat.

When we run Shipment and Booking History Download, the date range of the data profile Purge History Data is updated at run time with
the date range chosen while running the concurrent program, Shipment and Booking History Download.

We noticed that everytime we run netchange collections, the date parameters on the Purge HIstory Integration Interface are set based on
the dates chosen in the Concurrent program Shipment and Booking History Download.

But, when we run the concurrent program in Complete refresh mode, the dates on the Purge History Integration Interface are set with dates
which fall outside the history and hence no history is purged. Is this intended design that History will not be purged during Demantra Complete
Refresh collections, and only during Net Change collections?

To answer your question, history should be purged for both net-change and refresh collections. If this is not working please contact Oracle
Support

Note, the complete refresh collection is not meant for regular weekly runs. Ideally it should be run only once (boot strap) and that too
only if you want to collect all the data from Order Management (OM) into Demantra.

You should run only net-change collection for regular runs. Also for bootstrap data load, if OM has more data than required for Demantra,
net-change collection with appropriate date range should be run.