Functional Area Catalog Rules
This reference topic describes how predefined rules are applied to each of the predefined functional areas that can be assigned to catalogs.
A functional area represents one or more application level processes that use catalog data. Each functional area has a set of predefined rules that constrain the form, fit, and function of a catalog assigned to the functional area to meet the integration requirement of the functional area process. Catalogs that aren't assigned to a functional area aren't constrained by any rules and use the parameters in the user interface to control catalog behavior.
One or more functional areas can be assigned to a catalog. When you examine a catalog, you can see which functional areas the catalog might be assigned to.
A catalog can be assigned to one or more functional areas if the catalog being assigned meets the functional area rules. For example, the Inventory functional area and the Purchasing functional area might use the same catalog, and therefore that catalog is assigned to both functional areas.
Each owner of a functional area defines its specific rules and the Product Management application enforces the rules for any catalog that's created in the context of the functional area. In addition, if a catalog is assigned to a functional area, the catalog is validated against the functional area's rules.
A functional area rule can be implemented as a single parameter, or as an expression containing specific logic that's coded in the application. Some parameters are available to you in the user interface, such a choice list or button, so that you can view or change them. Some components in the user interface might be set to a specific value, or be disabled based on the rules.
This topic describes the available functional areas that you can assign to your catalogs, and how their predefined rules determine what effect your catalogs will have.
A functional area can only be assigned to one catalog at a time, though multiple functional areas can be assigned to the same catalog. Reassignment of a functional area to a catalog is allowed for some functional areas based on their rules, and is coded in the application. The reassignment action is available for functional areas that allow reassignment without validation.
Other topics describe how to create catalogs. When assigning a catalog functional area to a catalog, remember that:
-
To assign a functional area to a new catalog: In the Create Catalog dialog, select a value from the Functional Area list. You can't assign a functional area that's already assigned to an another catalog.
-
To assign a functional area to an existing catalog: On the Manage Catalogs page, select the catalog and click Assign. In the Assign to Functional Area dialog, select a value from the Functional Area list. You can't assign a functional area that's already assigned to an another catalog.
-
The functional areas assigned to a catalog are displayed in the Functional Area field in the Functional Area Parameters and Rules region of the Edit Functional Area Catalog page.
-
To work with catalogs in general, go to the Manage Catalogs page, which you can reach by either of these ways:
-
In the Product Information Management work area, use the Manage Catalogs task.
-
In the Setup and Maintenance work area, use the Manage Functional Area Catalogs task:
-
Offering: Product Management
-
Functional Area: Catalogs
-
Task: Manage Functional Area Catalogs
-
-
-
To find the catalog assigned to a functional area, open the Search filters on the Manage Catalogs page and add a search field for Functional Area, then search for that specified functional area. The search results display the catalog assigned to that functional area, if any.
Available Functional Areas
Here are the currently predefined functional areas:
-
Inventory
-
Purchasing
-
Planning
-
Service
-
Cost
-
Order Entry
-
Asset Management
-
Product Reporting
-
GDSN Syndication for UDEX
-
GDSN Syndication for GPC
-
Distributed Order Orchestration
-
Supplier Products and Services
-
VAT Invoices for China
-
Supply Chain Financial Flow Orchestration
-
Supply Chain Orchestration
-
Product Development
-
Quality Inspection Management
How Rules Are Applied To Functional Area Catalogs
In this section, we'll explain how predefined parameter settings affect functional area catalogs.
Parameters Used For Defining Functional Area Rules
This table describes the parameters that are used to control the behavior of the predefined functional areas, and how each parameter constrains or affects the behavior. Some of the parameters also apply to catalogs that haven't been assigned to a functional area. Some of the parameters can be controlled on the pages for creating and editing catalogs, some are controlled elsewhere.
Functional Area Rule |
Definition |
Where Presented in User Interface |
---|---|---|
Assign items to leaf-level categories only |
Allows items to be assigned to the lowest (or leaf) level of a category hierarchy. This parameter is ignored when the Enable hierarchy for catalog parameter is set to No, meaning that the catalog must be at a single level. |
Create Catalog dialog Details tab, and Functional Area Parameters and Rules region, of Edit Functional Area Catalog page Applies to all catalogs, with or without assignment to a functional area. |
Enable duplicate category names |
Allows duplicate category names across multiple catalogs. However, the category code must be unique for each category. For catalogs with hierarchy, category names can't be duplicated within the same level of the hierarchy. |
Predefined per functional area. This is a coded rule that's applied to specific functional area, no user interface control. Displayed read-only in Functional Area Parameters and Rules region of Edit Functional Area Catalog page |
Allow multiple item category assignments |
Allows items to be assigned to one or more categories in the same catalog. |
Create Catalog dialog Details tab, and Functional Area Parameters and Rules region, of Edit Functional Area Catalog page Applies to all catalogs, with or without assignment to a functional area. |
Enable deletion of item category assignments |
Allows item assignments to be deleted for a category. |
Predefined per functional area. This is a coded rule that's applied to specific functional area, no user interface control. Displayed read-only in Functional Area Parameters and Rules region of Edit Functional Area Catalog page |
Enable hierarchy for catalog |
Allows the catalog to have a hierarchy of categories within its categories. All functional area catalogs have this parameter selected by default when created. If the catalog is created in the context of a functional area, or assigned to a functional area, this rule can be set by the functional area. |
Predefined per functional area. This is a coded rule that's applied to specific functional area, no user interface control. Displayed read-only in Functional Area Parameters and Rules region of Edit Functional Area Catalog page |
Enable date-level control for item category assignments |
Allows the start date and end date of a category of the catalog to be used in processes. Item category assignments are date effective. |
Predefined per functional area. This is a coded rule that's applied to specific functional area, no user interface control. Displayed read-only in Functional Area Parameters and Rules region of Edit Functional Area Catalog page |
Default category required |
Requires that a category must exist for the catalog and be selected as the default category. The default category is used in the automatic assignment process for items. |
Predefined per functional area. This is a coded rule that's applied to specific functional area, no user interface control. The Default Category is selected in list in the Details tab of the Edit Functional Area Catalog page Applies to all catalogs, with or without assignment to a functional area. |
Controlled at (logic driven) |
Determines whether the catalog is controlled at the master level or the organization level:
See the separate table of expressions for the Controlled At parameter for each functional area. |
The Controlled At parameter in: Create Catalog dialog Details tab of the Edit Functional Area Catalog or Edit Catalog pages Applies to all catalogs, with or without assignment to a functional area. |
Catalog assignment change (logic driven) |
A logic expression associated with a functional area determines whether a catalog assigned to functional area can be removed from the functional area due to functional area processes that use the catalog data. See the separate table of expressions for catalog assignment changes for each functional area. |
Predefined per functional area. This is a coded rule that's applied to specific functional area, no user interface control. |
Catalog data security enabled |
Data security is enabled for the catalog and categories within the catalog. If the catalog is private, a data security grant must be defined for this type of catalog for users to access it. |
No user interface control. |
Automatic assignment of items |
Determines that items being created are automatically assigned to the default category for a catalog. The assignment is based on the value Yes being entered for certain attributes of certain attribute groups that are associated for this purpose with the functional area assigned to the catalog. See the separate table of functional areas that participate in the automatic assignment of items process. |
Predefined per functional area. This is a coded rule that's part of a process outside the creation of a catalog or the assignment of a catalog to a functional area. No user interface control. |
Restrict category to item assignment only |
Restricts the use of the default category in a functional area catalog to being the category to which new items are assigned. If the Enable hierarchy for catalog parameter is selected, then this parameter prevents the creation of child categories. |
Create Category dialog Category details on Hierarchy tab of Edit Functional Area Catalog page |
NOTE: Note: functional rules that are logic driven means that the rule is derived through an expression.
Expressions for the Controlled At Parameter for Each Functional Area
A functional area can have a specific set of logical constraints that are validated or enforced for the catalog when the catalog is assigned. During catalog creation, the value of the Controlled At parameter can be set to a value, or disabled based on the functional area rules. The logic for the Controlled At parameter uses the control level that's defined with the Manage Operational Attributes Groups task in the in the Setup and Maintenance work area. In that task, operational attribute groups are set up to be controlled at either the master level or the organization level.
In order for a catalog to be assigned to a functional area, the controlled-at level for a certain attribute of the items to be added to the catalog must agree with the controlled-at level of the catalog itself. The attributes that regulate each predefined functional area are specified in the following table.
Functional Area |
Expressions |
---|---|
Inventory |
For the Inventory attribute group: Inventory Item attribute, if the operational attribute control value is Master Level then both master and org controlled catalogs can be assigned. |
Purchasing |
If the Purchasing attribute group, Purchased attribute or Order Management attribute group internal ordered attribute control value is organization level, then organization-controlled catalogs can be assigned. |
Quality Inspection Management |
Catalog can be master controlled or organization controlled. |
Planning |
If the MPS and MRP planning attribute group, planning method attribute control value is organization level, then organization level-controlled catalogs can be assigned. If the MPS and MRP planning attribute group, planning method attribute control value is master level, then both master and organization-controlled catalogs can be assigned. |
Service |
Either master or organization controlled. |
Cost |
If the Costing attribute group, costing enabled attribute control value is master level, then both master level and organization level-controlled catalogs can be assigned. If the Costing attribute group, costing enabled attribute control value is organization level, then and organization level-controlled catalogs can be assigned. |
Order Entry |
If the order management attribute group, customer ordered attribute control value is master level, then both master level and organization level controlled catalogs can be assigned If the order management attribute group, customer ordered attribute control value is organization level, then and organization level controlled catalogs can be assigned. |
Asset Management |
Either master or organization controlled. |
Product Reporting |
Master level only. |
GDSN Syndication for UDEX |
Master level only. |
GDSN Syndication for GPC |
Master level only. |
Distributed Order Orchestration |
Either master or organization controlled. |
Supplier Products and Services |
Either master or organization controlled. |
VAT Invoices for China |
Master level only. |
Supply Chain Financial Flow Orchestration |
Either master or organization controlled. |
Supply Chain Orchestration |
Either master or organization controlled. |
Product Development |
Either master or organization controlled. |
Expressions for Catalog Assignment Changes for Each Functional Area
A functional area can have an associated logic expression that validates whether a catalog assigned to the functional area can be changed.
Functional Area |
Expressions |
---|---|
Inventory |
Catalog assignment change isn't allowed if an item assignment exists with INVENTORY_ITEM_FLAG = Y |
Purchasing |
Catalog assignment change isn't allowed if an item assignment exists with PURCHASING_ITEM_FLAG = Y or INTERNAL_ORDER_FLAG = Y |
Quality Inspection Management |
Catalog can be reassigned if no items are assigned to categories in the catalog. |
Planning |
CategorySetId change isn't allowed if an item assignment exists with ( (MRP_PLANNING_CODE <> 6 ) ) |
Service |
Catalog assignment change isn't allowed if an item assignment exists with INVENTORY_ITEM_FLAG = Y |
Cost |
Catalog Assignment change isn't allowed if an item assignment exists with COSTING_ENABLED_FLAG = Y |
Order Entry |
Catalog assignment change isn't allowed if an item assignment exists with INVENTORY_ITEM_FLAG = Y |
Asset Management |
Change allowed |
Product Reporting |
Change allowed |
GDSN Syndication for UDEX |
Catalog assignment change isn't allowed if an item assignment exists with GDSN_OUTBOUND_ENABLED_FLAG = Y |
GDSN Syndication for GPC |
Catalog assignment change isn't allowed if an item assignment exists with GDSN_OUTBOUND_ENABLED_FLAG = Y |
Distributed Order Orchestration |
Change allowed |
Supplier Products and Services |
Change allowed |
VAT Invoices for China |
Change allowed |
Supply Chain Financial Flow Orchestration |
Change allowed |
Supply Chain Orchestration |
Change allowed |
Product Development |
Change allowed |
Functional Areas that Participate in the Automatic Assignment of Items Process
A functional area can be enabled for an automatic process which assigns items to a default category in the catalog assigned to the functional area. This process is triggered when an item is created. Logic seeded as part of the functional area controls whether the item is automatically assigned to the default category for the catalog.
For example: If the Purchased attribute in the Purchasing attribute group has a value of Yes and the Internal Ordered attribute in the Order Management attribute group has value of Yes, then the new item is assigned to the default category in the functional area catalog for Purchasing.
Functional Area |
Attribute Group Name |
Attribute Name |
Attribute Internal Name |
Expression |
---|---|---|---|---|
Inventory |
Material Control |
Inventory Item |
INVENTORY_ITEM_FLAG |
Inventory: Material Control attribute group, Inventory Item attribute has a value of Yes, then the new item is assigned to the default category in the functional area catalog for Inventory. |
Purchasing |
Purchasing |
Purchased |
PURCHASING_ITEM_FLAG |
Purchasing: Purchasing attribute group, Purchased attribute has a value of Yes, then the new item is assigned to the default category in the functional area catalog for Purchasing. |
Planning |
General Planning |
Inventory Planning Method |
MRP_PLANNING_CODE |
Planning: General Planning attribute group, Inventory Planning Method attribute has a value of Yes, then the new item is assigned to the default category in the functional area catalog for Planning. |
Cost |
Costing |
Costing Enabled |
COSTING_ENABLED_FLAG |
Manufacturing: Costing attribute group, Costing Enabled attribute has a value of Yes, then the new item is assigned to the default category in the functional area catalog for Cost. |
Order Entry |
Order Management |
Customer Ordered |
CUSTOMER_ORDER_FLAG |
Sales and Order Management: Order Management attribute group, Customer Ordered attribute has a value of Yes, then the new item is assigned to the default category in the functional area catalog for Order Entry. |
Asset Management |
Asset Management |
Asset Item Type |
EAM_ITEM_TYPE |
Service: Asset attribute group, Enable Asset Tracking attribute has a value of Yes, then the new item is assigned to the default category in the functional area catalog for Asset Management. |
Service |
Service |
Contract Item Type |
CONTRACT_ITEM_TYPE_CODE |
Service: Service attribute group, Enable Contract Coverage attribute has a value of Yes, then the new item is assigned to the default category in the functional area catalog for Service. |
Summary of Functional Area Catalog Parameter Details
Functional Area Parameters Embedded in Catalog Details
The following table lists, for all the available functional areas, the predefined settings for the parameters shown in the Functional Area Parameters and Rules region of the Edit Functional Area Catalog page. These parameters are displayed on that page as check boxes that are selected or deselected, and their values are represented here as Yes or No, respectively.
Be sure to consult the table provided in the section on functional area parameters outside of catalog details, for the rest of the parameters.
Functional Area |
Assign items to leaf level categories only |
Allow multiple item category assignments |
Default Category Required |
Controlled At (logic driven) |
Catalog Assignment Change (logic driven) Assign action |
---|---|---|---|---|---|
Inventory |
Unchecked and disabled in UI. |
Unchecked and disabled in UI. |
Yes |
For Inventory attribute group: Inventory Item attribute, if the operational attribute control value is Master Level then both Master and Org controlled catalogs can be assigned. |
Catalog assignment change isn't allowed if an item assignment exists with INVENTORY_ITEM_FLAG = Y |
Purchasing |
Unchecked and disabled in UI. |
Unchecked and disabled in UI. |
Yes |
If the Purchasing attribute group, Purchased attribute or Order Management attribute group internal ordered attribute control value is organization level, then organization-controlled catalogs can be assigned. |
Catalog assignment change isn't allowed if an item assignment exists with PURCHASING_ITEM_FLAG = Y or INTERNAL_ORDER_FLAG = Y |
Quality Inspection Management |
No |
No |
No |
Either master or organization controlled |
Yes |
Planning |
Unchecked and disabled in UI. |
Unchecked and disabled in UI. |
Yes |
If MPS and MRP planning attribute group, planning method attribute control value is organization level, then organization level-controlled catalogs can be assigned. If MPS and MRP planning attribute group, planning method attribute control value is master level, then both master and organization-controlled catalogs can be assigned |
CategorySetId change isn't allowed if an item assignment exists with ( (MRP_PLANNING_CODE <> 6 ) ) |
Service |
Unchecked and disabled in UI. |
Unchecked and disabled in UI. |
Yes |
Either master or organization controlled |
Catalog assignment change isn't allowed if an item assignment exists with INVENTORY_ITEM_FLAG = Y |
Cost |
Unchecked and disabled in UI. |
Unchecked and disabled in UI. |
Yes |
If the costing attribute group, costing enabled attribute control value is master level, then both master level and organization level-controlled catalogs can be assigned. If the costing attribute group, costing enabled attribute control value is organization level, then and organization level-controlled catalogs can be assigned. |
Catalog Assignment change isn't allowed if an item assignment exists with COSTING_ENABLED_FLAG = Y |
Order Entry |
Unchecked and disabled in UI. |
Unchecked and disabled in UI. |
Yes |
If the order management attribute group, customer ordered attribute control value is master level, then both master level and organization level controlled catalogs can be assigned If the order management attribute group, customer ordered attribute control value is organization level, then and organization level controlled catalogs can be assigned |
Catalog assignment change isn't allowed if an item assignment exists with INVENTORY_ITEM_FLAG = Y |
Asset Management |
Unchecked and disabled in UI. |
Checked and disabled in UI. |
Yes |
Either master or organization controlled |
Change allowed |
Product Reporting |
Unchecked and disabled in UI. |
Checked and disabled in UI. |
Yes |
Master level only |
Change allowed |
GDSN Syndication for UDEX |
Unchecked and editable in UI. |
Checked and disabled in UI. |
Yes |
Master level only |
Catalog assignment change isn't allowed if an item assignment exists with GDSN_OUTBOUND_ENABLED_FLAG = Y |
GDSN Syndication for GPC |
Unchecked and editable in UI. |
Checked and disabled in UI. |
Yes |
Master level only |
Catalog assignment change isn't allowed if an item assignment exists with GDSN_OUTBOUND_ENABLED_FLAG = Y |
Distributed Order Orchestration |
Unchecked and disabled in UI. |
Unchecked and disabled in UI. |
Yes |
Either master or organization controlled |
Change allowed |
Supplier Products and Services |
Unchecked and editable in UI. |
Checked and disabled in UI. |
No |
Either master or organization controlled |
Change allowed |
VAT Invoices for China |
Unchecked and editable in UI. |
Unchecked and disabled in UI. |
No |
Master level only |
Change allowed |
Supply Chain Financial Flow Orchestration |
Unchecked and disabled in UI. |
Checked and disabled in UI. |
Yes |
Either master or organization controlled |
Change allowed |
Supply Chain Orchestration |
Unchecked and disabled in UI. |
Checked and disabled in UI. |
Yes |
Either master or organization controlled |
Change allowed |
Product Development |
Unchecked and editable in UI. |
Checked and disabled in UI. |
No |
Either master or organization controlled |
Change allowed |
Predefined Functional Area Parameters
The following table lists, for all of the available functional areas, the predefined settings for the parameters that are set or stored outside of the Edit Functional Area Catalog page.
Be sure to consult the table provided in the section on functional area parameters embedded in catalog details, for the rest of the parameters.
Functional Area |
Controlled At (logic driven) |
Catalog Assignment Change (logic driven) |
Catalog Data Security Enabled |
Enable duplicate category names |
Enable deletion of item category assignments |
Enable hierarchy for catalog |
Enable date level control for item category assignments |
---|---|---|---|---|---|---|---|
Inventory |
For Inventory attribute group: Inventory Item attribute, if the operational attribute control value is Master Level then both Master and Org controlled catalogs can be assigned. |
Catalog assignment change isn't allowed if an item assignment exists with INVENTORY_ITEM_FLAG = Y |
No |
No |
No |
No |
No |
Purchasing |
If the Purchasing attribute group, Purchased attribute or Order Management attribute group internal ordered attribute control value is organization level, then organization-controlled catalogs can be assigned. |
Catalog assignment change isn't allowed if an item assignment exists with PURCHASING_ITEM_FLAG = Y or INTERNAL_ORDER_FLAG = Y |
No |
No |
No |
No |
No |
Quality Inspection Management |
Catalog can be master controlled, or organization controlled |
Catalog can be reassigned if no items are assigned to categories in the catalog. |
No |
No |
Yes |
No |
No |
Planning |
If MPS and MRP planning attribute group, planning method attribute control value is organization level, then organization level-controlled catalogs can be assigned. If MPS and MRP planning attribute group, planning method attribute control value is master level, then both master and organization-controlled catalogs can be assigned. |
CategorySetId change isn't allowed if an item assignment exists with ( (MRP_PLANNING_CODE <> 6 ) ) |
No |
No |
No |
No |
No |
Service |
Either master or organization controlled |
Catalog assignment change isn't allowed if an item assignment exists with INVENTORY_ITEM_FLAG = Y |
No |
No |
No |
No |
No |
Cost |
If the costing attribute group, costing enabled attribute control value is master level, then both master level and organization level-controlled catalogs can be assigned. If the costing attribute group, costing enabled attribute control value is organization level, then and organization level-controlled catalogs can be assigned. |
Catalog Assignment change isn't allowed if an item assignment exists with COSTING_ENABLED_FLAG = Y |
No |
No |
No |
No |
No |
Order Entry |
If the order management attribute group, customer ordered attribute control value is master level, then both master level and organization level controlled catalogs can be assigned If the order management attribute group, customer ordered attribute control value is organization level, then and organization level controlled catalogs can be assigned. |
Catalog assignment change isn't allowed if an item assignment exists with INVENTORY_ITEM_FLAG = Y |
No |
No |
No |
No |
No |
Asset Management |
Either master or organization controlled |
Change allowed |
No |
No |
No |
No |
No |
Product Reporting |
Master level only |
Change allowed |
No |
No |
No |
No |
No |
GDSN Syndication for UDEX |
Master level only |
Catalog assignment change isn't allowed if an item assignment exists with GDSN_OUTBOUND_ENABLED_FLAG = Y |
No |
Yes |
No |
Yes |
No |
GDSN Syndication for GPC |
Master level only |
Catalog assignment change isn't allowed if an item assignment exists with GDSN_OUTBOUND_ENABLED_FLAG = Y |
No |
Yes |
No |
Yes |
No |
Distributed Order Orchestration |
Either master or organization controlled |
Change allowed |
No |
No |
No |
No |
No |
Supplier Products and Services |
Either master or organization controlled |
Change allowed |
No |
Yes |
No |
Yes |
No |
VAT Invoices for China |
Master level only |
Change allowed |
No |
Yes |
No |
Yes |
No |
Supply Chain Financial Flow Orchestration |
Either master or organization controlled |
Change allowed |
No |
No |
No |
No |
No |
Supply Chain Orchestration |
Either master or organization controlled |
Change allowed |
No |
No |
No |
No |
No |
Product Development |
Either master or organization controlled |
Change allowed |
No |
Yes |
No |
Yes |
No |
Individual Functional Area Catalog Parameter Details
Rule Details for Functional Area: Inventory
The following table describes all the parameters used to define rules for this function area catalog.
Rule |
Definition |
---|---|
Assign items to leaf level categories only |
Unchecked and disabled in UI. |
Allow multiple item category assignments |
Unchecked and disabled in UI. |
Default Category Required |
Yes |
Restrict category to item assignment only |
Unchecked and disabled in UI. |
Controlled At (logic driven) |
For Inventory attribute group: Inventory Item attribute, if the operational attribute control value is Master Level then both Master and Org controlled catalogs can be assigned. |
Catalog Assignment Change (logic driven) |
Catalog assignment change isn't allowed if an item assignment exists with INVENTORY_ITEM_FLAG = Y |
Catalog Data Security Enabled |
No |
Automatic Assignment of Items |
Inventory: Material Control attribute group, Inventory Item attribute has a value of 'yes', then the new item is assigned to the default category in the functional area catalog for Inventory. |
Enable duplicate category names |
N/A for single level catalog. |
Enable deletion of item category assignments |
No |
Enable hierarchy for catalog |
No |
Enable date level control for item category assignments |
No |
Rule Details for Functional Area: Purchasing
The following table describes all the parameters used to define rules for this function area catalog.
Rule |
Definition |
---|---|
Assign items to leaf level categories only |
Unchecked and disabled in UI. |
Allow multiple item category assignments |
Unchecked and disabled in UI. |
Default Category Required |
Yes |
Restrict category to item assignment only |
Unchecked and disabled in UI. |
Controlled At (logic driven) |
If the Purchasing attribute group, Purchased attribute or Order Management attribute group internal ordered attribute control value is organization level, then organization-controlled catalogs can be assigned. |
Catalog Assignment Change (logic driven) |
Catalog assignment change isn't allowed if an item assignment exists with PURCHASING_ITEM_FLAG = Y or INTERNAL_ORDER_FLAG = Y |
Catalog Data Security Enabled |
No |
Automatic Assignment of Items |
Purchasing: Purchasing attribute group, Purchased attribute has a value of Yes, then the new item is assigned to the default category in the functional area catalog for Purchasing. |
Enable duplicate category names |
N/A for single level catalog. |
Enable deletion of item category assignments |
No |
Enable hierarchy for catalog |
No |
Enable date level control for item category assignments |
No |
Rule Details for Functional Area: Quality Inspection Management
The following table describes all the parameters used to define rules for this function area catalog.
Rule |
Definition |
---|---|
Assign items to leaf level categories only |
Unchecked and disabled in UI. |
Allow multiple item category assignments |
Unchecked and disabled in UI. |
Default Category Required |
No |
Restrict category to item assignment only |
Unchecked and disabled in UI. |
Controlled At (logic driven) |
Catalog can be master controlled, or organization controlled |
Catalog Assignment Change (logic driven) |
Catalog can be reassigned if no items are assigned to categories in the catalog. |
Catalog Data Security Enabled |
No |
Automatic Assignment of Items |
N/A |
Enable duplicate category names |
N/A for single level catalog. |
Enable deletion of item category assignments |
Yes |
Enable hierarchy for catalog |
No |
Enable date level control for item category assignments |
No |
Rule Details for Functional Area: Planning
The following table describes all the parameters used to define rules for this function area catalog.
Rule |
Definition |
---|---|
Assign items to leaf level categories only |
Unchecked and disabled in UI. |
Allow multiple item category assignments |
Unchecked and disabled in UI. |
Default Category Required |
Yes |
Restrict category to item assignment only |
Unchecked and disabled in UI. |
Controlled At (logic driven) |
If the Purchasing attribute group, Purchased attribute or Order Management attribute group internal ordered attribute control value is organization level, then organization-controlled catalogs can be assigned. |
Catalog Assignment Change (logic driven) |
Catalog assignment change isn't allowed if an item assignment exists with PURCHASING_ITEM_FLAG = Y or INTERNAL_ORDER_FLAG = Y |
Catalog Data Security Enabled |
No |
Automatic Assignment of Items |
Purchasing: Purchasing attribute group, Purchased attribute has a value of Yes', then the new item is assigned to the default category in the functional area catalog for Purchasing. |
Enable duplicate category names |
N/A for single level catalog. |
Enable deletion of item category assignments |
No |
Enable hierarchy for catalog |
No |
Enable date level control for item category assignments |
No |
Rule Details for Functional Area: Service
The following table describes all the parameters used to define rules for this function area catalog.
Rule |
Definition |
---|---|
Assign items to leaf level categories only |
Unchecked and disabled in UI. |
Allow multiple item category assignments |
Unchecked and disabled in UI. |
Default Category Required |
Yes |
Restrict category to item assignment only |
Unchecked and disabled in UI. |
Controlled At (logic driven) |
If the Purchasing attribute group, Purchased attribute or Order Management attribute group internal ordered attribute control value is organization level, then organization-controlled catalogs can be assigned. |
Catalog Assignment Change (logic driven) |
Catalog assignment change isn't allowed if an item assignment exists with PURCHASING_ITEM_FLAG = Y or INTERNAL_ORDER_FLAG = Y |
Catalog Data Security Enabled |
No |
Automatic Assignment of Items |
Purchasing: Purchasing attribute group, Purchased attribute has a value of Yes, then the new item is assigned to the default category in the functional area catalog for Purchasing. |
Enable duplicate category names |
N/A for single level catalog. |
Enable deletion of item category assignments |
No |
Enable hierarchy for catalog |
No |
Enable date level control for item category assignments |
No |
Rule Details for Functional Area: Cost
The following table describes all the parameters used to define rules for this function area catalog.
Rule |
Definition |
---|---|
Assign items to leaf level categories only |
Unchecked and disabled in UI. |
Allow multiple item category assignments |
Unchecked and disabled in UI. |
Default Category Required |
Yes |
Restrict category to item assignment only |
Unchecked and disabled in UI. |
Controlled At (logic driven) |
If the Purchasing attribute group, Purchased attribute or Order Management attribute group internal ordered attribute control value is organization level, then organization-controlled catalogs can be assigned. |
Catalog Assignment Change (logic driven) |
Catalog assignment change isn't allowed if an item assignment exists with PURCHASING_ITEM_FLAG = Y or INTERNAL_ORDER_FLAG = Y |
Catalog Data Security Enabled |
No |
Automatic Assignment of Items |
Purchasing: Purchasing attribute group, Purchased attribute has a value of Yes, then the new item is assigned to the default category in the functional area catalog for Purchasing. |
Enable duplicate category names |
N/A for single level catalog. |
Enable deletion of item category assignments |
No |
Enable hierarchy for catalog |
No |
Enable date level control for item category assignments |
No |
Rule Details for Functional Area: Order Entry
The following table describes all the parameters used to define rules for this function area catalog.
Rule |
Definition |
---|---|
Assign items to leaf level categories only |
Unchecked and disabled in UI. |
Allow multiple item category assignments |
Unchecked and disabled in UI. |
Default Category Required |
Yes |
Restrict category to item assignment only |
Unchecked and disabled in UI. |
Controlled At (logic driven) |
If the Purchasing attribute group, Purchased attribute or Order Management attribute group internal ordered attribute control value is organization level, then organization-controlled catalogs can be assigned. |
Catalog Assignment Change (logic driven) |
Catalog assignment change isn't allowed if an item assignment exists with PURCHASING_ITEM_FLAG = Y or INTERNAL_ORDER_FLAG = Y |
Catalog Data Security Enabled |
No |
Automatic Assignment of Items |
Purchasing: Purchasing attribute group, Purchased attribute has a value of Yes, then the new item is assigned to the default category in the functional area catalog for Purchasing. |
Enable duplicate category names |
N/A for single level catalog. |
Enable deletion of item category assignments |
No |
Enable hierarchy for catalog |
No |
Enable date level control for item category assignments |
No |
Rule Details for Functional Area: Asset Management
The following table describes all the parameters used to define rules for this function area catalog.
Rule |
Definition |
---|---|
Assign items to leaf level categories only |
Unchecked and disabled in UI. |
Allow multiple item category assignments |
Unchecked and disabled in UI. |
Default Category Required |
Yes |
Restrict category to item assignment only |
Unchecked and disabled in UI. |
Controlled At (logic driven) |
If the Purchasing attribute group, Purchased attribute or Order Management attribute group internal ordered attribute control value is organization level, then organization-controlled catalogs can be assigned. |
Catalog Assignment Change (logic driven) |
Catalog assignment change isn't allowed if an item assignment exists with PURCHASING_ITEM_FLAG = Y or INTERNAL_ORDER_FLAG = Y |
Catalog Data Security Enabled |
No |
Automatic Assignment of Items |
Purchasing: Purchasing attribute group, Purchased attribute has a value of Yes, then the new item is assigned to the default category in the functional area catalog for Purchasing. |
Enable duplicate category names |
N/A for single level catalog. |
Enable deletion of item category assignments |
No |
Enable hierarchy for catalog |
No |
Enable date level control for item category assignments |
No |
Rule Details for Functional Area: Product Reporting
The following table describes all the parameters used to define rules for this function area catalog.
Rule |
Definition |
---|---|
Assign items to leaf level categories only |
Unchecked and disabled in UI. |
Allow multiple item category assignments |
Unchecked and disabled in UI. |
Default Category Required |
Yes |
Restrict category to item assignment only |
Unchecked and disabled in UI. |
Controlled At (logic driven) |
If the Purchasing attribute group, Purchased attribute or Order Management attribute group internal ordered attribute control value is organization level, then organization-controlled catalogs can be assigned. |
Catalog Assignment Change (logic driven) |
Catalog assignment change isn't allowed if an item assignment exists with PURCHASING_ITEM_FLAG = Y or INTERNAL_ORDER_FLAG = Y |
Catalog Data Security Enabled |
No |
Automatic Assignment of Items |
Purchasing: Purchasing attribute group, Purchased attribute has a value of Yes, then the new item is assigned to the default category in the functional area catalog for Purchasing. |
Enable duplicate category names |
N/A for single level catalog. |
Enable deletion of item category assignments |
No |
Enable hierarchy for catalog |
No |
Enable date level control for item category assignments |
No |
Rule Details for Functional Area: GDSN Syndication for UDEX
The following table describes all the parameters used to define rules for this function area catalog.
Rule |
Definition |
---|---|
Assign items to leaf level categories only |
Unchecked and disabled in UI. |
Allow multiple item category assignments |
Unchecked and disabled in UI. |
Default Category Required |
Yes |
Restrict category to item assignment only |
Unchecked and disabled in UI. |
Controlled At (logic driven) |
If the Purchasing attribute group, Purchased attribute or Order Management attribute group internal ordered attribute control value is organization level, then organization-controlled catalogs can be assigned. |
Catalog Assignment Change (logic driven) |
Catalog assignment change isn't allowed if an item assignment exists with PURCHASING_ITEM_FLAG = Y or INTERNAL_ORDER_FLAG = Y |
Catalog Data Security Enabled |
No |
Automatic Assignment of Items |
Purchasing: Purchasing attribute group, Purchased attribute has a value of Yes, then the new item is assigned to the default category in the functional area catalog for Purchasing. |
Enable duplicate category names |
N/A for single level catalog. |
Enable deletion of item category assignments |
No |
Enable hierarchy for catalog |
No |
Enable date level control for item category assignments |
No |
Rule Details for Functional Area: GDSN Syndication for GPC
The following table describes all the parameters used to define rules for this function area catalog.
Rule |
Definition |
---|---|
Assign items to leaf level categories only |
Unchecked and disabled in UI. |
Allow multiple item category assignments |
Unchecked and disabled in UI. |
Default Category Required |
Yes |
Restrict category to item assignment only |
Unchecked and disabled in UI. |
Controlled At (logic driven) |
If the Purchasing attribute group, Purchased attribute or Order Management attribute group internal ordered attribute control value is organization level, then organization-controlled catalogs can be assigned. |
Catalog Assignment Change (logic driven) |
Catalog assignment change isn't allowed if an item assignment exists with PURCHASING_ITEM_FLAG = Y or INTERNAL_ORDER_FLAG = Y |
Catalog Data Security Enabled |
No |
Automatic Assignment of Items |
Purchasing: Purchasing attribute group, Purchased attribute has a value of Yes, then the new item is assigned to the default category in the functional area catalog for Purchasing. |
Enable duplicate category names |
N/A for single level catalog. |
Enable deletion of item category assignments |
No |
Enable hierarchy for catalog |
No |
Enable date level control for item category assignments |
No |
Rule Details for Functional Area: Distributed Order Orchestration
The following table describes all the parameters used to define rules for this function area catalog.
Rule |
Definition |
---|---|
Assign items to leaf level categories only |
Unchecked and disabled in UI. |
Allow multiple item category assignments |
Unchecked and disabled in UI. |
Default Category Required |
Yes |
Restrict category to item assignment only |
Unchecked and disabled in UI. |
Controlled At (logic driven) |
If the 'Purchasing' attribute group, 'Purchased' attribute or 'Order Management' attribute group internal ordered attribute control value is organization level, then organization-controlled catalogs can be assigned. |
Catalog Assignment Change (logic driven) |
Catalog assignment change isn't allowed if an item assignment exists with PURCHASING_ITEM_FLAG = Y or INTERNAL_ORDER_FLAG = Y |
Catalog Data Security Enabled |
No |
Automatic Assignment of Items |
Purchasing: Purchasing attribute group, Purchased attribute has a value of Yes, then the new item is assigned to the default category in the functional area catalog for Purchasing. |
Enable duplicate category names |
N/A for single level catalog. |
Enable deletion of item category assignments |
No |
Enable hierarchy for catalog |
No |
Enable date level control for item category assignments |
No |
Rule Details for Functional Area: Supplier Products and Services
The following table describes all the parameters used to define rules for this function area catalog.
Rule |
Definition |
---|---|
Assign items to leaf level categories only |
Unchecked and disabled in UI. |
Allow multiple item category assignments |
Unchecked and disabled in UI. |
Default Category Required |
Yes |
Restrict category to item assignment only |
Unchecked and disabled in UI. |
Controlled At (logic driven) |
If the Purchasing attribute group, Purchased attribute or Order Management attribute group internal ordered attribute control value is organization level, then organization-controlled catalogs can be assigned. |
Catalog Assignment Change (logic driven) |
Catalog assignment change isn't allowed if an item assignment exists with PURCHASING_ITEM_FLAG = Y or INTERNAL_ORDER_FLAG = Y |
Catalog Data Security Enabled |
No |
Automatic Assignment of Items |
Purchasing: Purchasing attribute group, Purchased attribute has a value of Yes, then the new item is assigned to the default category in the functional area catalog for Purchasing. |
Enable duplicate category names |
N/A for single level catalog. |
Enable deletion of item category assignments |
No |
Enable hierarchy for catalog |
No |
Enable date level control for item category assignments |
No |
Rule Details for Functional Area: VAT Invoices for China
The following table describes all the parameters used to define rules for this function area catalog.
Rule |
Definition |
---|---|
Assign items to leaf level categories only |
Unchecked and disabled in UI. |
Allow multiple item category assignments |
Unchecked and disabled in UI. |
Default Category Required |
Yes |
Restrict category to item assignment only |
Unchecked and disabled in UI. |
Controlled At (logic driven) |
If the Purchasing attribute group, Purchased attribute or Order Management attribute group internal ordered attribute control value is organization level, then organization-controlled catalogs can be assigned. |
Catalog Assignment Change (logic driven) |
Catalog assignment change isn't allowed if an item assignment exists with PURCHASING_ITEM_FLAG = Y or INTERNAL_ORDER_FLAG = Y |
Catalog Data Security Enabled |
No |
Automatic Assignment of Items |
Purchasing: Purchasing attribute group, Purchased attribute has a value of Yes, then the new item is assigned to the default category in the functional area catalog for Purchasing. |
Enable duplicate category names |
N/A for single level catalog. |
Enable deletion of item category assignments |
No |
Enable hierarchy for catalog |
No |
Enable date level control for item category assignments |
No |
Rule Details for Functional Area: Supply Chain Financial Flow Orchestration
The following table describes all the parameters used to define rules for this function area catalog.
Rule |
Definition |
---|---|
Assign items to leaf level categories only |
Unchecked and disabled in UI. |
Allow multiple item category assignments |
Unchecked and disabled in UI. |
Default Category Required |
Yes |
Restrict category to item assignment only |
Unchecked and disabled in UI. |
Controlled At (logic driven) |
If the Purchasing attribute group, Purchased attribute or Order Management attribute group internal ordered attribute control value is organization level, then organization-controlled catalogs can be assigned. |
Catalog Assignment Change (logic driven) |
Catalog assignment change isn't allowed if an item assignment exists with PURCHASING_ITEM_FLAG = Y or INTERNAL_ORDER_FLAG = Y |
Catalog Data Security Enabled |
No |
Automatic Assignment of Items |
Purchasing: Purchasing attribute group, Purchased attribute has a value of Yes, then the new item is assigned to the default category in the functional area catalog for Purchasing. |
Enable duplicate category names |
N/A for single level catalog. |
Enable deletion of item category assignments |
No |
Enable hierarchy for catalog |
No |
Enable date level control for item category assignments |
No |
Rule Details for Functional Area: Supply Chain Orchestration
The following table describes all the parameters used to define rules for this function area catalog.
Rule |
Definition |
---|---|
Assign items to leaf level categories only |
Unchecked and disabled in UI. |
Allow multiple item category assignments |
Unchecked and disabled in UI. |
Default Category Required |
Yes |
Restrict category to item assignment only |
Unchecked and disabled in UI. |
Controlled At (logic driven) |
If the Purchasing attribute group, Purchased attribute or Order Management attribute group internal ordered attribute control value is organization level, then organization-controlled catalogs can be assigned. |
Catalog Assignment Change (logic driven) |
Catalog assignment change isn't allowed if an item assignment exists with PURCHASING_ITEM_FLAG = Y or INTERNAL_ORDER_FLAG = Y |
Catalog Data Security Enabled |
No |
Automatic Assignment of Items |
Purchasing: Purchasing attribute group, Purchased attribute has a value of Yes, then the new item is assigned to the default category in the functional area catalog for Purchasing. |
Enable duplicate category names |
N/A for single level catalog. |
Enable deletion of item category assignments |
No |
Enable hierarchy for catalog |
No |
Enable date level control for item category assignments |
No |
Rule Details for Functional Area: Product Development
The following table describes all the parameters used to define rules for this function area catalog.
Rule |
Definition |
---|---|
Assign items to leaf level categories only |
Checked and enabled in UI and set to Yes. |
Allow multiple item category assignments |
Enabled and set to Yes. |
Default Category Required |
No |
Controlled At (logic driven) |
Master level |
Catalog Data Security Enabled |
No |
Enable duplicate category names |
N/A for single level catalog. |
Enable deletion of item category assignments |
No |
Enable hierarchy for catalog |
Yes |
Enable date level control for item category assignments |
No |
Use the Setup and Maintenance work area (in the Product Management offering) to associate a catalog to a functional area; you need to do this only once.