Use this transaction to import supplier catalogs into your Purchasing system as Catalog Quotes. This supports catalog lookup and purchase order placement. During the import process, supplier sourcing rules may be added to Oracle Purchasing, and the Oracle Inventory item master may be updated with catalog item changes or new catalog items.

Prerequisite Setup in Oracle Purchasing

Allow updating of item description in Purchasing Options.

Prerequisite Setup in Oracle Inventory

Allow the updating of item status codes at the site level. Set the INV: Default Item Status profile to Active.

Prerequisites

• Create the inbound directory and update the INIT.ORA file. See: Defining Data File Directories, Oracle e-Commerce Gateway Implementation Manual.

• Define the ECE: Inbound file path profile option. See: e-Commerce Gateway Profile Options, Oracle e-Commerce Gateway Implementation Manual.

• Define trading partner relationships and enable EDI transactions for the trading partner. See: Defining Trading Partner Data.

• Define code conversions. See: Defining Code Conversion Categories, Assigning Categories, and Defining Code Conversion Values.

• Customize interface data file layout, if necessary. See: Changing the Interface Data File Record Layout.

To run the Price / Sales Catalog inbound program:

1. Navigate to the Run e-Commerce Inbound Process window:

   • Process > Import Program

   • In the Submit a New Request window, select Single Request to submit an individual request.

2. In the Name field of the Run e-Commerce Inbound Process window, select IN: Price Catalog (832/PRICAT) from the LOV.

3. The Parameters window will open. Enter the following parameters as necessary:

   • Inbound Datafile Name: Enter the inbound data file or accept the default.

   • Execute Open Interface? (Required)

     Select Yes to initiate the Purchasing Open Interface Import program using the default parameter values.

     Enter No if you do not want to initiate the Purchasing Open Interface.

   • Default Buyer: (Required) Enter the default buyer name for the Price/Sales Catalog or Response to RFQ.

   • Document Type: Valid options are Blanket and Quotation. The option of Blanket directs Purchasing to create a Blanket Agreement for the document to be imported. The option of Quotations directs Purchasing to create a Catalog Quotation for the document to be imported.

   • Document Sub Type: Used with document type of "Quotation" to indicate a document sub type of "Catalog Quotation" for the Price/Sales Catalog or Response to RFQ to be imported. The document sub type of "Bid Quotation" is invalid for the transaction.

   • Create or Update Items: Used with the Price/Sales Catalog or Response to RFQ to indicate whether you wish to update the item master with catalog item changes or add catalog items to the item master.

   • Create Sourcing Rules: Indicate Yes or No on whether supplier sourcing rules should be created automatically during the Price/Sales Catalog and Response to RFQ import process.

   • Approval Status: Enter desired status of Approved or Incomplete for Blanket Agreement and Quotation created by Purchasing for the Price/Sales Catalog or Response to RFQ to be imported.

   • Release Generation Method: Used when Document Type is set to Blanket and Create Sourcing Rules is set to Yes. Select from the following three blanket release methods:

     Automatic Release: allows Purchasing to automatically generate approved blanket releases for items that are autosourced to a single supplier.

     Automatic Release with Review: allows Purchasing to automatically generate releases and forwards them for approval.

     Release using Autocreate: allows you to use the Purchasing Autocreate function to convert purchase requisitions into blanket releases for blanket purchase orders.

   • Map Code: (Required) Enter the appropriate map code.

   • Debug Mode: Set the debug mode to report on debug information. Debug information is written to the concurrent manager log file:

     OFF: No debug information is generated.

     LOW: Summary debug information is written to the concurrent manager log file.

     MEDIUM: Medium level debug information is written to the concurrent manager log file.

     HIGH: High level debug information is written to the concurrent manager log file. (This option generates much information.)

   • Data File Characterset: Defaults to the characterset defined in the database. Accept this value or select from the list of values.

     Note: If the selected data file characterset is different from the database characterset, then the generic inbound program will perform a characterset conversion on the data in the data file. This conversion is done to the database characterset. If the conversion is failed, a 'Lossy Conversion' error will be raised. Transactions without Lossy Conversion errors in the same file will continue processing unless they have other types of errors.

     Use the View Staged Documents window to identify the transaction errors due to Lossy Conversion. The document status is set to 'SKIPPED' and the Line that caused this conversion error has the status 'Invalid characters detected during Characterset Conversion'.

4. Enter any Schedule and Completion options for the request.

5. Choose Submit and make a note of the Request ID returned.