By JeffG-Oracle on Mar 08, 2012
I am using legacy collection to load product family into Demantra. In the soucre EBS/Value Chain Planning (VCP)
I can see my product family and member in the ASCP plan.
I would like to be able to have product family dimension populated in a Demantra Hierarchy. I have used demhistory
flat file to upload forecasts for my items (members) and I expect to have product family dimension populated.
I started to analyse demantra collection and EP launch, and it seems to me that stagging table T_SRC_ITEM_TMPL is
populated by process "Collect Level Type (2)" or perhaps a subprocess.
The stagging table stores the link between members and product family itself, ebs_product_family_code field, but it
is populated with default value (0).
The profile 'MSD_DEM: Master Org' is used for collecting item -> product family rollups into demantra.
Item to product family rollup needs to be available in ASCP under the master organization specified by the above profile.
This is a source side profile, and cannot be set by hand in case of legacy source. To set the value, you will need to run the
request 'Configure Legacy Profiles' from 'Demand Management System Administrator' responsibility. Parameters for this
request are as follows:
- Legacy Instance
- Master Org
- Category set
After running this, check for records in msd_dem_legacy_setup_params table. Then try running flat file load and verify
product family is populated in t_src_item_tmpl table in demantra schema.
Also the product family members/product family relationship comes from the msc_system_items table for the master organization,
not organization where product family/product members is defined
You can check for a link between members and product family in the master org within msc_system_items and then the product family
should be visible within Demantra.