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 the Part 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

The HANDS_ON_TIME value from 42Q will be updated in the WO resource field, only for the mapped resources. 

 

Figure 13: Costing Tab

 

Figure 14: Quantities Tab 

The HANDS_ON_TIME value from the WipMove XML will be converted from seconds to hours and posted in the resource field.

If the resources are not mapped in the lookup form, then the standard resource value will be updated in the WO.

 

Figure 15: 42Q Attribute Lookup form

To access, navigate to Manufacturing Manager> Bill of Materials > Routing > Standard Operations > Click the form button Operation Resources.

 

Figure 16: Manual Charge Type

 

Figure 17: Main Tab

In the WO Resource field

 

Figure 18: Main Tab Setup

 

Figure 19: Quantities Tab

If ‘Post Hands on time’ is not enabled, users should manually enter the resource value. Thus, no action will be taken by the adapter for the ‘HANDS_ON_TIME’ sent from the 42Q WIP move.

 

Figure 20: Post Hands on time check box

Before entering the values manually,

 

Figure 21: Resource Requirement Coasting Tab

 

Figure 22: Resource Requirement Quantities Tab

Enter the values manually for resources
To access, navigate to Order Management Super User, Vision Operations(USA) > WIP> Resource Transactions.

 

Figure 23: Transaction Tab

In the WO Resources:

 

Figure 24: Resource Requirement Quantities Tab

 

42Q API Program Defaults Form

1. The 42Q URL field is used to send each outbound transaction from Oracle.
2. After the WO creation, the preliminary validation will happen in the table XX42Q_MDSWIP_DEFAULT_PARAMS by using fields such as Org ID, Application, and Project ID.
3. Only after the preliminary validation, the adapter will allow inbound and outbound transactions.
4. To access, navigate to 42Q Admin(OUR) > 42Q API Program Defaults.

 

Figure 25: 42Q API Program Defaults Form

 

FIELD NAME	DATA TYPE	DESCRIPTION	MANDATORY
Application	Varchar	42QMES (This is a default value for this interface)	Yes
Organization Code	Varchar	This is the Discrete Job (DJ) Inventory Organization code considered for interfacing with 42QMES Job Processing. The adapter will pick the Discrete Jobs, created under this inventory organization only.	Yes
Project ID	Varchar	Customer Code | Organization code	Yes
Activation Date	Date	Work Orders created from this date are only considered for interfacing with 42QMES.	Yes
Scrap Account	Varchar	This is the inventory scrap account that will be considered by the adapter when a work order quantity has to be scrapped or WIP move transaction received has a scrap transaction.	Yes
ORG Default	Varchar	INCLUDE (This is a default value)	Yes
Completion Subinventory	Varchar	The sub-inventory where the completed assemblies should be available when WIP completion transactions are processed.	Yes
Completion Locator	Varchar	The sub-inventory locator where the completed assemblies should be available when WIP completion transactions are processed.	Yes
Backflush Subinventory	Varchar	This is the supply sub-inventory code for backflush of components.	No
Backflush Locator	Varchar	This is the supply sub-inventory locator for backflush of components.	No
Customer Code	Varchar	Enter the Customer code setup/provided by 42Q.	Yes
Complete without all Push Mat	Varchar	If the check box is enabled, the adapter will bypass the PUSH components validation while completing the WIP job quantity. Thus, the work orders can be completed without PUSH items material issues.	No
Post Hands On Time	Varchar	If the check box is enabled, It Identifies all the resource transactions whose charge type is “Manual” and whose from operation and resource codes are set up in the custom Lookup table. If disabled, it ignores the procedure call to process hands on time.	No
Online Call for Route/Component	Varchar	If the checkbox is enabled, an online call will be triggered. If the checkbox is disabled no online call will not be triggered.	Yes
Online call URL	Varchar	Outbound URL for online web service call for verifying if the job quantity can be decreased or not in Oracle.	Yes
42Q URL	Varchar	The endpoint URL for all the outbounds from Oracle.	Yes
Notify User	Varchar	User Details	No
Notify Responsibility	Varchar	Responsibility Details	No
Notify Program	Varchar	Calls the customer’s ERP program details	No
Serial validation Flag	Varchar	-	No
Customer Intent Enabled	Varchar	-	No

 

Schedule Concurrent Managers

This action is intended for Oracle DBA/SysAdmin only, once this option is selected, follow the next steps: 

Setting up of XX42Q concurrent managers 

1. Navigate to Inventory > Setup > Transactions > Interface Managers

 

Figure 26: Navigation to Interface Managers

       2. Select Material Transaction > Tools 

       3. Ensure the below Managers are active.

 

Figure 27: Interface Managers 

 

Schedule the below Concurrent programs from 42Q Admin(OUR)

1. 42Q WIP Job Extract and Webservice Outbound 
2. 42Q Shipment Notification Extract and Webservice Outbound 
3. 42Q WIP Move and Material Issue Inbound Processing with ACK

 

 Scheduling the Concurrent Programs

1. Navigate to the respective responsibility where the concurrent program is to be scheduled exists.
2. Then, navigate to View > Requests and click on Submit a New Request

Figure 28: Submitting a New Request
 

Figure 29: New request confirmation

 

     3. Enter the concurrent program name to be scheduled and the respective parameters and click Schedule.
 

Figure 30: Run the Request
 

     4. A Schedule window will appear. 

 

Figure 31: Schedule Window 

 

    5. The user has to specify the interval/frequency that requires the program to run and click OK. 
    6. Then, Click on the Submit.

 

Figure 32: Submit the schedule