1/24/22, 1:07 AM Document 1488509.

1
Copyright (c) 2022, Oracle. All rights reserved. Oracle Confidential.

Fusion PIM: What are the Requirements for a Catalog to be Assigned to a Functional Area in Manage Functional Area Catalogs UI? (Doc ID
1488509.1)

In this Document

Purpose
Details
   Introduction
  Catalog Validations Performed Based on Attribute Control
  Inventory
  Purchasing
  Planning
  Service
  Cost
  Order Entry
  Product Line Accounting
  Asset Management
  Contracts
  Product Reporting
  GDSN Syndication for UDEX
  Process Product Line
  Distributed Order Orchestration
  Supplier Product and Services
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

Oracle Fusion Product and Catalog Management - Version 11.1.9.2.0 to 11.1.9.2.0 [Release 1.0]
Oracle Fusion Product Hub Cloud Service - Version 11.13.21.07.0 to 11.13.21.07.0 [Release 1.0]

Information in this document applies to any platform.

PURPOSE

This document explains what is Functional Area and the validation for each specific area that is used for catalogs in Manage Default Catalogs UI. Default Catalogs are used to
automatically assign categories to items during item creation and may be a required step for item creation, depending on the operational attributes enabled.

DETAILS

 Introduction

The item has specific operational attributes that are defined to configure the item for use in other Oracle applications such as Purchasing (Purchasable, Purchased) or Inventory
(Inventory Item, Stocked). During Item Create, templates can be used to create items; the values of these attributes can be defined within the templates and will trigger the
automatic category assignment process.   This process will look for specific catalogs that are assigned to the functional area and use the default category assigned to these catalogs
as the category the item is assigned to. 

A Functional area is an application or business process that implements catalogs requiring specific behavior for those catalogs. The behavior of the catalog in each functional area is
defined by a set of rules.

For example, if the item template indicates the item is Purchasable=Yes, then the item will automatically be assigned to the default category assigned to the catalog that is
assigned to the functional area called Purchasing.

Catalog Validations Performed Based on Attribute Control

During initial setup, one or more catalogs must be created to allow the automatic category assignment process to complete. The number of catalog is specific to what applications
are deployed with the Oracle Product Information Management application. 

The functional area that requires catalogs due to operational attribute values and the corresponding attributes are:

 Functional Area Attribute Group Name Attribute Name Attribute I

Inventory Inventory Inventory Item INVENTORY_ITEM_FLA

Purchasing Purchasing Purchased PURCHASING_ITEM_FL

Planning MPS and MRP Planning Planning Method MRP_PLANNING_CODE

Costing Costing Costing Enabled COSTING_ENABLED_FL

Order Entry Order Management Customer Ordered CUSTOMER_ORDER_FL

Product Line Accounting Main Item Description DESCRIPTION

Asset Management Asset Management Asset Item Type EAM_ITEM_TYPE

Service Contracts Service Contract Item Type CONTRACT_ITEM_TYP

 

 
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=8ww2if01v_163&id=1488509.1 1/5
1/24/22, 1:07 AM Document 1488509.1

 While assigning catalogs to a functional area in Manage Default Catalogs UI,

If the operational attribute control value is 'Organization Level' for an attribute, only those catalogs whose control level is 'Organization Level' show up in Catalogs List Of
Values (LOV).
If the operational attribute control value is 'Master Level' for an attribute, then only those catalogs whose control level is 'Master Level' shows up in Catalogs LOV.

For a sample of how to set the 'Operation Attribute Control Level' for each Functional area refer to "Purchasing" section in this note

To remove the Functional Area (example - Inventory, Purchasing, Costing etc) from the Catalog perform the following steps-

Get the list of all items associated with the Functional Area Catalog using the SQL available under section Category and Catalog Information in Doc ID 2751576.1
Navigate to Product Management > Production Information Management > Search for Item using the task - Manage Items from the right panel
Click on Specifications tab > Click on required Functional Area (as listed in the above table) available under Item Organization
Change the Item attribute (as listed in the above table) value from Yes to No
Make sure all the open transactions of the Items are closed.

FBDI, Import Map or Rest API /Webservice can be used to change these attributes values by taking care of dependent attributes if a large number of items need to update 

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.

Enable hierarchy of categories = unselected.

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
“Master Controlled” or “Organization controlled” catalogs can be assigned.

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

a. Catalog should not have hierarchy enabled.

Enable hierarchy of categories = Unselected.

b. Catalog should have a default category assigned.

c. Catalog should have Allow multiple item category assignments = “No”
d. 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.

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.

Example to set attributes we need to navigate to -> Setup and Maintenance ->Manage Operational Attribute Groups as shown below: 

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=8ww2if01v_163&id=1488509.1 2/5
1/24/22, 1:07 AM Document 1488509.1

Example for purchasing functional area:

From above screen shot you can see that for purchasing, purchasing attribute -> Purchased is at master control.

Same time the catalog which you want to assign to this functional are should also be master control as shown below:

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=8ww2if01v_163&id=1488509.1 3/5
1/24/22, 1:07 AM Document 1488509.1

If this attribute is organization control then catalog should also be organization control.

Similarly we need to validate for other functional areas as well

Planning

a. Catalog should not have hierarchy enabled.

Enable hierarchy of categories = Unselcted.

b. Catalog should have a default category assigned.

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.

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

a. Catalog should not have hierarchy enabled.

Enable hierarchy of categories = Unselected

b. Catalog should have a default category assigned.

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.

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

a. Catalog should not have hierarchy enabled.

Enable hierarchy of categories = Unselected.

b. Catalog should have a default category assigned.
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 either
“Master Controlled” or “Organization controlled” catalogs can be assigned.

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

a. Catalog should not have hierarchy enabled.

Enable hierarchy of categories = Unselected.

b. Catalog should have a default category assigned.

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.

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

a. Catalog should not have hierarchy enabled.

Enable hierarchy of categories = Unselected.

b. Catalog should have a default category assigned.
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=8ww2if01v_163&id=1488509.1 4/5
1/24/22, 1:07 AM Document 1488509.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 either
“Master Controlled” or “Organization controlled” catalogs can be assigned.
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

a. Catalog should not have hierarchy enabled.

Enable hierarchy of categories = Unselected.

b. Catalog should have a default category assigned.

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.

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

a. Catalog should not have hierarchy enabled.

Enable hierarchy of categories = Unselected.

b. Catalog should have a default category assigned.

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.

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

a. Catalog should not have hierarchy enabled.

Enable hierarchy of categories = Unselected.

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.

Enable hierarchy of categories = Unselected.

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”.

Process Product Line

a. Catalog should not have hierarchy enabled.

Enable hierarchy of categories = Unselected.

b. Catalog should have a default category assigned.

Distributed Order Orchestration

a. Catalog should not have hierarchy enabled.

Enable hierarchy of categories = Unselected.

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”.

Supplier Product and Services

a. Catalog should not have hierarchy enabled.

Enable hierarchy of categories = Unselcted.

b. Catalog should have a default category assigned.

Didn't find what you are looking for?

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=8ww2if01v_163&id=1488509.1 5/5