Payment Order 

Definition

Business object in Account Management (FS-AM), that depicts an order to a bank to execute a bank transfer or a debit collection, for example. For more information about the debit collection procedure, see Direct Debit Orders and Collection Authorization.

A payment order consists of two or more payment items: One ordering party item and one or more recipient items. Payment orders with one recipient item are described as single or individual payment orders, and those with multiple recipient items as collective payment orders.

The account currency of the recipient can be different from the account currency of the ordering party. For more information about the prerequisites and procedure, see Currency Exchange.

Payment operations on which a payment order is based can differ greatly from a posting perspective. The system differentiates between these payment operations on the basis of transaction types. This is shown in a simplified version in the table below:

Payment Operation (Transaction Type)	Elements of a Payment Order
Bank Transfer and so on	Paying Party	Payment Recipient
Debit Memo, Check	Payment recipient	Paying party
General	Ordering party	Order recipient

There are various types of payment orders:

●      Internal Payment Orders:

Payment orders whose order recipients are also managed in the Account Management (FS-AM) system. In this case, the system generates an internal payment item each for the ordering party and the order recipient item and updates these on the account specified in the payment order.

●      External Payment Orders:

Payment orders whose order recipients are not managed within the Account Management (FS-AM) system. In this case, the payment order data is retrieved using Business Add-Ins BadI: Connection of the Payment Transaction System at the Check Event and BadI: Connection of the Payment Transaction System at the Save Event for an external payment transaction system that then forwards the postings to the relevant subledger. In this case, a payment item is only generated for the ordering party item in the Account Management (FS-AM) system and updated on this account. IMG activity Connect Payment Transactions System for Outgoing Payment Transactions is also available to you. You can use this to create a system connection via Remote Function Call (RFC) between your SAP System and another SAP System, to which a payment transactions system is already connected via the BAdIs mentioned above. A combination of internal and external recipients is possible for collective orders.

 

If you do not wish to execute a payment order immediately, but on a defined date in the future, use the functions for forward orders.

Structure

The structure definition for the payment item is divided into methods and customer enhancements.

Methods

In Account Management (FS-AM), you can use one of the following channels for processing objects:

●      Dialog

●      Business Application Programming Interface (BAPI)

●      Direct Input (DI)

The following shows which payment order methods you can call up (and via which channel):

Method	Channel
	Dialog	BAPI	DI
Creating payment order	x	x
Display payment order (BAPI: Get data only)	x	(x)
Change payment order	x
Delete payment order	x
Reversing payment order	x	x
Renewed transfer of payment orders to PTS	x
Select payment order	x1	x2

These methods can change the status and release status of the payment order. See Status and Release Status of Payment Orders.

(1)     You can select payment orders in the dialog using a selection screen. You can also define any restrictions on the selection.

(2)     You can only select payment orders according to the account details of the ordering party with this BAPI.

Dialog

You can call up the following transactions in dialog mode:

Transaction Code	Short Description
BCA_PO_CREATE	Create payment order
BCA_PO_DISPLAY	Display payment order
BCA_PO_CHANGE	Change payment order
BCA_PO_DELETE	Delete payment order
BCA_PO_REVERSE	Reverse payment order
BCA_PO_RESEND_EXTERN	Repeated transfer of payment orders to the payment transaction system

Business Application Programming Interface (BAPI)

You can call up the following methods using the BAPI Explorer:

Method*	Short Description
PaymentOrder.Cancel	Reverse payment order
PaymentOrder.Create	Create payment order
PaymentOrder.GetDetail	Read payment order
PaymentOrder.GetListByAccount	Select payment order

* The first two methods are write methods.You can also execute these in a test run.

Direct Input

Direct input is not implemented for payment order. However, you can carry out external data transfers (EDT) for the individual payment items of payment orders. For more information, see Payment Items.

Customer Enhancements

To find the Business-Add-Ins (BAdIs) that are available for forward orders, in the Customizing for Account Management (FS-AM) choose Order Management ® Payment Order ® Business Add-Ins (BAdIs) ® General BAdIs and BAdIs for BAPIs.

Integration

Customizing

You make the settings for payment orders in the Customizing for Account Management (FS-AM) under Order Management ® Payment Order in the following Customizing activities:

●      Connect Payment Transactions System for Outgoing Payment Transactions

●      Assign Offsetting Transaction Types (Payment Order – Online)

●      Assign Offsetting Transaction Types (Internal Processes)

●      Edit Display of Change Documents

●      Set Recipient Account Identification / Additional Fields

●      Create Customer Fields

If you create correspondence and want to calculate charges for this, you must also make the following settings:

●      Create Charge Key

●      Assign Charge Key to Transaction Type

●      Create Payment Notes Text for Correspondence Charges

●      Select Trigger for Event-Controlled Bank Statement

●      Assign Transaction Types and Medium / Payment Method to a Payment Directive Type

If you wish to use the release functions, you must also make the following settings:

●      Assign Release Procedure to Release Object

●      Assign Rule to Release Steps

●      Assign Release WF and Release Procedure WF to Release Procedures

●      Define Rejection Reasons

If you wish to archive the payment orders, you must also carry out the following IMG activity:

●      Define Residence Time for Payment Order (Object PAYMORDER)

You must also make the settings for the payment item object in the Customizing for Account Management (FS AM).

Checks Run by the System

●      Authorization Check

You can have the system run an authorization check for the activities Create (Post), Change, Display, Delete, Reverse, and Force Post Payment Order, depending on the transaction types of the payment order. The check for the respective activity is also dependent on the ordering party transaction type of the payment order.

 

In addition to this authorization check using the SAP authorization object for the payment order, you can make your own authorization checks. Business Add-In BAdI: Definition of the Authorization Check is available for this in the Customizing for Account Management (FS-AM). Choose Order Management ® Payment Order  ® Business Add-Ins. For more information, see Authorization Administration.

●      Release Check

The system also runs checks for the relevance for release. This means it checks whether a payment order is forwarded to the release workflow on the basis of the specific characteristic value of its release attributes.

If the system identifies a payment order as being subject to release, it forwards it to the release workflow.Payment orders that are subject to release must be released by a user authorized for release before further processing can take place. For more information, see Release Object PAOR (Payment Order).

●      Checks for Posting a Payment Order

When you post a payment order, various checks are run. Some of these checks depend on the business transaction and the related transaction types. You can set in Customizing which checks are made for which business transactions. Read the section on this in the Implementation Guide (IMG) under Item Management® Basic Functions ®Transaction Types and Transaction Type Groups  ® Maintain and Assign Transaction Types for Payment Items.

...

○       Checks are made for:

                                                  i.       Formal checks to which posting control can be applied

                                                ii.       Formal checks to which posting control cannot be applied

The system first makes formal checks for all payment items (ordering party and recipient items). The checks depend on the channel via which a payment order is processed, and on the Customizing settings. They are not only made when you try to make a posting or simulate the posting, but also if you change to another tab page. Formal errors must always be corrected, as posting is otherwise not possible. The only alternative is to terminate processing.

Once all the formal checks have been completed successfully, the system checks for formal errors to which posting control can be applied. If it detects formal errors to which posting control can be applied, you can only process a payment order in accordance with the settings made in the Customizing for  Account Management (FS-AM) for the posting control rules. Possible settings include rejection by the system, postprocessing, or posting of the payment order.

For more information, see the documentation in the Implementation Guide for Define Main Set of Rules under Item Management ® Posting Control Rules. You can also terminate processing.

○       Check for material errors

Once the checks for formal errors and formal errors to which posting control can be applied have run successfully, the system makes material checks, first for the ordering party / recipient.

If the system finds material errors, you can still force the posting of the payment order. You can also process a payment order in accordance with the Customizing for Account Management (FS-AM) set for the posting control rules. Possible settings include rejection by the system, postprocessing, or posting of the payment order. For more information, see the documentation in Customizing for Define Main Set of Rules under Item Management ® Posting Control Rules. You can also terminate processing.

Once the material checks for the item of the order initiator have run successfully, the check is completed if there are only external order recipients. If there are more internal order recipients, there are more material checks. If the material checks fail for internal order recipient items, you can either force the posting of this item or proceed in accordance with the settings made for the posting control rules. The last option excludes rejection by the system as a setting. You also have the option of terminating the posting of the entire payment order.

Archiving

You have the option of specifying that payment orders are archived or deleted physically from the database once a certain period of time has expired. You define this period of time for each payment transaction area, product category, and product in the Customizing for Account Management (FS-AM) under Order Management ® Payment Order ® Archiving ® Define Residence Time for Payment Orders (object PAYMORDER).

You can display archived payment orders from the SAP Easy Access screen by choosing Account Management ® Archiving ® Data Display ® Payment Orders (Archiving object PAYMORDER).

For more information about the payment order archiving object, see the Customizing for Account Management in IMG activity Technical Documentation for Account Management by choosing Account Management (FS-AM) ® Concepts and Guidelines ®Archiving.

For more information about archiving, see Data Archiving and Deletion in Account Management (FS-AM).

Objects Derived or Generated by the System

Payment transaction area

When you create a payment order, the system derives the relevant payment transaction area from the bank details of the order initiator. Exactly one payment transaction area is assigned to each bank-specific bank key. The payment transaction area depicts the organizational responsibilities for payment transactions within a bank in the Account Management (FS-AM) system.

You create payment transaction areas in Customizing by choosing Basic Settings ® Organization ® Define Payment Transaction Areas. You must also make the required entries under Basic Settings ® Organization ® Assign Bank Key to a Payment Transaction Area.

Payment Order Number

The system uses the payment transaction area to derive a payment order number from the corresponding number range. You create number ranges in the Customizing settings by choosing Basic Settings ® Organization ® Maintain Payment Transaction Areas. A payment order in the Account Management (FS-AM) system is clearly and unmistakably identified by the payment transaction area and the payment order number.

Change Document

The system generates a change document that meets auditing requirements. All changes that you make to payment order data are logged in change documents. You call these up in all payment order transactions, with the exception of transaction Create Payment Order by choosing Extras ® Change Documents.

You can configure the display of the change documents in the Customizing for Account Management (FS-AM) by choosing Define Display of Change Documents. For more information, see Change Documents.

Correspondence Request

The system provides correspondence requests for the following correspondence types:

●      Confirmation of Execution

The system creates a confirmation if you set this for individual or all payment orders either directly in the payment order on the Ordering Party Details tab page, or in the Customizing for  Account Management (FS-AM) by choosing Order Management ® Payment Order ® Correspondence  ® Assign Charge Key to Transaction Type. BAdI: Creation Control for Confirmation of Execution is available to you in the Customizing for Account Management (FS-AM) for the data you want included in this confirmation. Choose Order Management ® Payment Order ® Business Add-Ins. In the standard system delivered, this contains the connection to the correspondence tool. For more information, see Correspondence in Account Management.

 

If you wish to create and issue a confirmation of execution, you must have made the required Customizing settings for the correspondence tool and the Print Workbench.

 

You define the formulation of the payment note text to identify this charge in correspondence in Customizing for Account Management (FS-AM), under Order Management ® Payment Order ® Correspondence ® Create Payment Notes Text for Correspondence Charges.

●      Confirmation of non-execution

This is always created if a payment order cannot be created due to material checks or formal checks to which posting control can be applied, and the user has already rejected it either in the create payment order dialog, or in postprocessing. The correspondence charges you can levy are similar in procedure to those for a confirmation of execution.

Charge for Correspondence and Editing Payment Orders

To levy charges for the creation of correspondence, choose Account Management (FS-AM) ® Current Settings  ® Financial Conditions ® Condition Group ® Edit Condition Group on the SAP Easy Accessscreen, and create standard conditions, or individual conditions for the account on the Financial Conditions tab page. For more information, see Editing Condition Groups and Editing Financial Conditions.

You must also have made the following Customizing settings for the calculation of charges.

●      Product Management ® Financial Conditions ® Define Condition Type

●      Order Management ® Payment Order ® Correspondence ® Create Charge Key

●      Order Management ® Payment Order ® Correspondence ® Assign Charge Key to Transaction Type

For more information, see Financial Conditions and in the documentation for the relevant IMG activities.

Payment Item

When you execute a payment order, the system generates payment items.

Future Item

In the payment order dialog, the system always determines the posting date using the posting date set for the bank posting area. For more information about setting this date, see Setting the Posting Date.

However, a posting date can be specified by other applications that generate payment orders (such as standing order) or channels (such as BAPI). In this case, the system checks whether payment items can be generated for this date. This is the case if the posting date is not earlier than the last date on which the bank posting area was settled. If the date is later than the current date for payment transactions, future items are generated.

Event-Controlled Bank Statements

The system creates this if a payment order is not executed, if the prerequisites for creation of a confirmation of non-execution are met and if you have made the Customizing settings for bank statements and the following Account Management (FS-AM) Customizing settings:

●      Item Management ® Basic Functions ® Define Rejection Reasons

●      Order Management ® Payment Order ® Select Trigger for Event-Controlled Bank Statement