The Pricing Call Is Failing When The Profile Option 'QP_BYPASS_PRICING' Is Set To 'Y'
(Doc ID 1668208.1)
Last updated on FEBRUARY 21, 2019
Applies to:Oracle Advanced Pricing - Version 12.1.3 and later
Information in this document applies to any platform.
The Pricing Call is Failing when the Profile Option 'QP_BYPASS_PRICING' is set to 'Y'. You have a requirement to call the Process Order API oe_order_pub.process_order to update the config_header_id and config_rev_nbr on the model line. During this call the users would like to By pass the Pricing Calls since you have custom logic to derive the unit selling price and Price List and pass the same to the Process Order API later in the Process.
To Achieve this, you set the Profile option ''QP_BYPASS_PRICING' to 'Y' before calling the Process Order API. But when the Process Order API is called, the Pricing Call Fails as the x_return_status is assigned the value ‘BYPASS_PRICING’ which is 14 Characters.
But in the Calling API oe_order_adj_pvt.price_line, the variable 'l_return_status ' is declared as VARCHAR2(10) which is causing the pricing call Fails.
The variable l_return_status declared as VARCHAR2 (10).This variable is passed to the Other QP APIs This is causing the Pricing API to error and hence the Process Order API is failing.
Debug is showing the following error
INITIALIZE_CONSTANTS Exception E_BYPASS_PRICING..l_routine: QP_PREQ_PUB.Initialize_Constants
Price Request: ORA-06502: PL/SQL: numeric or value error: character
string buffer too small ORA-06512: at "APPS.QP_PREQ_PUB", line 610
ORA-06510: PL/SQL: unhandled user-defined exception
STEPS TO REPRODUCE THE ISSUE
1. Responsibility: Order Management Super User.
2. Created a customize qp_preq_pub
3. The out variable x_return_status is assigned the value ‘BYPASS_PRICING’ which is 14 Characters.
4. The VARCHAR(10) is causing the pricing to fail.
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