Previous	Next		Contents	Index	Navigation		Library

   To define table and column mappings between Oracle Receivables and Oracle Sales Compensation and regenerate the code according to the mappings:

1. Define your table and column mappings between Oracle Receivables and Oracle Sales Compensation. This step identifies your source and destination tables and columns. See Mapping Transaction Attributes to Receivables Attributes for information on how to do this.

The following sections give you examples of some of the different types of mapping choices:

• Adding Attributes to the Default Mapping

• Direct Mapping at the Header Level

• Direct Mapping at the Line Level

• Direct Mapping at the Line Level Using an Expression

• Indirect Mapping at the Header Level Using a Foreign Key

2. Select Synchronize to regenerate the collection code according to your mappings.

Regenerating the collection code adds several lines of code to the standard collection code in Oracle Sales Compensation to accommodate any added column mappings. The added code consists of SQL statements that specify how to extract and insert information from Oracle Receivables tables and columns to Oracle Sales Compensation tables and columns.

   To use the Concurrent Manager to submit a set of requests that install the collection programs and collect the transaction data according to the defined table and column mappings:

1. Submit a Concurrent Manager request to run the Install Collection Package program.

The Install Collection Package program recompiles the code and puts it back in the database.

2. Submit a Concurrent Manager request for each of these four collection packages, depending on what type of transaction information you are collecting:

• Collect Invoices

• Collect Payments and Givebacks

• Collect Clawbacks

• Collect Writeoffs

These collection programs appear in the list of values for the Name field in the Submit Requests Window. The collection programs bring information from your mapped tables and insert them in the intermediate table CN_COMMISSION_LINES_API. Figure 4-6 illustrates this process.

By default, select Run from the Concurrent Requests menu to navigate to the Submit Requests window. Enter the name of the program in the Name field and select Submit.

   To use the Concurrent Manager to submit a request to run the Transaction Interface Loader program:

The Transaction Interface Loader program creates a batch program that loads your data into the Oracle Sales Compensation interface (intermediate) table CN_COMMISSION_LINES; you can run a query in the Maintain Transactions window to see this batch, called Transfer <date>. The date field shows the date when the data is transferred.

To see details of the collected transactions, click the Transactions button in the Maintain Transactions window. Oracle Sales Compensation takes you to the Transactions window and displays all your collected transactions. See Viewing Transaction Details for more information on working with the Transactions window.

Running the Transaction Interface Loader program is the the same task that you perform when you collect transaction information directly through an open interface. Collecting Transactions Using the Open Interface Directly, describes how to perform this task. Alternatively, you can execute the CN_COMMISSION _LINES_PKG.LOAD procedure in SQL*Plus to perform the same function.

Note: See the Oracle Applications User's Guide, Release 10SC, for details on how to work with the concurrent manager.