01.05.2017 Views

534857304

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 14 ■ Defining FI Accounts Receivable and Accounts Payable<br />

Update the following fields:<br />

Block Ind.: Enter your payment block reason key in this field. This is usually<br />

defined using a single-digit character. In this exercise, we used K as our payment<br />

block reason key for illustration purposes. This key is a freely definable payment<br />

block reason key. You can use any key of your choice.<br />

Description: Enter a meaningful short statement describing your payment block<br />

reason. As an example, we used Payment Block C900 as our payment block<br />

reason. You can use any meaningful description of your choice.<br />

Change in Pmnt Prop.: When you select the change in payment proposal<br />

checkbox, the payment block cannot be removed during an automatic payment<br />

program run.<br />

Manual Payments Block: Documents defined with a payment block key cannot<br />

be cleared during manual payment processing.<br />

Save<br />

your work.<br />

Manual Outgoing Payments<br />

Manual Outgoing Payments allow users to manually post vendor’s payments and clear open items on the<br />

vendor’s account against payments made. You will be looking at manual payments in depth in Chapter 17. In<br />

order for users to be able to perform manual outgoing payments, you must:<br />

• Define tolerances for vendors<br />

• Define reason codes for manual outgoing payments<br />

• Define accounts for payment differences<br />

Define Tolerances for Vendors<br />

Three tolerance groups are maintained in SAP FI. We covered the employee tolerance group and the G/L<br />

account tolerance group in Chapter 4. This section covers the Customer/Vendor tolerance group. For more<br />

information on tolerance groups, refer to Chapter 4.<br />

As mentioned, tolerances are simply control mechanisms that are designed to limit the amount input<br />

clerks are permitted to post to the system. It also serves as a control measure that determines the discounts a<br />

clerk is authorized to grant, the payment differences they are permitted to post in the system, and tolerances<br />

for payment advice. The advantage of setting tolerances is that they impose restrictions and help avoid major<br />

posting errors by clerks or users. Since tolerances are valid for group of business partners, the settings in this<br />

exercise are applicable to several customers’ and vendors’ tolerance groups. This means you don’t have to<br />

create a separate tolerance for vendors and customers; you can group them into one tolerance group.<br />

In this exercise, you will create tolerances with and without a tolerance group key. Tolerances created<br />

with tolerance group key allow users or clerks assigned to this tolerance group to post amounts up to the<br />

specification. Tolerance groups are defined using four-digit characters, which serves as the group ID or key.<br />

The group ID you have defined is assigned to the appropriate object in the system. In this exercise, your<br />

tolerance group ID will be assigned to the vendor/customer master record.<br />

232<br />

Problem: You have been asked by your team leader to create two tolerance groups—one<br />

with a group key and one without a group key—to satisfy the minimum tolerance group<br />

requirement.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!