Last updated on SEPTEMBER 26, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 7.2.1 to 7.4.0]
Information in this document applies to any platform.
Invalid M record being sent by dm_fusa (Paymentech Manager).
Tried executing the bill run in one of the test environments and found strange records in the fusa send files (fusas* files) sent to Paymentech.
This is an example of a fusas generated by pin_deposit:
PID=945209 SXXXXCA SID=945209 CANADASI START 121122 01.7
S106209T1,d,0 DAX***********4376 11170000000053051241002 121120tst429
A21234 TEST ST
A3BARRIE , ON L9A 1A1
The line after the PID is showing an M record which was not generated in other environment and is causing the transactions to get flagged as failed on the Paymentech side.
Why is this records being inserted?
The issue is observed on BRM 7.2.1.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms