SAP® Documentation

Single view

Payment transaction operations for the product ( RELNBANK_402_BKK_ZVKEHVO )

CPI1466 during Backup   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

Payment transaction operations for the product


A payment transaction operation is the combination of transaction type and medium. Examples of payment transaction operations include: bank transfer by telephone, debit memo by internet, or check presentation with deposit slip. The following requirements relate to payment transaction operations:

  • Every payment item represents a payment transaction operation.
  • You must define for every product what payment transaction operations are permitted or prohibited.
  • You must define for every blocking reason (this specifies what type of block applies to an account) what payment transaction operations are to be blocked.
  • The permitted / prohibited payment transaction operations must be evident on an account. The payment transaction operations per account are the result of the combination of product and blocks for the account.

As of release 4.02 A, a new concept applies to payment transaction operations, offering the following improvements:

  • better overview
  • easier maintenance and avoidance of wrong entries by the removal of identification numbers
  • uniform display of all attributes and, therefore, of the payment transaction operations.

Effects on Customizing

Choose Master data-> Product definition-> Product-> Create product, to maintain the payment transaction operations per product. Every single combination of transaction type and medium can be permitted or prohibited for the product or blocked per blocking reason.

With Master data-> Account-> Define blocking reasons account, you maintain the blocking reasons. You can define as many blocking reasons as you want, for example, 'Bankruptcy'. Per blocking reason you can assign as many features and as many payment transaction operations as you want. You can assign as many blocking reasons as you want to each account. A feature or a payment transaction operation can only be used for an account if this is allowed for the product of the account and is not blocked by one of the blocking reasons for the account.

Changes to the Interface

All payment transaction operations are displayed in a list structured like a matrix. In each line there is a transaction type and in each column a medium. At the intersection there is an LED display; if the transaction is permitted, the LED is green, if it is not permitted, it is red.

Changes in procedure

Payment transaction operations

When you maintain the payment transaction operations in the product configurator, the matrix is displayed. In addition, per column and per line, each a red and a green LED is displayed in the upper left hand corner. All the LED displays are interactive; if you click on an LED in the matrix, the color changes from red to green and vice versa.

If you click on the red LED display directly for the transaction type, all LED displays in the line turn red. The same applies to the green LED displays and the column LEDs.


In the section functionalities for the account, both the blocked functionalities and the available functionalities are displayed. All existing features / payment transaction operations are displayed. The following applies:

  • red light = blocked by a blocking reason
  • green light = assigned by the product
  • no light = neither assigned nor blocked

To get an overview of what is allowed for the account, choose the detail view for the account.

The procedure for defining the blocking reasons has not changed. These are still displayed in table controls.

CPI1466 during Backup   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 4081 Date: 20191024 Time: 022432     sap01-206 ( 123 ms )

Our Service

Looking for Support? Questions?




Leave us your contact details and we will call you back. Panels marked with * are mandatory.