This chapter covers the following topics:
Oracle iProcurement Release 12 gives catalog administrators the ability to make small and quick updates to catalog content online. The online authoring feature complements the existing batch upload process, which is optimized for large data upload. This release also gives more comprehensive and flexible rules for securing catalog content. Below is a description of the upgrade impact on the catalog management.
Bulk-loaded items in iProcurement will be migrated to newly created Global Blanket Procurement Agreements (GBPA) based on their Supplier, Supplier Site, Currency, Operating Unit, and Contract Reference. From the iProcurement Catalog Administration responsibility, there will be a summary of all newly created GBPAs for bulk-loaded items. There will also be a data-exceptions report that lists all the exceptions that prevent migration of bulk-loaded content to new GBPAs. For more details on how to correct these exceptions, refer to the iProcurement Preupgrade steps in the Oracle E-Business Suite Upgrade Guide: Release 11i to Release 12.
The following is a list of changes in Release 12 as a result of the catalog upgrade:
The upgrade will migrate bulk-loaded items into GBPAs. Release 12 , users will load content into a GBPA and they will no longer need to provide Supplier, Supplier Site, Operating Unit, and CPA/GCPA reference in the file. The bulk-load option will also be available for BPAs and quotes.
In Release 12, users will not be able to load catalog content for all Operating Units. Please refer to the Oracle Purchasing Implementation guide for more details on assigning GBPAs to Operating Units.
Approved Supplier’s Lists (ASLs) will not be shown in iProcurement search results. In Release 12, the Oracle Purchasing Sourcing Rule will be used to determine the best Supplier and Supplier Site combination during the requisition creation process.
The bulk-load file format in Release 12 has been changed. A Converter has been provided for users to convert old files to Release 12 format.
In Release 12, users will not need to run the extractor to update the catalog content. It will be updated in real-time.
The upgrade process will upgrade existing realms, stores, and catalogs to Release 12 stores and content zones in the following way:
Migrate local catalogs to become Local content zones. Local catalogs may contain supplier restrictions. These restrictions are carried forward as supplier restrictions in Release 12 content zones.
Migrate punch out, transparent punch out, and informational punch out catalogs to their corresponding types of Release 12 content zones.
Migrate catalog and non-catalog stores to become Release 12 stores. Release 12 stores can contain both catalog and non-catalog content. Previous stores may contain operating unit restrictions. These restrictions will not be carried forward into Release 12 stores. Instead, these restrictions are applied to every content zone within each store having operating unit restrictions.
Migrate category realms at the responsibility level. In Release 12, category restrictions are applied to each individual content zone.
Migrate item source realms for Responsibilities.
Migrate Default Smart Forms such that they have the lowest available sequence number within Release 12 stores. This way, smart forms that appeared by default previously will continue to appear by default in Release 12.
POR: Approved Pricing Only profile is no longer used. The upgrade will apply the correct settings in each content zone to achieve the same functionality in Release 12.
Migrate descriptor configuration. Previously, it is possible to provide invalid values for Descriptor settings such as Search Result Visibility, Item Detail Visibility, and Searchability— Invalid configuration settings were simply ignored by the system. Release 12 validates Descriptor configurations at the time when they are updated in the user interface, and will not allow any invalid value to be provided.
The upgrade will re-default all the properties for the seeded descriptors from previous releases. For example, visibility, sequence setting and alternate names may change. After the upgrade, administrators should review the seeded descriptors properties and make any necessary changes.
The following notes refer to changes in behavior in Release 12 as a result of Content Security enhancements:
Shopping Lists are migrated but content security is applied differently on Release 12 Public and Favorite lists. In Release 12, items on Shopping Lists are available to a user if that user’s responsibility and Operating Unit context are such that he would have access to that same item through a Store. If the user does not have access rights to an item through the normal Store search and browse function, he will not have access rights to that item on a Shopping List.
Refer to the Oracle iProcurement Implementation and Administration Guide for more details.