7/27/2019 Delta Information - SAP Bank Communication Management (EhP4) http://slidepdf.com/reader/full/delta-information-sap-bank-communication-management-ehp4 1/48 Ramp Up Knowledge Transfer – SAP Bank Communication Management in Enhancement Package 4 for SAP ERP 6.0 Delta Presentation Christian Mnich Solution Manager Suite Solution Management SAP AG October, 2008
48
Embed
Delta Information - SAP Bank Communication Management (EhP4)
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
7/27/2019 Delta Information - SAP Bank Communication Management (EhP4)
Standardization and automation of corporate to bankcommunication
Optimization of processes and increased payment flow
transparency through status monitoring
Enhanced straight-through-processing (STP) rates with end-
to-end SWIFTNet integration
Reduced maintenance costs by using global payment
standards
Includes ES bundle for the creation and status tracking of
payment orders as well as bank statements
Readiness for SEPA and ISO20022
Improved integration with cash management Automated triggering of follow-up activities via BAdI Indication of urgent payments in the payment monitor New services for payment advice Enhanced SEPA support Enhanced reporting capabilities Capability to assign additional approval users for dual control (Security)
Payment data is highly sensitive and requiressophisticated security processes to meet ever-increasing
regulatory mandates
Security gaps during payment file transfer (authorization,
signature, and encryption are often not part of the
solution)
High levels of manual processing, productivity losses,
excessive exception handling, and an overall lack of
transparency into payment flows
Missing straight-through processing
Delivered by Business Function FIN_FSCM_BNK
** Improvements
*Customer business challenges Business value
* Improvements
Initiate
payments
Batch
payments
Send
payment
media
Update
status
monitor
Approve
paymentsInvoice * * *
7/27/2019 Delta Information - SAP Bank Communication Management (EhP4)
indicating of urgent payments in Batch and Payment Monitor (TA BNK_Moni)and in Approval Monitor (BNK_APP)
changing of instruction key (and thus indirectly: urgent and cost assignment) inBatch and Payment Monitor (TA BNK_Moni) and in Approval Monitor (BNK_APP)
Item Level:
Header Level:
7/27/2019 Delta Information - SAP Bank Communication Management (EhP4)
Batch amounts and maximum payment amounts were converted on the fly and compared toentries defined in the rules amounts in release process can differ depending on exchange
rates application of different rules in release process is possible
Exchange rate type ‘M’ hard-coded no opportunity to enter another exchange rate type in
customizing
Amounts in rule currency not visible in batch monitor explanation of usage of 4-eye rather
than 6-eye approval is missingNow:
Definition of exchange rate type in Basic Settings
Batch amounts and maximum payment amounts converted when batch will be created only
once value fixed on database
7/27/2019 Delta Information - SAP Bank Communication Management (EhP4)
FileAct allows secure and reliable transfer of files and is typically used to exchange batches of structured financial messages and large reports. FileAct supports tailored solutions for marketinfrastructure communities, closed user groups and financial institutions. FileAct is particularlysuitable for bulk payments, securities value-added information and reporting, and for other purposes, such as central-bank reporting and intra-institution reporting.
FileAct is available in two different quality of service levels, one is Store-and-Forward mode theother Real-time mode.
SWIFTNet FileAct’s store-and-forward capability ensures that your correspondents whether receive your message or they are online at the time of transmission. Messages are deliveredwhen the recipient is ready to receive it. Store-and-Forward is an ideal way to send individualinstructions, confirmations and reports to large numbers of correspondents, some of which maybe in different time zones.
Real-time messaging provides a lower-cost alternative to store-and-forward for files that aredestined for correspondents that are online at the time of transmission. This makes it ideal for sending files to a few large correspondents or market infrastructures.
New Functionality: SWIFTNet FileAct Real-time mode will be supported according to theSCORE standard.
7/27/2019 Delta Information - SAP Bank Communication Management (EhP4)
End-to-end security is enhanced by means of a checksum or digital signature of critical messageelements like e.g. amount, currency or bank details. Therefore you will be able to ensure the
integrity of generated payment media from the ERP backend system via the SAP Integration
Package for SWIFT on SAP NeWeaver Process Integration until the SWIFT infrastructure
(SWIFTAlliance Access and SWIFTAlliance Gateway).
Certificates are exchanged between the ERP backend system and SAP NeWeaver Process
Integration and a parameter can be set accordingly (VerifyBackendSignature).
Prerequisite:
Component Number Short text Status
FIN-FSCM-BNK 1144603 BCM: Backend-Signature for Payment Medium Released for Customer
FIN-FSCM-BNK 1153053 BCM: Backend-Signature for Payment Medium In Process
S f
7/27/2019 Delta Information - SAP Bank Communication Management (EhP4)
Configuration of PI via Visual Administrator (JAVA)
Via the Visual Administrator and the Key Storage Service of the J2EE-Engine of SAPNetWeaver Process Integration a new View „BCM_SWIFT“ needs to be created and
the exported certificate has to be added as described in SAPNote 1144603.
3
B k d Si t f P t M di
7/27/2019 Delta Information - SAP Bank Communication Management (EhP4)
SWIFTNet 6.1 supports an enhanced header structure which Corporates might use to profit froma transaction-based pricing model. The Transaction Count <TtlNbOfTxs> and Request Type
Overwrite <Request Type> will be supported according to the SWIFTNet FileAct Implementation
Guide (SW4CORP_FAIMPGUIDE_May2008_V9.pdf ).
Prerequisite:
Component Number Short text Status
FIN-FSCM-BNK 1084448 BNK: Support of FileAct Request Type Released for Customer
FIN-FSCM-BNK tbd BCM: Support of FileAct TtlNbOfTxs In Process
C t S ifi St t M P i
7/27/2019 Delta Information - SAP Bank Communication Management (EhP4)
Within Corporate-to-Bank communication Banks will be able to provide specific status messageswhich need to be mapped to the „Batch and Payment Monitor (BNK_MONI)“ of SAP Bank
Communication Management.
There is an example implementation of a bank-specific status message mapping to highlight the
usage of the Enterprise Service „CollectivePaymentOrderNotification (CPON)“. It enables the
Content Conversion functionality of SAP NetWeaver Process Integration to extract the relevant
information out of the flat-file and map to the SAP standard interface.
Prerequisite:
Component Number Short text Status
FIN-FSCM-BNK tbd SIPS: Customer-specific Status Message Processing In Process
C t t
7/27/2019 Delta Information - SAP Bank Communication Management (EhP4)
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 bechanged without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge and other SAP products and services mentioned herein as well astheir 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 mentionedand associated logos displayed are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specificationsmay vary.
The information in this document is proprietary to SAP. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. Thisdocument contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be b inding upon SAP to any particular course of business,product strategy, and/or development. 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 theimplied 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. Thislimitation 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 inthese materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages
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 Genehmigungdurch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.
Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte undServices sowie die dazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Alle anderen in diesemDokument erwähnten Namen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sindunverbindlich und dienen lediglich zu Informationszwecken. Produkte können länderspezifische Unterschiede aufweisen.
Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmtenGeschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nichtdie Richtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. 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 einenbestimmten Zweck sowie für die Gewährleistung der Nichtverletzung geltenden Rechts.
SAP übernimmt keine Haftung für Schäden jeglicher Art, einschließlich und ohne Einschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendung dieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.
Die gesetzliche Haftung bei Personenschäden oder die Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenenHotlinks 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.