Bank Communication Management

Prévia do material em texto

FSC130
SAP Bank Communication
Management
SAP ERP - Financials
Date
Training Center
Instructors
Education Website
Participant Handbook
Course Version: 98
Course Duration: 2 Day(s)
Material Number: 50122135
An SAP course - use it to learn, reference it for work
Copyright
Copyright © 2014 SAP AG or an SAP affiliate company. 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.
Trademarks
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of
Adobe Systems Incorporated in the United States and other countries.
Apple, App Store, FaceTime, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C,
Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc.
Bluetooth is a registered trademark of Bluetooth SIG Inc.
Citrix, ICA, Program Neighborhood, MetaFrame now XenApp, WinFrame, VideoFrame, and
MultiWin are trademarks or registered trademarks of Citrix Systems Inc.
Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.
Edgar Online is a registered trademark of EDGAR Online Inc., an R.R. Donnelley & Sons Company.
Facebook, the Facebook and F logo, FB, Face, Poke, Wall, and 32665 are trademarks of Facebook.
Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google
Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater,
Google Voice, Google Mail, Gmail, YouTube, Dalvik, and Android are trademarks or registered
trademarks of Google Inc.
HP is a registered trademark of the Hewlett-Packard Development Company L.P.
HTML, XML, XHTML, and W3C are trademarks, registered trademarks, or claimed as generic
terms by the Massachusetts Institute of Technology (MIT), European Research Consortium for
Informatics and Mathematics (ERCIM), or Keio University.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System
z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power
Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter,
System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks,
OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks
or registered trademarks of IBM Corporation.
Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registered
trademarks of Microsoft Corporation.
INTERMEC is a registered trademark of Intermec Technologies Corporation.
IOS is a registered trademark of Cisco Systems Inc.
The Klout name and logos are trademarks of Klout Inc.
Linux is the registered trademark of Linus Torvalds in the United States and other countries.
Motorola is a registered trademark of Motorola Trademark Holdings LLC.
Mozilla and Firefox and their logos are registered trademarks of the Mozilla Foundation.
Novell and SUSE Linux Enterprise Server are registered trademarks of Novell Inc.
g201432323046
OpenText is a registered trademark of OpenText Corporation.
Oracle and Java are registered trademarks of Oracle and its affiliates.
QR Code is a registered trademark of Denso Wave Incorporated.
RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch,
BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry AppWorld are
trademarks or registered trademarks of Research in Motion Limited.
SAVO is a registered trademark of The Savo Group Ltd.
The Skype name is a trademark of Skype or related entities.
Twitter and Tweet are trademarks or registered trademarks of Twitter.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Wi-Fi is a registered trademark of Wi-Fi Alliance.
SAP, R/3, ABAP, BAPI, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects
Explorer, StreamWork, SAP HANA, the Business Objects logo, BusinessObjects, Crystal Reports,
Crystal Decisions, Web Intelligence, Xcelsius, Sybase, Adaptive Server, Adaptive Server Enterprise,
iAnywhere, Sybase 365, SQL Anywhere, Crossgate, B2B 360° and B2B 360° Services, m@gic
EDDY, Ariba, the Ariba logo, Quadrem, b-process, Ariba Discovery, SuccessFactors, Execution
is the Difference, BizX Mobile Touchbase, It's time to love work again, SuccessFactors Jam and
BadAss SaaS, and other SAP products and services mentioned herein as well as their respective
logos are trademarks or registered trademarks of SAP AG in Germany or an SAP affiliate company.
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.
Disclaimer
These materials are subject to change without notice. These materials are provided by SAP AG and
its affiliated companies (“SAP Group”) for informational purposes only, without representation or
warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the
materials. The only warranties for SAP Group products and services are those that are set forth in
the express warranty statements accompanying such products and services, if any. Nothing herein
should be construed as constituting an additional warranty.
g201432323046
g201432323046
About This Handbook
This handbook is intended to complement the instructor-led presentation of this
course, and serve as a source of reference. It is not suitable for self-study.
Typographic Conventions
American English is the standard used in this handbook. The following
typographic conventions are also used.
Type Style Description
Example text Words or characters that appear on the screen. These
include field names, screen titles, pushbuttons as well
as menu names, paths, and options.
Also used for cross-references to other documentation
both internal and external.
Example text Emphasized words or phrases in body text, titles of
graphics, and tables
EXAMPLE TEXT Names of elements in the system. These include
report names, program names, transaction codes, table
names, and individual key words of a programming
language, when surrounded by body text, for example
SELECT and INCLUDE.
Example text Screen output. This includes file and directory names
and their paths, messages, names of variables and
parameters, and passages of the source text of a
program.
Example text Exact user entry. These are words and characters that
you enter in the system exactly as they appear in the
documentation.
<Example text> Variable user entry. Pointed brackets indicate that you
replace these words and characters with appropriate
entries.
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. v
About This Handbook FSC130
Icons in Body Text
The following icons are used in this handbook.
Icon Meaning
For more information, tips, or background
Note or further explanation of previous point
Exception or caution
Procedures
Indicates that the item is displayed in the instructor's
presentation.
vi
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
Contents
Course Overview .......................................................... ix
Course Goals .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Course Objectives ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Unit 1: SAP Bank Communication Management –
Fundamentals............................................................... 1
SAP Bank Communication Management – Overview... . . . . . . . . . . .2
Basics – Payment Program and Payment Medium Workbench 11
SEPA Formats.. . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Unit 2: Business Process: Batching in BCM ...................... 37
Application View: Batching in BCM.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Customizing Batching Rules in BCM.... . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Unit 3: Business Process: Approval Process in BCM .......... 79
Application View: Approval Process in BCM .... . . . . . . . . . . . . . . . . . . 80
Customizing: Approval Process in BCM.... . . . . . . . . . . . . . . . . . . . . . . 110
Unit 4: Business Process: Status Tracking ...................... 127
Application View: Status Tracking and Bank Statement
Monitor.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128
Customizing: Status Tracking and Bank Statement Monitor ..134
Unit 5: SAP Integration Package for SWIFT ...................... 151
Overview SWIFT ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152
Overview SAP Netweaver Process Integration ... . . . . . . . . . . . . . . .162
Overview SAP Integration Package for SWIFT ... . . . . . . . . . . . . . . .168
Appendix 1: Data Sheet ............................................. 175
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. vii
Contents FSC130
viii
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
Course Overview
Target Audience
This course is intended for the following audiences:
• Members of the project team
• End users
• Consultants
Course Prerequisites
Required Knowledge
• Practical knowledge of payment processes
• AC010: Business Processes in Financial Accounting
• AC201: Payment and Dunning Program
Recommended Knowledge
• AC200: Financial Accounting Customizing I
• AC805: Cash Management
Course Goals
This course will prepare you to:
• Gain detailed knowledge of the processes of SAP Bank Communication
Management
• Understand the basics of SAP Integration Package for SWIFT
• Get familiar with the configuration of SAP Bank Communication
Management
Course Objectives
After completing this course, you will be able to:
• Describe in detail the processes of SAP Bank Communication Management
• Learn the configuration steps of BCM
• Define the system settings needed to implement BCM
• Describe how BCM connects to SWIFT through the SAP Integration
Package for SWIFT
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. ix
Course Overview FSC130
x
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
Unit 1
SAP Bank Communication
Management – Fundamentals
Unit Overview
This unit gives an overview of the main features of BCM and of the functions
provided by the payment program and the Payment Medium Workbench (PMW).
Additionally, a brief introduction of the SEPA formats will be presented.
Unit Objectives
After completing this unit, you will be able to:
• Explain the concept of SAP Bank Communication Management
• List the main benefits and features
• Understand how bank communication is enhanced with SAP Bank
Communication Management
• List and explain the major processing steps of the payment program
• Maintain the parameters for the payment run
• State the advantages of using the Payment Medium Workbench to create
payment media
• List the new SEPA formats
• Describe the main customizing steps
Unit Contents
Lesson: SAP Bank Communication Management – Overview ... . . . . . . . . . . .2
Lesson: Basics – Payment Program and Payment Medium Workbench. 11
Lesson: SEPA Formats .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Exercise 1: Master Records for Vendors, Posting Invoices, Payment
Run ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 1
Unit 1: SAP Bank Communication Management – Fundamentals FSC130
Lesson: SAP Bank Communication Management –
Overview
Lesson Overview
This lesson gives an overview of the features and processes of BCM.
Lesson Objectives
After completing this lesson, you will be able to:
• Explain the concept of SAP Bank Communication Management
• List the main benefits and features
• Understand how bank communication is enhanced with SAP Bank
Communication Management
Business Example
In your company, the payment transactions are performed through several
interfaces involving manual work and extensive paperwork. The CFO wants to
find an efficient way to send payment orders to the bank and receive account
statements where the manual work is reduced to a minimum, the security is
increased, and the process standardized.
Figure 1: Bank Communication Today
2
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: SAP Bank Communication Management – Overview
Today's payments landscape of a corporate client looks like the figure above: a
variety of interfaces to connect with several banks using several technologies. It
is also common that for every bank a proprietary interface has to be used. The
amount of effort needed to maintain each and every interface results in high costs
and an extensive manual work.
It is estimated that the yearly cost of having a banking interface is from 20.000 to
50.000 EUR. This estimation includes not only the cost of the interface itself, but
also the costs of maintenance, training, testing, and updates.
Figure 2: Bank Communication Today – Problems and Risks
It is not unusual that within a company attempts of manipulation of the payment
media have been detected. The process of sending such files to the bank involves
several people and intense manual work. Besides, unencrypted files are sometimes
found in directories that can be easily accessed by anyone.
Having several bank connection interfaces means that the staff either has to
know all of them or to specialize in one or some of them. Since the processes
tend to be different for every interface, these become inefficient. Aditionally,
today's communication does not allow a real-time status tracking of the files,
therefore any erroneous information is detected too late, resulting in extra fees and
post-processing costs.
Today's signature process requires that the bank check the signatures before
executing any payment order; this also adds extra manual steps inside the banks
that delay payments. Besides, for every single bank the company has to assign a
group of staff members that are authorized to send the payment media.
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 3
Unit 1: SAP Bank Communication Management – Fundamentals FSC130
Figure 3: Bank Communication Today with SAP ERP
Using SAP ERP, the payment media are generated with the help of the payment
program (transaction F110 or F111). The file will then be downloaded to a
file server, then the file is uploaded to a 3rd party system which takes over the
management of the transmission of files to and from the bank. Once within this
system, the file goes through a process of authorization which requires staff
members to log on and verify that an acompanying sheet corresponds with the
totals of the file. Should the verification be ok, then they proceed to sign. Once a
certain amount of approvers has signed (normally two), then the system sends the
file to the bank. The bank will then receive the file and the acompanying sheet
and will internally verify that the signatures match the ones they have on file as
approvers for that company before proceeding to execute the payment.
The bank will also send files to companies, namely account statements, which are
received and decrypted by the 3rd party system. It will also act as a collector of
statements and in several cases it will also transform the MT940 (SwiftMessage
Type 940) into statement.txt and lineitem.txt files. Afterwards, a staff member will
pick up the account staments and upload them in the respective systems.
4
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: SAP Bank Communication Management – Overview
Figure 4: Enhanced Bank Communication with SAP: Tomorrow‘s Landscape
Instead of a variety of interfaces for every bank, SAP Bank Communication
Management provides direct access to banks through the SWIFT Network. SAP
NetWeaver Process Integration plays an important role, since it enables the
connection between the SAP system and the SWIFT network.
SAP Bank Communication Management supports the communication of financial
transactions of a company to its banks via the Society for Worldwide Interbank
Financial Telecommunication (SWIFT) network.
It includes services for the creation and status tracking of payment orders, as well
as services for receiving bank statements.
SWIFT operates a worldwide financial messaging network. Messages are securely
and reliably exchanged between banks and other financial institutions.
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 5
Unit 1: SAP Bank Communication Management – Fundamentals FSC130
Figure 5: Bank Communication with SAP Bank Communication Management
Figure 6: SAP Bank Communication Management - Processes
6
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: SAP Bank Communication Management – Overview
The basic processes of SAP Bank Communication Management include:
• Batching of payments: As input the batching process receives payment runs.
The output are the batches.
• Approval of batches: As input the approval process receives batches. The
output are the payment media.
• Status tracking: Receives information from several sources; the batching
process, the approval process and the SAP Integration Package for SWIFT
• Bank Statement Monitor: Receives information from the SAP Integration
Package for SWIFT and the SAP ERP system
Figure 7: SAP Bank Communication Management – Key Features and
Benefits
The batching of payments feature offers the possibility to group payments
according to logical rules. These logical rules can be customized and are a very
flexible tool to batch similar payments. Examples include: grouping payments
that go to the same vendor or payments within a certain range (for example,
10.000 – 20.000 EUR).
The approval process allows the assignment of authorizations to certain staff
members that can approve payments. The payment media is generated only
after the last approver has signed. This means that the possibilities to manipule
payment files are drastically reduced. Personal digital signatures also facilitate
internal audit processes.
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 7
Unit 1: SAP Bank Communication Management – Fundamentals FSC130
Status tracking allows the status of the payment orders to be monitored, from
the moment when they are waiting for approval to the moment where the bank
executes them (provided the bank sends such kinds of status messages). Errors
also become visible and an automatic generation of alert workflow items can be
customized.
Since only one interface is needed to connect to the banks, the payment processes
are simplified to one process. If BCM is used together with SWIFT, it offers also
support of the Universal Financial Industry (UNIFI) standards defined by the
International Organization for Standardization (ISO). The SEPA standards are a
subset of UNIFI.
8
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: SAP Bank Communication Management – Overview
Figure 8: SAP Bank Communication Management – Business Example
1. Payment order initiated in SAP ERP and sent to SAP NetWeaver Process
Integration (PI).
2. Payment order is sent from SAP PI, using the SAP Integration Package for
SWIFT, to Swiftnet via SwiftAlliance Gateway.
3.
a) SWIFT sends confirmation (acknowledgement) to SAP PI which
forwards it to SAP ERP.
b) SAP ERP receives acknowledgment and updates payment status in
SAP BCM.
4.
a) Swift sends confirmation (delivery notification) to SAP PI which
forwards it to SAP ERP.
b) SAP ERP receives delivery notification and updates payment status
in SAP BCM.
5. Payment order is transferred via SwiftAlliance Gateway to the bank.
6. Payment order is transferred to Payment Engine to be processed (no
mapping).
7. After validation of the payment order the Payment Engine sends a status
message back for validation.
8. Status message is sent from Bank to SWIFT.
9. Status message is forwarded to SAP ERP.
10. SAP ERP receives status message and updates payment status in BCM.
11. The bank creates a bank statement (MT940).
12. Bank statement is sent via SwiftAlliance Gateway.
13. Swift sends statement to SAP PI.
14. ERP receives bank statement and updates the bank statement monitor.
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 9
Unit 1: SAP Bank Communication Management – Fundamentals FSC130
Lesson Summary
You should now be able to:
• Explain the concept of SAP Bank Communication Management
• List the main benefits and features
• Understand how bank communication is enhanced with SAP Bank
Communication Management
10
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Basics – Payment Program and Payment Medium Workbench
Lesson: Basics – Payment Program and Payment
Medium Workbench
Lesson Overview
This lesson gives an overview of the functions of the payment program together
with the Payment Medium Workbench. An extra section will present the new
SEPA formats.
Lesson Objectives
After completing this lesson, you will be able to:
• List and explain the major processing steps of the payment program
• Maintain the parameters for the payment run
• State the advantages of using the Payment Medium Workbench to create
payment media
Business Example
The accounting department needs to know how to execute a payment order using
the payment program and the Payment Medium Workbench. In addition, the
department wants to know how to create a SEPA credit transfer format using
these two tools.
Figure 9: Running the Payment Program – Parameters
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 11
Unit 1: SAP Bank Communication Management – Fundamentals FSC130
After the basic configuration is complete, the payment process can begin. In the
first step of the payment process, you have to define the following:
• What is to be paid?
• Which payment method will be used?
• When will the payment be made?
• Which company codes will be considered?
• How are they going to be paid?
Every payment program run is identified by two fields:
• RunDate
• Identification
Therun date filed is recommended as the actual date when the program is
executed. Its main purpose is to identify the program run.
The identification field is used to differentiate between program runs that have
the same run date.
Figure 10: Open Item Selection
All documents that were entered up to the Docs entered up to date are included in
the payment run.
The posting date is the date when the general ledger is updated with the postings.
This date is defaulted from the run date on the previous screen.
If multiple company codes are listed, they have to be separated by commas. If
you want to specify a range of company codes, you have to enter the first and last
company code in the range in parentheses.
12
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Basics – Payment Program and Payment Medium Workbench
The company codes in a payment run must be in the same country. For each
country, we defined payment methods that can be used within that particular
country. From these payment methods, choose the ones to be used in the current
payment run.
If you use more than one payment method in the paymentrun, remember that the
order in which you enter them is important. The method entered first has first
priority, the next has second priority, and so on. The system makes the payment
using the highest priority possible after the check.
Figure 11: Proposal Run
After the parameters are entered on the main payment program screen, schedule
the payment proposal to be created.
In the proposal run, the program selects documents and accounts with items that
are pending payment. To do so, it uses the search criteria that you specified when
you entered the parameters. The system then groups these items to payments and
assigns the payment methods and bank details to be used. If the system cannot
find a valid payment method or bank data, or if an item is blocked for payment, it
adds these items to the exception list.
Once the proposal run is completed, the system generates two reports: the
payment proposal list and the exception list. You can edit these reports online
or print them.
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 13
Unit 1: SAP Bank Communication Management – Fundamentals FSC130
Figure 12: Proposal List
The proposal list shows the business partners and the amounts to be paid or
received. Depending on the line layout users choose for the screen, the associated
document numbers and cash discounts can be displayed.
Any exceptions are also listed here. Users can drill down several times to view
and change the details of the individual payment items.
Figure 13: Exception List
Invoices that match the specified payment parameters but, for some reason, cannot
be paid are listed in the exception list.
If users select the additional log, the list shows why the invoice cannot be paid.
14
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Basics – Payment Program and Payment Medium Workbench
Figure 14: Payment Run
Once the payment proposal has been edited and saved, the payment run uses the
changes as a basis for the actual payments.
Up to this point, no postings have occurred. The documents included in this
payment run have been locked against any other postings, that is, an invoice
eligible to be paid in the current payment run is blocked for manual payment or
payment or in a different payment run.
In this step, payment documents are created, open items are cleared, and the
general and subledgers are posted to.
The payment program automatically posts payments and related postings, such as
those for tax, tax adjustments, exchange rate differences, or cash discounts.
An additional step is the printing of the payment media, but since this task is done
by BCM, this step will be skipped here.
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 15
Unit 1: SAP Bank Communication Management – Fundamentals FSC130
Figure 15: Payment Program Integration with BCM
You have several run indicators to choose from, however only two are relevant
for BCM:
1. FI AP/AR payment program for customers and vendors
2. FI-BL payment program for payment requests
PMW Advantages
• Easier to maintain and to extend. Replaces approx. 60 Classic Payment
Medium Programs (RFFO*) with huge maintenance costs
• Clearer to work with than the myriad previous payment medium programs
• Superior control and verification of payment procedure
• Improved performance with mass payments (> 50,000)
• Better sort functions with payment advice notes
• Separation of generic functions from format-specific mapping
• Easy creation of new formats with Customizing and either simple mapping
functions or mapping with the DME Engine, which can be maintained
without a lot of programming know-how
• Payment method and origin-specific customizable notes to payee
– Flexible configuration for payment usage (note to payee) fields
– Example: Different information for HR and FI payments
The Payment Medium Workbench
Previously, payment media formats were programmed in approximately 60
standard payment media programs (RFFO*). In the PMW, however, these formats
are defined outside the payment media program.
Generic print program SAPFPAYM replaces the classical RFFOXX* print
programs.
16
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Basics – Payment Program and Payment Medium Workbench
Superior control: Improved monitoring of the payment process, better checks that
all payments have been sent to the bank and that no payment has been sent twice.
Better sort functions with payment advice notes: Creates payment advice notes
independent of organizational units (company code, house bank, ...)
Separation of generic functions from format-specific mapping enables:
• Faster implementation of payment medium formats by subsidiaries without
the necessity to send time-consuming development requests to the core
development teams
• Faster delivery of changes of payment medium formats, for example, due
to legal changes
• Cheaper implementation of customer/bank-specific formats by consultants
or customers
• Cheaper adaptation or modification of standard formats according to the
customer’s needs
Figure 16: Steps in the PMW Process
When the payment media are created for a payment with a PMW payment
method, the program SAPFPAYM_SCHEDULE is launched.
This first carries out a pre-service. The pre-service processes the data supplied
by the payment run again specifically for the PMW:
• The payments are sorted according to PMW format and other format-specific
fields.
• Payment groups are created based on the level of granularity (one payment
medium file is usually created later for each group).
• The note to payee is formed.
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 17
Unit 1: SAP Bank Communication Management – Fundamentals FSC130
The payment program SAPFPAYM and advice note program
RFFOAVIS_FPAYM are launched based on the data generated by the payment
program.
• The program RFFOAVIS_FPAYM generates all the required advice notes
and the zero balance notices.
The program SAPFPAYM is started with all the variants that are defined for the
relevant payment groups in Customizing. This program generates the payment
media for the PMW payment methods, the accompanying sheets for the payment
media, an error log, and the payment summary.
The granularity is specified in the definition of the payment medium format
and determines how the payment media are to be output separately in payment
groups. A payment group usually corresponds to one payment file.
Example: If Company Code and House Bank are selected as the level of detail, a
payment group is created for each combination of company code and house bank.
At least one selection variant must be defined in the generic payment medium
program SAPFPAYM for each possible payment group. The payment medium
program is processed with all the defined variants.
The granularity can be refined, but not reduced, for the PMW formats shipped
with the system. This is because the granularity shipped by SAP is based on the
format requirements (usually specified by the banks).
18
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Basics – Payment Program and Payment Medium Workbench
Lesson Summary
You should now be able to:
• List and explain the major processing steps of the payment program
• Maintain the parameters for the payment run
• State the advantages of using the Payment Medium Workbench to create
payment media
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 19
Unit 1: SAP Bank Communication Management – Fundamentals FSC130
Lesson: SEPA Formats
Lesson Overview
This lesson gives an overview of the concept of SEPA, its formats, and the
configuration steps in the system.
Lesson Objectives
After completing this lesson, you will be able to:
• List the new SEPA formats
• Describe the main customizing steps
Business Example
You need to implement the new SEPA credit transfer format using the Payment
MediumWorkbench.
Figure 17: SEPA at a Glance – What Is It all About?
The introduction of SEPA brings with it a large number of changes to the way
everyday transactions are carried out. Specific requirements for businesses are as
follows:
- Fixed rules and standards for all credit transfers and direct debits denominated
in euro.
20
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: SEPA Formats
- International Bank Account Number. By February 2014, the IBAN will be the
sole payment account identifier for national and cross-border credit transfers and
direct debits in euro within the EU.
- Business Identifier Code. The Business Identifier Code (BIC) may still be
required until 1 February 2014 for domestic payments and 1 February 2016 for
cross-border payments.
- Pan-European reachability. Payment service providers cannot reject a SEPA
credit transfer or SEPA direct debit transaction if they currently accept equivalent
transactions carried out by national schemes.
- Free choice of payment locations. Payers cannot be restricted in choosing from
which account in Europe they would like to make credit transfers or direct debits
in euro. Neither can payees be forced to receive credit transfers or direct debits in
euro in an account held in a specific country.
- Additional debtor protection measures for direct debits. You can define
instructions on how to handle incoming collections by specific billers. You may
draw up black lists or white lists of billers, set maximum amounts, or specify
payment intervals. Additionally, you can block any direct debit collections from
your payment account.
- Principle of equal charges. Payment service providers must apply equal charges
to comparable cross-border and domestic payments in euro within the European
Union - ISO20022 XML message standard. The use of the message standard
is mandatory:
i) between payment service providers; and
ii) for the bundled transmission of credit transfers and direct debits in euro by
business users that are not microenterprises (microenterprises have less than ten
staff members and a turnover or a balance sheet total of up to €2 million).
- Multilateral interchange fees eliminated for direct debits in euro. Multilateral
interchange fees (MIFs are fees applied between payment service providers
in some Member States when passing on individual direct debits) are being
eliminated for direct debits in euro. Such fees will be eliminated by 1 February
2017 for national payments and were eliminated on 1 November 2012 for
cross-border payments.
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 21
Unit 1: SAP Bank Communication Management – Fundamentals FSC130
Figure 18: SEPA Payment Instruments and Formats
The new SEPA payment intruments, SEPA credit transfer, and SEPA direct debit,
are supported by SAP from release 4.7.
The tools used to create this format in the SAP system are the Payment Medium
Workbench (PMW) and the Data Medium Exchange Engine (DMEE). The former
controls specifications such as note to payee. The latter is the graphical definition
of the format.
The DMEE also allows the user to define additional optional fields, which will be
used in the future to take advantage of the Additional Optional Services (AOS)
offered by the banks.
22
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: SEPA Formats
Figure 19: Availability
• slide shows the necessary Support Packages for different Releases and
Enhancement Packages
Figure 20: SEPA CT Payment Method in the System
With the import of the support package a new PMW format will be available
for the SEPA credit transfer. Additionally, some basic Customizing of a note to
payee will be included
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 23
Unit 1: SAP Bank Communication Management – Fundamentals FSC130
A format can have several note to payees assigned depending on the origin (HR,
FI/AR, FI/AP). These notes to payee are created in this transaction
In payment method/country, the following aspects are defined:
• Method of payment: bank transfer
• Master record requirements: BIC & IBAN
• Document types for postings
• Print program: PMW
• Permited currencies: Only EURO
In payment method/company code define that payments abroad and foreign
business partners are allowed.
Create and assign selection variants for each level of detail (generally per company
code and house bank).
24
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: SEPA Formats
Exercise 1: Master Records for Vendors,
Posting Invoices, Payment Run
Exercise Objectives
After completing this exercise, you will be able to:
• Update the master records for vendors
• Post invoices from vendors
• Reserve identification for cross-payment run payment media
• Run the payment program
Business Example
The accounting department has received three invoices from three different
vendors. It has decided that they will be paid using a SEPA credit transfer.
User ID: FSACC-##
Task:
1. Check master records for vendors
Check if the payment method for SEPA credit transfer is assigned to your
vendors T-F00K00, T-F00L00 and T-F00M00 in your company code AC##.
Use your user FSACC-##. Replace ## with your group number.
2. Post incoming invoices from vendors
Post four invoices. Use the account 400020 as offsetting account and the
Sales Tax Code 0I (Input tax 0%). Note the four document numbers!
For your vendor T-F00K00 post an invoice in the amount of 200 € (Invoice
1) and an invoice in the amount of 4,000 € (Invoice 2). Make sure that the
payment method on the second invoice is 7 (MT101)
For your vendor T-F00L00 post an invoice in the amount of 8,000 € (Invoice
3).
For vendor T-F00M00 post an invoice in the amount of 10,000 € (Invoice 4).
3. Reserve identification for cross-payment run payment media
Reserve the identification BC##* (## = group-number) to create
cross-payment run payment media for your payment runs. Make sure
that payment runs with this identification are available in SAP Bank
Communication Management (BCM).
Continued on next page
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 25
Unit 1: SAP Bank Communication Management – Fundamentals FSC130
4. Initiate payment runs
Settle your open items you have created in exercise 1-2.
Create two payment runs. Create the first payment run to settle Invoice 1
and 4 and the second to settle Invoice 2 and 3. Define the corresponding
document numbers on the tab page Free Selections. Use the reservation IDs
BC##1 and BC##2 for your payment runs.
Use Payment Method 5 (SEPA Credit Transfer) for the first payment run and
Payment Methods 5 and 7 for the second payment run. Schedule the next
payment runs in one week.
Caution: Make sure to start the second payment run only after
having finished the first one.
26
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: SEPA Formats
Solution 1: Master Records for Vendors,
Posting Invoices, Payment Run
Task:
1. Check master records for vendors
Check if the payment method for SEPA credit transfer is assigned to your
vendors T-F00K00, T-F00L00 and T-F00M00 in your company code AC##.
Use your user FSACC-##. Replace ## with your group number.
a) Check master records for vendors
Log on with your user FSACC-##. Replace ## with your group number.
Accounting → Financial Accounting → Accounts Payable → Master
Records → Display
Enter the following data:
Field Name or Data Type Values
Vendor T-F00K00/T-F00L00/T-
F00M00
Company Code AC## (Replace ## with
your group number)
Company code data – Payment
transactions
Check
Enter.
Check the following data:
Field Name or Data Type Values
Payment methods 5 and 7
2. Post incoming invoices from vendors
Post four invoices. Use the account 400020 as offsetting account and the
Sales Tax Code 0I (Input tax 0%). Note the four document numbers!
For your vendor T-F00K00 post aninvoice in the amount of 200 € (Invoice
1) and an invoice in the amount of 4,000 € (Invoice 2). Make sure that the
payment method on the second invoice is 7 (MT101)
Continued on next page
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 27
Unit 1: SAP Bank Communication Management – Fundamentals FSC130
For your vendor T-F00L00 post an invoice in the amount of 8,000 € (Invoice
3).
For vendor T-F00M00 post an invoice in the amount of 10,000 € (Invoice 4).
a) Post invoices
Accounting → Financial Accounting → Accounts Payable →
Document Entry → Invoice
If it’s necessary to change the Company code, please press F7 and
switch to your Company Code (AC##).
Enter the following data:
First Invoice:
Field Name or Data Type Values
Vendor T-F00K00
Invoice date Today
Posting Date Today
Amount 200
Currency EUR
Calculate Tax Check
Tax Code 0I
G/L Account 400020
Amount in document currency *
Post.
Note the document number:__________________ (first invoice)
Second Invoice:
Field Name or Data Type Values
Vendor T-F00K00
Invoice date Today
Posting Date Today
Amount 4000
Currency EUR
Calculate Tax Check
Continued on next page
28
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: SEPA Formats
Field Name or Data Type Values
Tax Code 0I
G/L Account 400020
Amount in document currency *
Select tab Payment and enter the following information
Field Name or Data Type Values
Payment method 7
Post.
Note the document number:__________________ (second invoice)
Third Invoice:
Field Name or Data Type Values
Vendor T-F00L00
Invoice date Today
Posting Date Today
Amount 8000
Currency EUR
Calculate Tax Check
Tax Code 0I
G/L Account 400020
Amount in document currency *
Post.
Note the document number:__________________ (third Invoice)
Fourth Invoice:
Field Name or Data Type Values
Vendor T-F00M00
Invoice date Today
Posting Date Today
Amount 10000
Currency EUR
Continued on next page
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 29
Unit 1: SAP Bank Communication Management – Fundamentals FSC130
Field Name or Data Type Values
Calculate Tax Check
Tax Code 0I
G/L Account 400020
Amount in document currency *
Post.
Note the document number:__________________ (fourth Invoice)
3. Reserve identification for cross-payment run payment media
Reserve the identification BC##* (## = group-number) to create
cross-payment run payment media for your payment runs. Make sure
that payment runs with this identification are available in SAP Bank
Communication Management (BCM).
a) Reserve identification for cross-payment run payment media
Accounting → Financial Accounting → Accounts Payable → Periodic
Processing → Payments
Go to Environment → Payment Medium → Cross-Payment Run
Payment Medium → Reserve Identification
or:
In the IMG (Transaction: SPRO) select:
Financial Accounting → Accounts Receivable and Accounts Payable
→ Business Transactions → Outgoing Payments → Automatic
Outgoing Payments → Payment Media → Define Identification for
Cross-Payment Run Payment Media
Navigation:
Click FI-AP/AR Payment program for customers and vendors.
On the following screen click New Entries.
Enter the following data:
Field Name or Data Type Values
Identifier BC##*
BRM Check
Save.
4. Initiate payment runs
Continued on next page
30
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: SEPA Formats
Settle your open items you have created in exercise 1-2.
Create two payment runs. Create the first payment run to settle Invoice 1
and 4 and the second to settle Invoice 2 and 3. Define the corresponding
document numbers on the tab page Free Selections. Use the reservation IDs
BC##1 and BC##2 for your payment runs.
Use Payment Method 5 (SEPA Credit Transfer) for the first payment run and
Payment Methods 5 and 7 for the second payment run. Schedule the next
payment runs in one week.
Caution: Make sure to start the second payment run only after
having finished the first one.
a) Initiate payment runs
Remark: The following steps refer to both payment runs.
Accounting → Financial Accounting → Accounts Payable → Periodic
Processing → Payments
Enter the following data:
Field Name or Data Type Values
Run Date Today’s date
Identification First payment run:
BC##1
Second payment run:
BC##2
Continue (Enter).
The status of the new payment run is: no parameters entered as yet.
Choose the Parameter tab page and enter the following data:
Field Name or Data Type Values
Posting date Today’s date
Docs entered up to Today’s date
Company codes AC##
Payment methods 5 for the first payment run.
57 for the second payment run
Continued on next page
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 31
Unit 1: SAP Bank Communication Management – Fundamentals FSC130
Field Name or Data Type Values
Next posting date One week after posting
date
Vendor T-F00K00 to T-F00M00
Choose the Free selection tab page and enter the following data:
Field Name or Data Type Values
Field Name Document Number
Values First payment run:
“Document number first
invoice”, “Document
number fourth invoice”
Second payment run:
“Document number
second invoice”,
“Document number third
invoice”
To fill in Document Number click . Select Document Number. Press
Enter or double-click on Document Number.
Do not leave a space between the document numbers and the comma!
Choose the Additional Log tab page and enter the following data:
Field Name or Data Type Values
Due date check Check (first box)
Payment method selection in all
cases
Check (second box)
Line items of the payment
documents
Check (fourth box)
Vendor T-F00K00 to T-F00M00
Save.
Return to the Status tab page.
The status of the payment run is: Parameters have been entered.
Schedule a payment proposal
Continued on next page
32
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: SEPA Formats
Click on Schedule Proposal .
Check Start immediately.
Continue.
Update the status until it says Payment proposal has been created.
Check the results by clicking on Display Proposal and Display
Proposal Log .
Schedule a payment run
Click on Schedule payment run .
Check Start immediately.
Continue.
Update the status until this message appears:
Payment run has been carried out
Posting Orders: 2 generated, 2 completed.
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 33
Unit 1: SAP Bank Communication Management – Fundamentals FSC130
Lesson Summary
You should now be able to:
• List the new SEPA formats
• Describe the main customizing steps
34
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Unit Summary
Unit Summary
You should now be able to:
• Explain the concept of SAP Bank Communication Management
• List the main benefits and features
• Understand how bank communication is enhanced with SAP Bank
Communication Management
• List and explain the major processing steps of the payment program
• Maintain the parameters for the payment run
• State the advantages of using the Payment Medium Workbench to create
payment media
• List the new SEPA formats
• Describe the main customizing steps
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 35
Unit Summary FSC130
36
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
Unit 2
Business Process: Batching in BCM
Unit Overview
The concept of batching will be presented. In addition, the use of batching rules
will be explained.
Unit Objectives
After completing this unit, you will be able to:
• Explain the batching process in SAP Bank Communication Management
• Explain the concept of rules
• Understand the main Customizing settings in SAP Bank Communication
Management for batching payments
Unit Contents
Lesson: Application View: Batching in BCM .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Exercise 2: Batching of PaymentOrders.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Exercise 3: Free Form Payment (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Lesson: Customizing Batching Rules in BCM .... . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Exercise 4: Customizing Batching Rules in BCM .... . . . . . . . . . . . . . . . . . . . 73
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 37
Unit 2: Business Process: Batching in BCM FSC130
Lesson: Application View: Batching in BCM
Lesson Overview
This lesson gives an overview of the batching process in BCM.
Lesson Objectives
After completing this lesson, you will be able to:
• Explain the batching process in SAP Bank Communication Management
• Explain the concept of rules
Business Example
The accounting deparment needs to know how the batching process can help them
to group several payment orders into one or a few payment media.
Figure 21: Batching Process – Overview
Payment runs whose ID was reserved to work with BCM will be put together in a
collector, which is also identified by a collector ID.
38
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Application View: Batching in BCM
All the payment requests found in the collector will be grouped according to the
following criteria:
• The format: in the format customizing in payment medium workbench is
possible to split payment media according to parameters such as company
code and house bank. This is also known as the level of detail in PMW.
• The payment method: Different payment media will be generated for
different payment methods. For example, MT101 or SEPA credit transfer
• Batching rules: These are additional conditions that can be used to group
or split the payment media
From each batch, a payment media will be generated.
Figure 22: Payment Collector Creation and Batching of Payments
Creation of Cross-Payment Run Payment Media
Purpose
• Using the program SAPFPAYM_MERGE, you can group together payments
from several payment runs and transfer them together on payment media
• This kind of grouping is required in order to facilitate companies to instruct
their banks to process some payments in a similar way and to receive bank
statements in a similar way
Integration
• The required functions are supported in the payment programs for vendors
and customers (F110), for payment requests (F111) and also in all DME
preliminary programs for payroll and travel expenses.
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 39
Unit 2: Business Process: Batching in BCM FSC130
Example
• Three staff members have each created a payment run with identification
ALAM01, ALBH01, ALSH01 within the same week. In Customizing, it was
determined that all payment runs beginning with AL will be taken over by
BCM. In order to select the three payment runs, the selection parameter AL
should be entried under Identification.
Figure 23: Reason for Merging
Each payment run can contain payment orders to different banks.
As each bank has its own time schedule (for example, payment files delivered
until 10:00h will have the value date of the same day), it is important to collect
and transfer all payments to this bank until this fixed time.
The system now enables you to collect and merge payments by a range of selection
criteria, such as:
• Company
• House bank or house bank account
• Payment method and payment method supplement
• Currency
• Dates (value, posting, due date)
• Partner (vendor, customer)
• Payment run
• Payment document number
Due to privacy reasons HR payments can only be merged with other HR payments
40
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Application View: Batching in BCM
Figure 24: What can be Merged?
A company uses several applications to run the payment program: the application
from the FI/CO module for Accounts Payable and Receivable, the application
for payment requests (FI BL), and the application from HR payments using the
HCM module
All these payments can now be collected into a grouped collector, using the
cross-payment run payment media functionality.
There are several restrictions in place for the creation of collectors:
• The PMW must be used for all payment runs that use the SAP Bank
Communication Management.
• HR payments can only be grouped with other HR payments.
• Payments from company A can only grouped with payments from company
B if the local currencies are the same or else a new collector will be created
for each local currency.
• Payment run identifications must have been reserved in advance.
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 41
Unit 2: Business Process: Batching in BCM FSC130
Figure 25: Checking the Status of Collector Payments
Transaction BNK_MONIP gives an overview of all payments that are to be
managed through BCM. You can restrict the payments you want to see by the
collector and date they belong to, the payment run date and ID, by file, batch,
or other criteria.
The program presents a list of all payments routed over BCM and their current
status which uses the same logic of traffic lights:
• Red: for payments that have not been merged
• Yellow: for payments which are not in a file (approval process)
• Green: for payments that are in a file
• There are other statuses, such as payment rejected or payment resubmitted
Along with the status information, you can also see payment-relevant information,
such us:
• Payment document number
• Payment method
• Account ID
• House bank
• Payment run date
• Payment run ID
42
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Application View: Batching in BCM
Figure 26: Reversing a Merge Run
With EhP 4 it is possible to reverse a merge created by the program
SAPFPAYM_MERGE. In transaction BNK_MERGE_RESET the user can entry
the Run Date and the Identification of the run that needs to be reversed. It is
important not to confuse the Run Date/Identification of the merge with those
of a payment run. The user can easily check this information on the Status of
Collector Payments
The program to reverse a merge lists all batches belonging to a given merge run
with a traffic light depending on their status
• Green: all new batches that were just created but haven't gone through any
approval step. Also payments that could not be batched due to an error on
creation. The error can be due to missing rules or a wrong Merge ID
• Yellow: all other batches. For example batches with automatic approval
• Red: Batches in the middle of the approval process
The user has the option of reversing on a strict mode meaning that the reversal
will only take place provided that all the rows on the list have a green status. On
non-strict mode green and yellow batches can be reversed.
It is important to keep in mind that all cleared items need to be manually reversed.
TA FBRA
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 43
Unit 2: Business Process: Batching in BCM FSC130
Figure 27: What Is a Batch?
A batch is a group of payments that can be processed as one object by the bank
and that usually results in one bank statement item.
The batching of files is triggered automatically by the collector program, that is,
collectors and batches are created in one step.
• A collection of payment runs (Collector), will create a number of batches.
One Batch generates one payment file
• The number of batches created will depend on the batching rules set up in
Customizing, how the different payment methods are customized, and also
on the different target formats associated with those payment methods. The
format-based grouping takes precedence to the rules grouping.
• The created batches go through an approval process, if that is customized,
and the files will be created accordingly once the batches are approved by
the responsible user.
• If there is no approval process customized,the payment files are created
and sent to the bank.
44
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Application View: Batching in BCM
Figure 28: Batch and Payment Monitor
With this report, you are able to see the batches already created and their status. It
is different from transaction BNK_MONIP in that it shows only batches and files,
whereas the transaction shows individual payments that have been identified to be
managed by BCM, even if they have not been merged and batched.
The Batch and Payment Monitor is needed to have an overview of the batch life
cycle: Creation – approval – sending – confirmation – completion (bank statement)
The monitor has two levels:
• Initially, it shows only batches (headers)
• On drill-down, it shows (in a new ALV screen) all the payments (items) that
belong to the chosen batch
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 45
Unit 2: Business Process: Batching in BCM FSC130
46
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Application View: Batching in BCM
Exercise 2: Batching of Payment Orders
Exercise Objectives
After completing this exercise, you will be able to:
• Merge specific payment orders in a collector
• Create batches of the collector based on a set of predefined batching rules
• Check the status of batches and payments in the system
• Reverse a merge
Business Example
The accounting department would like to batch their payment orders according
to the following rules:
• Payments under 500 EUR → Create payment media automatically
• Payments between 500 EUR and 5,000 EUR → One Approver
• Payments greater than 5,000 EUR → Two Approver
User ID: FSACC-##
Task 1:
Payment status for batching process
1. Have a look at the status of your payments for the batching process. What is
the status of your payments? Go into detailed view.
Task 2:
Create an erroneous merge run by not entering a prefix for the identification for
the merge run
1. Merge your two payment runs and create batches. Make sure that you select
only your two payment runs BC##1 and BC##2. Leave empty the Prefix for
Identification in the area 'Payment medium run'
Task 3:
Check the status of your collector payments
1. Check the status of merge you did in the previous task. What color is the
status of your payments?
Continued on next page
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 47
Unit 2: Business Process: Batching in BCM FSC130
Task 4:
Reverse the erroneous merge
1. Reverse the merge you did on task 2
Task 5:
Create batches
1. Merge your two payment runs and create batches. Make sure that you select
only your two payment runs BC##1 and BC##2 and use the cross-payment
run payment media identification AC.
Task 6:
Display the batches
1. Take a look at your batches. How many batches were created? What is
the status of your batches?
Make yourself familiar with the navigation in the batch and payment monitor.
Task 7:
Payment status for batching process
1. Have a look on the status of your payments for the batching process. What is
the status of your payments now?
48
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Application View: Batching in BCM
Solution 2: Batching of Payment Orders
Task 1:
Payment status for batching process
1. Have a look at the status of your payments for the batching process. What is
the status of your payments? Go into detailed view.
a) Payment status for batching process
Accounting → Financial Supply Chain Management → Bank
Communication Management → Environment → Status of Collector
Payments
Enter the following data:
Original Payment Run
Field Name or Data Type Values
Run Date Today
Identification BC##*
The other fields can remain unchanged.
Execute.
On the next screen, have a look at the given values of your payments.
Have a special look at the status of your payments. The status of your
payments is Payment not in Batch .
Select one of your payments. Click Details . Check the additional
values. Do the same for your other three payments.
Continued on next page
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 49
Unit 2: Business Process: Batching in BCM FSC130
Task 2:
Create an erroneous merge run by not entering a prefix for the identification for
the merge run
1. Merge your two payment runs and create batches. Make sure that you select
only your two payment runs BC##1 and BC##2. Leave empty the Prefix for
Identification in the area 'Payment medium run'
a) Accounting → Financial Supply Chain Management → Bank
Communication Management → Processing → Merge Payments
Enter the following data:
Pymt. runs
Field Name or Data Type Values
Run Date Today
Identification BC##1 to BC##2
Payment Medium Run
Field Name or Data Type Values
Run Date Today
Prefix for the Identification empty
Execute. On the following screen verify that 4 payments were selected.
Enter.
Hint: Since you deliberately did not enter a prefix for the
identification the system will not be able to find rules where it
can draw batches from.
Continued on next page
50
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Application View: Batching in BCM
Task 3:
Check the status of your collector payments
1. Check the status of merge you did in the previous task. What color is the
status of your payments?
a) Accounting → Financial Supply Chain Management → Bank
Communication Management → Environment → Status of Collector
Payments
Enter the following data:
Field Name or Data Type Values
Merge date Today
Paying company code AC##
Execute
The status of your payments should be red, however they will have a
Merge ID assigned. Note the Merge ID
Merge ID__________________________
Task 4:
Reverse the erroneous merge
1. Reverse the merge you did on task 2
a) Accounting → Financial Supply Chain Management → Bank
Communication Management → Environment → Reset a Payment
Media Batch run
b) Enter the following data:
Field Name or Data Type Values
Run Date Today
Identification The merge ID number from the
previous task
Test Run Unchecked
Strict Check Checked
c) Execute
Continued on next page
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 51
Unit 2: Business Process: Batching in BCM FSC130
Task 5:
Create batches
1. Merge your two payment runs and create batches. Make sure that you select
only your two payment runs BC##1 and BC##2 and use the cross-payment
run payment media identification AC.
a) Accounting → Financial Supply Chain Management → Bank
Communication Management → Processing → Merge Payments
Enter the following data:
Pymt. runs
Field Name or Data Type Values
Run Date Today
Identification BC##1 to BC##2
Payment Medium Run
Field Name or Data Type Values
Run Date Today
Prefix for the Identification AC
Execute. On the following screen verify that 4 payments were selected.
Enter.
Task 6:
Display the batches
1. Take a look at your batches. How many batches were created? What is
the status of your batches?
Continued on next page
52
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Application View: Batching in BCM
Make yourself familiar with the navigation in the batch and payment monitor.
a) Accounting → Financial Supply Chain Management → Bank
Communication Management → Status Management → Batch and
Payment Monitor
Enter the following data:
Main Selection
Field Name or Data Type Values
Paying company code “AC##”
All other values can remain unchanged.
Execute.
Three batches were created.
The status of the batch with the low value payment is Payment medium
created.
The status of the other batches is Payment batch created.
Choose the New tab page. Here, you see the medium and the high value
batch, because they are waiting for the first approval.
Choose the Approved tab page. Here, you see the low value batch,
because no approvals arenecessary for low value payments.
Continued on next page
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 53
Unit 2: Business Process: Batching in BCM FSC130
Task 7:
Payment status for batching process
1. Have a look on the status of your payments for the batching process. What is
the status of your payments now?
a) Accounting → Financial Supply Chain Management → Bank
Communication Management → Environment → Status of Collector
Payments
Enter the following data:
Original Payment Run
Field Name or Data Type Values
Run Date Today
Identification BC##*
The other fields can remain unchanged.
Execute.
The status of the low value payment is Payment in File .
The status of the other payments is Payment not in File .
54
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Application View: Batching in BCM
Exercise 3: Free Form Payment (optional)
Exercise Objectives
After completing this exercise, you will be able to:
• Realize free form payments
• Route free form payments in SAP Bank Communication Management
• Run the payment program to settle payment requests
Business Example
The accounting department has received an order to execute a payment
immediately.
User ID: FSACC-##
Task 1:
Free Form Payment
1. Realize a free form payment for vendor T-F00L00 in the amount of 50 €.
Choose House Bank 1000, Account ID 1000 and Payment Method 5 (SEPA
Credit Transfer). Note the payment request number (not document number!).
Task 2:
Reserve identification for cross-payment run payment media
1. Reserve the identification BC##* (## = group-number) to create
cross-payment run payment media for payment runs to settle payment
requests. Make sure that payment runs with this identification are available
in Bank Communication Management (BCM).
Task 3:
Initiate payment run
1. Settle your payment request you have created in exercise 3-1. Use the
reservation ID BC##3.
Us Payment Method 5 (SEPA Credit Transfer) and schedule the next
payment run in one week.
Continued on next page
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 55
Unit 2: Business Process: Batching in BCM FSC130
Task 4:
Create batch
1. Merge your new payment run to create a batch. Make sure that you select
only your payment run BC##3. Use the cross-payment run payment media
identification AC.
Task 5:
Payment status for batching process
1. Have a look at the status of your free form payment for the batching process.
What is the status of this payment?
Task 6:
Display the batch
1. Take a look at your new batch. What is the status of your new batch?
56
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Application View: Batching in BCM
Solution 3: Free Form Payment (optional)
Task 1:
Free Form Payment
1. Realize a free form payment for vendor T-F00L00 in the amount of 50 €.
Choose House Bank 1000, Account ID 1000 and Payment Method 5 (SEPA
Credit Transfer). Note the payment request number (not document number!).
a) Accounting → Financial Accounting → Banks → Outgoings →
Online Payments → Vendors – Payment Request
Enter the following data:
Business Partner
Field Name or Data Type Values
Vendor T-F00L00
Company Code AC##
House Bank
Field Name or Data Type Values
Paying Company Code AC##
House Bank 1000
Account ID 1000
Payment Data
Field Name or Data Type Values
Pymt curr.amnt EUR 50
Payment method 5
Value Date Today
Posting Date Today
Enter. Click (Payments).
Write down the payment request number (not document number!):
_________________ (Payment Request)
Continued on next page
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 57
Unit 2: Business Process: Batching in BCM FSC130
Task 2:
Reserve identification for cross-payment run payment media
1. Reserve the identification BC##* (## = group-number) to create
cross-payment run payment media for payment runs to settle payment
requests. Make sure that payment runs with this identification are available
in Bank Communication Management (BCM).
a) Accounting → Financial Accounting → Accounts Payable →
Periodic Processing → Payments
Go to Environment → Payment Medium → Cross-Payment Run
Payment Medium → Reserve Identification
or
In the IMG (Transaction: SPRO) select:
Financial Accounting → Accounts Receivable and Accounts Payable
→ Business Transactions → Outgoing Payments → Automatic
Outgoing Payments → Payment Media → Define Identification for
Cross-Payment Run Payment Media
Navigation:
Click FI-BL Payment program for payment requests.
On the following screen click New Entries.
Enter the following data:
Field Name or Data Type Values
Identifier BC##*
BRM Check
Save.
Task 3:
Initiate payment run
1. Settle your payment request you have created in exercise 3-1. Use the
reservation ID BC##3.
Us Payment Method 5 (SEPA Credit Transfer) and schedule the next
payment run in one week.
a) Accounting → Financial Accounting → Banks → Outgoings →
Automatic Payment → Payment Requests
Enter the following data:
Continued on next page
58
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Application View: Batching in BCM
Field Name or Data Type Values
Run Date Today’s date
Identification BC##3
Continue (Enter).
The status of the new payment run is: no parameters created yet.
Navigation:
Click on Maintain payment run parameters .
Enter the following data:
Field Name or Data Type Values
Posting Date Today’s date
Next payment run on One week after posting
date
Company code AC##
Payment methods 5
Vendor T-F00L00
Navigation:
Click on Maintain parameters for additional log .
Enter the following data:
Desired log for payment method selection
Field Name or Data Type Values
Payment method selection in all
cases
Check
Other log options
Field Name or Data Type Values
Line items of the payment
documents
Check
Accounts required
Continued on next page
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 59
Unit 2: Business Process: Batching in BCM FSC130
Field Name or Data Type Values
Vendor T-F00L00
Enter.
Navigation:
Click on Dynamic selection .
Enter the following data:
Field Name or Data Type Values
Key number “Payment Request
number noted above”
Save. Save.
Schedule a payment proposal
Click on Schedule Proposal .
Check Start immediately.
Continue.
Update the status until it says Payment proposal has been created.
Check the results by clicking on Display Proposal Log . By
scrolling down you should see the payment amount of 50 € in a box.
Schedule a payment run
Click on Schedule payment run .
Check Start immediately.
Continue.
Update the status until it says:
Payment run has been carried out
Posting Orders: 1 generated, 1 completed.
Continued on next page
60
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Application View: Batching in BCM
Task 4:
Create batch
1. Merge your new payment run to create a batch. Make sure that you select
only your payment run BC##3. Use the cross-payment run payment media
identification AC.
a) Accounting → Financial Supply Chain Management → Bank
Communication Management → Processing → Merge Payments
Enter the following data:
Pymt. runs
Field Name or Data Type Values
Run Date Today
Identification BC##3R
Payment Medium Run
Field Name or Data Type Values
Run Date Today
Prefix for the Identification AC
Execute. Enter.
Continued on next page
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 61
Unit 2: Business Process: Batching in BCM FSC130
Task 5:
Payment status for batching process
1. Have a look at the status of your free form payment for the batching process.
What is the status of this payment?
a) Accounting → Financial Supply Chain Management → Bank
Communication Management → Environment → Status of Collector
Payments
Enter the following data:
Original Payment Run
Field Name or Data Type Values
Run Date Today
IdentificationBC##*
Set the other fields free.
Execute.
The status of your free form payment is Payment in file .
Task 6:
Display the batch
1. Take a look at your new batch. What is the status of your new batch?
a) Accounting → Financial Supply Chain Management → Bank
Communication Management → Status Management → Batch and
Payment Monitor
Enter the following data:
Main Selection
Field Name or Data Type Values
Paying Company Code “AC##”
All other values can remain unchanged.
Execute.
The status of the new batch with the low value payment is Payment
medium created.
62
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Application View: Batching in BCM
Lesson Summary
You should now be able to:
• Explain the batching process in SAP Bank Communication Management
• Explain the concept of rules
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 63
Unit 2: Business Process: Batching in BCM FSC130
Lesson: Customizing Batching Rules in BCM
Lesson Overview
This lesson gives an introduction to the customizing of batching rules.
Lesson Objectives
After completing this lesson, you will be able to:
• Understand the main Customizing settings in SAP Bank Communication
Management for batching payments
Business Example
Your company would like to implement its own rules. You have been selected to
try out one rule that you will test with payment requests.
Figure 29: Customizing in BCM – Basic Settings
64
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Customizing Batching Rules in BCM
Basic Settings: determine the rule currency, the exchange rate type, the number of
days for resubmission, and whether a signature is required when releasing a batch
• Rule currency: When a payment batch is evaluated for release (such as dual
control, triple control, automatic release and so on), the total batch amount
can be evaluated based on the default currency if the payments in the batch
consist of different currencies or different company code (hence different
local currency).
• Exchange rate type: determines which of the exchange rate types should be
used when converting other currencies into the rule currency.
• Days Resubmission: is the default date that will be displayed by the system
when a batch is resubmitted by an approver. The value is entered as number
of days after the batch is resubmitted.
• Signature required: should this parameter be checked, then the approval
process will require that the approver sign the change log.
The rule currency is used for two purposes in the release process:
• Determination of the release principle: dual, triple or 4x control in
BNK_COM. This will be explained in the lesson Customizing: Approval
Process in BCM
• Agent determination rules: also explained in the lesson: Customizing:
Approval Process in BCM
Payment Grupping: includes the Customizing of rules
Payment Status Management: deals with the mapping of status messages that
come from SWIFT or the bank
Bank Statement Monitor: includes the necessary Customizing steps to set up the
bank statement monitor for each account per house bank
Release Strategy: includes the necessary steps to set up a batch approval process
Figure 30: Customizing in BCM – Payment Grouping
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 65
Unit 2: Business Process: Batching in BCM FSC130
Rule Maintenance: In this IMG activity, you can define the rules for the kind of
grouping you desire for payments. Rules should be prioritized, so that when there
is more than one rule satisfying the criteria for grouping, your priorities determine
the batching rule. Once a rule is defined, click the maintain button to specify
the criteria for batching rules. Here, all attributes of the payment are provided.
Only attributes making sense for the batching rule should be double-clicked and
then maintained.
Aditional Criteria for Payment Grouping: In this IMG activity, you can set
additional criteria (apart from batching rules), such as requiring all payments of
a batching rule to belong to a certain date. Up to two grouping criteria can be
defined.
Payment Medium: Create/Assign Selection Variants: In this activity, you can
create and assign selection variants for a format. Selection variant maintenance
is a requirement for automatically scheduling the payment media of the Payment
Medium Workbench in the payment program.
Figure 31: Payment Grouping – Rule Maintenance
Rule ID: Rule identification
Priority: Resolution factor that helps a single rule to be picked up. Hence, a
payment batching rule should be specified with a meaningful priority
Rule description: Language-dependent rule description for Rule ID
66
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Customizing Batching Rules in BCM
Figure 32: Priority
Priority
• Use: When a payment is batched, the priority factor helps identifying a
single rule in case multiple rules are evaluated for a given payment. A
priority of 0 is the highest value that can be given.
• Dependencies: The priority makes sense when defined along with a payment
batching rule.
Figure 33: Rule Maintenance Process
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 67
Unit 2: Business Process: Batching in BCM FSC130
It is possible to select from several attributes for the conditions of the rules, such as:
• Merge ID: to restrict the generation of rules to certain collectors
• Amount paid in local currency: to segregate according amount ranges
• Vendor: in case some vendors are to be shown separately in the account
statement
• House bank: in case payments to certain bank need to be highlighted. For
example, if payments to Bank A need to be sent before 10 am
• Business area
• And several others
You can also use logical operators to control the conditions of the rule. For
example, it would be possible to create a rule for payments to vendors VENDOR00
– VENDOR50 (VIP) over 10,000 EUR or to vendors VENDOR51 to VENDOR99
over 5,000 EUR. This kind of batches could be set up to undergo a dual control.
Figure 34: Rule Example
The combination of logical operators, attributes, and relational operators enables
the creation of complex rules for the generation of batches. It is also possible to
use the multiple selection capabilites to select several attribute ranges or several
attribute single values.
In this particular scenario, payments over 10,000 EUR done to the range Vendor00
to Vendor49, which could be VIP vendors, will go to a batch. Consequently, also
payments to the range Vendor50 to Vendor99 but starting at 5,000 EUR would
belong to the same batch.
A similar scenario of direct debits could also be easily implemented where the
limits would contain positive amounts (incoming payments) and customers would
be used instead of vendors.
68
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Customizing Batching Rules in BCM
Since the rules are connected to an approval process, it makes sense to check the
outgoing payments by single, dual or triple control depending on the amount
being paid. This can be accomplished by creating three different batch rules for
three non-overlapping amount ranges.
Figure 35: Payment Grouping – Additional Criteria for Payment Grouping
When it is necessary to batch according to attributes that can take several values,
the Grouping Fields, which are populated from the structure REGUH, provide a
simple tool to tackle this task. Up to two Grouping Fields can be configured in the
system.
For example, if your company wants to create different batches not only for high,
medium and low payments but also by currency and by posting date it does not
need to enter every single currency key or every possible posting date.
The payment grouping can be done with all the fields from the vendor master data.
As of EhP 4 it is also possible to populate the grouping fields with other fields in
casethe structure REGUH does not provide them. For this purpose implement
the BAdI found in the following customizing path: Financial Supply Chain
Management → Bank Communication Management → Payment Grouping →
BAdI for Additional Payment Criteria
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 69
Unit 2: Business Process: Batching in BCM FSC130
Figure 36: Payment Grouping – Payment Medium: Create/Assign Selection
Variants
To assign a selection variant to a format, double-click the required format to
select it on the left side of the screen. The payment medium format is displayed
on the right side of the screen.
Use the possible entries button (F4) to display the existing variants in the Selection
variants field. Select the required variant.
You can create an appropriate variant by choosing Variants → Edit variants.
When you select this function, the selection screen of the report program
SAPFPAYM appears. Enter the required selection criteria on this screen, maintain
the attributes, and save the variants. You return to the screen for maintaining
selection variants for payment medium formats using the Back button.
Figure 37: Selection Variants
70
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Customizing Batching Rules in BCM
Variants of the Generic Payment Medium Program
• The payment run is separated into groups, depending on the level of detail
of the format, such that every group results in one single payment medium
(for example, file).
• The assignment has to be done once (as permanent setting instead of the
former payment program parameters for the classical payment medium
programs (RFFO*)), the payment program will schedule the corresponding
report variants for each group that has been created in a payment run.
• It is necessary to assign a report variant of the payment medium program to
each group to ensure that each payment will be contained in one payment
medium. A dummy selection variant can be easy assigned by ith using the
copy and paste functions together with the line marking functions or by
using the search and replace function.
• In the variant, you are able to customize format-specific parameters, print
parameters, and the output control.
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 71
Unit 2: Business Process: Batching in BCM FSC130
72
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Customizing Batching Rules in BCM
Exercise 4: Customizing Batching Rules
in BCM
Exercise Objectives
After completing this exercise, you will be able to:
• Verify batching rules
Business Example
The accounting department would like to verify the rules for different amounts.
User ID: FSACC-##
Task:
Check the batching rules
1. Check the following attributes from the batching rules and write them down
below:
Rule ID ACHIGH ACLOW ACMEDIUM
Priority
Merge ID
(range)
Amount in
local Currency
(range(s))
2. Look for more attributes for batching rules
Give three additional attributes to define rules for batches:
1.
2.
3.
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 73
Unit 2: Business Process: Batching in BCM FSC130
Solution 4: Customizing Batching Rules
in BCM
Task:
Check the batching rules
1. Check the following attributes from the batching rules and write them down
below:
Rule ID ACHIGH ACLOW ACMEDIUM
Priority
Merge ID
(range)
Amount in
local Currency
(range(s))
a) Check the batching rules
In the IMG (Transaction: SPRO) choose Financial Supply Chain
Management → Bank Communication Management → Payment
Grouping → Rule Maintenance
Navigation:
In the View for Rule maintenance, you can see the priorities of the
three rules like in the table below.
To see the Merge IDs and the Amount in local Currency of the rules
click on Detail View .
Result:
Rule ID ACHIGH ACLOW ACMEDIUM
Priority 1 1 1
Merge ID
(range)
AC000B –
AZZZB
AC000B –
AZZZB
AC000B –
AZZZB
Amount in
local Currency
(range(s))
- 999999999 to
- 5000
And
5000,01 to
999999999
- 499,99 to
499,99
- 5000 to - 500
And
500 to 5000
Continued on next page
74
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Customizing Batching Rules in BCM
2. Look for more attributes for batching rules
Give three additional attributes to define rules for batches:
1.
2.
3.
a) Look for more attributes for batching rules
Navigation:
Click Detail View of one existing batching rule.
Click New Entry .
Click Enter .
→ Attributes to define Rules for Batching
Result (Example):
1. Merge Date
2. Payment Method
3. Vendor
Go back. (Do not execute).
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 75
Unit 2: Business Process: Batching in BCM FSC130
Lesson Summary
You should now be able to:
• Understand the main Customizing settings in SAP Bank Communication
Management for batching payments
76
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Unit Summary
Unit Summary
You should now be able to:
• Explain the batching process in SAP Bank Communication Management
• Explain the concept of rules
• Understand the main Customizing settings in SAP Bank Communication
Management for batching payments
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 77
Unit Summary FSC130
78
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
Unit 3
Business Process: Approval Process
in BCM
Unit Overview
The concept of approval and approval customizing will be presented
Unit Objectives
After completing this unit, you will be able to:
• Understand the approval process in BCM
• Understand how urgent payments can be processed in BCM
• Get an overview of the integration of BCM with Cash Management
• Understand how digital signatures are used in the approval process in BCM
• Understand how to use different signatories to release payments
• Describe how to use workflow when approving batches
• Name the advantages of using workflow
• Unterstand the main Customizing settings in BCM for approval of payments
• Understand the main Customizing settings in BCM for digital signatures
Unit Contents
Lesson: Application View: Approval Process in BCM.... . . . . . . . . . . . . . . . . . . . 80
Exercise 5: Approval Process in BCM.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Lesson: Customizing: Approval Process in BCM .... . . . . . . . . . . . . . . . . . . . . . .110
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 79
Unit 3: Business Process: Approval Process in BCM FSC130
Lesson: Application View: Approval Process in BCM
Lesson Overview
This lesson gives an overview of the approval process in BCM.
Lesson Objectives
After completing this lesson, you will be able to:
• Understand the approval process in BCM
• Understand how urgent payments can be processed in BCM
• Get an overview of the integration of BCM with Cash Management
• Understand how digital signatures are used in the approval process in BCM
• Understand how to use different signatories to release payments
Business Example
Various employes are involved in the process of generating payment media. One
employee executes the payment program, aother approves until a certain amount,
and another gives the final approval. The department would like to know to what
extent SAP is able to support this process flow.
Figure 38: Approval Process – Overview
SAP Bank Communication Management offers a tool which allows specific users
to approve the payments associated to the batches. Once the payments are batched,
it can be decided whether the batch has to go for approval or not.
The payment media are generated only after the batch has been released by the
final approver.
The SAP Workflow tool is used as an engine behind the approval process. It is
encapsulated within the BCA release tool (framework for the principle of dual
control)
80
© 2014 SAP AG or an SAP affiliatecompany.
All rights reserved. 2014
FSC130 Lesson: Application View: Approval Process in BCM
SAP delivers standard workflow templates:
• 50100021 Workflow for One-Step Release Procedure
• 50100022 Workflow for Two-Step Release Procedure
• 50100023 Workflow for Three-Step Release Procedure
• 50100024 Workflow for Dynamic Release Process
Note: Standard Workflow Templates can be viewed in transaction SE80,
for package BCA_RELEASE_WORKFLOW→ Business Engineering →
Workflow Templates
Figure 39: Possible Actions for Approvers
The first approver is the one with the most flexibility when it comes to release
batches. He or she can approve a whole batch; resubmit a batch, where it is
rescheduled for re-batching a few days later; resubmit a single payment; and reject
batches and single payments.
On the other hand, the following approvers can only approve or return at a batch
level. The reason for this is that if subsequent approvers were allowed to approve
or return single payments, the batches would not be the same through the chain of
approval. This fact would definitely lead to audit confusions and problems.
Should the final approver return a batch, it is required that he or she attach a
reason for it. For example, the cash manager (final approver) could find out that
the account balance is not enough to settle all the payments in the batch. He
could return the whole batch to the first approver instructing him to reject some
payments in the batch until it can be settled with the available funds.
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 81
Unit 3: Business Process: Approval Process in BCM FSC130
Figure 40: Approve Payments
Change and Release Tab
The first three action buttons Approve/Resubmit/Reject are for the whole batch.
The user first selects one or more batches and then takes action:
• Choosing Approve will leave the batch as it is. The workflow is started (after
Save) so that other users can continue approval.
• The buttons Resubmit and Reject have the same effect as if every item
(payment) in the batch is resubmitted and rejected.
• On all three actions, the batch is removed from this tab and appears in
processed batches instead, together with a new status that describes the
action.
Additional Release Steps Tab
Here, the user can also display the payments that make up the batch, but there is
no action possible on the payment level: In this stage, the structure of the batch
may not be changed any more, otherwise the principle of dual control would be
violated.
Two actions are possible (both again with signature and simultaneously for all
batches selected):
• Approve continues the approval process
• Return stops the approval process and makes the batch like “initial again”:
That is, now it will appear on the first tab “Change and Release” and an
authorized user is able to do the same actions as for a new batch.
Both actions move the batch into the Processed Batches tab.
82
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Application View: Approval Process in BCM
Other Tabs
• Processed Batches and Processed/Dropped Payments store the objects acted
upon within the session (before a SAVE), and allows the user to undo his
or her actions
• Change Log is a preview of the application log that will be stored on SAVE,
and that can afterwards be seen with Transaction SLG1, object FBPM or
Transaction BNK_LG_SGN
Figure 41: Urgent Payments
With SAP Bank Communication Management Enhancement Package 4 it is now
possible to indicate urgent payments in the Batch and Payment Monitor and in
the Approval Monitor
The following features are included
• Indicate payments as urgent or not urgent (on batch level). The user can set
this indication manually in TA BNK_MONI and BNK_APP
• set the urgent flag automatically based on flexible rules, e.g dependent on
the payee
• remove an automatically set flag on batch level
• manually set or change the information regarding charge bearer
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 83
Unit 3: Business Process: Approval Process in BCM FSC130
Figure 42: Resubmit
If the user marks one or several payments and chooses Resubmit, a popup appears
where he can enter a new date, when those payments are to be included in another
batch.
Those resubmitted payments are shown in the list with their new status (technical
ID starting with $) and their amount is set to zero. In addition, they appear in the
Processed/Dropped Payments tab, with same status and their original amount
Undoing Changes
On the tabs Processed Batches and Dropped Payments the changes of the
processed or dropped batches can be undone. The user has the option to mark one
or several of those batches and choose undo to take back his decision and put the
batch back into the original tab (Change and Release or Additional Release Steps)
84
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Application View: Approval Process in BCM
Figure 43: Update of Cash Management after Reject/Resubmit of Documents
The payment program automatically posts payments and related postings, thus
when a payment is resubmitted or rejected on SAP BCM the system needs to
adjust the original value dates on the payment documents. For this purpose, there
is a BAdI definition BNK_BADI_ORIG_PAYM_CHG that updates the value
date and cash management data of the original payment documents. Should the
payment be resubmitted then the value date is set to the resubmission date. In case
the payment is rejected the value date is set to 31.12.9999 thus eliminating the
original document from the cash position report. It is also possible to implement
your own logic in that BAdI definition, so for example it would be possible to
automatically reverse the payment document in case the payment is rejected. Also
when a payment is resubmitted it might make sense to add additional days that
account for the value date settings on the payment program.
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 85
Unit 3: Business Process: Approval Process in BCM FSC130
Figure 44: Drill-Down Possibilities
On both the batch and payment level, there are a number of drill-down possibilities
that can be accessed through the navigation buttons in the ALV list or in the
context menu of the first column of the list
It is possible to specify that the approver is required to drill down to the payments
view before he or she can release a batch or payment.
Figure 45: Change Log
The approval actions performed within one session are summarized in the change
log. This tab is for information purposes only and does not allow an undo.
The change log stores only the state that is to be saved. If the user decides, for
example, to undo his approval for a batch, the corresponding entry will simply
disappear from the log.
• Approve is shown with the green (information) symbol.
• Reject/Return with yellow (warning symbol)
86
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Application View: Approval Process in BCM
The user proceeds as follows:
• Cancel (F12) will still stop the SAVE action.
• With Continue (Enter) he or she proceeds and, if the signature switch in
Customizing is active, the user gets the Signature popup. Here, the user has
to enter their signature to confirm the action. In the document section of the
signature popup, he or she can see a copy of the action log above. Only if the
signature is successful, the changes will be written to the database.
A normal Save implies a Refresh, that is, afterwards the program will again read
on the data base and display data.
Figure 46: Signatures
Digital signatures are used in the approval process of the batches. The object that
is signed is the action document (log from the approve payments transaction) and
not the batch file. Digital signatures are based on Customizing for the existing
Signature Tool.
Secure Storeand Forward
The technology behind the digital signature application is based in the so called
Secure Store & Forward Interface (SSF). Secure Store and Forward (SSF)
mechanisms provide you with the means to secure data and documents in SAP
Systems as independent data units. By using SSF functions, you can “wrap” data
and digital documents in secure formats before they are saved on data carriers or
transmitted over (possibly) insecure communication links. The data must not
remain within the SAP System; if you save the data in a secure format in the SAP
System, it remains in its secured format even if you export it out of the system.
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 87
Unit 3: Business Process: Approval Process in BCM FSC130
SSF mechanisms use digital signatures and digital envelopes to secure digital
documents. The digital signature uniquely identifies the signer, is not forgeable,
and protects the integrity of the data. Any changes in the data after being signed
result in an invalid digital signature for the altered data. The digital envelope
ensures that the contents of data are only visible to the intended recipient(s).
SSF requires the use of a third-party security product to provide its functions. As
the default provider, we deliver the SAP Security Library (SAPSECULIB)
with SAP Systems. The SAPSECULIB, however, is limited to providing digital
signatures only. For digital envelopes, encryption, or crypto hardware (for
example, smart cards or crypto boxes), you need to use a SAP-certified external
security product. For a product to be certified by SAP, it must support the PKCS#7
standard data format. For information about supported products, see the SAP
Complementary Software Program (http://www.sap.com/csp).
To effectively use the SSF mechanisms, you need to have an established
public-key infrastructure (PKI). The PKI makes sure that you can validate and
trust the digital signatures, certificates, and Certification Authorities (CAs). A PKI
is often, although not necessarily, supported by the external security products that
are available on the market. Although SAP Systems do not provide a PKI directly,
they do support PKIs provided by various security products.
Depending on the security product that you use, you can establish the use of a PKI
in one of many ways. You may want to create your own PKI and CA that you link
to your customers, or you and your customers may want to agree on a common
Trust Center. A common Trust Center is a third-party instance that both you and
your customers can trust to validate and authenticate your PKI participants. Using
a common Trust Center can solve many of the currently open questions regarding
the establishment of a PKI.
88
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
http://www.sap.com/csp
FSC130 Lesson: Application View: Approval Process in BCM
Figure 47: Different User ID for Signature
It is not uncommon that users log on to their systems using a Single-Sign-On
method, therefore they don't normally know or have a SAP password. This would
mean that these users would not be able to release payments in SAP BCM. Also
from a compliance point of view it is important to distinguish between system
password and payment release password. In order to solve this problem, SAP
BCM offers the possibility of assigning a signature user to a logon user.
In TA BNK_SIGN_MAINTAIN signatories can be assigned to logon users.
It is necessary to create a new user with password before that will act as a
signatory. The signatories then need to be confirmed by an authorized user in TA
BNK_SIGN-CONFIRM, where a list of all confirmations is displayed along with
a traffic light. If this traffic light is green the proposed and confirmed signatory
already agree and there is no action required; yellow, if the current user is allowed
to confirm the proposed signatory; red, if hte proposed and confirmed signatory
disagree, but the current user is not allowed to make them agree.
Approval Reporting
In SAP BCM it is possible to get a report on the approvers of a particular batch.
The TA BNK_MONIA allows the user to filter according to several parameters.
Take Over from Current Processor
A current processor is a notion in the first approval step where batches can be
edited. As soon as a user removes payments from a batch (reject or resubmit) he is
labeled the “Current Processor” of that batch.
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 89
Unit 3: Business Process: Approval Process in BCM FSC130
90
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Application View: Approval Process in BCM
Exercise 5: Approval Process in BCM
Exercise Objectives
After completing this exercise, you will be able to:
• Check cash management
• Approve payments
• Reject payments
• Reverse payments
• Resubmit payments
• Return payments
• List the approvers of a batch
• Process urgent payments
Business Example
The accounting department needs to approve the payments. Different release
strategies are in use.
User ID: FSAPP-## (Attention!)
Task 1:
Check cash management
1. Before releasing your payments, check your cash position in order to
compare how it is affected by rejections and resubmissions.
Task 2:
Approve, reject, and reverse payments. Log on with your user FSAPP-##
1. Approve your high value payments batch. Reject your one with medium
value payments.
2. Reverse the payments from the rejected batch.
3. Check the open items for your three vendors.
Task 3:
Return Payment
1. Return the batch from the group number assigned by the trainer.
2. Attach a Message.
Continued on next page
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 91
Unit 3: Business Process: Approval Process in BCM FSC130
Task 4:
Process your returned batch.
1. From your returned batch, note the payment document number from the
payment in the amount of 10.000 €. Reject the payment in the amount of
10.000 € and resubmit the payment in the amount of 8.000 € in 10 days.
2. Reverse the rejected payment.
3. Check the open items for your three vendors.
4. Rebatch the resubmitted payment.
Task 5:
Check your cash position
1. Now that you have resubmitted and returned batches check the changes in
your cash position. What has changed since you first executed the report?
Task 6:
Display batches.
1. Take a look at your batches. What is the status of your batches now?
Task 7:
Payment status for batching process
1. Have a look at the status of your payments for the batching process. What is
the status of your payments now?
Task 8:
Batch approver list
1. Check who released the batches of your company code
Task 9:
Urgent payments (Optional)
Caution: Read carefully which user you need for each step of the task.
1. You rejected and reversed the payment documents of invoice 2 (4.000 EUR).
Initiate a payment run to settle that invoice.USER: FSACC-##
2. Merge and batch the payment. USER: FSACC-##
3. Set the batch as urgent and approve it. USER: FSAPP-##
92
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Application View: Approval Process in BCM
Solution 5: Approval Process in BCM
Task 1:
Check cash management
1. Before releasing your payments, check your cash position in order to
compare how it is affected by rejections and resubmissions.
a) Accounting → Financial Supply Chain Management → Cash and
Liquidity Management → Cash Management → Information System
→ Reports for Cash Management → Liquidity Analyses → Cash
Position
Enter the following information:
Field Name or Data Type Values
Company code AC##
Cash Position Checked
Grouping ACBANKEN
Display as of Today
Display in EUR
Scaling 0
Execute.
Double click on today's cash position until you reach the detail of
Domestic Transfers.
Take note of the cash position for all days. You should see 22.200 EUR
in domestic transfers.
Continued on next page
2014 © 2014 SAP AGor an SAP affiliate company. All rights reserved. 93
Unit 3: Business Process: Approval Process in BCM FSC130
Task 2:
Approve, reject, and reverse payments. Log on with your user FSAPP-##
1. Approve your high value payments batch. Reject your one with medium
value payments.
a) Accounting → Financial Supply Chain Management → Bank
Communication Management → Processing → Approve Payments
Navigation:
Click on the tab strip Change and Release.
Select your batch with the high value payments.
Click on the icon Approve .
Double-click on the batch with the medium value payment.
Select the payment. Click on Details and note the Payment
document number:________________
Enter. Go back.
Select your batch with the medium value payment.
Click on the icon Reject .
Click on the tab strips Processed Batches and Change Log to view
the results of your transactions.
Save your settings.
Authorize your activities with your user password (digital signature).
Enter.
Continued on next page
94
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Application View: Approval Process in BCM
2. Reverse the payments from the rejected batch.
a) Accounting → Financial Accounting → Accounts Payable →
Document → Reset Cleared Items
Navigation:
Enter the following data:
Field Name or Data Type Values
Clearing Document “noted payment
document number above”
Company Code AC##
Fiscal Year “this year”
Save.
Click on Resetting and reverse.
Enter the following data:
Field Name or Data Type Values
Reversal Reason “01”
The other fields can remain free.
Enter. Enter. Enter.
Continued on next page
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 95
Unit 3: Business Process: Approval Process in BCM FSC130
3. Check the open items for your three vendors.
a) Accounting → Financial Accounting → Accounts Payable →
Account → Display/Change Line Items
Enter the following data:
Vendor selection
Field Name or Data Type Values
Vendor account T-F00K00 to T-F00M00
Company code AC##
Line item selection
Field Name or Data Type Values
Open items Check
Open at key date Today
Type
Field Name or Data Type Values
Normal items Check
Execute.
The item for vendor T-F00K00 in the amount of 4000 € is open again.
Continued on next page
96
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Application View: Approval Process in BCM
Task 3:
Return Payment
1. Return the batch from the group number assigned by the trainer.
a) Accounting → Financial Supply Chain Management → Bank
Communication Management → Processing → Approve Payments
Navigation:
Click on the tab strip Additional Release Steps.
Select the batch with the high value payments from group number ## +
1. Replace ## with your group number.
Click on the icon Return .
Save your settings.
Authorize your activities with your user password (digital signature).
Enter.
2. Attach a Message.
a) Accounting → Financial Supply Chain Management → Bank
Communication Management → Processing → Approve Payments
Double-click on Enter Attachment for Return of: … to create an
attachment for the returned batch.
Enter the following data:
Field Name or Data Type Values
Type SCR
Title “any text”
Enter.
In the text box write a reason for your return.
Save.
Continued on next page
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 97
Unit 3: Business Process: Approval Process in BCM FSC130
Task 4:
Process your returned batch.
1. From your returned batch, note the payment document number from the
payment in the amount of 10.000 €. Reject the payment in the amount of
10.000 € and resubmit the payment in the amount of 8.000 € in 10 days.
a) Accounting → Financial Supply Chain Management → Bank
Communication Management → Processing → Approve Payments
Navigation:
Click on the tab strip Change and Release.
Select your returned batch.
Click Workflow attachments to have a look at the message of
your returned batch. Go Back (F3).
Double-click on the batch number of your returned batch.
Select the payment in the amount of 10.000 €. Click on Details
and note the payment document number:________________
Close the window.
Select the payment in the amount of 10.000 € and click Reject .
Select the payment in the amount of 8.000 € and click Resubmit .
Choose the date in ten days. Go back (F3).
Save your settings. Enter.
Authorize your activities with your user password (digital signature).
Enter.
Continued on next page
98
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Application View: Approval Process in BCM
2. Reverse the rejected payment.
a) Accounting → Financial Accounting → Accounts Payable →
Document → Reset Cleared Items
Enter the following data:
Field Name or Data Type Values
Clearing Document “noted payment
document number above”
Company Code AC##
Fiscal Year “this year”
Save.
Click on Resetting and reverse.
Enter the following data:
Field Name or Data Type Values
Reversal Reason “01”
The other fields can remain free.
Enter. Enter. Enter.
Continued on next page
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 99
Unit 3: Business Process: Approval Process in BCM FSC130
3. Check the open items for your three vendors.
a) Accounting → Financial Accounting → Accounts Payable →
Account → Display/Change Line Items
Enter the following data:
Vendor selection
Field Name or Data Type Values
Vendor account T-F00K00 to T-F00M00
Company code AC##
Line item selection
Field Name or Data Type Values
Open items Check
Open at key date Today
Type
Field Name or Data Type Values
Normal items Check
Execute.
The item for vendor T-F00K00 in the amount of 4000 € is open. And
the item for vendor T-F00K00 in the amount of 10000 € is also open
again.
Continued on next page
100
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Application View: Approval Process in BCM
4. Rebatch the resubmitted payment.
a) Accounting → Financial Supply Chain Management → Bank
Communication Management → Processing → Merge Payments
Enter the following data:
Pymt. runs
Field Name or Data Type Values
Run Date Day of your payment
runs (Yesterday)
Identification BC##*
Payment Medium Run
Field Name or Data Type Values
Run Date today + ten days
Prefix for the Identification AC
Execute. Enter.
Continued on next page
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 101
Unit 3: Business Process: Approval Process in BCM FSC130
Task 5:
Check your cash position
1. Now that you have resubmitted and returned batches check the changes in
your cash position. What has changed since you first executed the report?
a) Accounting → Financial Supply Chain Management → Cash and
Liquidity Management → Cash Management → Information System
→ Reports for Cash Management → Liquidity Analyses → Cash
Position
Enter the following information:
Field Name or Data Type Values
Company code AC##
Cash Position Checked
Grouping ACBANKEN
Display as of Today
Display in EUR
Scaling 0
Execute.
Double click on today's cash position until you reach the detail of
Domestic Transfers.
Take note of the cash position for all days. You should see today 200
EUR and in 10 days 8.000 EUR.
Continued on next page
102
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Application View: Approval Process in BCM
Task 6:
Display batches.
1. Take a look at your batches. What is the status of your batches now?
a) Accounting → Financial Supply Chain Management → Bank
Communication Management → Status Management → Batch and
Payment Monitor
Enter the following data:
Main Selection
Field Name or Data Type Values
Paying company code AC##
Execute.
The status of the batch with the low value payment is Payment medium
created.
The status of the batch with the medium value payment is Rejected
by approver.
The status of theold batch with the high value payments is Resubmitted
by approver.
The status of the new batch with the high value payments is Payment
batch created.
Continued on next page
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 103
Unit 3: Business Process: Approval Process in BCM FSC130
Task 7:
Payment status for batching process
1. Have a look at the status of your payments for the batching process. What is
the status of your payments now?
a) Accounting → Financial Supply Chain Management → Bank
Communication Management → Environment → Status of Collector
Payments
Enter the following data:
Original Payment Run
Field Name or Data Type Values
Run Date Yesterday
Identification BC##*
No reversed documents Do not check
Leavet the other fields empty.
Execute.
The status of the low value payment in the amount of 200 € is Payment
in file .
The status of the payments in the amount of 4.000 € and 10000 € is
Payment reversed .
The status of the payment in the amount of 8000 € is Payment not in
file .
Task 8:
Batch approver list
1. Check who released the batches of your company code
a) Accounting → Financial Supply Chain Management → Bank
Communication Management → Environment → Batch Approver list
Enter the following information:
Field Name or Data Type Values
Paying company code AC##
Execute.
Continued on next page
104
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Application View: Approval Process in BCM
Task 9:
Urgent payments (Optional)
Caution: Read carefully which user you need for each step of the task.
1. You rejected and reversed the payment documents of invoice 2 (4.000 EUR).
Initiate a payment run to settle that invoice.USER: FSACC-##
a) Initiate payment run
Accounting → Financial Accounting → Accounts Payable →
Periodic Processing → Payments
Enter the following data:
Field Name or Data Type Values
Run Date Today’s date
Identification BC##3
Continue (Enter).
The status of the new payment run is: no parameters entered as yet.
Choose the Parameter tab page and enter the following data:
Field Name or Data Type Values
Posting date Today’s date
Docs entered up to Today’s date
Company codes AC##
Payment methods 7
Next posting date One week after posting
date
Vendor T-F00K00
Choose the Free selection tab page and enter the following data:
Field Name or Data Type Values
Field Name Document Number
Values Document number of the
second invoice
Continued on next page
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 105
Unit 3: Business Process: Approval Process in BCM FSC130
To fill in Document Number click . Select Document Number. Press
Enter or double-click on Document Number.
Choose the Additional Log tab page and enter the following data:
Field Name or Data Type Values
Due date check Check (first box)
Payment method selection in all
cases
Check (second box)
Line items of the payment
documents
Check (fourth box)
Vendor T-F00K00
Save.
Return to the Status tab page.
The status of the payment run is: Parameters have been entered.
Schedule a payment proposal
Click on Schedule Proposal .
Check Start immediately.
Continue.
Update the status until it says Payment proposal has been created.
Check the results by clicking on Display Proposal and Display
Proposal Log .
Schedule a payment run
Click on Schedule payment run .
Check Start immediately.
Continue.
Update the status until this message appears:
Payment run has been carried out
Posting Orders: 1 generated, 1 completed.
Continued on next page
106
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Application View: Approval Process in BCM
2. Merge and batch the payment. USER: FSACC-##
a) Accounting → Financial Supply Chain Management → Bank
Communication Management → Processing → Merge Payments
Enter the following data:
Pymt. runs
Field Name or Data Type Values
Run Date Today
Identification BC##3
Payment Medium Run
Field Name or Data Type Values
Run Date Today
Prefix for the Identification AC
Execute. On the following screen verify that 1 payments were selected.
Enter.
Continued on next page
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 107
Unit 3: Business Process: Approval Process in BCM FSC130
3. Set the batch as urgent and approve it. USER: FSAPP-##
a) Accounting → Financial Supply Chain Management → Bank
Communication Management → Processing → Approve Payments
Select the payment for 4.000 EUR that corresponds to your creation
user FSACC-##.
Select Change instruction .
Caution: Be careful to select the button which is located next
to History .
Select column IK (instruction key).
Select the displayed option.
Select Save.
Check how the column Urgent (at the right end) has now an X.
Hint: You can also change the urgent flag in the Batch and
Payment Monitor but ONLY on the tabs New and In approval.
Approve the batch.
Select Save.
Sign with your FSAPP-## password.
108
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Application View: Approval Process in BCM
Lesson Summary
You should now be able to:
• Understand the approval process in BCM
• Understand how urgent payments can be processed in BCM
• Get an overview of the integration of BCM with Cash Management
• Understand how digital signatures are used in the approval process in BCM
• Understand how to use different signatories to release payments
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 109
Unit 3: Business Process: Approval Process in BCM FSC130
Lesson: Customizing: Approval Process in BCM
Lesson Overview
This lesson shows how to customize the approval process in BCM
Lesson Objectives
After completing this lesson, you will be able to:
• Describe how to use workflow when approving batches
• Name the advantages of using workflow
• Unterstand the main Customizing settings in BCM for approval of payments
• Understand the main Customizing settings in BCM for digital signatures
Business Example
The accounting department wants to set up a dual-control process for the approval
of payments.
Workflow Concept
• Workflow covers all aspects of the process
– The process flow itself (business activity)
– The people involved (organization)
– The effects (process information)
Workflow management systems are information technology tools for the
technological implementation of Business Process Reengineering. They support
and speed up business processes. They enable the employees involved to carry out
complex business processes irrespective of time and place.
The flow of work is controlled and coordinated actively by the workflow
management system. The control functions are particularly useful for monitoring
the time spent on individual worksteps and for triggering the relevant escalation
procedures if deadlines are missed. It also enables you to track the current status
of a process at any time.
The Workflow Engine functions integrate and supplement the comprehensive
business functions of the SAP system.
The integration of Organizational Management into the Workflow Engine enables
tasks to be linked with agents using organizational assignments.
110
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Customizing: Approval Process in BCM
Figure 48: Advantages for End Users
As soon as a task is due for processing, it is delivered to the user in their electronic
inbox (the effort of retrieving the task is avoided, because the system delivers it).
All the information, explanations and instructions available are delivered to the
user at the same time.
The workflow branches automatically to the correct transactions of the SAP
system. The workflow definition maps the business process or a sub-process.
Insurance companies were probably one of the first to demonstrate the advantages
of a seamless processing chain. Here, clerks are responsible for acquiring
customers,concluding contracts, and providing support. This contradicts the basic
principles of Taylorism, since the clerk must carry out these tasks across several
applications and functions.
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 111
Unit 3: Business Process: Approval Process in BCM FSC130
Figure 49: The Key Five Questions for Every Business Process
Figure 50: Workflow in BCM
Bank Communication Management uses the already available functions of SAP
Business Workflow. It already contains predefined templates for the approval
process that can be adapted to suit the processes in your company. The workflow
tool distributes the approval tasks to the corresponding staff members defined
as approvers in BCM.
Bank Communication Management works with two release objects, BNK_INI
also called Edit Workflow and BNK_COM also called Main Approval Workflow
Since the first approver has the possibility of changing the batch by, for example,
resubmitting certain payments or rejecting some others the Release Object
BNK_INI is used to enable the editing possibilities.
112
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Customizing: Approval Process in BCM
The subsequent approvers can only approve or return at a batch level, for this, the
additional Release Object BNK_COM is used. A combination of the two objects
enables dual, 3x and 4x control.
Figure 51: Approvals Customizing – Release Strategy
The release strategy in BCM consists of four steps:
• Mark Rules for Automatic Payments: you can select the rules that need no
approval, meaning that inmediately after the batching a payment media will
be created without any approver involved.
• Change and Release: comprehends the customizing tasks of the release
object BNK_INI
• Additional Release Steps: contains the necessary steps to customize the
release object BNK_COM
• Digital Signatures: includes the necessary steps to customize digital
signatures in BCM
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 113
Unit 3: Business Process: Approval Process in BCM FSC130
Figure 52: Mark Rules for Automatic Payments
A user can choose the batching rules that need to go for approval once the batching
is made. If a batching rule is flagged as shown in the picture, the merge program
would create the payment file directly without any approval process. This would
be relevant for direct debits and possibly low value payments.
On the other hand, for high value payments it would make sense to have the
approver drill down on the individual payments of the batch.
Figure 53: Change and Release - Assign Role to Release Steps
Assign Role to Release Steps
114
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Customizing: Approval Process in BCM
In this IMG activity, you can assign a standard role to the individual release steps
of the release procedure that applies for a certain release object. Processing (users,
workplace, organizational units, positions and so on) is linked to the standard role.
The system uses the standard role to find the processors responsible and, through
the SAP Business Workflow, forwards the release object as a work item to them
for processing further.
Requirements
You have made the settings for the corresponding release object in IMG activity
Assign Release Object to Release Procedure.
Activities
1. Choose New Entries.
2. Enter the required values in the following fields:
a) Release Object
b) Release Procedure
c) Release Step
3. Assign a standard role (Rule) to these. You have the following two options
for this:
a) The standard role you are assigning is already created and you know
its number. Enter this number. The standard role you are assigning is
not yet created.
b) Select the corresponding line.
c) Choose Create Role. This brings you to the Selection of Rule
Parameters screen.
d) Select the required parameters, needed to define the standard rules.
e) Choose Generate Rule Now.
f) Choose Copy Generated Rule and save your data.
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 115
Unit 3: Business Process: Approval Process in BCM FSC130
Figure 54: Assign Role to Release Steps (BNK_INI)
ACTIVITIES (continued)
1. If you wish to assign users/processors to the standard rule you have the
following two options:
From this IMG activity:
a) Select the corresponding line
b) Choose Display Rule
2. Create a new responsibility or select an existing one
3. Choose Insert agent assignment
4. Select the user
5. Save your entries
When creating a responsibility you can simply assign it to an existing batch
rule. However, it is also possible to restrict the responsibility to the following
Responsibility Specs:
• Batch amount in batch currency
• Batch currency
• Total batch amount in rule currency
• Maximum payment amount in batch currency (1)
• Maximum payment amount in rule currency (1)
116
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Customizing: Approval Process in BCM
(1) Maximum payment amounts refer to the amount of the highest payment
in the batch
• Grouping field 1
• Grouping field 2
Hint: Also note the connection between the release reasons defined in the
IMG activity Assign Release Object to Release Procedure and the exact
rule definition. You must ensure that the system finds a user group for
each release object via the standard role/rule, that is, the rules are defined
in such a way that they cover all release reasons.
Figure 55: Simulate Rule Resolution
You can fill out one, some or all the container elements (also known as
responsibility specs) to obtain the assign agents that can approve such a batch.
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 117
Unit 3: Business Process: Approval Process in BCM FSC130
Figure 56: Additional Release Steps – Define Release Procedure
In this IMG activity, you can make basic settings for the release of a particular
release object. Since the release of release objects is regulated by the SAP
Business Workflow, in the group frame release you must define if and when the
system forwards a release object to the release process.
118
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Customizing: Approval Process in BCM
Activities
1. Choose a radio button in the group frame Release. If you choose always, you
must also select a release procedurefor all release objects. If you choose
conditional, you can differentiate the release of the release objects according
to release procedures and release reasons.
2. If you choose Display All, you can check whether release reasons have
already been defined for the release object.
3. In change mode, choose Execute. If no release reasons have yet been defined
for the release objects, the Customizing: Release Procedures screen appears.
If release reasons have already been defined for the release objects, the
Release Customizing: All Settings screen appears. If you choose New Entry
or select a line of a release reason, the Customizing: Release Procedures
screen appears.
4. On the Customizing: Release Procedures screen, define or change a release
reason for the selected release object and release procedure by selecting
release attributes from the overview and assigning a lower limit (in the case
of intervals, an upper limit, too) and a comparison operator to every release
attribute in the group frame Dynamic Selections. When you define release
reasons, make sure there is an 'And' connector between the conditions
you define when entering values for the release attributes. Also note the
connection between the release reason and the exact rule definition in the
corresponding IMG activity Assign Standard Role to Release Steps. You
must ensure that the system finds a user group for each release object via
the standard role/rule, that is, that the rules are defined in such a way that
they cover all release reasons.5. You assign the comparison operator by double-clicking on the input fields of
the release attributes.
The release object, release procedure, release reason and release attributes
are related as follows:
• Release object → release procedure 1 : 1 .. 3
• Release procedure → release reason 1 : n
• Release reason → release attributes 1 : 1 .. i; i = number of release
attributes in the overview
The system assigns the numbers of the release reasons. If you wish to delete
individual release reasons, you must individually delete all release attributes
of this release reason. Note that if you choose Deletion of Entries for Release
Object , the system will delete all release reasons.
6. Choose Execute and Save.
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 119
Unit 3: Business Process: Approval Process in BCM FSC130
Figure 57: Assign Role to Release Steps (BNK_COM)
In this IMG activity, you can make the following basic settings for the release of a
particular release object. Since the release of release objects is regulated by the
SAP Business Workflow in the group frame release, you must define if and when
the system forwards a release object to the release process.
If you have configured in transaction BNK_BNK_COM_REL01 release
conditions for the Release Procedures, then you should assign roles (approvers)
to each of the Release Steps.
The assignment is made in a similar way to the assignment of roles in object
BNK_INI.
120
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Customizing: Approval Process in BCM
Figure 58: Assign Workflow Template to Release Procedure
The Release Workflow is the one that the system calls to effect release. The release
workflow in turn calls up the Release Procedure Workflows as sub-workflows.
SAP delivers standard sub-Workflow Templates:
• 50100021 Workflow for One-Step Release Procedure
• 50100022 Workflow for Two-Step Release Procedure
• 50100023 Workflow for Three-Step Release Procedure
And a Release Workflow template:
• 50100024 Workflow for Dynamic Release Process
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 121
Unit 3: Business Process: Approval Process in BCM FSC130
Figure 59: Example of a Triple Control
On this example there is a batching rule for payments above 250.000 EUR. The
company wants to exercise a triple control of those payments given the high
amount. Due to the increasing compliance task the Financial Vicepresident needs
to give the final approval.
To customize this workflow on your companys system, first you assign the agent
ACCOUNTANT to rule VERYHIGH in the Release Object BNK_INI (Edit
Workflow). Now the user ACCOUNTANT can approve, resubmit or reject
payments or whole batches.
In order to trigger the pure approval workflow (Release Object BNK_COM), you
need to define a Condition for the release of this object. You define that for the
rule VERYHIGH the principle of treble control be used.
Finally, you assign the agent TREASURER to the first release step of BNK_COM
for the rule VERYHIGH and the agent VICEPRESIDENT to the second release
step of BNK_COM for the rule VERYHIGH.
122
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Customizing: Approval Process in BCM
Considerations for a smooth Workflow in BCM
• Should any problems arise in the configuration of the Workflow in BCM,
SAPNote 1041016 gives the following troubleshooting advice:
– Check that release procedure for BNK_INI is marked for “Always”
– User WF-BATCH must exist with authorization “SAP_ALL”
– In transaction SWU3 ensure that “RFC destination” is configured
– For object type “BUSISB001” in transaction SWETYPV, activate
“Linkage activated”
– And some more…
Figure 60: Digital Signatures – Specify Signature Method for Approval Using
Simple Signature
Here it is specified the simple signature method for BANCO / BC_LOG object
The options for Signature Method are:
• System Signature with Authorization by SAP User ID/Password
• User Signature with External Security Product with Verification
• User Signature with External Security Product without Verification
In Transaction SLG0 for object CDSG1 (Digital Signature Logging) make an
entry (Sub-object) BANCOM for Payment Release
• In Transaction SIGNA, we define our Application BANCO
• In Transaction SIGNO, we define the object BC_LOG (Bank Communication
Log) in application BANCO
• Meta Table BNK_META_LOG stores the signature information
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 123
Unit 3: Business Process: Approval Process in BCM FSC130
Lesson Summary
You should now be able to:
• Describe how to use workflow when approving batches
• Name the advantages of using workflow
• Unterstand the main Customizing settings in BCM for approval of payments
• Understand the main Customizing settings in BCM for digital signatures
124
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Unit Summary
Unit Summary
You should now be able to:
• Understand the approval process in BCM
• Understand how urgent payments can be processed in BCM
• Get an overview of the integration of BCM with Cash Management
• Understand how digital signatures are used in the approval process in BCM
• Understand how to use different signatories to release payments
• Describe how to use workflow when approving batches
• Name the advantages of using workflow
• Unterstand the main Customizing settings in BCM for approval of payments
• Understand the main Customizing settings in BCM for digital signatures
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 125
Unit Summary FSC130
126
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
Unit 4
Business Process: Status Tracking
Unit Overview
This unit will present an overview of the status tracking possibilities for payments.
Unit Objectives
After completing this unit, you will be able to:
• Understand how to use the Batch and Payment Monitor of BCM
• Have a basic understanding of how the statuses are routed from SWIFTNet
via SAP Netweaver Process Integration using the SAP Integration Package
for SWIFT
• Understand how to use the Bank Statement Monitor
• Understand the main customizing settings for the Batch and Payment Monitor
• Understand the configuration settings needed to use the Bank Statement
Monitor
Unit Contents
Lesson: Application View: Status Tracking and Bank Statement
Monitor .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128
Lesson: Customizing: Status Tracking and Bank Statement Monitor .. .134
Exercise 6: Create Bank Statement, Import it, Process it, Show it in the
Monitor .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 127
Unit 4: Business Process: Status Tracking FSC130
Lesson: Application View: Status Tracking and Bank
Statement Monitor
Lesson Overview
This lesson gives an overview of the status tracking for payments and the Bank
Statement Monitor.
Lesson Objectives
After completing this lesson, you will be able to:
• Understand how to use the Batch and Payment Monitor of BCM
• Have a basic understanding of how the statuses are routed from SWIFTNet
via SAP Netweaver Process Integration using the SAP Integration Package
for SWIFT
• Understand how to use the Bank Statement Monitor
Business Example
The accounting department wants to learn more about the different status tracking
capabilities of BCM.
Figure 61: Monitoring – Overview
128
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Application View: Status Tracking and Bank Statement Monitor
The batch and payment monitor receives status information from several sources;
the batching processsends information related to the batching rules and creation
of payment files; the approvals process sends information related to the approval
flow status; SWIFT and the bank send information related to the status of the
payment file within the communication channel.
The bank statement monitor has four traffic lights to follow the status of bank
statements received from the bank:
• Processing status
• Difference status
• Serial number status
• Reconciliation status
Figure 62: Batch and Payment Monitor
The Batch and Payment Monitor BNK_MONI is needed to have an overview of
the batch life cycle: Creation – approval – sending – confirmation – completion
(bank statement). The monitor has two levels: Initially, it shows only batches
(“headers”). On drill-down, it shows (in a new ALV screen) all the payments
(“items”) that belong to the chosen batch.
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 129
Unit 4: Business Process: Status Tracking FSC130
The monitor offers a list of parameters to select specific payments to show on the
report, the most important are:
• Batch number
• Rule ID
• Run date
• Paying company code
• Customer/vendor
• Payment method
• Currency
The monitor displays the information in tabs that fulfil certain requirements. The
user can choose to see all batches, the new ones, in approval, already approved,
sent to bank and completed (bank statement received). Additionally, it is also
possible to display the erroneous batches or payments on the exceptions tab.
Figure 63: Status Change in Batch and Payment Monitor
On transaction BNK_MONI you can trace the status history of batches and
individual payments. The status messages received from the bank need to be
defined in the system and assigned to an internal payment business transaction.
This conversion can be restricted to a company code or to a house bank, in order
to be able to trace back statuses coming from several sources, which in turn use
the same payment business transaction.
130
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Application View: Status Tracking and Bank Statement Monitor
Figure 64: Exception Handling
The concept of exception handling provides a tool to avoid that errors go
undetected. For example, if after the creation of a batch it is expected that the
approval process takes place within a day, then when that time slot is exceeded a
user can be alerted of such situation. For the notification BCM uses the central
Alert-Framework in SAP. This framework is part of the SAP Application Server.
You can define an alert category to suit your business requirements. When the
critical situation defined in the alert category arises, the system recognizes this and
sends an alert instance of this category to the recipients determined, for example
via SMS or Email.
Figure 65: Bank Statement Monitor
The bank statement monitor displays the status of bank statements from individual
house bank accounts. Information from an external bank statement is adapted
using internal bank account information from Financial Accounting, and then
different statuses are determined.
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 131
Unit 4: Business Process: Status Tracking FSC130
A bank statement that is delayed or that does not reach the monitor can be
identified with this function just as quickly as any differences occurring between
the bank statement balance and the internal G/L account balance. Any items that
are not assigned as well as differences in posting are also recognized in this way.
The bank statement monitor can determine the following statuses:
• Processing status: The processing status shows whether the bank statement
has been correctly processed. Red = The bank statement is not available, but
should be available based on your Customizing settings. Yellow = The bank
statement is available but some of the items could not be posted. Green =
The bank statement was posted correctly.
• Difference status: The difference status displays whether the account
statement has the same balance as the corresponding internal bank account.
Red = The difference amount exceeds the amount permitted. Yellow = The
difference amount is within the tolerance range for this account. Green =
There are no differences in amount - the balances are the same.
Note: In addition to the status, the difference amount permitted is also
displayed.
You specify the difference amount permitted between the bank statement and
the internal bank account for each account in Customizing. This means you can
set various difference amounts ranging from no difference to greater difference
amounts for each bank statement.
• Serial number status: The serial number status shows whether the sequence
of the last five bank statements is complete. Red = The sequence of the last
five bank statements is not complete. Green = The last five bank statements
are displayed in complete sequence.
• Reconciliation status: The reconciliation status displays whether or not
there are open items in the internal account. Red = Open items exist. Yellow
= Not all items have been posted. Green = All the items have been posted.
132
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Application View: Status Tracking and Bank Statement Monitor
Lesson Summary
You should now be able to:
• Understand how to use the Batch and Payment Monitor of BCM
• Have a basic understanding of how the statuses are routed from SWIFTNet
via SAP Netweaver Process Integration using the SAP Integration Package
for SWIFT
• Understand how to use the Bank Statement Monitor
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 133
Unit 4: Business Process: Status Tracking FSC130
Lesson: Customizing: Status Tracking and Bank
Statement Monitor
Lesson Overview
This lessons gives an overview of the customizing of the Batch and Payment
Monitor and of the Bank Statement Monitor.
Lesson Objectives
After completing this lesson, you will be able to:
• Understand the main customizing settings for the Batch and Payment Monitor
• Understand the configuration settings needed to use the Bank Statement
Monitor
Business Example
The accounting department needs to know how to personalize the traffic lights
in the settings of the Bank Statement Monitor and to map the external status
messages into internal status messages.
Monitoring Customizing – Overview
• Payment Status Management
– Map External Status to Internal Status
– Timeout for Batch Status Update
– BAdI: Implementation for Alert Categories
– BAdI: Actions after Error during Payment File Creation
• Bank Statement Monitor
– Settings for Bank Statement Monitor
The customizing of the monitoring functions in BCM is distributed in two main
customizing paths:
• Payment status management: deals with the mapping of external status
messages with internal payment business transactions as well as with the
configuration of timeouts and alerts
• Bank statement monitor
134
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Customizing: Status Tracking and Bank Statement Monitor
Figure 66: Map External Status to Internal Status
In this IMG activity, you can interpret the status codes from the external world.
Any incoming status message has a code which can be mapped to an internal
status based on a company code and house bank. If an alert needs to be triggered
for an external status code, you must define the alert. You can define the alert
category using transaction ALRTCATDEF under classification Map External
Status to Internal Status.
Example
Suppose:
• External status code = PAIN.002.001.02_RJCT<from SWIFT>
• Internal status code = BRE<Rejected by Bank>
• Alert category = BNK_REJ.
• => Ifa status message with status PAIN.002.001.02_RJCT appears, it will
be interpreted as “rejected by bank” as customized and an alert mail will
be sent to the persons responsible.
2014 © 2014SAP AG or an SAP affiliate company. All rights reserved. 135
Unit 4: Business Process: Status Tracking FSC130
Figure 67: Alert Categories
The Alert Categories are defined in Transaction ALRTCATDEF. An Alert
Category groups alerts on the basis of common properties. Every Alert is assigned
to an Alert Category
The classification of the Alert Category should be Bank Communication
Management: Alerts for Payment Status
Timeout for Batch Status Update
Use
• In this IMG activity you can specify a maximum allowed time interval
between two status updates. An alert will be triggered after the allowed
time elapses.
Activities
• Enter a maximum allowed time for a particular status transition.You can
specify a particular rule ID.
• You must enter an alert category. The classification of the alert category
should be Bank Communication Management: Alerts for Payment Status.
136
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Customizing: Status Tracking and Bank Statement Monitor
Figure 68: BAdIs
BAdI: Implementation for Alert Categories
• This Business Add-In (BAdI) enables you to realize the interface
IF_EX_BNK_PAYM_ALRT in Bank Communication Management, to
implement the logic for 'WHAT HAPPENS'defined by the users in the
Customizing of Implementation Guide (IMG). The standard system provides
a set of alerts. To create own alerts, customers must first define appropriate
Alert categories in the transaction ALRTCATDEF and then create a logic for
alert implementation in the BAdi implementation.
• For each alert category, you must create the corresponding BAdI
implementations. The alert category acts as a filter value for the BAdIs, to
perform the respective alert logic assigned to it.
Requirements
• In transaction ALRTCATDEF, you must define appropriate ALERT
CATEGORY that you want to use.
BAdI: Actions after Error during Payment File Creation
• In this IMG activity, you can define the actions you must take if the payment
file creation process ended with an error.
Figure 69: Customizing - Bank Statement Monitor
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 137
Unit 4: Business Process: Status Tracking FSC130
Activities
• Choose New Entries.
• To ensure the system selects and displays the relevant account in the monitor,
you need to enter the company code, house bank and house bank account.
• Activate the status you wish to use to define the account and to display the
account in the monitor.
– Processing status
– Difference status
– Serial number status
– Reconciliation status
• In the Interval and Interval Unit fields, define the time period in which you
want to receive a bank statement for this account. (This setting is taken into
account when determining the processing status.)
• Specify where the account should be displayed in the bank statement monitor.
• When determining the difference status, if you want to define a tolerance
between the bank statement balance and the internal general ledger account
balance, then enter a specific difference amount.
• Save your entries.
Note: The account currency is determined automatically from the account
data.
Example:
You want to display the GIRO account at the top of the monitor for the house bank
DB in company code 0001. You also want to display the account status. You
wish to receive a new bank statement daily. The bank statement balance and the
internal account balance must be the same.
Enter the following data:
• Company code: 0001
• House bank: DB
• House bank account: GIRO
• Select all bank statuses
• Interval: 1
• Interval unit: calendar days
• Define a factory calendar
• Position: 001
138
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Customizing: Status Tracking and Bank Statement Monitor
Figure 70: Customizing - Bank Statement Monitor II
Interval for Expected Bank Statements
Use: Here you determine the intervals in which the bank statements are to be
expected for the corresponding bank account.
• Dependencies
You can use the Processing Status indicator to check whether the statements have
entered the bank statement monitor.
Example
• Bank accounts are usually created on a daily basis for bank accounts with
daily postings.
• Enter 1 as the interval and choose Calendar Days as the interval unit.
Position- Display Item in Bank Statement Monitor
The display position of the account in the bank statement monitor.
• Use: Here you determine the position at which the bank statement for this
account should be displayed in the monitor.
Example
If you want to display an account at the top of the bank statement monitor then
you need to enter the number '1'.
Difference Amount Permitted in Account Currency
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 139
Unit 4: Business Process: Status Tracking FSC130
The difference in amount permitted between the bank statement end balance and
the G/L account balance.
• Use: You enter a difference amount for an account if you permit the end
balance on the bank statement to differ from the balance on the statement
date for the G/L account. The currency displayed is the account currency
set up for the house bank account. If an alternative account number has
been determined, the difference amount is interpreted in the currency that is
specified on the bank statement for the alternative account.
140
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Customizing: Status Tracking and Bank Statement Monitor
Exercise 6: Create Bank Statement, Import
it, Process it, Show it in the Monitor
Exercise Objectives
After completing this exercise, you will be able to:
• Create, import and process a Bank Statement
• To understand the information presented on the Bank Statement Monitor
Business Example
The accounting department needs to know whether an account statement has
been processes correctly.
User ID: FSACC-##
Task 1:
Create customer master data.
1. Create a customer master record called Cust## in your company code.
Replace ## with your company code. Copy Customer10 from Company
Code 1000.
Task 2:
Configure the Bank Statement Monitor.
1. Add your house bank 1000 with the Account ID 1000 to the monitor. Copy
the entry house bank DB with the Account ID GIRO in company code 0001.
Task 3:
Simulate postings and a bank statement.
1. Run the report RFEBKATX to create a bank statement from your house
bank and an open item for your customer. Choose any amount for the bank
statement and another amount for the invoice.
Task 4:
Import your bank statement.
1. Import the bank statement you have created.
Continued on next page
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 141
Unit 4: Business Process: Status Tracking FSC130
Task 5:
Display the bank statement monitor.
1. Run the bank statement monitor and analyze the display.
Task 6:
Reprocess your bank statement.
1. Reprocess your bank statement and post the difference on your customer
account.
Task 7:
Display the bank statement monitor.
1. Run the bank statement monitor again and analyze the display. What did
change?
142
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Customizing: Status Tracking and Bank Statement Monitor
Solution 6: Create Bank Statement, Import
it, Process it, Show it in the Monitor
Task 1:
Create customer master data.
1. Create a customer master record called Cust## in your company code.
Replace ## with your company code. Copy Customer10 from Company
Code 1000.
a) Accounting → Financial Accounting → Accounts Receivable →
Master Records → Create
Enter the following data:
Field Name or Data Type Values
Customer Cust##
Company Code AC##
Reference → Customer CUSTOMER10
Reference → Company Code 1000
Confirm.
Save.
Continued on next page
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 143
Unit 4: Business Process: Status Tracking FSC130
Task 2:
Configurethe Bank Statement Monitor.
1. Add your house bank 1000 with the Account ID 1000 to the monitor. Copy
the entry house bank DB with the Account ID GIRO in company code 0001.
a) In the IMG select: Financial Supply Chain Management → Bank
Communication Management → Bank Statement Monitor →
Settings for Bank Statement Monitor
Copy the following entry:
Field Name or Data Type Values
Company Code 0001
House Bank DB
Account ID GIRO
…and enter the following values:
Field Name or Data Type Values
Company Code AC##
House Bank 1000
Account ID 1000
Position ## +2
All other values can remain unchanged.
Save your entries.
Task 3:
Simulate postings and a bank statement.
1. Run the report RFEBKATX to create a bank statement from your house
bank and an open item for your customer. Choose any amount for the bank
statement and another amount for the invoice.
a) In the SAP menu use the transaction: SA38
Enter the following data:
Field Name or Data Type Values
Program RFEBKATX
Continued on next page
144
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Customizing: Status Tracking and Bank Statement Monitor
Click on Execute.
Enter the following data:
Field Name or Data Type Values
Download to PC Tick box
Statement file N:\statement##.txt
Line item file N:\lineitem##.txt
Company Code AC##
House Bank (ID) 1000
Account ID 1000
Statement Date Today
Invoice Date Today minus 2 days
Posting method Display all posting
screens
Customers to be posted to Cust##
Number of open items 1
First Amount 400
Document type SA
All other values can remain unchanged.
Execute the program.
Navigation:
On the following screen click Enter.
On the posting screen for the customer item. “Enter G/L account
document:” Enter a higher invoice amount than before (in the field
“Amount” for example 500). Enter.
Confirm the following screens with “Enter” until the document is
posted.
Continued on next page
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 145
Unit 4: Business Process: Status Tracking FSC130
Task 4:
Import your bank statement.
1. Import the bank statement you have created.
a) Accounting → Financial Accounting → Banks → Incomings →
Bank statement → Import
Enter the following data:
Field Name or Data Type Values
Import data Tick box
Statement file N:\statement##.txt
Line item file N:\lineitem##.txt
All other values can remain unchanged.
Execute.
On the following screen click Enter.
Task 5:
Display the bank statement monitor.
1. Run the bank statement monitor and analyze the display.
a) Accounting → Financial Supply Chain Management → Bank
Communication Management → Status Management → Bank
Statement Monitor
Enter the following data:
Field Name or Data Type Values
Company Code AC##
House Bank 1000
Account ID 1000
Statement Date Today
Execute.
Continued on next page
146
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Customizing: Status Tracking and Bank Statement Monitor
Task 6:
Reprocess your bank statement.
1. Reprocess your bank statement and post the difference on your customer
account.
a) Accounting → Banks → Incomings → Bank Statement →
Postprocess
A variant screen will pop up.
Enter the following data:
Field Name or Data Type Values
Difference posting type Partial payment
Enter the following data:
Field Name or Data Type Values
Company Code AC##
Execute.
Navigation:
Double click on the amount with the red icon.
On the frame below double click on the field remainder.
The system will automatically calculate the remainder amount and set
it per default to “partial payment”.
Select Enter.
Click on Post.
Continued on next page
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 147
Unit 4: Business Process: Status Tracking FSC130
Task 7:
Display the bank statement monitor.
1. Run the bank statement monitor again and analyze the display. What did
change?
a) Accounting → Financial Supply Chain Management → Bank
Communication Management → Status Management → Bank
Statement Monitor
Enter the following data:
Field Name or Data Type Values
Company Code AC##
House Bank 1000
Account ID 1000
Statement Date Today
Execute.
What did change?
The Reconciliation Status is green now.
148
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Customizing: Status Tracking and Bank Statement Monitor
Lesson Summary
You should now be able to:
• Understand the main customizing settings for the Batch and Payment Monitor
• Understand the configuration settings needed to use the Bank Statement
Monitor
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 149
Unit Summary FSC130
Unit Summary
You should now be able to:
• Understand how to use the Batch and Payment Monitor of BCM
• Have a basic understanding of how the statuses are routed from SWIFTNet
via SAP Netweaver Process Integration using the SAP Integration Package
for SWIFT
• Understand how to use the Bank Statement Monitor
• Understand the main customizing settings for the Batch and Payment Monitor
• Understand the configuration settings needed to use the Bank Statement
Monitor
150
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
Unit 5
SAP Integration Package for SWIFT
Unit Overview
This unit gives an overview of SWIFT, SAP Netweaver Process Integration, and
SAP Integration Package for SWIFT.
Unit Objectives
After completing this unit, you will be able to:
• Understand the SWIFT concept, benefits and features
• List the connectivity options for corporates to join SWIFT
• Describe the main features of SAP Netweaver Process Integration
• Get an overview of the architecture of SAP Netweaver Process Integration
• Explain the concept of SAP Integration Package for SWIFT
• Get an overview of the architecture of SAP Integration Package for SWIFT
Unit Contents
Lesson: Overview SWIFT... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152
Lesson: Overview SAP Netweaver Process Integration... . . . . . . . . . . . . . . . .162
Lesson: Overview SAP Integration Package for SWIFT... . . . . . . . . . . . . . . . .168
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 151
Unit 5: SAP Integration Package for SWIFT FSC130
Lesson: Overview SWIFT
Lesson Overview
This lessons gives an overview of SWIFT
Lesson Objectives
After completing this lesson, you will be able to:
• Understand the SWIFT concept, benefits and features
• List the connectivity options for corporates to join SWIFT
Business Example
The CFO would like to learn about the possibilities to connect the company to the
SWIFT network
Figure 71: What is SWIFT?
SWIFT is the financial industry-owned co-operative supplying secure,
standardised messaging services and interface software to 7,800 financial
institutions in more than 200 countries. SWIFT's worldwide community
includes banks, broker/dealers and investment managers, as well as their market
infrastructures in payments, securities, treasury and trade.
152
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Overview SWIFT
SWIFT is a combination of three things:
• a community of financial institutions;
• a messaging platform of the highest security and reliability;
• a standards setting body for electronic financial messaging.
Vision
• To be the global financial communitys foremost messaging infrastructure
that is lowest risk and highest resilience.
Mission
• SWIFT is a worldwide community of financial institutions whose purpose
is to be the leader in communications solutions enabling interoperability
between its members, their market infrastructures and their end-user
communities.
SWIFT2010 strategy
• The SWIFT2010 strategy is to achieve “more, together” by (1) increasing
SWIFTs share of the total financial messaging space, (2) enhancing SWIFTs
traditional messaging to provide highervalue interoperability services, and
(3) focusing exclusively on the cooperative space as it evolves under Board
guidance.
• Key SWIFT2010 focus areas are to:
• expand reach, including corporate access;
– support European integration;
– extra attention to emerging markets;
– improve automation in securities and derivatives.
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 153
Unit 5: SAP Integration Package for SWIFT FSC130
Figure 72: Why SWIFT?
The world of corporate treasurers has undergone significant changes over the
last years.
An ever more competitive, global, and regulated market is forcing treasurers
to rethink the way they operate. To do this, they need to respond to several
challenges such as:
• To improve efficiency and reduce costs. This includes providing a better
visibility of funds.
• To further reduce operational risk such as the risk of disruption and the risk
of human failure.
• To strengthen security by protecting against internal and external fraud.
• To comply with an ever stricter regulatory framework that aims to improve
transparency towards investors (for example, Sarbanes-Oxley).
To address these challenges, treasurers need to improve efficiency and overall
control. Because of this, they are increasingly trying to centralise and automate
their operations. However, in doing so, they still face the challenge of different
platforms and communication standards when trying to establish electronic
connections with their banks. Clearly, this situation is not ideal as these
environments are costly to maintain and operate. In addition, they are a source of
risk because their heterogeneity is more difficult to control (for example, weak
business continuity plans due to complexity, and lack of security discipline due
to multiplicity of passwords).
154
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Overview SWIFT
Figure 73: SWIFTNet
SWIFTNet is SWIFT IP-based Messaging Platform that comprises a portfolio of
products and services, enabling:
• Secure real-time transfers
• Store and forward transfers
• File transfer and browsing capability
SWIFTNet provides a complete range of end-to-end SWIFT Solutions covering
every aspect of financial services processing (Markets):
• Payments and cash management
• Treasury and derivatives
• Securities
• Trade Services
• Clearing and settlement, Custody services, Reporting
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 155
Unit 5: SAP Integration Package for SWIFT FSC130
Figure 74: SWIFTNet Messaging Services
SWIFTNet FIN is a messaging service which enables the transmission of
standarized messages in “SWIFT language” or MT Messages. MT stands for
Message Type.
• Example: MT 101 “Request for Transfer”, MT 940 “Customer Statement”
• SWIFTNet FIN works on “store and forward” mode: correspondents do not
need to be online to receive at the time of transmission
• Security:
– BKE (Bilateral Key Exchange) and Smart Card security: proprietary
smart card and smart card readers. Security will be enhanced in the
future to offer the same level of protection, but based on SWIFTNet
PKI (Public Key Infrastructure).
– Controlled for compliance with Closed User Group rules
• Message Validation: SWIFTNet FIN supports validation with MT standards
• Non repudiation: In case of dispute, SWIFT is able to confirm that message
exchange took place.
156
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Overview SWIFT
SWIFTNet FileAct is a secure, reliable and cost-effective way to transfer bulk
files in different formats to SWIFT correspondents
• Cost effective because pricing is “volume based”, enables reuse of SWIFT
infrastructure for connectivity and interfaces. The more SWIFT Net FileAct
files you send, the less you pay per file.
• Supports any character data types, any content structure: SWIFT formats,
domestic formats, proprietary formats, file size up 250Mbytes
• Non repudiation is optional
• Files can be for:
– Bulk payment processing
– Transmission of Cheque images
– Securities reporting
– Central Bank reporting / intra-institution reporting
• Usage most efficient when transferring “large batches of messages” such as
bulk payment files or very large reports with operational data
• Supports both real-time and store-and-forward communication
SWIFTNet InterActMessages are formatted with the new XML-based SWIFT
MX standards
• Directly embeds more recent technology standards: XML and PKI
• It is the service to use in business areas that benefit from new XML-based
MX standards
• In addition to “store and forward”, Inter Act messages can be also real time:
where instruction or confirmation expected real time
• Features: SWIFTNet PKI, Closed User Group control, Message Validation
of XML-based SWIFT standards
• Optional Features: Urgent flag, Delivery Notification (for “store and
forward”), non repudiation on emission and reception
SWIFTNet Browse: browse securely on financial web sites / online portals
available on SWIFTNet, using standard internet technologies and protocols such
as HTTP-S and HTML
• Combines the user friendliness of web technology with the security features
offered by SWIFTNet
• This is enabled by SWIFTNet Browse, complemented with SWIFTNet
InterAct and FileAct
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 157
Unit 5: SAP Integration Package for SWIFT FSC130
Figure 75: Connectivity Options for CorporatesTreasury Counterparties
This category allows a corporate to exchange treasury deal confirmations (spots,
forwards, currency options, derivatives) with any SWIFT member, with no need
to be register in a closed group. In other words, there are no limitations in terms
of numbers of counterparties. It is the nature of the information exchanged with
these counterparties which is restricted, to confirmations of FX/MM/IR deals
(MT3xx Messages).
To apply as a Treasury Counterparty (TRCO), the corporate needs to be sponsored
by 8 banks which are members of SWIFT.
Figure 76: Connectivity Options for CorporatesMember Administered
Closed User Groups (MA-CUGS)
158
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Overview SWIFT
In this category, a corporate registers in a “Closed User Group” (CUG) that is
managed by its bank.
Within the CUG, a corporate can communicate only with its bank. Corporate
to corporate communication is not allowed. In contrast with the Treasury
Counterparty category, any type of information can be exchanged between the
corporate and the bank. Use MA-CUG membership category (also calledMCCO)
if cash and liquidity management is the objective.
Figure 77: Connectivity Options for Corporates SCORE
SCORE is also an closed user group but administered directly by SWIFT. A
company which makes part of SCORE can inmediately exchange messages with
all SCORE-CUG participant financial institutions with no need to arrange separate
agreements with each bank. SCORE covers all corporates messaging needs for
treasury, cash management and security transactions.
To be eligible for SCORE, a company must be listed on a regulated stock exchange
of a country which is a member of the Financial Action Task Force (FATF).
Subsidiaries can also join under this scheme provided that they are majority
owned by a eligible company, duly incorporated, in good financial standing and
subject to regular audits in accordance with international accounting standards
by an independent firm.
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 159
Unit 5: SAP Integration Package for SWIFT FSC130
Connectivity Options for CorporatesOther
• Alliance Lite
– Secure and low cost access to SWIFT
– Easy to use
– Rich funcionality
• Service Bureaux
– Indirect connection to SWIFT via third party services
Alliance Lite
New internet access service that provides easy, secure and low cost access
to SWIFT. The only requirements to use itare an internet connection and a
SWIFT-issued security token. It is designed for companies that send and receive
up to 200 items a day. An item is a SWIFT MT message or a 100 kb chunk of
a fileact file.
Functionalities:
• Multibank payment initiation
• Cash reporting
• Foreign exchange transactions
Service Bureaux
With this model the company outsources the complete SWIFTNet connectivity
to an external party. This means that the corporate shares the SWIFTNet
infrastructure with other users. The service bureau has to ensure that the users
are strictly segregated from each other and that no user can see or alter data
belonging to another.
• The list of existing service bureaux and more information on these
organisations can be obtained at www.swift.com/index.cfm?item_id=42513.
160
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
http://www.swift.com/index.cfm?item_id=42513
FSC130 Lesson: Overview SWIFT
Lesson Summary
You should now be able to:
• Understand the SWIFT concept, benefits and features
• List the connectivity options for corporates to join SWIFT
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 161
Unit 5: SAP Integration Package for SWIFT FSC130
Lesson: Overview SAP Netweaver Process Integration
Lesson Overview
This lesson gives an overview of SAP Netweaver Process Integration.
Lesson Objectives
After completing this lesson, you will be able to:
• Describe the main features of SAP Netweaver Process Integration
• Get an overview of the architecture of SAP Netweaver Process Integration
Business Example
The IT department would like to know how to integrate different components that
do not make part of the SAP family of products.
Figure 78: The SAP Process Integration Platform
SAP NetWeaver Exchange Infrastructure provides you with a platform within
SAP NetWeaver that enables different interfaces to communicate using a standard
technology.
The Integration Platform of SAP NetWeaver Process Integration
162
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Overview SAP Netweaver Process Integration
SAP NetWeaver Exchange Infrastructure is an integration technology containing
the following possible partners and scenarios:
• SAP and non-SAP applications
• Integration scenarios within the company intranet (application to application
or A2A)
• Integration scenarios between business partners (B2B)
• Cross-component Business Process Management
As an integral part of SAP NetWeaver, SAP PI is based on an open architecture
and uses open standards (in particular from the XML and Java environments).
The services provided by SAP PI are indispensable in a heterogeneous and
complex system landscape:
• Options for defining interfaces centrally
• Configuration options for controlling the message flow
• Options for transforming message content between the sender and receiver
• A runtime infrastructure for exchanging messages
• Options for modeling and executing processes
The focus of SAP PI is message-based communication using HTTP.
Application-specific content is transferred from the sender to the receiver using
messages in a freely-definable XML schema using the Integration Engine.
Processing of the messages on the Integration Server is stateless, that is, a message
arrives, the receiver or receivers are determined, and the message is forwarded
immediately.
Figure 79: Structure of Messages in SAP NetWeaver Process Integration
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 163
Unit 5: SAP Integration Package for SWIFT FSC130
The properties of the message itself are contained in the message header, for
example the sender, which is used later to determine the receiver. The actual
business data is contained in the payload. You can also attach any number of
attachments (for example pictures, text documents, and so on) to the message. The
message header and the payload are in XML format.
XML is the standard exchange format in the Internet. Before this standard was
established, mainly proprietary exchange formats were used, which complicated
communication in heterogeneous system landscapes. There are standards and
tools that make it easier to use XML. You can use them to define mappings that
are necessary because of different structures in messages; the tools enable you to
evaluate conditions, for example, to determine the receivers of messages.
Figure 80: Connecting Different Systems to SAP NetWeaver Process
Integration
Connecting Different Systems to SAP NetWeaver Process Integration
As you already know, you can use SAP NetWeaver Process Integration to integrate
any SAP and non-SAP systems.
If the system in question is a non-SAP system or if you want to use existing
interfaces from an SAP system with Basis Release 4.6 or lower with SAP PI,
you need adapters to connect to the Integration Server. SAP provides a number
of adaptors for this purpose. (IDoc, File, RFC, Database Adaptor, Mail, SOAP,
RosettaNet Adaptor, ...)
The sender system provides data in a document format, for example, IDoc,and
sends it to the adapter by means of a protocol. The adapter transforms the
document to the SAP PI format and forwards it to the Integration Server by using
HTTP(S). In the configuration you specify which adaptor the receiver is to use
to receive the message. The Integration Server sends the message to the relevant
adapter, which in turn converts it to the protocol of the receiver and finally sends
it to the receiver.
164
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Overview SAP Netweaver Process Integration
If you want to use SAP XI to realize a cross-system integration process and
provided the systems involved are based on SAP Web AS 6.20 or higher, you can
use the new SAP PI programming model. You define your platform-independent
interface descriptions in the Integration Repository and then, using this
description, you can generate proxies in the various application systems for Java
applications or SAP systems. In the application system proxies represent the
interface from the Integration Repository.
From a technical perspective, proxy objects are classes and methods in a
programming language (ABAP or Java) that can generate and process messages
for a file format defined in the Integration Repository.
Figure 81: Component Overview
Architecture of SAP NetWeaver Exchange Infrastructure
Within SAP NetWeaver, SAP NetWeaver Exchange Infrastructure has the task of
connecting different versions of different vendor systems (both SAP and non-SAP
systems) implemented on different platforms (ABAP, Java, and so on).
SAP NetWeaver Exchange Infrastructure comprises the following components:
• You define the systems in your system landscape in the SLD.
• Enter a platform-independent description of all the required interfaces in
your company in the Integration Repository at design time. If the data to be
transferred is not all in the same format, you must use this description in the
Integration Repository to also define mappings.
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 165
Unit 5: SAP Integration Package for SWIFT FSC130
This does not yet affect any of your systems or processes.
• At configuration time, you select the components, interfaces, and mappings
defined in the Integration Repository that are required for the integration
processes in your system landscape and assign them to each other (logical
routing).
The result is stored in the Integration Directory.
• The application specific contents are transferred from the sender to the
receiver by means of messages in a freely-definable XML schema. The
structure of a message is determined by the data structures in the interface
used (IDoc, file, database, and so on).
• The Integration Engine on the Integration Server evaluates the configuration
in the Integration Directory when an inbound message is received at runtime.
It uses the configuration data to determinethe receiver or receivers of the
message, maps the inbound message to the interface structure of the receiver,
and then forwards it for further processing. The Integration Server is the
central communication and distribution machine for XML messages.
Both the Integration Repository and the Integration Directory are written in Java
and must be managed with the appropriate Java administration tools.
From a technical point of view, SAP NetWeaver Exchange Infrastructure is based
on a SAP NetWeaver Application Server (ABAP and Java); however, you must
install this server in addition to SAP NetWeaver Exchange Infrastructure. A
detailed SAP installation guide is available for this purpose.
166
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Overview SAP Netweaver Process Integration
Lesson Summary
You should now be able to:
• Describe the main features of SAP Netweaver Process Integration
• Get an overview of the architecture of SAP Netweaver Process Integration
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 167
Unit 5: SAP Integration Package for SWIFT FSC130
Lesson: Overview SAP Integration Package for SWIFT
Lesson Overview
This lesson gives an overview of SAP Integration Package for SWIFT.
Lesson Objectives
After completing this lesson, you will be able to:
• Explain the concept of SAP Integration Package for SWIFT
• Get an overview of the architecture of SAP Integration Package for SWIFT
Business Example
The IT department would like to know how to integrate SWIFT with Bank
Communication Management.
Figure 82: Architecture Overview SAP Integration Package for SWIFT
The Integration Package for SWIFT enables the communication with the SWIFT
products SWIFTAlliance Access (SAA) and SWIFTAlliance Gateway (SAG).
SWIFTAlliance Access is a messaging interface which enables the automated
access to SWIFTNet FIN (MT) and SWIFTInteract (for MX messages).
168
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Overview SAP Integration Package for SWIFT
SWIFTAlliance Gateway is a communication interface which offers a single
window on all SWIFTNet services, streamlining operations, increasing security
and resilience.
Figure 83: Architecture Overview in SAP NetWeaver Process Integration (PI)
1. ERP Service Enabling Component containing the SAP Interfaces. For
example: CollectivePaymentOrderRequest
2. Mapping between PI Interfaces and ISO20022 interfaces
For example: CollectivePaymentOrderRequest is mapped to
CustomerCreditTransferInitiation
3. Component containing the ISO20022 Interfaces
4. Component containing enhancements for the PI File Adapter (security, file
envelope)
Note: “SWIFT” Adapter refers to Enhancements of the PI File
Adapter.
The “SAP Integration Package for SWIFT” does the packaging into a SWIFT
conform envelope.
For FIN this is referred toSWIFT XMLv2.For FileAct it is worth mentioning that
an accompanying Parameter file is created (containing e.g. Local Authentication
information and RequestType details, to allow specific routing).
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 169
Unit 5: SAP Integration Package for SWIFT FSC130
SAP Integration Package for SWIFT: Availability
• Tight SAP Integration
– SAP Integration Package for SWIFT will be available for SAP R/3
4.6C and upwards, requiring SAP NetWeaver Process Integration 7.0
(formerly SAP XI)
– Support of various Status Messages in conjunction with SAP Bank
Communication Management (prerequisite: SAP ERP 6.0 (2005))
SAP NetWeaver Process Integration 7.0 (former SAP Exchange Integration XI) is
a prerequisite for the implementation of SAP Integration Package for SWIFT.
The SAP Integration Package for SWIFT can be integrated with R/3 releases
starting with R/3 4.6C. The adoption of the Payment Medium Workbench is a
requirement (it does not support the classic payment programs RFFO*)
The integration with SAP In-House Cash is also possible
SAP Bank Communication Management is available starting with SAP ERP 6.0
Ehp 2
170
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Lesson: Overview SAP Integration Package for SWIFT
Lesson Summary
You should now be able to:
• Explain the concept of SAP Integration Package for SWIFT
• Get an overview of the architecture of SAP Integration Package for SWIFT
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 171
Unit Summary FSC130
Unit Summary
You should now be able to:
• Understand the SWIFT concept, benefits and features
• List the connectivity options for corporates to join SWIFT
• Describe the main features of SAP Netweaver Process Integration
• Get an overview of the architecture of SAP Netweaver Process Integration
• Explain the concept of SAP Integration Package for SWIFT
• Get an overview of the architecture of SAP Integration Package for SWIFT
172
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
FSC130 Course Summary
Course Summary
You should now be able to:
• Describe in detail the processes of SAP Bank Communication Management
• Learn the configuration steps of BCM
• Define the system settings needed to implement BCM
• Describe how BCM connects to SWIFT through the SAP Integration
Package for SWIFT
Related Information
•
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 173
Course Summary FSC130
174
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
Appendix 1
Data Sheet
The following table should help you have a general overview of the required
information on the exercises:
Your group number: _ _
Company Code: AC_ _
Users: FSACC-_ _and FSAPP-_ _
Reserved ID on BCM: BC_ _
In-
voice
Vendor Amount Doc.
Number
Paym.
Method
Paym.
Run
Batch
Number
Paym.
Doc #
1 T-F00K00200 5 BC_ _1
2 T-F00K004000 7 BC_ _2
3 T-F00L00 8000 5 BC_ _2
4 T-F00M0010000 5 BC_ _1
Merge ID of Erroneous Merge: _____________
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 175
Appendix 1: Data Sheet FSC130
176
© 2014 SAP AG or an SAP affiliate company.
All rights reserved. 2014
Feedback
SAP AG has made every effort in the preparation of this course to ensure the
accuracy and completeness of the materials. If you have any corrections or
suggestions for improvement, please record them in the appropriate place in the
course evaluation.
2014 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 177
	toc
	Icons in Body Text
	toc
	SAP Bank Communication Management – Fundamentals
	Lesson:
	Lesson:
	PMW Advantages
	Easier to maintain and to extend. Replaces approx. 60 Classic Pa
	Lesson:
	Exercise 1: Master Records for Vendors, Posting Invoices, Paymen
	Business Process: Batching in BCM
	Lesson:
	Exercise 2: Batching of Payment Orders
	Exercise 3: Free Form Payment (optional)
	Lesson:
	Exercise 4: Customizing Batching Rules in BCM
	Business Process: Approval Process in BCM
	Lesson:
	Approval Reporting
	Take Over from Current Processor
	Exercise 5: Approval Process in BCM
	Lesson:
	Workflow Concept
	Workflow covers all aspects of the process
	Considerations for a smooth Workflow in BCM
	Should any problems arise in the configuration of the Workflow i
	Business Process: Status Tracking
	Lesson:
	Lesson:
	Monitoring Customizing – Overview
	Payment Status Management
	Exercise 6: Create Bank Statement, Import it, Process it, Show i
	SAP Integration Package for SWIFT
	Lesson:
	Alliance Lite
	Lesson:
	Lesson:
	Tight SAP Integration