Fusion Define Catalogs - Catalog Setup

14.4.2014 Document 1391190.
Fusion PIM: Common Problems and Solutions - Define Catalogs / Catalog Setup (Doc ID 1391190.1)
Modified: 10-Sep-2013 Type: FAQ
In this Document
Purpose
Questions and Answers
Summary:
Dependent Technologies:
Mandatory Log Channels:
Common Problems:
Unable to create a catalog, the catalog structure list of values is blank in the Create Catalog dialog.
Validation:
Unable to create a category and the category structure segments values are not listed in the Create Category dialog
Solution:
Validation:
Unable to assign catalog to a functional area in the Manage Default Catalog page.
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=dt9f00ukp_144&id=1391190.1 1/26
14.4.2014 Document 1391190.1
Solution:
Catalog Behavior Rules Based on a Functional Area
Validation:
Unable to re-assign a catalog to a functional area in the Manage Default Catalog page.
Solution:
Unable to find my catalog in the Manage Catalog page.
Solution:
Validation:
Unable to find my category in the category hierarchy table or the Add Category search and select dialogs.
Solution:
Validation:
Unable to download data from the catalog into a spreadsheet, the spreadsheet is launched but is blank.
Solution:
Validation:
Unable to deploy flexfield definitions, sandbox active.
Unable to see ADFDi buttons [Upload/Download/Add] from Edit in Spreadsheet option under Category Hierarchy tab.
References
APPLIES TO:
Oracle Fusion Product Model - Version 11.1.1.5.1 and later

Oracle Fusion Sales Catalog - Version 11.1.1.5.1 and later
Oracle Fusion Sales Catalog Cloud Service - Version 11.1.5.0.0 and later
Information in this document applies to any platform.
PURPOSE
This document covers common problems in the functionality of Fusion Product Catalog Application.
QUESTIONS AND ANSWERS
Summary:
14.4.2014 Document 1391190.1
Item catalogs are an item classification structure within the Oracle Fusion Product Information Management application, but are used by many other Oracle applications.
Item Catalogs area used for classification of items and for analysis of sets of items represented by categories.
Dependent Technologies:
None
Mandatory Log Channels:
AppsLogger modules:
oracle.apps.scm.productManagement.productCatalogManagement.itemSecurity.protectedUiModel.applicationModule.ItemSecurityAMImpl
Common Problems:
Unable to create a catalog, the catalog structure list of values is blank in the Create Catalog dialog.
A catalog cannot be created since a value cannot be selected or found by searching for a catalog structure in the list of values. The Catalog Structure value is flagged as
an error when the Save or Save and Close button are clicked.
Solution:
The catalogs are key flexfields enabled and require that the Key Flexfields be created prior to creating catalogs.
1. Check to make sure that key flexfields Structure and Structure Instance have been defined for the catalog key flexcode MCAT. You can access the key flexfields for
catalogs by using the Manage Key Flexfields for Catalogs task in the Oracle Fusion Functional Setup Manager application.
2. Prior to defining the key flexfield Structure and Structure Instance, a value set must be defined, please refer to the implementation guides for information on creating
value sets.
3. Define a key flexfield Structure and Structure Instance for the catalog key flexfields MCAT using the following steps:
Key Flexfield Setup
Prerequisite: Value sets must be defined prior to creating a key flexfield.
FSM Task: Manage Key Flexfield for Catalogs, search for the task in the FSM Overview page, within the All Task tab.
Steps:
14.4.2014 Document 1391190.1
a) Launch the page, the page opens with flexfield code MCAT that is seeded for catalog and categories.
b) The Key Flexfield Code MCAT is seeded; create the Key Flexfield structure for the new Key Flexfield for catalog.
c) Click the Manage Structures button, the Manage Key Flexfield Structure page will be displayed.
d) Click on the Create Icon
14.4.2014 Document 1391190.1
e) Enter the information:
Structure Code
Name
Select the delimiter used if more than one segment is defined
f) Click on Save button
g) Click the Create Icon in the Segment tables to create one or more segments.
14.4.2014 Document 1391190.1
h) Enter Information:
Segment Code
Segment Name
Sequence Number
Prompt (displayed in page)
Short Prompt
Display Width
Select Column name (where value is mapped to be storage)
Default Value Code previously created
i) Click Save and close ( Create Key Flexfield Segment Page)
j) Click Save and Close (Create Key Flexfield Structure Page)
k) Click Done button (Manage Key Flexfield Structures Page)
l) Now that the Key Flexfield structure is created, the structure instance for the KFF is created; Select the row for the KFF structure you just created and click the Manage
Structure Instances button
14.4.2014 Document 1391190.1
m) Click the Create Icon to launch the create structure instance
14.4.2014 Document 1391190.1
n) Enter information:
Structure Instance Code
Name
Select the Structure Name
o) Click Save button. The segment information from the creation of the key flexfield structure should be displayed in the Segment instances table
p) Click Save and Close to close the Create Structure Instances page, control returns to the Manage Key Flexfields for Catalogs page.
q) Click Deploy Flexfield button to deploy the key flexfield structures and structures for the key flexcode MCAT. Do not use the drop list for this button.
r) Once the Deployment process is completed, the deployment status will show as a green check mark indicating the new key flexfield has been created.
Validation:
After following the above steps to create a key flexfield structure and structure instance for catalogs, invoke the Create Catalogs task or invoke the Manage Catalogs task
(use the Create Icon) in the Oracle Functional Setup Manager, fill in the catalog information, select the key flexfields you created in the Catalog Structure LOV choice list,
and verify that the catalog is saved.
Unable to create a category and the category structure segments values are not listed in the Create Category dialog
During category creation, the Create Category dialog displays the fields for the category, but the key flexfield segments that are defined for the key flexfield structure
instance are not displayed below the Category Structure field. An error maybe displayed indicating the Category Structure is not entered when you click the OK button.
The category will sometimes be created as well, but an Application Error dialog will be launched when the catalog is saved.
14.4.2014 Document 1391190.1
Solution:
The key flexfield definition for the category structure is not complete or the key flexfields are not deployed.
Review the key flexfield that has been created for the catalog. The key flexfield structure should contain a key flexfield structure, segments for the structure and a key
structure instance.
Deploy the key flexfields for the catalog flex field code MCAT
2. Launch the Manage Key Flexfield for Catalogs task in the Oracle Function Setup Manager application, Overview Page within the All Task tab.
3. Click the Deploy Flexfield button, status should indicate the key flexfields are deployed successfully.
4. Close the Browser ( all tabs )
Validation:
After completion of the Deploy Flexfield operation, close the browser, reopen new browser window, invoke the Oracle Product Information Management application and
launch the Manage Catalog UI page. Search for the catalog that you created the category in. Create new category, the Category Structure segment prompts should be
displayed as fields below the Category Structure field.
14.4.2014 Document 1391190.1
Unable to assign catalog to a functional area in the Manage Default Catalog page.
A catalog that is created for a functional area does not appear in the choice list when editing the default catalog for a functional area or when searching in the choice list.
Solution:
A Functional area is an application or business process that implements catalogs requiring specific behavior for their catalogs, the behavior is defined by a set of rules.
The validation of the rules for each specific functional area is used to filter the values presented in the Catalog Name choice list. The Functional Area Rules include the
following:
1. The value of the Controlled At attribute for a catalog (see Figure 2) is determined based on Controlled at value of the Operational Attributes (see Figure 1) for the
Functional Area.
14.4.2014 Document 1391190.1
While assigning catalogs to a functional area in Default Catalogs UI, if the operational attribute control value is 'Org Level' for an attribute, only those catalogs whose
control level is 'Organization Level' shows up in Catalogs LOV.
If the value of the Controlled At operational attribute is 'Master Level', then only those catalogs whose Controlled At value is 'Master Level' and 'Organization Level' shows
up. The following chart shows the operational attribute groups that are used in the Functional Area Rules.
Check the value for the Controlled At attribute for the operational attributes using the Manage Operational Attribute Groups task in the Oracle Functional Setup Manager
application to determine what the value for the Catalogs Controlled At attribute value.
14.4.2014 Document 1391190.1
14.4.2014 Document 1391190.1
Catalog Behavior Rules Based on a Functional Area
All Functional Areas:
The catalog must have a default category assigned to the catalog for the Functional area. Check the catalog to see if a category has been assigned to the Default
Category attribute value.
The value of one or more catalog attributes has to have a specific value, for example the functional area may not allow the catalog to have a category hierarchy and the
value of the Enable hierarchies for categories attribute must be No. Check the rule below for each of the functional area and make sure the catalog conforms to the
rules.
Inventory:
a. Catalog should not have hierarchy enabled.
Allow hierarchy of categories = No.
b. Catalog should have a default category assigned.
c. For Inventory attribute group: Inventory Item attribute, if the operational attribute Controlled At value is Master Level then catalogs with Controlled At value of either
14.4.2014 Document 1391190.1
Master Controlled or Organization controlled catalogs can be assigned.
d. For Inventory attribute group: Inventory Item attribute, if the value of Controlled At operational attribute is Organization Level then only catalogs with the value of
Controlled At = Organization Controlled can be assigned.
Purchasing:
c. For Purchasing attribute group: Purchased attribute OR Order Management attribute group: Internal Ordered attribute, if the Controlled At value operational attribute
control value is Master Level then catalogs with Controlled At value of either Master Controlled or Organization controlled catalogs can be assigned.
d. For Purchasing attribute group: Purchased attribute OR Order Management attribute group: Internal Ordered attribute, if the value of Controlled At operational
attribute is Organization Level then only catalogs that have the value Controlled At = Organization Controlled can be assigned.
e. Catalog should have Allow multiple item category assignments = No
Planning:
c. For MPS and MRP Planning attribute group: Planning Method attribute, if the value of Controlled At operational attribute is Master Level then catalogs with Controlled
At value of either Master Controlled or Organization Controlled catalogs can be assigned.
d. For MPS and MRP Planning attribute group: Planning Method attribute, if the value of Controlled At operational attribute is Organization Level then only catalogs that
have the Controlled At = Organization controlled can be assigned.
Service:

14.4.2014 Document 1391190.1
c. For Service attribute group: Contract Item Type attribute, if the value of Controlled At operational attribute is Master Level then catalogs with Controlled At value of
either Master Controlled or Organization controlled catalogs can be assigned.
d. For Service attribute group: Contract Item Type attribute, if the value of Controlled at operational attribute is Organization Level then only catalogs where the
Controlled = Organization controlled can be assigned.
Cost:
c. For Costing attribute group: Costing Enabled attribute, if the value of Controlled at operational attribute is Master Level then catalogs with Controlled At value of
d. For Costing attribute group: Costing Enabled attribute, if the value of Controlled at attribute is Organization Level then only catalogs with the value of Controlled at =
Organization controlled can be assigned.
Order Entry:
c. For Order Management attribute group: Customer Ordered attribute, if the value of Controlled At operational attribute is Master Level then catalogs with Controlled
At value of either Master Controlled or Organization controlled catalogs can be assigned.
d. For Order Management attribute group: Customer Ordered attribute, if the value of Controlled At operational attribute is Organization Level then only catalogs with
the value of Controlled at = Organization controlled can be assigned
Product Line Accounting:

14.4.2014 Document 1391190.1
c. For Main attribute group: Item Description attribute, if the value of the Controlled At operational attribute is Master Level then catalogs with Controlled At value of
d. For Main attribute group: Item Description attribute, if the value of the Controlled At operational attribute is Organization Level then only catalogs with Controlled
At=Organization controlled can be assigned.
Asset Management:
c. For Asset Management attribute group: Asset Item Type attribute, if the value of the Controlled At operational attribute is Master Level then catalogs with Controlled
At value of either Master Controlled or Organization controlled catalogs can be assigned.
d. For Asset Management attribute group: Asset Item Type attribute, if the value of the Controlled At operational attribute is Organization Level then only catalogs with
Controlled at=Organization controlled can be assigned.
Contracts:
c. For Service attribute group: Contract Item Type attribute, if the value of the Controlled At operational attribute is Master Level then catalogs with Controlled At value
of either Master Controlled or Organization controlled catalogs can be assigned.
d. For Service attribute group: Contract Item Type attribute, if the value of the Controlled At operational attribute is Organization Level then only catalogs with a value
of Controlled at = Organization controlled can be assigned.
Product Reporting:

14.4.2014 Document 1391190.1
c. Catalog should have Enable auto assign of categories = No
d. Catalog should have Allow multiple item category assignments = No
e. Catalog should have the value of Controlled At = Master Controlled.
GDSN Syndication for UDEX:
d. Catalog have the value of Controlled At = Master Controlled.
Process Product Line:
Distributed Order Orchestration:
d. Catalog should have Allow multiple item category assignments = No.
Supplier Product and Services:

14.4.2014 Document 1391190.1
Validation:
Review the attribute values for the catalog you area assigning to a functional area and check to see that they match the rules listed above.
Unable to re-assign a catalog to a functional area in the Manage Default Catalog page.
In the Manage Default Catalogs UI page, a new catalog is selected from the Catalog Name choice list and the Save and Close button is clicked, an error dialog stating:
The functional area catalog cannot be updated. (EGP-2775752) is launched preventing from the new catalog to be assigned to the functional area.
Solution:
Once item has been assigned to any categories in the catalog assigned to a functional area, a new catalog cannot be assigned to the functional area. Check the catalog
that is being assigned to the functional area to see if item have been assigned to the catalog.
Continue to use the catalog that is assigned to the functional area. Use the date enablement features to end date categories and category associations that are no longer
14.4.2014 Document 1391190.1
in use.
Unable to find my catalog in the Manage Catalog page.
I search for a catalog is that is created, but do not find the catalog using the search or when I search for a group of catalog using a wildcard, the catalog does not appear
in the Search Results table in the Manage Catalogs UI page.
Solution:
Catalogs are date enabled; the display, use and specific operations for catalogs are controlled by the values of the Catalog Start Date and Catalog End Date. The Search
Results table in the Manage Catalogs UI page has date filter to control which catalogs are displayed. Check the Catalog filter in the table header, the default value is
display only the Active catalogs. Active catalogs have Catalog Start Date value that is later or equal to the current date and have a Catalog End Date value later or equal
to the current date ( or the End Date can be blank ). If the catalog you are looking for does not appear in the Search Result table, change the Catalog filter to a value of
All, which will display active, inactive and future dated catalogs.
Validation:
Set the Catalog filter value to All and search for the catalog. The filter allows the display of Active, Inactive and Future Dated catalogs.
Unable to find my category in the category hierarchy table or the Add Category search and select dialogs.
In the Category Hierarchy tab of the Edit Catalog UI page, specific categories are not displayed in the category hierarchy tree table or the categories cannot be found
using the category search.
Solution:
14.4.2014 Document 1391190.1
Categories and Category Associations are date enabled, the display, use and specific operations for categories are controlled by the values of the Category Start Date
and Category End Date or Category Association Start Date and Category Association End Date. ).
The tree table in the Edit Catalog UI page has two date filters to control which categories are displayed. Check the Categories and the Associations filters in the table
header, the default value is display only the active categories and active category associations. Active categories have Category Start Date value that is later or equal to
the current date and have a Category End Date value later or equal to the current date (or the End Date can be blank).
The display of the category in the tree table is depended on values for both filters. If you do not see the category in the category hierarchy table or cannot find it by
searching the category hierarchy, then set the value of the Category and Association filters to All, this will display active, inactive and future dated categories and
associations.
Validation:
14.4.2014 Document 1391190.1
Set the Categories filter value to All and Associations filter value to All. Then view or search for the category in the category hierarchy.
Unable to download data from the catalog into a spreadsheet, the spreadsheet is launched but is blank.
The spreadsheet that is launched from the Edit Catalog page is blank. The system launches a dialog Opening CategoryImport.xlsx, you select to open with Microsoft
Office Excel, the spreadsheet opens, but the spreadsheet is blank.
Solution:
Check the following:
1. Check to see that you are using Microsoft Office Excel 2007, this release is required to support the export/import process.
2. Check to see the Oracle ADF 11g Desktop Integration Runtime Add-in for Excel client is installed on your local machine. The validate the client is installed:
Open the Windows Control Panel
Click on Add or Remove Program
14.4.2014 Document 1391190.1
Search for Oracle ADF 11g Desktop Integration Runtime Add-in for Excel
If the client is not installed, download the client using the following steps:
In the Items Work Area: Click on the drop list for the Navigator in upper left hand corner of the work area.
Select Tools->Download Desktop Integration Installer
Follow directions for installing client.
3. Check to see if browser security is blocking access between the browser and application using the following steps:
Open Microsoft Office Excel 2007
Click on the Microsoft office button and then click on Excel Options (See image below)
Click the Trust Center tab and then click Trust Center Settings
14.4.2014 Document 1391190.1
Click the Trusted Locations tab.
Verify that the path to Oracle Product Information Management application is listed in the trusted locations table, see below.
14.4.2014 Document 1391190.1
If the path to the application server is not listed, add the path
Select the Allow Trusted Locations on my network (not recommended) checkbox
Click the Add New Location button (refer figure below)
Enter the hostname of the server that your Integrated Excel workbook will be accessing. The path should end with the /productManagement/.
Select the checkbox Subfolders of this location are also trusted
14.4.2014 Document 1391190.1
Click Ok.
Microsoft Office Excel is now configured to allow the integrated excel workbooks to access your remote hosts. Additional information is available in the ADF Desktop
Integration User Guide.
Validation:
Launch the export of the catalog information by clicking the Export Hierarchy button, download the information to Microsoft Office Excel, login to the using the same
userID and password used to access the application, the information from the catalog will be displayed within the spreadsheet.
Unable to deploy flexfield definitions, sandbox active.
14.4.2014 Document 1391190.1
Please refer to document 1357018.1 Deployed Flexfield segment is not visible in the Setup UI for Manage Catalogs.
Unable to see ADFDi buttons [Upload/Download/Add] from Edit in Spreadsheet option under Category Hierarchy tab.
The button in the ADFDi are not showing up because the excel macros are disabled.
Please enable the macros and re-launch the excel,
Steps to enable macros in Excel 2007
1. Click on 'Office Button' and select Excel Options

2. In Excel Options popup select Trust Center and click on Trust Center Settings
3. In Trust Center window select Macro Settings and select 'Enable all macros'
4. Close the excel and re-launch it.

Fusion Define Catalogs - Catalog Setup

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Fusion Define Catalogs - Catalog Setup

Hochgeladen von

Copyright:

Verfügbare Formate

14.4.2014 Document 1391190.

Oracle Fusion Product Model - Version 11.1.1.5.1 and later

QUESTIONS AND ANSWERS

Mandatory Log Channels:

Key Flexfield Setup

Prerequisite: Value sets must be defined prior to creating a key flexfield.

d) Click on the Create Icon

e) Enter the information:

Select the delimiter used if more than one segment is defined

f) Click on Save button

Prompt (displayed in page)

Select Column name (where value is mapped to be storage)

Default Value Code previously created

i) Click Save and close ( Create Key Flexfield Segment Page)

j) Click Save and Close (Create Key Flexfield Structure Page)

k) Click Done button (Manage Key Flexfield Structures Page)

m) Click the Create Icon to launch the create structure instance

Structure Instance Code

Select the Structure Name

4. Close the Browser ( all tabs )

Catalog Behavior Rules Based on a Functional Area

All Functional Areas:

a. Catalog should not have hierarchy enabled.

Allow hierarchy of categories = No.

b. Catalog should have a default category assigned.

Master Controlled or Organization controlled catalogs can be assigned.

a. Catalog should not have hierarchy enabled.

Allow hierarchy of categories = No.

b. Catalog should have a default category assigned.

e. Catalog should have Allow multiple item category assignments = No

a. Catalog should not have hierarchy enabled.

Allow hierarchy of categories = No.

b. Catalog should have a default category assigned.

a. Catalog should not have hierarchy enabled.

Allow hierarchy of categories = No.

b. Catalog should have a default category assigned.

a. Catalog should not have hierarchy enabled.

Allow hierarchy of categories = No.

b. Catalog should have a default category assigned.

a. Catalog should not have hierarchy enabled.

Allow hierarchy of categories = No.

b. Catalog should have a default category assigned.

Product Line Accounting:

a. Catalog should not have hierarchy enabled.

Allow hierarchy of categories = No.

b. Catalog should have a default category assigned.

a. Catalog should not have hierarchy enabled.

Allow hierarchy of categories = No.

b. Catalog should have a default category assigned.

a. Catalog should not have hierarchy enabled.

Allow hierarchy of categories = No.

b. Catalog should have a default category assigned.

a. Catalog should not have hierarchy enabled.

Allow hierarchy of categories = No.

b. Catalog should have a default category assigned.

c. Catalog should have Enable auto assign of categories = No

d. Catalog should have Allow multiple item category assignments = No

e. Catalog should have the value of Controlled At = Master Controlled.

GDSN Syndication for UDEX:

a. Catalog should not have hierarchy enabled.

Allow hierarchy of categories = No.

b. Catalog should have a default category assigned.

c. Catalog should have Enable auto assign of categories = No

d. Catalog have the value of Controlled At = Master Controlled.