Hierarchy

⤷

⤷

⤷

IMG Activity
ID | SEPA_MANDATE_FILTER | BAdI: Influencing the Selection of SEPA Mandates |
Transaction Code | S_EBJ_45000021 | (empty) |
Created on | 20130717 | |
Customizing Attributes | SEPA_MANDATE_FILTER | BAdI: Influencing the Selection of SEPA Mandates |
Customizing Activity | SEPA_MANDATE_FILTER | BAdI: Influencing the Selection of SEPA Mandates |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SAPF110S_SEPA_MANDATE_FILTER |
Use
This Business Add-In (BAdI) is used in the Payment Transactions (FI-AR-AR-PT and FI-BL-PT-AP) component.
For SEPA direct debits, the payment program determines a mandate which the payer has used to authorize the direct debit. If the payment program finds several active mandates when doing this, it uses the first of these mandates for the direct debit.
You can use this BAdI to influence the selection of the mandates, either by sorting the list of mandates found or deleting entries. This way you can accomplish that one payment run only uses new mandates, while another payment run only selects mandates already used.
There are entries for the payment run and payment method and also selection conditions for the mandate selection in the interface to assist you in deciding how the mandates are selected. You can distinguish between payment runs using the run identification:
- For F110 IS_PAYRUN-LAUFI+5 is empty.
- For F111 IS_PAYRUN-LAUFI+5 has the value R.
Requirements
For the payment processes, you use payment program F110 in accounts receivable accounting or payment program F111 for payment assignments.
If you want to influence the mandate selection for each item in payment program F110, then you should use BAdI: Assignment of a SEPA Mandate to an Item.
Standard settings
For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18).
Activities
After you call the IMG activity, the system displays a dialog box where you enter a name for the implementation.
If implementations of this Business Add-In have already been created, the system displays them in a dialog box. You then choose one of them by choosing Create, and continue as follows:
- In the dialog box, enter a name for the implementation of the Add-In and choose Create.
The system displays the initial screen for creating Business Add-In implementations. - On this screen, enter a short description for your implementation in the Implementation Short Text field.
- If you choose the Interface tab, you will notice that the system has populated the Name of the Implementing Class field automatically, by assigning a class name based on the name of your implementation.
- Save your entries and assign the Add-In to a package.
- To edit a method, double-click its name.
- Enter your implementation code between the
method <Interface Name>~<Name of Method>.
andendmethod.
statements. - Save and activate your code. Navigate back to the Change Implementation screen.
Note: You can also create an implementation for an Add-In and not activate it until later. If you want to do this, do not perform the following step: - Choose Activate.
When the application program is executed, the code you created is run through.
Example
You can find example implementations, including for separating payment runs between new and already used mandates, in the BAdI Builder on the Enh. Spot Element Definitions tab in the Implementation Example Classes section.
The following example implementations are available:
- CL_SEPA_MANDATE_FILTER_DEMO
See also
For information about how to implement BAdIs in the Enhancement Framework, see SAP Library for the SAP NetWeaver Platform on the SAP Help Portal at http://help.sap.com/nw_platform. Select a release and then choose Application Help. In SAP Library, choose SAP NetWeaver Library: Function-Oriented View -> Application Server -> Application Server ABAP -> Application Development on AS ABAP -> ABAP Customer Development -> Enhancement Framework.
Business Attributes
ASAP Roadmap ID | 257 | Create User Exits |
Mandatory / Optional | 3 | Nonrequired activity |
Critical / Non-Critical | 1 | Critical |
Country-Dependency | A | Valid for all countries |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20130719 |
SAP Release Created in |