Account Combinations
Budget Wand allows the user to create General Ledger account combinations automatically if they do not already exist in Oracle.
There are two requirements for this functionality to work.
- Dynamic Inserts for the Key Flexfield Segment structure must be allowed. This can be done within Oracle Applications from a responsibility with the relevant access. See the “Allow Dynamic Inserts” option for the example below.
- The “Create missing account combinations” setting in the Budget Wand User Options form must be enabled.
An excessive number of account combinations may cause the Account Combination wizard to not complete or appear to hang. In this scenario you have two options:
| Option | Description |
|---|---|
| Disable account combination caching | Update the Cache Account Combinations configuration option. Doing so will disabled account combination validation on the journal line. Any invalid account combinations will need to be corrected in the GL Interface table. |
| Set cache account combinations limit | Set the Cache Account Combinations Limit user option so that only a certain number of account combinations will be cached. Set this limit will require the user to open the Account Combinations each time the launch Journal Wand, to cache the required account combinations. The cached account combinations will be used to validate the account combinations used in any journal lines. If an account combination has not been cached, the journal line validation will fail. A zero, or null, value limit will disable the option and resort to default setting of caching all account code combinations. |