My Oracle Support Banner

APT_MOBILE_NUMBER, APT_FAX_NUMBER and APT_PAGER_NUMBER Not Migrated to Telecom table (Doc ID 2997370.1)

Last updated on JANUARY 13, 2024

Applies to:

Oracle Financial Services Lending and Leasing Cloud Service - Version 14.12.0.0.0 and later
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR
---------------
APT_PHONE in loan customer migration file does not migrate to servicing TELECOMS table

In loan customer migration file api_cusprim_111.dat, on providing APT_PHONE field as a valid phone number, APT_TELECOM_TYPE_CD as a valid value (ex: H) and APT_PERMISSION_TO_CALL_IND as Y, the APT_PHONE data does not migrate to itables (IAPPLICANT_TELECOMS) or to the servicing table (TELECOMS).

If the fields APT_MOBILE_NUMBER, APT_FAX_NUMBER and APT_PAGER_NUMBER are provided, all 3 migrate successfully to itables and servicing tables.

However if these are kept as NULL and only APT_PHONE is provided, no data migrated to TELECOMS. 

EXPECTED BEHAVIOR
-----------------------

System should populate the telecom details as provided during migration of application/applicant


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Prepare migration file and place in the api processing folder
2. Run the API batch jobs to process the migration file
3. Verify the system whether the details present in the migration file is displaye correctly



Changes

 

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.