Select the Responsibility
Setup -> Financials -> Flexfields ->Validations->Sets
Value Set Name : Provide the segment name that is required eg. PAM_Company
List Type :
List of Value : If the value set is between 10 to 200 items then select this feature. The user will not see a list of values in the self-service application.
Long List of Values : If the value set is more than 200 items then select this feature. This will require the user to enter a partial value for the list to be populated. If self-service applications are used then don’t use this option since it will not populate. Do not enable this feature for a non-validated value set.
Poplist : select poplist if the list of values are required in self-service application
No Security : No security feature is enabled for this value set.
Hierarchical Security : Any security rule that is applied to the parent values applied to the child values since this feature combines value security & value hierarchy.
Non-Hierarchical Security : Security is enabled, but any security rule applied to the parent will not flow to the child.
Format Type : Format to be used for the segment Value. Valid entries are Char, Date, DateTime, Number, Standard Date, Standard DateTime, and Time.
Additional formatting information like if the vale should only be numbers or only characters and what should be the range, if to left/right justify the value to suit the maximum size as well as the maximum size can be specified.
Note : Translatable Independent and Translatable Dependent value sets must have the Char format. The maximum size for Translatable Independent and Translatable Dependent value set values is 150. You cannot use the Numbers Only feature or the Right-Justify and Zero-fill feature with translatable value sets
Value Validation : There are several validation types that affect the way users enter and use segment or parameter values
- None (not validated at all)
- Independent
- Dependent
- Table
- Special (advanced)
- Pair (advanced)
- Translatable Independent
- Translatable Dependent
Note : Validation type of an existing value set cannot be changed since the changes affect all Flexfields and report parameters that use the same value set. The Accounting Flexfield only supports Independent, Dependent, and Table validation (table validation cannot have any additional WHERE clauses.
None
None type value set is used in order to allow users to enter any value so long as that value meets the value set formatting rules and does not exceed the maximum length defined for your value set. It should also comply to the format requirements for that value set
The None value set is not validated which means a segment that uses this value set does not provide a list of value. A segment that uses this value set (that is, a non-validated segment) cannot use flexfield value security rules to restrict the values a user can enter.
Independent
An Independent value set provides a predefined list of values for a segment. These values can have an associated description but will not be dependent on the value of any other segment.
This provides a predefined list of values like an independent set, but its values are stored in an application table. You define which table you want to use, along with a WHERE cause to limit the values you want to use for your set. Typically, you use a table-validated set when you have a table whose values are already maintained in an application table (for example, a table of vendor names maintained by a Define Vendors form). Table validation also provides some advanced features such as allowing a segment to depend upon multiple prior segments in the same structure.
Dependent
A dependent value set is similar to an independent value set, except that the available values in the list and the meaning of a given value depend on which independent value was selected in a prior segment of the Flexfield structure. You can think of a dependent value set as a collection of little value sets, with one little set for each independent value in the corresponding independent value set. You must define your independent value set before you define the dependent value set that depends on it. You define dependent values in the Segment Values windows.
EG.
In our scenario we have account and sub account. When we select bank account as natural account, then the sub account valid values should be A bank, B Bank & C Bank etc. When we select Equipment’s as the natural account the sub account valid values should be Computers, Printers, Plotters etc.
Sequence for creating the Dependent Value set
- Create your independent value set first
- Create your dependent value set, specifying a default value
- Define your independent values
- Define your dependent values
Special and pair value sets provide a mechanism to allow a "Flexfield-within-a-Flexfield". These value sets are primarily used for Standard Request Submission parameters. You do not generally use these value sets for normal Flexfield segments.
Eg. A part number segment could be made up of three more segments like Category Item & source.
Translatable Independent and Translatable Dependent A Translatable Independent value set is similar to Independent value set in that it provides a predefined list of values for a segment. However, a translated value can be used.
A Translatable Dependent value set is similar to Dependent value set in that the available values in the list and the meaning of a given value depend on which independent value was selected in a prior segment of the Flexfield structure. However, a translated value can be used.
Flexfield Value Security cannot be used with Translatable Independent or Translatable Dependent value sets.
For format validation, translatable value sets must use the format type Char. The maximum size must be no greater than 150. The Number Only option and the Right-justify and Zero-Fill Numbers option cannot be used with translatable value sets.
Range Flexfields cannot use Translatable Independent or Translatable Dependent value sets.
You cannot create hierarchies or rollup groups with Translatable Independent or Translatable Dependent value sets.
No comments:
Post a Comment