(Doc ID 521602.1)
Last updated on JANUARY 26, 2020
Applies to:Siebel CRM - Version 184.108.40.206 SIA  and later
z*OBSOLETE: Microsoft Windows Server 2003
Version: 220.127.116.11  Life Sci
Database: Microsoft SQL Server 2000 SP3
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: Microsoft Windows 2003 Server SP1
This document was previously published as Siebel SR 38-2799585051.
We have created a new sales method and have come across several issues.
We have created new Sales Stages, which we wanted unique reason Won / Lost values for. We therefore created new LOV values for the "Status" field called "ONPOS LOST"
We then created new "REASON_WON_LOST" LOV records that have a parent LIC of "ONPOS LOST" which in theory should display the new values when the sales stage is set within the UI.
However, when setting the "Sales Stage" field within the UI, the system does not display any value in the "Reason Won / Lost" field.
After further investigation it was discovered that the system updates the "STATUS_CD" column on the Opty table when the "Sales Stage" field is set in the UI. When we set the Sales stage to a Phase where the status is "ONPOS LOST" the column on the table is not updated, retaining its original value.
We also noticed that when it sets the "STATUS_CD" column using the originial sales stages, there is a discrepency between what is shown in the sales stages and what is written to the db. When selecting a phase that has a status of "OPEN" the systen writes "Accepted" to the "STATUS_CD" column on the opty table. This means that the "Reason Won Lost" LOV has a parent LIC of Accepted rather than of "OPEN" which is the value shown in the UI within the sales method. (print of the sales status - There is not "Accepted" value)
Can you advise us on why there is a discrepency between the UI and the db and how to implement our new sales methods.
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