Handling Import of Channel Data for Buy Side Flows

You can import supplier invoices from CSV files into Channel Revenue Management using the Import Management application. Import Management can be accessed from Tools > Import Management.

Import Supplier Invoices

Consideration: If you import supplier invoices via a CSV file (Batch Transaction Type = ORA_SUPPLIER_INVOICE_CSV), then import the CSV file once, and then schedule 2 processes to create accruals (for example, Create Accruals for Channel Batch and Create Accruals for Volume Programs).

How to Handle Errors

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

1. 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.

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

3. 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 supplier invoices.

This table contains all the required attributes that must be set up in various Oracle Fusion Cloud applications, for importing supplier invoices using CSV files.

Application	Attribute	Required?
HR foundation in HCM	Business Unit	Yes
HR foundation in HCM	Bill-to Location	Yes, if specified in the CSV file
HR foundation in HCM	Ship-to Location	Yes, if specified in the CSV file
HR foundation in HCM	Receiving Location	Yes, if specified in the CSV file
Financials foundation	Currency	Yes
Product Information Management	Item	Yes
Product Information Management	Supplier Item	Yes, if specified in the CSV file
Product Information Management	UOM	Yes
Inventory Management	Receiving Inventory Org	Yes, if specified in the CSV file
Procurement	Supplier	Yes
Procurement	Supplier Site	Yes
Procurement	Procurement BU	Yes, if specified in the CSV file
Procurement	Item Validation Org (Configure the Procurement Business Function for Procurement BU)	Yes
Payables Invoices	Invoice Type	Yes
Receiving	Transaction Type	Yes, if specified in the CSV file
Receiving or Inventory	Transaction Reason	Yes, if specified in the CSV file

Supplier Invoice Attributes

You must use Channel Batch Transaction as the import object. The attribute Batch Transaction Type is a required attribute. For supplier invoices, it's ORA_SUPPLIER_INVOICE_CSV. You can either download the Channel Batch Transaction template or map your template against the attributes in the Channel Batch Transaction object. These attributes are available for supplier invoices.

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.

This table contains all the attributes that are available for supplier invoice import

Attribute Name	Display Name	Description	Required?	Validated?	Document Header, Line
BatchTransactionType	Batch Transaction Type	The transaction type used to categorize the transaction data in the batch.	Yes	Yes Value is from the lookup ORA_CJM_BATCH_DATA_SOURCE	Header
BusinessUnit	Business Unit	The business unit for the transaction.	Conditional	Yes	Header, Line
BusinessUnitId	Business Unit ID	The unique identifier for the business unit.	Conditional	Yes	Header, Line
Comments	Comments	The comments for the transaction.	No	No	Header
Currency	Currency	The currency code for the transaction.	Yes	Yes	Header, Line
ItemNumber	Item	The inventory item number.	Conditional	Yes	Line
ItemDescription	Item Description	The description for the item.	No	No	Line
ItemID	Item ID	The unique identifier for the inventory item.	Conditional	Yes	Line
LineComments	Line Comments	The comments for the transaction line.	No	No	Line
OriginalReceivingTransactionNumber	Original Receiving Transaction Number	The unique identifier for the original transaction associated with the receiving line.	No	No	Line
OriginalSupplierInvoiceLineNumber	Original Supplier Invoice Line Number	The line number for the original supplier invoice line. If this attribute is specified and the Supplier Invoice Line referenced by it is present in document lines, then it will be treated as a correction. The Supplier Invoice Type value won't be used to determine if it is a correction or not.	No	No	Line
OriginalSupplierInvoiceNumber	Original Supplier Invoice Number	The supplier invoice number for the original supplier invoice. If this attribute is specified and the Supplier Invoice Line referenced by it is present in document lines, then it will be treated as a correction. The Supplier Invoice Type value won't be used to determine if it is a correction or not.	No	No	Line
OriginalSystemLineReference	Original System Line Reference	The original document reference for the transaction line in the external system.	No	No	Line
OriginalSystemReference	Original System Reference	The original document reference for the transaction in the external system.	No	No	Line
OriginalSystemSource	Original System Source	The name of the system source.	Yes	No	Header
ProcurementBusinessUnit	Procurement Business Unit	The procurement business unit on the purchase order.	No	Yes	Not in header, not in line. Used for validation.
ProcurementBusinessUnitId	Procurement Business Unit ID	The unique identifier for the procurement business unit on the purchase order.	No	Yes	Not in header, not in line. Used for validation.
PurchaseOrderBillToLocationCode	Purchase Order Bill-to Location Code	The unique identifier for the bill-to location.	No	Yes	Line
PurchaseOrderBillToLocationId	Purchase Order Bill-to Location ID	The unique identifier of the address for the bill-to location.	No	Yes	Line
PurchaseOrderDate	Purchase Order Date	The date on which the purchase order was communicated to the supplier.	No	No	Line
PurchaseOrderLineNumber	Purchase Order Line Number	The unique identifier for the purchase order line.	No	No	Line
PurchaseOrderLineRequestedDeliveryDate	Purchase Order Line Requested Delivery Date	The date by which the buyer has requested delivery of a line item by the supplier.	No	No	Line
PurchaseOrderLineRequestedShipDate	Purchase Order Line Requested Ship Date	The date by which the buyer asked suppliers to ship goods from their location.	No	No	Line
PurchaseOrderLineShipToLocationCode	Purchase Order Line Ship-to Location Code	The unique identifier for the ship-to location.	No	Yes	Line
PurchaseOrderLineShipToLocationId	Purchase Order Line Ship-to Location ID	The unique identifier of the address for the ship-to location.	No	Yes	Line
PurchaseOrderNumber	Purchase Order Number	The purchase order document number.	No	Yes	Line
ReceiptBillOfLadingNumber	Receipt Bill of Lading	A carrier's contract and receipt for the goods that the carrier agrees to transport from a specific origin address to a specific destination address.	No	No	Line
ReceiptNumber	Receipt Number	The number that acknowledges that a shipment was received in the warehouse.	No	No	Line
ReceiptShipmentNumber	Receipt Shipment Number	A shipment from one supplier that can include several items ordered on many purchase orders.	No	No	Line
ReceiptShippedDate	Receipt Shipped Date	The date when goods or services were shipped by the supplier.	No	No	Line
ReceiptWaybillNumber	Receipt Waybill	The non-negotiable document describing the contract for transporting cargo.	No	No	Line
ReceivingInventoryOrganizationCode	Receiving Inventory Organization Code	The user-defined unique code for the inventory organization.	No	Yes	Header
ReceivingInventoryOrganizationID	Receiving Inventory Organization ID	The unique identifier for the inventory organization.	No	Yes	Header
ReceivingLocationCode	Receiving Location Code	The unique identifier for the receiving location.	No	Yes	Line
ReceivingLocationId	Receiving Location ID	The unique identifier for the receiving location.	No	Yes	Line
ReceivingTransactionDate	Receiving Transaction Date	The date on which the transaction was performed.	No	No	Line
ReceivingTransactionNumber	Receiving Transaction Number	The unique identifier for the transaction associated with the receiving line.	No	No	Line
ReceivingTransactionReason	Receiving Transaction Reason	An explanation or justification that explains why the transaction is performed.	No	Yes	Line
ReceivingTransactionReasonId	Receiving Transaction Reason ID	The unique identifier for the transaction reason.	No	Yes	Line
ReceivingTransactionType	Receiving Transaction Type	The transaction type used to categorize the transaction.	No	Yes Value is from the Receiving lookup RCV_TRANSACTION_TYPE.	Line
SupplierName	Supplier	The organization or individual that provides goods or services to the buying organization for payment, bound by a contractual obligation.	Conditional	Yes	Header
SupplierId	Supplier ID	The unique identifier for the supplier.	Conditional	Yes	Header
SupplierInvoiceDate	Supplier Invoice Date	The invoice date of the supplier invoice.	Yes	No	Header
SupplierInvoiceLineNumber	Supplier Invoice Line Number	The line number for the supplier invoice line.	Yes	No	Line
SupplierInvoiceLineQuantity	Supplier Invoice Line Quantity	The quantity for the supplier invoice line. The quantity must be negative for return lines.	Yes	No	Line
SupplierInvoiceLineReason	Supplier Invoice Line Reason	An explanation or justification that explains why the transaction is performed.	No	No	Line
SupplierInvoiceLineUnitPrice	Supplier Invoice Line Unit Price	The unit price for the supplier invoice line.	Yes	No	Line
SupplierInvoiceLineUOM	Supplier Invoice Line UOM	The unit of measure for the supplier invoice line. UOM stands for Unit of Measure.	Yes	Yes	Line
SupplierInvoiceNumber	Supplier Invoice Number	The supplier invoice number for the supplier invoice.	Yes	No	Header
SupplierInvoiceType	Supplier Invoice Type	The supplier invoice type for the supplier invoice.	Yes	Yes Values are from the Payables lookup type INVOICE TYPE, lookup code STANDARD, CREDIT, and DEBIT. The reference data set is Common.	Header
SupplierItemNumber	Supplier Item	The supplier item number from the purchase order shipment line.	No	Yes	Line
SupplierItemId	Supplier Item ID	The unique identifier for the supplier item.	No	Yes	Line
SupplierNumber	Supplier Number	The unique identifier of the supplier assigned by the buying organization.	Conditional	Yes	Header
SupplierSite	Supplier Site	The entity that models how the buying organization conducts business with the supplier.	Conditional	Yes	Header
SupplierSiteId	Supplier Site ID	The unique identifier for the supplier site.	Conditional	Yes	Header
Channel Document Header DFF	Based on setup	The fields to capture additional information about the channel document header. Note: If a DFF attribute is populated in the CSV but not configured in the DFF, it will get copied to the document transaction without validation.	Based on setup	Yes	Header
Channel Document Line DFF	Based on setup	The fields to capture additional information about the channel document line. Note: If a DFF attribute is populated in the CSV but not configured in the DFF, it will get copied to the document transaction without validation.			Line

Note: When both ID and Name values are available, for example, BusinessUnitId and BusinessUnit, the ID value is evaluated.

Note: The combination of Batch Transaction Type, Business Unit ID, Original System Source, Supplier Invoice Line Number, Supplier Invoice Number, and Supplier Site ID must be unique.

Qualifiers for Supplier Invoice

Here's the list of qualifiers for supplier invoices

• Purchase Order Date

• Requested Delivery Date

• Requested Ship Date

• Supplier Invoice Date

• Receipt Transaction Date

• Transaction Reason

• Bill-to Location

• Ship-to Location

• Channel Document Header DFF (only for CSV integration)

• Channel Document Line DFF (only for CSV integration)

  Note: Only global segment descriptive flexfields are supported as program qualifiers, not context-based segments. However, your implementation can import context-based segments if it doesn't use them as qualifiers.