My Oracle Support Banner

Configurator PAC Query For Interim Order Taking Long Time (Doc ID 515110.1)

Last updated on NOVEMBER 22, 2019

Applies to:

Siebel eConfigurator - Version 7.8.2 [19213] and later
Siebel CRM - Version 7.8.2 [19213] and later
Oracle Solaris on SPARC (64-bit)
Version: [19221]
Database: Oracle
Application Server OS: Sun Solaris 10
Database Server OS: Sun Solaris 10

This document was previously published as Siebel SR 38-3347958851.

”Checked for Relevance on 06-Oct-2014”


Customer creates new order with specified order line items with hierarchy. In their custom workflow process, the step which invokes the Configurator PAC query workflow and resulting performance impact is called 'Create Session'. In order to build the entire hierarchy they use CreateSession method of business service Remote Complex Object Instance Service (RCOIS), along with other methods of the said business service. However on Production they recognize that executing this step takes 20 minutes.

After analyzing the log files there is a query which takes 18.5 minutes to execute. This query is internally built by Siebel in a workflow called Configurator PAC Query (OOTB and is NOT modified/customized). The query which is built is as follows:

"[Owner Account Id] = '" + [&Account Id] + "' AND [Id] <> '" + [&CP Root Id] + "' AND [Root Asset Id] <> '" + [&CP Root Id] + "'".

The query is further used by workflow "Configurator Eligibility Compatibility Workflow", at step "Initialize Projected Asset" which uses the business service "VORD Projected Asset Cache" and method "Initialize".

How to address this performance issue?


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.