Oracle Cloud Learning Center


11 Define Common SCM Configuration: Define Basic Items

This button toggles the Table of Contents floating window

 

This chapter contains the following:

Product Value Sets: Explained

Product Child Value Sets: Explained

Managing Default Item Class: Explained

Item Statuses: Explained

Managing Item Types: Explained

Cross-Reference Types: Explained

Item Imports: Explained

Related Item Subtypes: Explained

Managing Descriptive Flexfields for Items: Explained

FAQs for Define Basic Items

Product Value Sets: Explained

Value sets are specific to the application in which they will be used. In the Oracle Product Information Management application, value sets are used primarily for defining attributes where the values that an attribute can have is limited to a specific set of values.

Value sets can be edited or new value sets can be created from the Manage Product Value Sets page. The Edit icon launches the Edit Value Sets page, which redraws in the same region of the local area. The Create icon launches the Create Value Sets page, which redraws in the same region of the local area.

A value set is defined by the value set code and is specific to the module of an application in which the value set is to be used, such as Item Class.

The validation type determines how the value of field is validated for the assigned value set. The following are the seeded values:

  • Format Only

  • Independent

  • Dependent

  • Subset

  • Table

The value data type determines the data type for the value set. The following are the seeded values:

  • Character

  • Number

  • Date

  • Date/Time

Product Child Value Sets: Explained

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

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

You define child value sets as follows:

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

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

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

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

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

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

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

Managing Default Item Class: Explained

The Root Item Class is seeded and all item classes are created as children of the Root Item Class. For Oracle Fusion Product Model customers, only the Root Item Class is available. The Manage Default Item Class task enables Product Model customers to manage item class templates, descriptive flexfields, attachment categories and lifecycle phases. The Manage Default Item Class task launches an edit page for the Root Item Class.

The functionality for the Root Item Class is defined using three tabs:

  • The Basic tab enables descriptive flexfields and attachment categories to be viewed and managed for the Root Item Class.

  • The Lifecycle Phases tab enables one or more lifecycle phases of a lifecycle to be associated with an item class.

  • The Templates tab is where you define and manage item templates for the item class.

Item Statuses: Explained

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

You can create or edit or delete item statuses on the Manage Item Statuses page. Inactive dates are used to specify the date after which the item status will no longer be active. Operational attribute groups and attributes corresponding to the selected item status are displayed in the Details section. Select a value for the status from choice list for the attribute. Whenever the status is applied to the item, the value of the attribute may change. If the status will have no value, select No.

Select the Usage value of None or Defaulted or Inherited in the choice list for the Usage field that corresponds to how the attribute value will change based on the item status value:

  • Defaulted-Sets the values of the item status attributes when the status value changes, but allows the overriding of the value during import and update of item.

  • Inherited-Sets the values of the item status attributes when the status value changes, but overrides cannot occur.

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

Any change made to an item status is not applied automatically to existing items, but will be applied during the editing of an item when the item status value is changed.

Managing Item Types: Explained

Item types are managed on the Manage Item Types page.

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

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

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

Cross-Reference Types: Explained

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

Item Imports: Explained

You can import items and item-related information using interface tables. This import data is loaded into the production tables using the Import Item task.

Import Item

The Import Item task creates an Enterprise Storage Server (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. The import processes will perform all of the validations necessary to ensure the data imported is correct prior to moving the data into the production tables.

  1. Access the Enterprise Storage Server and provide a process name (job definition) such as Item Import Process.

  2. Select Setup and Maintenance from the Navigator.

    Access the All Tasks tab on the Overview page, and search for the Import Item task with the name of your ESS process definition.

  3. Click the Go to Task icon in the search results for that Import Item task.

    The parameters for the item import process are

    • Batch ID: Associate the interface table to an item batch definition.

    • Organization: Select an organization to be used for the import.

    • Process Only: Determines how the data is processed. The choices are:

      • Create

      • Sync

      • Update

    • Process All Organizations: Select Yes if the import contains items that will be imported to multiple organizations.

    • Delete Processed Rows: Select Yes to delete rows that are imported without errors

  4. Click Submit and the Request Number will be displayed.

Monitoring Import Items

Select Setup and Maintenance from the Navigator, then access Monitor Item Imports to search for specific Enterprise Storage Server processes and monitor their status in the search results table.

Related Item Subtypes: Explained

A related item is an item relationship between two existing items. How the two items are related is defined by a subtype. Multiple subtypes for related items are seeded, and you define additional subtypes on the Manage Related Item Subtypes page.

Managing Descriptive Flexfields for Items: Explained

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

Item Descriptive Flexfields

If you are not using Oracle Fusion Product and Catalog Management, 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, which you can access by searching for flexfield tasks on the Setup and Maintenance Overview page.

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, which you can access by searching for flexfield tasks on the Setup and Maintenance Overview page.

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, which you can access by searching for flexfield tasks on the Setup and Maintenance Overview page.

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, which you can access by searching for flexfield tasks on the Setup and Maintenance Overview page.

FAQs for Define Basic Items

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

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

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


Previous Page Next Page

Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices