Can One Manually Store Auth Codes In Oe_order_headers_all.credit_card_approval_code? (Doc ID 1913234.1)

Last updated on JUNE 22, 2017

Applies to:

Oracle Order Management - Version 12.1.3 and later
Information in this document applies to any platform.
***Checked for relevance on 04-APR-2016***

Goal

You are not using iPayments but a 3rd Party Credit Card Processing Company.

Can user use this oe_order_headers_all.credit_card_approval_code to populate the card number?
Trying to avoid using another flexfield for this value. Any suggestions on where other customers
store this value?

Summary Of Issue
Since you are using a 3rd Party Credit Card Processing, the company makes a call
to an outside credit card processing company and they give us an authorization code that
the user later manually run through the system. The user needs a place to store the
authorization code in the oe_order_headers_all table. There is already was a column
oe_order_headers_all.credit_card_approval_code.

Need clarification IF the users can use this field to populate the card number. Trying to
avoid using another flexfield for this value is this feasible.
 

Solution

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