Skip to main content

Descriptive Flexfields in Oracle Apps

Descriptive Flexfields in Oracle Apps


Overview of Flexfields:
A flexfield is a field made up of sub–fields, or segments. There are two types of flexfields: key flexfields and descriptive flexfields.
Key Flexfields:
A Key flexfield is a field made up of segments, where each segment has both a value and a meaning, which appears on your form as a normal text field with an appropriate prompt.
One example of a key flexfield is the Accounting Flexfield. This flexfield can always be customized to have as many segments as needed like Company, Department, Cost center, Account etc.
Descriptive flexfields:
Descriptive flexfields lets you add additional fields to the form in order to track additional information needed by the business that would not be captured by the standard 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 Square Brackets [ ]. Each field or segment in a descriptive flexfield has a prompt and can have a set of valid values
Descriptive Flexfield Concepts:
Descriptive flexfields have two different types of segments, global and context–sensitive.
A global segment is a segment that always appears in the descriptive flexfield pop–up window.
A context–sensitive segment is a segment that may or may not appear depending upon what other information is present in your form.
A descriptive flexfield can get context information from either a field somewhere on the form, or from a special field (a context field) inside the descriptive flexfield pop–up window. If the descriptive flexfield derives the context information from a form field (either displayed or hidden from users), that field is called a reference field for the descriptive flexfield.
A descriptive flexfield uses columns that are added on to a database table. A descriptive flexfield requires one column for each possible segment and one additional column in which to store structure information (that is, the context value). The descriptive flexfield columns are usually named ATTRIBUTEn where n is a number.
For example, if you have a descriptive flexfield on an Order Entry (Header) form, it populates the Structure column with the context field and the columns ATTRIBUTEn with the flexfield segments of the table OE_ORDER_HEADERS_ALL.
Example of enabling DFF:
Goal: Enable DFF in Sales Order form in Order Management
Navigation: Go to “Order management super User, Vision Operations” responsibility > Orders, Returns >> Sales Orders
Enable the DFF at right bottom screen.
To know the name of the DFF in a particular form do the following
Navigation: Help Menu >> Diagnostics >> Examine
Select Block Name as $DESCRIPTIVE_FLEXFIELD$
Field as ORDER.DF
Value will be populated and it will be the title of your DFF.
Title: Additional Header Information (Order Management)
Order management in the brackets represent the Application in which this DFF is registered.
To enable this
Navigation: Go to Application Developer >> Flexfield >> Descriptive >> Segments
Query the DFF
Press F11 and enter
Title: Additional Header Information
Application: Order Management
Press CTL + F11 to query the record
Click on Segments
Enter the following information
Number: 5
Name: Erp Schools Demo
Window Prompt: Erp Schools Demo
Column: ATTRIBUTE11
Save the record (CTL + S)
Press OK
You can assign any value set if you want, its optional so I am just leaving it as blank
Now check the “Freeze Flexfield Definition” Checkbox
Press OK
Now Click Compile button
Press OK
You will see the confirmation as shown above.
Now to go to Order management super User, Vision Operations” and open the Sales order Form and click on DFF box.
You can hide the context field by un checking the Displayed Check Box in Context Field
To Make any changes you have to uncheck the “Freeze Flexfield Definition” Checkbox
Press OK
Now uncheck the Displayed Box in Context Field area as shown
Save your Record
Check the “Freeze Flexfield Definition” Checkbox
Press OK
Press Compile Button
Press OK
“Flexfield View Generator” concurrent program will be submitted. To see the status of the program go to View Menu on top >> Requests >> Find
Once you see the status as completed you can go to Order Management and check for your changes
Now you should be able to hide the Context.

Comments

Popular posts from this blog

O2C Cycle with Accounting Entries

  ORDER    TO  CASH  PARTICULARS  DR  CR SPL NOTES ACCOUNT IS PULLED FROM Sales order entry No Accounting Sales Order Pick From Sub Inventory A/c 100 At Standard Cost Sub-inventory Material A/c Setup To Sub Inventory A/c 100 At Standard Cost(Staging) Sub-inventory Material A/c Setup Sales Order Issue COGS 100 It can be fetched from five places Master Item/Org/Order Type/Line Type/Shipping Params To Sub Inventory A/c 100 At Standard Cost Sub-inventory Material A/c Setup Transaction level Receivable A/c 120 Auto Accounting Tax A/c 10 Auto Accounting Freight A/c 10 Auto Accounting Revenue A/c 100 Auto Accounting Receipts Receipts with no remittance method Cash 100 Before application of the receipt Receipt class Unapplied A/c 100 Receipt class Unapplied A/c 100 After application of the receipt to the transaction Receipt class Receivables A/c 100 Receipt class Cash A/c 100 Receipt class Unidentified A/c 100 In case of receipt without customer...

Oracle Subledger Accounting (SLA) Tables, Views

Oracle Subledger Accounting (SLA) Tables, Views Oracle Subledger Accounting Tables: TABLE NAME DESCRIPTION XLA_AAD_GROUPS The XLA_AAD_GROUPS table stores the merge dependencies analyzed during the merge analysis.  All application accounting definitions with the same GROUP_NUM must be merged together. XLA_AAD_HDR_ACCT_ATTRS The XLA_AAD_HDR_ACCT_ATTRS stores standard, system and custom sources assigned to an accounting attribute at the AAD level. XLA_AAD_HEADER_AC_ASSGNS Store the analytical criteria for the application accounting definitions. XLA_AAD_LINE_DEFN_ASSGNS This table stores the journal lines definitions for the application accounting definitions. XLA_AAD_LOADER_DEFNS_T The XLA_AAD_LOADER_DEFNS_T table is the interface table that facilitates the data transfer from data files and the database. XLA_AAD_LOADER_LOGS The XLA_AAD_LOADER_LOGS table stores the errors and logs generated by the application accounting definitions loader. XLA_AAD_SOURCES XLA_AAD_SOURCES table stores a...

Create Accounting for a Payment generates errors 95333 and 95359

Create Accounting for a Payment generates errors 95333 and 95359 Error: 95333: A conversion rate does not exist to convert USD to AUD for the conversion type Corporate and conversion date 20-MAR-09 for line -25. Please use the Daily Rates form in General Ledger to enter a conversion rate for these currencies, conversion date and conversion type. 95359: There is no accounted amount for the subledger journal entry line. Please inform your system administrator or support representative that: The source assigned to the accounting attribute Accounted Amount has no value for extract line number 88547. Please make sure the source assigned to the accounting attribute Accounted Amount has a valid value, or assign a different source to this accounting attribute. Solution: 1. Specify a conversion rate for the currencies and conversion date mentioned in the error message 95333 Navigation under the General Ledger responsibility: Setup > Currencies > Currency Rates Manager > Daily Rates ...