Summary

The eScript-based Product Model Analyzer helps Siebel product administrators inspect a selected product hierarchy, apply focused structural rules, and find catalog hot spots before they affect configurator, quoting, and order-capture performance.

Long-lived product catalogs grow as teams add products, reuse definitions, and extend models. Over time, inefficient relationships, oversized domains, redundant constraints, and inactive child products can remain embedded in active hierarchies. These patterns are difficult to detect through the standard Siebel UI because they are distributed across many product definitions.

The Product Model Analyzer is implemented in eScript and exposed through Siebel Business Services. Given a root product and selected rules, it recursively analyzes the product hierarchy and returns violations at the affected object and at each parent level with full path context. It also returns summary counts for the product, class, and attribute definitions involved.

When to use it - This is the practical in-environment option for targeted diagnostics on product families. It runs natively in Siebel and is a strong fit when administrators need quick analysis without deploying a separate analysis platform.

Key benefits

• Analyze inside Siebel. Work with live catalog data and existing access controls, without external infrastructure.
• Focus on a root product. Traverse a selected hierarchy and report violations with the relationship path that led to each finding.
• Find known structural hot spots. Use predefined rules to inspect oversized domains, anonymous classes, single-item domains, invalid product relationships, and referenced class IDs.
• Reduce redundant retrieval. The Product Broker builds structured product objects and caches catalog data during analysis.
• Deploy and invoke flexibly. Import through a SIF into a development workspace, then call the Business Service through REST, workflow, the Business Service Simulator, or eScript.
• Extend with eScript. Developers can add new rule-definition Business Services without changing the analyzer-engine logic.

How it works

The toolkit consists of three core Business Service modules: the PMA Engine, the PMA Product Broker, and Rule Definitions. It requires Siebel Tools or Siebel Web Tools access with a development workspace, Siebel REST API access with a valid session token when REST invocation is used, and adequate application-server capacity for the selected hierarchy.

• Import and deliver. Create a development workspace, import Product Model Analyzer Toolkit.sif, then deliver the workspace or work in Inspect mode.
• Select a scope. Send the root product ID, optionally its current or workspace version, and the rule methods to PMA - Engine using RunRules.
• Traverse top-down. The PMA Engine maps products by depth across the selected hierarchy.
• Apply rules bottom-up. The engine evaluates the selected Rule Definition Business Services from the deepest level upward, allowing child violations to roll up to their parents.
• Retrieve and cache data. The PMA Product Broker queries the Siebel data model, creates product-definition objects, and avoids redundant lookups through its local cache.
• Review and remediate. Use the returned summary metrics and violation paths to prioritize corrections, then rerun the same rules to verify the outcome.

Predefined rules

The included rules provide a starting point and can be extended by developers using eScript.

• Domain CountReports Class or Dynamic Class relationships whose domain items exceed an input threshold; the default is 50.
• Anonymous ClassFinds Class or Dynamic Class relationships with no defined target class.
• Single ProductFinds Class or Dynamic Class relationships that contain exactly one domain product.
• Product Relationship Has ClassFinds Product-type relationships where a class is set.
• Search Class IDFinds selected class object numbers in the product's class hierarchy and relationships.

Accessing the toolkit

Request the eScript-based Product Analyzer Toolkit through an Oracle Support Service Request for Siebel CRM and reference Patch ID 39161569. The package includes a ReadMe, a product-analyzer demo video, the Product Model Analyzer Toolkit SIF, REST input and output samples, and Business Service Simulator input and output argument files.

Conclusion

Siebel Product Model Analyzer using eScript provides a repeatable, in-environment way to inspect the product models that matter most. Start with the predefined rules on high-priority product families, triage violations by their performance impact, assign fixes, and rerun the analysis as part of catalog release hygiene.

When a team needs broad, catalog-wide and multi-hop analysis outside the live application workload, the property-graph-based analyzer is the complementary option. For focused diagnostics in the existing Siebel environment, the eScript approach provides a fast path from issue detection to remediation.

For additional technical background refer to the article: How to identify and fix the hidden product catalog issues.