SAP Knowledge Base Article - Public

3742742 - Value date/Due date for SEPA DD

Symptom

Due Date/Value Date calculation with Lead Times in configuration activity Determine Local Instrument Code and Lead Times for Proposal and FRST 

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental." 

Environment

SAP S/4HANA Public Cloud Edition 

Resolution

  • Current base date is either actual system date/Created on (non-working day) or next working day

  • In Example shown below Days is set to 2 (i.e. Lead Time for SEPA Direct Debits (in Days) Number of days before the date on which SEPA Direct debits are executed, by which the bank must have received the file) in configuration activity Determine Local Instrument Code and Lead Times (ID 105971) 


    The application will calculate the Value Date by current base date + 2 days, then compare it with the Posting Date maintained in Proposal Parameter:
    - If Posting Date <= calculated Value Date, the Value Date determined equals the calculated Value Date
    - If Posting Date > calculated Value Date, the Value Date determined will be the first working day (either Posting Date itself or next working day)



Scenario 1: Calendar 01 maintained

To View Calendar See Configuration activity
 Maintain Calendar (ID 180007)

Select radio button Factory Calendar -> Display. Choose Calendar ID for example 01 -> Display Calendar 

 





Configuration activity Determine Local Instrument Code and Lead Times (ID 105971)




Payment created on system date (SY-DATLO) (04/03, holiday)

  • Current base date is 04/07 (next working day)
  • The calculated Value Date is 04/09 (04/07 as next working day + 2)
  • The determined value date table

Run Date / Posting Date

Current base date

Value Date/Due Date determined

04/03

04/07

04/09

04/05

 

04/09

04/07

 

04/09

04/09

 

04/09

04/10

 

04/10

04/11 (weekend)

 

04/13



1. Run Date/Posting Date: 04/03



2.  Run Date/Posting Date: 04/05




3. Run Date/Posting Date: 04/07




4. Run Date/Posting Date: 04/09



5. Run Date/Posting Date: 04/11 (weekend)




Scenario 2: No calendar maintained

If you have not defined a calendar, the system uses the EU calendar 





Configuration activity Determine Local Instrument Code and Lead Times (ID 105971)

Payment created on system date: 04/03, (working day)

    • Current base date is 04/03 (working day)
    • The calculated Value Date is 04/07 (04/04 ~ 04/05 weekend)
    • The determined value date table

Run Date / Posting Date

Current base date

Value Date/Due Date determined

04/03

04/03

04/07

04/05

 

04/07

04/07

 

04/07

04/09

 

04/09

04/10

 

04/10

04/11 (weekend)

 

04/13

 

1. Run Date/Posting Date: 04/03



2. Run Date/Posting Date: 04/05



3. Run Date/Posting Date: 04/07

4.  Run Date/Posting Date: 04/09



5. Run Date/Posting Date: 04/10




6. Run Date/Posting Date: 04/11 (weekend)




For RCUR, the current base date should be the first usage date of SPEA.



Keywords

V_FSEPA_INST_CD, SY-DATLO , KBA , FI-FIO-AP-PAY-2CL , Payment Apps (Public Cloud) , How To

Product

SAP S/4HANA Cloud Public Edition all versions

Attachments

Pasted image.png