Product Family Information Is Collected By ASCP But Not Collected Into Demantra
(Doc ID 459663.1)
Last updated on AUGUST 19, 2019
Applies to:Oracle Demantra Demand Management - Version 220.127.116.11 and later
Information in this document applies to any platform.
Users performed ASCP standard data collections to gather Product Family data to the ASCP module. But after they ran the concurrent request Collect Shipment and Bookings History, they find only one product family code got collected when Demantra Collections - Shipment and Booking History - was run. Users checked in tables t_src_item_tmpl and t_ep_item but again only found one Product Family Code Collected. There are several listed in table msc_system_items from the standard data collections run
1. Ran ASCP standard collection. Product Family information got collected and could be found in msc_system_items table
2. Ran Demantra Collection of Shipment and Booking History. The collection completed with normal status, but only one product family code got collected
2a. Demand Administrator Responsibility
2b. Nav: Collections > Oracle Systems > Shipment and Booking History
2c. Find Items
2d. Notice that only one Product Family was collected
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