Lastuse_date Field in the table SEPA_MANDATE is not updated after payment run?

[Former Member]

Hello dear Supporters,

SAP suggests that after each payment run, the relevant mandate Reference is updated in the Table SEPA_MANDATE.

After a payment run the respective Mandate Reference is updated in the SEPA_MANDATE table but not the field "LASTUSE_DATE". This field should be updated so that the client knows when was this mandate reference last used. and in case the "lastuse_date" is older than 3 years, payment run should not allow usage of this mandat reference.

Any idea if this is configurable through customizing?

Release: EHP6 FOR SAP ERP 6.0

Service package: 21.

Regards,

Rashed popalzai

[AmlanBanerjee · Accepted solution]

Hi Rashed,

There are different kinds of scenarios, as to how the field, SEPA_MANDATE-LASTUSE_DATE is updated.

In a normal scenario, when the FPY1 is executed the SEPA_MANDATE table is updated with all the relevant fields.

However, say suppose you have a scenario, where in the SWIFT code is the same and the IBAN of the SEPA mandate has changed intermediately, then in this scenario, the SEPA_MANDATE fields are updated after the generation of the Payment media files and not after the completion of FPY1.

Thanks,

Amlan

[FICAExpert]

Hi Rashed,The SEPA_MANDATE-LASTUSE_DATE should be updated with FPY1 real run. The update is done when filling DPAYH table entries:SE38 LFKPMASSFF0FORM FILL_PAYH.…
PERFORM SEPA_MARK_USED USING 'STD'.
…So you can check in Debugger mode more in detail why the update is not done on your system,.

Kind regards,
Annegret

[Former Member]

Hi Amlan,

thanks for the explaination.

The client's requirement is that if a sepa mandate in the source system has not been used in the last 3 years. SAP should not allow usage of this recurrent mandata Reference.

someone in the project thought it would be good idea to import the lastuse_date because SAP standard already checks this date and if older than 3 years will block the usage.

however, now we know that manuall update of this Feld generates problem. So we will try to solve the problem and requirement through "valid to" Field.

Thanks again.

Rashed

[Former Member]

I should also say that we have another mirror system that is a copy of the system we use. There we didnt migrate new customers, all other configurations are same. and there we dont have a problem. I strongly believe that updating the "lastuse_date" alone in the table SEPA_MANDATE has cause the payment runs not to update this field anymore.

any ideas how to solve this? would updating the SEPA_MANDATE_USE Table too would solve the problem?

Thanks,

[AmlanBanerjee]

Rashed,

The SEPA_MANDATE_USE table, is updated after the FPY1 run and contains the Mandate Guid, date and the payment document no.

This table contains all the list of the payment documents that has been generated against the mandate.

During the FPY1 run, there are consistency checks on these two tables, and if they are not in sync it may lead to the failure of the FPY1 job. Check SAP Note 1888285 and 2160487 for your reference.

You can check the FM, SEPA_MANDATES_USE_DB_UPDATE as well.

Now for new customers who, there is no issue as the first payment run happens from SAP and table SEPA_MANDATE and SEPA_MANDATE_USE are updated asynchronously during FPY1 run.

My recommendation would be to migrate the legacy mandates without the last use date in SAP.

This infers you treat them as a new mandate in SAP and during the first FPY1 run, SAP updates the last use date.

Thanks,

Amlan

[Former Member]

Thank you all,

I should maybe elaborate more.

We have migrated our customers from another system, along with that we had to migrate the Sepa Mandates.

Firs step we updated/created the Sepa Mandate for the customer.

2nd step: we received a file in which we have only two fields "IBAN & Lastuse_date". we then have uploaded these two files again in the table SEPA MANDATES to update the lastuse_date field.

I am not sure why we do it in 2 steps, my guess is in source system the info "lastuse_date" is not available and has to be extracted. Thus we receive an extra file with the info "Lastuse_date".

My theory is that this design is not complete.

I came accross another table SEPA_MANDATE_USE where all the usages of a sepa mandate is recorded. Can it be that during payment run there is a cross check between the tables SEPA_MANDATE & SEPA_MANDATE_USE and if the info does not match, the "LASTUSE_DATE" is not updated in SEPA_MANDATE.

or to put it another way: Can updating the "lastuse_date" in SEPA_MANDATE manually be the problem".

NOTE: SEPA_MANDATE_USE table has not been updated neither. (according to configuration it should have logged the use of mandate reference).