Setting Up Oracle Incentive Compensation for Oracle Transportation Management Integration

This appendix covers the following topics:

Configuring Tables and Columns

You must define Oracle Transportation Management tables before they can be used in the collections programs.

Specify the OIC Table CN_COMM_LINES_API_ALL and configure the columns that will be used for collection.

Navigation: Setup Tasks > Collection > Configure Tables and Columns

  1. Click Add 5 Rows.

  2. Select CN as the schema.

  3. Enter CN_COMM_LINES_API_ALL as the tables name.

  4. Select Collection usage.

  5. Click Save.

After you have added the table, configure the columns that will be used for collections. Enable and configure these columns for collection:

Additional Information: The column name is set in the application, but you can assign a user name to it to match your business process or for ease of use.

Related Topics

Configure Tables and Columns for Collections

Defining External Tables

If the information you need is in tables that are not in Oracle Incentive Compensation tables, then you must define these external tables and map their columns to respective Oracle Incentive Compensation tables.

Navigation: Setup Tasks > Collection > Define External Table Mappings

Define these Oracle Transportation Management tables:

These tables must already exist, and must be in the same instance as Oracle Incentive Compensation. After you have defined the tables, map the columns with the appropriate CN_COMM_LINES_API_ALL table columns.

Mapping between CN_COMM_LINES_API_ALL and WORK_INVOICE
CN_COMM_LINES_API_ALL Columns WORK_INVOICE Columns Description
SOURCE_TRX_ID WORK_INVOICE_XID Header ID of the source transaction.
SALESREP_ID DRIVER_GID Sales representative for transaction. The integration will look at the cross reference for the Driver_GID and derive the HR Person ID and use that person ID for this column.
REVENUE_CLASS_ID REVENUE Revenue class for transaction.
 
TRANSACTION_AMOUNT REVENUE Transaction Amount
TRANSACTION_CURRENCY_CODE REVENUE_CURRENCY_GID Currency is which the transaction happened.
Mapping between CN_COMM_LINES_API_ALL and WORK_INVOICE_ACTIVITY
CN_COMM_LINES_API_ALL Columns WORK_INVOICE_ACTIVITY Columns Description
INVOICE_NUMBER Invoice Number
SEQUENCE
Invoice number and sequence.
BOOKED_DATE ACTIVITY_DATE Date when order is booked.
REVENUE_CLASS_ID SPECIAL_SERVICE_GID Revenue class for transaction.
Special Services has different classes such as Hand Unload.
ATTRIBUTE41 PAYABLE_INDICATOR_GID Indicates the payable state of this activity (ex: Payable, Not Payable, Display as Zero, etc.). If the Payable indicator is Not Payable, then the transaction will not be sent to OIC.
ATTRIBUTE42 DISTANCE Distance recorded
ATTRIBUTE43 DISTANCE_UOM_CODE Unit of measurement of distance
ATTRIBUTE44 DURATION Duration of journey.
ATTRIBUTE45 DURATION_UOM_CODE Unit of measurement of duration.
ATTRIBUTE46 WEIGHT Weight of cargo.
ATTRIBUTE47 WEIGHT_UOM_CODE Unit of measurement of weight.
ATTRIBUTE48 VOLUME Volume of cargo
ATTRIBUTE49 VOLUME_UOM_CODE Unit of measurement of volume.
ATTRIBUTE50 SHIP_UNIT_COUNT Count of the number of shipment.
ATTRIBUTE51 ITEM_PACKAGE_COUNT Count of the number of item packages.

Related Topics

Define External Table mapping for Collection

Defining Collection Sources and Mapping

Create the OTM Collection transaction source. Create the OTM source table references and map the respective columns to the CN_COMM_LINES_API_ALL table column.

Related Topics

Define Collection Sources and Mapping

Add a New Transaction Source to the TRX TYPES Lookup

Source Table

Parameters

Notification Queries

Column Mapping

Collection Query

Triggers

Filters

Generating Collection Packages

After the setup is complete, you must generate a collections package before it can be used. You can also test generate a package before generating the final package.

Related Topics

Generate Collection Package