April 30, 2012

Oracle Flex fields

Oracle flexfields is one of the most important parts of Oracle Applications. It is because of the flexfields that the Oracle Applications is so generic in nature and can be used to suit any industry or organization. A flexfield, as the name suggests, is a flexible data field that your organization can customize to your business needs without programming. A flexfield is a field made up of sub–fields, or segments. While flexfields do not require programming, they do allow you to perform significant customizations to the Oracle Applications, so they do require enough explanation for you to get the most out of the features they provide.
Oracle Applications uses two types of flexfields, key flexfields and descriptive flexfields. A key flexfield is a field you can customize to enter multi–segment values such as part numbers, account numbers, and so on. A descriptive flexfield is a field you customize to enter additional information for which your Oracle Applications product has not already provided a field.

Features Oracle Applications flexfields:

·         Have “intelligent fields”—fields comprised of one or more segments, where each segment has both a value and a meaning.
·         Rely upon your application to validate the values or the combination of values that you enter in intelligent fields.
·         Have the structure of an intelligent field change depending on data in your application.
·         Capture additional information if you so choose.
·         Customize data fields to your meet your business needs without programming.
·         Query intelligent fields for very specific information.

Key Flexfields

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.”
Most organizations use “codes” made up of meaningful segments 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, consider an account number for a bank. A complete bank number may consists of various segments like the country code, area code, city code, branch code, account type, account number etc.
For example, the number of segments a bank requires to identify an account number uniquely is a requirement specific to the bank. Another bank might not require a country code if its presence is there only in one country. Key flexfields are used to identify such information uniquely.
A key flexfield is flexible enough to let you use any code scheme you want to describe an entity. When your organization initially installs an Oracle Applications product, your organization’s implementation team customizes all the key flexfields in that product to use meaningful code segments to describe each key flexfield entity. Your organization decides for each key flexfield, how many segments an entity has, what each segment means, what values each segment can have, and what each segment value means.
Your organization can also define rules that govern what combination of segment values are valid (cross–validation rules), or define dependencies among the segments. The result is that your organization can use the codes it needs rather than change its codes to meet someone else’s requirements.
The Accounting Flexfield in your Oracle Purchasing application is an example of a key flexfield that identifies a unique chart of accounts. One organization may choose to customize the Accounting Flexfield to have three segments called Company, Department, and Account, while another organization may choose to customize the flexfield to have five segments called Company, Cost Center, Account, Sub–Account, and Product.
A key flexfield appears on your form as a normal text field with an appropriate prompt. In figure 1 below, the Account field is actually the Accounting Key Flexfield.

 

Descriptive Flexfields

Descriptive flexfields like the key flexfields provides further scope of customization in Oracle Applications.
Descriptive flexfields provide customizable “expansion space” on your forms. Though the fields on an Oracle Applications form are more than enough to capture all the possible information from the user perspective, but still the users can feel the need of capturing additional information. A descriptive flexfield gives you room to expand your forms for capturing such additional information.
A descriptive flexfield appears on a form as a single–character, unnamed field enclosed in brackets ([ ]) as shown in below.

Read More

Enterprise Structure


Enterprise Structure defines how a company is structured from an operating, legal and reporting perspective. Oracle Application considers the following in defining enterprise structure from an Inventory perspective:
·         Set of Books
·         Legal Entity
·         Operating Unit
·         Inventory Organization
·         Locations

Set of Books (SoB)

This is a financial reporting entity having unique Chart of Account, Calendar and currency. A corporation may have more than one Set of Books. Each Set of Book has the following :
·         Calendar: This is the accounting calendar; this might be different from the workday calendar.
·         Currency: Each SoB has unique functional currency. Transactions can be enetered in multiple currencies which can be converted later.
·         Chart of Accounts: Each SoB has unique chart of Account which represent the set of accounts that related to the Inventory, Purchasing and Account Payables.

Legal Entity

This can be defined as the legal company for which fiscal or tax report can be prepared. A SoB can have multiple tax entities.

Operating Unit

This is a division. A corporation can be divided considering its operation. For example, a computer manufacturer may have separate divisions for Laptop, personal computers and Servers. The Laptop can be represented by one operating unit, which is having its centralized purchasing and ordering function.  The physical part, which is Inventory may have received in separate inventory organization but the purchase orders are maintained centrally in an operating unit to optimize the supply chain. Operating units affects transactions involving in order management, purchasing, payables and receivables.

Inventory Organization

This can be manufacturing facilities, warehouse or any facilities where a company stocks and transacts inventory.

Sub-Inventories

In Oracle Application, these are the physical locations within a manufacturing or warehouse facilities where goods are stocked and transaction takes place from here. These are created inside Inventory Organizations.

Locations

This represents a physical address of a facility, office, warehouse or any place else used in the entity. Inventory Organization uses locations to represent the address of the following:
·         Ship To
·         Bill To
·         Office Site
·         Internal Site
·         Receiving Site
Each Inventory Organization must have at least one location.
Read More
Copyright © . Oracle Apps (SCM) . All Rights Reserved
Oracle Apps (SCM) is an online knowledge sharing blog which index online free tutorials, blogs and other sources, to get easier and accessible manner. The blog has been created keeping only one intention of sharing knowledge and for learning purpose. All trademarks, trade names, service marks, copyrighted work, logos referenced herein belong to their respective owners/companies. If any of the posting is violating copyright and you want us to remove that content. Please contact Here