SAP ABAP IMG Activity SEPA_ADD_DAYS_ADJUST (BAdI: Determining the Lead Times for SEPA Direct Debits)

Hierarchy

☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ FBZ (Package) Payments

IMG Activity

ID	SEPA_ADD_DAYS_ADJUST	BAdI: Determining the Lead Times for SEPA Direct Debits
Transaction Code	S_EBJ_45000019	(empty)
Created on	20130717
Customizing Attributes	SEPA_ADD_DAYS_ADJUST	BAdI: Determining the Lead Times for SEPA Direct Debits
Customizing Activity	SEPA_ADD_DAYS_ADJUST	BAdI: Determining the Lead Times for SEPA Direct Debits

Document

Document Class	SIMG	Hypertext: Object Class - Class to which a document belongs.
Document Name	SAPF110S_SEPA_ADD_DAYS_ADJUST

Use

This Business Add-In (BAdI) is used in the Payment Transactions (FI-AR-AR-PT and FI-BL-PT-AP) component. You can use this BAdI to assist you in determining the data required for SEPA direct debits.

In the payment run (F110 for customer items or F111 for payment assignments), the system determines this data as follows:

• In the Customizing activity Determine Local Instrument Code and Lead Times, you define the rules for determining the Local Instrument Code and the related lead times.
• The system uses the current date as the baseline date for determining the lead times in the case of a payment run for SEPA direct debits. For Payment Runs for Direct Debit Pre-notification (F110 only), the system uses the posting date as the baseline date.
• The system also uses the posting date of the payment run as the clearing date of the payment documents.

You can use this BAdI to influence the determination of these date entries:

• If the Customizing settings are insufficient, you can adjust the days for the lead times, the local instrument code, and the calendar.

  To do this, you change the CV_SEPA_ADD_DAYS, CV_INST_CODE, or CV_CALID parameters.

• You can cause the baseline date for the calculation of the lead times to be in the future. This can be useful if, for instance, one or more days elapse between the proposal run and sending the payment media to the bank.

  To do this, change parameter CV_CURRENT_DATE.

• You can fill the clearing date with the run date of the payment.

  To do this, fill parameter EV_SET_CLEARING_DATE with the value X.

There are entries for the current payment in the interface, including house bank account, payment method, payer bank, mandate used and the payment run identification that you can use as a basis for making a decision. 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.

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:

1. 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.
2. On this screen, enter a short description for your implementation in the Implementation Short Text field.
3. 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.
4. Save your entries and assign the Add-In to a package.
5. To edit a method, double-click its name.
6. Enter your implementation code between the method <Interface Name>~<Name of Method>. and endmethod. statements.
7. 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:
8. Choose Activate.
   When the application program is executed, the code you created is run through.

Example

You can find example implementations in the BAdI Builder on the Enh. Spot Element Definitions tab under Implementation Example Classes.

The following example implementations are available:

• CL_SEPA_ADD_DAYS_ADJUST_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