Duplicate Payment Medium Creation

Hi All,
We are using Payment Medium workbench format ACH forone of the payment methods. When we do payment run F110 with this payment method, we are seeing a check box "Create Payment Medium" even during payment proposal run. If a user is checking this box during payment proposal it creates a payment medium file.
Note: this check box is there even when I am not entrying print-variant.
Hence, we run the risk of creating payment medium twice, once during payment proposal and second time during a payment run. Is there a way, we can suppress this check box "Create payment Medium" during payment proposal .
Thanks
Ron
Edited by: Ron on Jan 7, 2010 4:49 PM

Hi Smita,
This is helpful.
Just to be clear, Do we need to enter a different File Path for proposal in the Custom functional module (event 21) itself (which is separate from the path entered in FBPM selection variant for format ACH). Please let me know
Thanks
Ron

Similar Messages

Warning: Check whether a duplicate payment medium

Dear All
Does anyone come across the following error/warning when running F110 for the payment method of bank transfer e.g. "T"?
When I run F110, the part until to the generation of payment document is fine. But after the printout run, and when I tried to display my "own spool request". The first line always display a error describing about a warning :"Check whether a duplicate payment medium has been created"
When I go back to F110 to read the log about the "payment run" and "print job", I can see there 1 DME file being generated for payment and 1DME file for the print job. Why? Any hints whether the things go wrong?
Best Regards
João Fernandes

Long text of the message has enough information I think.
Comparing below fields , you have duplicate record in table REGUH REGUT.
Paying company code
Bank country
Payment run (date and ID)
Data medium format
Total amount and currency
Edited by: Pawan Kesari on Feb 16, 2010 6:53 PM

Dynamic Filename in Sel screen for Payment Medium Creation program SAPFPAYM

Hi,
We have a requirement to provide the dyanamic filename on the selection screen of payment medium program SAPFPAYM. The filename should contain the concatenation of date and time stamp.
For eg. it should be something like CLIENTNAME.ACH.PY<YYMMDDHHSS>.TXT.
Do we need to write the code in any of the custom event in the transaction OBPM3 to acheive this requirement OR Can anyone of you suggest me an alternate way to acheive this dyamic filename selection functionality.
Thanks!
Rupesh

Thanks Henri
I have used the same method to implement this. I have awarded you point for this as well.
Thanks,
Rupesh

APP -f110 Payment medium creation

Hi Gurus,
We are having problem with payment medium in APP. It's being generated at proposal, payment run and Print out. Every time we run this individual step the system won't let us run it without selecting payment medium. As a result there are three DME files are created.
Now we are going to automating the email remittances and we don't want three email remittance going out each time to same supplier.
We just want the payment medium should be created once at payment update run.
Can anyone throw some light on this?
Your expert advise would be highly appreciated.
Thanks
Sam

To my understanding Payment medium gets generated only if "Payment medium" check box is selected in pop up which appears when we run click proposal run or payment run button. In that case, you should not flag this check box during proposal run.
Print programs are generally integrated to Payment run, hence you need not run print program again for DME files. This happens at the payment run automatically provided valid variant is attached in print parameters.

Payment Medium creation Out put ?

Hi Experts
When ever i run the payment proposal with the payment medium option also it is generating the DME file in the spool with out the immediate out put.
It used to create the DME file generation directly with out this issue before.
I went to User defaults in SU3 and tick marked the option Out put Immediately.
Then also the message is coming up.
Please let me know how to fix this part.
Thanks
Meenakshi.N

Hello
Sometimes even when you deactivate in open selection, the authorisation precede the output.
Please check with BASIS for deactivation to your profile.
Reg
suresh

Duplicate payments in Payment list of F110 payment run

Hello all,
We had run APP trhu F110 payment run was as expected with amount 100000 EUR but when we checked payment list (EDIT- Payment - Payment list) there are duplicate entries and total is showing as 200000 EUR.
Following are onservations
1) In SAP posting made correctly to all vendors with a total of 100000 EUR. So no double payments posted in vendor account
2) Payment list is showing amounts with a doument numbers. Duplicate payments also having document numbers but which are not exists in SAP
3) Documents posted with doc type ZP in sap is not in serial i.e 1,2,3,4 Its posted like 1,3,5,7... the document no 2,4 can be seen in the payment list
4) Also I checked log for the payment run and I found one warning message as "Check whether a duplicate payment medium has been created"
5) Also status of payment run is "Posting orders: 1,174 generated, 605 completed"
6) I also checked setting in FBZP which is also correct
We need to correct the DME file with correect postings
If anyone has faced issue then please share your inputs
Thanks & regards

Dear Rajan,
the payment document validation works as follows:
If you select this parameter, a form is only printed if the related
payment document has already been posted.
Note that it is not advisable to schedule the payment program and the
data medium programs to run at the same time, if you want the system to
be able to carry out validation of the payment documents - because the
system does not start posting the documents at the same time as the
program runs, and in order to ensure that the payment program generally
finishes its run before all the payment documents have been posted, the
payment medium program (started after the payment program) would display
in the error list any documents that have not (yet) been found.
As a result double payments are not possible as no payment media is
created if the payment document is not posted. The items are still
open and are selected in the next payment run again.
If the payment document validation is not used, the payment media is
created but the open item is not cleared as the payment document is
not posted. In this case you have to clear the open items manually
(if a repeat update is not possible) to avoid double payments.
dear Prashant,
It is normal that if the automatic payment does not pay all the items, You can find them hanging into sm13.
However, in general, when this happens you could try to use the edit >
payments > after termination > draw up again option, if it is
available. If there is an entry in SM13, as in Your case, you should process it.
But sometimes the System does not allow to do it.
Anyway the only problem I can see is the one reported by the note 545340:
When the payment program is terminated, it may be the case that not all
payment documents exist on the updated database while the entries
already exist in the tables REGUH and REGUP. However, this basic
procedure has the advantage that the payment media can already be
created for the purpose of fast forwarding to the bank when for example
the payment documents update is delayed.
For this problem please refer to the Note 545340 point [4]
that answers to it.
Furthermore please be aware that:
as I told You in the beginning, If the payment program does not pay
all the invoices contained into the payment proposal, It will depend on
the fact that during the payment proposal run time and the payment
proposal time, something changed respect one of the selected invoices.
This means that one document number was NOT posted even if It is
contained in the tables REGUH and REGUP.
Please be informed payment data tables REGU* are used by only payment
program and no need to take any corrective action and should not be a
problem with auditors.
So You can pay the invoices manually or by the next automatic payment
run without any problem.
I hope now the System behaviour is more clear.
Mauri

Payment medium mt103 format

Hi,
i am working on DME(Data Medium Exchange), with the MT103,
and the function module linked is Z_FI_PAYMEDIUM_MT103_31.
my problem is when i try to debug and change the customized FM .. ..moudule,
i am not able to locate the program...how is this FM is getting called.
and i am running the payment medium through F110 T-code.
pl.help..
Thanks&Regards
Harikumar.p

Hi,
Thius reply may be a bit late but I had a similar problem and this is how I went about it, I assume you are utilisng the payment medium workbench.
To be able to debug or step through your custom FM or any other FM used to produce payment media with the payment media workbench you'll have to call the payment medium program inetractively (online or manually). The reason you're not able to step into the FM is because during payment medium creation with F110 the payment program is called using a background job and I think you can't debug a program that's executed in the background.
In short execute program SAPFPAYM_SCHEDULE specifying your payment run ID and date. hope this helps
Andy.

How to process Customer format parameters with Payment Medium Workbench

Hi
I have one bank transfer scenario PC00_M99_FPAYM requiring supplying a payment using the French format FR_ETEBAC_CRT_DOM but the execution date of the bank transfer should be replaced by the banku2019s value date. I planned to enter this required date using the Customer format parameters when running PMW.
The issue I tried to solve is described here below.
How to extract the Customer format parameters assigned to the payment medium format FR_ETEBAC_VRT_DOM when processed by the Payment medium Workbench in order to fill the Customer specific user-defined fields (ZREF01 to ZREF10 in structure FPAYHX)?
I noticed the event type 06 authorizes function modules similar like FI_PAYMEDIUM_SAMPLE_06 but the customer format parameters are only available at low level in function module FI_PAYM_MEDIUM_OPEN (example gc_format_params_c)
Can someone help on this matter? That would be great.
Thanks in advance,
Henri.

Just sharing my findings and proposed solution.
This worked
The expected date is the value date/payee's bank.
This date is created by the bank transfer program prior to be processed by Payment Medium Creation Tool (SAPFPAYM)
According to functional investigation it sounds like the bank transfer program does not allow working with the value date/payee's bank.
The investigation has been done in the Payment Medium Creation Tool. It allows adding the required value date/payee's bank into a customer format parameter.
Required configuration and development:
- Clone the current sap format FR_ETEBAC_VRT-DOM into a new Customized format ZFR_ETEBAC_VRT-DOM
- Clone the corresponding DMEE object FR_ETEBAC_VRT-DOM into a new DMEE object tree type PAYM ZFR_ETEBAC_VRT-DOM
- Create a new data structure: ZFR_Bank_Transfer with field CRVAL Value Date at Payee's Bank (comp type PRQ_CRVAL)
- Assign customer structure ZFR_Bank_Transfer to payment format ZFR_ETEBAC_VRT-DOM and declare field CRVAL as required field
- Build function module ZFI_PAYMEDIUM_06_FR in charge to extract value date/payee's bank from the customer structure and move it to the customer specific user-defined field ES_FPAYHX_CREF-ZREF01
- in new DMEE object tree type PAYM ZFR_ETEBAC_VRT-DOM Replace Source field FPAYH-ZALDT by FPAYHX-ZREF01 in the header record

IHC Duplicate Payment Request

Dear All,
I have an interesting scenario for IHC. Is there a way of checking and stopping duplicate payment requests.
My scenario is as follows:
Step 1: Execute payment run for subsidiary for external vendor payments (F110). This creates an IDoc and is sent to the clearing partner.
Step 2. IHC: - Post the payment order in IHC. This creates the payment request for the specific vendor. All nice and good.
Step 3. Now, someone resets and reverses the document posted at the subsidiary (FBRA). This creates open items again on the vendor.
Step 4. Executes payment run for subsidiary for external vendor payments.
Step 5, IHC - Post the payment order in IHC creating duplicate payment requests.
Step 6. Execute payment run for external vendors at IHC - F111.
Step 3 and 4 should not be done under normal circumstances.
How do I make sure that should step 3 and 4 be executed by the subsidiary, I will be able to detect the duplicate payment request to stop creating the second payment request.
Please see attached for this example of duplicate payment requests.
Your suggestions are most welcome.
Regards,
Godhelp

You can add a custom validation to fail payment request creation in head office if there is already an existing payment request with same Reference number (XBLNR), transaction amount (PAMTF), transaction currency (PACUR) & payee which is still not reversed (XREVE is blank).
Alternatively, while reversing payment document in subsidiary, check for status of payment order it created originally in IHC. You can find Subs company code + payment document number in AWKEY in IHC_DB_PN table and then read the status. If the status is "D4" then allow reset and reversal of payment document else not.

No payment mediums created (FPY1)

Hi All,
I have been trying to run FPY1 and i am facing some issues.
where as after i run FPY1 i have items cleared.
Log after i run FPY1 is as follows:
Job started
Step 001 started (program SAPFKPY3, variant &0000000000063, user ID F24494A)
Format ZENEL: No payment mediums created
Job finished
Log after i run payment medium program 'SAPFKPY3'
Long text for >Format ZSAPFD: No payment mediums created
No payment media were created for payment group 101 for format ZSAPFD.
I'm not sure where or how to correct this.It may be a very silly question, but would appreciate any help.
Thanks,
Venkat

Hi Venkat,
When you are performing a FPY1 run followed by running the payment medium program SAPFKPY3, depending on the business requirement , flat file\IDOCS get generated which is send to the payment agencies, normally banks or any financial institutions to process the same at their end.
In your scenario, the payment medium program is not able to run because there is no payment medium format assigned to the payment method for which you are performing the FPY1 run.
You need to configure the Payment medium format by doing the following SPRO configs-
IMG->Financial Accounting->Contract Accounts Receivable and Payable->Business Transactions->Payments->Incoming/Outgoing Payment Creation->Define Payment Methods
In this config, you need to select the country first and then select the payment method and click on the dispaly icon.and then you need to assign the payment medium that you have created.
IMG->Financial Accounting->Contract Accounts Receivable and Payable->Business Transactions->Payments->Incoming/Outgoing Payment Creation->Define Specifications for Paying Company Code
Here select the company code and then maintain the Payment medium format for the same .
Hope it helps..
Thanks,
Amlan

F110 - payment medium generation too fast ?

Hello
I want to share with you a new behavior we are having from time to time with F110 automatic payment.
we are generating a payment medium (SEPA_CT).
Sometime SAP can not generate the payment medium file, saying it can not find the FI document (that was just generated in first step of payment).
once finished, we run again the generation of payment medium, and now it's able to generate the payment medium with no problem.
is there someone else have / had this problem ? is there a way to solve this issue ?
Thank you All

Hi Tamim,
I hope this would be some help to you.
Cause :
Payment program and payment medium program were scheduled together,The payment program SAPF110S has not yet generated all payment documents for the payment run, but the payment medium program SAPFPAYM/RFFO* has already started to create a PMW file.
Solution recommended by SAP in Note 1896498 - F110: Error BFIBL02167 and 1922823 - F110 F111 Schedule payment media immediately w/ validation (attached):
If you schedule the creation of payment media together with the payment program (F110 or F111), you cannot activate payment document validation.
Schedule the payment medium printout AFTER all payment documents were created. Please, pay an extra attention that if the checkbox "Payment document validation" is set, the payment medium program should not be started together with the payment run program.

DMEE error (Error Log - Too many payment mediums created for this payment group)

Hi Experts,
Please see the below error while generating the DMEE file.
Error Log - Too many payment mediums created for this payment group
Error is - Too many payment mediums created for this payment group
Please explain how to resolve this error.Send detail documentation how to rectify this error
Regards
Sreedhar

Hi Nimish Agarwal,
With reference to the error faced i.e. BFIBL02160 "too many payment
mediums created for this payment group", please review the information
provided in the long text of this error in detail.
Please ensure that the orders are not carried out several times.
Alternatively you can apply the optional usable message 166 (same
class: BFIBL02), so that you can prevent creating duplicates in future.
Please customize this message as an error so as to prevent the system
from creating duplicate files. You can customize this message in OBA5.
The message BFIBL02 160 always occurs, if you create more than one
file for the same payment run, in order to warn you not to send the
same file twice to the bank.
The SAPFPAYM program does not create 2 files at once. But if you
run this program more than once for the same payment run, more than
one file is created. From the second run on you receive the error
message BFIBL02 160. You can easily test it, by creating a new
payment proposal and creating a new file with this proposal and
SAPFPAYM. The first time you run this program you will not receive
the message.
Hope this clarifies.
Kind Regards,
Fernando Evangelista

Payment Medium Format

Dear Friends,
After customized format tree created in T.code DMEE1, where and how can we attach this Payment Medium format to payment media program (RFFOM100).
After the f110 is completed, dmee is used and we have to download the Payment Medium file format according to the client specified format.
All the help will greatly apprecaiated.
Regards
Sridhar

hi,
before this you should configure a payment method ( T code OBVCU) , for payment data (DME) as per your client bank format. while creating payment method choose the payment medium program as RFFOM100. To generate the file, you have to run the APP this payment method.
After the payments have been successfully posted, you can go to DME administration and with the help of dme manager download files on your PC. SAP has determined that the standard print programs for automatic payments will no longer be supported, and they will be replaced by transfer structures created by a tool called the DME Engine.
This tool enables the business to create DME output files without ABAP development, and can be attached to a print program and form for the creation of Payment Advices.
Outside of the DME Engine (DMEE), the majority of the configuration takes place within the following
IMG Path: Financial Accounting -> Accounts Receivable and Accounts Payable -> Business Transactions -> Outgoing Payments -> Automatic Outgoing Payments -> Payment Media -> Make Settings for Payment Media Formats from Payment Medium Workbench Config
Assign Selection Variants
IMG -> Financial Accounting -> Accounts Receivable and Accounts Payable -> Business Transactions -> Outgoing Payments -> Automatic Outgoing Payments -> Payment Media -> Make Settings for Payment Medium Formats from Payment Medium Workbench -> Create / Assign Selection Variants or transaction
OBPM4..select your format that you are using
Check in FBZP config that all is linked!
Start with FBZP, create all there than go to DMEE either to create your own format or use the standard ones.. than go to the menu path above and work through from create to assign...
most of the work lies with payment method, and after running APP create the varient for the programms which are required.
regards,
rajendra

Error Log - Too many payment mediums created for this payment group

Hi Experts,
When I am doing payment to customers through T-code F110, I am able to clear the open item. But when we are executing the Payment medium - DME Administration, generate the Payment Advice and when we see the print preview of the Payment Advice in spool request, System is showing the following errors,
"BFIBL02160 Too many payment mediums created for this payment group"
"BFIBL02616 End of log for payment run 20120123 / NAA02 , NSD / 200"
"This is line 1/column 45 on page 1"
Message no. SP01R116
Kindly help how to rectify the same
Thanks in advance
Regards,
Nimish Agarwal

Hi Nimish Agarwal,
With reference to the error faced i.e. BFIBL02160 "too many payment
mediums created for this payment group", please review the information
provided in the long text of this error in detail.
Please ensure that the orders are not carried out several times.
Alternatively you can apply the optional usable message 166 (same
class: BFIBL02), so that you can prevent creating duplicates in future.
Please customize this message as an error so as to prevent the system
from creating duplicate files. You can customize this message in OBA5.
The message BFIBL02 160 always occurs, if you create more than one
file for the same payment run, in order to warn you not to send the
same file twice to the bank.
The SAPFPAYM program does not create 2 files at once. But if you
run this program more than once for the same payment run, more than
one file is created. From the second run on you receive the error
message BFIBL02 160. You can easily test it, by creating a new
payment proposal and creating a new file with this proposal and
SAPFPAYM. The first time you run this program you will not receive
the message.
Hope this clarifies.
Kind Regards,
Fernando Evangelista

Payroll - How to set RUN DATE in Payment Medium Workbench

Hi experts,
is it possible to set the run date in the payment medium workbench? Normally the run date is the same as the creation date. If I just try to fill in the timestamp and use another run date, no medium will be created until I set the run date = creation date.
But if I want to create the DTAUS-file now and want to set the date of the bank transfer (which is the run date, isnt it?) for the 27th of november, how do I do that? Is it possible at all without modifying the report PC00_M99_FPAYM?
Thanks for you help in advance.
Dirk

Hi Dirk,
We have a similar problem to this. Could you please advise whether you have found a solution to this without making changes to the program itself?
Many thanks,
Rita

Duplicate Payment Medium Creation

Similar Messages

Maybe you are looking for