Creating Catalog in Fusion

In this article we will focus on Basic catalog creation in oracle fusion application and also look into the changes oracle introduce in latest release R12.

Define Basic catalog

Overview

A catalog is a collection of item categories, which are to be defined in instance, that is used to classify items. Organization can organize the categories into a hierarchy the represents a taxonomy. Fusion will allows to create new item categories only in the context of a catalog. Organization can add existing categories or create new categories to one or more catalogs.

You can set the Catalog Content value to Items at all levels which allows items to be assigned to any level within the category hierarchy, not only to the leaf levels.

Catalogs are created at instance level and assigned to business functional area.

Catalog Components: How the catalog works

Catalog

A catalog, as discussed above, is a collection of categories that are organized to define a classification of items. The top most level of a catalog is the catalog root. All categories for the first level in the category hierarchy are associated with the catalog root through the catalog category association component.

Category

A category is used to classify or segregate items in a different areas/categories used by an organization to classify items. In other words, category is a component of a catalog that represents item classification defined by the categories in the catalog. Organization can associate a as many as categories to a catalog.

Functional Area

Functional area represents the business functions that is enabled and require item complete the business processing cycle. Like, Purchasing, Inventory, Order Management, etc. Organization required to assign catalog to all the functional areas that needs item for transaction processing. Catalog might be unique for each functional area or organization will use common catalog for all the functional areas depending on the business needs.

Item

An item represents the products or services offered by an organization. To purchase or sell an Item, it must be assigned to the catalog assigned to respective functional area. Further, item must be assigned to catalog category to represents item classification.

Create Catalog

To Create Basic catalogs, one must navigate to FSM and search for the Task “Define Basic Catalogs”. Expand the task to view below Task List.

1

Tasks present in the Task list are:

  •          Manage Product and Child Value Sets
  •          Manage Key Flexfield for Catalog
  •          Manage Catalog descriptive Flexfield
  •          Manage Category Descriptive Flexfields
  •          Create Catalog
  •          Manage Default Catalogs
We are not creating any descriptive Flexfield in our case, as DFF is specific to business scenario and required to capture additional information.

Product Value Sets

As categories are created as Key Flexfields in fusion, organization need to define value sets. While defining value sets, you need to provide Module Name. User need to provide “Item catalog”. This module represents the Items/Products related activity.

Navigate To: Implementation Project > Procurement > Define Common Procurement Configuration > Define Basic Catalogs > Manage Product and Child Value Sets

2

Key Flexfield for Catalog

After defining the value sets, organization needs to define flex field structures to create catalog. Product Model is the relevant application and Item Catalogs is the relevant module. User needs to click on Manage Structures and create a new structure.

Navigate To: Implementation Project > Procurement > Define Common Procurement Configuration > Define Basic Catalogs > Manage Key Flexfield for Catalog

Defining a key Flexfield structure in Fusion is a three step Procedure.

  1. Define Structure

3

To define structure, user need to create segment. While creating segment user will assign the value set created in previous step to one of the attribute.

5

Once user has created all the segments required, the structure is ready with these segments.42. Define Structure Instance

After creating a structure, user needs to create a structure instance. While defining structure instance, user need to associate the structure (defined in the previous step) with the Structure Instance. Segments in the structure will default including the value Set.

6

73. Deploy Flexfield

Once the structure instance definition is completed, user need to deploy it. Without deploying a Flexfield, organization cannot use it for transaction. Once the flexfield is deployed, a category structure definition is complete.

8

Create Catalog

After creating the catalog structure in previous steps, organization will define its catalog that is mapped to structure defined.

Navigate To: Implementation Project > Procurement > Define Common Procurement Configuration > Define Basic Catalogs > Manage Catalog

9

Once the catalog is ready, an organization will decide and create the categories required in context of a catalog. The categories created can be shared across multiple catalogs.

10

Default catalog

Finally, an organization catalog and category is ready to use with item. But before organization will create new item assigned to category, it needs to assign the catalog to business functional area. To assign the catalog to business functional area:

Navigate To: Implementation Project > Procurement > Define Common Procurement Configuration > Define Basic Catalogs > Manage Default Catalogs

11

Now, organization is ready to create an item for its operations.

Create Item

Create and item and assign catalog and category to classify item. Assignment to catalog and category is required also to make sure item is available for specific business operation, like purchasing, inventory, etc.

12

Making the Life Easier – R12

The above process requires to perform by an organization to create catalog. But here is the BIG change introduced by Oracle in R12, that removes the multiple steps require to create a catalog. In R12, user just needs to perform 1 single step to create catalog, i.e., “Define Functional Area catalogs”.

So, the multiple steps of R11:

  •          Manage Product Value Sets
  •          Manage Key Flexfield for Catalog
  •          Manage Catalog descriptive Flexfield
  •          Manage Category Descriptive Flexfields
  •          Create Catalog
  •          Manage Catalogs

zipped into a single step in R12:

  • Define Functional Area catalogs

Navigate To: Implementation Project > Procurement > Define Common Procurement Configuration > Define Functional Area catalogs > Manage Functional Area catalogs

13

So, now multiple questions/arguments coming into your mind, saying that this task is same as “Manage Default Catalogs” in R11. Yes, you are correct but all the flexfields dependency has been removed by oracle. Also, no need to create/define catalog and category first and then assign it to business functional area. Now in R12 at one single common task, user will create and assign catalog to business functional areas.

Click on edit for any of the business functional area and user will land on the below page

14

Leave a Reply

Your email address will not be published. Required fields are marked *