FS Wireless: $FLEX$ AND $PROFILE$ Notation Not Working For Descriptive Flexfields (Doc ID 1079423.1)

Last updated on SEPTEMBER 06, 2016

Applies to:

Oracle Field Service - Version 11.5.1 to 12.1.3 [Release 11.5 to 12.1]
Information in this document applies to any platform.
***Checked for relevance on 29-SEP-2013***

Symptoms

For the flexfield "Tasks additional information" a list of values (LOV) is being used where the validation type = Table. The list of values can be seen on the PDA. However, if the list is constrained using the clause ":$PROFILES$.user_id" the list cannot be seen in the PDA (although the restriction works if viewed on the desktop). If the constraint is hard coded, e.g. "where userid=123" it can be seen in the laptop.

The expectation is that the list of values can be constrained dynamically based on the user ID

The issue can be reproduced at will with the following steps:

  1.  Create a value set in Service of type Table, Value = MODEL_SERIAL, Meaning = RESOURCE_NAME, ID = MODEL_SERIAL
  2. Add where clause: STATUS='Not Used' AND USERID=$PROFILES$.USER_ID ORDER BY MODEL_SERIAL
  3. Attach the value set to a segment in the Flexfield "Tasks additional information"
  4. Restricted LOV can be seen dynamically in the forms application, but not in the Field Service Wireless application

 

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