Previous	Next		Contents	Index	Navigation	Glossary	Library

Syntax

#FND {POPIDR|LOADIDR|VALIDR}
CODE="flexfield code"
APPL_SHORT_NAME="application_short_name"
VALIDATE="{PARTIAL|NONE}"
[REQUIRED="{Y|N}"]
[DISPLAY="{ALL | flexfield qualifier |
segment number}"]
[UPDATE="{ALL | flexfield qualifier |
segment number}"]
[INSERT="{ALL | flexfield qualifier |
segment number}"]
[SEG=":block.concatenated values field name"]
[DESC=":block.concatenated description field name"]
[TITLE="window title"]
[VDATE="date"]
[NAVIGATE="{Y|N}"]
[AUTOPICK="{Y|N}"]
[NUM="structure defining field"]
[VRULE="flexfield qualifier\n
segment qualifier\n
{I[nclude]|E[xclude]} APPL=shortname;
NAME=Message Dictionary message name\n
validation value1\n
validation value2..."]
[ALLOWNULLS="{Y|N}"]

	CODEThe flexfield code you specify when you set up this flexfield using the Register Key Flexfield form. This code must match the code you registered.
	APPL_SHORT_ NAMEThe application short name with which your flexfield is registered.
VALIDATE	Use a validation type of PARTIAL to validate each individual segment value a user enters. PARTIAL validation does not create a new valid combination or check the combinations table to determine if a code combination already exists. Use NONE if you wish no validation (this is the usual argument for a range flexfield). Do not use FULL or FOR_INSERT for a range flexfield.
	Use the same value in your LOADIDR and VALIDR as you use in your POPIDR.
REQUIRED	Specify whether your user can exit the flexfield window without entering a value.
	You should specify the same value for REQUIRED in both your POPIDR and VALIDR triggers. You do not need the REQUIRED parameter for LOADIDR. The default value is Y.
	Note: Even if REQUIRED="N", a user who starts entering segment values for this flexfield must either: a) fill out the flexfield in full, or b) abandon the flexfield.
DISPLAY	The DISPLAY parameter allows you to display segments that represent specified flexfield qualifiers or specified segment numbers, where segment numbers are the order in which the segments appear in the flexfield window, not the segment number specified in the Define Key Segments form. For example, if you specify that you want to display only segment number 1, your flexfield displays only the first segment that would normally appear in the pop-up window (for the structure you specify in NUM).
	If you include the DISPLAY parameter in your POPIDR, you must include the DISPLAY parameter with the exact same argument in your LOADIDR and VALIDR calls.
	The default value for DISPLAY is ALL, which makes your flexfield display all segments. Alternatively, you can specify a flexfield qualifier name or a segment number.
	You can use DISPLAY as a toggle switch by specifying it more than once. For example, if you want your flexfield to display all but the first segment, you would specify:

				DISPLAY="ALL"
				DISPLAY="1" 

UPDATE INSERT	The UPDATE / INSERT parameters determine whether your users can update or insert segments that represent specified unique flexfield qualifiers or segment numbers, where segment numbers are the order in which the segments appear in the flexfield window, not the segment number specified in the Define Key Segments form.
	You do not need the UPDATE and INSERT parameters for LOADIDR or VALIDR.
	The default value for each is ALL, which allows your user to update/insert all segments. Alternatively, you can specify a flexfield qualifier name or a segment number. You can enter UPDATE="" or INSERT="" to prevent your user from updating or inserting values for any segments.
	You can use these parameters as toggle switches by specifying them more than once. For example, if you want your user to be able to update all but the first segment, you would specify:

				UPDATE="ALL"
				UPDATE="1" 

SEG	:block.concatenated values field name is a displayed, non-database form field that contains your concatenated segment values plus delimiters. If you do not specify the SEG parameter, Oracle Application Object Library does not display concatenated segment values. You do not need to specify _LOW and _HIGH, however, since Oracle Application Object Library adds the suffixes for you.
DESC	:block.concatenated description field name is a displayed, non-database, non-enterable field that contains concatenated descriptions of your segment values. If you do not specify the DESC parameter, Oracle Application Object Library does not display concatenated segment descriptions. You do not need to specify _LOW and _HIGH, however, since Oracle Application Object Library adds the suffixes for you.
TITLE	window title appears at the top of the pop-up window. The default value is the Flexfield Name you specify when you set up this flexfield using the Define Key Segments form.
VDATE	date is the date against which the Start Date and End Date of individual segment values is checked. You enter a Start Date and End Date for each segment value you define using the Define Key Segment Values form.
	For example, if you want to check values against a date that has already passed (say, the closing date of an accounting period), you might specify that date as VDATE using a field reference (VDATE=:block.field) and compare your segment values against that date.
	The default value is the current date.
NAVIGATE	Specify Y if flexfields should automatically determine the navigation out of the flexfield pop-up window (that is, if your user exits the window by pressing [Next Field], then the cursor appears in the field after the flexfield. Alternatively, if your user exits the flexfield by pressing [Previous Field], then the cursor appears in the field before the flexfield).
	This value should be Y for POPID, but is not needed for LOADID or VALID. The default value is N for backward compatibility.
AUTOPICK	Specify N if flexfields should not pop up a list of values window when a user enters an invalid value.
	You do not need the AUTOPICK parameter for LOADIDR or VALIDR. The default value is Y.
NUM	The non-displayed database :block.field that holds the identification number of your flexfield structure. You may also specify :$PROFILES$.your_profile_option_name to retrieve a value you set in a user profile option. You can "hardcode" a structure number, such as 101, into this parameter instead of providing a field reference, but such a number prevents you from using multiple structures for your flexfield. You must use this option if you are using multiple structures.
	You can use the following SQL statement to retrieve the structure identification numbers for your flexfield:

			SELECT ID_FLEX_NUM, ID_FLEX_STRUCTURE_NAME
			FROM FND_ID_FLEX_STRUCTURES
			WHERE ID_FLEX_CODE = 'flexfield code'; 

	where flexfield code is the code you specify when you register your flexfield.
	The default value for NUM is 101.
VRULE	Use VRULE to put extra restrictions on what values a user can enter in a flexfield segment based on the values of segment qualifiers (which are attached to individual segment values). You can specify the name of a flexfield qualifier and a segment qualifier, whether to Include or Exclude the validation values, and the Message Dictionary message name for the message Oracle Application Object Library displays if the user enters an improper value. The delimiter \n must be lowercase.
	For example, suppose you build a form where you want to prevent your users from entering segment values for which detail posting is not allowed into all segments of Oracle General Ledger's Accounting Flexfield. DETAIL_POSTING_ALLOWED is the segment qualifier, based on the global flexfield qualifier GL_GLOBAL, that you want to use in your rule. You want to exclude all values where the value of DETAIL_POSTING_ALLOWED is N (No). Your message name is "GL Detail Posting Not Allowed", and it corresponds to a message that says "you cannot use values for which detail posting is not allowed." You would specify your rule as:

			VRULE="GL_GLOBAL\nDETAIL_POSTING_ALLOWED\nE
			\nNAME=GL Detail Posting Not Allowed\nN" 

	When your user enters an excluded value in one of the segments affected by this qualifier, your user gets the message you specify. In addition, the excluded values do not appear in the Lists of Values on your segments. All other values, not being specifically excluded, are included.
	You can specify one or more VRULE parameters. Oracle Application Object Library checks multiple VRULE parameters bottom-up relative to the order you list them. You should order your rules carefully so that your user sees the most useful error message first.
ALLOWNULLS	Determines whether NULLs should be allowed into any segment. ALLOWNULLS overrides the value set definition (Value Required is Yes) for each segment only if you specify PARTIAL or NONE for the VALIDATE parameter.