Deciphering where Credit Card Report (SSRS) stores authorization expired info

Where does the base SSRS Credit Card Report gets the “Expired since ##/##/####” message for the pre-authorizations?

The CreditTran.ResponseMsg has “Approved” stored, not “Expired since”…

Here’s what our Reporting Manager found when he dug into it:

The report named ‘CreditCardRpt.rdl’ references the ResponseMsg field. When looking at the Report Data Definition for the report ‘CCRpt’ and the dataset properties of the report I see that the report is referencing the ‘ResponseMsg’ field from the CreditTran table. When I run a sql query against this table looking for the PNRef in the example below that field =’Approved’, not ‘ Expired since 2/24/2020’ as in the report.

I’d guess that you’re seeing the “magic” that happens inside an RDD. Not every column output by an RDD relates directly to an DB table.

That data is somewhere… But where? Is Epicor making a secret data exchange with ESDM based on a token we can’t use to hook onto? Would a trace show any clues if it’s turned on when running the Credit Card Report?

I think you’re going to need the help from someone like @hkeric.wci, or @josecgomez, that can look into the DLL’s to see what is going on behind the curtain.

If you think its just a combo of existing information (as opposed to being a calculation resulting in “new” info), you might just do some trial and error, running queries (BAQ or SQL) against related tables.

Or it’s encrypted somewhere, which is a best practice for the number, expiration, and 3 or 4 digit code.