ALM Process Fails When Using Payment Schedule and Next Payment Date = Origination Date (Doc ID 2583636.1)

Last updated on SEPTEMBER 10, 2024

Applies to:

Symptoms

For Oracle Financial Services Asset Liability Management (ALM), when running an ALM Process, the process fails for instruments with the following characteristics:

1. Origination Date is in future
2. Origination Date is equal to Maturity Date
3. Origination Date is equal to payment date in FSI_D_PAYMENT_SCHEDULE

There is no error in the engine log but it ends with the following SQL:

Module Logging OFS Access module data: /* 307: io_id_pschdl::GetID_PSCHDL*/

Module Logging OFS Access module data: select
select FSI_D_PAYMENT_SCHEDULE.id_number,
FSI_D_PAYMENT_SCHEDULE.payment_date,
FSI_D_PAYMENT_SCHEDULE.instrument_type_cd,
FSI_D_PAYMENT_SCHEDULE.amount,
FSI_D_PAYMENT_SCHEDULE.identity_code
from FSI_D_PAYMENT_SCHEDULE
where FSI_D_PAYMENT_SCHEDULE.instrument_type_cd = 180.00000
and id_number = ' 111111111'
and FSI_D_PAYMENT_SCHEDULE.identity_code = 20190331.00000
order by FSI_D_PAYMENT_SCHEDULE.payment_date

There is nothing after this SQL.

Additionally, the following error exists in the nohup.out in $FIC_DB_HOME/bin:

# Problematic frame:
# C [libcftm.so+0x3612c] AllocPaymentLine(CF_INPUT_DATA&, ProcErr*, char const*, UDPATTERN*, UDBPMASTER const*, int, int*, BI_ISArrayAsVector<ID_PSCHDL_OUT>*, long*, int, HOLIDAYCODE*, int*)+0x8ec

Cause

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