View Structure Details—Classic

Structure information is available as part of the item details. You can view structure details by navigating to item details and selecting the Structures tab.

All structures created for items are listed in the structure table within the Item Structures sub tab. Clicking the structure name enables you to drill into the structure details page to view the component information.

The Item Structure Details page shows multilevel structure components in a hierarchical table and provides you with a complete view of all the components and assemblies of the structure.

View the Item for a Particular Revision

To view the item for a particular revision, use Actions > Open Another Revision. The structure appears based on a reference date. The table shows how the default reference date differs based on the selected revision.

Selected Item Revision	Default Reference Date
Past effective	Revision end date
Current effective	Current date
Pending	Current date
Future effective	Future effective date

Here’s some information on structures and components:

Date Filter

Enables you to see what the structure looks like at a given date.

Let's say that you enter 7/18/19 and click Go. Then it shows the structure as on 7/18/19.

Note:

You can’t edit the component entities for a past date.

The Total Quantity in the summary table is calculated as a ratio of quantity to the yield factor.

Use Placeholder

The Use Placeholder column indicates whether a placeholder is set for the component. Here’s what happens if the value is set to Yes:

A placeholder is created for such items in the configurator model.
The items aren’t loaded into configurator models during structure import.

Note that:

The Use Placeholder column is editable if Structure Item Type specification for an item is set to Option Class. You must also make Component Order Management fields visible from Item Structure Details > View.
To change the placeholder value, on the Actions menu for a component select Edit. Select or deselect the Use Placeholder check box.
You can replace the placeholder with the actual data during order import when required.
The placeholder structure can be loaded on demand from the Configurator.
The value for Use Placeholder attribute can be set from both the item context and the change order context.
You can use SOAP and REST services to set or retrieve the Use Placeholder attribute.
Import and FBDI support Use Placeholder attribute.

Change Control

The Change Control column indicates whether structure changes are allowed. Change control permission is based on the business rules written for the structure name. The change orders column presents the number of change orders pending for the structure. Structure details, including header attachments and configured attributes, are presented in the details region.

Find Number

You can differentiate duplicate components in an assembly using the Find Number attribute.

The find number identifies a specific instance of an item in a structure. When a duplicate component is added, the application will automatically increment the find number, but you can modify it before you save your changes. Once the item is saved, here’s how you can change the find number:

Delete the component and add it again with the new find number.

Use the Replace action to replace a component with the same component and provide a different find number.

Example: Consider that a server containing 4 similar processors is positioned at the same level in the structure. Each instance of the processor will have a unique find number. This will allow you to have duplicate instances at the same level in the BOM, and differentiate each instance.

Here are some additional details:

You'll be prevented from creating duplicate find numbers for Model and Option Classes. The Find Number column will be displayed and defaulted to 1. Also, you can't add the duplicate component row.
You can't create overlapping effectivity dates for the combination of component and find number.

You must ensure that the date range of the duplicate component is outside the date range of the initial component. Note that the date range is calculated based on the start and end dates of the component.
Attributes such as Quantity, Basis Type, and Supply Type can have a different value in the duplicate row. Similarly, structure entities such as substitute components and reference designators can also have a different value in the duplicate row.
Find Numbers are automatically incremented when you add duplicate components in the user interface, but not when you update structures using REST services or import.
In the item structure import, if the find number value isn’t provided, it will be defaulted to 1. If you have a duplicate instance of the component in your structure, you must provide a unique find number value in import. In the absence of the unique find number, the import will create a single component with the find number value defaulted to 1 and the other components won’t be created. This is applicable for REST APIs and SOAP Services as well.
If you perform a Replace action to update the New Find Number value using import, it’s recommended not to import changes to other attributes in the same import batch.

Here are the best practices and recommendations:

All existing and new customers should use Item Sequence for sequencing the structure. It’s recommended not to use Find Number for sequencing of the structure. Find number should only be used to include duplicate components in a structure.
Agile PLM customers migrating to Oracle Fusion Cloud should map Agile PLM Find Number to Item Sequence.
CAD integration customers should map Agile PLM Find Number to Item Sequence.
Agile PLM MCAD customers using the find number feature must map Find Number to structure component descriptive flexfields.

Suggested Operation Sequence

You can use the Suggested Operation Sequence column to record a design engineer's suggestion for the operation sequence of components in a manufacturing work definition. This doesn't have a default value and isn’t automatically incremented.

Note: Suggested operation sequence isn’t a required value.

Example: In an assembly that includes 3 components, you can suggest an operation sequence for component A as 1, component B as 2, and component C as 3. The manufacturing team can refer to this to specify a sequence for assembly of components (in the manufacturing work definition).

Component Details

For each component in a structure, the component item and component information are provided in a component details region. To view component details, select the component. You can also view component details using the item search page available in Product Management Experience.

Click Tasks > Product Management Experience > Search Products.

Here’s what you see in the Component Details region:

Substitutes: Lists items that you can use in place of the component.
Reference Designator: Lists the component placement during assembly.
Where Used: Lists items based on the level in which this item is used in another structure.
Note that the following data security privileges are required to view the where used report: View Item Basic, Maintain Item Basic, and View Item Structure or Maintain Item Structure.
- Show Structure Levels:
  - First level: view first level of the structure in which the item is used.
  - level: view topmost level of the entire bill of material in which the item is used.
  - All levels: view all levels from the item to the topmost level in which the item is used.
- Show Items: Filter items based on their approval status in a change order.
  - Implemented: view items that are already effective.
  - All: view items that are effective and the items that are yet to go through change order approval.
- Include Substitute Components: Select Yes to identify where the item is used as a substitute component. Here are the important columns for substitutes:
  - Item: Shows the structure in which the context item is used as substitute. The number of structure levels shown in the item depends on what you select in the Show Structure Levels filter.
  - Substitute For: Shows the components for which the context item is marked as a substitute. Appears only if you select First level and Include Substitute Components filters.
  Here are some extra details on substitutes:
  - You can view substitute components only for first level structure in the UI and all levels in the OTBI report.
  - The component number displayed in the Substitute For column is read-only.
    When you click the information icon (orange triangle) on the item, a panel that includes links to item entities appears. Note that you’ll only see items for which you’re granted access.
  - You can enable substitute component search by default using the profile option Include Substitutes in Item Where Used Data.
  - When you select Include Substitute Components, the Where Used results are restricted to:
    the master organization and primary structure in Product Development, and to the context item's organization in Product Information Management.
  - You can perform a search on primary, alternate, or all structures based on the search filters in Product Information Management.
  - The change order details report (in Product Development) includes the following substitute component attributes: Primary UOM, Enforce Integer Requirement, Priority, and Global descriptive flexfields. The report doesn't include redlines for substitute components.
Change Orders: Lists pending changes for the component (item).
Additional Attributes: Lists extra attributes and their values that you might have configured for the structure type and name.
Note: Only the first-level components can be managed from the Structure Details page.

Set Use-Up Date as the Effective Date

When you remove or replace a component, you can view and select a use-up date specified in a supply plan as the effective date for the affected object. The use-up date calculation helps you identify the optimal effectivity dates for structure components that are being removed or replaced on engineering and commercialization change orders.

Here’s how you set the use-up date when you remove (or replace) a component:

Click the Affected Objects tab on the change order.
Open the affected object that contains the component you want to remove (or replace).
Navigate to the Structure tab.
Select the component you want to remove and click Actions > Remove.
Click Save and Close.
Click Actions > Calculate Use-up Date on the Affected Objects tab.
The Select Use-Up date dialog box appears with the use-up dates defined in the referenced plans for the component (in the Supply Planning work area).
Select the use-up date and click OK.
The date you select is populated in the Effective Date column on the Affected Objects tab. If you manually update the effective date, any existing values for Plan Name and Use-Up Item are cleared out.
Save your changes.

Some additional considerations:

The Calculate Use-Up Date action is only visible if the Supply Chain Planning offering is enabled.
If you've enabled Supply Chain Planning but aren't using Planning use-up dates, the Calculate Use-Up Date action won't retrieve any use-up dates.
The Plan Name and Use-Up Item columns are hidden by default. You can use View > Columns to show these columns if you’re using planning use-up dates.
When you add the effective date using the Calculate Use-Up Date action, the time is set to 00:00:00, because Use-Up Date is a date-only attribute.
The affected item’s effective date automatically changes to Effective on Approval if the specified effective date is in the past by the time the final approver (for the final approval status) approves the change order. If this happens, the Plan Name and Use-Up Item values are cleared out.
If you update the affected object's lifecycle phase, you must first save the lifecycle phase change before updating the effective date using Calculate Use-Up Date.