1. Implementing Order Management
  2. Guidelines for Creating Work Definitions for Configured Items

Guidelines for Creating Work Definitions for Configured Items

Assemble-to-order in a make flow creates the work order for the configured item dynamically at runtime according to the primary work definition that you set up at design time.

Here's what Oracle Manufacturing Cloud does:

  1. Receives a request to create a work order for a configured item:

  2. Uses the work definition that you set up to create a work order.

Note

  • Manufacturing uses the assemble-to-order (ATO) model as the ordered item when it creates the customer order. The item includes configure options that your user sets at runtime.

  • You must set up a work definition for the assemble-to-order model.

  • You must set the structure name of the model to Primary in Product Information Management. If the name isn't Primary, then you can't create a work definition for the model.

  • Manufacturing currently supports work definitions for an assemble-to-order model only for discrete manufacturing.

Create Work Definition

  • Use the right side of the page in the work definition to view each level of the model.

  • You can expand each option class and view the options in the class.

  • Set Production Priority to 1.

Specify Operations

  • You can assign the component of a model and a manufacturing resource to each operation.

  • You can assign an option class, which will assign all of its components.

  • You can apply an item to an operation only if the item is a component in the model.

To specify that the operation depends on the configure option, open your work definition for editing. On the Edit Work Definition Details page, click your operation, click Actions > Edit, then, in the Edit Operation dialog, set the Option Dependent attribute.

Value

Description

Contains a check mark.

The work order for the configured item includes the operation if:

  • Your user chooses the configure option that the flow assigns to the operation.

    or

  • The flow meets the criteria you set up in the applicability rule for the operation.

Doesn't contain a check mark.

The operation is required. The work order for the configured item always includes a required operation.

Specify Operations in the Hierarchy

You can assign each component to an operation from any level of the item structure.

  • You can expand an option class to view the configure options that the class contains.

  • You can expand a phantom to view the configure options that phantom contains.

  • If you assign the parent, then you can't assign its children.

  • If you already assigned the children, you can assign the parent, but the work definition will delete the child assignments.

  • You can choose to assign the option class or the options.

  • For a phantom that isn't an assemble-to-order item, you can choose to assign the parent phantom or the components.

  • If you assign an option class to an operation that depends on an option, and if the user selects at least one option in the class, then the work order for the configured item includes the operation that you specify in the work definition.

  • You can't expand a child assemble-to-order model.

  • You must assign the entire quantity for the component to the operation.

    • You can't update or split the quantity to more than one operation.

    • You can't inverse the quantity, unit of measure, or yield.

    • You can't assign an item that isn't part of the model structure.

Specify Child Models

If the supply type of a child model:

  • Is phantom. You don't need to create a separate work definition for the child model. The work order for the parent configured item includes the components of the configured item of the child model.

  • Isn't phantom. You must create a separate work definition for the child model. Use Planning to create supply for the configured item of the child.

Set Up Phantoms

A phantom is an item that you physically build but don't stock. If you specify an item as a phantom, and if your user chooses the item, then manufacturing stores it as part of the structure.

  • If you set the supply type for the component to Phantom in Product Information Management, then you can expand the phantom and view its components in the work definition.

  • You can keep expanding until you encounter a component that isn't a phantom.

  • You can't expand a child model even if its supply type is Phantom.

  • Manufacturing replaces each phantom with its physical counterpart at the next level of the hierarchy when configure-to-order creates the work order.

For details, see Overview of Phantom Explosion in Work Orders.

Apply Operation to Work Order

Use an applicability rule to assign an option-dependent operation.

  • Specify the criteria that determines whether to include the operation in the work order.

  • Create a rule for a configure option, option class, transaction attribute, or a combination of them.

  • Add a check mark to the Option Dependent option in the Option Dependent Details area. Enabling Option Dependent turns on the Add icon. Click Add to open the Add Applicability Rule dialog.

  • The Add Applicability Rule dialog displays the item structure for your model, but it only displays the configure options.

  • The dialog displays configure options and transaction attributes according to the date you select in the Date list on the Edit Work Definition Details page. It doesn't options and attributes that aren't currently in effect.

  • Expand each option class to view the configure options that the class contains.

  • You can't expand a child model.

Transaction Attribute

If you use a transaction attribute in an applicability rule, then:

  • Create the transaction attribute in the Product Information Management work area.

  • Assign the application scope to Configuration Matching when you create the transaction attribute. Configuration matching uses the value of the transaction attribute to determine whether the configuration already exists. Manufacturing also uses the transaction attribute to identify the operations it needs to build the configured item.

  • Use the item class to apply the transaction attribute to the configuration model, configure option, or child model. You associate a transaction attribute with an item class. Each item in the item class inherits the transaction attribute.

  • Assign either the configure option or the applicability rule to your option-dependent operation. Don't assign both. If you assign both, then the work definition doesn't evaluate the rule.

  • If your transaction attribute uses numeric data or string data, then make sure the validation type for the value set is independent or subset.

  • Expand the configure option in your rule to display the transaction attribute. Expand the transaction attribute to display the attribute value.

  • Use the internal name. The Add Applicability Rule dialog displays the display name of the transaction attribute. You can translate the display name. If the value set that the transaction attribute uses is translatable, then the item structure displays the internal name of the value and the translated value in parenthesis. For example, internal name(translated value). The work definition uses the value of the internal name to evaluate the rule. It doesn't use the translated value.

Operators

Use operators in the Rule Text window.

  • Include a combination of items and transaction attributes.

  • Use AND and OR conditions to create a complex rule.

Validate Your Rule

Click Validate to validate your rule syntax.

Use valid syntax.

  • Use single quotation marks to enclose each item number.

  • Use dot notation to separate each level of the hierarchy.

  • Use upper case letters for each operator.

Keywords

Syntax

Example Value

Use the ITEM keyword to specify whether the item a model or option class.

ITEM='CTO_474000'.'CTO_474300'.'CTO_474301'

where

  • CTO_474000 is the name of the model

  • CTO_474300 is the name of the option class

  • CTO_474301 is the name of the configure option

Use the TRANSACTIONALATTRIBUTE keyword to specify a transaction attribute.

Use double quotation marks to enclose each transaction attribute name and value.

'CTO_474000'.'CTO_474300'.'CTO_474301'. TRANSACTIONALATTRIBUTE ["Finish"] is equal to "Matte"

where

  • Finish is the name of the transaction attribute.

  • Matte is the value of the transaction attribute.

Operators

Numeric Attributes

String Attributes

  • Equal to

  • Not equal to

  • Less than

  • Less than or equal to

  • Greater Than

  • Greater than or equal to

  • Equal to

  • Not equal to

  • STARTSWITH

  • ENDSWITH

  • CONTAINS

  • DOESNOTCONTAIN

Verify Assignments

Make sure you assign each component in your work definition. If you don't, the flow will fail to create the work order for the configured item.

Go to the Edit Work Definition Details page, then click Actions > Export Operation Item Assignments. The export saves the entire model structure to Microsoft Excel.

Examine the status in Excel. If the status of your configuration model is.

  • Complete. You assigned all the required operations.

  • Incomplete. Identify which part of the hierarchy you must assign, then assign it.

Assignment Status

Description

Complete

You assigned an operation to the parent and each child.

Incomplete

You didn't assign the parent and each child.

Explicit

You assigned a child configure option.

Implicit

You assigned the parent and the child inherited the parent assignment.

Modify Attributes

The work definition gets values for attributes from the model that you create in the Product Information Management work area.

  • Basis

  • Quantity

  • Inverse Quantity

  • UOM

  • Item Yield

  • Planning Percent

  • Optional

  • Supply Type

You can't modify any of these attributes in the work definition except for Supply Type.

Related Topics