Table of Contents

1 Basic Settings ........................................................................................................................................ 2

1.1 Basic Settings for Approval ........................................................................................................... 2
2 Payment Grouping ................................................................................................................................ 2
2.1 Rule Maintenance ......................................................................................................................... 2
2.2 Additional Criteria for Payment Grouping .................................................................................... 4
2.3 Payment Medium: Create/Assign Selection Variants – BNK_OBPM4 .......................................... 5
2.4 Create Payment Medium Formats ................................................................................................ 6
2.5 Edit Variants .................................................................................................................................. 7
2.6 Creation of Variant – SAPFPAYM .................................................................................................. 7
3 Payment Status Management .............................................................................................................. 8
3.1 Define Directories for File Upload................................................................................................. 8
3.2 Map External Status to Internal Status ......................................................................................... 9
3.3 BAdI: Splitting an Imported File .................................................................................................. 10
4 Bank Statement Monitor .................................................................................................................... 11
4.1 Settings for Bank Statement Monitor ......................................................................................... 11
5 Release Strategy.................................................................................................................................. 13
5.1 Mark Rules for Automatic Payments (No Approval)................................................................... 13
5.2 Change and Release .................................................................................................................... 13
5.2.1 Assign Role to Release Steps ............................................................................................... 13
5.3 Additional Release Steps ............................................................................................................. 14
5.3.1 Define Release Procedure ................................................................................................... 14
5.3.2 Assign Role to Release Steps ............................................................................................... 15
5.3.3 Assign Workflow Template to Release Procedure .............................................................. 16
1 Basic Settings

1.1 Basic Settings for Approval

Use
In this IMG activity, you can define the default currency, resubmission date and whether or not a
signature is needed for payments.
Requirements
Default 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).
Default resubmission date
For resubmission of payments, the resubmission date from the current date can be set.
Sign log
If the check box is marked, the signature popup appears before the payment batch is approved.
Example
Default Currency = EUR
Default resubmission days = 5
--> The default resubmission date = the current date + 5

2 Payment Grouping

2.1 Rule Maintenance

Use
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 on 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.
Activities
Make the settings you require.
Example
Suppose you define rule YCHQ_TRNSF priority 0 and YAMNT_MED priority 1. If a payment satisfies the
criteria for batching, rule YCHQ_TRNSF is selected because of its higher priority.
2.2 Additional Criteria for Payment Grouping

Use
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. Two grouping fields are provided, one of
which you select for the batching.
Activities
Make the settings you require.
Example
Suppose you select VALUT field for batching rule YCHQ_TRNSF. This means that if a batching rule
YCHQ_TRNSF is selected, payments are further batched by the date, so all payments belonging to
YCHQ_TRNSF and of the same date will form a batch.
2.3 Payment Medium: Create/Assign Selection Variants – BNK_OBPM4

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.

Activities

1. 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.

2. Use the possible entries button (F4) to display the existing variants in the Selection variants
field. Select the required variant.

3. You can create an appropriate variant by choosing Variants -> Edit variants, or via the icon.
When you select this function, the selection screen of 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 via Back.

4. Save the selection variant assignment.

5. Transport the selection variant assignment by choosing Variants -> Transport All.
2.4 Create Payment Medium Formats

Business TransactionsOutgoing PaymentsAutomatic Outgoing PaymentsPayment MediaMake

Settings for Payment Medium Formats from Payment Medium WorkbenchCreate Payment Medium
Formats
2.5 Edit Variants

2.6 Creation of Variant – SAPFPAYM

3 Payment Status Management

3.1 Define Directories for File Upload

Use

In this Customizing activity, you create directories for the following files:

 Import files

 Archive files

 Error files

You need these directories to automatically upload ISO 20022 CustomerPaymentStatusReport XML
files from the application server directory to update the status of payment batches that were created
in SAP Bank Communication Management.

Requirements

You use report RBNK_IMPORT_PAYM_STATUS_REPORT for the automatic upload.

See also

For more information about the upload, see the documentation for report
RBNK_IMPORT_PAYM_STATUS_REPORT.
3.2 Map External Status to Internal Status
Use
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.
Activities
Make the settings you require.
Example
Suppose:
External status code = PAIN.002.001.02_RJCT<from SWIFT>
Internal status code = BRE<Rejected by Bank>
Alert category = BNK_REJ.
=> If a 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.
3.3 BAdI: Splitting an Imported File
Use

This Business Add-In (BAdI) is used in the Bank Communication Management (FIN-FSCM-BNK)
component. You must implement this BAdI if a file to be imported contains several XML
CustomerPaymentStatusReport (PSR) files.

The BAdI method SPLIT_PSR_FILE is called directly before the system processes the read file, splitting
it into several XML CustomerPaymentStatusReport (PSR) files. This is necessary because the XSL
transformation in the next processing step of the upload can only deal with one PSR file at a time.

Requirements

You use report RBNK_IMPORT_PAYM_STATUS_REPORT for the automatic upload.

Standard settings

For more information about the standard settings (filters, single or multiple uses), see the Enh. Spot
Element Definitions tab in the BAdI Builder (transaction SE18).

Example

You can find an example implementation (CL_BNK_SPLIT_FILE_EXAMPLE) in the BAdI Builder on the
Enh. Sport Element Definitions tab in the Implementation Example Classes section.

See also

For more information about the Upload Payment Status Report, see
RBNK_IMPORT_PAYM_STATUS_REPORT.

For information about implementing BAdIs as part of the enhancement framework, see SAP Library for
SAP NetWeaver Platform on SAP Help Portal at http://help.sap.com/nw_platform. Choose a release
and then Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View ->
Application Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP
Customer Development -> Enhancement Framework.
4 Bank Statement Monitor

4.1 Settings for Bank Statement Monitor

Use

In this IMG activity you make the required settings for the house bank accounts that you want to view
using the bank statement monitor.

Activities

1. Choose New Entries.

2. To ensure the system selects and displays the relevant account in the monitor, enter the
company code, house bank, and house bank account.

3. 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

4. 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.)

5. Specify where the account should be displayed in the bank statement monitor.

6. 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.
 Note: The account currency is determined automatically from the account data.

7. Save your entries.

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 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

Further notes

For more information, see the documentation on the Bank Statement Monitor in the SAP Library. To
do this, choose Financial Supply Chain Management -> Bank Communication Management.
5 Release Strategy

5.1 Mark Rules for Automatic Payments (No Approval)

5.2 Change and Release

5.2.1 Assign Role to Release Steps

Use
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.
Standard settings
SAP does not supply any standard roles for Bank Communication Management.
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 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.
4. 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.
c) Choose Continue.
d) Choose Change.
This brings you to the Standard Role: Change screen.
For more information on changing standard roles, refer to the documentation on the SAP
Business Worklfow in the SAP Library. Choose Basis Components -> Business Management
-> SAP Business Workflow -> Role Documentation, or on the corresponding screens
choose Help -> Application Help.
Via the area menu
Choose Tools -> ABAP Workbench -> Development -> Workflow -> Definition Tools ->
Standard Roles -> Change.
This brings you to the Standard Role: Change screen.
For more information on changing standard roles, refer to the documentation on the SAP
Business Workflow in the SAP Library. Choose Basis Components -> Business Management
-> SAP Business Workflow -> Role Documentation, or on the corresponding screens,
choose Help -> Application Help.
Note: When defining rules, make sure there is an 'And' link between the conditions you
define when entering values.
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.
5. Save your entries.

5.3 Additional Release Steps

5.3.1 Define Release Procedure

Use
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.
Requirements
You have made the standard settings for the SAP Business Workflow in the Basis Customizing settings
by choosing Business Management -> SAP Business Workflow -> Maintain Standard Settings for SAP
Business Workflow .
Standard settings
The standard setting supplied for the release objects is no release (radio button is never in the group
frame release).
Activities
1. Choose a radio button in the group frame Release.
If you choose always, you must also select a release procedure for 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. Go back.
4. 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.

5.3.2 Assign Role to Release Steps

5.3.3 Assign Workflow Template to Release Procedure