Standing Orders 

Definition

Business object of the Account Management (FS-AM) system depicting a periodically generated payment order credited to or debited from one or more recipient accounts. Standing orders with one recipient item are called single or individual standing orders, and those with multiple order recipient items, collective standing orders. For standing orders we differentiate between those with a fixed, meaning always the same amount and those with a variable amount, known as variable standing orders.

Structure

In Account Management, the standing order is a feature of the account. For more information about editing account contract features, see Editing Features.  In addition, the standing order has a feature attribute in the product. For more information about product attributes and their characteristics, see: Product.

You manage standing orders for each account on a time-dependent basis. For more information about time dependency, see the Implementation Guide (IMG) for Account Management (FS-AM) in IMG activity Technical Documentation for Account Management (FS-AM) (Transaction FS_AM_TECH_DOC) under Concepts and Guidelines ® Time Dependency  ® Standing Order.

The transaction type forms the basis of a standing order. You define transaction types in the Customizing for Account Management (FS-AM) under Item Management ® Basic Functions ® Transaction Types and Transaction Type Groups ® Maintain and Assign Transaction Types for Payment Items.

Methods

In Account Management (FS-AM), you can use the following channels to process objects:

●      Dialog

●      Business Application Programming Interface (BAPI)

●      Direct Input (DI)

The following overview shows which methods of a standing order can be called up via which channel:

Method	Channel
	Dialog	BAPI	DI
Create standing order	x	x	x
Display standing order	x
Change standing order	x	x	x
Delete standing order	x	x	x
Execute standing order	x
Query standing order data		x
Select standing orders	x	x
Archive standing orders	x

Dialog

You can call up the following transactions in dialog mode:

Transaction code	Short description
BCA_SO_CREATE	Create standing order
BCA_SO_CHANGE	Change standing order
BCA_SO_DISP	Display standing order
BVW_STANDORDER	Display archived standing orders
BCA_SO_DELETE	Delete standing order

Business Application Programming Interface (BAPI)

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

Method*	Short description
StandingOrder.Change	Change standing order
StandingOrder.Create	Create standing order
StandingOrder.GetDetail	Query standing order data
StandingOrder.GetList	Select standing orders

* You can also execute the first three methods as a test run.

Direct input

You can create standing orders for migrating by way of external data transfer (EDT) via direct input. For more information, see IMG activity Technical Documentation for Account Management (FS-AM) under Concepts and Guidelines ® Migration ® Migration Objects ® Standing Order.

Customer Enhancements

You can find the Business Add-Ins (BAdIs) that are available for standing orders in the Customizing for Account Management (FS-AM) by choosing Order Management ® Standing Order  ® Business Add-Ins (BAdIs).

Integration

Customizing

You make the settings for standing orders in the Customizing for Account Management (FS-AM) by choosing Order Management ® Standing Order:

You make the settings for correspondence by choosing Order Management →Payment Order → Correspondence.

Checks Run by the System

When you create/change standing orders, the checks the system makes include:

●      Have you entered the required fields Transaction Type and Payment Method?

●      Have you specified the account identification data for both the order initiator (initial screen) and the order recipient?

●      Have you specified at least one order recipient item?

●      Have you specified a transaction amount and a transaction currency for standing orders with a fixed amount?

●      Is the maximum transfer amount less than the minimum transfer amount for variable standing orders?

●      Does the value / the total of the values for percentile execution (variable standing orders) amount to 100 %?

●      Have you specified the time periods, meaning how often and on which key date the standing order is to be executed?

●      Have you stored an offsetting transaction type for the transaction type in the Customizing settings?

Release Check

You can transfer standing orders to the release workflow, depending on certain properties. In this case, the system also runs checks for release-relevance. This means it checks whether a standing order is to be  forwarded to the release workflow on the basis of the specific characteristic value of its release attributes. If the system identifies a standing order as being subject to release, it forwards it to the release workflow. Standing orders that are subject to release must be released by a user authorized for release before further processing. For more information, see Release Object STOR (Standing Order).

Archiving

You can specify whether standing orders are archived or deleted physically from the database once a certain period of time has elapsed. You define this period of time for each bank posting area, transaction type, product category, and product in the Customizing settings by choosing Order Management ® Payment Order ® Archiving ® Define Residence Time for Payment Orders (object STANDORDER).

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

Before a standing order can be archived, the following prerequisites must be met:

●      The status of the standing order must be Deleted or Rejected.

●      All the payment orders generated by the standing order must be archived.

●      If there are multiple standing orders for an account and you wish to deleted the standing order with the highest standing order number, the underlying account must be closed and the reactivation period must have expired (see Account Closure).

●      If you have implemented BAdI Archivability of Standing Orders,  the archiving status of archiving object Standing Order must be Archivable.

For more information about archiving object Standing Order, see IMG activity Technical Documentation for Account Management under Concepts and Guidelines ® Archiving ® Archiving Objects.

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

Objects Generated by the System

Correspondence requests in connection with the standing order

You can create different types of correspondence for standing orders. These relate to the execution or non-execution or any other processing for standing orders and are depicted in the Account Management system in the form of the following correspondence types.

●      Confirmation of Execution (Correspondence Type BAS5)

The system creates this if you have made the following Customizing settings:

○       For individual standing orders on the Time Periods tab page of the standing order in question

○       For all standing orders in the Customizing  for payment orders by choosing Order Management ® Payment Order ® Correspondence ® Assign Charge Key to Transaction Type

●      Confirmation of Non-Execution (Correspondence Type BAS4)

The system always creates this if it rejects a standing order, for example due to insufficient funds or account locks. You define possible reasons why standing orders are rejected in Customizing by choosing Item Management  ® Basic Functions  ® Define Rejection Reasons.

●      Event-controlled bank statement

The system creates this when a standing order is not executed, provided you have made the following settings in addition to the generally required settings for the bank statement in Customizing:

○       Item Management ® Basic Functions ® Define Rejection Reasons

○       Order Management ® Standing Order ® Select Trigger for Event-Controlled Bank Statement

●      Notice of Deletion (Correspondence Type BAS4)

The system creates this automatically before deleting a standing order after not having been able to execute it several times. For more information, see the documentation for IMG activity Define Maximum Number of Failed Attempts.

●      Confirmation of Deletion (BAS3)

The system creates this automatically in the following cases:

○       When the system deletes a standing order for which you have entered the deletion details in the dialog, provided you do not deactivate the Correspondenceindicator (correspondence type BAS3) on the Operation tab page of the standing order being deleted.

○       When the system automatically deletes a standing order after not having been able to execute it several times. For more information about automatic deletion, see the documentation for IMG activity Define Maximum Number of Failed Attempts (correspondence type BAS4).

The system does not create this automatically if you make the deletion via BAPI. In this case, you can use the RUNCORRESPONDENCE parameter to have the system create this correspondence.

Using BAdI: Correspondence Control – Automatic Standing Order Deletion you can suppress creation of the confirmation of deletion when the system deletes standing orders because their last execution date has been reached. This can be meaningful if you wish to prevent your customers from receiving up to three letters within a short space of time (confirmation of change, confirmation of execution and confirmation of deletion, for example).

●      Confirmation of Creation (Correspondence Type BAS1)

The system always creates this when you create a standing order in online mode. In you create it via a BAPI you can use the RUNCORRESPONDENCE parameter to have the system create this correspondence. The system does not create correspondence for direct input.

●      Confirmation of Change (Correspondence Type BAS2)

The system always creates this when you change a standing order in online mode. For each standing order, with the Generally Correspondenceindicator you define whether you generally want correspondence generated for creating, changing or deleting (standing orders). With the No Correspondence indicator you can decide whether correspondence is generated just for one particular editing of a standing order. If you change it via BAPI you can use the RUNCORRESPONDENCE parameter to have the system create this correspondence. Parameter NOCORRESPONDENCE controls individual cases.

Before correspondence can be generated, you have to make settings for the correspondence tool in the Account ManagementImplementation Guide by choosing Tools ® Correspondence Tool. For more information about correspondence, see Correspondence in Account Management.

Charges in Connection with Standing Orders

You can levy the following charges in connection with processing and executing standing orders:

●      Charges for executing standing orders

●      Charges for creating standing orders

●      Charges for changing standing orders

●      Charges for deleting standing orders

●      Charges for creating correspondence relating to standing orders

Before you can levy charges, you must have made the general settings for the Financial Conditions. Posting these charges depends on the general and individual condition settings for the ordering party account. You can override these in the dialog transactions of the standing order. You can use the following indicators to control this in the dialog transactions:

●      If the No Charge indicator is set on the Operation tab page, no direct charge is posted for creating, changing and deleting standing orders or for creating a confirmation of creation, change or deletion (BAS1 - BAS3).

●      If the No Correspondence indicator is set, no correspondence is created for creating, changing and deleting standing orders.

Combinations of these two indicators mean the following:

                            a.      Both indicators are not set (default): The system posts charges in accordance with the Customizing settings and the standing order master data and creates correspondence.

                            b.      Both indicators are set: The system does not post any charges for the standing order currently being created, changed or deleted, and does not create correspondence.

                            c.      The No Charges indicator is set, the No Correspondence indicator is not set: If the CONFIRM_CREATE indicator is set in the standing order master data record, the system creates correspondence but does not levy a charge for it. Also, no charge is posted for creation, change or deletion, irrespective of the conditions for the account.

                            d.      The No Charges indicator is not set, the No Correspondence indicator is set: The system posts a charge for creating, changing or deleting the standing order in accordance with the conditions for the account, but does not generate correspondence.

●      To create the confirmation of execution (BAS4 and BAS5) free of charge, you have the following options:

○       Set the appropriately named indicator on the Time Periods tab page in the Create Standing Order and Change Standing Order transactions.

○       Do not specify a charge key for the transaction type in question in Customizing under Order Management ® Payment Order ® Correspondence ® Assign Charge Key to Transaction Type.

Before correspondence charges can be calculated, you must have created a charge key in the Customizing by choosing Order Management ® Payment Order ® Correspondence ® Create Charge Key and assigned it to the required transaction types by choosing Order Management ® Payment Order ® Assign Offsetting Transaction Types to Transaction Types.

Change documents

The system generates a change document that meets auditing requirements. All changes you make to standing order data are logged in change documents. You can call these up in the standing order transactions by choosing Extras ® Change Documents.

You can configure the display of change documents in Customizing by choosing Define Display of Change Documents.

In Customizing, choose Order Management ® Standing Order ® Define Change Document Display to define whether and in which order you want the individual attributes of a change document displayed on the Display Change Documents screen. In addition, you define the standard settings for the selection criteria.

Work Item in the Release Workflow

The system generates a work item for the release process, if required on the basis of the Customizing settings.

Payment Order

When a standing order is executed, the system generates a payment order.

List of SO Changes

Thanks to the time dependency of standing orders, the system can store multiple standing order changes to the ordering party data, separately from one another. No details of the recipient items are displayed, because for collective standing orders, the list could become too long and unmanageable.

The list of changes to a standing order contains the following fields:

• In the list header:
• • Bank country
  • Bank key
  • Account number of ordering party
  • Account holder
  • Standing order number
  • Transaction type

• In the list lines:
• • Valid from
  • Status
  • Next execution
  • Payment method
  • Medium