Professional Documents
Culture Documents
Oracle Procurement Transaction Account Builder Configuration
Oracle Procurement Transaction Account Builder Configuration
Oracle Procurement Transaction Account Builder Configuration
2. How to identify the chart of accounts (COA) for the above ledger.
Setup and Maintenance → Global Search → Search for task → Manage Subledger Accounting
Options
Click on respective account type (For Example Charge Account to find out the sources for charge
account).
You can find all available sources for the charge account from below page.
Similarly, click on different account types (Variance/Accrual) to find out the respective sources.
6. How to customize the charge account code combination for a specific requirement
Navigation
Setup and Maintenance → Global Search → Search for task → Manage Account Rules
Suggestion: - It is always recommended to create account rule from scratch using create option.
Click on + icon
Below are Sample Rules and Conditions(Also, available in standard TAD account rules)
Navigation
Setup and Maintenance → Global Search → Search for task → Manage Account Rules
Suggestion: - It is always recommended to create account rule from scratch using create option.
Value Type Value Conditions Meaning
Source Subinventory "Subinventory Material Source: Sub inventory Material Account
Material Account"."All" Is not null 'And'
Account "Cross BU" = N 'And' ( Condition Meaning - This condition will
"Destination Type be evaluated for Inventory/Dropship
Code"(PO,S,S) = INVENTORY destination type of PRs and Pos and is an
'Or' "Destination Type Inventory item.
Code"(PO,S,S) = DROP SHIP )
'And' "Item Asset Indicator" = The source is meant to drive the value
Y from the Costing mapping set
“Material Account – Subinventory" and
This mapping set has input sources as
“Secondary Inventory Name and
Inventory Organization Code” ”
Note: Deliver to locations are not inventory locations and these are customer’s locations with respect to
drop ship. If you create any custom mapping set, with deliver to location as input source, the rule will
fail
Navigation
Suggestion: - It is always recommended to create account rule from scratch using create option.
Requirement: To derive the account code combination for PO charge account based on the
projects. If project details are captured in PR or PO then which account needs to be derived
based on the category and if not populated then which account needs to be derived.
1. Create two mapping sets in purchasing module with input source as Item category
and output as account code combination.
2. First mapping set is triggered when project details are captured with respect to the
categories
3. Second mapping set is triggered without project details with respect to the
categories.
Input Source Chart Of account Valueset
Item Category Operations Accounting Flex ORA_PO_TAB_CATEGORY_VS
"Project Number"(PJC,S,S) Is null 'Or' ("Project Number"(PJC,S,S) Is not null 'And' "Task
Capitalizable Indicator"=N)
Category Accounts
Furniture 01-000-1540-0000-000
Home & Office Merchandise 01-000-1540-0000-000
Laser Printer 01-000-1560-0000-000
Miscellaneous_1 01-000-7740-0000-000
Category Accounts
Furniture 01-740-1540-0000-000
Home & Office Merchandise 01-740-1540-0000-000
Laser Printer 01-740-1560-0000-000
Miscellaneous_1 01-740-7740-0000-000
Navigation
Suggestion: - It is always recommended to create account rule from scratch using create option.
Requirement: To derive the account code combination for PR/PO charge account which is
initiated from Manufacturing Work Orders.
Add the new account rule to the existing charge account rule
XX_PURCHASING_CHARGE_ACCOUNT_CC” with above conditions listed.
Either we can use the standard source which will include below input sources or create a custom
mapping set as per the business requirement.
Navigation
Setup and Maintenance → Global Search → Manage Account Rules
Suggestion: - It is always recommended to create account rule from scratch using create option.
Requirement: To derive the individual account segment of PR/PO charge account based on the
“Project Number”.
Add the new account rule to the existing charge account rule XX_Purchasing_Project_Account”
with below listed conditions.
8. How to customize the variance account code combination for a specific requirement.
Navigation
Setup and Maintenance → Global Search → Manage Account Rules
Suggestion: - It is always recommended to create account rule from scratch using create option.
Add the new account rule “XX_Purchasing_Variance_Account” with below conditions listed.
Value Type Value Conditions Meaning
Source Requisition "Cross BU" = N 'And' "Cross BU" = N 'And' "Requisition
Variance "Requisition Variance Variance Account"."All" Is not null
Account Account"."All" Is not null Meaning system fetches the variance
account from PR in the PO when PR is
converted to PO.
Source PO Charge ("Cross BU" = Y 'And' ("Cross BU" = Y 'And' "Destination Type
Account "Destination Type Code"(PO,S,S) = EXPENSE ) 'Or' "Cross
Code"(PO,S,S) = EXPENSE ) 'Or' BU" = N 'And' "Requisition Variance
"Cross BU" = N 'And' Account"."All" Is null 'And' (
"Requisition Variance "Destination Type Code"(PO,S,S) =
Account"."All" Is null 'And' ( INVENTORY 'Or' "Destination Type
"Destination Type Code"(PO,S,S) = DROP SHIP)
Code"(PO,S,S) = INVENTORY Meaning system fetches the variance
'Or' "Destination Type account from Purchase Order Charge
Code"(PO,S,S) = DROP SHIP) account.
9. How to customize the Accrual account code combination for a specific requirement
Use the standard Purchasing Accrual Account Rule OR follow the same steps to create new rule
from scratch as mentioned for Variance account or Charge account.
These are used for Global procurement scenarios where Supply Orchestration is involved.
These two accounts are used for more advanced procurement scenarios where there is an
intercompany transaction involving a procuring organization and a destination organization.
11. How to check if data security rules are enabled for an account segment or code
combination.
• Go to Task "Manage Key Flex-fields", Search for "GL#' as Key Flex-field Code.
"General Ledger" should be returned. Click on action "Manage Structures".
• Manage Key Flex-field Structures, Search for the structure customer defined. Click
on the "Edit"
• For each segment, Edit the segment to check the "Default Value Set Code". List
down all the value sets used each segment.
• Go to Task "Manage Value Sets". For each value set, Edit it. Please review if it is
"Security enabled" and "Data Security Resource Name" is set.
If yes, the user needs to have the data security to use the segment.
Cross-validation rules prevent the creation of combinations with values that can't coexist in the
same combination
Suppose your accounting key flexfield has an Organization segment with two possible values, 01
and 02. You also have a Natural Account segment with many possible values, but company
policy requires that Organization 01 uses the natural account values 001 to 499 and
Organization 02 uses the natural account values 500 to 999. You can create cross-validation
rules to ensure that users can't create a general ledger account with combinations of values
such as 02-342 or 01-750.
Note: Cross-validation rules have no effect on combinations that already exist. The flexfield
treats any existing invalid combinations that pre-date the rule as valid.
If you want to prevent users from using previously existing combinations that are no longer valid
according to your cross-validation rules, manually disable those combinations using the
combinations page for that key flexfield.
13. Charge account generation based upon DFF For Requisition/Purchase order.
Navigation
Setup and Maintenance → Global Search → Manage Account Rules
Suggestion: - It is always recommended to create account rule from scratch using create option.
Requirement: To derive the Company Segment for PR/PO charge account based on the DFF
value captured.
Add the new account rule “XX_Purchasing_DFF_Company” with below conditions listed.