Demo
What Is Transaction Account Builder (TAB) in Oracle Fusion?
Transaction Account Builder (TAB) in Oracle Fusion Cloud provides a flexible way to derive accounting flexfields and segments for subledger applications. With TAB, organizations can define rules to derive all the transaction account combinations on purchasing documents such as purchase orders and requisitions.
If you want to see where TAB fits in the broader transaction flow, pair this with the Oracle Fusion Purchase Order Accounting guide and the foundational Oracle Fusion General Ledger setup guide. Oracle's product reference is available through the Oracle Procurement documentation and the broader Oracle Financials documentation.
If your goal is to configure TAD, account rules, and procurement accounting hands-on, the Oracle P2P Procure-to-Pay Cloud Learning Subscription is the most relevant follow-up course.
TAB replaces the Account Generator workflow from Oracle E-Business Suite (EBS). In EBS, the Purchasing module relied on the Account Generator workflow to drive account combinations, and any customization required modifying the Oracle Workflow Builder. In Oracle Fusion Cloud, TAB replaces this entirely with a more configurable mechanism for account defaulting — no workflow customization needed.
Oracle provides seeded TAB account rules out of the box. When business requirements go beyond the seeded functionality, TAB supports custom rules, mapping sets, and segment overlays to address those needs.
Transaction Account Types
Under TAB, the Transaction Account Definition (TAD) is the top-level entity. Within a TAD, you specify the transaction account types — these are the accounts that TAB derives for purchasing documents. Oracle Fusion provides the following five transaction account types:
- Charge Account: The account where the actual money spent is charged.
- Accrual Account: An intermediary account that records the money spent on goods or services that have been consumed but not yet invoiced.
- Variance Account: Captures the difference between the purchase order amount and the actual invoice amount — the variance between what was ordered and what was billed.
- Destination Charge Account: Relevant in intercompany transactions where the procuring organization and the destination organization are different. This is the charge account belonging to the destination organization.
- Destination Variance Account: Also relevant in intercompany transactions. This is the variance account belonging to the destination organization.
TAB Components: Account Combination Rules, Segment Rules, and Mapping Sets
TAB uses three key components to configure how accounts are derived on purchasing documents:
Account Combination Rule
An account combination rule populates all segments of the relevant chart of accounts for a given transaction account type. Oracle provides seeded account combination rules, or you can create custom rules for specific business requirements.
Within an account combination rule, you define conditions and sources. Oracle provides a large pool of sources — you can specify conditions such as "if the destination type is expense" or "if the employee charge account is not null" to control which source drives the derivation. If no condition is specified on a rule line, it applies to all transactions.
Segment Rule
A segment rule (also called a segment overlay rule) overrides a specific segment of the chart of accounts rather than the entire account combination. Segment rules work in conjunction with account combination rules — the combination rule first populates all segments, and then the segment overlay rule overrides a particular segment based on defined criteria.
For example, if the charge account is derived by the account combination rule but the natural account segment needs to be determined differently based on the item category, a segment overlay rule can handle that override.
Mapping Set
Mapping sets enable complex account derivation rules based on combinations of input values. For instance, if the PO charge account needs to be derived based on a combination of item number and inventory organization — where Item A001 in Organization 002 maps to account 101.10.15910.000 — a mapping set can address this. Mapping sets are attached to account rules, which are in turn attached to the Transaction Account Definition.
Mapping sets are not mandatory. They are required when the seeded TAB rules do not meet specific business requirements and custom derivation logic is needed.
How to Set Up TAB in Oracle Fusion Cloud
The setup for Transaction Account Builder in Oracle Fusion Procurement follows a specific sequence. Navigate to Setup and Maintenance, select the Procurement offering, and scroll down to the Procurement Transaction Account Rules functional area. The key tasks available here are:
-
Manage Mapping Sets — Create or modify mapping sets that define input-to-output mappings for account derivation. You specify the output type (account combination or segment), input sources (such as item category or inventory organization), and the corresponding account values.
-
Manage Account Rules — Create or modify account rules with a rule type of either account combination rule or segment, and the associated chart of accounts. For segment rules, specify which segment to override and attach the relevant mapping set.
-
Manage Transaction Account Definitions — A Transaction Account Definition contains the account rule assignments — for each of the five transaction account types, you attach an account combination rule and optionally a segment overlay rule.
-
Manage Subledger Accounting Options — The final step is attaching the Transaction Account Definition to the ledger. Select your ledger, expand the subledger applications, and for Purchasing, specify which Transaction Account Definition to use.
Important: It is a good practice to duplicate the seeded Transaction Account Definition rather than modifying it directly. Copy the Oracle-provided definition, then customize the copy for your specific charge account, variance account, or other requirements. After making changes to a Transaction Account Definition, make sure its status is set to Active — changes will not take effect until the definition is activated.
Example: Overriding the Natural Account Segment Using a Mapping Set
To illustrate how these components work together, consider this scenario: the charge account on a requisition is derived by the standard account combination rule, but the business requires the natural account segment to change based on the item category selected on the requisition.
The setup involves three steps. First, create a mapping set with the output type set to "Segment," the input source set to "Item Category," and define the mappings — for example, the Miscellaneous category maps to natural account 101. Second, create an account rule with the rule type set to "Segment" for the natural account, and attach the mapping set you just created. Validate the rule before saving. Third, open the Transaction Account Definition attached to your ledger, and for the Charge Account type, attach the new segment overlay rule. Activate the definition.
Once this is configured, when a requisition is created with the Miscellaneous item category, the charge account will default as usual from the account combination rule, but the natural account segment will be overridden to 101 based on the segment overlay rule and mapping set.
If you want to go deeper than the TAB concept and actually configure it inside complete procurement scenarios, review the Oracle P2P Procure-to-Pay Cloud Learning Subscription. It covers transaction account definitions in the context of requisitions, purchase orders, accounting, and budgetary control instead of as an isolated setup task.
