Signals And Workflows Used For Pricing in eSales
(Doc ID 497243.1)
Last updated on FEBRUARY 14, 2022
Applies to:
Siebel Pricer - Version 7.8 [19021] to 8.1.1.3[21219] [Release V7 to V8]All Platforms
Product Release: V7 (Professional)
Version: 7.8.2 [19213]
Database: Oracle 9i
Application Server OS: Microsoft Windows 2000 Server SP 4
Database Server OS: Redhat Linux 8.0
This document was previously published as Siebel SR 38-2977663681.
*** ***
Goal
Questions:
Customer is implementing Siebel eSales and needs some clarification about the pricing in eSales.
1) Is Siebel 7.8.2 (eSales App) is using the Pricing workflows for Order Management. If so which pricing workflows and signals?
2) In Sales and Call Center Order Management customer is using the Pricing Workflow ("Basic Pricing Procedure") in the signal "Calculate Price" and has done a lot of customizations to "Basic Pricing Procedure". In eSales they do not want to use all these customizations in "Basic Pricing Procedure", instead just want to use vanilla "Basic Pricing Procedure" workflow. How to use that and where to configure?
3) Customer found 2 vanilla signals
- CalculatePriceAll_eSales
- CalculatePrice_eSales
What is the use of these signals and when are these signals invoked?
Solution
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
Goal |
Solution |