Example of a Key Flexfields
A key flexfield can capture expense account information.
Scenario
When entering details for each expense, the user specifies an account to which the expense is charged.
Entering Expense Accounts
A user interface for entering expenses helps the user select an expense account that identifies the cost center and other details needed for processing the expense.
The expense account field is a foreign key reference to a account combination (EXPENSE_LINES.EXPENSE_ACCOUNT = ACCOUNT.COMBINATION).
Account combinations Table for Entering Accounts and Employees
The account combinations table supports entering account information, such as for expense accounts.
The combinations page, which is the maintenance page for the key flexfield, is for managing rows in the combinations table. In this example, managing the combinations means adding or editing account numbers that adhere to the key flexfield metadata rules.
If dynamic combination creation isn't enabled, then when entering an expense line, the user can only select an account that already exists in the ACCOUNTS (combinations) table. If they require an account that doesn't exist, they must consult with the appropriate application administrator who can add the account to the combinations table.
If dynamic combination creation is enabled, then when entering an expense line, the user can either select a preexisting account, or type in a new account that's created dynamically on the fly in the ACCOUNTS (combinations) table. Once the new combination is created, the same user can refer to it on the expense line.
When managing employee information, the user specifies the cost center that the employee belongs to. The cost center field corresponds to a single, labeled segment of the Account Key Flexfield and has metadata defined such as the allowable value set for that segment.