My Oracle Support Banner

ASS_SUSPENSE_EXT.ERROR_CODE Is Not Set By FCT_Suspense For Rejected CDRs (Doc ID 779228.1)

Last updated on OCTOBER 15, 2019

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.3.1.0.0 to 7.3.1.0.0 [Release 7.3.0]
Information in this document applies to any platform.

Goal

CDRs that are rejected for various reasons get errors reported in the stream log and the dumps but the field DETAIL.ASS_SUSPENSE_EXT.ERROR_CODE is "0" (zero) instead of the highest level error code. This affects the mapping of suspence reason and subreason as well.

FCT_Suspense should be setting this value.

-- Steps To Reproduce:
Process any CDRs that contain validation errors.

From Registry file:

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

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