My Oracle Support Banner

Facing an issue with populating derived_address, the postal code is not considered while updating address. (Doc ID 3009017.1)

Last updated on MARCH 13, 2024

Applies to:

Oracle Financial Services Behavior Detection Platform - Version 8.0 and later
Information in this document applies to any platform.

Symptoms

Facing an issue with populating derived_address, the postal code is not considered while updating address.
If a record exists in derived_address without the postal code and the same address now with postal code comes in FOTP, ideally mantas should create a new address in derived_address table with postal code populated. But mantas seems to relate the existing address with the new transaction and postal code is never entered in derived_address table in this case. Consequently postal code is not entered in FSDM for this transaction party. This is also evident from the bdf "DerivedAddress_FrontOfficeTransactioPartyStageInsert" which checks for an existing entry in the table without postal code.

"WHERE
NOT EXISTS
(SELECT
1
FROM
DERIVED_ADDRESS DA
WHERE
COALESCE(FOTPS.PARTY_ADDR_STRT_LINE1_TX, '~') = COALESCE(DA.ADDR_STRT_LINE1_TX, '~')
AND COALESCE(FOTPS.PARTY_ADDR_STRT_LINE2_TX, '~') =COALESCE(DA.ADDR_STRT_LINE2_TX, '~')
AND COALESCE(FOTPS.PARTY_ADDR_STRT_LINE3_TX, '~') = COALESCE(DA.ADDR_STRT_LINE3_TX, '~')
AND COALESCE(FOTPS.PARTY_ADDR_STRT_LINE4_TX, '~') =COALESCE(DA.ADDR_STRT_LINE4_TX, '~')
AND COALESCE(FOTPS.PARTY_ADDR_CITY_NM, '~') = COALESCE(DA.ADDR_CITY_NM, '~')
AND COALESCE(FOTPS.PARTY_ADDR_STATE_CD, '~') = COALESCE(DA.ADDR_STATE_CD, '~')
AND FOTPS.PARTY_ADDR_CNTRY_CD = DA.ADDR_CNTRY_CD
)
"

Changes

 Code Issue

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
References


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