My Oracle Support Banner

CASTR 8.0.8: Attempted Transaction indicator is not saved in the backend (Doc ID 2714936.1)

Last updated on OCTOBER 01, 2020

Applies to:

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

Symptoms

Report: CASTR

Version:8.0.8.0.0

Problem description: The Attempted Indicator is not displaying in the Reporting Entity tab even though it was set to completed before approve action. Due to this user is facing below two issues:

1.After Auto split action, the Attempted Transaction indicator is not saved in the backend, but it is displayed in the GUI.
2.Generated e-file is missing the Attempted Indicator in the PART A1 which causes a file structure error on FINTRAC (error code 400).

Steps to reproduce this issue:
1. Login to ECM
2. Select a case with all the data and post to CRR
3. Login to CRR and select the posted report and take automatic split action on it
4. Now approve the report and generate E-file
5. FCT_REGULATORY_REPORT.V_REPORT_INDICATORS is null as user did not click on save in Reporting Entity tab. Hence null will get display in E-File which will lead to decrease the row length and E-file rejection.

Changes

1.Attempted Indicator is not displaying in the Reporting Entity tab

   

 

   

 

   

 

 

Cause

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
Symptoms
Changes
Cause
Solution


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