Check this out.
I would first add an updateable dashboard to a tracker...then add the tracker to MES (following the directions below).
PAGE NO:
7753ESC
PROBLEM DESCRIPTION:
How do I add a Tracker to one of the MES blank buttons?
This topic gets involved, but by all means, if you have permissions to do customizations, you can assign a Tracker to the blank buttons.
THINGS YOU NEED TO KNOW:
==============================
So what are the pertinent properties?
----------------------------------------------------------
" EpiBinding: The message that appears when the button is clicked. Right now, a message simply says "not used". Clear this property field.
" Text: The label of the button. This value is blank because the button is blank. For this example, we will open a custom dashboard that reports booking information. Type Bookings Dashboard. If you can also see the MES menu, you will notice that the label now appears on the button.
What is a GUID?
--------------------------
A GUID (pronounced GOO-id) is a unique and long combination of letters and numbers for every visible entity in Vantage. A GUID has been assigned to the button you chose, and it cannot be changed. You will note that this property was grayed out for the button.
What is the menu ID?
----------------------------------
The menu ID is the unique ID assigned to a menu item, in the eyes of Epicor. This can be determined in Menu Maintenance.
From System Management - Utilities, select Menu Maintenance. In this case the Serial Number Tracker is found on menu SVG01052.
What does the script portion do?
----------------------------------------------------
The purpose of the script portion of the button programming is to assign the GUID, and hence the button, to the menu ID, and hence the the desired Epicor program. We will assign the GUID.
Using the Event Wizard to create a Load Event.
---------------------------------------------------------------------------
Here you add a form load event that will enters a unique procedure, btnLaunchTracker, that ties together both the GUID and the menu ID. The GUID comes from the properties of the button that you clicked. You will need to replace the guid with the one associated to the button that you are modifying. Take note that we also enabled this procedure - in effect, enabling the button.
TIME TO DO THE CUSTOMIZATION
==============================
First you need to create a MES Developer Icon
====================================
* Make a copy of your MES icon and rename it to something like MES Developer
* Then right click on it and choose Properties
* In the Target field locate where it shows -MES and change it to -MESC.
Creating the Customization
------------------------------------------
1) Launch MES in customization mode by using the shortcut for MES Developer described above.
2) Login in to MES
3) Right-click somewhere on the form, and in the context menu, select Customization and bring up the Tools Dialog form.
4) On the Script Editor set the VB radio button.
5) On the MES menu navigate to a tab that has a blank button. I will use the Supervisor tab in this illustration.
6) Click on a blank button. I've choosed to use the 3rd button on the right which is button10.
7) Make a note of the EpiGuid number, you'll need it latter.
8) Clear the EpiBinding
9) Set the Text property. Since we are going to run the Serial Number Tracker I set it to "SN Tracker".
10) Set the Visibility property to true.
11) Set the Enabled property to true.
Now for the Script work
-------------------------------------
So far, so good. We have cosmetically applied the necessary trait to the button - we have enabled it, given it a label, and made it exist in the MES customization framework. Now, we have to get to the "nitty-gritty" of the script, which serves to assign the button with the desired program.
12) In the Customization Tools Dialog box, click the Wizards tab then choose the Form Event Wizard.
13) Set the selected event type to "Load" and click the right arrow. You will see the following code in the View/Edit Event handling code window.
Private Sub MESMenu_Load(ByVal sender As object, ByVal args As EventArgs) Handles MESMenu.Load
'//
'// Add Event Handler Code
'//
End Sub
Add these two lines to the code before the End Sub line
btnLaunchTracker = CType(csm.GetNativeControlReference("799a9b4c-7f77-4710-8468-603516ea244b"), EpiButton)
btnLaunchTracker.Enable = True ' //Use for 9.04.
btnLaunchTracker.ReadOnly= False '// Use for 9.05
When your done the code will be:
Private Sub MESMenu_Load(ByVal sender As object, ByVal args As EventArgs) Handles MESMenu.Load
'//
'// Add Event Handler Code
'//
btnLaunchTracker = CType(csm.GetNativeControlReference("799a9b4c-7f77-4710-8468-603516ea244b"), EpiButton)
btnLaunchTracker.Enable = True ' //Use for 9.04.
btnLaunchTracker.ReadOnly= False '// Use for 9.05
End Sub
HINT: Be sure to set the guid (799a9b4c-7f77-4710-8468-603516ea244b) to the one that matches your button.
14) Click the Update All Event Code button.
15) In the Customization Tools Dialog box, click the Script Editor tab. A script appears that controls the logic for the entire customization. It includes declarations, calls to different logic, this, that, the other. Don't worry about understanding what's there. (I don't understand it all myself.)
16) Now we need to paste some lines of code into the Script. Your first questions is WHERE?
Take note of the last line: End Module. This must remain the last line. Take note of the second to the last line: End Sub. That line must stay where it is, as well. In other words, End Sub and upward must stay together, and End Module must remain the very last line. So: We are interested in the gap between the last End Sub line and the last End Module line.
17) Copy the following lines and paste them into the script editor.
Private Sub btnLaunchTracker_Click(ByVal Sender As Object, ByVal args As EventArgs ) Handles btnLaunchTracker.Click
ProcessCaller.LaunchForm(MESMenu, "SVGO1052") '<=== enter your menu Id here
End Sub
Hint: What does the custom script do? The script enters a unique click event, btnLaunchTracker_Click, that ties together both the GUID and the menu ID. The menu ID comes from the entry for the desired program in Menu Maintenance. It will almost certainly have to be replaced by you.
18) Scroll to the top of the script and you'll find until you find the following code:
'// ** Wizard Insert Location - Do Not Remove 'Begin/End Wizard Added Module Level Variables' Comments! **
'// Begin Wizard Added Module Level Variables **
'// End Wizard Added Module Level Variables **
'// Add Custom Module Level Variables Here **
Add the following line of code right after the Add Custom Module Level Variables Here line
Private WithEvents btnLaunchTracker As EpiButton
When your done the code will be:
'// ** Wizard Insert Location - Do Not Remove 'Begin/End Wizard Added Module Level Variables' Comments! **
'// Begin Wizard Added Module Level Variables **
'// End Wizard Added Module Level Variables **
'// Add Custom Module Level Variables Here **
Private WithEvents btnLaunchTracker As EpiButton
19) When you have completed the above the Script code should look like:
'//**************************************************
'// Custom VB.NET code for MESMenu
'// Created: 10/14/2009 12:14:51 PM
'//**************************************************
Imports System
Imports System.Data
Imports System.Diagnostics
Imports System.Windows.Forms
Imports System.ComponentModel
Imports Microsoft.VisualBasic
Imports Epicor.Mfg.UI
Imports Epicor.Mfg.UI.FrameWork
Imports Epicor.Mfg.UI.ExtendedProps
Imports Epicor.Mfg.UI.FormFunctions
Imports Epicor.Mfg.UI.Customization
Imports Epicor.Mfg.UI.Adapters
Imports Epicor.Mfg.UI.Searches
Imports Epicor.Mfg.BO
Module Script
'// ** Wizard Insert Location - Do Not Remove 'Begin/End Wizard Added Module Level Variables' Comments! **
'// Begin Wizard Added Module Level Variables **
'// End Wizard Added Module Level Variables **
'// Add Custom Module Level Variables Here **
Private WithEvents btnLaunchTracker As EpiButton
Sub InitializeCustomCode()
'// ** Wizard Insert Location - Do not delete 'Begin/End Wizard Added Variable Initialization' lines **
'// Begin Wizard Added Variable Initialization
'// End Wizard Added Variable Initialization
'// Begin Wizard Added Custom Method Calls
'// End Wizard Added Custom Method Calls
End Sub
Sub DestroyCustomCode()
'// ** Wizard Insert Location - Do not delete 'Begin/End Wizard Added Object Disposal' lines **
'// Begin Wizard Added Object Disposal
'// End Wizard Added Object Disposal
'// Begin Custom Code Disposal
'// End Custom Code Disposal
End Sub
Private Sub btnLaunchTracker_Click(ByVal Sender As Object, ByVal args As EventArgs ) Handles btnLaunchTracker.Click
ProcessCaller.LaunchForm(MESMenu, "SVGO1052")
End Sub
Private Sub MESMenu_Load(ByVal sender As Object, ByVal args As EventArgs)
'Add Event Handler Code
btnLaunchTracker = CType(csm.GetNativeControlReference("799a9b4c-7f77-4710-8468-603516ea244b"), EpiButton)
btnLaunchTracker.Enable = True ' //Use for 9.04.
btnLaunchTracker.ReadOnly= False '// Use for 9.05
End Sub
End Module
20 ) Now save your customization by selecting File > Save on the Customization Tools Dialog.
From:
vantage@yahoogroups.com [mailto:
vantage@yahoogroups.com] On Behalf Of Rob Bucek
Sent: Thursday, January 31, 2013 5:22 PM
To:
vantage@yahoogroups.com
Subject: RE: [Vantage] E9 - Assigning BIN locations
Part entry is not accessible through the normal mes license... not sure if anyone has found a slick custom work around..
Rob Bucek
Production Control Manager
PH: (715) 284-5376 ext 311
Mobile: (715)896-4832
FAX: (715)284-4084
[cid:
1.234354861@...<mailto:1.234354861%40web65412.mail.ac4.yahoo.com>]
http://www.dsmfg.com/>
(Click the logo to view our site)
http://www.dsmfg.com/>
From:
vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com> [mailto:
vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>] On Behalf Of Anthony Gercar
Sent: Thursday, January 31, 2013 3:55 PM
To:
vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
Subject: RE: [Vantage] E9 - Assigning BIN locations
I know you can add a primary bin in part entry... not sure if you can in MES.
From:
vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com> [mailto:
vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>] On Behalf Of Tim Vonderhaar
Sent: Thursday, January 31, 2013 4:51 PM
To:
vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>
Subject: [Vantage] E9 - Assigning BIN locations
Is there a way out of the box via MES or handheld to assign a primary bin location for a part?
Tim
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]