two payment runs: first and recurrent for SEPA mandates

[Former Member]

Dears,

I'm using traénsaction FPY1 to run payment for sepa direct debit. I would like to generate two payement files:

one for the FIRST time excution for mandantes with 5 days as due date

another file for RECURRENT execution of mandates with 2 days as due date.

How can configure this situation in order to make difference.

At this moment, with the current set up all mandate are grouped together.

Thanks in advance,

Thierno

[Former Member]

You can configure two different payment methods and get them assigned to their respective contract accounts.  On the FPY1 you should be able to set up variants based on Due date and their corresponding payment method as selections which will result in two separate files.

[AmlanBanerjee]

Hi Thierno,

Check this thread http://scn.sap.com/thread/3297892

Thanks,

Amlan

[Former Member]

Thanks all for your answer.

Note, only one payment method is defined for SEPA, that is 'S'. At moment,

when the t-code FPY1 is run first and recurrent mandate are selected in the same file.

@Amlan:
I read your explanation about the issue, it looks very interesting but I'm sure
that I understand all.

You said: “When the Due Date(E_AUSFD) in this Function Module is exactly two days after the Payment Run Date ID (I_DPAYC-LAUFD) then all Records in I_MANDATE where I_MANDATE-PAY_TYPE = 'N' should be eliminated.”

What is the Function Module you are talking about ?

Is I_DPAYC table name ? 

Is I_MANDATE a table name ?

I couldn’t find those objects in my system.

Which transaction are you using to enter Payment Run Date ID ?

I’m using only program SAPLFKKAKTIV2 (transaction FPY1) to schedule the job for FICA payment run.

I read that a sap note should be release in Q2 2013 to solve this issue, but I could find it yet.

Thanks in advance for any ideas or useful links.

Thierno

[AmlanBanerjee]

Hi Thierno,

I would recommend you to enhance event 0601 for your requirement.

Event 0601 is processed after the open item selection, but before the payment method selection. This means that you can deactivate items from the group such that the balance of the group changes.

By changing field XAKTP_0601, you can activate or deactivate items. You can also enter an item indicator and lock reason

So based on the due date, you can activate or de-activate the items and can generate two separate payment runs for first time and recurring time mandates.

Hope it helps.....

Thanks,

Amlan

[Former Member]

Thanks, Amlan for your replay.

In your other post: http://scn.sap.com/thread/3297892, you advice notes to install.

can you tell me the excact notes we maybe need.

Thanks in advance,

Thierno

[Former Member]

Dear Thierno,

I've asked the SAP team for this question as I appear to have the same need.

It seems that in order to generate 2 separate files (FRST and RCUR), you need to execute separate payment run. It makes it logical if you want to have specific posting date that are different for RCUR and FRST payments.

Another solution is, in the transaction DMEE,  to fill DPAYH-SRTF1 (format-specific

sorting of payment data). This is done in payment medium event 00.

Doing  this you can sort the XML file as example like this:

- mandate type (B2B/ not

B2B)

- sequnce type (FRST/RCUR)

- collection date (AUSFD)

See note 1550902

I have not tried this yet so I can't assure you that it works.

I would really appreciate if you would share any other findings on this subject (Events to use...)

Hope it helps,

Anaïs JAUSSAUD

[Former Member]

Hello Anaïs,

thansk for your replay. I'll try this and come back to if any soilution found with this or another idea.

Regards,

Bassamba

[Former Member]

Hi Anais,

Can you give me the right event number as event 00 you specified does not exist.

thanks,

thierno

[Former Member]

Dear Thierno,

This event exists in the standard format. Transaction /FQP3 then SEPA_DD and there is the event 00 : FKK_PAYMEDIUM_EU_SEPA_DD_00.

I have not tried this solution yet for the specific SEPA format that I use so I can't unfortunately tell you more about this solution.

However, I've seen that SAP just realeased a new note on this subject Note 1825967 - FI-CA / SEPA: Mandatsfelder in Zahlungsdaten / Sortierung but i don't know if it helps more.

For our concern, we are thinking of using two payment runs for separating FRST and RCUR as the posting date is different for both payments and FPY1 allows one posting date per run.

Regards,

Anaïs

[Former Member]

hi,

In the solution above given by Alan, he's speaking about I_MANDATE, but i cannot find this object in event 0601.

I assume that it is not ht right event, can anyone advice ?

Regrards,

[AmlanBanerjee]

Hi Thierno,

You will find the parameter I_MANDATE in event 656.

Thanks,

Amlan

[Former Member]

Hi alan,

thank you for your replay,

But when I'm in event 601, I nocited that event 656 is not yet start, when I run payment program (transaction FPY1)

How can you manage to start event 656 before event 601 then ?

Thanks in advane,

Thierno

[AmlanBanerjee]

Hi Thierno,

I dont think you would require to enhance event 656 for your requirement.

I would recommend you to only enhance event 0601 for your requirement.

Event 0601 is processed after the open item selection, but before the payment method selection. This means that you can deactivate items from the group such that the balance of the group changes.

By changing field XAKTP_0601, you can activate or deactivate items. You can also enter an item indicator and lock reason.

So based on the due date, you can activate or de-activate the items and can generate two separate payment runs for first time and recurring time mandates.

Hope it clarifies...

Thanks,

Amlan

[Former Member]

Dear all,

here is the latest reply from SAP to the question on how to separate files FRST and RCUR:

the coding from note 1657294 makes it possible to pass mandate information to event 0655. If the note is not implemented you should do so.

If you  want to separate FPY1 for FRST and RCUR you will need

additional customer  function module for event 0655 with coding like above:

You have to copy sample function module FKK_SAMPLE_0655 to customer

function

module and implement coding like this:

FUNCTION

ZFKK_SAMPLE_0655

CASE I_BASICS-MACAT.

WHEN 'FRST'.

IF I_SEQ_TYPE NE

'FRST'.

* add a message to the application log if wanted

T_MESSA_KK-MSGID

= 'ZZ'.

T_MESSA_KK-MSGNO = '100'.

T_MESSA_KK-MSGV1 = 'Not

FRST'.

T_MESSA_KK-MSGTY = 'I'.

APPEND T_MESSA_KK.

E_RESULT-POKEN =

'006'.

ENDIF.

WHEN 'RCUR'.

IF I_SEQ_TYPE NE 'RCUR'.

* add a message

to the application log if wanted

T_MESSA_KK-MSGID = 'ZZ'.

T_MESSA_KK-MSGNO

= '100'.

T_MESSA_KK-MSGV1 = 'Not RCUR'.

T_MESSA_KK-MSGTY = 'I'.

APPEND

T_MESSA_KK.

E_RESULT-POKEN = '006'.Kind

regards,

ENDIF.

ENDCASE.

ENDFUNCTION.

I am working on it this week, I will let you know how that works. Please do the same if you do this.

Regards,

Anaïs

[janvandenveldenbzk]

Hello,

Anyone already got this working?

Kind regards,

[former_member201285]

Hello,

if anybody uses FI-CA 606, install note 1837361 first. Otherwise, the import-parameter I_SEQ_TYPE might be missing here - I had been very confused about it!...

Kind regards,

Ulrich

[former_member201285]

Hello,

we have already gone live with SEPA for a small data pool, and the solution with exit 655 works perfectly. Consider, that this exit is also called for a non-SEPA-payment, if you use both methods  (SEPA and non-SEPA) in parallel.

Kind regards,

Ulrich