Oracle Configurator Cloud

1. Oracle Configurator Cloud Guide for Setting Up User Defined Attributes (UDA) and Transactional Item Attributes (TIA) in the Configurator Cloud July 2018 Al Satchu, Senior Principal Product Manager Configurator Cloud

2. User Defined Attribute (UDA) Setup for Configurator Cloud Extensible Flexfield Deployment Create Model/Items Using Item Class with UDAs Import Model into the Configurator Model Environment 1 5 Defining a Value Set for an Attribute Setting up an Attribute Group and Attributes for UDAs Creating a Functional Item Page for Configurator Attribute Group Setup on Item Class 6 2 7 3 4

3. 1. Defining a Value Set for an Attribute Before creating a User Defined Attribute (UDA), a value set must first be defined. The value set determines the attribute type i.e. numeric, text, date and whether the attribute is user enterable (Format Only) or user selectable from a list (Independent). With a user that has Product Information Management (PIM) setup privileges, navigate to: Setup and Maintenance and search for and navigate to the Manage Value Sets task

4. 1. Defining a Value Set for an Attribute Create a value set for the UDA, specify the Validation Type, the Data Type and supporting definition data. Note: Value Sets are also used when creating Transaction Item Attributes (TIAs)

5. 1. Defining a Value Set for an Attribute For Independent value sets, those used to allow the end user to select from a list of values, click on Manage Values to define the values that may be selected.

6. 1. Defining a Value Set for an Attribute From the Manage Values page specify the values, their description, start and end dates and sort order.

7. 2. Setting up an Attribute Group and Attributes for UDAs Once your value sets are defined you may define the attribute group and the attributes that represent the User Defined Attributes to be included as part of the model or item definition. With a user that has Product Information Management (PIM) setup privileges, navigate to: Setup and Maintenance and search for and navigate to the Manage Attribute Groups task

8. 2. Setting up an Attribute Group and Attributes for UDAs Create an attribute group and attributes based upon the value sets you defined earlier.

9. 2. Setting up an Attribute Group and Attributes for UDAs Be sure to specify the context in which the attribute group and attributes will be used i.e. in the context of an Item.

10. 3. Creating a Functional Item Page for Configurator With a user that has Product Information Management (PIM) setup privileges, navigate to: Setup and Maintenance and search for and navigate to the Manage Item Classes task. Then click on the Root Item Class.

11. 3. Creating a Functional Item Page for Configurator Navigate to the Pages and Attribute Groups tab.

12. 3. Creating a Functional Item Page for Configurator Navigate to the Pages sub-tab and create a new page providing a Display and Internal name. The page defined here will be used to house all the UDAs for items associated to the item class. Generally no attribute groups are associated to this page at the Root Item Class level, that is generally done on child item classes.

13. 3. Creating a Functional Item Page for Configurator Navigate to the Functional Item Pages sub-tab and assign the page you created to the Configurator functional area with Usage: Item Attributes.

14. 4. Attribute Group Setup on Item Class After defining a child item class under the Root Item Class, associate the attribute group that holds the attributes you wish to be included as part of your model and item component definitions. Navigate to the Attributes Group sub-tab and add the attribute group(s) that include the attributes you wish to expose on the items to be associated to the item class.

15. 4. Attribute Group Setup on Item Class Navigate to Pages sub-tab and add the attribute groups to the page defined earlier on the Root Item Class for the Configurator functional area. That page will show in the list as an inherited page.

16. 5. Extensible Flexfield Deployment Once the item classes setup/changes are complete its suggested that the Item Extensible Flexfields should be redeployed to generate all the necessary artifacts used by Product Information Management (PIM). With a user that has Product Information Management (PIM) setup privileges, navigate to: Setup and Maintenance and search for and navigate to the Manage Extensible Flexfields task. Search for Flexfield Code: EGO_ITEM_EFF.

17. 5. Extensible Flexfield Deployment Navigate to Actions > Deploy Flexfield to generate the required artifacts based on the new setup.

18. 6. Create Model/Items Using Item Class with UDAs Create a model with the new item class that has UDAs defined against it. Navigate to the Specifications tab and then click on the page you created for the Configurator functional area.

19. 6. Create Model/Items Using Item Class with UDAs Here you should see the attribute group and the attributes you associated to the page earlier. Specify values for the attributes and save your changes.

20. 6. Create Model/Items Using Item Class with UDAs The attribute values set here extend the definition of your model/item and may be leveraged and referenced within Configurator.

21. 7. Import Model into the Configurator Model Environment Once your model definition has been finalized it may be imported within the Configurator Modeling Environment. Open a draft version of the model and navigate to the Structure > Item Attributes sub-tab and there you will find the UDAs you specified in PIM.

22. 7. Import Model into the Configurator Model Environment The UDA values may then be referenced in Configurator rules to dictate the runtime behavior of your model and may also be displayed in runtime UIs as required.

23. Transactional Item Attribute (TIA) Setup for Configurator Cloud Edit Item Class Create Transactional Item Attribute (TIA) Create Model with TIAs Import Model with TIAs into Configurator 1 2 3 4

24. 1. Edit Item Class Transactional Item Attributes (TIAs) are defined on an Item Class. Models and item components associated to the Item Class inherit the attributes as part of their definition. TIA values as the name implies are set in a transaction at runtime by an end user or by the system (via rules). With a user that has Product Information Management (PIM) setup privileges, navigate to: Setup and Maintenance and search for and navigate to the Manage Item Class task and search for the Item Class the TIAs are to be defined against.

25. 2. Create Transactional Item Attribute (TIA) Navigate to the Transactional Attributes tab and create a new TIA by clicking on the Create icon.

26. 2. Create Transactional Item Attribute (TIA) Specify the TIA (display) name, Internal Name and Description. Specify the application scope the TIA is valid for. This setting dictates the applications the TIAs defined will be passed to from Configurator. At a minimum Configurator must be specified for use within Configurator. Specify the Data Type and Value Set from the TIA. Optionally specify a Default value for the TIA and whether the TIA is active, required, read-only or hidden.

27. 2. Create Transactional Item Attribute (TIA) Once saved, any new model or item associated with this Item Class will include the TIAs as part of their definition.

28. 3. Create Model with TIAs After creating a new model in PIM with an item class that has TIAs, navigate to the Specifications tab and click on Transactional Attributes. Here you will find a listing of all the TIAs associated to the model item. These attributes are now part of the model definition and are available for end-user entry at runtime.

29. 4. Import Model with TIAs into Configurator The TIA definition on a model or item component are preserved upon import into Configurator. TIAs defined for a model or its components become part of the model’s overall structure and may be referenced as such in Configurator Rules and UI. The runtime behavior of a TIA similar to that of a model’s supplemental structure, with the added benefit that the values specified at runtime flow to downstream applications like Order Management and Manufacturing.

30. 4. Import Model with TIAs into Configurator TIAs are automatically presented in runtime as part of the Default UI template and may be moved, re-ordered or hidden in custom UIs.

31. 4. Import Model with TIAs into Configurator The TIA values may also be referenced in rules to dictate the runtime behavior of your model to drive selections, etc.