My Oracle Support Banner

OBPM-OBCL || Swiftmsgtype Coming As 103/202 Instead Of Pacs.008.001.08 Or Pacs.009.001.09 For CBR Notification (Doc ID 3078723.1)

Last updated on APRIL 04, 2025

Applies to:

Oracle Banking Payments - Version 14.7.0.0.0 and later
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR
---------------
Swiftmsgtype coming as 103/202 instead of pacs.008.001.08 or pacs.009.001.09 for CBR Notification for MX payments.

For OBPM-OBCL MT103 xml translation, OBPM is sending 103 values against this "" tag instead of pacs.008.001.08. However, Pacs.008.001.08 value is required against SWIFTMSGTYPE tag to make xml translation work.

EXPECTED BEHAVIOR
-----------------------
Swiftmsgtype should be coming as pacs.008.001.08 or pacs.009.001.09 for CBR Notification from OBPM.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Send MT103 from OBPM to OBCL.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, OBPM MT103 xml translation cannot be done in OBCL.

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
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.