Submit the Visa VCF4 Transaction Loader And Validation Program and Receive Unique Constraint Error (Doc ID 2111928.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Internet Expenses - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

Problem Description
--------------------------------------------------
Run the Visa VCF4 Transaction Loader and Validation Program and log shows the error
"...unique constraint AP.AP_CREDIT_CARD_TRXNS_U3 is violated..."


Client has been live with iExpense Application since April 2015 (ie. approximately 8 months)
For approximately 7.5 months, the client has been successfully loading their Visa VCF4 files with the seeded VCF4 Transaction Loader and Validation Program
Around Dec 12 2015, the client noticed that the 'Visa VCF4 Transaction Loader and Validation Program' log was showing the error
"...unique constraint AP.AP_CREDIT_CARD_TRXNS_U3 is violated..."
This same "...unique constraint AP.AP_CREDIT_CARD_TRXNS_U3 is violated..." error happened for 3 different Visa VCF4 credit card files.

The client had some preliminary discussions with Visa. Visa is saying that some credit card transactions can use
a duplicate reference number. Visa said that to identify if this transaction is unique they use card number, reference number, posting date, sequence number.

Normally, iExpense Visa Loader should  use card_id, card_program_id, reference_number to determine if a transaction is unique.
So, it appears based on the current VCF4 Transaction Loader and Validation Program design these transactions (that use duplicate reference numbers) are being rejected
as they violate the unique constraint (recall unique constraint is that combination of card_id, card_program_id, reference_number must be unique)


Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms