Bank chain (multilevel payment chain) 

Description

As of Release 4.5A, you will be able to use bank chains (multilevel payment chains). By entering a bank chain, you can make payments through several banks (intermediary and correspondence banks of both sender and receiver). You can enter up to three intermediary banks in a chain.

The bank chain function can be activated according to client. A scenario for determining a bank chain is assigned to a client. The scenarios describe how bank chain determination should take place. A number of typical scenarios are provided by SAP. Further individualized scenarios can be created and named by the customer.

There are two types of bank chain:

• General Bank Chains

This type is created in bank chain Customizing. They are of a general nature, not related to a particular procedure (e.g. Treasury transaction) or business partner.

• Partner-Specific Bank Chain

These bank chains are contingent upon master data (e.g. Treasury business partners or creditors), and thus represent master data themselves. They are created using a partner's account connection.

The individually supported partners are:

• Vendors

• Customers

• Treasury business partners

• House banks

You maintain bank chains in your current system directly from the TR business partner and TR standing instructions. For more information about this, see release note Payment transactions via correspond. banks: Multi-level payment methods.

You can maintain bank chains for creditors, debtors, and house banks in Release 4.5A via the menu ( Accounting -> Financial Acct. -> Banking -> Master data -> Bank chain).

A bank chain is chosen according to the settings in bank chain determination during the payment run (both for open items and for payment requests from Treasury and Cash Management).

If one of the values relevant for the bank chain is changed in the payment proposal (e.g. house bank or partner bank), the bank chain is reconfigured and shown to the user.

Bank chains transcend payment medium boundaries. The following formats are supported in Release 4.5A: S.W.I.F.T., MT100, MT200, MT202, EDI (Basis-IDOC: PEXR2002), sending of payment data via ALE (Basis-IDOC: FIPARQ01).

Damage caused to data by errors

None

Software/hardware requirements

In Release 4.5A, no change documents are written for the specific

bank chains.

Installation information

None

System administration changes

None

Change system parameters in customizing

You activate the function "bank chain" in the operation Activate bank chain.

You define the scenarios for bank chains in the operation Define scenario.

You record the general bank chain in the operation Establish general bank chain.

You find the operation in the IMG menu under Financial acct. -> Bank accounting -> Bank chain.

Effect on batch input

None

Changes to the interface

• Maintain partner-specific bank chains via the menu (Accounting -> Financial acct. -> Banks -> Master data -> Bank chain).

• Changes to the Treasury interface are described in release note Payment transactions via correspond. banks: Multi-level payment methods.

Changes in procedure

None

Procedure for removing dataset errors

None

Dependent functions

None

Planning

Linking to master data maintenance for vendors and customers.

Further notes

For more information, see release notes:

• Payment transactions via correspondence banks: Multi-level payment methods

• New payment transaction formats