How To Diagnose An Issue In The Unified Item Catalog (Release 12 onwards) [ID 461747.1]

To Bottom

Modified:Jul 11, 2012 Type:TROUBLESHOOTINGStatus:PUBLISHED Priority:3

Comments (0)

In this Document

PurposeTroubleshooting Steps

 INTRODUCTION

 TESTCASE

 BASIC FUNCTIONAL SETUP

 ITEM AND CATEGORY DATA

 STORES AND CONTENT ZONES

 SMART FORMS

 SHOPPING LISTS

 ITEM BULKLOADER

 UPGRADE ISSUES

 DEBUG LOGGING

 TRACING

 RELATED CODE FILES

  PATCHE

dummyTop

S

 HOW TO'S / TOOLS

 WHITEPAPER

 DOCUMENTATION

References

Applies to:

Oracle iProcurement - Version 12.0.0 and laterInformation in this document applies to any platform.iProcurement - Version: 12.0

Purpose

This document give information on performing analysis of issues encountered within the Release 12 Unified Catalog in Oracle Procurement products.  The changes include the removal of the requirement for running the extractor concurrent jobs, and a totally new item data model.

Troubleshooting Steps

INTRODUCTION

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:

Catalogs are automatically and perpetually up-to-date and based on real-time data

Support for extensible base and category attributes to enhance the product data catalog. Oracle iProcurement customers can define base and category attributes for their specific needs.

Support for price breaks based on quantity, shipping organization and effective date range.

 

TESTCASE

It is very important to understand as much about a problem as possible, in order to effectively assist in diagnosing the cause and working toward the solution. As such, it is helpful to record a detailed test case, to understand the background, specific set-up, and the steps taken during the process. These should include:

Overview of the setup specifically related to the issue. Demonstration of how the problem is encountered. Is the same type of problem found when performing similar actions in

other pages or forms? Details on the extent of the problem, including details on which Items,

Categories, Users, and Operating Units are affected. Details on when and how the problem might have started occurring

(e.g. after system setup or data changes). Confirm if any customizations are included in the instance, specifically

related to iProcurement and Purchasing?

BASIC FUNCTIONAL SETUP

It has been found that most problems within the item catalog have their root cause in setup.  As such, the following points cover some of the more common setup areas and how to validate they are stored as intended.

a) Profile Options

The following values determine item visibility:

PO: Legal Requisition Type   Value: SUPPLIER - the user can only see purchasable items. The user cannot see any internally orderable items.   Value: INTERNAL - the user can only see internally orderable items.   Value: BOTH - the user can see both purchasable and internally orderable items.

POR: Allow Manual Select SourceWhether to allow a user to manually select how to source an item that is available from multiple internal sources/suppliers. If this profile is set to Yes, a link with text “Select Source” will be displayed for such items.

POR: Enable Advanced SearchIf this profile is set to No, the user would not be able to use advanced search in the local catalog. 

b) Item Attributes

If only some fields for items are incorrectly shown, validate what attributes are set to be 'Search Results Visible' and 'Item Detail Visible'. The following query shows all base attributes that are item detail visible;

SQL> SELECT attribute_name FROM icx_cat_attributes_tl WHERE language = 'US' AND rt_category_id = 0 AND item_detail_visible = 1 order by sequence;

c) Stores

Check the store and content zone setup is as intended, see below for more detail in troubleshooting issues in this area.

d) Item Status

From Release12 onwards, making the Item Status 'Inactive' for a Master Item, the system automatically updates the items Purchasable flag to 'N', making it unavailable in iProcurement (stored in field PURCHASING_ENABLED_FLAG in table MTL_SYSTEM_ITEMS_B).

This rule follows the setup in the Attribute Controls form (Purchasing Responsibility > Setup > Items) where the Status Setting value for Attribute Name 'Purchasable' should be 'Defaults Value' or 'Sets value'.  If it is set to 'Not Used' changes in Item status code will not change the Purchasable flag, and the item will still be available in iProcurement Search.

ITEM AND CATEGORY DATA

- Line Items

Item data is not now stored in a seperate ICX set of tables for use by iProcurement, items are either part of Agreements, Templates, or the Master Inventory Catalog.  iProcurement now has its search based directly on these tables (via Intermedia Indices), so there is a single source of truth, and zero maintainence required.

Occasionally it may be necessary to check item data in the database against that displayed on the iProcurement page (or that was bulkloaded).  As such, the following queries can be used to validate the data in the tables:

For Blanket Agreement Line Items:  SQL> SELECT po_line_id FROM po_lines_all WHERE item_description like '%&description%';   SQL> SELECT count(*) FROM icx_cat_items_ctx_hdrs_tlp WHERE po_line_id = &po_line_id;   SQL> SELECT count(*) FROM icx_cat_items_ctx_dtls_tlp WHERE po_line_id = &po_line_id;

For Requisition Template Line Items:   SQL> SELECT express_name req_template_name, sequence_num req_template_line_num FROM po_reqexpress_lines_all WHERE item_description like '%&description%';   SQL> SELECT count(*) FROM icx_cat_items_ctx_hdrs_tlp WHERE req_template_name = '&req_template_name' AND req_template_line_num = &req_template_line_num;   SQL> SELECT count(*) FROM icx_cat_items_ctx_dtls_tlp WHERE req_template_name = '&req_template_name' AND req_template_line_num = &req_template_line_num;

For Master / Inventory Items:   SQL> SELECT inventory_item_id FROM mtl_system_items_b mi WHERE segment1 like '%&item_number%';   SQL> SELECT count(*) FROM icx_cat_items_ctx_hdrs_tlp WHERE inventory_item_id = &inventory_item_id;   SQL> SELECT count(*) FROM icx_cat_items_ctx_dtls_tlp WHERE inventory_item_id = &inventory_item_id;

(A) The following queries can be used to review all inventory fields for the item:

SQL> SELECT * FROM icx_cat_items_ctx_hdrs_tlp WHERE inventory_item_id = &inventory_item_id;SQL> SELECT * FROM icx_cat_items_ctx_dtls_tlp WHERE inventory_item_id = &inventory_item_id;

Note: The above SQL will provide the value of the org_id and can be compared to the value of the intermedia key that is returned in the debug log. This intermedia key contains org_id value and sqe value apart from keyword being searched.

If the org_id is not present, then there is a setup issue.

(B) Please provide output of the following sql below.

SQL> select * from ctxsys.dr$sqe

Here if the records are present in (A) but do not comply the AND condition in the above sqe,then also the records will not appear in search.

- New Master Items:a) For New master items created and the data is NOT in icx_cat_items_ctx_hdrs_tlp.

1. (Please confirm the software is on the latest code release) all file names are mentioned in this Note ( Related Code Section)2. Stop and Restart the Apache server, Create a new Item and then search iProcurement for the new Item.

b) If after doing (a) and the item still cannot be found, please gather a FND Debug log as shown in the DEBUG LOGGING SECTION If this reports a no data found then the script b6892753.sql needs to be executed. This datafix script will populate the PO_ATTRIBUTE_VALUES, and PO_ATTRIBUTE_VALUES_TLP table for all master items present in icx_cat_item_ctx_hdrs_tlp and not in PO_ATTRIBUTE_VALUES and PO_ATTRIBUTE_VALUES_TLP

Also see the data model in Note 602896.1.

- Categories

Release 12 still requires the mapping of iProcurement 'shopping' categories to underlying Purchasing Categories, as in previous releases (using iProcurement Catalog Administration). The creation and update of items and categories will enable categories for use in iProcurement, where in prior releases it was required to run the Classifications and Items Extractor concurrent requests. The following basic steps show to to create a new category;

1. Create a new Category Segment in System Administrator: Flexfield > Key > Values 2. Choose 'PO Item Category' 3. Go to Purchasing responsibility: Setup > Items > Categories > Category Codes > Enter New Category 4. Go to Category Sets and enter the category in the list of Purchasing Categories. 5. This should allow the category to be used for items.

Categories are stored in the following data structure:

In traces you will see use of MTL_CATEGORIES_KFV which is a synonym of view MTL_CATEGORIES_B_KFV

MTL_CATEGORIES_B_KFV includes decode statements on the segment fields for clearer display of data from underlying table MTL_CATEGORIES_B.

Table MTL_CATEGORIES_B joins to Category Set data in tables : MTL_CATEGORY_SETS_B, MTL_DEFAULT_CATEGORY_SETS

These all join using criteria; MTL_CATEGORIES_KFV .STRUCTURE_ID = MTL_CATEGORY_SETS_B.STRUCTURE_ID AND MTL_CATEGORY_SETS_B.CATEGORY_SET_ID = MTL_DEFAULT_CATEGORY_SETS.CATEGORY_SET_ID

As explained in Note 454694.1, unless you have specific category mapping requirements, its recommended to use Profile Option 'POR:Autocreate Shopping Category and Mapping' = Yes, so that when items are created in new categories they are immediately available for iProcurement users.

- Intermedia Index

As indicated above, in Release 12 onwards there are two intermedia indices (ICX_CAT_ITEMS_CTX_HDRS_TLP and ICX_CAT_ITEMS_CTX_DTLS_TLP) which hold most of the item data used in the search.  This provides much faster and flexiable searching abilities than queries directly on tables or views.  Detail on this is given in the Implementation Guide - Appendix A -"Search Engine Logic". 

As such, these indices must be constantly managed to ensure they match the underlying table data.  This is done seemlessly during code execution (e.g. when create an item), however the following two concurrent jobs are available for explictly performing maintainence if needed in case of some failure:

Purge Catalog interMedia Index (ICXPCIIP) - This request purges; any inactive blankets agreements, inactive and deleted quote lines, inactive and deleted requisition template lines, and master items belonging to inactive purchasing categories.

Rebuild Catalog interMedia Index (ICXRCIIP) - This request refreshes the intermedia indexes used in iProcurement catalog search. An alternative to this is to use the following SQL, however this is not recommended and should only be done when instructed by Oracle Development:

  SQL> exec ICX_CAT_INTERMEDIA_INDEX_PVT.drop_index;   SQL> exec ICX_CAT_INTERMEDIA_INDEX_PVT.create_index;

 

If the underlying data seems ok, but the search is still not returning what is expected, here are some tests and information that can be checked:

a) Get the full Query Text

If the search was run with FND debug log enabled (see below), then the entire intermedia search query is printed to the log output. This will be commonly preceded by log line:

RequisitionAMImpl]:doQuery:: final search query is :

b) Perform an Intermedia Query in SQL*Plus

Execute the following query, replacing words pen/paper with a search word;

SQL> SELECT count(*) FROM icx_cat_items_ctx_hdrs_tlp WHERE contains(ctx_desc, '(${pen})') > 0; SQL> SELECT count(*) FROM icx_cat_items_ctx_hdrs_tlp WHERE contains(ctx_desc, '(${pen} AND ${paper})') > 0;

  - If the above query fails to execute successfully, checks should be run to verify if the Intermedia Setup is OK. [test-intermedia.sql?]  - If the above query returns no results, enable FND debug logging for the user, update the item from the application and submit the changes. Rerun the query and analyse the log text.  - If the query returns too many results, run the following query with relevant language, item and org_id information:

SQL> SELECT inventory_item_id, document_number, po_line_id, line_num, req_template_name, req_template_line_num, supplier, ip_category_name, po_category_id, supplier_part_num, supplier_site_id, source_type, item_type, line_type_id, unit_meas_lookup_code, description FROM icx_cat_items_ctx_hdrs_tlp WHERE contains(ctx_desc, '(${&ItemA} AND ${&ItemB}) AND (((&Org_ID within orgid) AND ({&LANG} within language))*10*10)') > 0;

If this query returns just the expected row, then check again the setup, especially around Stores and Content Zones.

c) Multiple and Duplicate Items

In Release 12 items are shown for each source they come from, e.g. blanket agreements or quotation lines.  The value for base descriptor 'Source' will confirm the items origin.  Items can be compared using the following queries.

SQL> SELECT inventory_item_id FROM mtl_system_items_kfv WHERE concatenated_segments like '%&item_number%';

SQL> SELECT inventory_item_id, po_line_id, req_template_name, req_template_line_num, org_id, language, source_type, owning_org_id FROM icx_cat_items_ctx_hdrs_tlp WHERE inventory_item_id = &inventory_item_id;

 

STORES AND CONTENT ZONES

Stores hold Content Zones and Smart Forms.  Content Zones hold items according to their Category and/or Supplier, and the Users Responsibility or Organization Unit.  Full details on the intended functionality of Stores and Content Zones is given in the Implementation and Administration Guide (B31402-02) - Managing Content Presentation.

The following queries can be used to compare online display and functionality to data stored in the database:

a) These show the Content Zones in the Store, and provide background information for a specific Content Zone:

SQL> SELECT store_id, name, description FROM icx_cat_shop_stores_tl WHERE language = '&language' AND name like '%&StoreName%';

SQL> SELECT content_id, content_type, sequence, display_always_flag FROM icx_cat_store_contents WHERE store_id = &store_id;

SQL> SELECT cont_zone.zone_id, cont_zone.type, supplier_attribute_action_flag, sec_attr.supplier_id, sec_attr.supplier_site_id, category_attribute_action_flag, sec_attr.ip_category_id, items_without_supplier_flag, items_without_shop_catg_flag, security_assignment_flag, sec_cont.org_id, sec_cont.responsibility_id FROM icx_cat_content_zones_b cont_zone, icx_cat_zone_secure_attributes sec_attr, icx_cat_secure_contents sec_cont WHERE cont_zone.zone_id = &content_id AND cont_zone.zone_id = sec_attr.zone_id (+) AND cont_zone.zone_id = sec_cont.content_id (+);

b) Its possible to check organization and responsibility assigned to a content zone using the following queries:

SQL> SELECT zone_id, name, description FROM icx_cat_content_zones_tl WHERE language = '&language' AND name like '%&ZoneName%';

SQL> SELECT security_assignment_flag FROM icx_cat_content_zones_b WHERE zone_id = &zone_id;

SQL> SELECT org_id, responsibility_id, secure_by FROM icx_cat_secure_contents WHERE content_id = &zone_id;

c) Its also possible to check supplier and category restrictions using the following;

SQL> SELECT category_attribute_action_flag, supplier_attribute_action_flag, items_without_supplier_flag, items_without_shop_catg_flag FROM icx_cat_content_zones_b WHERE zone_id = &zone_id;

SQL> SELECT securing_attribute, supplier_id, ip_category_id FROM icx_cat_zone_secure_attributes WHERE zone_id = &zone_id;

d) In addition, the Display Always Flag and search Keywords are used during the setup (no restriction), therefore the following queries can by used to verify this;

SQL> SELECT content_id, content_type, sequence, display_always_flag FROM icx_cat_store_contents WHERE store_id = &store_id;

SQL> SELECT keywords FROM icx_cat_content_zones_tl WHERE language = '&language' AND zone_id = &zone_id;

SMART FORMS

Smart forms for use in Non-Catalog Requests are a flexiable means of including important information and making sure the right values are selected.  This also includes the optional use of Information Templates.  Details on setup is again in the iProcurement Implementation Guide, however the following queries can be used in analysing data further;

SQL> SELECT template_id, template_name, item_description FROM por_noncat_templates_all_tl WHERE language = '&language' AND template_name like '%&form_name%';

Since Smart From visibility is only by Operating Unit;

SQL> SELECT org_id FROM por_noncat_templates_all_b WHERE template_id = &template_id;

Display is also influenced by Display Always Flag and Keywords, which can be checked using:

SQL> SELECT content_id, content_type, sequence, display_always_flag FROM icx_cat_store_contents WHERE store_id = &store_id;

SQL> SELECT keywords FROM por_noncat_templates_all_tl WHERE language = '&language' AND template_id = &template_id;

SHOPPING LISTS

 - Public Lists

Public lists comprise Requisition Templates created in Purchasing for requesters to use as needed. These are not secured, so the following simple queries can be used to check template and their items, for comparison to what is shown in the pages.

SQL> SELECT distinct req_template_name, org_id FROM icx_cat_items_ctx_hdrs_tlp WHERE req_template_name = '&reqTemplateName' AND org_id = &orgId AND language = '&language';

SQL> SELECT org_id, inventory_item_id, req_template_line_num, supplier, ip_category_name FROM icx_cat_items_ctx_hdrs_tlp WHERE req_template_name = '&reqTemplateName' AND org_id = &orgId AND language = '&language' ORDER BY req_template_line_num;

 

 - Personal Favorite Lists

Before Release12, a requester could only have one Personal Favorites List, along with the general Shopping Lists. However using the iProcurement Preferences page they can create and maintain multiple personal favorite lists. Items can be moved between lists as needed for better organization.

The following query returns lines on the lists available for a particular User, Operating Unit and Language combination, and can be used to check for data issues.

SQL> SELECT fav_hdrs.favorite_list_id, primary_flag, fav_hdrs.favorite_list_name, fav_lines.favorite_list_line_id, fav_lines.po_header_id, fav_lines.po_line_id, fav_lines.inventory_item_id, fav_lines.req_template_name, fav_lines.req_template_line_num, fav_lines.org_id, fav_lines.language FROM icx_cat_fav_list_headers fav_hdrs, icx_cat_fav_list_lines_tlp fav_lines, icx_cat_items_ctx_hdrs_tlp ctx_hdrs WHERE employee_id = &EmployeeId AND fav_lines.org_id = &orgId AND fav_lines.language = '&language' AND fav_hdrs.favorite_list_id =

fav_lines.favorite_list_id AND fav_lines.po_line_id = ctx_hdrs.po_line_id (+) AND fav_lines.inventory_item_id = ctx_hdrs.inventory_item_id (+) AND fav_lines.req_template_name = ctx_hdrs.req_template_name (+) AND fav_lines.req_template_line_num = ctx_hdrs.req_template_line_num (+) AND fav_lines.org_id = ctx_hdrs.org_id (+) AND fav_lines.language = ctx_hdrs.language (+) ORDER BY fav_hdrs.favorite_list_id, fav_lines.favorite_list_line_id;

 

ITEM BULKLOADER

From Release 12 onwards, the Bulk Loader does not copy the uploaded item/price file to the Middle Tier Server, and therefore does not use the remote listeners to copy the file on to the Concurrent Manager node. Now, the upload file will be stored directly in the database. As a result, the Profile Option: POR: Catalog Bulk Load Directory is obsolete and there is no need to set up the remote listeners (FNDFS) for the concurrent manager.

The bulkloader process is still handled as a concurrent request, however the logging has changed here.  Release 12 includes much more online error information and so the reliance on the log is reduced. Always check the error detail (hyperlinked) from the upload status page in iProcurement Catalog Administration.

This same information can also be returned using the following queries;set FND: Debug Log Enabled = Yes

SQL> SELECT job_number, job_type, job_status, user_file_name, role, po_header_id, document_type_code, document_number, org_id, interface_header_id, lines_processed, lines_failed, failure_message, system_failure_message, session_id FROM icx_cat_batch_jobs_all WHERE job_number = &jobNumber 

And also to get individual line failure reasons (also shown online) use the following;

SQL> SELECT descriptor_key, message_text, token_list FROM fnd_new_messages msg, icx_por_failed_line_messages fm WHERE fm.job_number = &jobNumber AND fm.MESSAGE_NAME = msg.message_name;

  (For Item Loads)

SQL> SELECT err.error_message, err.error_message_name, err.interface_line_id, err.table_name, err.column_name, err.column_value

FROM po_interface_errors err, icx_cat_batch_jobs_all jobs WHERE jobs.job_number = &jobNumber AND err.interface_header_id = jobs.interface_header_id;

 (For Schema Load)

SQL> SELECT line_number, descriptor_key, message_name, token_list FROM icx_por_failed_line_messages WHERE job_number = &jobNumber; SELECT line_number, descriptor_key, descriptor_value FROM icx_por_failed_lines WHERE job_number = &jobNumber;

If this doesnt clarify the reasons for the failure, or the error is a technical exception, the Concurrent Request Log will provide a Session ID that was used for the job. This should be used as input into the following query to get the debug log information;

SQL> SELECT module, message_text FROM fnd_log_messages WHERE audsid=&SessionID ORDER BY log_sequence desc

Dont forget to make sure the Concurrent Manager is running ok, and often restarting and resubmitting a request can resolve temporary issues.

 

UPGRADE ISSUES

The Release 12 upgrade process includes significant data manipulation, and as such its useful to know what is being done at each stage.  Whilst the upgrade process itself is outside the scope of this document, subsequent issues in the item catalog may benefit from knowing where the data originated from.  The following phases of work make up the catalog upgrade process:

Purchasing Phase 1: Update PO tables for the new data model. iProcurement Phase 1: Moves data from iProcurement data model into

Purchasing Open Interface tables Purchasing Phase 2: Move the data from Purchasing Open Interface

tables to Purchasing Transaction Tables. iProcurement Phase 2: Populate the iProcurement Intermedia Index

Table with valid blankets, quotations, requisition templates and master items.

Purchasing Final Phase (not part of pre-upgrade): Make the documents created during Purchasing Phase 2 approved. Create attachments when required. Archive the data created during Purchasing Phase 2.

iProcurement Final Phase (not part of pre-upgrade):  Upgrade the iProcurement Favorite Lists. Create the Intermedia Index.

 

DEBUG LOGGING

All of the iProcurement catalog processes will generate logs using the default debug logging method.

This is explained in Note 290614.1 - How To Get Log Files In iProcurement, where from 11.5.10/FP.J onwards it uses the standard FND debug logging. Its recommended to set to log to a file (as opposed to the screen), so to capture full information.  The following example User Profile Options can be used to enable logging:

FND: Debug Log Enabled = Yes FND: Debug Log Level = Statement FND: Debug Log Module = % FND: Debug Log Filename for Middle-Tier = 

Some example entries to look out for, in item search issues are:

RequisitionAMImpl]:searchIntermediaString = (${pen}) & (((sqe(icxzb1)) & ((204 within orgid) & ({US} within language)))*10*10) RequisitionAMImpl]:includedSourceTypes = [QUOTATION, MASTER_ITEM, TEMPLATE, GLOBAL_BLANKET, INTERNAL_TEMPLATE, BLANKET]...SearchVOBuilder]:Bind values map: {languageKey=US, allowedItemTypeKey=BOTH, intermediaKey=(${pen}) & (((sqe(icxzb1)) & ((204 within orgid) & ({US} within language)))*10*10), orgIdKey=204, rateTypeKey=Corporate, functionalCurrencyKey=USD, employeeIdKey=27695, invOrgIdKey=204, goodsLineTypeKey=1} ...

Here note the value of intermediaKey. This intermedia key contains org_id value and sqe value apart from keyword being searched.** See section on item and category data setup > line items for the sql to be used to validate the org_id for the inventory item.

RequisitionAMImpl]:doQuery:: final search query is :...RequisitionAMImpl]:executeQuery start RequisitionAMImpl]:executeQuery end

Also check the log for keywords related to the specific problem, such as : category, price etc.

Obviously for bulkloader issues, the concurrent log mentioned above should be used.  Also Profile Option POR: Set Debug Catalog Loader ON should be set to Yes for additional log messages.

TRACING

Tracing is useful when you need to check what queries are running in the database when performing certain activities, or especially for investigating performance related issues.  The steps to enable SQL Tracing is also explained in Note 290614.1 - How To Get Log Files In iProcurement, and from 11.5.10/FP.J this is best enabled using the options under the Diagnostics link.

Remember to use tkprof with the raw traces files to provide additional information, and a more readable format for analysis.

Since the bulkloader is a concurrent process, setting tracing for this requires a separate action.  Rather than enabling tracing for all bulkload attempts (by setting it against the concurrent program), if you set profile option "Initialization SQL Statement - Custom". at USER level (as detailed in Note 290614.1), it will just generate trace files for that users bulkload jobs.

 

RELATED CODE FILES

The following list of code files can be useful in matching against error messages and for searching for later versions included in patch fixes;

SEARCH ITEM DISPLAY

BULKLOADER

ShoppingAMImpl.class ICXVPPIB.pls

UploadAgreementCO.class

ShoppingVOBuilder.class ICXVPPDB.pls

UploadSchemaCO.class

ShoppingClientHelper.class

ICXVPPRB.pls

ViewUploadErrorsCO.class

SearchResultsCO.class ICXVPPMB.pls

ViewUploadHistoryCO.class

PublicListVOBuilder.class ICXVPPCB.pls

LoaderAMImpl.class

FavoriteListVOBuilder.cla ICXVPPS CatalogLoaderJob.cl

ss B.pls ass

BaseSearchVOBuilder.class

ICXVUTLB.pls

ItemElementProcessor.class

SearchResultsRegionHandler.class

. DataRootElementProcessor.class

ResultsInParagraphRegionHandler.class

. CatalogLoaderSql.class

ResultsInGridRegionHandler.class

. JDBCDataLoader.class

poprg.ldt . .

porgup.ldt    

icxprg.ldt    

ICXVPPIB.pls    

ICXVPPIS.pls    

The following steps explain how this can be useful in investigating possible similar issues;

Check any errors or logs related to the issue, and note the code objects and files mentioned.

Check the version of these files in the instance exhibiting the problem. Search the patches available for later releases of these files, and

match the patch descriptions to the issue encountered. Apply as relevant.

To find patches: Visit Metalink > Patches and Updates > Advanced Search > Complete: Product / Release / Platform / Patch / Includes File [Enter file] > Click Go.

 

PATCHES

From Release 12 onwards, standard patches will be released as part of Release Update Packs (RUP) only. As such, check the following note for details on the latest RUP patch, and any catalog fixes it includes.

Note 423541.1 - Oracle E-Business Suite R12 Release Update Pack (RUP) Schedule Note Note 222339.1 - Procurement Family Patch Release History 

HOW TO'S / TOOLS

Note 880285.1 - Items Are Not Visible in iProcurement in Release 12Note 454694.1 - Items With Mapped Category After Item Creation Do Not Show Up In iProcurementNote 466203.1 - How To Load Items In The Catalog From Xml Or Xls FilesNote 558273.1 - How To Diagnose Issues in Bulkloading Items in iProcurementNote 602896.1 - How Has The iProcurement Catalog Data Model ChangedNote 728118.1 - How Can You Enable Categories In iProcurementNote 729400.1 - How To Refresh The iProcurement Search (Intermedia) IndexNote 751324.1 - What Are The Steps For Enabling Items In The Procurement Catalog?Note 862144.1 - How To Disable Or Remove Items From iProcurement CatalogNote 883428.1 - How To Upload Images For Inventory Items

WHITEPAPER

Note 560749.1 - White Paper: Enhanced Catalog Content Management, Online Authoring And Content Security Model

 

DOCUMENTATION

The following documentation, in addition to troubleshooting notes like this one, should be checked for any question or problem related to product functionality and setup;

Oracle iProcurement Implementation and Administration Guide Release 12 (Part No. B31402-01)

It may also be helpful to compare to previous release document Oracle iProcurement Implementation Guide Release 11i (Part No. A85361-05)

References

NOTE:222339.1 - Procurement Family Patch Release HistoryNOTE:290614.1 - How To Get Log Files In iProcurementNOTE:382592.1 - How To Diagnose A Problem In The Item CatalogNOTE:423541.1 - Oracle E-Business Suite Release 12 Release Update Pack (RUP)NOTE:454694.1 - Rel 12 and 12.1 - Items With Mapped Category After Item Creation Do Not Show Up In iProcurementNOTE:466203.1 - How To Load Items In The Catalog From Xml Or Xls Files In Release 12?NOTE:558273.1 - How To Diagnose Issues in Bulkloading Items in

iProcurementNOTE:560749.1 - White Paper: Enhanced Catalog Content Management, Online Authoring And Content Security Model in Release 12NOTE:602896.1 - How Has The iProcurement Catalog Data Model Changed In Release 12NOTE:728118.1 - How Can You Enable Categories In iProcurement On Release 12?NOTE:729400.1 - How To Refresh The iProcurement Search (Intermedia) Index In Release 12NOTE:751324.1 - What Are The Steps For Enabling Items In The Procurement Catalog?NOTE:862144.1 - How To Disable Or Remove Items From iProcurement Catalog In Release 12?NOTE:880285.1 - Rel 12 and 12.1 - Items Are Not Visible in iProcurementNOTE:883428.1 - How To Upload Images For Inventory Items In Release 12

 

Attachments

 

12iP_dataModel.jpg (23.19 KB)

 

Related

 

 

Products

 

Oracle E-Business Suite > Procurement > Procurement > Oracle iProcurement > E-Content Manager > Manage Item/PriceList INTFC CatalogAdmin

 

Keywords

 

BULKLOAD; BULKLOADER; CATALOGS; CATEGORY; FAVORITES; FAVORITES LIST; INTERMEDIA; ITEM; ITEM

CATALOGS; MTL_CATEGORIES_B; PO_LINES_ALL; SHOPPING LISTS

Back to Top

Copyright (c) 2012, Oracle. All rights reserved.

 Legal Notices and Terms of Use  

Privacy Statement  

Third Party Licenses  

京 ICP 备 10049020 号

      OK

   

dummyBottom

f1 !jxxomdlcy

   

OKCancel