By JeffG-Oracle on Jun 12, 2012
Latest Demantra and VCP certification is released. Demantra 220.127.116.11, patch 14076370. VCP 18.104.22.168, Use note 746824.1.
All available at My Oracle Support.
This patch resolves:
1. Bulk loader causing crash on Linux
2. Various PE related issues
3. Simulation with DP shapes. Consecutive simulation run, when DP shapes were introduced, was failed because vector of DP shapes used by engine were not reset between engine runs in simulation mode.
Available at https://support.oracle.com
Oracle has released 14810986 available ay My Oracle Support, https://support.oracle.com
1. This a re-release. The original patch has been replaced.
2. This is not customer-specific. It is a generic EP_LOAD patch that improves performance for 7.3.1.x installations.
Proceed to document 1448266.1, Demantra Non Invasive Partial Schema Export Utility Extracting Partial Schema Dumps for Analysis. In this document you will find instructions and 2 SQL scripts. Give it a try. If you have a problem, feel free to post to this BLOG or the community located at:
A USA based company is assessing Demantra Trade Promotion Management (TPM) capability. It appears that SOX
is necessary in their case due to the nature of what TPM does and the necessity for auditability. Do we
have any detail on SOX compliance for Demantra?
SOX compliance with regards to IT:
1. Requires auditing of data changes done by who, what, when
a. Audit trail profiles can be set up for key financial series and view them in audit trail reports
b. One functionality we do not have which typically is asked for is user login history. We have only
active sessions, history is not available.
2. Segregation of duties
a. With respect to TPM, you could have deduction and financial analyst for settlement be different
from promotion creator, promotion approver or sales team.
b. Budget Approver for funds can be different from funds consumer.
c. Promotion creator can be different than promotion approver
d. For a US customer you may have to write some custom scripts to capture promotion status change
and produce an external report as part of compliance.
One additional requirement is transparency of forward commitments entered into with retailers / distributors
for trade spending, promotions. Outside of Demantra - Consumer Goods Trade Funds Analytics.
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.
Demantra is a Data Base resource intensive application.
- Evident from large implementations
- Large-scale implementations are global solutions across multiple regions or
retailer oriented store-level solutions - Require very large demand data
repositories storing billions of data points.
Common Demantra Performance issues
- Poor worksheet response times
- Longer Batch Engine run times
- Extended Simulation runs
- Prolonged Data loads
- Slow running user updates
These issues can be addressed by appropriate DB setup and tuning activities
This customer has been live on a Demantra VMI implementation and suddenly reported worksheet performance issues.
Sales_Data was ~32M records, non-partitioned
Analyze_Schema was not being run
Did a chained row count after Analyze_Schema – 48%
Recommended Rebuild_schema and worksheet performance improved 60% on average
This is a Demantra DM/PTP/DSM implementation. Just before UAT customer loaded full volume of Sales history,
Promotion and Settlement data and started experiencing serious worksheet performance issues.
MDP_Matrix=1.5M; Sales_Data=30M; Promotion_Data = 22M;
- CBO parameter changes
- Relocating null and empty columns in very large tables at the end of the row
- Sales_Data partitioning
- Reorder of Data by PK
- Worksheet specific Indexes
Performance Improvements reported:
Series Config Changes, 21%
GL Data Trim, 8%
Reorder Data by PK, 32%
Worksheet Cache Refresh, 73%
Here is a summary for relase 22.214.171.124 install/upgrade/features
See the following for details.
This blog delivers the latest information regarding performance and install/upgrade. Comments welcome