You are on page 1of 6

Question: What is value set?

Answer: It is a set of values

Question: Why do we need value sets?


Answer: You do not always want a user to enter junk free text into all the
fields. Hence, Oracle Apps uses value set to validate that correct data is
being entered in the fields in screen.

Question: Is value set attached to all the fields that require validations?
Answer : A big NO

Question: Then where lies the usage of value sets?


Answer: Broadly speaking, value sets are attached to segments in Flexfields.
You can argue that value sets are also attached to parameters of concurrent
program(but in reality oracle treats parameters as Descriptive Flexfields)

Question: This is insane, flexfields havent been covered in


http://getappstraining.blogspot.com as yet?
Answer: Agreed, hence lets restrict value set explanation to their usage in
concurrent program parameters.

Question: Any examples?


Answer: For the namesake, lets add a Parameter to the concurrent program
that we defined in Concurrent Program Training Lesson link. Lets add a
parameter named cost centre, the values to this parameter must be
restricted to one of the three values, i.e. HR, SEC, IT.

At the time of submission of the concurrent program the user should be able
to pick a cost centre from a list. This is where value set gets used.

No Security - All security is disabled for this value set


Hierarchical Security - Hierarchical security is enabled. With hierarchical
security, the features of value security and value hierarchies are combined.
With this feature any security rule that applies to a parent value also applies
to its child values

Choosing a Validation Type for Your Value Set


None (not validated at all) :You use a None type value set when you want to
allow users to enter any value so long as that value meets the value set
formatting rules.

a segment that uses this value set does not provide a list of values for your
users
Independent :An Independent value set provides a predefined list of values
for a segment.These values can have an associated description.
Independent values are stored in an Oracle Application Object Library table
Dependent :Dependent value set is Values in the list depend on which
independent value was selected in a prior segment of the Flexfield structure.
Table

: Fetch value from our own application Table

Special (advanced)

Special and pair value sets provide a mechanism to

allow a "flexfield-within-a-flexfield". These value sets


Pair
are primarily used for Standard Request
Submission Parameter.
Translatable Independent :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
Translatable Dependent : 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

FLEXFIELDS: A flexfield is a flexible data field that your organization can


customize to your business needs without programming

Key Flexfields :A key flexfield is a field made up of segments, where each


segment has both a value and a meaning. You can think of a key flexfield as
an "intelligent" field that your business can use to store information
represented as "codes."

DFF will be used to capture extra information

Differences between DFF and KFF

DFF

KFF

1.

DFF will be used to capture EXTRA 1.


Information

KFF will be used to capture KEY Information

2.

Attribute columns will be used

2.

Segment columns will be used

3.

We can register MAX DFF

3.

We have 29 built in KFF we are not suppose to


create new KFF

4.

DFF will be accept what ever Data 4.


we enter

KFF we can define rules to capture valid data

5.

WE have context field

WE have no Context field

6.

DFF data will be stored in Attribute 6.


Columns

5.

DFF codes will be stored in segments KFF


description will be stored in FND_FLEX_VALUES
tables.

What is the significance of cross validate segments in the Key flexfield


structure screen (figure 6)?
1) Cross validation rule prevents user to enter invalid segment value
code combinations.
2) create when you enter values for key flexfields. A cross validation
rule defines whether a value of a particular segment can be combined
with specific values of other segments. Cross validation is different from
segment validation, which controls the values you can enter for a
particular segment.When a user finishes entering segment values in a
flexfield popup window, the flexfield checks whether the values make up
a valid combination before updating the database. If the user entered an
invalid combination, a diagnostic error message appears, and the cursor
returns to the first segment assumed to contain an invalid value

Dynamic Insertion
Dynamic insertion allows you to create a combination of segment values for a
key flexfield without using a combinations form. During the implementation of
a key flexfield, your organization can either explicitly define a list of valid
code combinations for the key flexfield using a combinations form, or allow
you to create valid combinations as you enter values in the key flexfield for
the first time on a form other than the combinations form. Your organization
can also specify cross-validation rules for a key flexfield so that you can only
define specific code combinations during dynamic insertion.

freeze rollup group: Rollup groups are used to create summary accounts for
reporting purposes in GL. Only accounting flex field is using this feature
currently

What is the difference between flexfield qualifier and segment qualifier?

Flexfiled qualifier identifies segement in a flexfield and segment qualifier identifies


value in a segment.
There are four types of flexfiled qualifier 1) Balancing segment qualifier 2) cost
center 3) natural account and 4) intercompnay
segemtn qualifier :- 1) allow budgeting 2) allow posting 3) account type 4) contral
account and 5) reconciliation flag

Difference between job and positions in oracle hrms


Jobs are meant to describe the duties someone performs, e.g. Engineer,
Accountant, Manager.
Positions are meant to describe specific instances of that job, e.g. Trainee
Engineer, Senior Cost Accountant, Sales Manager
In other words, Positions are subsets of Jobs.

Grades can be set up against either a Job or a Position. You select which ones
are valid.

Define Security Profiles:


Security profiles are used in Oracle Applications HCM to restrict the
information which a user can see. Information can be restricted in many ways
e.g., based on Organization, Position, Supervisor etc
Security profile controls access to people records, when user logins to HCM
applications
Once the security profile is created, it is attached to a
enforce the security access

responsibility to

You might also like