R12: OIE: Credit Card Transactions Loaded A Second Time Become Unvalidated
Last updated on FEBRUARY 14, 2017
Applies to:Oracle Internet Expenses - Version 12.1.3 and later
Information in this document applies to any platform.
Visa VCF 4 Transaction Loader and Validation Program
Credit Card transactions become invalidated when the original transaction datafile is processed a second time by running the Visa VCF 4 Transaction Loader and Validation Program a second time against the same file. The second concurrent run did not create new transactions, but set the validate_code in table from AP_CREDIT_CARD_TRXNS_ALL for the existing ones to N.
No changes should be made to existing Validate transactions. The validate_code in table from AP_CREDIT_CARD_TRXNS_ALL should not be updated from Y to N.
The issue can be reproduced at will with the following steps:
1. Run the Visa VCF 4 Transaction Loader and Validation concurrent program against a new data file and the following in the concurrent log file:
6 credit card transactions were successfully uploaded.
Number of new credit card accounts registered: 4.
Validating 6 transactions.
Rows valid: 6.'
2. See the 6 transactions have validate_code in table AP_CREDIT_CARD_TRXNS_ALL set to 'Y'.
3. Submit a second run of the Visa VCF 4 Transaction Loader and Validation concurrent program for the same data file. The concurrent log shows
No credit card transactions were uploaded
4. Check the 6 previously loaded transactions and see that the validate_code in table AP_CREDIT_CARD_TRXNS_ALL now is set to 'N'.
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