Categories Categorysets Keyflexfeilds - Oracle Apps R12
Categories Categorysets Keyflexfeilds - Oracle Apps R12
You can define an unlimited number of categories and group subsets of your categories into
category sets. A category can belong to multiple category sets. You can assign a category to a
category set either at the time you define a category set or at the time you assign an item to
the category.
To define a category:
o to an item
You cannot assign an inactive date to a category that is the default category for a
mandatory category set.
When you install Oracle Inventory or Oracle Purchasing Oracle provides the category set
Standard.
When you install or upgrade Inventory, Oracle provides the category set Inventory by default
and assigns existing inventory categories to this set. If you plan to use Order Entry/Shipping's
group pricing functionality with item categories, you must add the categories to this set.
When you upgrade Oracle Purchasing from a previous version, Oracle provides the category
set Class by default and assigns your existing purchasing categories to this set.
Attention: You must use this window to define valid categories for each
purchasing category set before you can use Oracle Purchasing.
The flexibility of category sets allows you to report and inquire on items in a way that best
suits your needs.
Steps Involved
o Define flexfield structures for the item categories flexfield.
o Define categories.
o Define category sets.
You must define default category sets for your functional areas. See: Defining
Default Category Sets.
When you enable an item in a functional area, the item is assigned to the default (mandatory)
category set and default category of the functional area. You can override the category set's default
category. In addition, you can manually assign your item to an unlimited number of category sets.
You can assign an item to one category within each category set.
4. Select the item from the current organization to assign to the category.
5. Select a category.
The list of values contains categories with the same flexfield structure as the category set
you selected in the Category Set window. If Enforce the list of valid categories is selected the
list is limited to those categories.
2. Select an item.
The item you selected appears at the top of the Category Assignment window.
The list of values contains categories with the same flexfield structure as the category set
you selected. If Enforce the list of valid categories is selected the list is limited to those
categories.
After assigning an item to another organization you can disable the item for one or more
functional areas in the new organization. However, Inventory does not remove the
corresponding functional area's default category set. For example, you may have set the value
of the Purchased attribute to "Yes" when you defined the item in the item master
organization. When you assign this item to another organization Inventory copies over the
"Yes" value of the Purchased attribute and therefore assigns the default category set of the
purchasing functional area. In the new organization you may decide to set the value of the
Purchased attribute to "No." After you disable the item for the purchasing functional area in
the new organization, the item still retains the purchasing default category set. You may
manually delete the purchasing category set in the new organization.
If you copy an item from another item with category sets defined at the Organization level,
Inventory assigns the new item the default categories of the mandatory category sets, even if
the original item did not have the default categories. This is because Inventory copies the
values of the item defining attributes and not the category sets and categories themselves.
When you install or upgrade Oracle Inventory or Oracle Purchasing, Oracle provides two
category flexfield structures by default: Item Categories and PO Item Category.
Each segment structure can display prompts and fields that apply specifically to a particular
naming convention. For example, you might want one of your category sets to use two
segments for the names of categories. Another item grouping scheme might use just one
segment for the names of categories. You choose a flexfield structure for every category set
and category that you define.
Once you set up or modify your structures and segments, you must freeze your flexfield
definition and save your changes. When you do, your flexfield compiles automatically to
improve on-line performance. You must recompile your flexfield every time you make
changes using this form, including enabling or disabling cross-validation rules. You must also
recompile your flexfield after you enable or disable shorthand entry using the Shorthand
Aliases window.
You can see your flexfield changes immediately after you freeze and recompile your
flexfield. However, your changes affect other users only after they change responsibilities or
exit your application and sign back on.
Once you freeze your flexfield definition and save your changes, Oracle Applications submits
one or two concurrent requests to generate database views of the flexfield's combinations
table. You can use these views for custom reporting at your site. One of these views is always
generated and contains concatenated segment values for all structures of the key flexfield.
You see the name of this view in the Toolbar window. The other view is for the particular
structure you are defining and freezing. This second view is generated only if you enter a
view name for your structure in the View Name field. See: Overview of Flexfield Views.
Warning: Plan your key flexfield structures carefully, including all your segment information such as
segment order and field lengths, before you define your segments using this form. You can define
your key flexfields any way you want, but changing your structures once you acquire any flexfield
data may create data inconsistencies that could have a significant impact on the behavior of your
application or require a complex conversion program. Changing your existing structures may also
adversely affect the behavior of to start taking changes again. does any of that make senseany cross-
validation rules or shorthand aliases you have set for your structures, so you should be sure to
manually disable or redefine any cross-validation rules (using the Cross-Validation Rules window)
and shorthand aliases (using the Shorthand Aliases window) to reflect your changed structures.