Note: We do not claim that this is an exhaustive list of all the various errors you can have in executing the APP.

Transcription

1 Common Errors and their resolutions in Automatic payment program Runs The SAP Automatic Payment Program (APP) is a powerful facility for single or mass payment of Vendor invoices. The program can be manually executed (F110, F111) or scheduled to run automatically (F110S) and pay vendor open items based on a predetermined parameter selection. In the course of executing this program, users may come across certain errors that may prevent them from completing the process. This post tries to discuss some of those errors, their causes and how to resolve them. Note: We do not claim that this is an exhaustive list of all the various errors you can have in executing the APP. Note also that the automatic payment program can handle both Vendor outgoing payments and customer incoming payments. 1) Company codes xxxx/xxxx do not appear in proposal FA001; correct This error occurs during the automatic payment program run (with transactions F110 and F111). It may be due to one of the following: a) Open item not due for payment This means that the open item you are trying to pay is not due for payment. Meaning that the baseline date of the invoice document is in the future. Execute transaction FBL1N to confirm whether this is the case.

2 As can be seen on the screen shot (above) this open item is not due for payment. Solution: Either (a) wait until the invoice is due for payment or (b) change the baseline date of the document with transaction FBO2 and run the payment program again. But only do this if it is absolutely necessary. b) The invoice document is in park status The invoice document you are trying to pay may be in park status and not posted. Meaning that there is no open item to pay. Check with FBL1N to confirm this. Solution: simply post the document and proceed with the payment. c) Payment request not released If you are executing the payment program with the F111 transaction, this error may mean that the payment request you are trying to pay has not been released. Note: If after executing transaction for payment request (FIBLAPOP or FIBLFFP) and you get the below message, you should release the item for payment with transaction F8REL - Release Payment Requests. Otherwise, if you go ahead to execute the APP (F111) you will get this error Company codes xxxx/xxxx do not appear in proposal FA001; correct Solution: release the payment request with transaction F8REL and proceed with your payment run.

3 Click this to select item for release Click this to release payment Now you can proceed with your payment run Note: that you have to first delete the already created payment proposal and start again. Note: also that if you are the one that created the payment request the system may not allow you to release it if the dual control is active and you may get the message below. Therefore another officer may release on your behalf. d) Conflicting selection between the payment request parameters and the payment run parameters Sometimes your selected parameters in the payment request screen (FIBLAPOP - Vendors - Payment Request or FIBLFFP - Free Form Payment) and that of the payment run (F111) is

4 contradictory. Example in the payment proposal you opted to pay by Swift 103 as a payment method, but when running the payment program (F111) you selected the Check as in the screen shots below: FIBLAPOP Parameters. F111 Parameters If you proceed to edit proposal or will again have this error:

5 This is normally not an issue with F110 as you can over-ride any default made in the vendor master or the vendor invoice data during the payment run. Solution: change your parameter in your payment run to align with the payment request selection. e) No posted document on the vendor There is simply no document posted on the vendor selected in your payment program selection. Solution: no payment can be made on a vendor without open item. f) Vendor master data is blocked for processing This error Company codes xxxx/xxxx do not appear in proposal FA006; correct can also appear if you try to pay an invoice on a vendor that is blocked for processing. Solution: Unblock the Vendor with transaction fk05/xko5 and proceed with your payment 2) No changes possible due to unconfirmed changes to master data It means that before or after the invoice might have been posted to the affected Vendor someone made changes to one or more of the sensitive fields without confirming the changes before the automatic payment program run. When a change happened to the vendor master data after an invoice is posted to it or during the payment run, the system locks the vendor and the payment program would not be able to pay any open items on it.

6 Solution: Confirm the vendor with transaction FK08 and run the payment program again. Note: that the one that make the changes to the vendor master data cannot be the one to confirm it (dual control principle). This is a standard control of SAP in vendor master data maintenance.

7 Note: also that you do not need to go out of the payment run or delete your payment proposal. Just confirm the vendor and proceed. 3) Only the following accounts can be used: xxxxx This error most likely mean that the House Bank Account you used in your Payment Run has a different currency from the invoice you picked to pay. Here, because this house bank has another account under it that has the same currency with the invoice selected, the system is proposing that account for you to pay from.

8 Solution: You may choose to accept the proposal of the system or selected another house bank and account that fits the criteria and pay from that.

9 4) Commitment item xxx/0000// does not exist You have implemented the funds management module (SAP FM), and you created a GL account for (say your house bank) without setting it up as a commitment item. When you implement the FM module of SAP any GL account you created in FI should have a corresponding master data (Commitment item) created in FM. Click on to see the log Note: Initially there is no error message displayed for this, however you know that the payment program was not successfully executed because it does not generate any payment document. It just said: But after going to the log you will find the reason for none payment.

10 Solution: a) Create the commitment item and assign it in the GL master data b) Use transaction FMCIA to create commitment item (we will discuss this in future when we go in to SAP FM) c) Use transaction FS00 to assign commitment item to GL master data Save the changes and go out of FS00. After the above you need to go back and proceed with your payment run by doing the following: Action: a) Delete the payment run (as below)

11 Click on to delete b) Delete the payment proposal

12 c) Delete the payment parameter d) Now run the payment program again (F110)

13 Payment run is now successful. 5) No G/L account has been specified for 1 /usd for the bank account This means that the House Bank Account is not configured for this payment method. Before you can use a House Bank Account in an automatic payment program (APP), the House Bank, the House Bank Account and the currency must be configured in the paying company code and for the selected payment method.

14 This is a configuration issue and will be discussed in detail in the post on automatic payment program configuration. Solution: Send this error to the FI Support Consultant to make the necessary configuration and after which you should proceed with your payment process. Sometimes it may also be that the house bank account you selected has a different currency and there is no alternative one fitting the criteria for the system to propose. If alternative house bank account is available the system will instead issue the following error. This error has already been address in point 3. 6) No variant found for format MT103 This error means that, the selected house bank account is not assigned to this payment medium variant. It should be noted that this error comes after the payment program run is actually completed and payment documents already generated. It is an error that happens in the generation of the selected payment medium. Solution: This is a system configuration issue. Contact your FI Support Consultant do the necessary assignment using transaction OBPM4 after that you can proceed with the generation of the payment medium. Automatic payment method configuration will be discussed in detail in later blog postings.

15 7) Account is contained in proposal FA002, release not possible This error may appear when one of the vendor in the current payment run is locked in an earlier payment run by another staff or even yourself. When you run the payment program but for a reason it remains incomplete, then the vendor(s) in this payment run is locked. Solution: a) Either delete the earlier payment proposal locking the vendor ( how to delete the payment proposal and payment parameter has just been demonstrated above) or b) Go and complete the earlier payment run, and then proceed with the current run again. 8) Some key information missing in the Vendor Master Data If in your Automatic payment configuration (FBZP), you specify that certain fields (street, postal code, P.O. Box etc.) will be required for a particular payment method (example Swift MT103), then these fields must be maintained in the master data of the vendor you are trying to pay. Otherwise, the system may give errors like Required address data missing; please maintain as below.

16 Solution: Use transactions FK02, or XK02 to maintain the master data and proceed with your payment. Note: Automatic payment program configuration will be discussed in a later post. 9) Payment method X not defined in company code This error occurs when you are paying a vendor invoice with a payment method that is not defined in the paying company code. Before you can use a certain payment method in a company code that payment method must be define in the Automatic Payment Program (APP) configuration. Solution: This is a configuration issue, please contact your SAP FI Support Consultant. Proceed with your payment after the correction. Alternatively, change the payment method and proceed with your payment. 10) Posting period xx xxxx not possible for company code xxxx

17 This error simply means that the posting period that the system is trying to access is not open. If relevant posting period is not open the system will give this error as you try to create a proposal. Solution: Use transaction OB52 to open the posting period.