Receiving Price/Sales Catalog Information Electronically
Your supplier can send you the latest price/sales catalog information and responses to requests for quotation through the Purchasing Documents Open Interface. The Purchasing Documents Open Interface processes catalog data in the Oracle Applications interface tables to ensure that it is valid before importing it into Purchasing. One way to import catalog data into the Purchasing Documents Open Interface, and finally into Purchasing, is through Electronic Data Interchange (EDI). EDI programs import the catalog information into Purchasing directly as blanket purchase agreement lines or catalog quotations, whichever you choose. You can also choose to have the programs automatically populate the item master and/or apply sourcing rules to the imported item information. If you import price/sales catalog information as blanket purchase agreement lines, you can also specify release generation methods.
The catalog information is sent by the supplier in the form of a "flat file." Your supplier can send you flat files with two kinds of action codes: Original or Replace. An Original file is one in which all the catalog information is new to your system. A Replace file replaces already-created blanket purchase agreement lines or catalog quotations with new documents containing new price/sales catalog information. (The Purchasing Documents Open Interface program replaces the old documents by invalidating their effectivity dates; then it creates new documents with the new price/sales catalog information and the old effectivity dates.) For EDI Gateway to distinguish between Original and Replace action codes, you need to set up code-conversion categories and values in EDI Gateway. See: Defining Code Conversion Categories. See: Defining Code Conversion Values. See also: Overview of Code Conversion.
Prerequisites
Allowing updating of the item master enables price or item description changes or to be communicated quickly to Purchasing. Before you run the EDI Price/Sales Catalog Inbound Program or the EDI Response to Request for Quote Inbound Program, you need to make sure of the following settings if you want to update the item master:
- Allow updating of item descriptions. Navigate to the Purchasing Options window. In the Control options region, check Allow Item Description Update. See: Defining Control Options.
- Allow updating of item status codes at the site level. Navigate to the Personal Profiles window. Make sure that INV: Default Item Status is set to Active.
Make sure default category sets are set up appropriately for both Purchasing and Inventory by performing the following steps:
1. Navigate to the Default Category Sets window by choosing Setup > Items > Categories > Default Category Sets in the Purchasing responsibility.
Make sure that both Purchasing and Inventory are listed in the Functional Area column and each has a default Category Set defined for it.
2. Make sure that you have a default category set each for both Purchasing and Inventory in the Category Sets window. Navigate to the Category Sets window by choosing Setup > Items > Categories > Category Sets in the Purchasing responsibility.
If you've selected the Enforce List of Valid Categories check box in the Category Sets window, make sure that the Default Category also appears in that List of Valid Categories. If not, enter it in the list.
How Sourcing Works
When you import price/sales catalog information into Purchasing through the EDI Catalog Inbound or EDI Response to RFQ Inbound report in Oracle EDI Gateway, you have the option of choosing Yes or No in the Create Sourcing Rules field in the Parameters window that appears. If you choose Yes, Purchasing checks to see if a sourcing rule is assigned to the item at the item level and does the following:
- If no sourcing rules exist for the item, Purchasing generates a sourcing rule automatically, allocating 100 percent to the supplier importing the information.
- If a sourcing rule exists for the item, Purchasing compares the effectivity dates of the incoming document with those of the existing sourcing rule for the item. To ensure that only one sourcing rule is used for the item, Purchasing does the following:
If the effectivity dates of the incoming document are the same as the existing sourcing rule's effectivity dates, Purchasing checks to see if the supplier is in the Approved Supplier List. If not, Purchasing adds the supplier to the existing sourcing rule with an allocation of 0 percent. Later, you can query the sourcing rule and define your own percentage splits between suppliers.
If the effectivity dates of the incoming document are different than the existing sourcing rule's effectivity dates, but are within or overlap the existing effectivity dates, then no new sourcing rule is created that will conflict with the existing sourcing rule.
If the effectivity dates of the incoming document do not overlap the existing sourcing rule's effectivity dates, Purchasing updates the item's sourcing rule with the new effectivity dates, adding the supplier at an allocation of 100 percent.
See Also
Inbound Price/Sales Catalog (832/PRICAT)
Running the EDI Price/Sales Catalog Inbound Program
Inbound Response to Request for Quote (843/QUOTE)
Running the EDI Response to Request for Quotation Inbound Program
Purchasing Documents Open Interface
Oracle Manufacturing, Distribution, Sales and Service Open Interfaces Manual, Release 11
