My Oracle Support Banner

In LC Incorrect Population Of 78 In Eport LC MT707 When Benficiary Confirmation Required Is Yes (Doc ID 2637310.1)

Last updated on FEBRUARY 10, 2020

Applies to:

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

Symptoms

On : 12.2 version, Implementation Support

ACTUAL BEHAVIOR
---------------
Incorrect Population of 78 in Export LC MT707 when Beneficiary Confirmation required is Yes

EXPECTED BEHAVIOR
-----------------------
On save and authorize, the system should populate the tag 78 with the same data.

STEPS
-----------------------
 The issue can be reproduced at will with the following steps:
Case 1:: Export LC
1. Export LC is created such that the field 78 of MT710 is populated via the FFT ‘INSTRUCTION’
2. MT 710 is generated with the data as input in field 78.
3. 3) Amendment is performed from LCDAMEND with Beneficiary Confirmation required; the system automatically defaults the previous data to the corresponding FFT for the FFT ‘INSTRUCTION’. Note that this was being automatically populated for Import from MT700 to MT707.
4. On save and authorize, the system populates the tag 78 with the same data.

Case 2: Import LC

1. Import LC is created such that the field 78 of MT700 is populated via the FFT ‘INSTRUCTION’
2.MT 700 is generated with the data as input in field 78.
3. The amendment is performed from LCDAMEND; no change is done on the instruction FFT and the system automatically defaults the previous data to the corresponding FFT.
4. On save and authorize, since no changes where done on the Instruction Field, MT707 is generated without the tag 78.
5. For export LC : (A) Export LC is created such that the field 78 of MT710 is populated via the FFT ‘INSTRUCTION’
(B) MT 710 is generated with the data as input in field 78.
(C)The amendment is performed from LCDAMEND; the system automatically defaults the previous data to the corresponding FFT for the FFT ‘INSTRUCTION’. Note that this was being automatically populated for Import from MT700 to MT707.
(D) Despite step 3, to verify the 78 generation logic in MT707, populate the FFT ‘INSTRUCTION’ with the same data as input in 710.
BUSINESS IMPACT
(E) On save and authorize, the system populates the tag 78 with the same data.
(F) Also while simulating in the QA environment, please note that the system is also populating field 47B, Without any change in what was populated in 710.
-----------------------
The issue has the following business impact:
Due to this issue, users cannot create a LC

Changes

 Fix provided to populate 78 in MT707 only if there is a change from the previous version

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.