1. Implementing Channel Revenue Management
  2. Handling Import of Indirect Sales Data

Handling Import of Indirect Sales Data

In this topic, you'll learn how you can handle the import of indirect sales data for special price agreement flows.

You can import data into Channel Revenue Management using a CSV file through the Import Management application. The following graphic depicts the flow of data import.

This image depicts the flow of data import for special price agreements.

Import Indirect Sales Data for Special Price Agreements

Import Management can be accessed from Tools > Import Management.

Consideration: If you import indirect sales data via the CSV file (Batch Transaction Type = ORA_SPECIAL_PRICE_AGRMNT_CSV), then you must first import the CSV file. When you load indirect sales data via the CSV file, the Process Indirect Sales Data scheduled process is triggered and this creates a special price agreement batch, accruals, and updates the checkbook automatically.

This figure depicts how the import indirect sales data flow works for special price agreements

How to Handle Errors

Here are some tips to handle errors that may occur during the import process:

• The import process provides you with an error.csv file and a reject.csv file for a given import. All the errors are in the error.csv file. The reject.csv file is a copy of your source CSV with additional columns with error messages.

• Correct the errors in the reject.csv file. Remember to remove the first and last columns and save as a new CSV file.

• Import the new CSV file.

Note: You must fix all the errors in the CSV file before rerunning the import. A batch is created only if there are no validation errors.

Attributes Required from Oracle Fusion Cloud Applications

You must set up these attributes that are part of various Oracle Fusion Cloud applications for importing indirect sales data.

Application Attribute Required?
HR foundation in HCM Business Unit Yes
Financials foundation Currency Yes
Product Information Management Item Yes
Product Information Management UOM Yes
Pricing Item Validation Organization (Pricing Parameter Item Validation Organization based on BU) Yes
Receivables Distributor Bill-to Account Yes
TCA End Customer (party). Either Bill-to Customer (party) or Ship-to Customer (party). Yes for Bid Request and Meet Competitor Price

Special Price Agreement Attributes

You must use Channel Batch Transaction as the import object. The attribute Batch Transaction Type is a required attribute. For special price agreements, it's ORA_SPECIAL_PRICE_AGRMNT_CSV. You can either download the Channel Batch Transaction template or map your template against the attributes in the Channel Batch Transaction object.

Review the My Oracle Support (MOS) topic, How To Import Customer and Supplier Invoices from CSV files into Channel Revenue Management Using the Import Management Application (Doc ID 3045218.1) for additional information.

The following attributes are available for special price agreements:

Display Name Attribute Name Description Required Validated
Agreement Name AgreementName The name of the special price agreement. No No
Agreement Number AgreementNumber The unique number that identifies the special price agreement. No No
Batch Transaction Type BatchTransactionType The transaction type used to categorize the transaction data in the batch. No Yes
Bill-to Customer BillToCustomer The name of the bill-to customer. No No
Bill-to Customer Registry ID BillToCustomerRegistryID The user-friendly unique identifier for the bill-to customer. No No
Business Unit BusinessUnit The business unit for the transaction. No Yes
Comments Comments The comments for the transaction. No No
Currency Currency The currency code for the transaction. No Yes
Distributor Distributor The name of the distributor. No Yes
Distributor Account DistributorAccount The bill-to customer account number of the distributor. No Yes
Distributor Claim Number DistributorClaimNumber The claim number recorded in the system of the distributor. Yes Yes
Distributor Registry ID DistributorRegistryID The unique user-friendly identifier for the distributor. No Yes
Item ItemNumber The inventory item number. No No
Item Description ItemDescription The description for the item. No No
Line Comments LineComments The comments for the transaction line. No No
Original System Line Reference OriginalSystemLineReference The original document reference for the transaction line in the external system. No No
Original System Reference OriginalSystemReference The original document reference for the transaction in the external system. No No
Original System Source OriginalSystemSource The name of the system source. Yes No
Requested Ship Date RequestedShipDate The original date the customer requested the item ship on. No No
Sales Order Date SalesOrderDate The ordered date on the sales order. No No
Sales Order Line Number SalesOrderLineNumber The unique identifier for the sales order line. No No
Sales Order Number SalesOrderNumber The identifier for the sales order. Yes No
Shipped Date ShippedDate The date the shipment was actually sent. No No
Shipped Quantity ShippedQuantity The quantity of goods or services that was shipped by supplier. No No
Shipped UOM ShippedUOM The unit of measure for the shipped quantity. UOM stands for Unit of Measure. No No
Ship-to Customer ShipToCustomer The name of the ship-to customer. No No
Ship-to Customer Registry ID ShipToCustomerRegistryID The user-friendly unique identifier for the ship-to customer. No No
Unit Claimed Amount UnitClaimedAmount The amount per unit that is claimed by the distributor. No No
Unit Purchase Price UnitPurchasePrice The price per unit that a distributor paid for an item. No No
Unit Selling Price UnitSellingPrice The price per unit that a buyer paid for an item. No No
Waybill WaybillNumb​er The non-negotiable document describing the contract for transporting cargo. No No
Attribute Category AttributeCategory The user-defined descriptive flexfield context sensitive segments configured to capture additional information on the transaction header. No No
Channel Document Header DFF

AttributeCharacter1-20

AttributeDate1-5

AttributeNumber1-10

The segments of the descriptive flexfield used to hold user-defined information on the transaction header.

Note: If a DFF attribute is populated in the CSV but not configured in the DFF, it will be copied to the document transaction without validation.
 No No
Line Attribute Category LineAttributeCategory The user-defined descriptive flexfield context sensitive segments configured to capture additional information on the transaction line.
Channel Document Line DFF

LineAttributeCharacter1-20

LineAttributeDate1-5

LineAttributeNumber1-10

 The segments of the descriptive flexfield used to hold user-defined information on the transaction line.

The following attributes are part of the duplicate record check:

  • Order Number
  • Order Line Number (optional attribute)
  • Order Date
  • Original System Source
  • Item
  • UOM
  • Quantity (Shipped Quantity)
  • Distributor Account
  • Batch Status
  • Batch Line Status
  • Waybill Number (Optional Attribute)
  • Business Unit

Qualifiers for Special Price Agreements

Here's the list of qualifiers for special price agreements:

  • Requested Ship Date (order line)
  • Ordered Date (order header)
  • Actual Ship Date (order line)
  • Distributor (order header)
  • End Customer (order header)
  • Item (order line)
  • UOM (order line)

Mapping between Customer Qualifiers for Special Price Agreements

Customer Qualifier in Special Price Agreement Name in Channel Batch Transaction Template CSV File Accounts Receivable Transaction UI Accounts Receivable receivablesInvoices REST API
Distributor Account Distributor Account Bill-to Account Number BillToCustomerNumber
End Customer (does not require a bill-to account) Bill-to Customer or Ship-to Customer