Scribd
Upload
10 views2 pages

Defining Key Flexfields: Every Time

Key Flexfields (KFF) and Descriptive Flexfields (DFF) are used in Oracle EBS to uniquely identify and capture additional information about various business entities. KFF requires careful planning and validation of segment information, and changes to flexfield definitions necessitate recompilation to ensure performance and consistency. Users will see changes only after re-logging into the application, and modifications to structures can lead to data inconsistencies if not managed properly.

Uploaded by

MOHAMED
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
10 views2 pages

Defining Key Flexfields: Every Time

Key Flexfields (KFF) and Descriptive Flexfields (DFF) are used in Oracle EBS to uniquely identify and capture additional information about various business entities. KFF requires careful planning and validation of segment information, and changes to flexfield definitions necessitate recompilation to ensure performance and consistency. Users will see changes only after re-logging into the application, and modifications to structures can lead to data inconsistencies if not managed properly.

Uploaded by

MOHAMED
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 2

KFF - Keyflexfields are used throughout the Applications to uniquely identify informations such as GL

accounts, INV items, FIxed Assets and other entities that every business needs to keep track of.

DFF- Descriptive flexfields enable you to capture additional pieces of information from transaction entered
into Oracle EBS.

DFF and KFF share common features. They are multisegment fields. Application validates individual
segments based ons makes valueset rules and ensures that the segments makes sense using CVR (cross-
validation rules).

Defining Key Flexfields


You define descriptive information and validation information for each segment. You
also determine the appearance of your key flexfield window, including the size of the
window, the number and order of the segments, and the segment descriptions and
default values.

Once you set up or modify your structures and segments, you must freeze your
flexfield definition and save your changes. When you do, your flexfield compiles
automatically to improve on-line performance. You must recompile your
flexfield every time you make changes using this form, including enabling or
disabling cross-validation rules. You must also recompile your flexfield after you
enable or disable shorthand entry using the Shorthand Aliases window.

You can see your flexfield changes immediately after you freeze and recompile your
flexfield. However, your changes affect other users only after they change
responsibilities or exit your application and sign back on.

Once you freeze your flexfield definition and save your changes, Oracle Applications
submits one or two concurrent requests to generate database views of the flexfield's
combinations table. You can use these views for custom reporting at your site. One of
these views is always generated and contains concatenated segment values for all
structures of the key flexfield. You see the name of this view in the Toolbar window.
The other view is for the particular structure you are defining and freezing. This
second view is generated only if you enter a view name for your structure in the View
Name field. See: Overview of Flexfield Views.
Warning: Plan your key flexfield structures carefully, including all your segment
information such as segment order and field lengths, before you define your segments
using this form. You can define your key flexfields any way you want, but changing
your structures once you acquire any flexfield data may create data inconsistencies
that could have a significant impact on the behavior of your application or require a
complex conversion program. Changing your existing structures may also adversely
affect the behavior of to start taking changes again. does any of that make senseany
cross-validation rules or shorthand aliases you have set for your structures, so you
should be sure to manually disable or redefine any cross-validation rules (using the
Cross-Validation Rules window) and shorthand aliases (using the Shorthand Aliases
window) to reflect your changed structures.

You might also like