Download as pdf or txt
Download as pdf or txt
You are on page 1of 33

8/18/2017 Document 1164613.

Payments In Order Management In R12 (Doc ID 1164613.1)

In this Document

Purpose
Scope
Details
Terminology
CVV2 / CVC2
CID
Address Verification Service (AVS)
Authorization
Process Flow
Customer enters transaction
Credit Card Encryption
Credit Card Authorization
Credit Card Encryption
Profiles
Mandatory Setups
Payee Set up
Obsoleted profile and system parameters in R12
Test case
Multiple Prepayments and Reversal of receipt
Test Case for Defer Payment and Refunds
Copy Order
Error Message
References

APPLIES TO:

Oracle Order Management - Version 12 to 12.2.2 [Release 11 to 12.2]


Information in this document applies to any platform.
***Checked for relevance on 30-Oct-2012***
***Checked for relevance on 08-Mar-2017***

PURPOSE

The purpose of this page is to walk through the setup required for payments and multiple prepayments using Credit Card or
Cash in Oracle Applications Release 12.

It is primarily intended as an aid to Support Engineers building a testcase, but has been given a Status of 'Published' so that
external users can also view the content and attached files.

SCOPE

This note is intended as an aid for any users trying to understand the basics of Payments.

The Customer is paying the amount using credit card / Cash. This testflow assumes that you are working in a Vision
environment.
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=87o5hpl90_126&id=1164613.1 1/33
8/18/2017 Document 1164613.1

The Setup Steps include the relevant setup needed to create a testcase for understanding PrePayments functionality. Some of
these steps only require viewing the setup that already exists in the Vision environment. If the Setup Steps are already done,
one can go directly to the Testflow Steps to repeat testcase.

The functional flow is changed from Release 11i. All the below mentioned test cases belong to Release 12 and above.

DETAILS

Terminology

CVV2 / CVC2

Card Verification Value 2 / Card Validation Code 2,


CVV2 is for Visa Card and CVC2 is for MasterCard.

A CVV2 / CVC2 code is a security feature of a credit card. It is an extra 3-digit number printed, but not raised, on the back of
the card. By verifying this code of a customer’s card, one can be sure the customer has the card in front of him. This along
with address (and zip code) verification (AVS) is used to prevent fraud. To provide extra security, merchants do not store the
CVV2 / CVC2 code. Additionally, one can provide a secure connection that encrypts the card information before it is
transmitted over the Internet. The credit card companies require this code be provided on each sale for protection against
fraud.

CID

Card Identification Number.


CID is the CVV2 equivalent for American Express Cards.
It is a 4 digit, non-embossed number printed above the account number on the face of the card.

Address Verification Service (AVS)

An additional level of verification for credit card accounts. Address Verification Service is provided by MasterCard and Visa
Credit Card networks to match the billing address with the address that is maintained for the cardholder by the issuing bank.
Various AVS codes are returned based on the complete match, zip code match, street address match etc.

Authorization

Authorization is the process in credit card processing term for requesting the credit card company to reserve a specific amount
from the customer’s account for a pending transaction. It does not actually charge the account - that is done during the
‘capture’ transaction. An authorization code is returned by the credit card company, and that code should be used in the
subsequent ‘capture’. Authorization code typically expires after a specified number of day , this could be from couple of days
to 2 weeks , depending on the credit card issuer.

Process Flow

Customer enters transaction

On the websites, customers will fill the necessary details including credit card information.

Credit Card Encryption

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=87o5hpl90_126&id=1164613.1 2/33
8/18/2017 Document 1164613.1

The next step is from Order Management. From the websites, orders are created in the Applications.

1. Provide the CC details on the Order


The web orders are interfaced into OM. iStore orders will come through as booked but could be on hold if it fails CC
authorization.

2. Based on System Security Options Input Security Code is made mandatory/optional

Credit Card Authorization

Book and Authorize order

Order Booking triggers the CC authorization. If the order fails authorization, it is put on Authorization Hold and needs to be
authorized manually. Batch authorization is not yet available.

If Oracle Payments Payment Administrator (iPayment) is not installed, Credit Card authorization is not triggered. In this case,
Credit Card is only for information purpose.

Credit Card Encryption

Navigate to Oracle Payments Payment Administrator -> Oracle Payments Setup


Shared Setups -> System Security Options

ppset1.jpg
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=87o5hpl90_126&id=1164613.1 3/33
8/18/2017 Document 1164613.1

Click Go To Task

ppSnap3.jpg

If the Require Security Code Entry is set to Yes, then on entering the payment method on the Sales Order , as Credit card,
security code field becomes mandatory.

The result of the above setup results as below

cpp1.jpg

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=87o5hpl90_126&id=1164613.1 4/33
8/18/2017 Document 1164613.1

Profiles

OM: Credit Card Privileges

PPProfile.jpg

This one is currently used to mask the credit card number, approval code and to control the access to the credit card number
etc. attributes. It will be modified to only control the access to the credit card attributes, such as to enter or update the credit
card information.

This profile option should have two values in R12, “Yes” or “No”. User is only able to enter or update credit information if the
value is “Yes’, otherwise, all the credit card fields should be disabled, user can enter/update credit card related attributes,
otherwise user can only view the information. The masking of sensitive data including CC# and ACH/Direct Debit number in
the new data model will be controlled centrally by Oracle Payments.

Result of setting to No:

pptc1.jpg

Outcome of setting the profile to Yes is included in the Test Cases.

The above details are picked up from Customer Standard form -- Payment details for the site entered on the Order Header.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=87o5hpl90_126&id=1164613.1 5/33
8/18/2017 Document 1164613.1

ctsddform.jpg

To create new credit card entries click on the Add button on the customer standard screen , you can create new entries even
from the Sales Order form just by entering the credit card details and a subsequent save.

Mandatory Setups

Payee Set up

Payee setup is mandatory because an Operating Unit can be attached to one payee only i.e. there is a one – one mapping
between Operating unit and payee.

Based on the Operating unit selected while creating the order, the payee is selected based on the mapping set up in this
payee tab of Oracle Payments Payment Administrator responsibility.

So if there is a Payee already attached to an Operating Unit and you want to add another Payee, follow the steps below

Navigate to Oracle Payments Payment Administrator -> Oracle Payments Setup -> Funds Capture Setup -> Payee

ppset2.jpg

For Operating unit (Vision Operations) Payee (say Vision Online) payee status should be Active

Go to the payee tab and select the payee code 1234

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=87o5hpl90_126&id=1164613.1 6/33
8/18/2017 Document 1164613.1

ppset3.jpg

In the assign operating units node, make sure that the Operating unit on which the order is to be created (say Vision
Operations) is listed for the Vision Online payee.

Use the query below to find out the payee to which Vision Operations is currently attached.

select mpayeeid from iby_fndcpt_payee_appl where org_id=204;

Output :
61

select payeeid,name from iby_payee where mpayeeid=61;

Output
Payeeid Name
1234 Vision Online

This is because the Sample payment system and the payment system account are usually created and set up by default (in
most environments) for Vision Online payee.

From the Assign Operating Units node, ensure operating unit Vision Operations is attached to our Payee

ppset4.jpg

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=87o5hpl90_126&id=1164613.1 7/33
8/18/2017 Document 1164613.1

ppset5.jpg

The active payment channels for the current operating unit are the ones, which would be supported for this payee.

Obsoleted profile and system parameters in R12

Following OM profile options and system parameters related to credit card processing are now obsoleted in R12.

OM: Risk Factor Threshold for Electronic Payments

OM: Estimated Authorization Validity Period

OM: Number of Days to Backdate Bank Account Creation

OM: Payment method for Credit Card Transactions

OM: Process Payment Immediately at Booking

System Parameters: Enable Multiple Payments

Test case

Multiple Prepayments and Reversal of receipt

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=87o5hpl90_126&id=1164613.1 8/33
8/18/2017 Document 1164613.1

1. Create an order with one line.

tcc1.jpg

2. Enter the payment type as credit card along with credit card details.

tcc2.jpg

3. Book the order

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=87o5hpl90_126&id=1164613.1 9/33
8/18/2017 Document 1164613.1

tcc3.jpg

4. Approval Code is generated on Authorization

tcc4.jpg

Approval code is populated.

Now the authorization is completed successfully and Prepayment can be done.

5. Click Action -> Payments

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=87o5hpl90_126&id=1164613.1 10/33
8/18/2017 Document 1164613.1

tcc5.jpg

6. Check the Prepay Check box as below

tcc6.jpg

Checking the prepay check box will make amount column as mandatory. Either input the value for Percentage field or enter
the amount manually that is to be prepaid.

7. Click Process Payments button.


Now the prepaid amount gets updated.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=87o5hpl90_126&id=1164613.1 11/33
8/18/2017 Document 1164613.1

tcc7.jpg

The Credit card information is deleted once the payment is done.

tcc8.jpg

8. For second interim payment

a. Enter payment type as Credit card

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=87o5hpl90_126&id=1164613.1 12/33
8/18/2017 Document 1164613.1

tcc9.jpg

b. Save the order

tcc10.jpg
Authorization happens automatically since the order is already booked.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=87o5hpl90_126&id=1164613.1 13/33
8/18/2017 Document 1164613.1

tcc11.jpg

C. Action -> Payments

tcc12.jpg

d. Click Prepay check box and perform process payments for 100$ amount instead of %

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=87o5hpl90_126&id=1164613.1 14/33
8/18/2017 Document 1164613.1

tcc13.jpg

e. Click Process Payments button

tcc14.jpg

f. Now Authorized Amount is cleared since the payment is done for the mentioned amount

tcc15.jpg

g. Prepayment is done for complete amount specified

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=87o5hpl90_126&id=1164613.1 15/33
8/18/2017 Document 1164613.1

tcc16.jpg

9. Click on View Receipts button

tcc17.jpg

10. Click Open Button

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=87o5hpl90_126&id=1164613.1 16/33
8/18/2017 Document 1164613.1

tcc18.jpg

11. Open Receipts screen from Receivables

tcc19.jpg

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=87o5hpl90_126&id=1164613.1 17/33
8/18/2017 Document 1164613.1

tcc23.jpg

12. Click Reverse Button

tcc24.jpg
Now the receipt is reversed

Test Case for Defer Payment and Refunds

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=87o5hpl90_126&id=1164613.1 18/33
8/18/2017 Document 1164613.1

1. Create an order with one line and enter the credit card details

ac1.jpg

2. Click Action -> Payments button


Check Defer Flag

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=87o5hpl90_126&id=1164613.1 19/33
8/18/2017 Document 1164613.1

ac2.jpg
3. Click ok

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=87o5hpl90_126&id=1164613.1 20/33
8/18/2017 Document 1164613.1

ac3.jpg

4. Book the order

ac4.jpg

5. Now the hold is applied against the order for processing further.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=87o5hpl90_126&id=1164613.1 21/33
8/18/2017 Document 1164613.1

ac5.jpg

6. Run Process Pending Payments request

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=87o5hpl90_126&id=1164613.1 22/33
8/18/2017 Document 1164613.1

ac6.jpg
The request will authorize the payments and will remove the holds

7. Now the order is booked and authorized for 100 USD and now process payments for 100 USD

ac9.jpg
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=87o5hpl90_126&id=1164613.1 23/33
8/18/2017 Document 1164613.1

8. Then update payment amount as 50 USD

ac11.jpg

9. Details for test case to update the payment from 50 USD to 25 USD.

Check Prepay button and update the amount field directly to 25

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=87o5hpl90_126&id=1164613.1 24/33
8/18/2017 Document 1164613.1

ac12.jpg

9. Save the order

ac13.jpg

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=87o5hpl90_126&id=1164613.1 25/33
8/18/2017 Document 1164613.1

ac14.jpg

Now the Pending Process payment hold has been applied to the order.

10. Click Process Payments

ac15.jpg

ac16.jpg

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=87o5hpl90_126&id=1164613.1 26/33
8/18/2017 Document 1164613.1

ac17.jpg

11. Click View Receipts

ac18.jpg

When the Prepaid Amount of a Prepayment Credit Card Order is reduced in Order Management, the difference between the
amounts is not refunded on the Prepayment Receipt, but rather is put On Account if the Receipt has not yet been Remitted.
However, if the Prepayment Receipt is remitted before the Prepaid amount is changed on the Order, the difference is set as a
Refund, rather than On Account.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=87o5hpl90_126&id=1164613.1 27/33
8/18/2017 Document 1164613.1

Copy Order

Enforce setup for security code to Yes (Require Security Code Entry is set to Yes).

cppsetup.jpg

1. Create an order with payment type as Credit Card.

cpp1.jpg

Because of the above profile setup Security code is now a mandatory field.

2. Click Action -> Copy

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=87o5hpl90_126&id=1164613.1 28/33
8/18/2017 Document 1164613.1

cpp2.jpg

Error Details

Message Text : Security Code has been set as mandatory. Please uncheck Payments information to copy the order.
Message Name : OE_CC_NO_COPY_SEC_CODE_REQ
Message Number : 251792

3. Payments Check box is check when clicking Copy Function from Sales order form Action button

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=87o5hpl90_126&id=1164613.1 29/33
8/18/2017 Document 1164613.1

cpp3.jpg

4. Uncheck the Payments check box

cpp4.jpg

5. Click Ok.

Now new order is created by Copy action.


https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=87o5hpl90_126&id=1164613.1 30/33
8/18/2017 Document 1164613.1

cpp5.jpg

6. New order is created without payment details

cpp6.jpg

If Require Security Code Entry is set to No then the credit card details would get populated automatically without unchecking
the Payments check box.
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=87o5hpl90_126&id=1164613.1 31/33
8/18/2017 Document 1164613.1

the Payments check box.

Packages:

Copy Order
OE_ORDER_COPY_UTIL.Copy_Order (OEXUCPYB.pls)

Code flow table and packages

Oe_Prepayment_Pvt.Delete_Payments, Oe_Header_Payment_Util.Delete_Payment_at_header is used to update the payment


type code in oe_order_headers_all

Oe_payment_trxn_util.update_payment_trxn, OE_PAYMENT_TRXN_UTIL.Delete_Payment_Trxn - Update or Delete of the Trxn


extension id from OE_PAYMENTS table

Error Message

Existing in previous release

Scenarios Message Text Internal Name Availablity

Credit Card Authorization Payment of &AMOUNT has ONT_PAYMENT_AUTH_SUCCESS From R11i


success been authorized

Credit Card Authorization Credit card authorization for ONT_CC_AUTH_HOLD_APPLIED From R12
failure on account of this order has failed. The
payment authorization order has been placed on
Credit Card Authorization
Failure Hold.

Credit card authorization Credit card authorization for ONT_CC_ SECURITY_CODE_ From R12
success but security code this order has succeeded FAILED
related errors but with security code
warning. Order has been
put on Hold.

Risk management Risk management ONT_CC_RISK_HOLD_APPLIED From R12


evaluation failure evaluation for this order has
failed due to a high risk
credit card. The order has
been placed on Credit Card
High Risk Hold.

Error when calling Oracle The following error OE_VPM_IPAYMENT_ERROR From R11i
Payments occurred when calling
Oracle Payments for Credit
Card Authorization: (error
messages passed back by
Oracle Payments)

Credit Card Attributes Credit Card Security Code is OE_CC_SECURITY_CODE_REQD From R12
validations required for credit card
payment

Credit Card Expiration Date OE_VPM_CC_EXP_DT_REQUIRED From R11i


is required for Credit Card
Payment Authorization.

Credit Card Holder Name is OE_VPM_CC_NUM_REQUIRED From R11i


required for Credit Card
Payment Authorization.

Credit Card Number is OE_VPM_INV_TO_REQUIRED From R11i


https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=87o5hpl90_126&id=1164613.1 32/33
8/18/2017 Document 1164613.1

required for Credit Card


Payment Authorization

Invoice To is required for OE_VPM_CC_HOLDER_REQUIRED From R11i


Credit Card Payment
Processing.

Unable to set up a Credit OE_VPM_IPAYMENT_ERROR From R11i


Card Bank Account for the
Customer

Still Have Questions?


To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a
discussion in the My Oracle Support Order Management EBS Community.

Let us know your feedback!


We hope you find this information useful. Our desire is to provide the right information when you need it. Please let us know
how we are doing. To provide feedback on this note:

1. Select the "Rate this document" link. Depending on how you are viewing the note, you will find the link on the:
a) bottom left when viewing the note in a separate window.
b) upper right when viewing the note in the My Oracle Support window.

2. In the resulting pop-up box, enter your comments and ratings for the document.

3. Select Send Rating.

REFERENCES

NOTE:743389.1 - Order Management Testcase Repository Library


NOTE:395462.1 - Test Credit Card Numbers
Didn't find what you are looking for?

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=87o5hpl90_126&id=1164613.1 33/33

You might also like