PACS ANALYSIS DOCUMENT

BTMJ – MUFG Bank Limited - India

JIRA REFERENCE NUMBER : TSR-172893

ISSUE CREATION DATE : 14-OCT-2021

REOPEN DATE (If Any) : NA

JBASE REFERENCE : NA

Information in this document is subject to change without notice.

No part of this document may be reproduced or transmitted in any form or by any means,
for any purpose, without the express written permission of TEMENOS HEADQUARTERS SA.

© 2021 Temenos Headquarters SA - all rights reserved.

 PACS Analysis Document – TSR-172893

Document History
Author Version Date Description

Harresh M 0.1 18-Oct-2021 Initial Draft

Arun Sreedharan 1.0 18-Oct-2021 Reviewed

Comments:

{Add any comments here}

V2.0/May-21 Quality Assurance Internal Use

To view template history, please click here*
2
 PACS Analysis Document – TSR-172893

Table of Contents

1. Client/JIRA Information...................................................................................................... 4
2. Review Information............................................................................................................ 4
3. Symptoms.......................................................................................................................... 4
4. Problem Description.......................................................................................................... 4
5. Analysis............................................................................................................................. 4
6. Alternate Recommendations to the Client..........................................................................4
7. Steps for Recreation.......................................................................................................... 4
8. Code Analysis.................................................................................................................... 5
9. Code fix Suggestion........................................................................................................... 5
10. Supporting Screen Prints for the Problem...............................................................5
11. Expected Solution to the Problem...........................................................................5
12. Action to Be Carried Out......................................................................................... 5
13. Area details............................................................................................................. 5

V2.0/May-21 Quality Assurance Internal Use

To view template history, please click here*
3
 PACS Analysis Document – TSR-172893

1. Client/JIRA Information

Product : FT
Priority : HIGH
Product Release: 202101
System status : TEST
Database : ORACLE
Front end : BROWSER

2. Review Information

Analysed By : Harresh M
Reviewed By : Arun Sreedharan

3. Symptoms
ERROR - 191.AC.1-Mandatory header fields (&) missing#DEPARTMENT COMPANY
CODE".

4. Problem Description
System throws the error ; ERROR - 191.AC.1-Mandatory header fields (&)
missing#DEPARTMENT COMPANY CODE" on MT191 generation

5. Analysis
MUFG Bank is currently doing implementation in India. They are generating MT191 from
AC.CHARGE.REQUEST with ReceiverBIC alone and if this is done system throws the above
error message . System populates this properly when DebitAccount is specififed and same
behavior is expected when ReceiverBIC alone is provided and this needs to be fixed in
202101 release

6. Alternate Recommendations to the Client

NA

7. Steps for Recreation

1. Take 202101 environment with all latest updates

V2.0/May-21 Quality Assurance Internal Use

To view template history, please click here*
4
 PACS Analysis Document – TSR-172893

2. Create a AC.CHARGE.REQUEST record with ReceiverBIC alone and authorise it

3. Now create another record with DebitAccount and authorise it
4. Observe the DOH records and messages generated

8. Code Analysis
AC.CHG.REQ.DELIVERY

BEGIN CASE
CASE customerRecord
HANDOFF.INFO(5) = customerRecord
CASE ReceiverBic AND SwiftToRaise MATCHES "1N'91'"
HANDOFF.INFO(5)<ST.Customer.Customer.EbCusCoCode> =
EB.SystemTables.getIdCompany()
END CASE

*
** Build HEADER record
HANDOFF.INFO(3)<1> = EB.SystemTables.getIdCompany()
HANDOFF.INFO(3)<2> =
EB.SystemTables.getRNew(FT.AdhocChargeRequests.AcChargeRequest.ChgChargeCcy
)
HANDOFF.INFO(3)<3> = R.ACCOUNT<AC.AccountOpening.Account.DeptCode>
HANDOFF.INFO(3)<4> = EB.SystemTables.getIdNew()
HANDOFF.INFO(3)<5> =
EB.SystemTables.getRNew(FT.AdhocChargeRequests.AcChargeRequest.ChgTotalChgA
mt)
HANDOFF.INFO(3)<6> = customerKey

Here if Account is present they are defaulting DeptCode and CO.CODE is defaulted if
ACCOUNT is present (DE.MAPPING set up is done like this). In our case only ReceiverBic
will be there so these fields are not defaulted . So when ReceiverBic is present system should
default these fields too

9. Code fix Suggestion

NA

V2.0/May-21 Quality Assurance Internal Use

To view template history, please click here*
5
 PACS Analysis Document – TSR-172893

10.Supporting Screen Prints for the Problem

V2.0/May-21 Quality Assurance Internal Use

To view template history, please click here*
6
 PACS Analysis Document – TSR-172893

11. Expected Solution to the Problem

System should generate MT191 when ReceiverBIC alone is provided like that of account
case

12.Action to Be Carried Out

This issue needs to be fixed in 202101 T24 release

V2.0/May-21 Quality Assurance Internal Use

To view template history, please click here*
7
 PACS Analysis Document – TSR-172893

13.Area details
Server Information : NA
User name : NA
Password : NA
Backup available until : NA
Tar Backup Details : NA

*Template History (in footer) only applicable for templates and checklists

V2.0/May-21 Quality Assurance Internal Use

To view template history, please click here*
8