A flexfield is a field made up of sub–fields, or segments. There are two types of flexfields: key flexfields and descriptive flexfields. A key flexfield appears on your form as a normal text field with an appropriate prompt. A descriptive flexfield appears on your form as a two–character–wide text field with square brackets [ ] as its prompt. When opened, both types of flexfield appear as a pop–up window that contains a separate field and prompt for each segment. Each segment has a name and a set of valid values. The values may also have value descriptions.
KFF, DFF, Structure, Segemnt, Value, Value Set, Value Description, Aliases, Rules, Groups, Security.

Key Flexfields
Most organizations use ”codes” made up of meaningful segments (intelligent keys) to identify general ledger accounts, part numbers, and other business entities. Each segment of the code can represent a characteristic of the entity. For example, your organization might use the part number PAD–NR–YEL–8 1/2×14” to represent a notepad that is narrow–ruled, yellow, and 8 1/2” by 14”. Another organization may identify the same notepad with the part number ”PD–8×14–Y–NR”.
Both of these part numbers are codes whose segments describe a characteristic of the part. Although these codes represent the same part, they each have a different segment structure that is meaningful only to the organization using those codes.
The Oracle Applications store these ”codes” in key flexfields. Key flexfields are flexible enough to let any organization use the code scheme they want, without programming. When your organization initially installs Oracle Applications, you and
your organization’s implementation team customize the key flexfields to incorporate code segments that are meaningful to your business. You decide what each segment means, what values each segment can have, and what the segment values mean. Your organization can define rules to specify which segment values can be combined to make a valid complete code (also called a combination). You can also define relationships among the segments. The result is that you and your
organization can use the codes you want rather than changing your codes to meet Oracle Applications’ requirements.
For example, consider the codes your organization uses to identify general ledger accounts. Oracle Applications represent these codes using a particular key flexfield called the Accounting Flexfield. One organization might choose to customize the Accounting Flexfield to include five segments: company, division, department, account, and project. Another organization, however, might structure their general ledger account segments differently, perhaps using twelve segments instead of five. The Accounting Flexfield lets your Oracle General Ledger application accommodate the needs of different organizations
by allowing them to customize that key flexfield to their particular business usage.
Descriptive Flexfields
Descriptive flexfields provide customizable ”expansion space” on your forms. You can use descriptive flexfields to track additional information, important and unique to your business, that would not otherwise be captured by the form. Descriptive flexfields can be context sensitive, where the information your application stores depends on other values your users enter in other parts of the form. A descriptive flexfield appears on a form as a single–character, unnamed field enclosed in brackets. Just like in a key flexfield, a pop–up window appears when you move your cursor into a
customized descriptive flexfield. And like a key flexfield, the pop–up window has as many fields as your organization needs.
Each field or segment in a descriptive flexfield has a prompt, just like ordinary fields, and can have a set of valid values. Your organization can define dependencies among the segments or customize a descriptive flexfield to display context–sensitive segments, so that different segments or additional pop–up windows appear depending on the values you enter in other fields or segments.

  1. KFF & DFF
  2. Structure, Segment & Qualifier
  3. Value (Parent, Group, Hirearchy & Qualifier) , Value Description & Value Set
  4. Security Rule, Cross-Validation & Alias
  5. Accounting Flexfield (Chart of Account & Account Generator processes)
Shared entities can be referenced by multiple products. These entities allow you to define broad-level structures that help you to include members when implementing the E-business suite. Which business unit will own specific data in a shared entity is at the discretion of the compnay. Employee data is always owned by human resources, provided the E-business suite is installed.

Step 1: Develop the Organization Structure
A successful implementation of Multiple Organization support in Oracle Applications depends primarily on defining your organizational structure in the multi-level hierarchy used by Oracle Applications. The levels are:
• Business groups
• Primary ledgers (as defined in Accounting Setup Manager)
• Legal entities
• Operating units
• Inventory organizations
 
Step 2: Define Accounting Setups
Use the Accounting Setup Manager in Oracle General Ledger to define accounting setups that include the following common financial components:
One or more legal entities (optional)
Primary ledger
  • Reporting Currencies (optional)
  • Balancing segment value assignments (optional)
  • Subledger Accounting Options

Operating Units (available if legal entities are assigned)
  • Intercompany Accounts (available if legal entities are assigned)
  • Intracompany Balancing Rules (optional)

Sequencing (optional)
Secondary Ledger (optional)

To use multiple organizations, you must define an accounting setup with at least one legal entity, a primary ledger that will record the accounting for the legal entity, and an operating unit that is assigned to the primary ledger and a default legal context (legal entity). It is also recommended that balancing segment values be assigned to the legal entity to help you identify legal entity transactions during transaction processing and reporting and to take advantage of Intercompany Accounting.
Note: If your enterprise structure requires that you define a business group, you should define accounting setups before business groups.
————————————————————————————————————————————————————————
Installation step 1.1 – Create legal entity
Once the installation of R12 is complete, log into the system with user id and password as sysadmin/sysadmin and create the user who ‘ll handel the Accounting part. Assign Grants Accounting Super User to the user

Go to the grants accouting super user responsibility and define a new legal entity.
Navigation : Grants accouting super user ->Set up -> Financials -> Accounting setup manager -> Accouting setups

Installation step 1.2 – Accounting Setup

Installation step 1.2.1 – Chart of Account

Lets define a six segment chart of account as shown below

Navigation : Grants accouting super user ->Set up -> Financials -> Flexfields-> Key ->Segments

 Installation step 1.2.1 – Calendar