TSV Not Writing Exception Records other than blank or 000

[Therone]

Hi,

It was found on our side that TSV as well as B24POS (TSVCOL and TXNCOL) do not write or extract transactions with exception records other than 000 or maybe blank. This issue might have an impact on reporting and also a huge impact on fraud reporting when using TSV.

702 [3] auth.excp^rsn^cde.byte[0:2] PIC X(3).
A reason code indicating why the exception flag is set.
This field is used only for exception records. For any other records, this field is set to blanks.

We have a case (00042527) open and IR is busy investigating.

Regards

[Juliana]

Hi Therone

To extract this field to show on TSVCOL record you need to do the following things

Step 1. Check whether this field "702 [3] auth.excp^rsn^cde.byte[0:2] PIC X(3)" is set in PTLF file under Customer transaction (head.rec^typ = "01").

Step 2. If Yes on Step 1, then Configure IRTSVCOI add the following line under the section of [TRANSACTION-LOG-LOCATION-<n>]

    FLD<n>= STRING(702,3)

Then restart Prognosis configuration, it should work.

If Step 1 answer is NO, the field  "702 [3] auth.excp^rsn^cde.byte[0:2] PIC X(3)" is set in PTLF file under Exception Record (head.rec^typ = "20" or head.rec^typ = "21") then you need to contact our consulting team to customise the log reader library irb24tlb for you to extract this field.

[Therone]

Hi Juliana,,

Thank you for your response.

In our case the Exception Record is "21" . Will there be any costs involved if we should request your consulting team to cutomise the log reader library?

Can I maybe suggest that IR look at this and make it a customer selection as it can cause serious fraud as well as transaction volume / value reporting issues.

Regards,

Therone

[Juliana]

Hi Therone

Because it involves some customisation and test so it will involves some cost.  Your suggestion will be passed to our product team.

Thanks & Regards

Juliana