EB.DUPLICATE is not working for FOREX Application

The Settlement accounts of 2 deals were amended on Value Date, but the deals posted to the accounts previously specified

PLAIN.ARREARS market convention is not allowed to set SOD.MAT as "YES" for RFR swaps

After Upgrade to R21 some Forex & Swap COB Reports Header alignment is not properly Printed in &HOLD& , Below are the Core Report name which has the issue on Headers. FX.POSITIONS REVALUATION.ASSET.LIABILITY REVALUATION.SUMMARY REVALUATION.DETAIL FX.MATURITY FX.UNCONFIRMED.BY.COUNTERPARTY FX.EXCEPTIONS FX.DELIVERY FX.MATURED.DELIVERY SW.CCY.REVAL

A MM Placement contracts is inputted with SEND.PO EQ “HOLD”, post authorization if the SEND.PO is changed to NONE/RELEASE, PO is not generating.

Unable to create FX spot transaction. Getting error as MISSING FX.TRANSACTION.TYPE – RECORD (TRANSACTION.TYPE)

A Fatal error “** FATAL ERROR IN (UPD.INT.MOVEMENT.RUN) ** Unable to read SYSTEM record from INT.MOVEMENT.PARAM “ is thrown on trying to authorize FOREX record when INT.MOVEMENT.PARAM is not defined as IC module is not licensed for use.

MD.DEAL causing the sessions to time out, due to incorrect set-up in PM.GROUP.TYPE

MT 320 generation for auto-updating in MM deals

The Settlement accounts of MM deals were amended on Value Date, but the deals posted to the accounts previously specified

Please set the TRAN.CODE.START and TRAN.CODE.END in PM.PC.PARAM of POR.TRANSACTION as required.

Why the FOREX fields – “Payment Order Status” and “Payment Order Broker Status”  is not enabled with the option “HOLD” and “RELEASE”