Setting Primary In Shuttle Can Leave Inconsistent Data on Unexpected Browser Closure
(Doc ID 2299118.1)
Last updated on APRIL 14, 2020
Applies to:Siebel CRM - Version 16.7 [IP2016] and later
Information in this document applies to any platform.
In Opportunities, Sales Orders on change position operation if the Browser does experience unexpected closure, the application leave inconsistent data among tables.
The issue can be reproduced at will with the following steps:
1. Create a Sales Order
2. Change the Position and setup as Primary the new one;
3. Delete previous Position
4. Close the Browser
Result : The application update the table S_ORDER_POSTN according with last
changes but do not update table S_ORDER with same changes.
Therefore when new/old user goes again in application won't see the sales
The sql used to retrieve data in List Sales Order does have an inner join
which do not find same values in both tables for where clause :
T1.PR_POSTN_ID = T3.POSTN_ID
INNER JOIN Siebel.S_ORDER_POSTN T3 ON T1.PR_POSTN_ID = T3.POSTN_ID
AND T1.ROW_ID = T3.ORDER_ID
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