My Oracle Support Banner

CASTR808: Auto-Split Function Not Behaving Correctly When Applying Domicile Account Split Logic (Doc ID 2737818.1)

Last updated on DECEMBER 21, 2020

Applies to:

Oracle Financial Services Regulatory Reporting - Version 8.0.0 and later
Information in this document applies to any platform.


When the Account transit is associated to a different legal entity than the location of the transaction, a split should occur such that the an STR is created for both the entity of the location of the transaction and for the entity of the account location. The transaction would be associated with the location of the transaction and a copy of the transaction would be created and associated with the account location.

Steps to Simulate: 

1. Login to CASTR and select a report which has transaction location and Domiciled Branch code are of different Reporting Entity
2. Take automatic split.

Actual: STR was created for the both location of transaction and account location but not all applicable (i.e. both) transactions were copied to the STR report for the entity of the account location.
- A second behavior was observed in the same test case where the STR report for the entity / location of the transaction was generated, no report was generated for the entity / account location

Expected: By taking automatic split action copy of the same report should get generated with Domiciled code Reporting entity.



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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.