Forms Personalization Condition Value Does Not Work With Global or Local Variables (Doc ID 1384492.1)

Last updated on MAY 01, 2017

Applies to:

Oracle Order Management - Version 11.5.10.2 and later
Information in this document applies to any platform.
Forms Personalization
Condition Value
Global Variables
Local Variables


Symptoms

On : 11.5.10.2 version, Transaction Entry

When attempting to create Forms Personalization on OEXOEORD, the following error occurs.

ERROR
-----------------------
Error:
Tokens in the string (${item.line.ordered_quantity.value} > to_number({global.XX_L_AVG_QTY.value}))
could not be evaluated. Please check the syntax

They are not able to get the forms personalization 'value' to work with global or local variables, the syntax cannot not be evaluated.  For example, the customer is trying to validate the qty of an ordered item based on global or local variable when they enter an order for qty of 100, the forms personalization should make the call to have the qty verified based on the customers pre-defined business requirements on how much qty they can order in a given period based on various parameters like the last shipment or how many were ordered in the last six months..etc


If they hard code a value, the syntax works. So for example, if they use the following:
Forms Personalization (Sales Orders)
Function Name: ONT_OEXOEORD > Description: Validate Quantity (not enabled)
Condition (TAB)
Trigger Event WHEN-VALIDATE-RECORD
Trigger object: Line
Condition : ${item.line.ordered_quantity.value} = 100 vs. using > to_number${global.XX_L_AVG_QTY.value}

However, using a hard coded number does not work for the business case, they need to calculate the value for each Customer because of many variables and the number could be higher or lower depending on each scenario for each Customer.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Responsibility: Order Management Super User
2. Navigate: Orders Workbench, Order Organizer OEXOEORD > Forms Personalization
3. Receive error when trying to use global or local variables for value.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms