My Oracle Support Banner

FAQ on DM_FUSA TMP Files (Doc ID 2340726.1)

Last updated on MARCH 25, 2019

Applies to:

Oracle Communications Billing and Revenue Management - Version and later
Information in this document applies to any platform.


 On : version, Paymentech Manager

The integration of Billing and Revenue Management (BRM) with Chase PaymentTech is going through OOB DM_FUSA. There are few refunds present in the Chase PaymentTech DFR (return) file but not present in the BRM system.  

An example of tmp file:
S643445T1,1d51150,91a   BVIFF138A266D64357C3444313331313742353636463532323932313537363436303539353337343433353930353030344236323539363231383133363235373537363836303435373309190000000049958403027 171030      I4N
S643445T1,1d51150,91b   BVIFF138A266D64357C3444313631343739353736463536323132423534363036373542353837343432353930353030344236323539363231383133363235373537363836303435373309200000000029958401007 171030039862I3Y

An example of DFR file:

Questions and Answers

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
Questions and Answers
 How to interpret those many files generated by FUSA dm under sys/dm_fusa/fusa_temp directory?
 How to obtain CC info or any other important info from these TMP files?
 Chase DFR doesn't have any transaction IDs for refund transactions. How to interpret Chase PaymentTech DFR files?

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.