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

Similar Messages

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

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

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.

Payment medium DME format for Cheque Refunds

Dear Gurus,
We have cheque Refund process in ISU FICA, cheques are not printed in SAP, instead data will send to printwork bench via SAP PI to print the cheques and distribute to customers, which is handled by 3rd Party.
In order to send the data we may have to develop custom payment medium generate DME file, I wanted to check with you if any one has an idea is there any SAP standard payment medium format or function module which enables less development.
Would really appreciate your inputs and thoughts.
I checked by copying International Payment medium CHECK and activated DME format, however am unsuccessful on put. DME file generated with no Data.
Regards
Prab.

Pravakar,
There is no standard DME format for Chq Refunds as far as I know.
In R/3, there is a standard program for Voyager<FCKR>. If you are looking for similar program in ISU, You need to go for customized program.
Also if you want Text file for your Chq Refund, suggest you look into the format of Legacy to understand the format.
If it is similar to BACS Refund file like VOL1, HDR1, HDR2 etc, you can copy the standard FMs
FKK_PAYMEDIUM_BACS_00
FKK_PAYMEDIUM_BACWAY_10
FKK_PAYMEDIUM_BACS_15
FKK_PAYMEDIUM_BACWAY_20
FKK_PAYMEDIUM_BACWAY_25
FKK_PAYMEDIUM_BACS_30
FKK_PAYMEDIUM_BACWAY_40
and tailor suit to your requirements. But again, if this is only a text file for SAP PI, suggest you to look what they are expecting from SAP <like Chq no, amount,date, Customer number>.
In that case you can write a program where it shall use the data base tables DFKKCR*, DFKKOP & FKKVKP.
Coming to FPY1, you may see a DME entry in FDTA for Check but you cannot view it there as it is only a correspondece. Alternatively you can view in Spool.
Hope this is clear and helps.
Rgds
Rajendra

Payment Medium Workbench(PMW) for check printing

Dear experts,
We have recently implemented PMW to speed up our telegrahic transfer (TT) payments to the banks.
All is well so far.
Now we want to include the check printouts as well. Previously when we were using the classic payment medium program, we were able to assign the RFFOUS_C for check printing.
How do I go about doing the same thing in the PMW? Appreciate some pointers.
regards
Sylvia

Hello,
SAP has provided some of the DME structures for different countries. like GB_BACS for GB etc.
If your client is not part of those structure, probably you are required to create your own structure. It also depends on the bank of your client. They may want the file in a different format. Therefore, you need to first talk to the bank and get a sample file in which they need the format.
You can create the DME structure by using transaction code DMEE - Tree Type is PAYM.
You can create the DME structure as a flat file or XML file based on the requirement of your client (bank).
You can also copy the standard structure to Z structure and modify it according to your requirements.
Please also make sure that you have made settings in OBPM1, OBPM2, OBPM3 and OBPM4 (More importantly you should maintain the path where it needs to be downloaded)
Take help of basis consultant in order to create the directories. You can see the directories in AL11.
If there are no directory path maintained in OBPM4, then the file gets saved to temporary directory in AL11.
Regards,
Ravi

Check printing through Payment Medium Workbench

Hi,
Is it possible to print the check through payment medium workbench, just like the classical RFFO*_C program ?
Thanks
Wasim

>
Wasim Habib wrote:
> Hi,
>
> Is it possible to print the check through payment medium workbench, just like the classical RFFO*_C program ?
>
> Thanks
> Wasim
Not yet.. per SAP, PMW will gradually phase out the classic payment medium programs (RFFO*).
~Suresh

Error while running payment medium in f110 Message no. FZ208

Dear All ,
I am getting the following error while running payment medium,
No data records found for these selection criteria
Message no. FZ208
Diagnosis
No data could be accessed for this selection.
Possible causes are:
No data exists for the activated selection.
You have no authorization to display or edit data from this selection.
Procedure
First check whether your selection criteria are correct. You may need to expand the criteria to include a larger search area to check whether data exists in the system.
Make sure you have the proper authorizations for displaying and editing data. Read the Release note for DME management for further information on the authorization objects.
Please note that i have made some changes in the payment media format and saved before that it was woking fine, can any one help me in finding out the error

Hi,
Please verify whether there is no other payment proposal pending for the same payment criteria. Or just follow the following steps for deleting the existing proposal and recreate the payment run alongwith parameters(since you have made changes to the payment media format),proposal and then run the payment:
In F110 select Edit-Proposal-Delete
Edit-Parameters-Delete
Please note,incase we also want to delete the output after the payment is run then we can delete the same through Edit-Payment Run-Delete Output and then proceed with the above steps.
Regards
Sonali T

Payment medium error

Hi Gurus,
When i am trying to download the file after executing F110, i am encountering an error message "No data records found for these selection criteria". This is the first time i am executing payment run for new company code. am i missing any configuration.
Thanks and Regards,
Suresh

SAP has provided some of the DME structures for different countries. like GB_BACS for GB etc.
If your client is not part of those structure, probably you are required to create your own structure. It also depends on the bank of your client. They may want the file in a different format. Therefore, you need to first talk to the bank and get a sample file in which they need the format.
You can create the DME structure by using transaction code DMEE - Tree Type is PAYM.
You can create the DME structure as a flat file or XML file based on the requirement of your client (bank).
You can also copy the standard structure to Z structure and modify it according to your requirements.
Please also make sure that you have made settings in OBPM1, OBPM2, OBPM3 and OBPM4 (More importantly you should maintain the path where it needs to be downloaded)
Complete your FBZP settings - Importantly payment methods in country, select your DME structure.
Take help of basis consultant in order to create the directories. You can see the directories in AL11.
If there are no directory path maintained in OBPM4, then the file gets saved to temporary directory in AL11.
If you are using DME structure, then forget the classic payment medium.
1. First ask the bank for the format, file type etc. Ask bank for any document available.
2. The see for that country if SAP has provided any standard DME structure (Transaction Code DMEE - Tree Type PAYM)
3. If this is not sufficient, then copy the standard DME strcutre and modify it accordingly to your requirement.
4. Assign this DME structure in FBZP - Payment Methods in country. * Use payment medium workbench
5. Check with your basis whether any secured folders are created in AL11 (where the output file needs to get generated) - If not ask them to create.
6.Check your settings in OBPM1 / OBPM2 / OBPM3 / OBPM4 - (In OBPM4 make sure you have given the secured folder path and file name for your variant)
7. Run F110 - Check you have maintained your variant details properly for program RFFOAVIS_FPAYM
If you maintain all these steps correct, hope your DME file should get generated.
Regards,
Ravi

Change the assigned report on payment medium

Hi gurus,
I'm been asked to modify the assigned traditional payment report from RFFO_A to RFFO_D on a certain payment medium and, eventhough the system doesn't populate any error nor warning message, I'm afraid there could happen some inconsistencies, specially on table PAY* tables.
Do you know of any? And in case so, is there any workaround?
Thanks in advance! Regards,
Rushid Rush
Has somebody ever come across this same doubt and has solved it?
Thanks!!

Hi,
As you are only looking for payment document from BSAK, you may filter BSAK document based on document type.. Usually, the document type for vendor payment is ZP but check in your system which document type is set up for outgoing payment document.
Regards,
Chirag

Issue with check generation in Automatic Payment Program

Hi experts,
I need your inputs for an issue with check generation in Automatic Payment Program. Trying to make a payment to a US vendor with payment method C. The due item is getting picked up and a clearing document is getting generated. But Check is not being generated, niether can I see an entry in PAYR table. However, if I try to generate a check manually in FCH5 for the same clearing document, it is working.

Have u checked the Variant created in F110 - Printout / data medium, whether the Hose bank details are correctly set or not.
If yes, check the Printer details
Let us know the results
Thanks

Payment Medium - F110 - RFFOES_D - CBS19 FILE

Hi,
I have a problem concerning TR. F110 - domiciliary receipt ( recibo domiciliário ). The payment medium program is RFFOES_D. Everything is maintained and i can generate a file. The problem is that in TR F110 --> Environment --> payment medium --> DME administration i only can see " exported files " ( the icon appears in that collumn).
I had the same problem when creating with DMEE, i only could see the "second file" because in the Selection variants - TR OBPM4 - there was a check box to choose that.
Is there anything i could do in order to have the same beahaviour but for classic Payment Medium Programs?
for example if you put in google the following search criteria : " Programa automatico de pagos rffoes_d " the first one is a PDF file, in the last page there is the exact beahaviour that i want , concerning the CBS19 file.
Can u please help me, it's very urgent. Full points of course for any help !!
Thanks in advance,
Mário

Hi Naveen,
You need to maintain the variant for the Payment media. Please follow these twh steps to solve the probelm.
1. Check for the payment Methos 'E.' in country whether in OBVCU, a programme for Payment medium has been maintained, if not please maintain the same. For India it is RFFOIN_C.
2. Maintain the Variant for this programme under SE38 and select the same when setup the payment proposal under Printout/data medium.
Your problem will get solved and can see the payment media file generated.
Hope this resolves your issue.
Regards
Bharat

How to generate checks when executing Automatic Payment Program (F110)

Is it possible to generate checks automatically when I execute the automatic payment program? Will reward points to any suggestion. Thanks!

hi patrick
try this.....ur problem may solve.....
Create Automatic Payment Transactions (F110)
Purpose
Use this procedure to generate checks proposals or ACH proposals and then subsequently issue checks or set up ACH files to be transmitted to the bank.
Trigger
Perform this procedure when through either an ACH or a check, a creditor of the University needs to be paid.
Prerequisites
Open invoices with reached due dates have to be present in the SAP system.
Menu Path
Use the following menu path to begin this transaction:
·         Select Accounting Financial Accounting Accounts Payable Periodic processing Payments to go to the Automatic Payment Transactions: Status screen.
Transaction Code
F110
Business Process Information
The automatic payment process will be centrally managed in the Accounts Payable Office. The automatic payment program will be executed each day for all open invoices (across vendors) in the system. There will be separate payment run execution corresponding to each payment method category:
Check payments: clears the open invoices and issues a check output
ACH payments: clears the open invoices and issues an ACH file output
Foreign currency payments: clears open invoices but no output is issued
State/Grant payments: clears open invoices but no output is issued
The process steps executed during the automatic payment program are:
Enter Payment Parameters
Edit/review Payment Proposal
Post Payments
Generate Payment Medium (print checks or create ACH payment file)
Generate Positive Payment File
The payment parameters are entered in order to limit the open invoices and credits selected for payment. It is important to note that the payment terms that are defined on the invoice will drive whether a invoice is due for payment during the current payment run. During the payment program execution, the invoices that are due for payment will be presented to the user on a payment proposal list.
The payment proposal is a list of expected payments grouped by vendor account. Invoices that are due for payment but cannot be paid due to some kind of accounting or system error are listed as exceptions. Examples of typical exceptions are missing banking information (for ACH payments) and blocked invoices. Some payment exceptions will be resolved at the Accounts Payable Office. However the Department must resolve some exceptions. When these types of exceptions appear on the payment proposals, the Accounts Payable Office will inform the Department of the blocked payment in order to get a resolution. Key personnel in the Accounts Payable Office will be the only resources to have access to the editing function of the payment proposal processing. Typically, there is no business reason the edit or change a payment proposal. Editing options for a payment proposal includes: changing the default disbursing bank account information or changing the payment method.
After the payment proposals have been reviewed and edited, the proposals are posted as payments. It is important to note that any open credit on the vendor's account is also taken in consideration when creating the vendor's payment. The payment method supplement defined on the invoice will drive the check sorting.
In addition to the printed check output, the payment program run produces an ACH file and a Positive Pay file. Both files are sent to the bank for further processing. The ACH file contains the vendor's payment and banking data. The Positive Pay file contains the check data (check processed, voided, etc) and is used for confirmation of payments.
Helpful Hints
·         The R/O/C column in the field description tables below defines whether the field is required (R), optional (O), or conditional (C).
·         On certain screens you may have to scroll to view some data entry fields.
·         Click the tab to view the current overall status of the payment process by viewing the informational messages.
Procedure
1. Start the transaction using the menu path or transaction code.
    Automatic Payment Transactions: Status
2. As required, complete the following fields:
·         Run date
·         Identification
3. Click the tab.
The payment program parameters are used to limit the program's selection of open invoices and credits.
    Automatic Payment Transactions: Parameters
4. As required, complete/review the following fields:
·         Posting date
·         Docs entered up to
·         Company codes
·         Pmt meths
·         Next p/date
·         Vendor
5. Click the tab.
Free selection criteria are extended parameter selection criteria used to limit the open invoices and credits selected in the payment run.
    Automatic Payment Transactions: Free Selection
6. Perform any of the following:
If You Want To
Then
Select data by a particular field value; use the match code on the Field Name field to obtain the required field
Enter the required field value to be considered in the payment program selection of open items. The field value is entered in the Values field
Payment selection can be based on fields on the invoice or credit memo document or fields on the vendor master.
Example: A (AP payment block)
Exclude the open items that match your field value
Select to the left of Exclude values.
Include only those open items that match your field value
Deselect to the left of Exclude values.
7. Click the tab.
This information is used to expand the information that is automatically recorded in the payment run log. The payment run log is used to diagnose any program errors during the payment run.
    Automatic Payment Transactions: Additional Log
8. Perform the following:
If You Want the Payment Program Log to Record
Then
Information on due date check
Select to the left of Due date check.
Activate this option.
Any payment method selection data
Select to the left of Payment method selection in all cases.
Activate this option.
Line item information the payment documents generated upon posting the payment proposal
Select to the left of Line items of the payment documents.
Activate this option.
9. As required, complete/review the following fields:
·         Vendors (from)
·         Vendors (to)
Enter the same vendor account number range for Accounts required section of the transaction.
10. Click the tab.
The specifications defined in this section of the transaction inform the payment program the correct form to use for check printing and the correct payment file format to use for ACH payments.
    Automatic Payment Transactions: Printout and DME
11. As required, complete the following fields:
·         RFFOAVIS
·         RFFOUS_C
12. Click the tab.
    Exit editing
13. Click to save the data.
If you want to delete the payment program parameters entered, select Edit Parameters Delete.
    Automatic Payment Transactions: Status (2)
The system displays the message, "Details have been saved for the run on XX/XX/XX XXXX."
14. Click .
If you want to refresh the screen in order to view the current status (processing step) of the payment program click at any time.
    Schedule Proposal
15. Perform one of the following:
If You Want To
Then
Execute the payment program (i.e. process the payment parameters entered and create a payment proposal) immediately
Select to the left of Start immediately.
Activate this option.
Designate a target computer
Enter the name in the Target computer field.
16. Click to process the payment parameters and create a payment proposal.
While the payment program is selecting and processing data, the status will display the message, "Proposal is running." When the payment proposal has completed and is ready for review/edit, the system will display the message, "Payment proposal has been created."
    Automatic Payment Transactions: Status (3)
The system displays the message, "Proposal run has been scheduled."
17. Click .
    Automatic Payment Transactions: Status (4)
The system updates the status, "Payment proposal has been created."
18. Perform one of the following:
If You Want To
Then
Go To
Execute the payment run
Click .
Step 19
Edit the payment proposal
Click .
Step 43
Display the payment proposal
Click .
Step 54
Display the payment proposal run log
Click .
Step 57
Delete the proposal
Select Edit Proposal Delete.
Step 60
Display the proposal list in a printer friendly format
Select Edit Proposal Proposal List....
Step 62
Display only the exception (error) invoices or credits
Select Edit Proposal Exception List....
Step 67
Exit this transaction
Step 72
    Schedule Payment
19. Perform the following:
If You Want To
Then
Execute the payment program (i.e. process the payment parameters entered and create a payment proposal) immediately
Select to the left of Start immediately.
Activate this option.
Designate a target computer
Enter the name in the Target computer field.
20. Click to process the payment proposal and post the payment documents.
While the payment program is selecting and processing data, the status will display 'Payment is running'. When the payment proposal posted the status will display 'Payment run has been carried out. Posting orders X generated, X completed. (X will represent the total number of checks produced).
    Automatic Payment Transactions: Status (5)
The system displays the message, "Payment run has been scheduled."
21. Click .
    Automatic Payment Transactions: Status (6)
The system updates the status, "Payment run has been carried out." If you click after seeing the status update, "Payment run has been carried out", the system will display an update to the status, "Posting orders: XXXX generated, XXXX completed."
22. Perform one of the following:
If You Want To
Then
Go To
Review the payments posted
Click .
Step 23
Display the payment proposal
Click .
Step 26
Display the payment proposal run log
Click .
Step 29
Display the payment list in a printer friendly format
Select Edit Payments Payment List.
Step 32
Display only the exception (error) invoices or credits
Select Edit Payments Exception List.
Step 36
Print the payment run information
Click .
Step 40
Exit this transaction
Step 72
    Job Log Entries for F110-XXXX-XXXX / XXXX
23. Review the displayed information.
24. Click .
25. Return to Step 22.
    Display Payment Proposal: Payments
26. Review the displayed information.
27. Click .
28. Return to Step 22.
    Job Log Entries for F110-XXXX-XXXX-X / XXXX (2)
29. Review the displayed information.
30. Click .
31. Return to Step 22.
    List Variant
32. Click .
    Payment list
33. Review the displayed information.
34. Click .
35. Return to Step 22.
    List Variant (2)
36. Click .
    Payment list (2)
37. Review the displayed information.
38. Click .
39. Return to Step 22.
    Schedule Print
40. As required, complete/review the following fields:
·         Start date
·         Start immediately
·         Start time
·         Target computer
·         Job name
41. Click .
42. Return to Step 22.
    Accounting clerk
43. Click .
    Edit Payment Proposal: Payments
44. Review the displayed information.
45. Perform one of the following:
If You Want To
Then
Go To
Continue with the payment process
Click .
Step 18
Review/edit invoice information for the payment (invoice numbers, discounts, payment amounts, etc).
1. Click on the line you want to select.
2. Click .
Step 46
Change the key payment information (payment method, house bank, payee name and address, etc.)
1. Click on the line you want to select.
2. Click .
This option does not work for lines that have exceptions.
Step 51
    Edit Payment Proposal: Open Items
46. Double-click on the line you want to choose.
    Change Line Items
47. As required, complete/review the following fields:
·         Payment block
·         Discount amount
·         Cash discount %
48. Click .
49. Click .
50. Return to Step 45.
    Change Payment
51. As required, complete/review the following fields:
·         Payment method
·         Pmt meth.supl.
·         Due date
52. Click .
53. Return to Step 45.
    Display Payment Proposal: Payments
54. Review the displayed information.
55. Click .
56. Return to Step 18.
    Job Log Entries for F110-XXXX-XXXX-X / XXXX (3)
57. Review the displayed information.
58. Click .
59. Return to Step 18.
    Delete proposal
60. Click .
    Automatic Payment Transactions: Status (7)
The system displays the message, "Data and log deleted."
61. Go to Step 72.
    List Variant (3)
62. As required, complete the following field:
·         Variant
63. Click .
    Payment list (3)
64. Review the displayed information.
65. Click .
66. Return to Step 18.
    List Variant (4)
67. As required, complete the following field:
·         Variant
68. Click .
    Payment list (4)
69. Review the displayed information.
70. Click .
71. Return to Step 18.
72. Click until you return to the SAP Easy Access screen.
73. You have completed this transaction.
Result
You have executed a payment proposal, executed and posted a payment run and printed checks.
reward me points.......dont forget

Payment Medium Probelm.

Hi All,
When I am trying to generate payment medium from F110 I am getting the below error messges.
1) Supplier Country's country key is missing or is not valid
2) SCB(State Central Bank) Indicator is missing or is not valid.
Could you please explain me, is there any customizing is missing or any problem with the documents.
Thanks in Advance
Ranga Swamy

Hi
Please check whether the Vendor's bank account has any bank key defined. If not maintain the same in the Vendor Master - general view. Please note the bank key is specific to the Country key.
Hope this should help you.
Regards
Nambi

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

Warning: Check whether a duplicate payment medium

Similar Messages

Maybe you are looking for