SYSTEM redefaults Maximum Liability Amount as Maximum Contract Amount during modification of an Islamic LC contract in ILDTRONL Screen (Doc ID 2657244.1)

Last updated on JUNE 21, 2021

Applies to:

Symptoms

ACTUAL BEHAVIOR
---------------
SYSTEM posts accounting entries for Liability amendment amount for a dummy amendment of an Islamic LC contract

EXPECTED BEHAVIOR
-----------------------
Accounting entries for Liability amendment amount should be posted only when an LC amendment involving change of amounts is done

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Perform Issuance of an Islamic LC Contract with liability tolerance as 0
2. After SYSTEM defaults the maximum liability amount, modify the amount to another value and save and authorize
3. Then Unlock the contract and save with no financial change
4,. Verify if any accounting entries are posted and verify the SWIFT message generated on amendment authorization

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users are able to save Islamic LC Contracts with incorrect max liability amount leading to data inconsistency

Changes

 User modifies the SYSTEM defaulted maximum liability to another amount during Issuance

Cause

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