Previous	Next		Contents	Index	Navigation		Library

Oracle Sales Compensation stores each compensation transaction across three database tables, each corresponding to a source Oracle Receivables table that contains similar types of data. Each compensation transaction spans all three Oracle Sales Compensation tables, with one record in each table corresponding to a different level of detail in the compensation transaction:

• CN_TRX contains information typically found in the header of an Oracle Receivables source document--such as the ship-to and bill-to customer names.

• CN_TRX_LINES contains information typically found at the line level of detail in a Receivables document--such as product ordered, quantity, and price.

• CN_TRX_SALES_LINES contains information about the sales lines in a Receivables source document--such as the salesperson's name and the amount of sales credit assigned to the representative by Oracle Receivables.

Note: For more information about sales lines and a detailed description of the structure of each of the Oracle Receivables source tables shown in Figure 4 - 4, see Oracle Receivables Technical Reference Manual.

If the default compensation transaction does not contain all the data your organization needs to pay compensation, you need to define additional data that you want Oracle Sales Compensation to collect from Oracle Receivables. You define this data by customizing columns in the appropriate Oracle Sales Compensation transaction table.

For example, Global Computers, Inc. uses the zip code of the ship-to customer to provide incentive compensation by territory during sales promotions. Because zip code is not among the data Oracle Sales Compensation collects in a default compensation transaction, Global must customize a transaction attribute in the appropriate compensation transaction table. See Mapping Transaction Attributes to Receivables Attributes for more information on how to map transaction information from Oracle Receivables.