Decomposition Not Working As Expected For Skinny Branch IC Accounting Scenario
(Doc ID 2998946.1)
Last updated on JANUARY 28, 2024
Applies to:
Oracle Financial Services Accounting Foundation Cloud Service - Version NA and laterInformation in this document applies to any platform.
Goal
Requirement:
User has the requirement to record customer balances and accrued interest on one Legal Entity ( eg : GB3) as intercompany assets or liabilities against another Legal Entity eg : (GB7).
Use Case:
Source system will send customer cash account balances and accrued interest transactions along with customer mapping data to Oracle. Oracle generates intercompany accounting entries for both cash account balances and accrued interest for GB3 branch. Send the entries back to AFCS and posts to GL. The balances in AFCS (Extended Code Block level) and GL (COA level) will get updated.
Issue observed for this scenario:
Upon validating the processed data for this scenario within AFCS, observed issues in decomposition.
User have registered an SLA with AHCS and have posted the aggregated journals data. The journals are accounted in the ERP.
As part of back feed, the decomposition process is picking up only those journal lines received from ERP for decomposition whose credit/debit indicator is matching with the corresponding sourced journal line. This is resulting in movements computation of only one leg (debit or credit).
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Goal |
Solution |
References |