42Q-MES0190-A Oracle Adapter Configuration Guide

         

Tools
Oracle Adapter Configuration Guide
Version MES15.80
Revision A1

 

 

Introduction

This guide is designed to assist the users with the Post-Installation steps after installing the XX42Q Oracle Adapter.

Post Installation Setup

After installation, users need to set up the Attribute Lookup form and API program defaults form, and then schedule the Concurrent Managers.

42Q Attribute Lookup Form

• Custom attributes are used to send additional fields to 42Q in the WO create/change XML in addition to the standard fields that are mapped in the 42Q Define Discrete Job form.
• The 42Q Attribute Lookup form maps the custom attributes with the 42Q Attribute Name. 
• As it is plant-specific, if the customer is required to map the same field for different organizations, they should add them in the new line.
• 42Q Attribute lookup form is also used to map the additional attribute information that 42Q sends to the ERP in the WIP or Mat move transaction.
• HANDS_ON_TIME is used as a custom attribute in the lookup form as it sends the time taken to complete each operation during the WIP Move in 42Q.
• Users can add, delete, or update the required attribute tags as required.

Figure 1: 42Q Attribute Lookup

 

 

FIELD NAME	DATA TYPE	DESCRIPTION	MANDATORY
Lookup Name	Varchar	Type of attribute	Yes
Plant	Varchar	The Organization in which the particular WO has been created.	Yes
Customer Attribute Name	Varchar	The name of the attribute.	Yes
Attribute Value	Varchar	The field ID that is to be included. Users are allowed to select only from the predefined list of values. By using this field ID, the values are fetched for the custom attribute name.	Yes
Enabled	Checkbox	Enable/Disable an XML attribute/tag from appearing in the WO outbound XML	No

 

The 42Q Attribute Lookup Form maintains four types of attributes depending on the location of the field. They are as follows:

WO_ATTRIBUTE

1. The fields are available at the WO header level.
2. To access navigate to 42Q Admin(OUR) > Discrete Jobs form.
3. Enter the WO number and click Find. 

Figure 2:  Discrete Jobs Form

 

WO_PART_ATTRIBUTE

1. The fields that are available in the Organization item form for the assembly item, are used in the work order.
2. To access navigate to Inventory > Items > Organization Items.
3. Enter thePart number, and click Find.

Figure 3: Organization Item Form

 

WO_BOM_ATTRIBUTE

1. The fields that are available and used in BOM are specific to the work order.
2. To access navigate to 42Q Admin(OUR) > 42Q Define Discrete Jobs form 
3. Enter the WO number, click Find, and click Components.

Figure 4: Components- Discrete Jobs form

Figure 5: Material Requirement 
 

COMPONENT_PART_ATTRIBUTE

1. It contains the fields that are available in the Organization item form for each component used in the work order.
2. To access navigate to Inventory > Items > Organization Items 
3. Enter the Component Item, and click Find.

Figure 6: Inventory tab

       4. To find the Field name and value for all the forms, Select the field and navigate to Help > Diagnostics > Examine. 

Figure 7: Examine the Field name and Value

HANDS_ON_TIME

1. This attribute mapping is used to select the HANDS_ON_TIME from XML and post it in the mapped resources for each operation.
2. HANDS_ON_TIME in the Lookup form consists of Organization, Operations, and Resources which are displayed in the Plant, Custom Attribute Name, and Attribute Value fields.

Figure 8: 42Q Attribute Lookup Form

 

      3. While the 42Q performs WIP moves, each operation contains different resources.
      4. The HANDS_ON_TIME  value of the resources has been updated based on two charge types: Wip Move and Manual.

 

Figure 9: Charge types
 

• If the Charge type is WipMove, no action will occur from the adapter. The oracle will post the standard WO resource value. To access, navigate to Manufacturing Manager> Bill of Materials > Routing > Standard Operations > Click the form button Operation Resources.

 

Figure 10: WIP Charge type

 

• If the Charge type is Manual, the adapter will check for the toggle ‘Post Hands on Time’ in the 42Q API Program default form.

 

Figure 11: Post Hands on Time 

 

If ‘Post Hands on Time’ is enabled, the adapter will check whether the resources are mapped in the lookup form.

 

Figure 12: 42Q Attribute Lookup form