In R12, We have an option to select whether to use FA Account Generator Workflow or not. In case, we wish not to use FA Account Generator workflow, Sub Ledger Accounting (SLA) will generate FA accounts.
The profile option to control this is:
FA: Use Workflow Account Generation. This should be 'Yes' (By Default 'No' if it is null) to use workflow Account Generator.
Based on this profile option, the FA Account Generator Workflow is conditional, while SLA is always used.
This post explains how SLA works in case of the profile option FA: Use Workflow Account Generation is set to No, which means FA Account Generator is not being used.
Note: This view is in context when Payables Code Combination is also null along with code combination generated by FA Account Generator workflow.
Oracle provides default SLA Application Accounting Definition setup. If this meets the requirements, SLA customization is not required and we can use the seeded AAD.
SLA Application Accounting Definition looks like following.
AAD is setup for different Event Classes and Event Types which has Journal Line Definition Assignments. To see the sla rules for particular event class, for example: 'Additions', place the cursor on desired event class and click on Journal Line Definition Tab.
JLD has different Journal Line Assignments, For Example: 'Assets Addition Cost' which has Account Derivation Rules. ADRs can be for all segments or we can create rules for individual segments based on the requirements. Here, the Rule Name and Description shows which is the source to derive account segments.
If you see, for Natural Account segment, rule name and description says, the source is Asset Categories window and for Balancing Segment, Asset Assignments window and for all other segments, source is Book Controls window.
To see the rule in detail, place the cursor on desired ADR rule(For Example: Natural Account Segment field), and click on Account Derivation Rule tab.
Here, we can create the conditions for ADR, where the ADR works only if the conditions are met. In this case, the ADR derives the Account segment from Asset Categories window to build account code combination when the code combination generated by FA Account Generator workflow is null.
We can also map the segment values by using the value type as Mapping Type, where we can provide constant values or Input-Output segments mapping according to the requirements.
Default Sources when using Oracle Seeded AAD:
---------------------------------------------------------------------------------
Following image represents the default sources when we are using the default SLA setup provided by Oracle.
This shows different Event classes/types in first level, account types/journal line types in second level and default sources to derive segment values for generating the Account code combinations in third level.
The profile option to control this is:
FA: Use Workflow Account Generation. This should be 'Yes' (By Default 'No' if it is null) to use workflow Account Generator.
Based on this profile option, the FA Account Generator Workflow is conditional, while SLA is always used.
This post explains how SLA works in case of the profile option FA: Use Workflow Account Generation is set to No, which means FA Account Generator is not being used.
Note: This view is in context when Payables Code Combination is also null along with code combination generated by FA Account Generator workflow.
Oracle provides default SLA Application Accounting Definition setup. If this meets the requirements, SLA customization is not required and we can use the seeded AAD.
SLA Application Accounting Definition looks like following.
AAD is setup for different Event Classes and Event Types which has Journal Line Definition Assignments. To see the sla rules for particular event class, for example: 'Additions', place the cursor on desired event class and click on Journal Line Definition Tab.
JLD has different Journal Line Assignments, For Example: 'Assets Addition Cost' which has Account Derivation Rules. ADRs can be for all segments or we can create rules for individual segments based on the requirements. Here, the Rule Name and Description shows which is the source to derive account segments.
If you see, for Natural Account segment, rule name and description says, the source is Asset Categories window and for Balancing Segment, Asset Assignments window and for all other segments, source is Book Controls window.
To see the rule in detail, place the cursor on desired ADR rule(For Example: Natural Account Segment field), and click on Account Derivation Rule tab.
Here, we can create the conditions for ADR, where the ADR works only if the conditions are met. In this case, the ADR derives the Account segment from Asset Categories window to build account code combination when the code combination generated by FA Account Generator workflow is null.
We can also map the segment values by using the value type as Mapping Type, where we can provide constant values or Input-Output segments mapping according to the requirements.
Default Sources when using Oracle Seeded AAD:
---------------------------------------------------------------------------------
Following image represents the default sources when we are using the default SLA setup provided by Oracle.
This shows different Event classes/types in first level, account types/journal line types in second level and default sources to derive segment values for generating the Account code combinations in third level.
