Skip Headers

Oracle iProcurement Implementation and Administration Guide
Release 12.1
Part Number E13409-05
Go to Table of Contents
Contents
Go to previous page
Previous
Go to next page
Next

Content Management

Understanding the Procurement Catalog

Oracle iProcurement and Oracle Purchasing have a single shared catalog data model. This data model forms the basis of what can be more generally thought of as the procurement catalog which determines the types of catalog content your requesters can see and how that content is presented to them. The procurement catalog combines the best features of previous catalog models and provides a number of significant capabilities and benefits:

Business Flow

  1. Online authoring and file upload from the Oracle Purchasing Buyer's Work Center, Oracle iSupplier Portal, and Oracle iProcurement Catalog Administration provide the content for the catalog.

  2. Review changes between the content revision and the last approved version using the Difference Summary for Catalog Changes.

  3. Buyer approves catalog content changes using the Oracle Purchasing approval hierarchy, revision control, and archival capabilities.

  4. Approved content updates the procurement catalog in real-time.

Implementation Flow

  1. Analyze the content that your requesters want to see and define the catalog schema.

  2. Determine what type of container makes sense for the items and services your requesters want access to and define your content zones.

  3. Create or upload the catalog data.

  4. If needed, organize your content zones into stores.

Understanding Catalog Schema

At a high level, the area that define the catalog are the catalog data and the catalog schema.

Catalog data consist of the items and services available for purchase. The associated prices for these items and services are also considered part of the catalog data.

Catalog schema is comprised of:

The types of categories in the catalog that define the catalog’s hierarchy are:

There are two types of descriptors in the catalog:

The combination of categories and descriptor make up your catalog schema.

Catalog Content Structure

Catalog is general term that refers to your online shopping content. However, you don’t define or setup catalogs in Oracle iProcurement. Instead you define content zones. Catalog Administrators partition local catalog content into local content zones, define punchout or transparent punchout content zones, and then assign these content zones to stores. The combination of content zones that you assign to a store determines what catalog content your users see.

Oracle iProcurement offers four types of content zones that you can set up. You can create more than one of each type of content zone.

Type Location of Content Description
Local Oracle Purchasing Consists of items, categories, and descriptors defined in Oracle Purchasing and Oracle Inventory.
Punchout Supplier's site or Oracle Exchange Consists of items that the supplier maintains. The requester clicks a link to the external site from the Shop store or Search Results Summary page, and adds items from the external site to the shopping cart in Oracle iProcurement.
Transparent punchout Supplier's site or Oracle Exchange When the requester searches for items, the transparent punchout content zone accesses the external site in the background and returns the matching items to the Search Results Summary and Search Results pages. The requester then adds the items to the shopping cart.
Informational Your company’s intranet, supplier's site, or Oracle Exchange Captures instructions, policies, and links for ordering items and services that may not be supported by the other catalog types. For example, an informational content zone can contain a link to an existing policy or instructions page in your company. Unlike the other catalog types, items purchased through the informational content zone cannot be added to the shopping cart.

See: Maintaining Catalog Content.

Implementation Checklist

Use the following checklist for all setup related to catalog creation and management. This is a checklist of all setup steps in this chapter.

Catalog Setup Checklist
Step Required or Optional Information Source
Load catalog content Required Online Catalog Authoring
Loading Catalog Content
Determine catalog (content zone) types to implement. Required Understanding the Catalog
Choosing a Catalog Type
Create one or more catalogs (content zones): local content zone, punchout or transparent punchout content zone, or informational content zone. Required For local catalog information, see Creating and Maintaining Local Content.
For punchout or transparent punchout, see the Oracle Procurement Buyer's Guide to Punchout and Transparent Punchout.
For informational catalogs, see: Maintaining An Informational Content Zone.
Define access to content zones. Optional Maintaining Content Zones
Set up Smart Forms. Optional Smart Forms
Decide whether to create more than one store. Optional Managing Content Presentation
Create stores to group content zones and Smart Forms. Optional Maintaining Stores
Set or review search related options. Recommended Setting Search Related Options
Associate images with content, stores, or items. Optional Managing Images

Maintaining The Catalog Schema

A catalog's schema refers to the structure and organization of the catalog. Schema consists of categories, descriptors, and category hierarchies. You can use online Schema maintenance in iProcurement Catalog Administration to manage schema online, or you can upload schema elements:

Both of these maintenance functions are available from iProcurement Catalog Administration by clicking the Schema tab.

the picture is described in the document text

Catalog Schema Components

Categories

A category classifies items. There are three types of categories:

Descriptors

A descriptor describes items or categories. Descriptors are of two types:

Note: For details regarding schema components see: Understanding Schema.

Category Hierarchies

The category hierarchy presents a hierarchical view of the catalog to requesters. Use the category hierarchy to view and create hierarchies of categories and to create browsing categories.

For example, several item categories may be grouped under browsing categories as follows:

Office Equipment, Accessories and Supplies < - browsing category
   Office Supplies < - browsing category
      Desk Furniture < - shopping category
         MZ451DESK < - item
         MZ882DESK < - item
   Calendars < - item category
Writing Instruments < - browsing category
   Ball Point Pens < - shopping category
      PA453BIC < - item
      PA221ROL < - item

You do not have to have the same number of levels in all categories. In the example above, Office Equipment, Accessories and Supplies contains multiple levels of categories. Writing Instruments contains just two levels (one browsing and one item category level).

Creating a category hierarchy is optional. If you create one, requesters see the hierarchy when they browse categories in a store. If you do not create one, then requesters cannot browse categories for items. (They can still find items by searching, just not by browsing.) Some companies find it useful to enable requesters to browse categories, others may not.

Note: The changes you make to the category hierarchy are visible immediately in the catalog.

Loading Schema

Schema maintenance can sometimes require a large volume of edits which is more conveniently done using a file of the commands. Oracle iProcurement provides an upload interface to satisfy this need using an XML file.

To use an XML catalog schema load:

  1. On the iProcurement Catalog Administration Schema page, click Upload.

  2. On the Upload Schema page, click Download Resources, and save the zipped resource file to a convenient local folder.

    The resource file contains a document type definition (DTD) for creating the XML file and a readme file that contains detailed instructions and examples. If you are creating an XML file to load catalog schema (categories and descriptors) for the first time, open and review the Readme_Schema file.

    Note: If you have recently updated Oracle iProcurement, it is important to use the latest version of the DTD.

  3. Once you complete your XML catalog schema file, save it to the location of your choice. Save the file with any name, using a .xml extension.

  4. Return to the iProcurement Catalog Administration Schema page and click Upload.

  5. Click Browse to locate your completed file.

  6. Select your file and click Open in the dialog box.

    Tip: If you cannot find your file in the Open dialog box, make sure you are browsing in the correct directory, and set the File Type in the dialog box to All files.

  7. Click Submit. When the loader receives your file, validation begins. A confirmation page displays the job number that is automatically assigned to your job. Check the status of your job on the iProcurement Catalog Administration View Schema Upload History page to make sure that no errors occurred during the upload.

To monitor the schema job status:

Related Topics

Maintaining The Catalog Schema

Online Schema Maintenance

Oracle iProcurement Catalog Administration provides the same functionality editing schema online as uploading it. Uploading gives you the advantage of planning your categories and descriptors up front, and loading them in a single file. Online maintenance enables you to search for, view, and sort the data.

Schema maintenance online:

Maintaining Descriptors

Descriptors are the attributes of an item or service that help describe it to the requester. Base descriptors apply to all items or services in the catalog. Some base descriptors, such as Description, are required. Local descriptors apply only to items within a specific shopping category and could also be thought of as category attributes.

To create or edit base descriptors:

  1. In iProcurement Catalog Administration, select the Schema tab.

  2. Click the Base Descriptors subtab.

  3. On the Base Descriptors page click Create Descriptors.

  4. See the field descriptions below.

  5. Click Apply.

To create or edit category descriptors:

  1. In iProcurement Catalog Administration, select the Schema tab.

  2. Click the Item Categories subtab.

  3. On the Item Categories page, search for the category to which you want to add descriptors. If you cannot find the category, see Category Searching.

  4. Click Edit for the category.

  5. On the Edit Item Category page, do either:

  6. See the field descriptions below.

  7. Click Apply.

    Note: If you change the Searchable attribute of an existing descriptor, the system launches a job to handle the change.

To enter descriptor information, refer to the following fields:

To delete a descriptor:

  1. Start on the iProcurement Catalog Administration Schema tab and follow the instructions above for finding and editing a base or category descriptor.

  2. On the page that displays the descriptors, click the Delete icon for the descriptor.

  3. Click Yes to confirm the deletion.

    Note: You can only delete a descriptor if it is not in use by any item in the catalog. For example, if you want to delete the descriptor Ink Color from category Pens, there must not be any Pens in the catalog that has a value for Ink Color.

  4. A job is created for the deletion. You can monitor it on the iProcurement Catalog Admimistration View Schema Upload History page.

Maintaining Shopping Categories

Shopping categories, also known as genus categories, group similar items. Shopping categories are at the lowest level of the category hierarchy. A shopping category can never be a parent category to a child category.

To create or edit an shopping category:

  1. In iProcurement Catalog Administration, select the Schema tab.

  2. Click the Item Categories subtab.

  3. On the Item Categories page, do either:

  4. Enter the following information:

  5. Click Apply.

  6. If you want to add category descriptors, see: To create or edit category descriptors .

To delete an shopping category:

  1. On the Item Categories page search for the category. If you cannot find the category, see Category Searching.

  2. Click the Delete icon.

    Caution: You cannot delete a category if it is in use by any items. Mass expire these items first.

  3. Click Yes to confirm the deletion.

    Note: To delete browsing categories, see Maintaining Category Hierarchy.

To view all shopping categories in the catalog:

  1. In iProcurement Catalog Administration, select the Schema tab.

  2. Click the Category Hierarchy subtab.

  3. On the Category Hierarchy page, select any browsing category.

To search for a specific shopping category:

  1. On the Item Categories page, use only the following operators to search for shopping categories

  2. Click Go. (Do not press Return on your keyboard.)

    Note: Only shopping categories can be found on the Item Categories page. To find browsing categories, see Maintaining Category Hierarchy.

Maintaining Category Hierarchy

A category hierarchy is used to view and create hierarchies of categories to provide the requester with browsing categories.

Although you can have any number of categories in the system, the performance of the Category Hierarchy page may be slow if it contains too many top-level browsing categories. If you do have many browsing categories, it is best to categorize them into a manageable number of top-level browsing categories.

Note: If you plan to have a large category hierarchy, consider using the XML schema loader to expedite your schema management.

To create or modify a hierarchy of categories:

  1. In iProcurement Catalog Administration, select the Schema tab.

  2. Click the Category Hierarchy subtab.

  3. On the Category Hierarchy page, do any of the following:

  4. If you are creating a top-level or child category, enter the following information:

  5. If you are inserting an existing child:

To find categories within the hierarchy:

To create a parent category:

  1. Find your category hierarchy:

  2. To create a topmost browsing category that will exist directly under the root category, click Create Top-Level Category. (If needed, you can later move this category to another level.)

  3. To create a browsing (parent) category under an existing browsing category, select the existing category and click Create Child.

    Note: Any category created through the category hierarchy is a browsing category that can contain only other categories, not items.

To create a child category:

  1. Find your category hierarchy:

  2. To create a child browsing category, select the category and click Create Child.

  3. To create a child shopping category, do not use the category hierarchy. Click Schema then Item Categories to create your shopping category. Return to the hierarchy, select the browsing (parent) category, and click Insert Existing Child to insert your new shopping category.

To move categories around:

  1. On the Category Hierarchy page, select the desired category and click the Remove icon. The category is removed from the hierarchy, but still exists in the system.

  2. Select the new desired parent category and click Insert Existing Child.

  3. Search for and select the removed category.

  4. Click Apply.

    Note: When you move a browsing category, the category and all its subcategories, if any, are moved to the new location in the hierarchy.

To delete a browsing category:

  1. On the Category Hierarchy page, locate the browsing category that you want to delete.

  2. You may need to click the expand icon to find the category, if it exists under a parent category.

  3. Click the Delete icon for the category.

    Note: Deleting a category removes it entirely from the catalog. Deleting a category does not delete that category's subcategories, if any.

  4. A job is created for deleting from category hierarchy.

To delete an item category, use Manage Item Categories.

To remove categories from the hierarchy:

To remove categories from the hierarchy:

  1. On the Category Hierarchy page, locate the browsing or item category that you want to remove.

  2. You may need to click the expand icon to find the category, if it exists under a parent category.

  3. Click the Remove icon for the category.

Removing a category does not delete it. The category still exists, but it is no longer part of the hierarchy. If the category that you removed contains subcategories, then the subcategories are also removed from the hierarchy. (It is like removing a branch from a tree. The removed branch still contains its sub-branches.)

In the following example, removing Office Supplies disconnects it from Office Equipment, Accessories and Supplies:

Office Equipment, Accessories and Supplies < - browsing category
   Office Supplies < - browsing category
      Desk Furniture < - shopping category
Writing Instruments < - browsing category
   Ball Point Pens < - shopping category 

When browsing categories online, requesters now see:

Office Equipment, Accessories and Supplies < - browsing category
Writing Instruments < - browsing category
   Ball Point Pens < - shopping category

The removed browsing category, Office Supplies, still contains Desk Furniture. The shopping category Desk Furniture still contains its items. Requesters can still search for specific items in Desk Furniture, but they cannot browse for them through the hierarchy.

A job is created for removing the category from the hierarchy.

iProcurement Shopping Category Mapping

Use shopping category mapping to map Oracle iProcurement catalog categories to categories defined in Oracle Purchasing. This ensures that the items you upload that are linked to shopping categories will not error out.

Features of online shopping category mapping:

To map shopping categories:

  1. In iProcurement Catalog Administration, select the Schema tab.

  2. Click the Category Mapping subtab.

  3. On the Category Mapping page, click Shopping Category, and search for the shopping category. See: To search for a shopping category.

  4. Select one or more shopping categories and click Map.

  5. Search for the Oracle Purchasing category to which you want to map.

  6. Select the Oracle Purchasing category and click Apply.

To view the current shopping mapping:

  1. On the Category Mapping page, select Shopping Category, and search for the shopping category for which you want to view the mapping. See: To search for a shopping category.

  2. Note that only shopping categories are mapped. Browsing categories cannot be mapped.

    Tip: Alternatively, search for the browsing category. Use the hierarchy icon to view its shopping categories, and then search for the shopping categories.

  3. Once the item category is listed, click the Oracle Purchasing category to which it is mapped.

  4. The resulting page displays all of the shopping categories that are mapped to that Oracle Purchasing category.

To remove the current shopping mapping:

  1. On the Category Mapping page, search for the shopping category for which you want to remove the mapping. See: To search for a shopping category.

  2. Note that only shopping categories are mapped. Browsing categories cannot be mapped

    Tip: Alternatively, search for the browsing category. Use the hierarchy icon to view its shopping categories, and then search for the shopping categories.

  3. Once the item category is listed, click its Remove Mapping icon.

    Note: There is a concurrent request for removing shopping category from the hierarchy.

To search for a shopping category:

Oracle Purchasing Category Mapping

Use Oracle Purchasing category mapping to map categories defined in Oracle Purchasing to categories created in Oracle iProcurement. Online Oracle Purchasing category mapping is optional, to achieve the following:

Note: You cannot map Oracle Purchasing categories to a category that contains subcategories; you can map only to the lowest-level (item) categories.

For example, the following categories are defined in Oracle Purchasing:

Category Code Category Description
0215.MISC Miscellaneous Office
0217.MISC Miscellaneous Furniture

In Oracle iProcurement, these categories display by their category description to requesters. (If no description is provided - it is optional - then the categories display by their category code to requesters.) You may wish to display a single category name that is more meaningful to requesters than its code or description. In this example, you create a category called Office Supplies in Oracle iProcurement. Then you use Oracle Purchasing category mapping to map 0215.MISC and 0217.MISC to Office Supplies. When requesters order items, they see the category Office Supplies, but internally this category is mapped to 0215.MISC for all miscellaneous office items and 0217.MISC for all miscellaneous furniture items. Once viewed in Oracle Purchasing, the requisition and purchase order display 0215.MISC or 0217.MISC accordingly.

If the profile POR: Autocreate Shopping Category and Mapping is set to Yes, then for any new Oracle Purchasing category, a shopping category and the corresponding mapping are automatically created. If the profile is No, then no shopping category and mapping are created. You can create them manually.

To map categories using Oracle Purchasing category mapping:

  1. In iProcurement Catalog Administration, select the Schema tab.

  2. Click the Category Mapping subtab.

  3. Click the Purchasing Category subtab and search for the Oracle Purchasing category. See: To find an Oracle Purchasing category.

  4. Select one or more Oracle Purchasing categories and click Map.

  5. Search for the shopping (Oracle iProcurement) category to which you want to map.

  6. Select the shopping category and click Apply.

To view the current Purchasing mapping:

  1. On the Category Mapping page, search for the Oracle Purchasing category for which you want to view the mapping. See: To find an Oracle Purchasing category.

  2. Once the category is listed, click the shopping category to which it is mapped.

  3. The resulting page displays all of the Oracle Purchasing categories that are mapped to that shopping category.

To remove the current Purchasing category mapping:

  1. On the Category Mapping page, search for the Oracle Purchasing category for which you want to remove the mapping. See: To find an Oracle Purchasing category.

  2. Select one or more Oracle Purchasing categories and click Remove Mapping.

To find an Oracle Purchasing category:

Maintaining Catalog Content

In Oracle iProcurement Catalog Administration, maintaining catalog content includes both getting the content information into the catalog and the upkeep of that catalog.

Maintaining Local Content

Filling the local catalog with content, items and services, consists of the following activities.

  1. Enabling catalog authoring is used to control who can update the catalog. See: Enabling Catalog Authoring.

  2. Catalog load is used to load content into the catalog from data contained in files. See: Loading Catalog Content.

  3. Online catalog authoring is used to make updates directly to the catalog using the Oracle iProcurement Catalog Administration Web interface. See: Online Catalog Authoring.

Other activities related to maintaining local content:

Enabling Catalog Authoring

A global purchase agreement is created by a buyer in Oracle Purchasing. The buyer selects the Enable Catalog Administrator Authoring option from the Actions list to enable the agreement for catalog administrator authoring. See: Using Agreement Actions, Oracle Purchasing User's Guide.

Loading Catalog Content

Loading the catalog from existing data files involves the following tasks:

To download templates and instructions:

  1. On the iProcurement Catalog Admimistration home page, click the Upload subtab.

  2. On the View Document Upload History page click Upload.

  3. On the Upload Document page, click Download Resources to open the Download Resources page.

    the picture is described in the document text

    Note: The resources downloaded from this page and from the global purchase agreement Upload Lines page are the same.

  4. Decide whether you will upload your content using text, XML, CIF, or cXML files.

  5. If you are loading a spreadsheet text file and all your items are in the same category, select the appropriate category name.

  6. Click Download and save the resource file to a convenient location.

    The resource file contains various template files and a readme file that contains detailed instructions and examples. The template files vary depending on your choice of upload file type. If you are creating an upload for the first time, open and review the readme file first.

    Note: : If you have recently updated Oracle iProcurement, it is important to use the latest version of the DTD or templates. If you upload your catalog items using an older version of a template, the loader may find errors in your file.

To load catalog items for blanket purchase agreements and quotations:

  1. Once you have a completed catalog item file ready to upload, save it to the location of your choice.

  2. Navigate to the iProcurement Catalog Administration home page. Click Agreement. On the View Document Upload History page click Upload.

  3. On the Upload Document page:

  4. If you are uploading a CIF or cXML file, select a Classification Domain. See the Readme file for CIF or cXML for details: To download templates and instructions.

  5. If you want to apply category mapping or some other code conversion to data in the file, select Yes for "Apply Oracle e-Commerce Gateway Mapping." See Applying Category Mapping.

  6. Optionally, select an error limit for "Set Error Tolerance."

  7. Click Submit. When the loader receives your file, validation begins. A confirmation page displays the job number that is automatically assigned to your job. Check the status of your job to make sure that no errors occurred during the upload.

To load catalog items for global blanket purchase agreements:

  1. Once you have a completed catalog item file ready to upload, save it to the location of your choice.

  2. Return to the iProcurement Catalog Administration home page. Click Agreement. If needed, run a search for the global agreement you wish to upload items to.

  3. Select your global agreement and open it for update.

  4. Select Via Upload from the Add Lines list and click Go. On the Upload Lines page:

  5. If you are uploading a CIF or cXML file, select a Classification Domain.

  6. Select an option for Submit for Approval.

  7. If you want to apply category mapping or some other code conversion to data in the file, select Yes for "Apply Oracle e-Commerce Gateway Mapping." See Applying Category Mapping.

  8. Optonally, select an error limit for "Set Error Tolerance."

  9. Click Submit. When the loader receives your file, validation begins. A confirmation page displays the job number that is automatically assigned to your job. Check the status of your job to make sure that no errors occurred during the upload.

Providing Content Translation

For translation details, see the Readme files when Loading Catalog Content

Monitoring Upload Status

To check the status of catalog uploads:

  1. For blanket agreements and quotations navigate to the View Document Upload History page to view the list of jobs.

  2. Use the raised column headings to sort by job or load date, if needed.

  3. Your jobs are assigned one of the following status readings. (For file uploads, large files may take some time to load. You do not need to remain logged in while a job completes.)

  4. If the job failed, try submitting it again. For file uploads, correct your file and upload it again. See: To correct catalog upload errors.

Upload Errors

To correct catalog upload errors:

  1. On the View Document Upload History page, find the jobs with status Error.

  2. For failed jobs, click the status link.

  3. On the View Upload Errors page, a description of each error displays. Edit the incorrect fields in your file. Rejected lines indicate validation errors.

  4. For failed jobs with no rejected lines, the file experiences a format error.

    If you uploaded global blanket agreement items, you can check the job status by looking at the Upload Status column in the agreement summary (this column is hidden by default and you must personalize the page to see it). In case of and error, there is a link to see the errors. You must discard the errors before you can update the agreement.

    For more information on correcting upload errors, see the Readme file that is part of your Resources file. See: Loading Catalog Content.

  5. Once you have corrected the errors, save and re-upload the file.

Additional Information About The Job Or Error

If you have trouble diagnosing an error in a job, or if you want to monitor the job in Oracle Applications, use the Requests window in Oracle Applications or Oracle Purchasing. The number assigned to your job on the View Document Upload History page is the same as the Request ID in the Requests window. Use the View Log button in the Requests window to get more details on the errors, if needed.

Note: You must be logged on as the same user who submitted the job to access the View Log button for the request.

Catalog load jobs are named as follows in the Requests window:

Note: The Requests window uses different status readings for its jobs. For example, a file with a status of Failed on the View Document Upload History page has a status of Completed - Warning in the Requests window.

e-Commerce Gateway Category Mapping

If the Apply Oracle e-Commerce Gateway Mapping option during loading is set to Yes, Oracle iProcurement checks whether category mapping is set up in Oracle e-Commerce Gateway. If the category in the file matches a category that is mapped in Oracle e-Commerce Gateway and is in the catalog, the loader adds the item to the mapped category. This option applies to all item load files.

The e-Commerce gateway category mapping always performs a look up of shopping categories from the external category provided. The loader uses this derived shopping category and any additional category mappings configured in the iProcurement Administration Tool to determine an item's shopping and Purchasing category as it is loaded into the catalog.

Choose No if you do not want to use category mappings in Oracle e-Commerce Gateway. For example, you may have set up the category mapping strictly for use with punchout catalogs or some other purpose, and do not want those mappings to apply to categories in the local catalog. Choose Yes if you want to apply already-established category mapping to your local catalog.

Flow

The mapping process flows as follows:

Details

The following table shows the fields upon which the loader performs category mapping, depending on the file format:

File Format Category Field that is Mapped
Tab-delimited text Shopping Category
XML
<SHOPPING CATEGORY>
Catalog Interchange Format (CIF) version 2.1 SPSC Code
CIF version 3.0 Classification Codes (or SPSC Code if Classification Codes is not provided)
cXML Classification

Oracle iProcurement performs the mapping on the category name specified in the file; however, if you also specified a category key, Oracle iProcurement maps the key if it can't find the name. The category mapping is case insensitive. (The supplier validation for supplier-specific mapping is case sensitive.)

Category mapping is not performed on schema files that you upload.

Examples

Scenario 1:

The item will be loaded to the catalog with a Shopping Category of Folders and Purchasing category OFFICE.SUPPLIES.

Scenario 2:

The item will be loaded to the catalog with a Shopping Category of Folders and Purchasing category OFFICE.STUFF.

Scenario 3:

The item will be loaded to the catalog with a Purchasing category of OFFICE.SUPPLIES and no value for Shopping Category.

Scenario 4:

Oracle e-Commerce Gateway enables you to specify mapping for a specific supplier, or for no specific supplier. The loader always chooses supplier-specific mapping over non-supplier-specific mapping.

Supplier External Category Oracle Purchasing Category
Supplier A File Folders OFFICE.FOLDERS
(no supplier specified) File Folders OFFICE.MISC

In this example, the category File Folders in the file is mapped to Purchasing category OFFICE.FOLDERS if the supplier in the Purchasing document being loaded to is Supplier A. If the supplier in the file is Supplier B, then File Folders is mapped to Purchasing Category OFFICE.SUPPLIES. A shopping category is derived from the Purchasing category.

If we are loading to a document associated with supplier A, the item will be loaded to the catalog with a Shopping Category of Folders and Purchasing category OFFICE.SUPPLIES.

Online Catalog Authoring

To use online catalog authoring:

  1. From the iProcurement Catalog Administration Agreements tab select the agreement to update. If the agreement you want is not visible, use a different View or Search. See: Finding Agreements.

  2. Catalog lines can be added from existing catalog items, uploaded, or manually entered. See: Updating Agreements.

  3. The updated agreement is submitted for approval.

  4. If acceptance is defined as required for catalog administrators, the buyer will receive a notification to review and accept the changes submitted by the catalog administrator. The changes accepted by the buyer are incorporated in the document and it is submitted for approval.

  5. Once approved, the agreement content is available for requesters in Oracle iProcurement.

Finding Agreements

  1. From the Agreements tab of the iProcurement Catalog Administration home page you can view your agreements using a set of predefined search parameters or click Search to enter your own.

    If you click Search you can enter Agreement, Supplier, Buyer, or Approval Status information and click Go. You may also add additional search parameters and click Save Search to create your own personalized view.

    You can also create your own specialized views and set the default view by clicking Personalize. See the online help for more details.

  2. From the search results you would select the agreement that you want to work on, select what you want to do with the agreement from the Select Agreement list, and click Go.

Updating Agreements

  1. Select the agreement you want to work on and choose the Update action. You will be able to manage or add to your selected agreement.

    Note: You can only update line information for the agreement. Clicking on the Header or Control tabs provides a view of that information for the agreement. Only an Oracle Purchasing buyer can make changes.

  2. On the Update Blanket Purchase Agreement page you can mange existing agreement lines. You access the management tools using the icons found in the Actions column:

  3. On the Update Blanket Purchase Agreement page you can add new lines. You have several options for adding lines:

  4. Click Save to save your changes and then Submit to initiate workflow approval. If appropriate in your organization, you can provide a justification before submitting for approval by clicking Approval Options.

Reviewing Catalog Changes

The Difference Summary page for catalog changes provides a summary between new catalog content and the last approved version. When suppliers or catalog administrators make changes to catalog data this summary highlights the changes. You can review and verify changes prior to submission. You can sort and drill down on the summary to view additional information as well as export changes to a spreadsheet to further manipulate the data.

Similarly, buyers can also access the Difference Summary page when reviewing changes submitted from a supplier or catalog administrator. The summary gives the buyer a clear snapshot into the requested changes, so they can judiciously accept or reject the changes.

Note: The difference summary is no longer be available after the buyer accepts the changes.

To view the Difference Summary:

  1. Find and select your agreement from the Agreements tab of the iProcurement Catalog Administration home page.

  2. Select View Difference Summary from the Select Agreement list, and click Go.

Obtaining Change Acceptance

Suppliers and catalog administrators can submit a global blanket purchase agreement (GBPA) for approval. When they submit the document for approval, a notification is sent to the buyer assigned to the GBPA header for acceptance. The buyer can then:

As soon as the buyer submits the accepted changes for approval, the system will submit the document to the approval hierarchy. From this point on, the following is true:

Understanding Locking

Once a document is being edited by someone, the document becomes locked. The Purchasing buyer has the option of cancelling the pending changes in a locked document and updating the document himself.

External Content

Requesters using Oracle iProcurement can link ("punchout") using an Internet connection to external supplier catalogs. Two versions of this type of external content can be configured to access supplier hosted catalogs, punchout and transparent punchout. Brief discussions of each follow and also see Catalog Content Structure

Punchout Catalog Hosted by Supplier or Marketplace

When creating requisitions, requesters can punch out directly to an Oracle Exchange marketplace, such as Exchange.Oracle.com, or to a supplier's Web store (to access supplier-hosted catalogs). After selecting items for purchase, requesters return to Oracle iProcurement to add more items to their cart and check out as they normally do. For more information about setting up punchout, see the Oracle Procurement Buyer's Guide to Punchout and Transparent Punchout. A supplier version of this guide is available, Oracle Procurement Supplier's Guide to Punchout and Transparent Punchout.

Transparent Punchout Catalog Hosted by Supplier or Marketplace

A transparent punchout catalog (also known as a distributed search) lets requesters search for items on an external site without leaving Oracle iProcurement. Unlike punchout, requesters do not access the site directly. Instead, when the requester searches for items, the transparent punchout works in the background to access the remote catalog and returns the matching items directly to the search results in Oracle iProcurement. Requesters do not necessarily know the items came from an external site. From the Search Results page, requesters add the items returned from the transparent punchout to their shopping cart and check out as they normally do.

From Oracle iProcurement, you can set up a transparent punchout to a supplier site or to an Oracle Exchange marketplace, such as Exchange.Oracle.com. For more information, see the Oracle Procurement Buyer's Guide to Punchout and Transparent Punchout. A supplier version of this guide is available, Oracle Procurement Supplier's Guide to Punchout and Transparent Punchout.

Related Topics

Understanding the Procurement Catalog

Maintaining Local Content

Smart Forms

Requesters can procure an item or service that is not found in the catalog. For these cases, they can use a non-catalog request. The non-catalog request offers the ability to add an item or service to the shopping cart based on a description of the item or service. Through the use of smart forms, companies can conveniently control both the list of fields and whether a particular field is enterable or pre-defined. For example, purchasing organizations can lock-down the purchasing category for certain requests and thereby more accurately categorize spend. Similarly, purchasing administrators can ensure spend is exclusively directed to preferred suppliers, and default contract numbers achieve touchless buying.

The following figure shows the non-catalog request that requesters can enter. In the Item Type field, requesters can enter goods billed by quantity, service billed by quantity, or goods or services billed as an amount.

the picture is described in the document text

In addition to this standard non-catalog request, you can create different smart forms and assign them to one or more stores.

Oracle iProcurement provides a default standard smart form. The catalog administrator can create multiple additional smart forms. For example, you can create a Computer Services smart form and an Office Services smart form. Once these smart forms are assigned to a store, both appear for the requester to select from.

To use the single, standard smart form that Oracle iProcurement provides, you do not need to perform any setup other than the profile options.

Setup Steps

  1. Set Profile Options (required)

  2. Define Commodities (optional)

  3. Create A Smart Form (optional)

  4. Assign A Smart Form To A Store (required, if you create new Smart Forms)

Set Profile Options (required)

Set the line types profile options listed in Profile Options.

Define Commodities (optional)

You can define commodities for use by the non-catalog request template. Commodity is a display-only field on the non-catalog request template that defaults based on the category selected. Define commodities to provide a default category on the template, and you want to restrict the requester to choose only categories within that commodity. For example, for a Computer Services non-catalog request, requesters can only select categories in the Technical Services commodity. (Alternatively, you can enter a default category in the template and make the Category field non-editable.)

Note: The requester may see only a subset of the categories in that commodity if those categories are inactive.

Commodities are groupings of categories. Use commodities to group categories that you have already defined in the Purchasing Category set in Oracle Purchasing. You can place only Purchasing categories in these commodities.

For example, you create the commodities Filters and Brakes to group the following Purchasing categories already defined in Oracle Purchasing:

Example Commodities and Categories
Commodity Purchasing Category Category Code in Oracle Applications
Filters Air Filters AIR.FIL
Filters Oil Filters OIL.FIL
Brakes Brake Shoes SHOES.BRAKES
Brakes Brake Pads PADS.BRAKES
Brakes Brake Foundations FOUND.BRAKES

Note: You cannot create a hierarchy of commodities. Only one commodity level, higher than the category level, is supported.

Commodities are visible across all operating units and organizations.

A category cannot belong to more than one commodity.

To define commodities:

  1. Log in to Oracle Applications using one of the following responsibilities:

  2. Use the following navigation to access the Commodities setup page: Setup > Items > Commodities > Commodities.

    Note: If you cannot find the Commodities menu, then you might be logged in with a customized responsibility. The system-provided Purchasing Super User responsibility comes with the Commodities menu built in. Use the system-provided responsibility if you cannot find the Commodities menu.

  3. On the Commodities page, click Create Commodity.

  4. On the Create Commodity page, enter:

  5. Make sure that Active is selected.

    You can assign categories only to active commodities. (You can make all other changes, such as removing categories and changing person assignments, to active or inactive categories.)

    Both active and inactive commodities appear in the non-catalog requests.

  6. Assign the desired categories to your commodity:

  7. Click Apply.

  8. You do not need to perform the Assign Person functionality to use commodities with non-catalog requests.

Creating And Updating A Smart Form

To define the smart form:

  1. In iProcurement Catalog Administration, select Stores.

  2. Click the Smart Forms subtab.

  3. On the Manage Smart Forms page, click Create Smart Form.

    the picture is described in the document text

  4. On the page for creating or editing the smart form, enter the following fields:

  5. Continue with the steps below for editing the smart form fields.

To edit the smart form fields:

  1. On the page for creating or editing the smart form, select whether each field is User Editable. If you de-select User Editable for a field, then the requester cannot change it.

    Note: All fields in the Default Item Information section are required when the requester enters the smart form. Do not de-select User Editable for a required field, unless you enter a default value for it.

  2. If you want to provide default values for any of the following fields in the smart form, enter them here. For example, if your smart form is designed for items that are typically ordered by the Box, then select Box as the Unit of Measure.

  3. If you want to assign an information template to your smart form, click Add Information Template. For example, if the smart form is for business cards, assign a business card information template. This information template appears at the bottom of the non-catalog request page. In this example, the information template would include fields for a name, address, and phone number for the business card. For information on setting up information templates, see: Information Templates.

  4. Continue with the steps below to assign the smart form to a store.

Assign A Smart Form To A Store (required)

If you created a smart form, you must assign it to a store for it to be visible to requesters. Assign it to either of the following stores:

To assign the smart form to a store:

  1. From the Stores subtab of the Stores tab, select a store to update.

  2. Assign the smart form to either the non-catalog request store provided by Oracle iProcurement or a new store that you create. See the instructions for Creating Or Editing A Store.

  3. When you assign more than one smart form to a store, the store will prompt you to provide a sequence number for each smart form. Smart forms that are available to a requester (based on operating unit context) will appear in sequence based on their sequence numbers.

Any smart form that you add to a store appears in the Request Type drop-down menu, under its smart form name, when the requester accesses the non-catalog request. For example, you can create a Computer Supplies smart form and an Office Supplies smart form and assign them to the same store. Both smart forms display in the Request Type menu for that store. The fields in the request vary depending on which smart form the requester selects.

Profile Options

For profile setup instructions, see Set Profile Options. To use each of the possible item types, set the following profile options:

  1. POR: Goods Line Type

  2. POR: Rate Based Services Line Type

  3. POR: Amount Based Services Line Type

    Note: It is possible to have unit values defaulted onto the non-catalog request based on the line type. To do this, associate a unit of measure with the line type in Oracle Purchasing.

Function Security

To hide access to the standard non-catalog request template that Oracle iProcurement provides, exclude the submenu iProcurement: Non-catalog Request (ICXPOR_NONCATALOG) from the Internet Procurement Home menu when defining users' responsibilities.

Workflow

You can configure the PO Create Documents workflow to automatically source non-catalog requests from a contract. The attribute name that controls this option is Should non-catalog requests be autosourced from contract? If set to Yes, then if a valid contract purchase agreement exists for the given supplier, then the system automatically creates a purchase order that references that contract. The default value for this attribute is No. For information about the PO Create Documents workflow, see Customize Workflows.

Implementation Considerations

When you create a smart form, you must create it for a specific Organization (operating unit).

For example:

Managing Content Presentation

Oracle iProcurement uses stores and content zones to organize items for requesters. Each store contains one or more content zones. For more information, see Catalog Content Structure. When requesters search, Oracle iProcurement searches across all local and transparent punchout content zones in the store and displays the results. (You search one store at a time.)

Grouping similar content into a single store provides the following benefits:

Oracle iProcurement Catalog Administration provides the following tools designed to aid you in organizing your catalog content:

There are some additional tools available that impact the presentation of your content:

Maintaining Stores

A store enables you to group content zones and smart forms into a single, searchable store. The store should be easy for requesters to understand - for example, a store containing all computer supplies or all office supplies.

Maintaining A Store

  1. In the iProcurement Catalog Administration, select the Stores subtab from the Stores tab.

  2. On the Manage Stores page, click Create Store to create a new store. If you want to update an existing store, click the Pencil (Update) for your store.

    the picture is described in the document text

  3. Click Continue to see if additional configuration is required for your store.

  4. On the Create Store: Configuration page you can provide the store sequence, indicate if local content is to be displayed first in the search results summary screen, and only on that screen, by checking "Show local content first." Force a search results match by checking "Always Show as Match."

  5. Click Apply to save your store.

  6. If you want to vary language-specific fields, such as the name and description, see Translating Data.

  7. If you want to test your store, from the Manage Stores page click Test Stores Setup. For the operating unit and responsibility combination you can see details of the stores and content zones configuration.

To sequence stores:

You can sequence your stores so that they are presented in a specific order to iProcurement requesters. When a requester logs into Oracle iProcurement, stores are displayed from left to right, top to bottom, in order of sequence numbers. Stores that the requester does not have access to are omitted from the Shop home page.

  1. On the Manage Stores page, click Sequence Stores. It is recommended that you sequence the order in which multiple stores display on the Shop page; otherwise, the stores display in a system-generated order.

  2. Enter sequence numbers. You can reuse sequence numbers or use decimals.

  3. Click Apply.

  4. The stores are sequenced horizontally, three per row. For example, stores sequenced 1 through 4 display as follows on the Shop page:

    Store 1 Store 2 Store 3
    Store 4    

To delete a store:

Deleting a store does not delete the content zones in the store; it deletes the store definition.

Note: Any content zones that are not assigned to a store are not accessible to requesters. To enable requesters to search the content zones that were in your deleted store, assign the content zone to another store.

If the store you delete is a requester's Favorite Store (requesters can select this in their preferences), then the requester's new favorite store defaults to the store with the lowest sequence.

To delete a store:

  1. In the iProcurement Catalog Administration, select the Stores subtab from the Stores tab.

  2. On the Manage Stores page, click the Trash Can (Delete) icon for the store.

  3. Click Yes to confirm the deletion.

Profile Options

It is recommended that you leave POR: My Favorite Store at the default setting of -1 during implementation. When set to -1, Oracle iProcurement automatically displays the store that has the lowest sequence number (you set the sequence when defining the store) and that the requester has access to, if you use content security to control catalog access.

For a list of profile options that affect search behavior, see Search Engine Logic.

Note: The requester can change the default favorite store by selecting My Favorite Store in the iProcurement Preferences.

Implementation Considerations

Note the following about creating stores:

Maintaining Content Zones

Content zones are containers for your catalog items and services. You manage your content zones from the Manage Content Zones page available as a subtab of the Stores tab.

the picture is described in the document text

The Manage Content Zones page provides the following information for each content zone:

Maintaining A Local Content Zone

To create a content zone:

  1. In iProcurement Catalog Administration, select the Content Zones subtab from the Stores tab.

  2. On the Manage Content Zones page, select Create Local Content Zone from the drop down list and click Go.

    the picture is described in the document text

    For detail regarding the different types of catalog content see Understanding the Procurement Catalog.

    Note: The default local content zone, All Local Content, contains items from all suppliers and categories. You can modify or delete it to fit your needs.

  3. On the Create Local Content Zone page, enter a Name and Description. The name and description are used for your information only, they do not appear in the Oracle iProcurement shopping pages.

  4. Suppliers: Select the suppliers whose items you want to appear in this content zone:

  5. Categories: Select the categories whose items you want to appear in this content zone:

    Note: If there is a Purchasing category to Shopping category mapping for a particular Purchasing category, iProcurement considers items with that Purchasing category to be shopping categories (by way of the category mapping).

  6. Assign Content Zone Security: Select the security for this content zone:

  7. Click Apply to return to the Manage Content Zones page.

To make this content zone accessible from other stores:

To add suppliers:

To add categories:

To add operating units:

To add responsibilities:

Maintaining An Informational Content Zone

To create an informational content zone:

  1. In iProcurement Catalog Administration, select the Content Zones subtab from the Stores tab.

  2. On the Manage Content Zones page, select Create Informational Content Zone from the drop down list and click Go.

    For detail regarding the different types of content zone content see Understanding the Procurement Catalog.

  3. On the Create Informational Content Zone page, enter the following:

  4. If you want to vary language-specific fields, such as the name and description, seeTranslating Data.

  5. Assign Content Zone Security: Select the security for this content zone:

  6. Click Apply to return to the Manage Content Zones page.

  7. Any content zone you create must be added to a store to be searchable. Either add the content zone to the default Main Store that Oracle iProcurement provides or create your own store to which to add the content zone. See: Creating Or Editing A Store.

Maintaining A Contractor Request Content Zone

Oracle iProcurement provides the Contractor Request content zone for use by Oracle Services Procurement.

If your company has enabled Oracle Services Procurement, then requesters can click Contractor Request directly below the Shop tab and be taken to the contractor request entry page.

If desired, you can make contractor requests additionally accessible in a store. For example, you can assign the Contractor Request content zone to a store that you created. When a requester clicks the store on the Shop page, all of the content zone in that store are displayed. The requester can then click the Contractor Request content zone and be taken to the contractor request entry page. (If you create a store that contains only the Contractor Request content zone, then clicking the store takes the requester directly to the contractor request entry page.)

The method of clicking Contractor Request directly below the Shop tab always remains. Including the Contractor Request content zone in a store is an additional option for you, to make contractor requests accessible in other places.

Manage A Content Zone (Update, Copy, Delete)

In iProcurement Catalog Adminstration, click the Content Zones subtab in Stores.

Function Security

None, but you can optionally control access to content zones. .

Related Topics

Understanding the Procurement Catalog

Maintaining Stores

Content Translation

The language in which you are currently viewing fields and data in Oracle iProcurement is called the session language. The language in which you first entered the data is the "initial" language.

For example, you have three language installations of Oracle iProcurement - English, French, and Japanese. The first time you enter these fields, your session language is English. The data you enter is propagated to French and Japanese as well as English. Any change you make in English is made in all languages; however, once you change your session language and change your session language, you must maintain that language separately. For example, you change your session language to French and change a catalog name. Later, you change your session language to English and change the catalog's name in English. That change is now made only in English and Japanese. The application detects that you already made a language-specific change to the French version, and no longer propagates changes to French, unless your session language is currently French.

Catalog Content That Can Vary By Language

The following language-specific fields can be translated in a multiple language installation of Oracle iProcurement:

Punchout catalog definition:

Transparent punchout catalog definition:

Local catalog definition:

Informational catalog definition:

Store definition:

Non-catalog request template:

Base and category descriptors:

Item and browsing categories:

* The options or values in these fields, such as Yes or No, vary depending on your session language.

Schema and items that you upload can also be translated. See the Readme files

Note: Translating a catalog definition does not mean that the catalog's contents are automatically translated. It depends on your setup. For example, data in Oracle Purchasing honors the existing translations of the data. If you provided both German and English versions of a category name when defining categories in Oracle Purchasing, then both German and English versions of the category name are available in Oracle iProcurement. In another example, you can translate a punchout catalog's name, but the supplier controls whether the data exists in a particular language.

Changing The Session Language And Translating The Content

To vary online data by language, change the session language:

  1. Enter and save the data in one language first. For example, create a store in French.

  2. Click "Preferences" at the top of any page.

  3. In your general preferences, select the desired language, such as English, and click Apply Changes.

  4. Return to the page where you entered the data. For example, return to the page where you defined your store.

  5. Translate the language-specific fields to the new language.

  6. Save your changes.

Managing Images

Images in the catalog are one of the following kinds:

Including images in the catalog is optional. If you provide images for items, the corresponding image appears when a requester searches for and views items, assisting the user in selecting the correct item for purchase. JPEG and GIF image formats are recommended.

Note: The supplier site or marketplace externally hosts images associated with transparent punchout items. For more information, see the Oracle Procurement Supplier's Guide to Punchout and Transparent Punchout.

Uploading Items With Images

To upload images, use the PICTURE or THUMBNAIL_IMAGE fields in an XML upload file, or the Image or Thumbnail Image fields in a text upload file. These images can be either internally stored files or URLs that point to an image stored remotely.

You can also use the loader to associate an image with an item you have extracted, if the item has a supplier item number. (The loader requires a supplier item number.) See the instructions for creating thumbnail images for items.

Specifying Image Files Stored on a Local Server

To reference image files stored on the local server:

  1. For the POR: Hosted Images Directory profile option, enter the directory path you use to store image files.

    This path usually corresponds to the OA_MEDIA directory. Contact your database administrator or installation team for the exact location of your OA_MEDIA directory.

  2. Ask your database administrator to transfer the pictures to the directory you specified.

  3. Use the PICTURE descriptor in an upload file to specify a regular sized image for the Item Detail page. Use the Thumbnail Image descriptor to specify a smaller image for the search results and comparison pages

    For information about preparing and uploading files, see:

    Note: The file name for the image is case sensitive.

  4. Load your catalog file. See: Loading Catalog Content

Specifying Image URLs

To specify the URL of the image that resides on the Internet:

  1. Obtain the complete path of the image (for example, http://www.mycompany.com/toplogo2.gif).

  2. Use the PICTURE field in an XML upload file (or the Image field in a text bulk load file) to specify an image URL for the Item Details page. Use the THUMBNAIL_IMAGE field in an XML upload file (or the Thumbnail Image field in a text upload file) to specify a thumbnail image URL for the search results and comparison pages.

    You can use the same image for both the image and thumbnail image, or create separately sized versions. For more information, see the instructions for creating thumbnail images for items.

  3. Load your catalog file. See: Loading Catalog Content.

Authoring Items With Images

You can include images in the catalog content you create using iProcurement online authoring. These images can be either internally stored files or URLs that point to an image stored remotely. See: Online Catalog Authoring.

  1. Navigate to the Create Lines or Update Lines page for the agreement that contains the item you want to display an image.

  2. In the Details region of the page enter the Image Name (file name) or the Image URL.

  3. When you have completed your work on this line, click Apply.

Creating Thumbnail Images For Items

You can upload or author items with thumbnail images, using an image file or image URL.

You can create and size thumbnail images in the following ways:

Creating Store Images

You can also set up stores to display images to help guide requesters. Like item images, store images can be either internally stored files or URLs that point to an image stored remotely.

  1. Follow the instructions for locating image files for items to store your images. See: Uploading Items With Images.

  2. Select the Stores tab in iProcurement Catalog Administration.

  3. If this is an existing store click the Pencil (Update) for that store. If this a new store click Create Store. See: Maintaining Stores.

  4. Enter either an image file name or the URL that links to the image in the Image field.

  5. Click Continue, then Apply when you have completed your entries.

Image Related Profile Options

For details on these and other Oracle iProcurement profile options see: Setting Profile Options.

The following profile options apply to all images:

The following profile options affect thumbnail images:

See: Creating Thumbnail Images For Items

Function Security

The ICX_CAT_ARGEEMENTS_SUMMARY function controls access to the iProcurement page from which files are uploaded, and stores and catalogs are defined. Anyone assigned the iProcurement Catalog Administration responsibility already has access to this function.

Implementation Considerations

If you specify both a server image and an image URL, only the server image appears in Oracle iProcurement.

Note: If your images do not appear after following the instructions in the previous sections, then verify whether you have multiple middle-tier servers, each on a different server. If you do, then you must copy the OA_MEDIA directory and your images to each server, or make the OA_MEDIA directory an nfs-mounted directory that all servers share.

You cannot extract images for master items that do not exist on a blanket agreement or catalog quotation. If the master item exists on a requisition template or ASL entry with a supplier item number, then you can use the loader to associate an image with the extracted item. (The loader requires a supplier item number.)

By default, Oracle iProcurement uses blank image files (invisible to the requester) to display items that do not have images:

You can replace the default blank image files with different image files. For example, if most of your items have images, you can display an image with the text No Image Available for the exceptions rather than a blank space. (This text displays the same in all languages.) The replacement blank image files must have the same names and file format (.gif) as the default ones. You can find the default blank files in the OA_MEDIA directory.

The following functionality can also influence images, if you do not want to maintain images:

You can edit descriptor properties online in iProcurement Catalog Administration or through uploading schema. For more information about descriptors, see Maintaining The Catalog Schema.

Additional Considerations for Thumbnails

The recommended height and width for thumbnail images is 100x100 pixels. You should not exceed a width of 280 pixels because the column width on the Compare Items page is 280 pixels. If the thumbnail image exceeds that, the image wrap.

Additional Considerations for Store Images

The recommended image dimensions for a store or catalog image is 70 by 55 pixels.

By default, Oracle iProcurement uses a blank image file (invisible to the requester) to display items that do not have images. For stores without images on the Shop home page, it uses ag_placeholder_store.gif (70 by 55 pixels) to display the blank image. (Punchout and informational catalogs have no default blank image. When no image is specified, they display only the catalog name and description on the Search Results Summary page.)

Tip: You can use standard clip art icons that Oracle Applications Framework provides. Look in the OA_MEDIA directory for these image files. For example, the file medicalequipment_cctitle.gif is a small picture of a stethoscope, which you could use as an image for a medical supplies store

Managing Searching And Browsing

As part of the procurement catalog setup, you should:

Search Result Layouts

Oracle iProcurement requesters can choose to display shopping search results in either an paragraph search result display format or the grid display format.

To set up search result layouts:

Profile Options

For a list of profile options that affect search behavior, see Search Engine Logic.

Global Agreements

Overview

Using global agreements, purchasing professionals are able to negotiate prices on behalf of multiple organizations within an enterprise and then enable the resulting agreement to be shared by those organizations for procuring products and services.

Global Agreements allow buying organizations to negotiate pricing and define agreements in a centralized shared services environment. Execution against the Global Agreement can be controlled and handled in more than one operating unit. Instead of creating multiple agreements in multiple operating units, you can create a single global agreement that can be viewed and used for sourcing by multiple operating units.

In addition to the Supplier/Supplier Site with whom the agreement was negotiated by the negotiating organization, it may not be the same supplier site which processes the purchase orders from the multiple buying organizations, where the agreement is enabled.

Creating and Using a Global Agreement

Global Agreements in Oracle iProcurements

The following areas are impacted by the global agreements enhancements in Oracle iProcurements: