My Oracle Support Banner

LCDTRONL : After modificaiton of Customer Number (CIF) in Beneficiary Details, same LC contract can't be mapped to any BC contract. (Doc ID 2573472.1)

Last updated on AUGUST 18, 2019

Applies to:

Oracle FLEXCUBE Universal Banking - Version 12.0.3 and later
Information in this document applies to any platform.


1. User booked a LC contract by mapping a CIF in Beneficiary details.
2. There is no BC contract booked under the LC.
3. User amended the LC contract and changed the Beneficiary ID to a different CID.
4. Post save & authorization of LC amendment, same LC contract is not available to map a newly created BC contract ( LC ref No LOV in BCDTRONL ).

After modification of Beneficiary ID in LCDTRONL, modified LC contract should be available to map to while booking a new BC contract (LC ref No LOV in BCDTRONL).

The issue can be reproduced at will with the following steps:
1. Query one LC contract in LCDTRONL screen and link a CIF in Beneficiary details.
2. Amend the LC contract and modify Beneficiary ID to a different CID.
3. Save and authorize the record.
4. Create a BC contract in BCDTRONL screen and try to map the modified LC contract.
5. Modified CL contract won't be available in the LOV.

The issue has the following business impact:
Due to this issue, users cannot map any LC contract with a new BC contract, if Beneficiary ID is modified to a different CID of the LC contract.


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

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