Customer Structure
A significant part of implementing PeopleSoft Receivables involves converting existing data. Before you set up customers, familiarize yourself with the options for defining customer structures.
To ensure that your customer setup and maintenance is as simple and non-redundant as possible, PeopleSoft Receivables stores customer information at the business unit level and at the TableSet level.
PeopleSoft Receivables stores customer accounting and receivables information by customer within a business unit. This type of information includes:
Customer's balance.
Customer's open items.
Amount the customer owes in each aging category.
Payment performance indicators, such as average days late and day's sales outstanding.
The combination of a business unit and a customer ID determines where the system stores customer accounting and receivables information. Once you set up your business units, the system stores accounting and receivables data by customer within a business unit (or at a subcustomer level, if enabled). The Receivables Update Application Engine process (ARUPDATE) creates and stores this information.
PeopleSoft Receivables stores a variety of identifying and descriptive customer information by TableSet, such as:
Customer's name and address.
Customer's credit profile.
Certain processing options.
Correspondence options.
Team member (sales person) assigned to the customer.
Any number of business units can share customer information stored under a SetID. With customer information keyed by SetID, the advantages are similar to control tables keyed by SetID. You enter the information once and then link it to as many business units as you want. Each of these business units can process invoices, payments, and other receivables transactions for the customer.