Processing Constraint With PL/SQL API - Reference To OE_HEADER_SECURITY.g_record Does Not Fire
(Doc ID 784046.1)
Last updated on AUGUST 07, 2024
Applies to:
Oracle Order Management - Version 11.5.10.2 to 11.5.10.3 [Release 11.5.10]Information in this document applies to any platform.
FORM:OEXOEORD.FMB - Sales Orders
FORM:OEXPCFWK.FMB - Define Processing Constraints
Symptoms
Want to restrict users not to update Sales Order (SO) line price after created from quotation. For that reasona a customized Validation Template (API ) was created to check some conditions and on that basis deciding whether system allow to change the Selling Price or not.
While running the custom PL/SQL code written for 'Validation Template' for the type as 'PL/SQL' and attached the validation template to the processing constraint, the API call to oe_header_security.g_record
(oe_header_security.g_record.order_type_id), it does not show any value.
EXPECTED BEHAVIOR
The API call should return the correct data.
-- Steps To Reproduce:
The issue can be reproduced at will with the following steps:
1. OM Superuser > Validation Constraint
2. Processing Constraint
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |