9642 ajaz ahmed ppt_1_v2

Post on 05-Dec-2014

2.372 Views

Category:

Technology

0 Downloads

Preview:

Click to see full reader

DESCRIPTION

iReceivables - All you need to know Presentation at Collaborate 2012

TRANSCRIPT

iReceivables – All you need to know

Ajaz Ahmed Royal College of Physicians and Surgeons of Canada

aahmed@royalcollege.ca

1. To educate attendees how iReceivables could

be a tool of choice to empower internal or

external customers

2. To share practical experience in implementing

iReceivables and integrating a 3rd party

payment system

Objectives:

1. Salient Features

2. Product Functionality

3. Security Considerations for iReceivables

4. Integration Nuts and Bolts

5. Integration with 3rd Party Payment Systems

6. Conclusion

7. Other Important Information

8. Q & A

Topics:

• Self-service access to view real-time balance

and transaction information.

• Customers can Pay their invoices online.

• Customers can Dispute an invoice

• Customers can Print their invoices using Bills

Presentment Architecture (BPA) templates

1. Salient Features:

iReceivables Salient Features

iReceivables is a bolt-on module to Oracle

Receivables. Transactions or activities in Oracle

Receivables can be visible to a customer

logged on to iReceivables.

Customers have access to their accounts on

24/7 basis using internet

2. Product Functionality:

Accounts Summary / Detail pages

Clicking on any of

the hyperlinks in the

Accounts Summary

area would open the

Account Details

page.

Accounts Summary / Detail pages

Transactions can be

further drilled down

for details.

An invoice can be

selected to print,

make an online

payment or to

register a dispute.

Online Payment Pages

iReceivables uses Oracle Payments for payment

processing.

A 3rd Party Payment System integration with Oracle

Payments is required to facilitate online payment

functionality in iReceivables.

Online Payment Pages

iReceivables offers

an intuitive payment

page.

On successful

payment processing,

a confirmation is

returned to customer

with an authorization

code.

Online Payment Pages

Customer’s balance

gets updated.

A Receipt is

generated in

Receivables and

applied to the

selected invoice.

1. User makes online Payment

2. Payment details passed to Oracle Payments engine

3. Oracle Payments formats the Payment and passes it to

Payment Gateway

4. Payment Gateway communicates it to Payment Processor

5. Payment processor contacts CC issuer

6. CC issuer authorizes or rejects a payment request

7. Authorization result is transmitted back to the customer

Online Payment – Credit Card approval flow

Start

Credit Card

details valid?

iReceivables

user initiates

online

payments

request

Return a

Message to

User

NoYes

Pass Payment

Information to

Oracle

Payments

Servlet

Oracle Payment

formats the

Payment

instruction and

passes it to

Payment

Gateway = PayPAL

Gateway

communicates

with Payment

processor =

Moneris

Payment Processor

communicates it to

Credit Card Issuer and

transmits response

back to Gateway, to

Oracle payments and

to iReceivables

Payment Page

Payment

Authorized?

No

Create a

Receipt in

Oracle

Receivables

with status =

Confirmed

End

Response from Gateway Yes

1

2

3

4

5 6

7

Online Payment – Credit Card approval flow

Payment processing is a two-

step process.

After authorization, “Automatic

Remittances Master Program”

needs to be run in Oracle

Receivables to settle all

authorized funds.

Dispute Processing

Two types of approval

hierarchies – primary

and non primary

Workflow (WF) routes

approval requests.

Two types of

Approvals Workflows

Dispute Processing

Dispute reasons can

be set using FND

Lookup codes.

Registering a dispute

results in launching a

Credit Memo.

Request is routed

through the approval

hierarchy.

All supported configurations for making iReceivables

accessible via the internet to external users require use of

Demilitarized Zone (DMZ) protected with firewalls to ensure

that only authorized traffic is allowed to cross firewall

boundaries.

This arrangement ensures that even if intrusion attempts

against the DMZ are successful, it remains contained within

the DMZ, leaving EBS inside the intranet unaffected.

3. Security considerations for iReceivables

3. Security considerations ….cont’d

iReceivables seamlessly integrates with a number of

Oracle EBS R12 modules after the required

implementation steps are followed.

Oracle Payments’ integration with third party Payment

Processors or Gateways is required to allow

iReceivables customers to pay online.

4. Integration: Nuts and Bolts

Integration: Nuts and Bolts …cont’d

ARI_CONFIG package allows modifications to the followings:

• Account Summary page’s information, discount alerts and

dispute status section

• Contact Us global button e-mail address

• iReceivables transaction search and customer search

Dispute pages can also be customized.

iReceivables messages can also be edited using look up codes.

iReceivables - setups

Three setup tabs:

Profiles:

- to setup OIR profile values

Rules:

- to setup rules that offer a high degree of

flexibility

System parameters:

- to setup Credit Card Receipt Method and

Bank Account Payment Method.

iReceivables – setups

Receipt Class with creation

method of Automatic and

defining at least one Receipt

Method associated with this

Receipt Class.

Approval limits for Credit

Memo and defining a Credit

Memo batch source

Receivables – setups

System Security to setup

encryption. Oracle Wallet

needs to have been defined

beforehand.

Payment Systems to setup

3rd Party Payment

Gateway/Processors

Payment Methods, Payees

and Credit Card Brands

Oracle Payments – setups

Oracle Bills Presentment Architecture (BPA) – setups

-Data Sources configuration

-Template Management

-Template Assignment

Template Assignment Rules

define criteria to automatically

pick desired template for

viewing and printing.

Internal and external users

Function security for external users

Indexing customers database

Document Sequence

System Profile values

Oracle Sysadmin – setups

Oracle Workflow (WF) – setups

Two predefined types of workflows for Credit Memo approvals:

1. AR Credit Memo Approval Request (ARCMREQ)

(Uses Oracle HR hierarchy or Approval limits based hierarchy)

2. AR Credit Memo using AME

(Uses Oracle Approvals Management (AME))

Set the “AR: Use Oracle Approvals Management in Credit Memo

Workflow” profile option to Yes.

Oracle Workflow (WF) – setups

Credit Memo

request is

sent from

iReceivables

Collector

receives

and sends

to approver

Receivable

Role

approves;

CM created

Non-Primary Approvers hierarchy

Primary Approvers hierarchy

• Primary path: based on Approval Limits defined in Oracle Receivables

• Non-Primary path: based on the Oracle HR resources position hierarchy

Payment Systems requiring open network (internet) connectivity:

• PayPal

• Cybercash

• Concord EFSNet

Payment systems using non-open networks (e.g., a leased line):

• First Data North

• Paymentech

5. Integration with 3rd Party Payment Systems

PayPal plug in for R12 – Payflow Pro(formerly Verisign):

PayPal has developed its own integration with Oracle Payments R12.

Plug-in is fee to download and installation is simple.

Package contents: 7 Jar files, 3 config files, a SQL script and docs

Installation: involves copying files, editing class paths and adding

servlet entries to system config files, running autoconifg, runnng SQL

script and bouncing concurrent manager and webserver. Oracle

Payments setup is used to define PayPal payment system and Payee

Integration with 3rd Party ….cont’d

Implementation setups are spread over a number of EBS modules

Integration of Payment System could become a complex task

Setting up Oracle Wallet and security certificates are technical tasks

Select payment system based on type of payment processing

requirements – credit card, pin-less debit card or ACH transfers

PayPal Payflo Pro Gateway solution is very easy to implement

Complying with PCI security standard is a requirement, follow

Payment Applications Best Practices document available at Metalink

6. Conclusion

Consult a network architect to design and configure a DMZ based

configuration for making iReceivables accessible to customers while

safeguarding rest of the EBS from the possibility of any intrusion

attack

Plan a phased roll-out

Customers can be provided with ‘how to’ links in Related Information

area of home page

Like any web application, older browser version used by customers

to access iReceivables may often result in support calls

Conclusion…cont’d

Oracle Notes • Payment Applications Best Practices [ID 738344.1]

• Oracle E-Business Suite R12 Configuration in a DMZ [ID 380490.1]

• Tips and Queries for Troubleshooting Advanced Topologies [ID 364439.1]

• iReceivables uptake of Oracle Payment [ID 414659.1]

• How To Setup a Wallet At R12 Level In scope Of PA-DSS Implementation? [ID

1118887.1]

Useful links https://support.oracle.com/CSP/ui/flash.html

https://www.paypal.com/cgi-bin/webscr?cmd=_payflow-gateway-overview-outside

http://www.pcisecuritystandards.org

http://www.pcicomplianceguide.org

7. Other important information

Q & A

top related