Die Präsentation wird geladen. Bitte warten

Die Präsentation wird geladen. Bitte warten

© 2008 Eventure Events. All rights reserved. External Payment Collector powered by Enterprise SOA Stefan Wolf SAP Labs.

Ähnliche Präsentationen

Präsentation zum Thema: "© 2008 Eventure Events. All rights reserved. External Payment Collector powered by Enterprise SOA Stefan Wolf SAP Labs."—  Präsentation transkript:

1 © 2008 Eventure Events. All rights reserved. External Payment Collector powered by Enterprise SOA Stefan Wolf SAP Labs

2 External Payment Collectors A customer likes to pay invoices at external payment Collectors, who may be: 1.Convenience stores 2.Post Offices 3.Bank Offices 4.Cash Point (ATM) 5.Gas Stations 6.…

3 External Scenario: –Cash desks are owned by 3rd parties who collect outstanding debts on behalf of other companies –3rd party = External Payment Collector –Cash flow between different companies –Enterprise services and functionality have been delivered with ERP6.0 EhP2 Internal Scenario: –Cash desks are owned by the company, who send out the bills and is in direct relationship with the payer (customer) –Cash flow inside the same company –Enterprise services and enhancements of the functionality will be delivered with ERP6.0 EhP4 Use cases

4 SAP FI-CA Payment Collector Process: Customer payment XI (3) Send open Item Information (2) Request Open Item(s) (1) Customer (4) Receive Open Item(s) (5) Customer select items to be paid (6) Post payment(s) (7) Process received payment(s) (7) Clear Open Item(s) (8) Retry if Clearing not possible Monitoring

5 Scenario 1: Online Processing –External payment collector is always in online mode –Communication in both direction is guaranteed The external payment collector retrieves open items for a customer on request Payments are send online to the ERP system. The ERP system clears the debits immediately or repeat clearing attempt until successful or assigned to a clarification account Reversal of payments can be reported The external payment collector reports a day-end-closing message, which will be used to post a debit on the external payment collector account read open items (request) FI-CA ERP read open items (response) Send payments Day-end-closing Available Services

6 Enterprise Services Available enterprise services: –Read open items for a customer (synchronous inbound XI interface) –Send open items to external cash desks (asynchronous outbound XI interface) –Post payments (asynchronous inbound XI interface) –Reverse payments (asynchronous inbound XI interface) –Day-end-closing – Reconciliation of external cash desk (asynchronous inbound XI interface)

7 Scenario 2: Based on stored Information –FI-CA sends open items periodically to external payment collector (e.g. once a day) for selected customers –Information are used to identify open items, when the customer wants to pay send open items FI-CA ERP

8 Scenario 3: Offline Processing –External payment collector is from time to time in offline mode –Customer is able to pay using Barcode information of his invoice –External payment collector sends bundled customer payments information when online again Send payments as a bundle FI-CA ERP

9 Details about open Items Which open item information will be communicated ? –Open amount –Open tax amount –Due Date –Description –Business partner, contract account, contract –Invoice number, payment form ID –Additional fields are available using XI enhancement concept FI-CA Send open items ERP

10 Details about communicated Payments (1) Payments: –Cash Desk collects and sends payment information to FI-CA. Payments are either a single (online scenario) or a bundle of payments (offline scenario) –FI-CA posts the payment and clears the invoice immediately FI-CA Post payment ERP

11 Details about communicated Payments (2) What payment information will be sent? –Office and cash desk ID –Unique payment transaction ID –Grouping key (groups together payments for one day) –Payment amount –Payment explanation (clearing information for open items) –Payment method information (cash, check, payment cards) –Additional fields are available using XI enhancement concept FI-CA Post payment ERP

12 Details about communicated Payments (3) Features: –Single and mass transfer of payments –Reverse functionality –Monitoring functionality (technical and business view) Error processing in the ERP: –All payment information is stored in FI-CA –If the payment can not be posted (e.g. database lock), the payment will be scheduled for retry processing –Retry backend job tries periodically to post payments –If retry fails, posting on clarification account takes place and clarification entry is created –New monitoring tool exists for monitoring payments, error processing and reporting

13 Monitoring in ERP - Payments Payment Collectors external cash Desk Payment Status Monitor payments Selection Period External Payment information Clearing Document No. in FICA Payment amount 7

14 Monitoring in ERP - Overview Payment Collectors external cash Desk Grouping Key Status Selection Period Grouping Key Overview Total amount 6

15 Payment Collector SAP FI-CA Process: Day-End-Closing XI (1) Send Day-End- Closing Information (3) Post Debit on Payment Collector Account (1) Process Day-End- Closing Monitoring

16 Reconciliation All payments processed during one working day at one cash desk are grouped together and identified by a grouping key The grouping key can be used by the cashier as an identifier when the bank transfer for the received payments is initiated The total sum of these payments will be transmitted to FI-CA for reconciliation purposes with the day-end-closing message After receiving the day-end-closing message it is possible to perform: –A FI-CA debit posting on the account of the external payment collector (Each external payment collector is represented as a business partner and contract account in FI-CA) –The debit of the external payment collector can be collected with the standard FI-CA functionality and the bank payment will be automatically matched with the debit Day-End-Closing FI-CA ERP Contract Account Payment Collector ,98

17 Yesterday - Solution without ESOA 1.Cash desks collect money from customers 2.Once a day a file will be transferred from cash desk to FI-CA 3.Various file formats => customer report will read file and create a payment lot in FI-CA 4.Batch job will post payment lots 5.Clarification of erroneous data 6.Manual reconciliation of cash flow from external agents => High integration costs (implementation and ongoing) No direct (immediate) clearing Payments FI-CA BAPI Payment Lot Post

18 Benefits of SOA approach –High level of automation –Easy to-use standardized interface for payment transfer and open item request by using Enterprise Service –Lower operating cost due to integrated monitoring/reporting tool –Lower integration cost due to standard interface –Out-of-the-box solution by partnering Business benefits –Improved Cash Flow, lower DSO –Following local market behavior –Increased Customer satisfaction –Wall to wall solution regarding customer and agent payments Today and tomorrow – Solution with ESOA

19 Menu External Cash desk in the FI-CA System External cash Desks Services

20 Customizing External Cash desk Customizing

21 Internal Scenario –Post deposits (asynchronous inbound XI interface) –Post withdrawals (asynchronous inbound XI interface) –Post corrections based on differences (asynchronous inbound XI interface) –Post GL-postings (asynchronous inbound XI interface) –Request cash balance (synchronous outbound XI interface) –Reverse above mentioned postings (asynchronous inbound XI interface) Enhancement of backend monitoring functionality Enhancement of external scenario –Commission calculation based on received payments –SAP ICM functionality is used to calculate the commissions Cash Desks Enhancements in EhP4

22 SAP ICMSAP FI-CA External cash desk External payment collector Calculation of Commissions in the external scenario XI (1) Day-end-closing message (2) Processing of day- end-closing message (3) Post Agent postings Monitoring 1 (4) Calculate commissions (3) Post commissions for agent 2 3 ICM calculation rules (4) Bill commissions periodically Commission calculation only in the external scenario

23 –If a company receives payments collected by an external payment collector it may be agreed to pay commission based on the payments received –The calculation of the commission is initiated using the agent posting functionality in the FICA backend system –As a result of the calculation a credit will be posted on the contract account of the external agent –The calculation rules are defined and executed in the SAP ICM management system Please note that the commissions calculation is only provided in the external scenario (external payment collectors) External Scenario : Calculation of Commissions

24 ServicesExternal Scenario Internal Scenario Available in ECC 6.0 with Read open items EhP2 Customer payments (send, post, reverse payments) EhP2 Day-end-closing Not availableEhP2 Post depositsNot available EhP4 Post withdrawalsNot available EhP4 Post differencesNot available EhP4 Post GL-postings EhP4 Request cash BalanceNot available EhP4 Reverse PostingsNot available EhP4 Services and Processes

25 Thank you very much for your attention! Stefan Wolf Head of Field Service North America SAP Labs, LLC 3410 Hillview Avenue Palo Alto, CA T

26 Copyright 2006 SAP AG. All Rights Reserved No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C ®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence. The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.

27 Copyright 2006 SAP AG. Alle Rechte vorbehalten Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden. Die von SAP AG oder deren Vertriebsfirmen angebotenen Softwareprodukte können Softwarekomponenten auch anderer Softwarehersteller enthalten. Microsoft ®, WINDOWS ®, NT ®, EXCEL ®, Word ®, PowerPoint ® und SQL Server ® sind eingetragene Marken der Microsoft Corporation. IBM ®, DB2 ®, DB2 Universal Database, OS/2 ®, Parallel Sysplex ®, MVS/ESA, AIX ®, S/390 ®, AS/400 ®, OS/390 ®, OS/400 ®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere ®, Netfinity ®, Tivoli ®, Informix und Informix ® Dynamic ServerTM sind Marken der IBM Corporation. ORACLE ® ist eine eingetragene Marke der ORACLE Corporation. UNIX ®, X/Open ®, OSF/1 ® und Motif ® sind eingetragene Marken der Open Group. Citrix ®, das Citrix-Logo, ICA ®, Program Neighborhood ®, MetaFrame ®, WinFrame ®, VideoFrame ®, MultiWin ® und andere hier erwähnte Namen von Citrix-Produkten sind Marken von Citrix Systems, Inc. HTML, DHTML, XML, XHTML sind Marken oder eingetragene Marken des W3C ®, World Wide Web Consortium, Massachusetts Institute of Technology. JAVA ® ist eine eingetragene Marke der Sun Microsystems, Inc. JAVASCRIPT ® ist eine eingetragene Marke der Sun Microsystems, Inc., verwendet unter der Lizenz der von Netscape entwickelten und implementierten Technologie. MaxDB ist eine Marke von MySQL AB, Schweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, und weitere im Text erwähnte SAP-Produkte und -Dienstleistungen sowie die entsprechenden Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und anderen Ländern weltweit. Alle anderen Namen von Produkten und Dienstleistungen sind Marken der jeweiligen Firmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Produkte können länderspezifische Unterschiede aufweisen. Die in dieser Publikation enthaltene Information ist Eigentum der SAP. Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, nur mit ausdrücklicher schriftlicher Genehmigung durch SAP AG gestattet. Bei dieser Publikation handelt es sich um eine vorläufige Version, die nicht Ihrem gültigen Lizenzvertrag oder anderen Vereinbarungen mit SAP unterliegt. Diese Publikation enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts. SAP entsteht aus dieser Publikation keine Verpflichtung zu einer bestimmten Geschäfts- oder Produktstrategie und/oder bestimmten Entwicklungen. Diese Publikation kann von SAP jederzeit ohne vorherige Ankündigung geändert werden. SAP übernimmt keine Haftung für Fehler oder Auslassungen in dieser Publikation. Des Weiteren übernimmt SAP keine Garantie für die Exaktheit oder Vollständigkeit der Informationen, Texte, Grafiken, Links und sonstigen in dieser Publikation enthaltenen Elementen. Diese Publikation wird ohne jegliche Gewähr, weder ausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zweck sowie für die Gewährleistung der Nichtverletzung geltenden Rechts. SAP haftet nicht für entstandene Schäden. Dies gilt u. a. und uneingeschränkt für konkrete, besondere und mittelbare Schäden oder Folgeschäden, die aus der Nutzung dieser Materialien entstehen können. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit. Die gesetzliche Haftung bei Personenschäden oder Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinks zugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über Internetseiten Dritter ab.

Herunterladen ppt "© 2008 Eventure Events. All rights reserved. External Payment Collector powered by Enterprise SOA Stefan Wolf SAP Labs."

Ähnliche Präsentationen