3Defining Items

This chapter contains the following:

Define Items: Overview

Before you can define items in Oracle Fusion Product Hub, you must complete several tasks in the Setup and Maintenance work area.

Task Description

Manage Item Profile Options

Profile options manage configuration data centrally and influence the behavior of applications.

Manage Advanced Item Profile Options

This task is used by Product Hub. If you do not install Product Hub, you do not need to define these options.

Define Units of Measure

Units of Measure must be created before you can create or import items.

Manage Lifecycle Phases

Item Lifecycle Phases are used as an indicator of the stage for an item within the lifecycle process. Each phase represents a set of tasks and deliverables that are required before promoting an item to the next phase.

Manage Product and Child Value Sets

In Product Hub, value sets are primarily used to define attributes that have a specific set of values. Each value set is associated with one or more attributes in the same attribute group or in a different attribute group.

Manage Attachment Categories for Product Management

Used to create attachment categories and associate them with item classes.

Manage Operational Attribute Groups

Operational attributes determine the behavior of the item with respect to various applications outside of Product Hub, such as Oracle Fusion Purchasing or Oracle Fusion Inventory Management.

Manage Item Attribute Groups and Attributes

Used to determine how the attributes appear in the user interface, as well as how they are used in the application.

Manage Item Classes

Item classes are created at the root item class or under the parent item class and inherit values based on selections made when defining the item class.

For Product Hub customers, the Manage Item Classes task is used to create and manage item classes, user defined attributes and data security.

Manage Item Class Descriptive Flexfields

Descriptive flexfields appear in the user interface as additional information and can also appear in search results tables.

Deploy Item Flexfields

After you associate attribute groups and pages with an item class, you must deploy flexfields to view the pages or attribute groups at runtime. The metadata that was created for the attribute group is not synchronized with the production data in Product Hub until the flexfield is deployed.

Manage Item Statuses

Item statuses are used to define the state an item is in and based on the state, the default values for item operational attributes.

Manage Item Types

Item types are date effective and are made active or inactive by adjusting the start and end dates.

Manage Cross Reference Types

Cross-References provide the functionality to map additional information about an item in the form of a value and cross-reference type. For example, the cross-reference can map a relationship between an item and an old part number.

Manage Item Descriptive Flexfields

Used to define descriptive flexfields that are specific to items.

Download Import Template

Each template includes table-specific instructions, guidelines, formatted spreadsheets, and best practices for preparing the data file for upload.

Upload Item Data

After you have created the CSV file, the next step in the Import process will upload the CSV Zip file to the designated location within the Oracle Universal Content Management system.

Load Interface File through Scheduled Process

Once the CSV file is uploaded to UCM, you use the Load Interface File for Import scheduled process to move the data from the UCM folder to the interface tables.

Import Items

The Item Import task creates an Enterprise Scheduled Service (ESS) process that takes the data that is loaded in the interface tables and uses the import process to move the data to the production tables.

Monitor Item Imports

Use this task to monitor the ESS process status in the search results table

Manage Related Item Subtypes

A related item is an item relationship between two existing items. How the two items are related is defined by a subtype.

Manage Item Revision Descriptive Flexfields

Use descriptive flexfields associated at Item Revision level to capture item revision information whose values may differ between revisions of the same item.

Manage Item Relationship Descriptive Flexfields

Item types are date effective and are made active or inactive by adjusting the Start Date and End Date.

Manage Trading Partner Item Descriptive Flexfields

When defining descriptive flexfields associated with trading partner items, you must use certain prefixes when naming the context segments, in order for the segments to be displayed for the respective trading partner type.

Define Item-Specific UOM Conversions

After you define units of measure, define the conversions used for items.

Item Profile Options: Explained

Profile options manage configuration data centrally and influence the behavior of applications.

The profile options have a default value, which can be used for initial installations. These profile options should be evaluated to determine if additional values should be set:

  • EGP_DISPLAY_IMAGES: Specify if images should be displayed in the search results table in the Manage Items task.

  • EGP_ITEM_IMPORT_ITEMS_PER_THREAD: During item import, multiple threads of operation are created to process the items being imported. This profile option controls how many items are processed per each thread. It is a technical option used to optimize item import performance. The default value is 100.

  • EGP_ITEM_IMPORT_NUMBER_OF THREADS: This option works in conjunction with the EGP_ITEM_IMPORT_ITEMS_PER_THRESD option. It controls how many threads of operations are created during the item import process. The default is 4.

  • EGP_UPDATEABLE_ITEM: By default, the item number can't be changed after the item has been created. It can be updated after creation only if this option is set to Yes.

Advanced Item Profile Options: Explained

Profile options manage configuration data centrally and influence the behavior of applications. Only those customers who have licensed Oracle Fusion Product Hub can access these advanced profile options.

The profile options have a default value, which can be used for initial installations. These advanced profile options should be evaluated to determine if additional values should be set. Manage these values using the Manage Advanced Item Profile Options task in the Setup and Maintenance work area.

  • EGO_ASSIGN_PACK_ORG: Assign all child items in the pack to the same organization as the parent pack item.

  • EGO_ASSIGN_PACK_SUP_SITE_ORG: Assign all child items in the pack to the same supplier site organization combination as the parent pack item.

  • EGO_DEFAULT_STYLE_CATALOG: Enable the assignment of the related SKU items to the same catalog as the style item.

  • EGO_DEFAULT_STYLE_ITEM__ORG: Enable the assignment of the related SKU items to the same organization as the style item.

  • EGO_DEFAULT_STYLE_PEOPLE: Enable the assignment of people to the related SKU items as the style item.

  • EGO_DEFAULT_STYLE_SUP_SITE_ORG: Enable the assignment of the related SKU items to the same supplier site organization combination as the style item.

  • EGO_GATHER_STATS: Specify the threshold value above which statistics collection is enabled.

  • EGP_ITEM_IMPORT_DEFAULT_CATG: Specify the catalog to be used for deriving the item class of items being imported.

  • EGI_PUBLICATION_ITEMS_PER_PAYLOAD: Determines the number of items to be used per payload in the publication concurrent program.

  • EGI_PUBLICATION_NUMBER_OF_PAYLOADS: Determines the number of parallel payloads to be used in the publication concurrent program.

  • EGO_VER_LINE_ACTIVATE_COUNT_PER_THREAD: Specify the number of versions or change order lines that become effective in a single thread.

Item Templates: Explained

Use item templates to assign attribute values during item creation in Oracle Fusion Product Hub.

An item template is a defined set of attribute values. When you apply an item template to an item in an organization, you insert the attribute values into the item definition. The defined attribute values from the item template automatically populate the appropriate item attribute fields.

Item templates are specific to an item class and an organization. The templates are inherited in a hierarchical item class and apply to all child item classes. Item templates can contain values for predefined attributes and user-defined attributes.

In addition to predefined item templates, you can create item templates, if required. You can also copy existing item templates to multiple organizations.

Create Item Templates

You can select a predefined item template to apply to an item. You can also create item templates in an organization. To create item templates, use the Manage Item Classes task available for the Product Management functional area in the Setup and Maintenance work area.

You can also edit or delete item templates as required.

Copy Item Templates

You can copy multiple existing item templates to multiple organizations simultaneously.

Copy the item templates as follows:

  1. In the Navigator, click Setup and Maintenance.

  2. On the Setup and Maintenance page, click the Product Management offering.

  3. On the Setup: Product Management page, click the Items functional area, and then click the Manage Item Classes task.

  4. Select the item class with the item template to copy, and click Edit.

  5. In the Templates and Formats tab of the Edit Item Class page, select the item templates to copy, and click Copy.

  6. In the Copy Templates dialog box, search and select the organizations where the templates are to be copied, and click OK. You can also search and select an organization hierarchy, in which case the template will be copied to all organizations in the hierarchy.

You can specify a default item template in an organization. To do so, select the Default check box for an item template in the Templates and Formats tab. The item template is used by default when you create an item.

Add Predefined Item Templates

If the predefined item templates do not automatically appear in an organization, you can add them manually.

Add the item templates as follows:

  1. In the Edit Item Class page, click Actions > Add Predefined Templates.

  2. In the Add Predefined Templates dialog box, search and select the organization in which to add the item templates, and click OK.

Define units of measure, unit of measure classes, and base units of measure for tracking, moving, storing, and counting items.

The following figure shows that the unit of measure class named 'Quantity' contains the units of measure: Box of 8, Box of 4, and Each. The unit of measure named Each is assigned as the base unit of measure.

Relationship between a unit of measure class and its
units of measure, one of which is defined as the base unit of measure

Units of Measure Classes

Units of measure classes represent groups of units of measure with similar characteristics such as area, weight, or volume.

Units of Measure

Units of measure are used by a variety of functions and transactions to express the quantity of items. Each unit of measure you define must belong to a unit of measure class.

Base Units of Measure

Each unit of measure class has a base unit of measure. The base unit of measure is used to perform conversions between units of measure in the class. The base unit of measure should be representative of the other units of measure in the class, and must be the smallest unit. For example, you could use CU (cubic feet) as the base unit of measure for a unit of measure class called Volume.

Item Lifecycle Phases are used as an indicator of the stage for an item within the lifecycle process. Each phase represents a set of tasks and deliverables that are required before promoting an item to the next phase.

Each item must have a lifecycle phase associated with it.

Four lifecycle phase types are predefined in the application: Design, Preproduction or Prototype, Production and Obsolete. You can use the predefined phase types to create new values for the lifecycle phases.

Companies may use different terms to describe the same item lifecycle phase. For example, the phases named Production and In Manufacturing both refer to the lifecycle phase during which an item can be used to build and ship products.

Lifecycle phases are associated with item classes. The items in an item class can be assigned to any of the lifecycle phases associated with that item class.

Note: The lifecycle phase of a child item is not automatically promoted when the parent item is promoted.

The effective date for items, in the Design lifecycle phase of a change order cannot be modified. If the item is in the 'Design' lifecycle phase, the change on the change order is effective on approval. If a future effective date is set for the affected object in a change order, a warning message appears with the following buttons:

  1. Continue: To continue with the future effective date.

  2. Edit: To cancel the current Save action, return to edit mode and correct the future effective date.

Note: The best practice is to make items Effective on Approval, if they are in the design lifecycle phase.

Before you create or import items, create lifecycle phases. Assign phases to the item class used to create the items. You can also assign them to a parent item class of the item class used to create the item. When an item is assigned to a lifecycle phase, that phase is visible as part of the item's attributes. In item structures, lifecycle phases are used to control specific processes.

Setting Up Item Lifecycle Phases: Explained

Item lifecycle phases represent the stages that an item or product goes through in its lifecycle. For example, for an item that can be used in production, the representative lifecycle phase is Production. Companies may use different terms to describe the same item lifecycle phase. For example, the phases named Production and In Manufacturing both refer to the lifecycle phase during which an item can be used to build and ship products.

Four lifecycle phase types are predefined in the application: Design, Obsolete, Preproduction or Prototype, and Production. You can use the predefined phase types to create new values for the lifecycle phases.

Lifecycle phases are associated with item classes, and the items in an item class can be assigned to any of the lifecycle phases associated with that item class. Before you create or import items, you must create lifecycle phases and assign those phases to item classes. When an item is assigned to a lifecycle phase, that phase is visible as part of the item's attributes. In item structures, lifecycle phases are used to control specific processes.

To set up lifecycle phases:

  1. In the Setup and Maintenance work area, select the Product Management offering.

  2. On the Setup: Product Management page, search for and click the Manage Lifecycle Phases task.

  3. Click the Create Lifecycle Phase button.

  4. Enter values in the following fields:

    1. Sequence

    2. Phase (name of lifecycle phase)

    3. Phase Code

    4. Select Phase Type

  5. Save and close the Manage Lifecycle Phases page.

  6. Associate the lifecycle phase with one or more item classes.

    1. In the Setup and Maintenance work area, select the Product Management offering.

    2. On the Setup: Product Management page, search for and click the Manage Default Item Class task.

    3. Click on the Lifecycle Phases Tab. This tab contains all lifecycle phases that are associated with the root item class.

    4. Associate the lifecycle phase to the root item class.

      1. Click the Lifecycle Phase tab.

      2. Click on Add Icon. The Search and Add: Lifecycle Phases dialog is displayed.

      3. Search for the Lifecycle Phase that you created.

      4. Click the OK button to associate the lifecycle phase with the item class.

  7. Click the Save and Close button to save the changes.

Manufacturer Parts and Manufacturers: Explained

Manufacturers must to be created before you may even create manufacturer parts produced by that manufacturer. Manufacturer parts (manufacturer items) can be related to any item designed or produced by your company. Any items on a structure may be sourced with parts from the approved manufacturers list (AML). Manufacturer parts are identified with manufacturer part numbers (MPNs).

Add a descriptive flexfield to the manufacturer part by using the Manage Trading Partner Item Descriptive Flexfields task (in the Setup and Maintenance work area and the Product Management offering). After you add the flexfield, deploy it.

Product Child Value Sets: Explained

The Manage Product Child Value Sets task uses the same page as the Manage Product Value Set task.

A child value set is used to define variants for stock-keeping units or SKUs. A SKU contains the common properties for an item. For example, a shirt can be produced with colors; white, red, yellow, and blue. The variant is used to represent the colors of the shirt.

You define child value sets as follows:

  • Create a value set with validation type of independent, for example All Colors.

  • Select the new value set in the Manage Product Value Sets results table, for example All Colors.

  • Click Manage Values, create several values, for example Blue, Red, Green, Yellow, and Black.

  • Create a value set with validation type of Subset and enter the first value set you created for the independent value set, for example: Summer Colors.

  • Select the value set Summer Colors in the Manage Product Value Set result table.

  • Click Manage Values and then click the Add icon. The dialog will show a list of values based on the value set named Summer colors. Select two of them. The value set Summer Colors is a child of All Colors.

The value set Summer Colors is a child of All Colors.

Attachment Categories: Explained

The basic tab of the Manage Item Class task is used to associate attachment categories to specific item classes.

The Attachment Categories region allows for the creation and management of attachment categories for the items created within the item class. To classify item attachments, associate attachment categories with item classes. Associated attachment categories are inherited down through the item class hierarchy.

Managing Attachment Security: Explained

The privileges for accessing the attachments of an item are by default inherited from business objects. You can further define the security of item attachments so that different users can have access to the same item but only have access to certain categories of attachments to that item. For example, there may be multiple categories of objects (such as specifications, drawings, or financial documents) attached to an item. There may be multiple job roles (such as buyer, design engineer, or accountant) who have access privileges to the item. Though they all may have the same access to the item itself, their access to the attached objects may need to be restricted by attachment category. By default, all job roles are granted access to the predefined attachment category Miscellaneous.

Any security policy defined for an attachment category is enforced on all business objects to which the attachment category is associated only if those business objects are enabled for attachment security.

To provide attachment security, perform the following tasks:

  • These tasks are not specific to attachment security, but are required prerequisites, to be performed once for each attachment category:

    • Create attachment categories.

    • Assign the attachment categories to item classes.

  • These tasks are specific to attachment security:

    • Define data security policies, which apply to attachment categories.

    • Enable data security policies for selected business objects.

Creating Attachment Categories

Attachment data security is implemented by using attachment categories. Attachment categories affect access to attachments through the item classes for the items being edited. Attachment data security can be assigned individually at the user level. It can also be assigned at the group level through job roles. You create attachment categories using the Manage Attachment Categories task in the Setup and Maintenance work area. You associate each attachment category with attachment entities that represent business objects: items, item revisions, catalogs, categories, and trading partner items.

Assigning Attachment Categories to Item Classes

You assign attachment categories to item classes using the Manage Item Classes task in the Setup and Maintenance work area. While editing an item class, you associate it with one or more attachment categories for which you want to provide security. This association is required only for attachment categories that are associated with attachment entities at the item level and item revision level. Since attachment categories are inherited down through the item class hierarchy, you can associate an attachment category with all item classes by assigning it to the Root Item Class.

Defining Data Security Policies

A data security policy is defined by a set of allowable actions on a database resource (such as an attachment category) for a job role. When that role is provisioned to a user, the user has access to the data defined by the policy. That is, an attachment data security policy defines who (defined as a job role) can perform what operations (such as read, update, or delete) on which set of attachment categories, according to a defined condition.

To define a data security policy for an attachment category:

  1. Sign in with the predefined IT Security Manager role.

  2. In the Setup and Maintenance work area, go to the following:

    • Offering: Product Management

    • Functional Area: Users and Security or Application Extensions

    • Task: Manage Data Security Policies

    The Security Console is automatically launched by the Manage Data Security Policies task. You can also open the Security Console directly from the Navigator.

  3. On the General subtab of the Administration tab of the Security Console, click Manage Database Resources.

    A database resource defines an instance of a data object. A data object is a table, view, or flexfield.

  4. On the Manage Database Resources and Policies page, search for the Display Name equal to Application Attachment Category. The category appears in the search results, with an Object Name of FND_DOCUMENT_CATEGORIES

    The data security policies defined for the selected database resource appear in the Policies Details region.

  5. In the Search Results region for the selected database resource, select Edit from the Actions menu.

  6. On the Condition tab of the Edit Data Security page, select Create from the Actions menu.

  7. In the Create Database Resource Condition dialog box, name the condition and specify the attachment categories in scope for the data security policy.

    The following table suggests values for an example condition:

    Field Value

    Name

    IPDrawings

    Display Name

    IPDrawings

    Description

    IP Drawings-Restricted to R&D

    Condition Type

    SQL predicate

    You can also specify the condition as a filter on a table or view.

    SQL Predicate

    category_name in ('Sketches')

    The SQL predicate consists of a query on the table or view named by the database resource (in this example, FND_DOCUMENT_CATEGORIES). The category name specified in the predicate must exactly match the name that you specified when you created the attachment category.

  8. On the Policy tab of the Edit Data Security page, select Create from the Actions menu.

  9. On the General Information tab of the Create Policy dialog box, specify the module. By default, the Module field is the module associated with the database resource for which you're creating the policy.

  10. On the Role tab of the Create Policy dialog box, select fscm in the Application list, then search for and select the role names to be assigned the new policy, such as Product Data Steward.

  11. On the Rule tab of the Create Policy dialog box, select Multiple Values in the Row Set field, then search for and select in the Condition field for the name of the condition that you created, such as the example here, Secured Attachments for Product Hub.

  12. On the Action tab of the Create Policy dialog box, move actions from the Available Actions list to the Selected Actions list to specify the actions that are applicable to the data secured on the database resource, which you want to grant to the roles you selected.

  13. On the Edit Data Security page, click Submit to update the database resource FND_DOCUMENT_CATEGORIES.

  14. On the Manage Database Resources and Policies page, click Done.

Enabling Attachment Data Security for Business Objects

You can enable and disable attachment security at the level of business objects. When you enable attachment security for a specific business object, then attachment security is enforced for every attachment category assigned to the business object. Note that, by default, all job roles are granted access to the predefined attachment category Miscellaneous.

To enable your data security policies on attachment categories:

  1. Sign in with the SCM implementation consultant role.

  2. In the Setup and Maintenance work area, go to the following:

    • Offering: Product Management

    • Functional Area: Application Extensions

    • Task: Manage Applications Core Attachment Entities

  3. On the Manage Attachment Entities page, you will search for and select each of the attachment entities that you previously assigned to the attachment categories that you created. Attachment entities represent business objects: items, item revisions, catalogs, categories, and trading partner items.

    Enter one of the following attachment entity names in the Entity Name field and click Search. The attachment category that you created should appear in the Attachment Categories region for the selected attachment entity.

    Business Object Attachment Association Level Attachment Entity Name

    Item Level

    ITEM_ENTITY

    Item Revision Level

    ITEM_REVISION_ENTITY

    Trading Partner Level

    EGP_TRADING_PARTNER_ITEMS

    Catalog Level

    CATALOG_ENTITY

    Category Level

    CATEGORY_ENTITY

  4. For each selected attachment entity in the search results, click Enable Security.

  5. When you have enabled security on all the desired attachment entities, click Save and Close.

  6. On the Setup page, search for and open the Run User and Roles Synchronization Process task from the Initial Users functional area.

  7. Submit the scheduled process to complete enabling security on attachments.

Operational Attributes Groups: Explained

Operational attributes determine the behavior of the item with respect to various applications outside of Oracle Fusion Product Hub, such as Oracle Fusion Purchasing or Oracle Fusion Inventory Management.

You choose the control level for operational attributes on the Manage Operation Attribute task in the Setup and Maintenance work area. For each listed operational attribute group, you select the control level for each of the group's attributes. You can control the operational attributes at the master organization level or at the organization level. You can define operational attributes as part of a new item request.

Some operational attributes for items are defined as key flexfields. Key flexfields allow a structured value for attribute to be captured. Key flexfields can capture a key, such as a part number, a job code, or an account code.

Examples of operational attributes with the attribute groups they belong to:

  • Inventory = Shelf Life Days

  • Order Management = Shippable

  • Purchasing = Negotiation Required

  • Receiving = Allow Substitute Receipts

Operational attributes are stored in the Items data table.

Attributes that exist for each instance of an item and the values for the attributes can be different.

For example:

  • The number of megabytes (MB) or gigabytes (GB) of e-mail storage on a digital subscriber line account.

  • The monogram text on a shirt pocket.

  • The color of a music player.

These attributes are defined at the item class and their attribute value is captured at the time of a transaction by downstream applications. The metadata values of these attributes are maintained at the item class. Order orchestration and order capture systems are two examples of downstream use. All transactional attributes must be associated with a value set.

The following metadata values can be defined for an attribute.

  • Required: Indicates whether the attribute value is required at the transaction.

  • Default Value: Indicates the default value of the attribute.

  • Value Set: Indicates the value set associated with the attribute.

  • Read Only: Indicates whether the attribute value is read only.

  • Hidden: Indicates whether the attribute is not shown.

  • Active: Indicates whether the attribute is active or inactive.

Transactional attributes are inherited across the item class hierarchy. The metadata is data-effective. Changes in the metadata will be reflected immediately at the item level. For example:

  • Any of the metadata of a transactional item attribute belonging to a specific domain, if modified in the child item class would break the inheritance. Any changes done at the parent item class for this transactional item attribute would not get inherited. Multiple records with same date range can exist if they belong to different domains. For example, the transactional item attribute Memory is associated with a Domain and order capture. Each of the domains may use a different set of metadata for its own purpose. Hence, for the same date range, two different records can exist. Only Start Dates for a transactional item attribute would be entered by a user. End date would be calculated automatically based on the next Date Effective record.

  • Users can modify (either Start Date and metadata) of a future effective record. Records with Starting date as Past cannot be modify or edited.

  • Only start dates can be set to permit updating by a user, and the end date of a record will automatically be pulled from the next record.

  • Any changes performed in the parent item class would be inherited by the child item class. If the corresponding record is modified in the child, then these changes will not be inherited.

Item pages provide a mechanism with which to configure the user interface.

Pages and Attribute Groups

Pages and attribute groups enable you to structure your data.

Benefits include:

  • You can combine and sequence attribute groups into pages.

  • There is no limit on the number of attribute groups associated with a page

  • Pages can be created at item class and are inherited down the item class hierarchy.

  • Attribute groups can be added to pages sequentially and based on this sequence, these attribute groups are shown in items

  • Attributes groups can be added for an inherited page at the child item class.

Functional Item pages are another type of special pages which are used to associate pages already created for use in the application. Application scope indicates the application which uses these pages and the usage indicates the specific use of the configured pages.

Data Quality

You can associate attributes for the purpose of standardization and matching, to be performed when items are created. You restrict the attributes to be processed for standardization or matching or both. Selecting Standardization allows the data quality engine to return the standardized values for these attributes. Matching allows the data quality engine to return any existing items which matches the value of these attributes and are potential duplicates.

Lifecycle Phases

Sequential lifecycle phases enable you to track and control the lifecycle phases of items. Each phase represents a set of tasks and deliverables that are required before promoting the item to the next phase. You can associate lifecycle phases to an item class which are created elsewhere. Lifecycle phases are inherited down the item class hierarchy and new lifecycle phases can be added to child item classes. For example, the lifecycle phases for a computer component item class might be: Concept, Prototype, Production, and Retirement.

Templates

Template is a defined set of attribute values used during item creation. When you apply a template to an item, you overlay or default-in the set of attribute values to the item definition. For example, every time users in a particular organization create new items, the attributes, as defined and approved by the organization appear in the appropriate fields. No user guesswork is required, and time is saved during the creation of items with a similar form, fit and function. Templates are created for each item class. Templates are specific to organization. Templates are inherited down the item class hierarchy. You can define both operational attributes and user defined attributes for each template.

Search and Display Format

Search formats provide a convenient way to save frequently used search criteria. Search formats created at item class will be available to all users. Search formats are always created in the context of item class. Display formats enable you to predefine search display views. You can use these views to look at different sets of item attributes that are returned by the search. Display formats created at item class will be available to all users. Display formats are always created in the context of item class.

Import Format

An import format identifies the base and user-defined attributes in an item class that are imported into the application using a spreadsheet. Consequently, when you import item business entities from a spreadsheet, the items are all imported into the particular item class defined in the import format. These imported item business entities inherit all the attribute groups defined for the specific item class. You cannot edit the layout of an import format once it is created.

Managing Operational Attribute Groups: Explained

You view operational attribute groups and define their control level for the attributes associated with them on the Manage Operational Attribute Groups page.

Attribute groups are listed in the Operational Attribute Groups table. Select an attribute group, and attributes associated with it are listed in a lower table.

In the Controlled At column, you define the organization level (master and child) at which selected attribute will be controlled.

Configuring Extensible Flexfields or User-Defined Attributes

User-Defined Item Attributes and Attribute Groups: Explained

User-defined attributes are based on extensible flexfields. You create an attribute group, which determines which attributes are used at runtime. Extensible flexfields or user-defined attributes are not available to customers who only license Product Model.

User defined attributes can have a static or dynamic list of valid values, or a range of values. Values for user-defined attributes are defined when you create the item and remain the same for the life cycle of the item.

User-defined attributes can be saved within attribute groups. You associate user-defined attributes with items by adding attribute groups to item classes.

For example, items that are part of the Small Gasoline Engines item class include the following specifications:

  • RPM

  • Power

  • Oil and fuel mixture

  • Weight

An attribute is defined for each of these specifications and these attributes are grouped together as the Engine Performance attribute group.

You create attribute groups on the Manage Attribute Groups page.

Note: For each user-defined attribute, you can optionally define validation rules to be applied when the user inputs data.

An attribute group can be single-row, multi-row, or variant.

Multi-row attribute groups enable you to associate multiple sets of attribute values with the same object instance. It gives you the ability to store multiple additional attributes that are dependent on the item, organization, attribute group, and a unique value within the attribute group.

For example, if your item is a book, you can create an attribute group named Chapters containing the following attributes:

  • Chapter number

  • Name

  • Number of pages

Multiple rows of Chapters can be associated with a book, while Name and Number of pages each require a single row. The attribute Chapter number is identified as Part of Unique Key

After you create the attribute group and attributes, perform the following tasks to complete the extensible flexfield setup:

  • Associate the attribute to the item class by using the Manage Item Class task

  • Deploy the attribute by using the Deploy Item Extensible Flexfields task

Tip: Sets of user defined attribute groups can be organized on a single page that can then be linked from the Specifications tab.

Create Extensible Flexfields or User-Defined Attributes: Procedure

You can create user-defined attributes or extensible flexfields from the Product Management offering in the Setup and Maintenance work area.

To create extensible flexfields, follow these steps:

  1. Create an attribute group.

  2. Create attributes within the group and a corresponding value set for each attribute.

  3. Deploy the item attributes.

  4. Associate the attribute group to the item class.

  5. Create pages and link attribute groups to pages.

  6. Deploy the item attributes.

You can now view the attribute groups in the item master record. Each of these steps are described in detail in separate topics.

For more information on creating extensible flexfield, see User Defined Attribute Groups and Attributes (Extensible Flexfields-EFFs) Setup White Paper (Doc ID 1992317.1) on My Oracle Support at https://support.oracle.com.

Create Item Attribute Groups and Attributes: Procedure

Create item attribute groups and attributes using the Manage Item Attribute Groups and Attributes task from the Setup and Maintenance work area.

Follow these steps to create item attribute groups:

  1. From the Setup and Maintenance work area, click the Product Management offering.

  2. Search and open the Manage Item Attribute Groups and Attributes task.

  3. On the Manage Attribute Groups page, create an attribute group and specify its context usage as item.

You can provide the attribute group with view or edit privileges, or both. For each user-defined attribute, you can optionally define validation rules to be applied when the user enters any data.

Note: When creating or editing attribute groups, or when creating new item classes associated with attribute groups, you must redeploy the extensible flexfield so that the attribute group is available in the application. To redeploy the flexfield, search for the flexfield code named EGO_ITEM_EFF in the Manage Attribute Groups page. In the search results, select the row that contains the flexfield code EGO_ITEM_EFF and click Deploy Flexfield. After the flexfield deployment is complete, click OK. Check the Deployment Status and Deployment Date columns to verify that the extensible flexfield deployed successfully on the current date.

Associate Attribute Groups and Pages to Item Classes: Procedure

Pages include a collection of attributes groups and attributes. You can add multiple attribute groups to a page and specify the display sequence of attribute groups. The page is then associated with an item class so that the attributes are visible on the item page. You can add multiple pages to an item class. Child classes inherit the attribute groups that are created for a parent item class. Additionally, you can create attribute groups specific to a child class.

In order to add an attribute group to a page, you must add the attribute group to the attribute groups tab in the item class. After you add the attribute group to the attribute groups tab, you must save the item class page.

Follow these steps to associate attribute groups and pages to an item class:

  1. Open the Manage Item Classes task from the Product Management offering in the Setup and Maintenance work area.

  2. Search for an item class in which you want to configure attribute groups.

    • In the Pages and Attributes tab, select Attribute Groups.

    • Create new attribute groups or modify the existing attribute groups, as required.

    • Save the item class page.

  3. In the Pages and Attributes tab, select Pages.

    • Select the page for which you want to configure attribute groups or create a new page.

    • Assign an attribute group to the page.

    • Specify the sequence of attribute groups.

  4. In the Pages and Attributes tab, select Functional Item Pages.

    • Select the functional area and save the item class page.

      Note: Functional item pages are mostly used by other products that consume extensible flexfields. For example, you can use the functional item pages to define extensible flexfields for Product Development..

You have associated the user-defined attribute groups (extensible flexfields) and pages to the item class. To view the user-defined attributes in the item page, you must deploy the extensible flexfields.

Deploy Item Flexfields: Explained

After you associate attribute groups and pages with an item class, you must deploy flexfields in order to to view the pages or attribute groups at runtime. The metadata that was created for the attribute group is not synchronized with the production data in Product Hub until the flexfield is deployed.

To deploy flexfields, select the Deploy Item Flexfields task in Setup and Maintenance work area. All flexfields for Product Hub are created within the flexfield code EGO_ITEM_EFF.

The deployment process is a CPU-intensive process, and is usually run at off-hour periods. You can choose from these deployment options:

  • Deploy Flexfield: Online incremental deployment. The deployment process begins immediately. Only the flexfield setup that changed is deployed.

  • Deploy Offline: Allows the deployment to be scheduled. The flexfields are deployed, one at a time, in the order that you deploy them to the queue. Because all Product Hub flexfields use the same flexfield code, the process deploys all of the attribute groups and attributes for all of the context usages at the same time. You cannot select individual attribute groups or item classes for deployment. You should choose to deploy offline if the flexfield changes impact 30 or more item classes.

  • Refresh and Deploy Offline: Use this option only if the first two options result in errors. You must log out and log back in to view the flexfield configuration on the item.

Item Attribute Groups and Attributes: Explained

Attribute groups are a logical group of attributes that are displayed in their own subregion of the user interface page at run time. Attribute groups can be either single-row or multiple-row. The selected behavior determines how the attributes appear in the user interface, as well as how they are used. Each attribute group is associated with one or more item classes.

To create an attribute group and attribute, you use Manage Item Attribute Groups and Attributes task (in the Setup and Maintenance work area under the Product Management offering). Create an attribute group and specify its context usage as item. You can provide the attribute group with view or edit privileges, or both. Choose the behavior of attribute as either single-row or multiple-row:

  • Single-row attribute group: Contains a collection of attributes that appear as separate fields in a region named for the attribute group. For example, a single-row attribute group named Processor contains the attributes appropriate for a processor. When these attribute groups are displayed in the user interface, the attribute fields for each group are arranged compactly within a region titled with the name of the attribute group. Attributes can be multiple data types.

  • Multiple-row attribute group: Attributes appear as columns in a table that represents the attribute group. Each row in the table is considered an attributes group. The attributes is collection of values specified by the columns in the table. The table appears in the user interface within a region titled with the attribute group name, such as MSRP Price. No other fields appear in the table. For example, a multiple-row attribute group named MSRP Price contains the attributes Country, MSRP, and Currency. Each row of the table describes an MSRP price, and is a value of the MSRP Price attribute group.

When you configure an attribute group, you can assign privileges. Using these privileges you control the user's ability to view or edit attributes in the following: view or edit Item tasks, change order impact analysis, and item structure report. To do this, under Context Usage select the view and edit privileges for the attribute group.

Within the attribute group, create an attribute and a value set. For example, create an attribute group named Cost and Compliance and within that add attribute named Material Cost. Using value sets, define the set of currencies applicable to item cost. After you create attribute group and attribute, perform the following in the Setup and Maintenance work area under the Product Management offering:

  • Associate the attribute to the item class by using Manage Item Class task

  • Deploy the attribute by using Deploy Item Flexfields task

Attributes in Item and Change Order Context: Explained

Generally, an item attribute can be edited through the item page or change order page. However you can restrict the attribute to be edited only through change order page, by using the Manage Item Rule Set task in the Setup and Maintenance work area. You can access this task from the Product Management offering and the Product Rules functional area. When creating the rule set, select the Association Type as Change order type.

Properties of attribute types vary according to the context. This table shows how the properties differ when you view them in the item page context and the change order context.

Attribute Type In Item Page Context In Change Order Context

Item attributes that are controlled by change orders

Editable only in the initial item revision and if the item is not yet assigned to a change order.

Editable.

When you create a rule set and define rules, you must set the Severity to Needs Approval. Any other setting will prevent users from viewing previous revisions of the item.

Item attributes that are not controlled by change orders

The following revisions are editable:

  • Revision that is already effective.

  • Revision that is scheduled to be effective in future.

All revisions display the value that is already effective; even previous revisions do not display revision-specific values.

Note: The previously effective revisions are not editable even during the execution of scheduling jobs.

Editable.

All revisions display revision-specific values.

Configure Attribute Groups for Product Development

For Product Development you can configure the attributes groups displayed as part of item, document, and change order. You specify the attribute groups for an item class and set the display sequence of attribute groups. This configuration affects attribute groups appearing on: item details page, create item dialog, change order affected object, change order impact analysis, and item structure report. Attribute groups created for an item class at a higher level are inherited to child classes. Additionally, you can create attribute groups specific to a child class.

Configure attribute groups as follows:

  1. In the Setup and Maintenance work area, go to the following:

    • Offering: Product Management

    • Functional Area: Items

    • Task: Manage Item Classes

  2. Search for an item class in which you want to configure attribute groups.

    • In the Pages and Attributes tab, select Attribute Groups.

    • Create new attribute groups or modify the existing attribute groups, as required.

  3. In the Pages and Attributes tab, select Pages.

    • Select the page for which you want to configure attribute groups or create a new page.

    • Assign an attribute group to the page. Also specify the sequence of attribute groups.

  4. In the Pages and Attributes tab, select Functional Item Pages.

    • Select the page you created or modified in the previous step and assign it to Product Development.

Note: You must deploy item flexfields after you create or modify attributes.

Create Data Privileges for Attribute Groups: Procedure

User defined attribute groups are supported by following tables at the following data levels:

Non-translatable tables:

  • Item Data Level - EGO_ITEM_EFF_B

  • Item Revision Data Level - EGO_ITEM_REVISION_EFF_B

  • Item Supplier Data Level - EGO_ITEM_SUPPLIER_EFF_B

Translatable tables:

  • Item Data Level Translatable - EGO_ITEM_EFF_VL

  • Item Revision Data Level Translatable - EGO_ITEM_REVISION_EFF_VL

  • Item Supplier Data Level Translatable - EGO_ITEM_SUPPLIER_EFF_VL

To create data privileges for attribute groups:

  1. Select Navigator> Security Console.

  2. Click Manage Database Resources.

  3. Enter the criteria to search for an object (or database resource) and click Search.

  4. Select object for which you want to create data privileges.

  5. From the Actions menu, select Edit.

    The Edit Data Security page appears.

  6. Click the Actions tab.

  7. Click Add to create a new data privilege.

  8. Enter the name of the data privilege, display name and description.

  9. Click Submit.

If the Manage Database Resources button is disabled, follow these instructions to enable the button:

  1. Select Navigator > Security Console.

  2. Search for the Security Management role (ORA_ASE_SECURITY_MANAGEMENT_DUTY) and edit that role.

  3. In Functional Security Policy, click Add Function Security Policy.

  4. Search for the Enable Database Resource Management privilege.

  5. Click Add Privilege to Role and click Next.

  6. In Summary and Impact Report, click Save.

Item classes are created at the root item class or under the parent item class and inherit values based on selections made when defining the item class.

The Manage Item Classes task, accessed through the Setup and Maintenance work area, is used to create and manage item classes, user defined attributes and data security.

You can define item classes in a hierarchy where the child levels indicate the sublevels or types of the parent item class. All items are created within an item class. The item class hierarchy can be used to control processes for some levels of the hierarchy.

You can also use item classes for classification purposes and in some cases, item creation may not be allowed. By optionally setting the Item Creation Allowed attribute to No, item creation under an item class can be prevented. However, a child item class of that item class can be set to allow for item creation.

For example, the following figure illustrates the Desktop item class as a child of the Computers item class and both are set to not allow item creation.

Figure showing a sample item class hierarchy with and
without item creation allowed.

The Green Desktop and the Gaming Desktop item classes are children of the Desktop item class and are set to allow item creation. Optionally, you can specify a date on which an item class becomes inactive. The inactive date of a child item class must not be a past data and must be earlier than the inactive date of a parent item class. Also, all children of a parent item class with an inactive date must be made inactive at the same time or earlier.

Note: Product Development does not support the versioning of item classes.

When setting up definition steps for a new item request at the item class, you can identify various item details as required, at each step. The definition of the entire entity or just specific attributes can set as required. This ensures that the item information required for a downstream step is defined and available for use.

You can define data security on an item class. All child items and item classes of the item class inherit the data security specified. Consider the following while creating and managing data security for item classes:

  • Item classes have a Public check box, which when selected indicates that all items in the item class are public. All new item classes, including its child items and child item classes, are public by default, and do not require data security to be set. To make a child item private, you must deselect the Public check box in the Data Security dialog box.

  • Depending on your settings for the Public check box, if a parent item class or a parent root item class is public, all new item classes created under it are public by default. Similarly, item classes created under a private item class or private root item class are private.

  • When a parent item class is made public or private, the child items and child item classes inherit the updated data security setting of the parent.

  • Private item classes cannot have child item classes that are public.

  • Public item classes can have child item classes that are private or public.

  • In case of private items, you can search for and view only the items you have access to.

  • For EFF Attribute Groups, you must set the data security for public and private item classes. The data security controls which EFF attribute groups are visible to specific user, user group, or organization.

  • You must set data security at the item class level to restrict access to user-defined attributes and values for public and private items.

You can control the creation, view, and update of items by associating a role with the item class and assigning it to a principal or group of users. Security allows a person or a group to have privileges to an item of an item class in each organization. This role is inherited. Therefore, if you have the privilege in a parent item class, you will automatically have the same privilege in the child item classes.

Item Class Descriptive Flexfields: Explained

User-defined attributes are used to configure additional attributes to support your organization's requirements. Descriptive flexfields appear in the user interface as additional information and can also appear in search results tables.

If you need to add only shallow and small numbers of individual data fields, consider using descriptive flexfields. For example, you may want to use a descriptive flexfield to capture different address fields (represented as context-sensitive segments) for different countries (represented as contexts). Address fields, though they may differ in number per country, are usually all at the same hierarchy level. For table layouts, if you have data that require a different context segment value per row, and that context segment value has different respective context-sensitive segments (in terms of type and number), then you must use descriptive flexfields, not extensible flexfields.

You cannot group attributes using descriptive flexfields. For example, if you wanted to define a maximum CPU speed and a minimum CPU Speed for an item, you have to specify an attribute called Maximum CPU Speed and another called Minimum CPU Speed. You couldn't have a grouping called CPU Speed and have two child attributes called Maximum and Minimum.

With descriptive flexfields, you can define many contexts for an object but you can display only one context at a time. For example if the context value is a State, then the context segment called "Capital" would have different values depending on the value of the context. If the descriptive flexfields have only one context, the context selector can be hidden in the user interface. You can define descriptive flexfields on items, structures, catalogs, categories, new item requests, and change orders.

Default Item Class: Explained

For non-Product Hub customers, the Manage Default Item Class task (in the Setup and Maintenance work area under the Product Management offering) is used, since these customers cannot create additional item classes nor can they create user defined attributes such as EFFs. An exception to this rule is that Product Development customers can create additional item classes and EFFs. The Manage Default Item Class task launches an edit page for the Root Item Class.

The Manage Default Item Class task has three tabs:

  • Basic: Item Class descriptive flexfields and attachment categories are defined on this tab.

  • Item Management: Item number generation method is defined using this tab.

  • Lifecycle Phases: The lifecycle phases that the items assigned to this item class will use are defined on this tab.

  • Item Templates: The item templates that are used to create items are defined on this tab.

Item Statuses: Explained

In the Item Status table, select a status code to display the associated attribute groups and attributes as well as control information.

Item statuses are used to define the state an item is in and based on the state, the default values for item operational attributes.

Item statuses are seeded; the values are Active and Inactive. You can create, edit or delete item statuses on the Manage Item Statuses page.

Operational attribute groups and attributes corresponding to the selected item status are displayed in the Details section.

Whenever the status is applied to the item, the value of the attribute may change. Select the usage that corresponds to how the attribute value will change based on the item status value:

  • Defaulted - Allows you to override the value during the import and update of an item.

  • Inherited - Sets the values of the item status attributes when the status value changes. You cannot override the value.

  • None -The item status attribute values will not be changed.

Any change made to an item status is not applied automatically to existing items. The change will be applied when the item status value is changed while editing an item.

Status attributes for each item status control the actions that you can perform on the item. Some of the status attributes are: Build In WIP, Customer Orders Enabled and Internal Orders Enabled.

The Controlled at field is not editable and is populated from the value set on the Manage Attribute Groups page.

Setting Up Data Security for Item Classes: Explained

Before you can create or view items in the Product Information Management work area, you must define data security for items. Define data security in the item class for each role/organization pairing and user/organization pairing.

Initially, you must define data security in the root item class and the master organization for both the Product Manager and the Product Data Steward roles. If you created an implementation user to create items in the Product Information work area, then you must assign the Product Manager and Product Data Steward roles to that user, and you must assign that user to the master organization. (Assign the appropriate role or roles and organizations to any additional users you create to control what each user is allowed to do in the application.) You can assign all of the actions to the Product Manager and Product Data Steward role for the master organization to allow all users with these roles to have complete access to item data.

The following table describes the specific actions that you must assign to both the Product Manager and the Product Data Steward roles for the root item class and the master organization you created. (When you create additional organizations, you must define data security for each organization that these roles are assigned to.)

Actions Description

Maintain Item Asset Maintenance Group

Allows access to edit item asset management specifications. Does not encompass view privilege.

Maintain Item Attribute

Allows access to edit item user defined attribute specifications. Does not encompass view privilege.

Maintain Item Basic

Allows access to edit item basic information including attachments, organizations, suppliers, relationships, and other related information.

Maintain Item Costing Group

Allows access to edit item costing specifications. Does not encompass view privilege.

Maintain Item General Planning Group

Allows access to edit item general planning specifications. Does not encompass view privilege.

Maintain Item Inventory Group

Allows access to edit item inventory specifications. Does not encompass view privilege.

Maintain Item Invoicing Group

Allows access to edit item invoicing specifications. Does not encompass view privilege.

Maintain Item Lead Times Group

Allows access to edit item lead times specifications. Does not encompass view privilege.

Maintain Item MRP And MPS Group

Allows access to edit item MRP and MPS specifications. Does not encompass view privilege.

Maintain Item Order Management Group

Allows access to edit item order management specifications. Does not encompass view privilege.

Maintain Item Pack

Allows access to edit item packs. Does not encompass view privilege.

Maintain Item People

Allows management of user access to items in the enterprise. Does not encompass view privilege.

Maintain Item Physical Group

Allows access to edit item physical specifications. Does not encompass view privilege.

Maintain Item Primary Group

Allows access to edit item primary specifications. Does not encompass view privilege.

Maintain Item Process Manufacturing Group

Allows access to edit item process manufacturing specifications. Does not encompass view privilege.

Maintain Item Purchasing Group

Allows access to edit item purchasing specifications. Does not encompass view privilege.

Maintain Item Receiving Group

Allows access to edit item receiving specifications. Does not encompass view privilege.

Maintain Item Revision

Allows access to create and manage item revisions. Does not encompass view privilege.

Maintain Item Service Group

Allows access to edit item service specifications. Does not encompass view privilege.

Maintain Item Structure

Allows access to create and manage item structures. Does not encompass view privilege.

Maintain Item Structure Group

Allows access to edit item structure specifications. Does not encompass view privilege.

Maintain Item Web Option Group

Allows access to edit item web option specifications. Does not encompass view privilege.

Maintain Item Work In Process Group

Allows access to edit item work in process specifications. Does not encompass view privilege.

View Item Attribute

Allows access to view item user-defined attribute specifications.

View Item Basic

Allows access to query and view item basic information including attributes, attachments, organizations, suppliers, and relationships.

View Item Pack

Allows access to view item packs.

View Item Structure

Allows access to view item structures.

Create Item Class Item

Allows access to create items within an item class.

Read

Read

Update

Update

For initial start up, define the data security at the root item class level and define the complete set of actions for the person or groups. Data security defined at the root item class level is inherited by all new item classes created. To define data security for an item class and organization:

  1. In your implementation project, search for the Define Advanced Items task list.

  2. Click the Go to Task icon for the Manage Item Classes task.

  3. Select the Root Item Class row and click on the Edit icon.

  4. Click on the Security tab. The Item Class People and Actions table are initially empty.

  5. To add a new row, click the Add icon in the Item Class People table.

  6. In the Group field, choose Principal.

  7. In the Name column, click on the Search link.

  8. Enter Product for the role name and click on the Search button. The results show all combinations of the roles Product Manager or Product Data Steward and the organizations to which they were assigned. In addition, two of the rows have no organization assignments.

  9. Select the Product Data Steward row without an organization assignment and click the OK button.

  10. Select the organization that you created in the Creating Item Organizations: Explained section of this document.

  11. Define the actions that the Product Data Steward and Product Manager Roles can perform by adding actions to the Actions table.

    1. Click on the Add icon to launch the Select and Add Action dialog.

    2. Perform a search for each of the following terms, select all of the returned actions, then click apply:

      • Maintain

      • View

      • Create

    3. After selecting all of the appropriate actions, click OK to close the dialog.

  12. Repeat this process to define item class security for the Product Manager.

  13. Save your changes.

Managing Item Types: Explained

Item types are managed using the Manage Item Types task in the Setup and Maintenance work area (under the Product Management offering).

There are 32 seeded item types and you can edit them or create additional item types.

Item types are date-enabled and are made active or inactive by adjusting the Start Date and End Date.

To benefit from the use of item types, you must enable them by selecting the Enable check box.

Cross-Reference Types: Explained

Cross-references provide the functionality to map additional information about an item in the form of a value and cross-reference type. For example, the cross-reference can map between an item and an old part number, where the value is the value for the old part number and the type is Old Part Number. Cross-reference types are part of item relationships where the item relationship type is cross-reference. There are no values seeded for cross-reference types. You define the values using the Manage Cross Reference Types task. Cross-reference types are date-enabled and can be made active or inactive by adjusting the values of the start date and end date. To use the item relationship for cross-reference, you must enable cross-reference types by checking the Enable check box.

Item Descriptive Flexfields: Explained

You can use descriptive flexfields to capture additional information about items beyond what is provided by the predefined set of operational attributes in Oracle Fusion Product Hub.

Item Descriptive Flexfields

If you are not using Oracle Fusion Product Hub, then you cannot create user-defined attribute groups and attributes. However you can use descriptive flexfields associated at Item level to create fields to capture information about items. Like other descriptive flexfields, item descriptive flexfields have context segments and context-sensitive segments whose values are validated on entry by value sets. You can define the value sets to control what values users can enter in a descriptive flexfield segment. Examples of information that you might capture are size and volumetric weight.

Manage this flexfield type by using the Manage Item Descriptive Flexfields task available in the Setup and Maintenance work area.

Item Revision Descriptive Flexfields

Use descriptive flexfields associated at Item Revision level to capture item revision information whose values may differ between revisions of the same item.

Manage this flexfield type by using the Manage Item Revision Descriptive Flexfields task available in the Setup and Maintenance work area.

Item Relationship Descriptive Flexfields

When defining descriptive flexfields associated with item relationships, you must use certain prefixes when naming the context segments, in order for the segments to be displayed for the respective relationships.

The prefixes required for naming the context segments are listed in the following table, with their corresponding item relationship types. For example, if you define an item relationship descriptive flexfield with a context segment named RELATED_RELATIONSHIP_ATTRIBUTES, then the value segments of this context will be displayed for Related Item Relationships when users conduct transactions in that context. For another example, when users navigate to a UI of a particular object, such as a Competitor Item, they see the contexts whose internal name has the prefix COMP.

Relationship Type Prefix for Context Segment

Competitor Item Relationship

COMP

Customer Item Relationship

CUST

Item Cross-reference Relationship

XREF

GTIN Relationship

GTIN

Manufacturer Part Number Relationship

MFG

Related Item Relationship

RELATED

Source System Item Relationship

SYS

Manage this flexfield type by using the Manage Item Relationship Descriptive Flexfields task available in the Setup and Maintenance work area.

Trading Partner Item Descriptive Flexfields

When defining descriptive flexfields associated with trading partner items, you must use certain prefixes when naming the context segments, in order for the segments to be displayed for the respective trading partner type.

The prefixes required for naming the context segments are listed in the following table, with their corresponding trading partner types. For example, if you define a trading partner item descriptive flexfield with a context segment named COMP_TPI_ATTRIBUTES, then the value segments of this context will be displayed for Competitor Item when users conduct transactions in that context.

Trading Partner Type Prefix for Context Segment

Competitor Item

COMP

Customer Item

CUST

Manufacturer Item

MFG

Manage this flexfield type by using the Manage Trading Partner Item Descriptive Flexfields task available in the Setup and Maintenance work area.

Import Items: Explained

Item Management provides the ability to create and management item data through two methods: the Product Information Management work area and a process to import Items from files located in a specific folder in Oracle Universal Content Management system.

The objects listed below are supported through both methods:

  • Items

  • Item revisions

  • Item category assignments

  • Item associations*

  • Item relationships

  • Item flexfields *

  • Item translatable flexfields*

  • Item revision flexfields*

  • Item revision translatable flexfields*

  • Item supplier flexfields*

  • Item translatable supplier flexfields*

  • Item style variant attribute value Sets

  • Trading partner items

Note: You must license Oracle Fusion Product Hub to use certain flexfields.

The following is an overview of the item import process:

  1. Download the item import template file from the File-Based Data Import for Oracle Supply Chain Management Cloud.

  2. Enter data in tabs within the item import template file.

  3. Generate CSV (ZIP file).

  4. Upload to Oracle Universal Content Management.

  5. Move the data into Item Management interface tables.

  6. Import data to Item Management product tables.

Related Item Subtypes: Explained

A related item is an item relationship between two existing items. How the two items are related is defined by a subtype.

Multiple subtypes for related items are seeded, and you can define additional subtypes using the Manage Related Item Subtypes task.

Seeded values are:

  • Accessories

  • Collateral

  • Complimentary

  • Conflict

  • Cross-Sell

  • Fulfillment

  • Impact

  • Mandatory Change

  • Merge

  • Migration

  • Optional Change

  • Option charge

  • Prerequisite

  • Promotional upgrade

  • Repair to

  • Service

  • Split

  • Substitute Supersede

  • Upsell

  • Warranty

Item Revision Descriptive Flexfields: Explained

Use item revision descriptive flexfields to capture item revision information whose values may differ between revisions of the same item.

Manage this flexfield type by using the Manage Item Revision Descriptive Flexfields task in the Setup and Maintenance work area.

Trading Partner Item Descriptive Flexfields: Explained

When defining descriptive flexfields associated with trading partner items, you must use certain prefixes when naming the context segments, in order for the segments to be displayed for the respective trading partner type.

The prefixes required for naming the context segments are listed in the following table, with their corresponding trading partner types. For example, if you define a trading partner item descriptive flexfield with a context segment named COMP_TPI_ATTRIBUTES, then the value segments of this context will be displayed for Competitor Item when users conduct transactions in that context.

Trading Partner Type Prefix for Context Segment

Competitor Item

COMP

Customer Item

CUST

Manufacturer Item

MFG

Supplier Item

SUPP

Manage this flexfield type by using the Manage Trading Partner Item Descriptive Flexfields task in the Setup and Maintenance work area.

Item Keyword Search: Explained

Keyword search allows you to quickly find items that you are looking for. Before you can use the Keyword search in the Product Information Management work area, you must build the index.

Use the Manage Item Keyword Search task in the Setup and Maintenance work area to select the attributes that will be used in the indexing process. After you have selected the attributes, choose from these indexing options:

  • Index Now: This action allows you to launch the indexing process using the current configuration of attributes, organizations, and languages. The organizations and languages are displayed in the section below the attribute selection table.

  • Schedule Index: This action provides you the option of scheduling the indexing process. You don't get the option of adding additional organizations, nor languages as part of the parameters displayed.

Note: Only users or groups associated with the privilege, Manage Index Delta Organizations (EGP_MANAGE_INDEX_DELTA_ORGS), will be able to see and edit the data in the Organizations and Languages tab in the Manage Item Keyword Search Attributes page.

The Index Change Status field displays one of the following statuses:

  • Complete: The index has run and completed successfully, the Last Indexed value indicates the date and time the index completed.

  • Pending: Changes have been made to the index configurations and index needs to be run.

  • Running: The index program is currently running.

  • Scheduled: The index program is scheduled to run.

The status in the UI is displayed for each attribute. One or more attributes can be part of a scheduled process. If you cancel a scheduled process, then some of the attributes may still show the status as Addition in Progress. By the time you cancel the scheduled process, some of the attributes may already be included in the index.

Item Keyword Search Scheduled Process Actions: Explained

The Item Keyword Search scheduled process is used to create and maintain the Item Keyword Search index.

You can use the following actions for the scheduled process:

  • CREATE: Creates the index, if not present. This will index all items in the instance.

  • DROP: Drops the index. Use this action only when the index is damaged and needs to be indexed from the beginning.

  • UPDATE: This action checks if any additions or deletions have been made to the list of keyword attributes using the Manage Keyword Attributes task. This action will re-index either all rows or the affected rows, depending on whether predefined attributes have been added or deleted.

  • REBUILD: This will re-index all rows. Use this action only when the index is damaged and needs to be rebuilt because it takes a very long time to complete.

  • SYNC: This will process the index changes in the queue.

    Note: After adding a new language to the Keyword Search index, you must run the Item Keyword Search scheduled process with the SYNC action. If you don't run the schedule process with the SYNC option, you don't get an index search result. The scheduled process can't find the items because they are not yet indexed.

You do not need to enter values for any of the remaining fields on the page.

During an upgrade, if you have scheduled this scheduled process before the upgrade, you must cancel the scheduled process and resubmit it after the upgrade.

Implicit publication enables you to set up a periodic schedule to automatically publish objects to each spoke system. To set up the implicit publication of objects from Oracle Fusion Product Hub to external systems, the following are required:

  • Define the publication options for a spoke system.

  • Define the schedule and parameters for the scheduled process.

  • Define profile options.

  • Access the payload generated by the publication scheduled process.

  • Configure the Service Oriented Architecture composite to publish to the external spoke system.

Spoke System Publishing Options

Use the Manage Spoke Systems task in the Setup and Maintenance work area to manage import and publication options for each spoke system.

The following table list publication criteria and available options for each value.

Publication Criteria Options

Objects

  • Items

  • Item classes

  • Item catalogs

  • Trading partner items

Item entities

  • Attributes

    Selected by default, and including:

    • Item main attributes

    • Operational attributes

  • Attachments of type URL

  • Supplier site organizations association

  • Item category assignments

  • Pack hierarchies

  • Item relationships:

    • Global trade item number (GTIN)

    • Related items

    • Cross-references

  • Structures:

    • All

    • Primary

  • All pack items

    All items with a pack type, regardless of membership in a hierarchy, are published whenever a change to the pack occurs.

  • Item selection rules

    Add rules that select certain items.

  • Item validation rules

    Select an existing validation rule set.

Item class entities

  • Item class attachment categories

  • Item class attribute groups

  • Item class descriptive flexfields

  • Data quality attributes

  • Product hub portal attributes groups

  • Item class pages

  • Item class lifecycle phases

  • Item class page attribute group

  • Item class translation content

  • Item overview attribute groups

  • Supplier attribute groups

  • Transactional attributes

  • Transactional attributes translation content

Select the item classes in the hierarchy to include for publication.

Item catalog entities

  • Catalog translation content

  • Catalog attachments

  • Catalog descriptive flexfields

  • Categories

  • Category translation content

  • Category attachments

  • Category descriptive flexfields

  • Category item assignments

Search for, and select, the catalogs to be published. The publication will include the entire hierarchy for the catalogs you select.

Trading partner item entities

  • Trading partner items for customers

  • Trading partner items for suppliers

  • Trading partner items for manufacturers

  • Trading partner items for competitors

  • Item relationships for related items

  • Trading partner item attachment

  • Trading partner items descriptive flexfields

Select the trading partner items to include for publication.

Profile Options for Large Volume Publications

If you are publishing over 1,000 items or records, you may want to consider changing the values for the following profile options in the Setup and Maintenance work area.

Profile Option Purpose

Number of Items per Payload for Publication

This profile option determines the number of items to be used per payload in the publication process. The seeded value is 1,000.

Number of Parallel Payloads for Publication

This profile option determines the number of parallel payloads to be used in the publication process. The seeded value is 100.

Note: The profile option values are defined with the Manage Advanced Profile Values task in the Setup and Maintenance work area.

You can view the errors identified during publication from the log files of the scheduled process.

Access the Payload

Access the XML payload from the Enterprise Manager or the Unified Content Manager folder. The folder PIM is predefined in the Contribution Folders folder.

Configure Service Oriented Architecture Composite

Because the transformation of data and the publication target must be configured separately for each spoke system to which publication is to be supported, the default composite shipped with Service Oriented Architecture Composite does not actually complete the publication process. For more information, see the Oracle Fusion Middleware Managing and Monitoring Processes with Oracle Business Process Management guide and the Oracle Cloud Administering Oracle SOA Suite and Oracle Business Process Management Suite guide.

You initiate the publication process by launching the Product Hub Publication scheduled process. The scheduled process request first populates the publication database tables with the primary key values of all the data that needs to be published and then initiates a business event. The Publication Service Oriented Architecture Composite is launched as a result of this business event.

From the Scheduled Processes work area, create and submit the scheduled process named Product Hub Publication. This process publishes the objects of each spoke system. Select the spoke system, the objects to be published, and a date.

The parameters required for running the Product Hub Publication scheduled process are listed in this table.

Scheduled Process Parameters Definition

Spoke System

Name of the external spoke system to which item, item class, or catalog information is to be published.

Publish Items

Indicates whether items are to be published.

Publish Item Classes

Indicates whether item classes are to be published.

Publish Catalogs

Indicates whether catalogs are to be published.

Publish Trading Partner Items

Indicates whether to publish trading partner items.

Publish All Records

Indicate whether to publish all records of the objects.

Publish from Date

Indicates to publish records of objects from a start date.

Publish to Date

Indicate to publish records of objects to an end date.

Folder Location

Unified Content Manager folder location to save the output xml file.

Process Sequentially

Indicates the publication jobs to run sequentially when there are more than one jobs. Otherwise, the jobs will run in parallel.

Generate XSD

Indicate whether to generate the schema XSD.

Publication processes can be both recurring or one-time event. Let's say you're setting up an integration to a legacy application, where you are publishing new items that are created in the Product Hub application. You would want to set up the scheduled publication job to run each night.

The scheduling frequency is based on the integration requirements and the availability of the applications that integrate with Product Hub to receive and process the data. For example, you may have a situation where the Product Hub is feeding new item information to an ERP application and the ERP application only has a small window in which it can be updated.

Managing Document Classes: Explained

These are the steps for setting up and managing Document classes.

Create Root Document Class

  • Use the Manage Item Classes setup task. This is found in Product Management > Items > Manage Item Classes.

  • In the Create Item Class dialog, create a subclass of the root item class. You may want to call it Root Document Class, or a name that parallels the name of your root item class.

Assign Root Document Class

  • Use Setup in the Product Development workspace.

  • Enable Document Management.

  • Designate your root document class.

Add Document Subclass

  • Use the Manage Item Classes setup task to add subclass to the root document class.

  • Users will be able to select from those subclass when creating a document object.

FAQS for Defining Items

The item class hierarchy provides a logical classification and grouping of similar products, and also acts as a template for product definition by enabling the association and inheritance of data elements and policies that are shared by products.

To create an item class, select a parent item class on the Item Class Search Results page and select Create. Provide the required information, and optionally include additional details, such as attribute groups, pages, templates, and search and display formats.

Create a template for item class and then define the Overview and Specification tabs of the item class template.

What's lifecycle validation?

Lifecycle validation enforces compatible lifecycle phases between parent and component items in an item structure, at the structure name level. For example, an item in the Design lifecycle phase can only have component items that are in the same lifecycle phase or the next phase. The only exception is for items in the Obsolete lifecycle phase, because this is considered the end of life for an item. Items in the Obsolete lifecycle phase cannot be added to a new structure.

The lifecycle phases for a computer component lifecycle might be:

  • Concept

  • Design

  • Prototype

  • Production

  • Retirement (Obsolete)

What number generation methods are available?

The available number generation methods are: Sequence Generated, User-Defined, and Rules.

How can I promote an item's lifecycle phase?

You can change an item's lifecycle phase based on the lifecycle of the item. Phases associated at the item class will be shown and depending on your business process, can be promoted.

There are business rules associated with these changes. Checks are performed for component's lifecycle phase and prompt an error message if there are incompatibilities.

How can I demote an item's lifecycle phase?

You change an item's lifecycle phase based on the life cycle of the item. Phases associated at the item class will be shown and depending on your business process, can be demoted. Changing an item's lifecycle phase also changes not only its lifecycle phase but also all the components present in the item's structure, which based on the structure setup.

What's the difference between lifecycle phase types and lifecycle phases?

Lifecycle phase types are seeded and describe the type of lifecycle phase. They are Design, Obsolete, Preproduction or Prototype, and Production.

Lifecycle phases must be created by the user by selecting one of the seeded lifecycle phase types.

What does the All Values Required field, in the Definition Workflow Details table on the Item Management tab of the Edit Item Class task mean?

When checked, all attributes of the associated entity specified on that row must be populated by the assignee in order to for the workflow to proceed to the next step of the definition workflow. For example, if the associated entity is Physical Attributes, then all attributes in the attribute group must be populated by the assignee in the New Item Request workflow step.

Can mandatory definitions be inherited?

If the association is inherited and All Values Required is not checked, then inherited-required attributes from parent will be displayed in read only format under selected list and you can move additional required attributes from available list to selected list.

If the association is inherited and All Values Required is checked in parent, then All Values Required is read only and inherited attributes will be placed under selected list also in read only format.