Ansicht
Dokumentation
V_FSEPA_INST_CD - Determine Local Instrument Code and Lead Times
ROGBILLS - Synchronize billing plans ABAP Short ReferenceThis documentation is copyright by SAP AG.
Define the rules that payment programs use to determine the direct debit type and the lead time for SEPA direct debits.
In this Customizing activity, you define the rules that the payment programs use to determine the following values necessary for SEPA direct debits:
- Calendar that is to be used to calculate the lead time.
No rules are delivered in the standard SAP system. The system determines the following values:
- For B2B Mandates:
Local instrument code B2B
Lead time 1 day
- For other mandates:
Local instrument code CORE
Lead time 5 days for the first use of a mandate
Otherwise two days for the subsequent use of a mandate
If you do not define a calendar, the payment program uses a standard logic to determine the calendar. In the FI payment programs (transaction F110 and F111) the calendar is determined for example using the Payment Program Configuration -> Edit -> Value Date -> With Bank Calendar. If you have not entered a calendar there, the system uses the EU calendar, which you still may need to define.
You determine the local instrument code using these rules for the following:
- The countries/regions of the house banks or for the house banks,
- for the bank countries/regions of the payers or for the banks of the payers.
When you determine the lead times, you can also differentiate between first and subsequent direct debit of mandates used multiple times, and also between one-time use mandates. You can also define different lead times for B2B mandates.
When maintaining the rules, you do not need to fill all key fields. If you leave the values empty, the system interprets the entries generically. You determine the order in which the generic entries are to be read by the payment program in the Customizing activity Change Priority Rules for Local Instrument Code and Lead Times.
You can test which entries the payment program selects in which situations in the activity above by using the Simulate button. You enter a house bank and determine the bank details of the payer either using a mandate, or using the bank key and IBAN.
Entry for one country/region
You can define with the following entry that all German banks (for example) accept the local instrument code COR1, and consequently use it for all direct debits within Germany.
| Bank country/region house bank | DE |
| Bank country/region payer | DE |
| Local instrument code | COR1 |
| Lead time | 1 day |
Additional entry for an exception
If a particular bank in Germany does not yet support the local instrument code COR1, then you add the three entries for the local instrument code CORE with the related bank key for this bank (two entries for first and subsequent usage of mandates with multiple use, and one for one-time mandates). This entry can, depending on the circumstances, be useful for both the bank of the payer and for the house bank. The payment program then uses first the entry for which more key fields are specified, and only selects the generic entry if no specific entries are found.
Adjustment of the lead time
If you always schedule the payment runs two days before presenting the payment file (for example, to have enough time to check the payment data), you would in turn have to increase the lead days by two days. Alternatively, you can move the baseline date in business add-in (BAdI) SAPF110S_SEPA_ADD_DAYS_ADJUST back by two days.
Note: This configuration activity can be used in both quality systems and product systems. If you implement this activity in the quality system, it overwrites the configuration in the production system.
General Data in Customer Master ABAP Short Reference
This documentation is copyright by SAP AG.
Length: 4990 Date: 20240523 Time: 215046 sap01-206 ( 96 ms )
