Workflows Consuming Unnecessary Row Ids
(Doc ID 2334288.1)
Last updated on FEBRUARY 09, 2019
Applies to:Siebel CRM - Version 15.18 [IP2015] and later
Information in this document applies to any platform.
On : 15.18 [IP2015] version, Order Management
It has been observed that the application consumes a huge amount of row-ids when the product configurator workflows like for example PSP or Pricer workflow are executed with IP15/IP16.
When configuring a CP (using product configurator), the row_ids used for the workflow instances are not following a sequential order (apparently it's jumping 20~30)
STEPS TO REPRODUCE
1. Set AOM log level to 5
2. Log into the application (make sure there's only one user logged into the application)
3. Start a product configuration
4. Perform a number of actions inside the configurator (add/remove items,etc)
5. Quit the configuration session
6. Check in the log file the sequence of row_ids used (e.g.: check workflows execution consuming row_ids in Process Instance Id)
Below is an extract of the log file with the experienced issue:
EngInv Arg 4 000cfba259025b21:0 2017-05-04 16:46:22 Output:
This is the output of "Pricing Procedure - Aggregate Volume Discount" workflow execution where row_id used as process instance id is 8-7ZG2PVM
(*Process Instance Id9*8-7ZG2PVM).
If the row_id generation was following a sequential order, we would expect to see in the log for the next value 8-7ZG2PVN but, the next row_id found is 8-7ZG2PXZ which gives a difference of 85 between each one.
In previous versions of Siebel 22.214.171.124, row_id generation is following a sequential order (1-2HP1, 1-2HP2, 1-2HP3, etc) when configuring a product.
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