Authorization Code Is Generated Only Once (Doc ID 455885.1)

Last updated on FEBRUARY 27, 2017

Applies to:

Oracle Service Contracts - Version 11.5.10.2 and later
Information in this document applies to any platform.

Symptoms

Find that Credit card authorization code is generated only once even when the contract is rejected and repriced with new pricing amounts. The system still uses the old authorization code of the old amount.

EXPECTED BEHAVIOR
Since the price of the contract is changed, they expect to get a new authorization code from the payment system.

Steps To Reproduce:
1. Enter a contract through Oracle Contracts
2. Under Pricing/Billing tab, set the payment type as Credit card
3. Enter credit card number as 4111111111111111 , Expiry as 12/08
4. Save the record. Since the credit card encryption patch is applied, the credit card number is
changed to XXXXXXXXXXXX1111
5. Action -> Check QA -> QA check completed successfully
6. Action -> Approve contract ->
Upon Submitting for approval, the QA check performs a Credit Card Authorization in which it
passes and the Authorization code is generated.
Using help >> Diagnostics >> Examine, check the CC_AUTH_CODE value
7. Reject the Approval notification
8. Increase the duration of the contract and reprice the contract.
9. Since the price of the contract is changed, they wish to get a new authorization code from the
payment system. However system is using the old authorization code of old amount.
10. Query the contract again, navigate to the Summary >> Pricing/Billing and do the
following on the credit card section:
Using help >> Diagnostics >> Examine, check the CC_AUTH_CODE value
The value is the same as step 6.

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