3Items and Documents

This chapter contains the following:

Setup Tasks to Define Items

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 within a 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 the Universal Content Management system, you use the Load Interface File for Import scheduled process to move the data from the Universal Content Management 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

Profile options manage configuration data centrally and influence the behavior of applications. The profile options have a default value, which you can use for initial installations.

Review these profile options and determine if you want to change the default values.

Profile Options Description

EGP_DISPLAY_IMAGES

Specifies if images are displayed in the search results table in the Manage Items page.

EGP_UPDATEABLE_ITEM

By default, you can't change the item number after you have created the item. However, if you set this option to Yes, you can update items even after they're created.

EGP_ITEM_IMPORT_ITEMS_PER_THREAD

When you import items, the application creates multiple threads of operation to process the imported items. This profile option controls how many items the application can process per thread. It's a technical option used to optimize the item import performance. The default value is 20. Contact Oracle Support to determine the optimal value before you make a change.

EGP_ITEM_IMPORT_NUMBER_OF_THREADS

Determines the number of parallel threads of execution used when the item import process is run. The default value is 12. You can use these criteria to configure the profile option:

  • Number of service servers configured on your instance: You can get this information by contacting Oracle Support.

  • Other active processes: Other application processes that may be concurrently running on this server and utilizing the same service servers.

If the item import is the only process running on the instance, you can configure the number of threads up to 16 times the number of service servers. If there are other processes likely to be running concurrently, reduce the number of threads proportionally.

This profile option works in conjunction with the EGP_ITEM_IMPORT_ITEMS_PER_THREAD profile option.

Access the Profile Options

In the Setup and Maintenance work area, use this navigation to access and manage the item profile options:

  • Offering: Product Management

  • Functional Area: Items

  • Task: Manage Item Profile Option

Advanced Item Profile Options

Profile options manage configuration data centrally and influence the behavior of applications. You can access the advanced profile options only if you have licensed Oracle Fusion Product Hub and have the privileges of a product data steward.

The profile options have a default value, which you can use for initial installations. Review these profile options and determine if you want to change the default values.

Profile Options Description

EGO_ASSIGN_PACK_ORG

Assigns all child items in the pack to the same organization as the parent pack item.

EGO_ASSIGN_PACK_SUP_SITE_ORG

Assigns all child items in the pack to the same supplier-site- organization combination as the parent pack item.

EGO_DEFAULT_STYLE_CATALOG

Enables the assignment of the related SKU items to the same catalog as the style item.

EGO_DEFAULT_STYLE_ITEM__ORG

Enables the assignment of the related SKU items to the same organization as the style item.

EGO_DEFAULT_STYLE_PEOPLE

Enables the assignment of people to the related SKU items as the style item.

EGO_DEFAULT_STYLE_SUP_SITE_ORG

Enables the assignment of the related SKU items to the same supplier-site-organization combination as the style item.

EGP_ITEM_IMPORT_DEFAULT_CATG

Specifies the catalog that you want to use for deriving the item class of the imported items.

EGI_PUBLICATION_ITEMS_PER_PAYLOAD

Determines the number of items that you want to publish per payload in the publication concurrent program.

EGI_PUBLICATION_NUMBER_OF_PAYLOADS

Determines the number of parallel payloads that you want to publish in the publication concurrent program.

EGO_VER_LINE_ACTIVATE_COUNT_PER_THREAD

Specifies the number of versions or change order lines that become effective in a single thread.

EGI_ALLOW_ITEM_CREATE_DQ_MATCH_FOUND

Determines whether the application can create an item when it finds a matching item during the data quality check. The default value is Yes.

Access Advanced Item Profile Options

In the Setup and Maintenance work area, use this navigation to access and manage the advanced item profile options:

  • Offering: Product Management

  • Functional Area: Items

  • Task: Manage Advanced Item Profile Options

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 Setup and Maintenance work area, select the following:

    • Offering: Product Management

    • Functional Area: Items

    • Task: Manage Item Classes

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

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

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

Units of measure, unit of measure classes, and base units of measure are used for tracking, moving, storing, and counting items.

The following graphic 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 cubic inches 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.

Set Up Item Lifecycle Phases

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, use the Manage Lifecycle Phases task:

    • Offering: Product Management

    • Functional Area:

    • Task: Manage Lifecycle Phases

  2. Click the Create Lifecycle Phase button.

  3. Enter values in the following fields:

    1. Sequence

    2. Phase (name of lifecycle phase)

    3. Phase Code

    4. Select Phase Type

  4. Save and close the Manage Lifecycle Phases page.

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

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

Considerations for Manufacturer Parts and Manufacturers

Manufacturers must 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.

Define Product Child Value Sets

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 sizes; small, medium, and large. The variant is used to represent the sizes of the shirt.

You define child value sets as follows:

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

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

  • Click Manage Values, create several values, for example Small, Medium, Large, Extra Large.

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

  • Select the value set Plus Sizes 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 Plus Sizes. Select two of them. The value set Plus Sizes is a child of All Sizes.

Attachment Categories

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.

Manage Attachment Security

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 aren't 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 Controls

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. Operational attributes are stored in the Items data table.

In the Setup and Maintenance work area, use this navigation to specify the control level for operational attributes:

  • Offering: Product Management

  • Functional Area: Items

  • Task: Manage Operational Attributes Groups

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.

You can also control the decimal precision of all numeric operational attribute values. All numeric item-operational attributes have the maximum decimal digits precision value of three by default. You can specify the precision up to three digits after the decimal point. For example, 8.724 is a valid item operational value, but 8.7241 is an invalid value.

Note: You can't change the default value for the decimal precision in the Mass Updates page.

You can define some item operational attributes as key flexfields. Key flexfields allow you to capture a structured value for an attribute. Some examples of key flexfields are part number, job code, and 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

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 size of a shirt.

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.

How You Manage Operational Attribute Groups

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.

Configure Extensible Flexfields or User-Defined Attributes

User-Defined Item Attributes and Attribute Groups

User-defined attributes are based on extensible flexfields. Create an attribute group to determine 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. You can define the values for user-defined attributes when you create the item and the values remain the same for the life cycle of the item.

You can save user-defined attributes within attribute groups. You can 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

You can define an attribute for each of these specifications and then group these attributes 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 a single row, multirow, or variant.

Multirow 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 that contain the following attributes:

  • Chapter number

  • Name

  • Number of pages

You can associate multiple rows of Chapters with a book, while Name and Number of pages require a single row each. The Chapter number attribute is identified as a part of the unique key.

After you create the attribute group and attributes, perform these 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

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

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. In the Setup and Maintenance work area, use the Manage Item Attribute Groups and Attributes task:

    • Offering: Product Management

    • Functional Area: Items

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

Redeploy Extensible Flexfield

Redeploy the extensible flexfield so that the attribute group is available in the application.

  1. Search for the flexfield code named EGO_ITEM_EFF in the Manage Attribute Groups page.

  2. In the search results, select the row that contains the flexfield code EGO_ITEM_EFF and click Deploy Flexfield.

  3. After the deployment is complete, 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

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

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

To deploy item flexfields:

  1. In the Setup and Maintenance work area, use the Deploy Item Extensible Flexfields task:

    • Offering: Product Management

    • Functional Area: Items

    • Task: Deploy Item Extensible Flexfields

  2. Search for the Flexfield Code value EGO_ITEM_EFF

    All flexfields for Product Hub are created within the flexfield code EGO_ITEM_EFF.

  3. Select the desired flexfield in the search result and choose a deployment option from the Actions menu:

    • 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 can't select individual attribute groups or item classes for deployment. You should deploy offline if the flexfield changes impact 30 or more item classes.

    • Refresh and Deploy Offline: Use this option if the first two options result in errors.

      Note: You should only run this option if it's specifically recommended by Oracle support.

    To see the effects of these deployment options, you must sign out and sign back in.

Configure Extensible Flexfield Data Security

This example demonstrates how to configure extensible flexfield data security. The IT Security Manager job role provides access to the Oracle Authorization Policy Manager application where security is managed. Use this job role to create data security privileges on the required item extensible flexfield tables.

The following table summarizes key decisions for this scenario.

Decisions to Consider In This Example

Should I configure extensible flexfield data security at the instance level, item class level, or at the individual item level for more granular control?

Item class

In this example you will use the nontranslatable and translatable tables to:

  • Create data privileges for extensible flexfield attribute groups using the Oracle Authorization Policy Manager.

  • Associate new privileges with extensible flexfield attribute groups from the Setup and Maintenance work area.

  • Grant users access to item extensible flexfield attribute groups from the Setup and Maintenance work area.

Creating Data Privileges for Extensible Flexfield Attribute Groups

  1. Open Oracle Authorization Policy Manager and search for the database resource, Item Data Level EGO_ITEM_extensible flexfield.

  2. Click Search.

  3. Enter Item Data Level EGO_ITEM_extensible flexfield in the Search field.

  4. From the results of the search, select a table for which you want to create a data privilege.

  5. Select Edit from the Actions menu.

  6. On the Edit Data Security page, select the Actions tab.

  7. Create the required data privileges for this table. In this example you are creating data privileges for the Item Data Level translatable table. Create two privileges, one securing view access to the attribute group and another securing edit (maintain) access to the attribute group.

    Tip: To make determining whether a privilege is for viewing or editing, when naming privileges append a V or M to the name to indicate view or maintenance usages.

  8. Once the required privileges are created, submit the changes. A confirmation window indicates the success of the update.

  9. Log off APM.

    Note: You can create different sets of privileges on each extensible flexfield table. Also, you can create as many individual privileges as you have attribute groups if you want to secure each attribute group with a different set of privileges.

Associating New Privileges with Extensible Flexfield Attribute Groups

Once the extensible flexfield data privileges are created in Oracle Authorization Policy Manager, associate the privileges with extensible flexfield attribute groups.

  1. Use APPLICATIONS_IMPLEMENTATION_CONSULTANT and go to the Setup and Maintenance work area.

  2. Select the Product Management Offering.

  3. Select the Items functional area.

  4. Select the Manage Item Attribute Groups and Attributes task.

  5. Search for attribute group that needs to be secured.

  6. In the search results table, select the attribute group and click Edit.

  7. In the Context Usages section of the selected Attribute Group Details page, access the View privilege column droplist and associate the view data privilege created in APM with this data level.

  8. Access the Edit privilege column droplist and associate the Maintain data privilege created in APM with this data level.

  9. Click Save.

  10. Deploy the flexfields.

  11. Click Submit.

Granting Users Access to Item Extensible Flexfield Attribute Groups at the Item Class Level
  1. In the Setup and Maintenance work area, select the Product Management Offering.

  2. Select the Items functional area., then select the Manage Item Classes task.

  3. Select the item class you want to manage user access to.

  4. In the item class page, Select the Security sub tab.

  5. In the Item Class People table, grant users access to extensible flexfield attribute groups by assigning the extensible flexfield privileges with them.

  6. From the Actions table, select the Add icon.

  7. In the Select and Add: Actions dialog box, search for your attribute group privilege and associate.

  8. Click Save.

    Note: The extensible flexfield data privileges can be granted to users at two different levels. One Item class level that will ensure that all items associated with the item class will be granted access. Item access can also be managed at the instance level, in item's case Item Class level. You can provide access to users at the item class level if the same set of users manage items within the item class. This allows for easy and limited maintenance of grants.
    Note: At the item level, this allows a more granular control of granting access at individual item level. The navigation and access to manage item level security remains the same as for operational attributes.

Item Attribute Groups and Attributes

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 from the Product Management offering in the Setup and Maintenance work area. 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, select the view and edit privileges for the attribute group in Context Usage.

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 groups and attributes, complete these tasks:

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

  • Deploy the attribute by using the Deploy Item Flexfields task

Create Item Attributes: Video and Procedure

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 Attribute Groups and Attributes

      New attributes are created within an attribute group and then associated with the item class where the attributes must appear.

  2. Let's create a new attribute group.

    • On the Manage Attributes Group page, click Create.

    • Enter a name. It's automatically populated to the other required name fields.

    • In the Behavior field, choose the behavior of attribute as either Single Row or Multiple Rows.

      Select Single Row if you want the collection of attributes to appear as separate fields, and only allow one set of responses.

      Select Multiple Row if you want the collection of attributes to appear as columns in a table, and allow multiple sets of responses.

    • In Context Usage, set the context usage to specify whether the attribute group applies to the item directly, to the item revisions, or to the item suppliers. In this case, select item.

    • Click Save.

  3. Let's create an attribute in the attribute group.

    • In attributes, click Create.

    • Enter a name. It's automatically populated to the other required name fields.

    • In Date Type, set a data type to suit your purpose. In this case, select Number.

  4. Let's create a new value set.

    • Click Create Value Set.

    • Add a name for the value set and enter the module as Product Development.

    • In Validation Type, select Format Only.

    • In Value Data Type, select Number.

    • In Precision, set the maximum number of digits users can enter.

    • In Scale, set the maximum number of digits allowed after the decimal point.

    • In Minimum Value and Maximum Value, enter the range which must fit the precision and scale.

    • Save and close all objects.

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

    • Offering: Product Management

    • Functional Area: Items

    • Task: Manage Item Classes

  6. Let's add the attribute group you created to an item class:

    • In the Manage Item Classes page, open the item class to which you want to add the attribute group.

      Select the Pages and Attributes Group tab.

    • Search for the attribute group you created and add that attribute group.

    • Click Save and Close.

      The attribute appears on the Pages sub-tab.

    • On the Pages sub-tab, select Product Development so that the attribute group appears only in Product Development work area (and not in the Product Information Management work area).

    • In Attribute Groups, click Select and Add.

      Search for the attribute group you created and add that attribute group and click Save.

    • Click Save and Close.

      Close the Manage Item Classes task so you can deploy the new attribute group.

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

    • Offering: Product Management

    • Functional Area: Items

    • Task: Deploy Item Extensible Flexfields

  8. Search for item attributes and click Deploy Flexfield. Wait until the process is completed and then click OK.

  9. Sign out of the application and sign in again.

Configure Attributes in Item and Change Order Context

You can configure attributes, and multirow extended flexfields (EFFs) as follows:

  • Attributes controlled by change orders - can be modified only through a change order.

  • Attributes that aren't controlled by change orders - can be modified through the item page in the Product Development work area, or a change order.

    For example, you can use this feature to update multi-row extended flexfield attributes without creating an engineering change order.

Note: This topic is applicable only for item level extended flexfields in Product Development.

Properties of attributes differ based on their configuration. 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

Attributes controlled by change orders

Editable only in the initial item revision and if the item isn't yet assigned to the change order.

Editable depending on the change order status.

All revisions display revision-specific values.

 

Attributes that aren't controlled by change orders

The following revisions are editable:

  • Revision which is already effective.

  • Revision which is scheduled to be effective in future.

Editable depending on the change order status.

All revisions display the value which is already effective; even previous revisions don't display revision-specific values.

For example, revisions A, B, and C show the same value.

Note: The previously effective revisions aren't editable even during the execution of scheduling jobs.

All revisions display revision-specific values.

For example, revisions A, B, and C show different values based on changes you actually made to the attribute.

Here's how you configure attributes and EFF attributes to be controlled by the change order:

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

    • Offering: Product Management

    • Functional Area: Product Rules

    • Task: Manage Item Rule Set

  2. Create a new rule set and specify how you want the attribute to be modified:

    • On the Manage Rule Sets page, click Create.

    • Enter the details of the rule set.

    • Composite: Select No.

    • Type: Select Validations

    • Association Type:

      To modify attributes through the change order only, set Association Type as Attribute Group.

      Note: You can't modify the Association Type after you save the rule set.
    • Click Save and Continue.

  3. Create a new rule in the rule set you created in the previous step:

    • On the Edit Rule Set page, click Rules.

    • To create a new rule, click Create.

    • Sequence: Enter 10.

    • Severity: Select Needs approval.

      Note that Needs approval is mandatory for attributes that are controlled by change orders. Any other setting will prevent users from viewing previous revisions of the item.

    • Click Ok.

  4. Enter the details of the new rule:

    • In Validation Condition enter the criteria for validation.

    • For example, enter !changed([Item].[your attribute group]).

    • Validate the rule.

    • Click Save and Close.

  5. Add the new rule set to the master rule set.

    • On Manage Rule Sets, search for the master rule set.

    • Open the master rule set.

    • Add the rule set you created in a previous step.

    • Click Done.

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

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.

Create Rules to Automatically Generate Fields for Items

You can automatically generate the following fields during item creation: item name, and item description.

  1. In the Setup and Maintenance work area, use the following to configure a rule set:

    • Offering: Product Management

    • Functional Area: Product Rules

    • Task: Manage Item Rule Sets

  2. Create a rule set. In the Create Rule Set dialog:

    • Association Type: Select Item class.

    • Association Name: Select an item class for which you want to automatically generate fields during item creation.

    • Click Save and Continue.

    The Edit Rule Set page appears.

  3. Depending on the purpose of the rule, define the Return Type as either Item Number or Item Description. Here is a sample rule that concatenates two extended flexfield attributes and uses the resulting text as the value for the item description.

    [Item].[Descriptions].[Description 30 Characters]+" "+[Item.[Descriptions].[Description 45 Characters]
  4. Click Save and Close.

  5. Use the following to configure an item class:

    • Offering: Product Management

    • Functional Area: Items

    • Task: Manage Item Classes

  6. Search for and open the item class you modified in a previous step.

  7. On the Item Management tab:

    • Click Number Generation. In Item Number Generation Method, select Rule Generated.

    • Click Description Generation. In Item Description Generation Method, select Rule Generated.

  8. Click Save and Close.

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

To to create and manage item classes, user-defined attributes, and data security, use the Manage Item Classes task in the Setup and Maintenance work area:

  • Offering: Product Management

  • Functional Area: Items

  • Task: Manage Item Classes

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 in 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 date 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 doesn't 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 don't 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 within it are public by default. Similarly, item classes created within a private item class or a 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 can't have child item classes that are public.

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

  • In the 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 users, user groups, or organizations.

  • You must set data security at the item class level to restrict access to user-defined attributes, and to 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

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

There are two ways to work with a default item class, depending on whether or not you're able to use Oracle Fusion Product Hub.

With Product Hub

You can designate a single item class to be the default item class selection when users search for or create items in the Product Information Management work area. This item class is then defaulted in flows where users have to explicitly select an item class.

To begin, identify an item class that's heavily used in your enterprise. You can then designate it as the default. Here's how:

  1. In the Setup and Maintenance work area, use the Manage Item Classes task:

    • Offering: Product Management

    • Functional Area: Items

    • Task: Manage Item Classes

  2. Query the item class to be used as the default.

  3. On the Edit Item Class page, select Default Item Class.

Subsequently, the item class designated as the default becomes the item class selected by default:

  • In the Item Class field in the Create Item dialog box, when users create items

  • In the item class query field in the page header, when users search for items on the Manage Items page

Other considerations:

  • For new installations of Product Hub, the Root Item Class is selected as the default item class.

  • For updated installations of Product Hub, you can select any other item class to designate it as the default item class.

  • Whenever a new item class is selected as the default, the previously selected default item class is automatically deselected.

Without Product Hub

For non-Product Hub customers, the Manage Default Item Class task is used because these customers can't create additional item classes nor can they create user defined attributes such as extensible flexfields. You can access this task from the Product Management offering in the Setup and Maintenance work area. An exception to this rule is that Product Development customers can create additional item classes and extensible flexfields. 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.

Overview of Item Status

Every item has an Item Status attribute. By setting the item status, you can change the default values for a subset of operational attributes referred to as status-controlled attributes of the item, according to how the status has been set up.

Set Up Item Statuses

You can use predefined item statuses, and also define your own statuses.

To create, edit or delete item statuses, use the Manage Item Statuses task:

  • Offering: Product Management

  • Functional Area: Items

  • Task: Manage Item Statuses

The predefined item statuses are:

  • Active

  • Inactive

For each item status, the Details section of the Item Statuses page contains the operational attribute groups and status-controlled attributes governed by the selected item status. The same set of status-controlled attributes applies to all statuses. You define how the item status affects each attribute.

The defined status-controlled attributes are listed under the reference for the Item Status attribute, which is a member of the Item Main specifications. Examples of status-controlled attributes are Build In WIP, Customer Orders Enabled, and Invoice Enabled. All of the status-controlled attributes have the values Yes and No.

Whenever a defined status is applied to an item by a user, the value of each of the status-controlled attributes in this list is set to the value you choose here, subject to the usage you select. Note that the affected attribute value in the item might not be different after the item status is applied.

To set the values and usages for the status-controlled attributes, in the Details table, set the Attribute Value control to Yes or No, then set the Usage. The usage values are:

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

  • Inherited - Sets the values of the item status-controlled attributes when the status value changes. You can't override the value.

  • None -The item status attribute values won't be changed.

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

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

Apply Item Statuses

You can use an item status to change the default values for status-controlled attributes.

To set the item status of a particular item, select a value of the Item Status field on the Edit Item page for the item.

When you change the item status of an item, that status can change the default values of the status-controlled attributes of the item, depending on how the item status has been set up. In turn, the status-controlled attributes can change the value of certain operational attributes, which can affect the actions that you can perform on the item.

When an item is created, the value of a given attribute is determined by these rules of precedence:

  1. The value entered by the end user. The value might be entered through the UI, FBDI, import maps, web services, or REST APIs.

  2. The effect of the value that was set for the Item Status field

  3. The value provided by an item template was applied. This only applies if the attribute was configured with a usage of Defaulted by the Manage Item Statuses task.

For example, assume that:

  • The defined item status Active sets the value of the attribute Stocked to Yes and the usage of the attribute as Defaulted.

  • An item template named CustomItem sets the value of the attribute Stocked to No

At runtime:

  1. An item is created by using the item template named CustomItem. The value of Stocked is set to No.

  2. The user edits the item and sets the Item Status field to Active. The value of Stocked is set to Yes.

  3. The user sets the value of Stocked to No. That value overrides any previous setting, if the defined usage of the attribute is set as Defaulted.

Set Up Data Security for Item Classes

Before you can create or view items in the Product Information Management work area, you must define data security for items. You define data security in item classes for each pairing of roles to organizations and of users to organizations.

If the Public check box is checked on an item class, then data security setup isn't required. For more details on how public item classes work, refer to the related topic on item classes listed here.

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.

Setup Task to Manage Item Types

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

There are 32 predefined 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

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

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.

Overview of Import Items

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 WebCenter Content.

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 WebCenter Content.

  5. Move the data into Item Management interface tables.

  6. Import data to Item Management product tables.

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.

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

Predefined 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

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

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.

Build Item Keyword Index

Keyword search lets you find items quickly that you're looking for. Before you can use the keyword search in the Product Information Management work area, you must build the index.

  1. In the Setup and Maintenance work area, select the Manage Item Keyword Search Attributes task.

    • Offering: Product Management

    • Functional Area: Items

    • Task: Manage Item Keyword Search Attributes

  2. Select the attributes that you want to use in the indexing process.

  3. Click Index from the global header region and choose from these indexing options:

    • Create Index: Lets you start the indexing process using the current configuration of attributes, organizations, and languages.

    • Schedule Indexing: Lets you schedule the indexing process. The indexing is run based on your selections on this page.

      This initiates the indexing process.

Note: To see and edit data in the Indexed Organizations and Languages section, you must have the Manage Item Keyword Search Organizations and Languages (EGP_MANAGE_ITEM_KEYWORD_ORG_LANGU) privilege.

Understand Indexing Statuses

When you initiate the indexing process, you get these statuses in the Indexing Status column:

  • Completed: 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 rerun.

  • Running: The indexing process is currently running.

  • Scheduled: The indexing process is scheduled to run.

The status is displayed for each attribute on the Manage Item Keyword Search Attributes page. One or more attributes can be a 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.

How You Migrate Item Keyword Index Values to Another Server

You can migrate item-keyword-index setup values to another server using the Manage Item Keyword Search Attribute setup task. Before you migrate the index values, you must migrate the organization and languages to the target server.

You can access the setup tasks here:

  • Offering: Product Management

  • Functional Area: Items

  • Task: Manage Item Keyword Search Attribute

The setup task migrates the organizations first, but it will not migrate the languages. You must install the languages manually on the target server. You can use either the CSV or the XML format to migrate your organizations and languages. After the organization and languages are migrated to the target server, then you can use the Manage Item Keyword Search Attributes task to build your index on the target server.

Item Keyword Search Scheduled Process Actions

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:

Note: Before you use CREATE, DROP, and REBUILD actions, consult with Oracle Support.
  • CREATE: Creates the index, if not present. This action indexes all items in the instance.

  • DROP: Drops the index. Use this action only when the index is damaged and it 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 reindex either all rows or the affected rows, depending on whether predefined attributes have been added or deleted.

  • REBUILD: This action will reindex all rows. Use this action only when the index is damaged and it needs to be rebuilt. The process of rebuilding the index takes a longer time to complete.

  • SYNC: This action processes the index changes in the queue.

    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 don't have 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.

Publish Item Objects

Publication helps you schedule and publish item objects automatically to each spoke system.

To publish item objects from Oracle Fusion Product Hub to a spoke system, do these steps:

  1. Define publication options for a spoke system.

  2. Define the schedule and parameters for the scheduled process.

  3. Access the payload generated by the publication scheduled process.

Now, let's discuss these steps in detail.

You can publish item objects using the Manage Spoke Systems task.

  1. From the Setup and Maintenance work area, use this navigation to open the Manage Spoke Systems task:

    • Offering: Product Management

    • Functional Area: Product Spoke Systems or Item Batches

    • Task: Manage Spoke Systems

    You can also select the Manage Spoke Systems task in the Product Information Management work area.

  2. Select a spoke system from the Search Results table to open the Edit Spoke Systems page.

  3. Click the Publication Options tab.

  4. Select the Item Relationships: Spoke System References entity in the Item Publication Criteria area.

  5. Save the page.

When you publish the spoke system, the publication content includes the complete category-classification path for the item-category assignment. The category-classification path is also published in the publication payload as a part of the item-category assignment.

Define the Schedule and Parameters for the Scheduled Process

Publish the item objects using the Product Hub Publication Job scheduled process.

  1. From the Scheduled Processes work area, click Schedule New Process.

  2. Open the Product Hub Publication Job schedule process.

  3. Define the Publish Items parameter as Yes to publish your items. You need to configure all the parameters in the Process Details dialog box. Here are the most relevant parameters:

    Schedule Process Parameters Description

    Spoke System

    Name of the external spoke system where you want to publish items, item classes, or catalog information.

    Publish from Date

    Publishes records of objects from a start date. Specify the start date.

    Publish to Date

    Publishes records of objects to an end date. Specify an end date. Use this parameter with the Publish from Date parameter.

    Process Sequentially

    Specifies the publication jobs to run sequentially when there is more than one job. Otherwise, the jobs run in parallel with each other.

  4. (Optional) Click the Advanced button and schedule the process to run at a later date and time.

  5. Submit the scheduled process.

    The scheduled process publishes the objects of each spoke system.

Publication processes can be a recurring or a one-time event. Let's say you're setting up an integration to a legacy application, where you're publishing new items that are created in Oracle Fusion Product Hub. 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 Oracle Fusion Product Hub is feeding new item information to an ERP application. The application is available only for a brief period to accept the feed. So, you must plan the schedule process accordingly.

You should review the log files for additional details:

  • The log file for the Product Hub Preprocessing Publication Job scheduled process contains the parameters that were used to run the job, plus record counts of what's published.

  • The log file for the Product Hub Publication Job scheduled process contains the identifier dDocName (which corresponds to the Content ID in Oracle WebCenter Content) and the name of the compressed file containing the publication files.

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

  • If an item record in the publication fails, the publication process doesn't publish the failed record but it does publish the remaining item records.

  • The publication process updates the log file with additional information about the publication failure including the item number, rule name, and any error message that you have configured for the rule definition. Using this information, you can trace any publication errors and fix them.

  • The publication log file also:

    • Contains additional information to clarify publication exceptions.

    • Displays rule exception messages that you have created during the rule definition.

    • Displays exception messages based on the exception type during publications.

    • Includes publication subjob exceptions.

Define Profile Options to Publish Items

If you're publishing over 1000 items or records, you can consider changing the values of the publication profile options to optimize the publication process.

You can control of the size of the publication payload to match the requirements of applications and processes. To control the payload size, use the Manage Advanced Item Profile Options task in the Setup and Maintenance work area to modify the values of one or more of these profile options:

  1. In the Setup and Maintenance work area, use the Manage Advanced Item Profile Options task:

    • Offering: Product Management

    • Functional Area: Items

    • Task: Manage Advanced Item Profile Options

  2. Update one or more of the profile options in this table:

    Profile Option Code Profile Option Name Purpose

    EGI_PUBLICATION_ITEMS_PER_PAYLOAD

    Number of Items per Payload for Publication

    Number of items in each XML file.

    This profile option determines the number of items to be used per payload in the publication process.

    The predefined value is 100.

    EGI_PUBLICATION_NUMBER_OF_PAYLOADS

    Number of Parallel Payloads for Publication

    Number of scheduled subprocesses that are launched in the extraction process.

    This profile option determines the number of parallel payloads to be used in the publication process.

    The predefined value is 10.

    EGI_PUBLICATION_SIZE_OF_ZIP_FILE

    Size of the Publication Payload File in Megabytes

    This profile option controls the overall size of the payload Zip file, in megabytes. The payload Zip file can contain more than one XML file for the item object. This profile option lets you chunk large publication jobs into multiple XML files. This profile option controls the overall size of the payload Zip file.

    The predefined value is 500.

Access the Payload Generated by the Publication Scheduled Process

You can access the XML payload of the publication scheduled process from Oracle WebCenter Content.

The log file for the Product Hub Publication Job scheduled process contains an entry like this example that identifies the output file for the publication:

The file PIM_Publication_PIMDH_12054.zip was uploaded to the folder /Contribution Folders/ with the content identification number dDocName:UCMFA00019982.
Note: The contents of the /Contribution Folders/ folder is limited to 1000 files.

The identifier dDocName in the log file corresponds to the Content ID field of the user interface of Oracle WebCenter Content.

To locate your publication file, use the GET_SEARCH_RESULTS search service of the Core Content Server for Oracle WebCenter Content, using these criteria:

  • The value of dDocName from the log file

  • The FAFusionImportExport Security Group

Here's an example of a search criteria expression for GET_SEARCH_RESULTS that uses information from the scheduled process log file:

IdcService=GET_SEARCH_RESULTS
dDocName = UCMFA00019982

What's Published in the Publication Payload

This table lists the payload that's published for a spoke system. The Publication Criteria column specifies what you define in the spoke system and the Options column specifies the published content.

Publication Criteria Options

Objects

  • Items

  • Item classes

  • Item catalogs

  • Trading partner items

Item entities

  • Attributes

    The attributes are selected by default, and they include:

    • 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

Item catalog entities

  • Catalog translation content

  • Catalog attachments

  • Catalog descriptive flexfields

  • Categories

  • Category translation content

  • Category attachments

  • Category descriptive flexfields

  • Category item assignments

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

Setup Document Classes

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.

Are there any restrictions when specifying the item class code?

The item class code is the read-only internal name that's generated after you enter the name of a new item class. If you plan to define approval rules for new item requests or change orders based on the item class, the item class code should not end with a numeric character. For example, if you use the item class code XYZ1 in the approval rule, it will fail to execute correctly.

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 predefined and describe the type of lifecycle phase. The predefined values are Design, Obsolete, Preproduction or Prototype, and Production.

You can create lifecycle phases by selecting one of the predefined lifecycle phase types.

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 you have not selected the All Values Required check box, then inherited-required attributes from parent will be displayed in a read-only format in the selected list and you can move additional required attributes from available list to selected list.

If the association is inherited and you have selected the All Values Required check box, then All Values Required is read-only and inherited attributes are placed in the selected list, also in a read-only format.

Why can't I search for items across work areas?

If you're unable to search for items by the same criteria when using the Manage Items task or not able navigate to Item Details page from search results in either the Product Development work area or the Product Information Management work area, then you might need to perform the Deploy Item Extensible Flexfields task in the Setup and Maintenance work area, using the Refresh and Deploy Offline option.

Note: You should consult with Oracle Support before running this deployment option in other situations.