Kindly Join My Membership Club
kzitem.info/rock/1xVxwcN21FGpWhw-m-LFewjoin
Transaction Account Builder (TAB) provides a flexible mechanism to derive accounting flexfields for subledger transactions.
Purchase requisitions and purchase orders have several accounts stored on them. The three mandatory accounts are:
Charge Account - The account against which the money spent is finally withdrawn or charged.
Variance Account - Certain situations call for variances to be recorded for certain kind of spending. An entry is created against this account for all such variances. E.g. price variance between PO and invoice.
Accrual Account - An intermediary account which records money spent for goods or services that have been consumed or taken ownership of and that is yet to be invoiced. An entry against this account is reversed once the money is physically spent or the invoice is issued.
In addition to these three accounts, there are two other accounts for more advanced procurement scenarios where there is an intercompany transaction involving a procuring organization and a destination organization. Namely:
Destination Charge Account - The charge account belonging to the destination organization
Destination Variance Account - The variance account belonging to the destination organization
Business would like to automate the derivation of these accounts on transactions based upon their corporate policies. There needs to be calculations done to build these accounts on transactions such as a requisition or purchase order. The Subledger Accounting (SLA) engine does that. The component of the engine which does it is known as Transaction Account Builder or TAB.
In other words, TAB is the component of Subledger Accounting which is solely responsible for building or defaulting the accounts on a transaction such that appropriate accounting entries can be created against such transaction accounts.
TAB is a new concept in Oracle Fusion Applications and it replaces all prior account generator solutions. Before Oracle Fusion there was a similar need to default transaction accounts. That need was fulfilled by different solutions. For instance, in Oracle E-Business Suite (EBS), Oracle Purchasing uses the Account Generator Workflow to derive account code combinations on purchase orders and requisitions. Oracle EBS Purchasing provides default Account Generator processes for you to use. If the defaults do not satisfy your accounting requirements, you can use the Oracle Workflow Builder to customize the default processes. Account Generator Workflow has been obsoleted in Fusion and replaced by SLA’s Transaction Account Builder process.
Oracle Fusion delivers seeded account defaulting rules within SLA's transaction account builder which aims to address the common defaulting scenarios of customers and also to facilitate further rule extensions in place of customers/implementers having to plan it out from scratch.
In PeopleSoft applications, ChartFields are used to define and default the account segments in the transaction accounts. Each ChartField has its own attributes for maximum efficiency and flexibility in recording, reporting and analyzing its intended category of data. Though, PeopleSoft delivers a set of ChartFields and associated functionality that fully covers most accounting and reporting requirements, ChartFields are designed to be configured by customers to meet their specific requirements.
In JD Edwards, account generation is carried out by AAI (Automatic Accounting Instruction). AAIs are rules that define the relationships between your day-to-day accounting functions and your chart of accounts. In the General Accounting system, AAIs determine how to distribute general ledger entries that the system generates. Each AAI is associated with a specific general ledger account that consists of a business unit, an object, and optionally, a subsidiary and is mapped to your chart of accounts.
Негізгі бет Oracle Procurement Cloud: TAB, TAD, And TAT
Пікірлер: 1