SAP FICO ACCOUNTS PAYABLE Issue-25

Issue No.: 25
The user has executed transaction code F110 to pay 50 vendors, but he only has 20 checks left. Hence, when he ran the program, it printed the checks with random numbers. Now the problem is he is unable to cancel the payments, as there is no check number. How can he reprint or cancel the checks?

The check printing program generated more checks than there are available check numbers. To handle this issue, follow these steps:

1. Before proceeding, ensure that you have maintained a new check lot through transaction code FCHI. Be sure to correct your check lot before you do anything.
2. In transaction code F110, enter the payment run ID and payment run date.
3. Go to the Printout/data medium tab and place the mouse curser on variant field against print program.
4. From the system menu, choose Environment → Maintain Variants

Figure Using transaction code F110

5. SAP R/3 will show the Maintain variant: XXXX screen, at the bottom of which you will see the section shown in Figure

Figure Using transaction code F110

6. Select Void and reprint checks from payment run already printed. This procedure will void all of the checks
generated through this particular payment program.
If you want to void and regenerate a particular set of checks, enter the check numbers you want to void along with a  void reason code.
7. Save the variant and come back to the payment run screen. Click on to

  generate the desired checks.

SAP FICO ACCOUNTS PAYABLE Issue-24

Issue No.: 24
In transaction code F-33 (bills of exchange discounting), the user entered all data. When this is executed, the user receives a message that A/C No. 400400 (Interest account) requires an assignment to a CO object. What does this mean?

When a controlling area is active, the user has to assign a valid cost object while posting expenses. In this case, bank interest is an expenses account, while posting selects a valid cost object.

SAP FICO ACCOUNTS PAYABLE Issue-23

Issue No.: 23
While posting a transaction through T-code F-58, the user sees this error message: "Changes for vendor XXXXXX not yet confirmed."

In SAP R/3 configuration, you define certain fields as sensitive to have proper control and tracking on master data changes. If the user changes these sensitive field(s), someone other than the user who changed the master data has to confirm these changes. Until such confirmation, the SAP R/3 system does not allow any transactions with that trading partner. For example, you configure payment term as a sensitive field. To accommodate business requirements, user XXXXX updates the payment term with a new payment term ID. In order to carry out any transactions with this business partner, the changes have to be approved by another user.

To confirm this change, the user has to use transaction code FK09. Follow this procedure before executing
transaction code F-58.