9642 ajaz ahmed ppt_1_v2


Published on

iReceivables - All you need to know
Presentation at Collaborate 2012

Published in: Technology
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

9642 ajaz ahmed ppt_1_v2

  1. 1. iReceivables – All you need to knowAjaz AhmedRoyal College of Physicians and Surgeons of Canadaaahmed@royalcollege.ca
  2. 2. Objectives:1. To educate attendees how iReceivables could be a tool of choice to empower internal or external customers2. To share practical experience in implementing iReceivables and integrating a 3rd party payment system
  3. 3. Topics:1. Salient Features2. Product Functionality3. Security Considerations for iReceivables4. Integration Nuts and Bolts5. Integration with 3rd Party Payment Systems6. Conclusion7. Other Important Information8. Q&A
  4. 4. 1. Salient Features:• 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
  5. 5. iReceivables Salient Features
  6. 6. 2. Product Functionality: 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
  7. 7. Accounts Summary / Detail pages Clicking on any of the hyperlinks in the Accounts Summary area would open the Account Details page.
  8. 8. 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.
  9. 9. Online Payment PagesiReceivables uses Oracle Payments for paymentprocessing.A 3rd Party Payment System integration with OraclePayments is required to facilitate online paymentfunctionality in iReceivables.
  10. 10. Online Payment Pages iReceivables offers an intuitive payment page. On successful payment processing, a confirmation is returned to customer with an authorization code.
  11. 11. Online Payment Pages Customer’s balance gets updated. A Receipt is generated in Receivables and applied to the selected invoice.
  12. 12. Online Payment – Credit Card approval flow1. User makes online Payment2. Payment details passed to Oracle Payments engine3. Oracle Payments formats the Payment and passes it to Payment Gateway4. Payment Gateway communicates it to Payment Processor5. Payment processor contacts CC issuer6. CC issuer authorizes or rejects a payment request7. Authorization result is transmitted back to the customer
  13. 13. Online Payment – Credit Card approval flow Start iReceivables user initiates 1 online payments request Payment processing is a two- Pass Payment step process. 2 Information to Oracle Payments Yes Credit Card details valid? No After authorization, “Automatic Servlet Remittances Master Program” Create a Oracle Payment Receipt in formats the Payment Oracle 3 Payment instruction and Response from Gateway Authorized? Yes Receivables with status = needs to be run in Oracle passes it to Payment Gateway = PayPAL Confirmed Receivables to settle all Gateway 7 Payment Processor communicates it to Return a Credit Card Issuer and No Message to authorized funds. 4 communicates with Payment processor = transmits response back to Gateway, to Oracle payments and User Moneris to iReceivables Payment Page 5 6 End
  14. 14. Dispute Processing Two types of approval hierarchies – primary and non primary Workflow (WF) routes approval requests. Two types of Approvals Workflows
  15. 15. 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.
  16. 16. 3. Security considerations for iReceivablesAll supported configurations for making iReceivablesaccessible via the internet to external users require use ofDemilitarized Zone (DMZ) protected with firewalls to ensurethat only authorized traffic is allowed to cross firewallboundaries.This arrangement ensures that even if intrusion attemptsagainst the DMZ are successful, it remains contained withinthe DMZ, leaving EBS inside the intranet unaffected.
  17. 17. 3. Security considerations ….cont’d
  18. 18. 4. Integration: Nuts and BoltsiReceivables seamlessly integrates with a number ofOracle EBS R12 modules after the requiredimplementation steps are followed.Oracle Payments’ integration with third party PaymentProcessors or Gateways is required to allowiReceivables customers to pay online.
  19. 19. Integration: Nuts and Bolts …cont’d
  20. 20. iReceivables - setupsARI_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 searchDispute pages can also be customized.iReceivables messages can also be edited using look up codes.
  21. 21. iReceivables – setupsThree setup tabs:Profiles: - to setup OIR profile valuesRules: - to setup rules that offer a high degree of flexibilitySystem parameters:- to setup Credit Card Receipt Method andBank Account Payment Method.
  22. 22. Receivables – setupsReceipt Class with creationmethod of Automatic anddefining at least one ReceiptMethod associated with thisReceipt Class.Approval limits for CreditMemo and defining a CreditMemo batch source
  23. 23. Oracle Payments – setupsSystem Security to setupencryption. Oracle Walletneeds to have been definedbeforehand.Payment Systems to setup3rd Party PaymentGateway/ProcessorsPayment Methods, Payeesand Credit Card Brands
  24. 24. Oracle Bills Presentment Architecture (BPA) – setups-Data Sources configuration-Template Management-Template AssignmentTemplate Assignment Rulesdefine criteria to automaticallypick desired template forviewing and printing.
  25. 25. Oracle Sysadmin – setups Internal and external users Function security for external users Indexing customers database Document Sequence System Profile values
  26. 26. Oracle Workflow (WF) – setupsTwo 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.
  27. 27. Oracle Workflow (WF) – setups Primary Approvers hierarchy Credit Memo Collector Receivable request is receives Role sent from and sends approves; iReceivables to approver CM created Non-Primary Approvers hierarchy• Primary path: based on Approval Limits defined in Oracle Receivables• Non-Primary path: based on the Oracle HR resources position hierarchy
  28. 28. 5. Integration with 3rd Party Payment SystemsPayment Systems requiring open network (internet) connectivity:• PayPal• Cybercash• Concord EFSNetPayment systems using non-open networks (e.g., a leased line):• First Data North• Paymentech
  29. 29. Integration with 3rd Party ….cont’dPayPal 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 docsInstallation: involves copying files, editing class paths and addingservlet entries to system config files, running autoconifg, runnng SQLscript and bouncing concurrent manager and webserver. OraclePayments setup is used to define PayPal payment system and Payee
  30. 30. 6. Conclusion 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
  31. 31. Conclusion…cont’d 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
  32. 32. 7. Other important informationOracle 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 linkshttps://support.oracle.com/CSP/ui/flash.htmlhttps://www.paypal.com/cgi-bin/webscr?cmd=_payflow-gateway-overview-outsidehttp://www.pcisecuritystandards.orghttp://www.pcicomplianceguide.org
  33. 33. Q&A