Previous  Next          Contents  Index  Navigation    Library

Direct Mapping at the Line Level Using an Expression

This form of direct mapping allows you to change the transaction data you bring in from Oracle Receivables.

An example of using an expression may be the following scenario--you want to bring the information in the QUANTITY_ORDERED column in the Oracle Receivables table RA_CUSTOMER_TRX_LINES into Oracle Sales Compensation table CN_TRX_LINES; if the value in the QUANTITY_ORDERED column is NULL, you want it changed into zero (0) in the corresponding Oracle Sales Compensation table. You would accomplish this by using an expression.

Oracle Sales Compensation moves information from the CN_TRX_LINES attribute columns to the attribute columns in the CN_COMMISSION_LINES table by matching the value in a column called the User Column Name. The first part of the mapping procedure, therefore, consists of defining the User Column Name for the Oracle Sales Compensation tables CN_TRX_LINES (at the Line level) and CN_COMMISSION_LINES on the Tables and Columns form. Table 3 illustrates the source and destination tables and columns for the mapping.

Table 3: Source and Destination Tables and Columns for Direct Mappingfrom Oracle Receivables to Oracle Sales Compensation at the Line Levelusing an Expression

Receivables Source Table Receivables Source Table Alias Receivables Source Column Name Receivables Source Column Expression
RA_CUSTOMER _TRX_LINES RCTL QUANTITY_ORDERED NVL(RCTL.QUANTITY_ORDERED,0)

Intermediate Sales Compensation Table Intermediate Sales Compensation Table Column Intermediate Sales Compensation Table User Name Column
CN_TRX_LINES (Line level) ATTRIBUTE2 AR_QUANTITY_ORDERED
Destination Sales Compensation Table Destination Sales Compensation Table Column Name Destination Sales Compensation Table User Name Column
CN_COMMISSION_LINES ATTRIBUTE3 AR_QUANTITY_ORDERED

   To define direct mapping at the line level using an expression:

Attention: The name you type in the User Column Name field is your name for the column, and this name must NOT be the same as the system name for the column. If you are bringing in transaction information into the ATTRIBUTE1 field, then the name in the User Column Name field must NOT be ATTRIBUTE1.

   To collect the transaction data according to the mappings you just defined:

Note: For more information on running the Concurrent Manager, see the Oracle Applications User's Guide.


         Previous  Next          Contents  Index  Navigation    Library