Administrator Role

Overview of the Administrator Role

The MOC Administrator role is used to setup and maintain master data for the Manufacturing Operations Center application. It is also used to calculate meter readings and sustainability consumption. Following is a brief overview of the tasks under this role:

• Contextualization setup: Used to setup contextualization method for equipment.

• Tag setup: Used to associate tags to equipment and MOC entities, and define rules for adding the business context through the contextualization setup.

• Sustainability aspect setup: Used to setup sustainability aspect and its corresponding usage categories and emission codes.

• Site setup: Used to setup site.

• Site sustainability setup: Used to setup the association of site to sustainability aspect and define the sustainability aspect sources and emission factors.

• Equipment setup: Used to setup equipments.

• Tag equipment mapping setup: Used to associate tags to equipment.

• Resource setup: Used to setup resources.

• User-defined entities setup: Used to setup user defined entities.

• Shift setup: Used to create shift templates and generate shifts for site and its entities.

• Hierarchy setup: Used to setup and build hierarchy.

• Meter setup: Used to setup meters.

• Meter entity association: Used to associate meter to entities.

• Lookups setup: Used to setup lookup values.

• Extensible attributes setup: Used to create attribute groups and attributes and associate to classifications and create pages.

• Run Requests: Used to run the MTH: Process and Populate MOC Entity Sustainability Aspect program that calculates meter readings and sustainability aspect consumption.

• Events

Refer to the Oracle Manufacturing Operations Implementation Guide for detailed information on setting up sustainability, site sustainability, equipment, resources, user defined entities, shifts, hierarchy, meters and lookups.

Related Topics

Setting Up Tags

Creating Equipment Contextualization Information

Setting Up Extensible Attributes for MOC Entities

Running the MTH: Process and Populate MOC Entity Sustainability Aspect

Setting Up Events

Setting Up Tags

A tag is the metadata configured in PLC or other device connector providing data at the program interval. MOC requires specific tags for obtaining the operation details and business context. There are two types of tags. Business context tags provide work order, operation, product, and equipment details. Data tags provide value of output, scrap, rework, quantity, and completed quantity.

To define tag data information

1. Navigate to the Tag Setup page. If you have already imported the tag metadata using the csv template, then they display on this page.

2. To add a new Tag Data Source, Click Add Source.

3. Enter the name of the new tag data source in the Tag Data Source field.

4. Select the Type of the tag. Options are Operation and Sustainability.

   

5. Select the System for the tag. The list of Source Systems that you set up while setting up the MOC application display in the list of values for this field. Refer to the “Setting Up Source Systems” chapter of the Oracle Manufacturing Operations Systems Implementation Guide for more information.

6. Save your work.

To add tags to a tag data source

1. Select a Tag Data Source to which you want to add tags.

2. Click Add.

3. Enter the following information for a tag:

   • Tag Code is the code for the tag.

   • Tag is the name of the tag.

   • Description is a brief description of the tag.

4. Select the Data Type for the tag. Options are Alphanumeric and Numeric. Numeric displays by default.

5. Select the Reading Type for the tag. Options are Cumulative and Incremental. Cumulative displays by default.

6. Select the Order in which the readings for the tag are recorded. Options are Ascending and Descending. This field is enabled only if you select Cumulative as the Reading Type. If you select Cumulative as the Reading Type, then Ascending displays by default.

   

7. Enter a Reset Value. Reset Value is the value at which the tag reading recording must be reset. This field is enabled only if you select Cumulative as the Reading Type.

8. Enter an Initial Value. Initial Value is the starting value that you expect to receive from a tag meter recording. This field is enabled only if you select Cumulative as the Reading Type. Zero is the default value.

9. Enter a Reading Interval (in minutes) as the time interval at which the tag readings must be recorded. You can enter a reading interval only for a tag of the sustainability type tag data source.

10. Status displays as Active by default. To inactive a tag, click Inactivate.

11. Click Save.

    Note: A tag can be associated to an equipment record only once, but can be associated to multiple equipment.

To update a tag

1. Select a tag.

2. Click Update. Edit the following fields:

   • Tag

   • Description

   • Reading Type

   • Order. This field is enabled for a Cumulative reading type tag only.

   • Reset Value. This field is enabled for a Cumulative reading type tag only.

   • Initial Value. This field is enabled for a Cumulative reading type tag only.

   • Reading Interval. This field is enabled for Incremental reading type tag of a Sustainability type tag data source.

3. Click Save.

Mapping Tags to Equipment

Oracle Manufacturing Operations Center enables you to map tags to equipment using the Tag Mapping page. You map a separate tag for each equipment output.

To map tags to equipment

1. Navigate to the Tag Mapping page.

2. Select the Site Name. All the Sites defined in the MOC application display in the list of values (LOV).

3. Select Equipment Name of the equipment to which you want to map tags.

4. Click Go. If tags are already mapped to the selected equipment, then they display.

5. Click Add to map a tag.

6. Enter the Tag Code that you want to map to the equipment. All the tags in the Tag Master display in the LOV. This is a required field.

   

7. Optionally, enter a Data Element for the tag.

8. Optionally, enter Attribute Group Name and Attribute Name. You can choose from a list of attribute groups and attributes that you define using the Extensible Attributes page as part of setting up the MOC application. Refer to the topic “Setting Up Extensible Attributes” chapter of the Oracle Manufacturing Operations Implementation Guide for more information.

9. Click Submit.

   Note: You can associate a tag to either to an entity or an attribute belonging to an attribute group. MOC does not allow an association to both an entity and attribute.

Running the MTH: Process and Populate MOC Entity Sustainability Aspect

Run the MTH: Process and Populate MOC Entity Sustainability Aspect to calculate the carbon emission and electricity usage costs for an entity. When you run the concurrent program the data obtained from the meter readings is processed to calculate the sustainability aspect consumed, the cost of and the carbon emission due to the consumption.

To run the MTH: Process and Populate MOC Entity Sustainability Aspect

1. Navigate to the Parameters window.

2. Enter the Process Mode as:

   • INIT to run the process in Initial mode.

   • INCR to run the process in Incremental mode.

3. Enter the Meter Calculation Start Date.

4. Click Submit.

5. Note the Request ID number.

6. Choose View from the menu and select Requests to view the status of your request in the concurrent program manager.

7. When your request ID is complete with a Status of Normal, click View Details to view the details of the run.

Creating Equipment Contextualization Information

Contextualization is the ability to take highly granular tag data collected from shop floor transactions and convert it into meaningful business data for analyzing. The contextualization rules engine enables users with various levels of sophistication on the shop floor to add the business context to the data tags. There are two tag types used:

• Business Context Tags–tags that provide work order, operation, product, and equipment details.

• Data Tags–tags that provide value of output quantity, scrap quantity, rework quantity, reject quantity, completed quantity, equipment status, and attribute tags.

The Equipment Contextualization page is used to associate a contextualization method for equipment and to define the mandatory or optional context for the business related to that equipment. The following three methods are used to add the business context:

Tag Based Contextualization

Business context such as work order, operation, and item is derived from the tags that are configured in the PLC for that equipment from the shop floor. The business context tags and the data tags are received into MOC with using the same group identifier for this type of contextualization.

Schedule Based Contextualization

Business context is derived from the equipment production schedule. If this contextualization method is selected, MOC uses the data tags from the equipment to select business context of:

• Work order and operation from the equipment production schedule

• Product from production material produced

• Equipment based on the setup of the tag to equipment association is done

• Shift based on the reading time

Manual Contextualization

Context is determined through data entered manually and is not derived from the Manufacturing Operations Center hub. The Manual Contextualization page on the Tag Data Workbench under the User role enables you to manually enter and edit context for all active tags that have not been summarized in the Equipment Summary tables.

To select equipment for contextualization

1. Navigate to the Equipment Contextualization Setup page.

2. Select a value in the Plant field.

3. In the Equipment field, select a specific record and then select Go. You can also leave the field null and select Go to display all the equipment records for the plant.

   The results table displays all the equipment associated to this plant record.

   

4. To edit equipment contextualization values, select equipment records and select a Contextualization Method. Choices are:

   • Tag Based—context is determined through tag readings of the equipment.

   • Schedule Based—context is determined through schedule data in the Equipment Production Schedules table.

   • Manual—context is determined through data entered manually.

5. In the Workorder field, indicate whether a business context is Mandatory or Optional for the selected equipment.

   Workorder context is determined from either the tag or the equipment production schedule.

6. In the Workorder Segment field, indicate whether a business context is Mandatory or Optional for the selected equipment.

7. In the Item field, indicate whether a business context is Mandatory or Optional for the selected equipment.

8. Save your work.

To change multiple records using the same contextualization rule

1. Select equipment records to create similar contextualization rules.

2. Select Enter Context in Batch to display the Batch Equipment Contextualization Update page.

   

3. Select the appropriate values in the following fields for the batch update:

   • Contextualization Method

   • Workorder

   • Workorder Segment

   • Item

4. Select OK to return to the Equipment Contextualization Setup page.

5. Save your work to create the batch update for the selected records.

Related Topics

Setting Up Tags

Adding Reason Codes

You can use tags to display reasons for downtime status and scrap quantity. You can define a list of all reason codes and reason meanings for Manufacturing Operations Center (MOC) plants, at the Instance level in FND_LOOKUPS, and equipment level in the Equipment Reason Setup user interface. In the Tag Mapping setup for the reason tag, map the tag to a data element (Equipment Downtime Reason and Scrap Reason).

You can set up Reason Codes using FND Lookup. Lookup types seeded by Manufacturing Operations Center include:

• MTH_SCRAP_REASON (for setting up scrap reasons)

• MTH_EQUIP_DOWNTIME_REASON (for setting up downtime reason)

• MTH_EQUIP_IDLE_REASON (for setting up idle time reason)

• MTH_EQUIP_RUN_REASON (for setting up run reasons)

• MTH_MESSAGE_DOMAIN_NAME (for setting up domain name for mobile alert messages)

  When you enter the lookup_code, meaning, and description for MTH_MESSAGE_DOMAIN_NAME, the text in the description field should be prefixed with an @ symbol. For example:

  LOOKUP_CODE	Meaning	Description
  ASCENDQUICK	ascendquick.com	@ascendquick.com

Add reason codes in the Application Object Library Lookups window from the Development Manager responsibility. You can also set up reason codes using the Lookups menu from the MOC Administrator's responsibility.

To add reason codes

1. Navigate to the Application Object Library Lookups window.

2. In the Type field, query by example MTH_SCRAP_REASON, MTH_EQUIP_DOWNTIME_REASON, or MTH_EQUIP_IDLE_REASON. The window displays all Reason Codes associated with these types.

   

3. Click a new (empty) row to add a new code.

4. Enter a Code.

5. Enter a Meaning for the code.

6. Enter an optional Description.

7. Enter an Effective date range. The From date defaults to the current date.

8. The Enabled indicator defaults to Enabled.

9. Save your work.

Related Topics

Viewing and Adding Reason Codes

Setting Up Equipment Reason Codes

You must add equipment reason codes prior to adding events. Reason codes define the Equipment Down event types with associated reasons.

Equipment can be down and unavailable due to planned preventive maintenance activities. MOC updates the equipment shift for each equipment item, taking into account planned downtime.

MOC captures the expected uptime for each equipment item when the equipment is down due to unplanned downtime, or when equipment is idle. The application helps to identify equipment availability for production.

To set up equipment reason codes

1. Navigate to the Equipment Reason Code Setup page. Use the Equipment Reason Code Setup page to set up equipment downtime reason codes. You can define the following reasons for equipment:

   • Downtime Reasons and Expected Uptime

   • Idle Time Reasons and Expected Uptime

   • Scrap Reasons

2. Select an Equipment Hierarchy from the List of Values (LOV).

3. Select a Level Name from the LOV.

4. Select a Level Instance.

5. You can optionally select an Equipment Criticality value from the LOV.

6. Click Go to perform your search. Based on the search criteria, the page displays the Level Instance and equipment for the selected Level in the Equipment Hierarchy.

   

7. Select one or more equipment rows and click the Update Sequentially button to navigate to the Update Equipment Reason Code Sequentially page. You can add Downtime reasons, Idle Time reason, and Scrap reasons for your equipment. You can also define Expected Uptime for each Downtime and Idle Time reason code.

To add or update equipment reason code sequentially

1. From the Update Equipment Reason Code Sequentially page, select the Downtime tab to add or update equipment downtime reason codes and expected uptime.

   

2. Enter a Downtime Reason Code, or select a code from the search page.

3. Enter a value for Expected Uptime (Hours).

4. Click the Next button to enter Downtime reasons for the next equipment item that you selected, or click Apply to save your work.

5. Select the Idle Time tab to enter equipment idle time reason and expected uptime.

   

6. Enter an idle time Reason Code, or select a code from the search page.

7. Enter a value for Expected Uptime (Hours).

8. Click the Next button to enter Idle Time reasons for the next equipment item that you selected, or click Apply to save your work.

9. Select the Scrap tab to enter equipment scrap reasons.

   

10. Click Add to enter a new scrap reason.

11. Enter a Reason Code, or select a code from the search page.

12. Click the Next button to enter Scrap reasons for the next equipment item that you selected, or click Apply to save your work.

Setting Up Events

Oracle Manufacturing Operations Center (MOC) provides a workbench to generate and process events based on event types. Based on the event type, action is taken by PL/SQL.

MOC supports collection of data from external OPC systems, and by using Event Management Framework, the application routes events and takes appropriate actions.

Update Equipment Event Action Sequentially Page

Use this page to add and update Event Types and Event Actions. You can also add notifications when events occur. You can add and update event types and actions for equipment items in order of selection from the Events Setup page. You can also view event actions previously added for equipment items (rows).

To set up events

1. Navigate to the Event Setup page. Use the Event Setup page to set up event actions for event types. You can select the following actions against an event type by equipment items:

   • Seeded action such as creating work requests in EAM

   • Calling custom APIs or PL/SQL scripts

   • Sending e-mail notifications

   • Sending mobile alerts

2. Select an Equipment Hierarchy from the List of Values (LOV).

3. Select a Level Name from the LOV.

4. Select a Level Instance.

5. You can optionally select an Equipment Criticality value from the LOV.

6. Click the Go button to perform your search. Based on the search criteria, the page displays the Level Instance and equipment for the selected Level in the Equipment Hierarchy.

   

7. Select one or more equipment rows and click the Update Sequentially button to navigate to the Update Equipment Event Action Sequentially. You can add or update event actions for each equipment row selected.

To add or update equipment event actions

1. From the Update Equipment Event Action Sequentially page, click the Add button in the Event Types region to add a new Event Type. If an event action was previously defined for an event type and you return to this page, then the earlier definition appears and you can modify the actions, if required.

   

2. Select an Event Type from the LOV.

3. Select a Reason Code from the LOV (if applicable.) The Reason Code LOV is enabled only for the Equipment Down event type.

4. Click the Add button to add Event Types.

5. Select the Event Action tab. The Seeded Actions region appears.

6. Click the Add button to add a seeded event action.

7. Select a seeded Event Action from the LOV.

8. Select the Name and the appropriate indicators for the notification method.

9. Click the Add button in the Custom Actions region to add custom event actions

10. Select the Notification tab to add event notifications.

    

11. Click the Add button to add new notifications.

12. Enter notification details for the selected event.

13. Click Finish to save your work.

14. Click the Next button to add event actions for the next equipment item that you selected, or click Finish to save your work.

Setting Up Extensible Attributes for MOC Entities

Oracle Manufacturing Operations Center supports an extensible attributes framework to capture specific attributes for manufacturing entities. The extensible attributes framework helps in setting up and capturing parameters that are unique for your business environment, plant, equipment, items, work orders, batch operations and user-defined entities. The extensible attributes setup consists of the following steps:

• Setting up profile options for item and equipment entity classifications

• Defining classifications for Others entity type

• Creating attribute groups

• Creating attributes

• Associating attribute groups to classifications

• Creating attribute pages

Entities and Classifications

Shop floor or manufacturing entities are business objects in Oracle Applications with unique characteristics and processes. MOC supports item, equipment, work order, batch operation, and miscellaneous custom entities.

Entities are grouped into classification to define the type of attributes they can monitor. For example, boiler equipment in the shop floor are classified into one group which is the resource Boiler. You can define this classification using attribute metadata such as Pressure, Temperature, and so forth. Each MOC entity type page contains two tabbed regions: Classifications and Attributes. Entity pages open with all the classification values displaying in the search results table region. You can filter this list.

Classifications are defined based on the hierarchy of the entities. The hierarchy level is determined by the information in the following table:

Entity	Classification Source Creation	Values
Item:	Profile Option–MTH:Item Classification for Extensible Attributes	Hierarchy Name. The level is always Level 9 for the hierarchy selected.
Equipment:	Profile Option–MTH:Equipment Classification for Extensible Attributes	Hierarchy Levels.
Work Order:	Work order type	Discrete or Process Manufacturing work order types only.
Other:.	No classification	N/A
Batch Operations	Work order	Work Order Number

Attributes and Attribute Groups

Attribute groups are a grouping of similar attributes used to monitor an entity. For example, Specifications is a seeded attribute group for the Equipment entity containing the attributes Parameter, Upper Control Limit, and Lower Control Limit. Oracle Product Information Management functionality is used for attribute creation.

Similar attributes can be categorized in an attribute group, such as a collection of items similar in type or function. You can:

• Group attributes based on business functions

• Define and use an unlimited number of attribute groups

• Create attribute pages for ease of viewing attributes

Attribute Pages

An attribute page is a view used to display, create, and edit different attributes from the various attribute group categories. An attribute page is a way of categorizing attribute groups and displaying them separately in these categories based on different functional areas. You can create attribute pages for each item, equipment, work order, batch operation, user-defined entity and other values of your entities—and assign corresponding attribute groups to these pages.

Refer to the Oracle Manufacturing Operations Center Implementation Guide for more information.

Related Topics

Viewing Classifications for Shop Floor Entities

Viewing and Creating Attribute Group Data for Entities

Viewing and Creating Attribute Pages for Entities

Setting Up E-Business Suite to run the Inbound Integrations for Discrete Flow

Manufacturing Operations Center (MOC) inbound integration is designed to work with E-Business Suite (EBS) and non-EBS target systems. The inbound integration with Oracle E-Business suite includes and enhances the collection of equipment entities and reference data, such as production segments, sub-segments, and resource schedules. This integration reduces the entity creation effort within MOC and also helps to reconcile data with Oracle EBS.

With MOC inbound integration, master and reference data collection from EBS into MOC is enhanced to collect resource instance, operation, and activity data so that there is no reconciliation issue of the references used in MOC and EBS for this integration.

MOC also collects the output and usage data from shop floor. On a demand basis, this data is consolidated to perform operation move, work order completion, and scrap and resource transactions. This data is pushed to the interface table for non-EBS consumption and targets the EBS interface table for EBS transactions.

To set up and collect inventory organizations from Oracle EBS

Prerequisites

• Set up MOC Locations under the source organizations.

• For outbound integration, set flag PROJECT_REFERENCE_ENABLED = 2.

1. Navigate to the Organizations window:

   Manufacturing and Distribution Manager > Inventory > Setup > Organizations > Organizations

2. Select an organization in the Name field.

3. Enter a location in the Location field.

4. Enter address details in the Address field.

5. In the Organizations Classification region, enter Inventory Organization.

6. Select the corresponding Enabled check box.

7. Save the record.

8. Select the Others button.

   The Additional Organization Information window opens.

9. Select Accounting Information.

10. Click OK.

11. In the Accounting Information window, select the appropriate record in the Primary Ledger, Legal Entity, and Operating Unit fields.

12. Click OK, and save the record.

13. Click the Others button.

    The Organization Parameters window opens.

14. Select a workday calendar.

15. Optionally, select the EAM Enabled check box if you want this location to be associated to the EAM organization.

16. Click Costing Information tab.

17. Enter costing details in the mandatory fields.

18. Save and close the window.

    For more information on setting up parameters, see: Defining Default Inventory Parameters, Oracle Inventory User's Guide.

19. Navigate to MTH Project > MTH Setup > MTH Systems to run the Oracle Data Integrator (ODI) package for the organization setup.

20. Run the ODI package MTH_PKG_ORGANIZATIONS_SRC

To create the site in MOC and map the organization to that site

1. Navigate to the Sites Summary window.

2. Select the Add button.

   The Add Site window opens.

3. Enter a site code in the Site Code field.

4. Enter a site name in the Site Name field.

5. Click the Add button in the Data Sources region.

6. Select a system code from the System Code LOV.

7. Select the source organization from the Source Organization LOV.

8. Click the Save & Close button.

To create a department

1. Navigate to the Departments window:

   Manufacturing and Distribution Manager > Bills of Material > Routings > Departments

2. Select an organization in the Organization window.

3. Enter a department in the Department field of the Departments window.

4. Save and Close the window.

   For detailed information on creating departments, see: Defining a Department, Oracle Bills of Material User's Guide.

To create a resource group

1. Navigate to the CRP RESOURCE GROUPS Lookups window:

   Manufacturing and Distribution Manager > Bills of Material > Setup > Resource Groups

   The Application Utilities: CRP RESOURCE GROUPS Lookups window opens.

2. Click New from the File menu.

3. Enter the organization code in the Code field.

4. Enter the meaning of the code in the Meaning field.

5. Enter a description in the Description field.

6. Save and close the window.

   See: Defining Resource Groups, Oracle Capacity User's Guide.

7. Navigate to MTH Project > MTH Setup > MTH Equipment Hierarchy.

8. Run the ODI package MTH_PKG_EQUIPMENT_ENTITIES_SRC.

To define a resource and attach the resource to the department

1. Navigate to the Resources window:

   Manufacturing and Distribution Manager > Bills of Material > Routings > Resources

2. Enter the resource, description, type, charge type details in the Resources window.

3. Save the record.

4. Click the Equipment button.

   The Equipment Types window opens.

5. Enter the equipment name in the Equipment field.

6. Save and close the window.

7. Navigate to the Departments window.

8. Query the department you want to attach to the resource.

9. Select the Resources button.

10. Query the resource that you created and assign it to the department.

    See: Defining a Resource, Oracle Bills of Material User's Guide.

    Defining a Department, Oracle Bills of Material User's Guide.

11. Navigate to MTH Project > MTH Setup > MTH Resources.

12. Run the ODI package MTH_PKG_RESOURCES _SRC.

To create resource costs

1. Navigate to the Resources window.

2. Query for the resource you created and select the Costed check box. This enables the Absorption Account field.

3. Select the Standard Rate check box.

4. Enter Absorption Account and Variance Account details in the respective fields.

5. Click the Rates button.

   The Resource Costs window opens.

6. Enter the cost type as Frozen or Pending.

7. Enter the Resource Unit Cost.

8. Save and close the window.

   See: Defining a Resource, Oracle Bills of Material User's Guide.

9. Navigate to MTH Project > MTH Setup > MTH Resources.

10. Run the ODI package MTH_PKG_RESOURCE_COST_SRC.

To collect resource instances, such as an equipment

Note: Resource instances are collected as equipment entities and they are of type Machine in MOC.

Prerequisite

Create items of type Equipment and then generate a serial number for the equipment items.

1. Create items.

   See: Defining Items, Oracle Inventory User's Guide.

2. Define equipment items.

   See: Define Equipment Items, Oracle Warehouse Management Implementation Guide.

3. Generate serial number for the item.

   See: Setting Up Serial Number Control, Oracle Inventory User's Guide.

4. Run the ODI package MTH_PKG_EQUIPMENTS_SRC 001.

To collect department and resource group hierarchies

1. Associate the department or resource groups with resources and equipment.

2. Map the serial number with resource instances by setting up the hierarchy between equipment entities and resources and equipments.

3. Assign the resources to the department.

   See: To define a resource and attach the resource to the department.

4. Run the ODI package MTH_PKG_EQUIPMENT_HIERARCHY_SRC.

5. Review the equipment hierarchy and the equipment denorm tables.

To collect the inventory items with BOM and routing setup

1. Create an item and assign it to your organization.

   See: Defining Items, Oracle Inventory User's Guide.

2. Navigate to MTH Project > MTH Setup > MTH Items.

3. Run the ODI package MTH_PKG_ITEMS_SRC.

To set up and collect item categories from EBS

Prerequisite

Update MTH_DIM_HIERARCHY table with the CATEGORY_SET_NAME column.

1. Create an item category and assign it to an existing item.

   See: Defining Categories, Oracle Inventory User's Guide.

2. Navigate to MTH Project > MTH Setup > MTH Items.

3. Run the ODI package MTH_PKG_ITEM_CATEGORIES_SRC.

4. Search for the new item category in the MTH_ITEM_CATEGORIES_D table.

To set up and collect the item costs from EBS

1. Define cost type for the item.

   See: Define Your Cost Types, Oracle Inventory User's Guide.

   Defining Cost Types, Oracle Cost Management User's Guide.

2. Navigate to MTH Project > MTH Setup > MTH Items.

3. Run the ODI package MTH_PKG_ITEM_COST_SRC.

4. Search for the cost details in the MTH_ITEM_COST table.

To set up and collect item hierarchy and item denorm from EBS

1. Navigate to MTH Project > MTH Setup > MTH Items.

2. Run the ODI package MTH_PKG_ITEM_HIERARCHY_SRC.

3. Validate the item hierarchy created for the created items, item categories in the MTH_ITEM_HIERARCHY table.

4. Search for the new records in the item Denorm table, MTH_ITEM_DENORM_D.

To collect the work orders

1. Create a discrete job.

   See: Defining Discrete Jobs Manually, Oracle Work in Process User's Guide.

2. Navigate to MTH Project > MTH Transactions > MTH Production Schedules.

3. Run the ODI package MTH_PKG_PRODUCTION_SCHEDULES_SRC.

4. Search for the discrete job in the MTH_PRODUCTION_SCHEDULES_F table.

To set up and collect work order associated with sales order reservations from EBS

1. Create a sales order.

   See: Defining Sales Order Main and Other Header Information, Oracle Order Management User's Guide.

2. Attach the sales order to a WIP job.

   See: Creating Reservations, Oracle Inventory User's Guide.

3. Navigate to MTH Project > MTH Transactions > MTH Sales Orders.

4. Run the ODI package MTH_PKG_WORKORDER_RESERVATION_SRC.

5. Search for the created sales order in the MTH_WO_SALES_ORDERS_F table.

   Note: You can also update and delete the work order associated with sales order reservations.

To collect the work order segments

1. Query the discrete job.

   See: Finding Discrete Jobs, Oracle Work in Process User's Guide.

2. Select the Operations button to review the operation details.

3. Run the ODI package to collect production segments.

4. Review the data in the MTH_PRODUCTION_SEGMENTS_F table.

To collect the work day shifts

Prerequisites

Set the profile MTH: Shifts Setup as External Source.

Create a workday calendar and assign it to Inventory organization.

1. Create a workday calendar.

   See: Using the Workday Calendar, Oracle Bills of Material User's Guide.

2. Update the calendar value in the Organizations Parameters window.

3. Navigate to MTH Project > MTH Setup > MTH Workday Shifts.

4. Run the ODI package MTH_PKG_WORKDAY_SHIFTS_SRC.

5. Search for the workday shifts in the MTH_WORKDAY_SHIFTS_D table.

To collect the equipment shifts

Prerequisite

Work day shifts must be collected for the plant.

1. Navigate to MTH Project > MTH Setup > MTH Workday Shifts.

2. Run the ODI package MTH_PKG_EQUIPMENT_SHIFTS_SRC.

3. Search for the shifts in the MTH_EQUIPMENT_SHIFTS_D table with entity type as Site and Equipment as two different entities.

To set up and collect resource requirements or resource usage from EBS

Prerequisite

You should have already collected work order and work order segment.

1. Query the discrete job.

   See: Finding Discrete Jobs, Oracle Work in Process User's Guide.

2. Run the ODI package to view the data collected in MTH_RESOURCE_REQUIREMENTS_F table.

To set up and collect material requirements and material consumed from EBS

Prerequisite

You should have already collected work order and work order segment.

1. Query the discrete job.

   See: Finding Discrete Jobs, Oracle Work in Process User's Guide.

2. Review the required quantities in the Material Requirement window by selecting the Components button.

3. Run the ODI package to view the data collected in MTH_PROD_MTL_CONSUMED_F table.

To set up and collect equipment schedule and resource instance schedule from EBS

Prerequisites

Collect work day shifts and equipment shifts to collect the equipment production schedules.

Collect work orders and work order segments.

1. Update the discrete job.

   See: Adding and Updating Operations, Oracle Work in Process User's Guide.

2. Update the date in the Resource Requirements window.

   See: Viewing Job and Schedule Operations, Oracle Work in Process User's Guide.

3. Select the Instance button to add the instances and save the record.

4. Run the ODI package to view the data collected in MTH_EQUIP_PROD_SCHEDULES_F table.

Setting Up E-Business Suite to run the Outbound Integrations for Discrete Flows

MOC outbound integration is designed to work with EBS and non-EBS target systems. MOC's outbound integration with ERP Systems enables you to automate the process of updating the enterprise and transaction system data with operational data captured from shop floor with minimal or no latency. The equipment transaction data such as status and output are collected from Shop floor, processed within MOC and then interfaced to Oracle EBS as Oracle WIP transactions.

The outbound integration's primary objective is to avoid the redundant effort of having to enter the transaction and reference data back into the enterprise and transaction systems. It also provides close integration with Oracle E-Business suite for Discrete Shop Floor Management and Flow Manufacturing applications.

Master and Reference data collection from EBS into MOC is enhanced to collect resource instances, operation and activity references so that there is no reconciliation issue of the references used in MOC and EBS for this integration.

MOC also collects the output and usage data from shop floor. The data is consolidated on a demand basis to perform the operation move, work order completion, scrap, and resource transactions. The data is pushed to the interface table for non-EBS consumption and then targets the EBS interface table for EBS transactions.

Prerequisites

• Export details profile should be set as Yes to collect the outbound integration data.

To set up tags in MOC for outbound integration after collecting inbound data

Create the tags and set up the tag mapping in MOC. See: Setting Up Tags

The types of tags required include:

• Output

• Status

• Item

• Work Order

• Work Order Segment

Note: Set up tags separately for equipment associated with each segment of the work order. Tag data should be populated for the first part of the ITEM_PK (item tag). The work order tag is the first part of the WorkOrder_PK. The work order segment tag is the first part of the WOSegment_PK.

To set up the tag based contextualization for the equipment collected from EBS

Note: Set up the tags separately for equipment associated with each segment of the work order.

• Set up equipment contextualization.

  See: Creating Equipment Contextualization Information.

To launch the interface managers

1. Launch a transaction manager from the list.

   See: To launch a transaction manager, Oracle Inventory User's Guide.

2. Select the Schedule button in the Launch Inventory Managers window.

   The Schedule window opens.

3. Enter the Start At and End At dates.

4. Enter the time in Re-run every field.

5. Click OK.

6. Repeat the steps for Material Transaction and Move Transaction in the Interface Managers window.

Setting Up Inbound Data Collection for Oracle Process Manufacturing (OPM)

Set Up and Collect the Organization Information

Prerequisites

• Set up MOC Locations under the source organization.

• Ensure that system_pk is the same as source system SID as defined in MTH_SOURCE_LOCATION.

• Set up Yield Subinventory and Yield Locator parameters for the outbound collection in OPM organization.

1. Set up the organization.

   See: Setting Up E-Business Suite to run the Inbound Integrations for Discrete Flow.

   Note: In the Inventory Parameters tab of the Organization Parameters window, select Process Manufacturing Enabled check box for process manufacturing organization in the Enabled Products & Features region.

2. Create the site in MOC and map the organization to that site.

   See: Setting Up E-Business Suite to run the Inbound Integrations for Discrete Flow.

Collect Resource Class and Resource Category

Note: In OPM flow, Resource Class is same as the Resource Group and Resource Category is same as the Department of MOC. Hence, Resource Category and Resource Class are collected into MOC as Department and Resource Group, respectively.

To create resource class

1. Navigate to the Resource Classes window.

   OPM Process Planning > Capacity Planning > Setup > Resource Classes

2. Enter the name of the resource class.

3. Save the record.

To create a generic resource

1. Navigate to the Resources window.

   OPM Process Engineer > Setup > Generic Resources

2. Enter a resource name in the Resource field.

3. Enter a description for the resource.

4. Enter the unit of measure in the Usage UOM field.

5. Enter a component class in the Cost Component Class field.

6. Clear the Capacity region fields.

7. Save and close the window.

To create a resource category and plant resource

1. Navigate to the Resource Information window.

   Process Engineer > Setup > Plant Resources

2. Query the resource that you created in the Resources window.

3. Enter the count number.

4. Enter the planning cost number.

5. Select a value from the Schedule Indicator LOV.

6. Enter the Usage UOM value.

7. Enter the capacity range values in the Range and To fields.

8. Enter the Ideal Capacity value.

9. Select the Capacity UOM value from the LOV.

10. Save the record.

Collect Resources

Note: Resources of type Machine and Person are only collected, for which Resource Class should be Machine for machine type resource and Labor for person type resource. The resources must be attached to a department.

1. Create a generic resource in the Resources window.

   Note: Create records with Machine and Labor in Resource Class field.

2. Create a plant resource by navigating to the Resource Information window.

   See: To create a resource category and plant resource.

3. Run the ODI Package MTH_PKG_RESOURCES_SRC.

Collect Resource Instances

Prerequisite

Create items of type Equipment and then generate a serial number for the equipment items.

See: Setting Up E-Business Suite to run the Inbound Integrations for Discrete Flow.

1. Navigate to the Resource Information window.

2. Query the resource created.

3. Click the Equipments button.

   The Resource Equipments window opens.

4. Enter the Equipment Item.

5. Save the record.

6. Select Scheduling to Instance from the Schedule Indicator LOV.

   The Instances button is now enabled.

7. Click the Instances button.

8. Enter the Start Date. This defaults to the system date.

9. Enter the End Date.

10. Click the Accept button.

    The Resource Instances window opens.

11. Enter the Serial Number, Equipment Item, and Equip Serial Number in the respective fields.

12. Save and close the window.

13. Run the ODI package MTH_PKG_EQUIPMENTS_SRC.

14. Query the created records in the MTH_RESOURCES_D and MTH_EQUIPMENTS_D tables.

Set Up Hierarchy between Equipment Entities and Resources and Equipments

Note: When the entities, resources and resource instances are set up, the hierarchies between equipment entities and resources and equipments are simultaneously set up.

1. Run the ODI package MTH_PKG_EQUIPMENT_HIERARCHY_SRC.

2. Query the equipment hierarchy and equipment denorm tables for the collected hierarchies.

Collect Inventory Items from EBS

Note: Items are collected if INVENTORY_ITEM_FLAG = Y, MTL_TRANSACTIONS_ENABLED_FLAG = Y, STOCK_ENABLED_FLAG = Y

To set up formula

1. Navigate to the Formula Details window.

   Formulator > Formulas

2. Enter the Formula name.

3. Enter a version for the formula.

4. Enter a description in the Description field.

5. Enter product details.

6. Select the Ingredients tab.

7. Enter the ingredient.

8. Enter quantity in the Quantity field.

9. Enter all the mandatory information for the product line.

10. Save the record.

11. Select Change Status option from the Actions menu.

    The Change Status window opens.

12. Change the status to Approved for General Use.

13. Click OK.

    See: Setting Up Formula Information, Oracle Process Manufacturing Product Development User's Guide.

To set up process operations

1. Navigate to the Process Operation Details:Activities window.

   Process Engineer > Process Operations

2. Enter the operation name, version, description, and the process quantity in the respective fields.

3. Enter the activity details in the Activities region.

4. Click the Resources button.

   The Process Operation window for the activity opens.

5. Select the resource from the Resource LOV.

6. Enter the Process Quantity and the Usage details.

7. Save the record.

8. Select Change Status option from the Actions menu.

   The Change Status window opens.

9. Change the status to Approved for General Use.

10. Click OK.

To set up routing

1. Navigate to the Process Routing Details window.

   Process Engineer > Process Routings

2. Enter a routing name.

3. Enter a description for the routing.

4. Enter the quantity in the Quantity field.

5. Select the unit of measure in the UOM LOV.

6. In the Routing Steps region, enter the operation step.

7. Enter the name of the operation, and the version for each routing step.

8. Save the record.

9. Select Change Status from the Actions menu.

   The Change Status window opens.

10. Change the status to Approved for General User.

11. Click OK.

To set up recipe

1. Navigate to the Recipe Details window.

   Process Engineer > Recipes

2. Enter a recipe name, its version, and description.

3. Enter a product name, formula, and the version.

4. Enter a routing and its version.

5. Select a unit of measure from the UOM LOV.

6. Save the record.

7. Click the Step/Material Association button.

   The Recipe: Step/Material Association window opens.

8. Select an operation step from the Step LOV.

9. Select a line from the Line LOV.

10. Save the record.

11. Select Change Status from the Actions menu.

    The Change Status window opens.

12. Change the status to Approved for General Use.

13. Click OK.

To set up validity rules

1. Navigate to the Recipe Details window.

2. Query the recipe that you created.

   Ensure that the status of the recipe is Approved for General Use.

3. Click the Validity Rules button.

   The Recipe: Validity Rule Details window opens.

4. Enter the Organization name.

5. Check the effective start date, unit of measure, and the product details.

6. Save the record.

7. Select Change Status from the Actions menu.

   The Change Status window opens.

8. Change the status to Approved for General Use.

9. Click OK.

To collect the EBS inventory items

1. Create an item and assign it to your organization.

   Note: Enable the Recipe Enabled and Process Execution Enabled check boxes in the Process Manufacturing tab of the Master Items window.

   See: Defining Items, Oracle Inventory User's Guide.

2. Navigate to MTH Project > MTH Setup > MTH Items.

3. Run the ODI package MTH_PKG_ITEMS_SRC.

4. Query the item in the MTH_ITEMS_D table.

Set Up and Collect Item Categories from EBS

Prerequisite

Update MTH_DIM_HIERARCHY table with the Category_set_name column.

1. Create an item category.

   See: Defining Categories, Oracle Inventory User's Guide.

2. Navigate to MTH Project > MTH Setup > MTH Items.

3. Run the ODI package MTH_PKG_ITEM_CATEGORIES_SRC.

4. Search for the new item category in the MTH_ITEM_CATEGORIES_D table.

Set Up and Collect the Item Hierarchy and Item Denorm from EBS

1. Navigate to MTH Project > MTH Setup > MTH Items.

2. Run the ODI package MTH_PKG_ITEM_HIERARCHY_SRC.

3. Validate the item hierarchy created for the items and item categories in MTH_ITEM_HIERARCHY table.

4. Search for the records in the MTH_ITEM_DENORM_D table.

Collect the Production Batches

Prerequisites

• Create items with recipe and formula information.

• Batch information such as resources, equipment hierarchies, and items should have already been collected.

• Sufficient on-hand stock of components and ingredients must be available before executing work orders or batches.

• OPM batch and batch steps should be in WIP released status.

To create batch details

1. Navigate to the Create Batch/Firm Planned Order window.

   Production Supervisor > Batch Details

2. Select the organization.

   Note: The organization much be Process Manufacturing Enabled.

   The Find Batches window opens.

3. Click the New button.

   The Create Batch/Firm Planned Order window opens.

4. Select a recipe from the Recipe LOV and the version of the recipe from the Version LOV.

5. Select the Product Output tab.

6. Select a product from the Product LOV.

7. Enter the product quantity and the unit of measure.

8. Click OK.

   The Batch Details window opens listing the new production batch with status as Pending.

9. Select the Release option in the Actions menu.

   The Release Batch dialog box opens.

10. Click OK.

11. Navigate to Batch Steps window.

    Production Supervisor > Batch Steps

12. Select a step.

13. Select the Release Step option in the Actions menu. Optionally, you can also complete the batch from the Actions menu.

14. Navigate to MTH Project > MTH Transactions > MTH Production Schedules

15. Run the ODI package MTH_PKG_PRODUCTION_SCHEDULES_SRC.

16. Query the record in the MTH_PRODUCTION_SCHEDULES_F table.

Set Up and Collect Production Batches associated with Sales Order reservations from EBS

Note: Only those sales orders associated with an OPM batch are collected. Any modification done to the reservation in EBS will automatically update the record in MOC.

To create an OPM batch associated with sales order reservation

1. Create a sales order of Order Type Standard(Process).

   See: Defining Sales Order Main and Other Header Information, Oracle Order Management User's Guide.

2. Attach the sales order to an OPM batch.

   1. Navigate to the Item Reservations window.

      Inventory Super User (Process Operations) > On-hand, Availability > Reservations.

      The Item Reservations window opens.

   2. Create a sales order with the Demand Source Type as Sales Order and the Supply Type as Job or Schedule (Process Batch).

      See: Creating Reservations, Oracle Inventory User's Guide.

3. Navigate to MTH Project > MTH Transactions > MTH Sales Orders.

4. Run the ODI package MTH_PKG_WORKORDER_RESERVATION_SRC.

5. Search for the created sales order in the MTH_WO_SALES_ORDERS_F table.

   Note: You can also update and delete work orders associated with sales order reservations.

Collect the Production Batch Segments

Prerequisites

• Set up process operations for recipe.

• Production batches should have already been collected.

1. Navigate to the Batch Details window.

   Production Supervisor > Batch Details

   The Batch Details window opens.

2. Query the batch that you created.

3. Select the Steps button.

   The Batch Steps window opens.

4. Review the batch step and operation details.

5. Run the ODI package MTH_PKG_PRODUCTION_SEGMENTS_SRC to collect the production segments.

6. Review the data in the MTH_PRODUCTION_SEGMENTS_F table.

Collect the Production Batch Sub-segments

Prerequisites

• Set up process operations for the recipe for which the batch is created.

• Associate activities (sub-segments) with each operation (batch steps).

• Batch and batch segments should have already been collected.

1. Navigate to the Batch Steps window.

   Production Supervisor > Batch Details > Steps (Button)

2. Select the Activities button.

   The Step Activities window opens.

3. Review the batch step activities.

4. Run the ODI package MTH_PKG_PRODUCTION_SUB_SEGMENTS_SRC to collect the production sub-segments.

5. Review the data collected in the MTH_PROD_SUB_SEGMENTS_F table.

Create Workday Shifts from UI

Prerequisites

• Set up the profile option MTH: Shifts Setup as MOC.

• Your plant should have been created and mapped to the OPM organization.

1. Navigate to the Sites Summary window.

   The Sites Summary window opens.

2. Select the Entity Shift Setup tab.

   The Entity Shift Setup window opens.

3. Select the plant for which process manufacturing is set up from the Site LOV.

4. Enter the Start Date and the End Date.

5. Select the Generate button.

6. Choose Yes in the Confirmation window.

Create Equipment Shifts from UI

Prerequisites

• Set up the profile option MTH: Shifts Setup as MOC.

• Your plant should have been created and mapped to the OPM organization.

• Resources and equipments (resource instances) must have been created and collected in MOC for the OPM organization.

Create workday shifts from UI.

Note: Generating workday shifts for the plant will automatically generate the shifts for all its child entities in that plant.

Set Up and Collect Resource Requirements or Resource Usage from EBS

Prerequisites

• Set up process operations for the recipe for which the batch is created.

• Associate activities with each operation.

• Batch, batch segments, and batch sub-segments should have already been collected.

1. Navigate to the Step Resources window.

   Production Supervisor > Batch Details > Steps (B) > Batch Steps > Activities (B) > Step Activities > Resources (B)

   The Step Resources window opens.

2. Review the resource details.

3. Run the ODI package MTH_PKG_RESOURCE_REQUIREMENTS_SRC to collect the resource requirements.

4. Review the data collected in the MTH_RESOURCE_REQUIREMENTS table.

Set Up and Collect Material Requirements or Materials Consumed from EBS

Prerequisites

• Set up Step/Material Association for the recipe for which the batch is created.

• Associate ingredients and final product with the operation steps.

• Batch, batch segments, and batch sub-segments should have already been collected.

1. Query the batch created in the Find Batches window.

2. Review the material requirements information in the Ingredients, Products, and By-Products tabs.

3. Run the ODI package MTH_PKG_MTL_CONSUMED_SRC to collect the material requirements.

4. Review the data in MTH_PROD_MTL_CONSUMED_F table.

Set Up and Collect Equipment Schedule or Resource Instance Schedule from EBS

Prerequisites

• Workday shifts and equipment shifts must have been already collected.

• Production batch, batch segments, and batch sub-segments should have been already collected.

• Planned_End_Date of a batch is determined based on the process operations and process routing set up of a recipe or product.

1. Query the batch already created.

2. Review the Plan Start Date and Plan Completion Date of each resource in the batch in the Step Resources window.

3. Run the ODI package MTH_PKG_EQUIPMENT_PROD_SCHEDULE_SRC to collect the equipment production schedules.

4. Review the data collected in the MTH_EQUIP_PROD_SCHEDULES_F table.

   Note: Plan Start Date and Plan Completion Date of each resource in the batch should be collected as Schedule_from_date and Schedule_to_date in the MTH_EQUIP_PROD_SCHEDULES_F table.

Setting Up Tags for Outbound Integration after Collecting Inbound Data for OPM

Create Tags and Set Up the Tag Mapping in MOC

See: Setting Up Tags.

The types of tags required include:

• Output

• Status

• Item

• Work Order

• Work Order Segment

Note: Set up tags separately for equipment associated with each segment of the work order.

1. Tag data should be populated for the Status and Output tags along with the item, work order and work order segment as the three data elements are mandatory in the tag based contextualization.

2. Value for the item tag should be populated in the first part of the ITEM_PK. Similarly, value for the work order tag should be populated in the first part of the WorkOrder_PK and value for the work order segment tag in the first part of the WOSegment_PK.

Set Up the Tag Based Contextualization for the Equipment Collected from EBS

• Set up equipment contextualization.

See: Creating Equipment Contextualization Information.

Viewing Classifications for Shop Floor Entities

Manufacturing Operation Center entities are grouped into classifications, and associated to attributes that define specific characteristics for items in your organization. MOC supports item, equipment, work order, user-defined entities, batch operation, and other miscellaneous entities:

• Equipment classifications can designate the machine or plant location where manufacturing activity is performed on the shop floor.

• Item entity classifications can be group by categories such as product or line type, ABC classes, or cost structure.

• Other entity classifications are created on the Extensible Attributes Workbench per your requirements for miscellaneous categories in your organization.

• Work Order classifications designate Work in Process work order types, choices are discrete or process types.

To view entity classifications

1. Navigate to the specific Entity page.

   MOC provides Entity: Batch Operation, Entity: Equipment, Entity: Item, Entity: Others, Entity: User Defined and Entity: Work Order.

   There are two tabbed regions: Classifications and Attributes. The page opens with all the classification values displaying in the search results table region. Classifications are created in several different areas depending on the entity type, see: Setting Up Extensible Attributes for MOC Entities

   You can filter your list by entering a value in the Classification field and selecting Go.

   

2. Select a value link in the Classification column to navigate to the Classifications Details page.

   This page displays the following values in the Basic Information and Other Details regions:

   • Classification—name for this grouping

   • Entity—type of entity

   • Classification Code

   This page enables you to navigate to associated attribute groups and attribute pages for this item classification.

   

To create and update Others entity classifications

1. Navigate to the Entity: Others page.

   The page opens with all the Classification values displaying in the search results table region.

   

2. Select Create to create a new classification record.

3. On the Create Classification page— enter values in the Name and, optionally, Description fields.

   

4. Select Apply to save your work.

To update an Other entity classification record

1. Navigate to the Update Classification page.

2. Change the appropriate information in the Name and Description fields.

3. Select Apply to save your work.

Related Topics

Setting Up Extensible Attributes for MOC Entities

Viewing and Creating Attribute Group Data for Entities

Viewing and Creating Attribute Pages for Entities

Viewing and Creating Attribute Group Data for Entities

Manufacturing Operation Center Equipment entities are associated to attributes that capture specific characteristics for functional areas in your organization. Similar attributes can be categorized in an attribute group, and you can define an unlimited number of attribute groups that fit your business environment.

To view all attribute groups created for specific entities

1. In the specific Entity page, select the Attributes tabbed region.

   This includes the Entity: Batch Operation, Entity: Equipment, Entity: Item, Entity: Others, Entity: User Defined, and Entity: Work Order pages.

   All the existing attribute groups for the specific entity type selected appear in the results table.

   You can filter the display by using a combination of values and conditional qualifiers in the following fields: Attribute Group Display, Attribute Group Description, Attribute Group Descriptions, Behavior, Business Entity, Database View, and Internal Name.

   

   This page enables you to select:

   • A record link in the Display Name column to navigate to the Attribute Group Details page

   • Create to navigate to the Create Attribute Group for Equipments page

   • Copy to create a new attribute group using information in an existing record

To view and add attribute groups to a shop floor entity

1. On the specific Entity Classification Details page, select Attribute Groups to display the Attribute Groups for an entity page.

   All attribute groups associated to this equipment entity appear.

   You can filter the results by using values for Display Name or Description. This page enables you to:

   • Navigate to the Attribute Group Details page.

     Select an attribute group value link.

   • Add attribute groups to this specific entity.

   

2. Select Add Attribute Groups to associate attribute groups to the entity selected.

   Depending on the entity is selected, the following pages appear:

   • Add Attribute Groups for Batch Operation

   • Add Attribute Groups for Equipment

   • Add Attribute Groups for Item

   • Add Attribute Groups for Others

   • Add Attribute Groups for User Defined Entities

   • Add Attribute Groups for Work Order

   On the Add Attribute Groups page you can filter the display by using a combination of Attribute Group Type, Behavior, Display Name, Description, and Internal Name.

   

3. In the results table, select the attribute group records you want to add to the selected entity.

4. Select Apply to save your work.

   The records appear on the refreshed Attribute Groups for this entity page.

Related Topics

Setting Up Extensible Attributes for MOC Entities

Viewing Classifications for Shop Floor Entities

Viewing and Creating Attribute Pages for Entities

Viewing and Creating Attribute Pages for Entities

Attribute pages can be created for each entity for ease of use in data entry and viewing. You can assign multiple attribute pages to a specific entity attribute group. For each page, you can choose the attributes displayed and the specific order listed.

To view and create Attribute Group Pages

1. Select Pages to display attribute pages created for this entity classification.

   This includes Batch Operation Pages, Equipment Pages, Items Pages, Others Pages, User Defined pages, and Work Order Pages.

   The attribute group pages for the specific entity selected appear in the results table.

   You can search records on the entity Pages by Display Name or Description.

   

2. Select Create to create a new page for this entity.

   The Add Pages for the select entity type appears.

   

3. Enter the following data in the Basic Information region:

   • Display Name—name displayed on the page.

   • Description—a description of the attribute category.

   • Internal Name—internal name for the page, this value cannot be updated once a page has been created.

   • Sequence—sequence number for each page associated with an attribute group, the sequence number determines the order pages are listed.

4. In the Attribute Groups region, select Add Another Row to add attributes groups to this page. To add an existing attribute group:

   • Enter a Sequence number

   • Select an existing Display Name value

5. Select Apply to save your work.

   The attributes for this entity, and the display sequence appear in the Pages region.

Related Topics

Setting Up Extensible Attributes for MOC Entities

Viewing Classifications for Shop Floor Entities

Viewing and Creating Attribute Group Data for Entities

Archiving and Purging Data

Use the archive and purge concurrent programs to remove data you no longer use on a day-to-day basis from the tables where current data exists. When you archive, you add data copied from production tables into archive tables based on the criteria provided, then delete the data from the production tables. When you purge, you delete data that meets the provided criteria from the archive tables. Archiving improves database performance by moving historical data from the production tables into archive tables. You can not recover data after purging except from backups of the database files.

You can archive and purge extensible attributes data, which includes data stored in the following tables:

• MTH_TAG_READINGS

• MTH_EQUIPMENTS_EXT_B

• MTH_EQP_EXT_SUMMARY

Specification data is not archived or deleted. The Process Engineer Dashboard includes archived data.

To run the concurrent program MTH: Archive Transaction Data

1. Navigate to the Parameters window.

2. In the Site field, select a site (plant) for which to archive data.

3. In the Equipment field, optionally select the equipment for which to archive data.

   Leaving this field blank archives the data for all equipment at the site.

4. In the Entities field, leave the default value of Extensible Attributes. You can not change this value.

5. In the Archive Before Date field, enter the date before which you want to archive.

   For example, if you enter 01-Jan-2017, you will archive all data prior to and including 31-Dec-2016.

6. Optionally, in the Batch Size (Days) field, enter the number of transaction days of data processed at a time. The default value is 10,000.

   For example, if you select 10 days of records and specify a batch size of 2, the concurrent program runs 5 times before completion. This can improve system performance and error handling.

7. Click OK.

8. Click Submit.

9. Note the Request ID number.

10. Choose View from the menu and select Requests to view the status of your request in the concurrent program manager.

11. When your request ID is complete with a Status of Normal, click View Details to view the details of the run.

To run the concurrent program MTH: Purge Archived Data

1. Navigate to the Parameters window.

2. In the Site field, select a site (plant) for which to purge archived data.

3. In the Equipment field, optionally select the equipment for which to purge data.

   Leaving this field blank purges the data for all equipment at the site.

4. In the Entities field, leave the default value of Extensible Attributes. You can not change this value.

5. In the Purge Before Date field, enter the date before which you want to purge.

   For example, if you enter 01-Jan-2017, you will purge all data prior to and including 31-Dec-2016.

6. In the Batch Size (Days) field, enter the number of transaction days of data processed at a time.

   For example, if you select 10 days of records and specify a batch size of 2, the concurrent program runs 5 times before completion. This results in better system performance and error handling.

7. Click OK.

8. Click Submit.

9. Note the Request ID number.

10. Choose View from the menu and select Requests to view the status of your request in the concurrent program manager.

11. When your request ID is complete with a Status of Normal, click View Details to view the details of the run.