This note contains the missing IMG-Documentation of the Bank Communication Management (BCM):

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.

Requirements

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

Text is available in the system.

3 Payment Status Management

3.1 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.2 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.

3.3 BAdI: Implementation for Alert Categories

Use

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.

Activities

1. Choose the menu path 'Tools -> ABAP Workbench -> Utilities -> Business Add-Ins -> Implementation'. Alternatively, enter the transaction SE19.

2. Specify a name for the implementation and choose Create. A dialog box appears. Enter the name of the Business Add-In BNK_BADI_PAYM_ALRT . The maintenance screen for the Business Add-In appears.

OR

Alternatively, enter the Business Add-In definition transaction SE18 to reach its implementations. The menu contains an entry Implementation, which you can use to get an overview of the existing implementations. You can also create new implementations from here.

3. Assign a name to the implementing class such as Y_CL_IM_BNK_BADI_PAYM_ALRT. You can follow the naming convention:

Namespace prefix, Y, or Z

CL_ (for class)

IM_ (for implementation)

Name of the implementation

4. Double-click the implementation class name to implement the method. The system starts the Class Builder editor.

5. When you have finished incorporating the logic, you must activate your objects.

3.4 BAdI: Actions after Error during Payment File Creation

Use

In this IMG activity, you can define the actions you must take if the payment file creation process ended with an error.

Activities

Make the settings you require.

4 Bank Statement Monitor

4.1 Settings for Bank Statement Monitor

Text is available in the system.

5 Release Strategy

5.1 Mark Rules for Automatic Payments(No Approval)

Use

In this IMG activity, you can mark the the batching rules that need no approval, meaning that no approval process is required.

Activities

Make the settings you require.

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 the IMG activity

Through the area menu

From the 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'.

Through 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'.

Activities

1. Choose a radio button in the group frame Release.

a) If you choose always, you must also select a release procedure for all release objects.

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

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

7. Choose Execute.

8. Go back to the initial screen of the IMG activity.

If you choose statistical , you must define a fraction of a million that the system is to forward to the release process, and a release procedure.

If you choose never, you cannot make any more settings.

If you change from always, conditional or statistical to never, the system deletes all the settings for the release object.

9. Save your entries.

5.3.2 Assign Role to Release Steps

Use

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.

Activities

Make the settings you require.

5.3.3 Assign Workflow Template to Release Procedure

Use

In this IMG activity, you can assign a release workflow and a release procedure workflow to every release procedure of a release object. The release workflow realizes the technical processing of the release in the system. The release procedure workflows realize the technical processing of the various release procedures (such as the principle of treble control) in the system.

Requirements

You have made the settings for the corresponding release object in IMG activity Assign Release Object to Release Procedure.

You have made the settings for the corresponding release object in IMG activity Assign Role to Release Steps.

You have made the following settings for the workflows involving deadline monitoring (such as SAP Workflow 50100061 for release object DEH_ESK) in the customizing settings of the basis components by choosing 'Business Management -> SAP Business Workflow -> Basic Settings (SAP Business Workflow) -> Deadline Monitoring for Work Items -> Schedule Deadline Monitoring'.

You have executed activity Schedule Background Job for Case-Specific Deadline Monitoring by double clicking on the appropriate line.

You have executed activity Optional: Schedule Permanent Deadline Monitoring by double clicking on the appropriate line.

You have set the Periodic Deadline Monitoring indicator.

You have entered a value for the Interval Until Next Deadline Check .

Standard settings

Assign a release workflow and a release procedure workflow to the different release procedures of every release object.

5.4 Digital Signatures

5.4.1 Define Basis settings

Text is available in the system.

5.4.2 Specify Signature Method for Approval Using Simple Signature

Text is available in the system.