Reference Data Sets

You begin this part of your implementation by creating and assigning reference data to sets. Make changes carefully as changes to a particular set affect all business units or application components using that set. You can assign a separate set to each business unit for the typeofobject that is being shared. For example, assign separate sets for payment terms, transaction types, and sales methods to your business units.

Your enterprise can determine that certain aspects of your corporate policy can affect all business units. The remaining aspects are at the discretion of the business unit manager to implement. This allows your enterprise to balance autonomy and control for each business unit. For example, your enterprise holds business unit managers accountable for their profitand loss, but manages working capital requirements at a corporate level. In such a case, you can let managers define their own sales methods, but define payment terms centrally. In this example:

Each business unit has its own reference data set for salesmethods.

One central reference data set for payment terms is assigned to all business units.

When you submit a "payment process request", you can enable the Apply credits up tozero amount payment option. Enabling the option causes the payment process to apply credits when the credits reduce the payment amount below zero.

The following scenario illustrate the impact of this option.

Credit Amount Greater Than Invoice Amount

Aninvoice for 200 USD and a credit memo for 225 USD are due for payment.

The following tabledescribes the payment processing that occurs based on the setting for the Apply credits up to zero amount payment option.

Assume that the “Apply Credits Up to ZeroAmount” option is enabled.

Payment processing applies 200 USD of the credit memo to the invoice and creates a payment for 0 USD. The remaining credit is 25 USD.

Payables users can also see general ledger data for all balancing segment values in the ledger.