My Oracle Support Banner

Credit Card Orders fail In Autoinvoice With 'A transaction attribute has an invalid value for its type, or a mandatory parameter is NULL' when supplemental encyption is enabled (Doc ID 1945583.1)

Last updated on FEBRUARY 20, 2020

Applies to:

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

Symptoms

Credit Card Orders error in Autoinvoice with NULL Mandatory Parameter after applying secondary encryption

After enabling the Oracle Payments security option "Supplemental Data Encryption"for Card Holder name and Expiration Date, the Credit Card payment Sales Orders get stuck in interface table for Autoinvoice.

On the instance that does not have this security option enabled, there is no errors.
Autoinvoice for Sales Orders using credit card payment fails with errors -


 ERROR
-----------------------
ERROR A transaction attribute has an invalid value for its type, or a mandatory parameter is NULL .
Cause field iby.iby_fndcpt_tx_extensions.instr_sec_code_length is NULL for these Sales Order Credit Card approvals


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Enable the security option "Supplemental Data Encryption" in Payments setup
2. Try to run Autoinvoice and fails with errors

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


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