Mike
Forum Replies Created
-
Brandon– the service is maxqprod, userid is QCTL (for production), and password is quantum
Hope that helps !
-
https://www.componentcontrol.com/about/authorized-partner-program/value-added-partners
Yes, Oracle is not cheap, the licensing changed on SE2, a lot more expensive. Finding an Oracle partner that fully understands your use case is not easy to do either.
My own personal view, I don’t see NUP (User Licensing) being the right choice unless you can guarantee who and what connects to your database(s). That is all human and non-human.
If you are going to open up a customer portal or use APIs to connect to other people/devices, then how would you get the NUP requirement right?
-
We purchased it a couple of years ago.
So, it is expensive, you also need to pay for a monthly maintenance fee as with any other module/add-on. It also comes with some connection licenses as far as I can remember, maybe 10?
There is a fairly large set of standard APIs available, I know we have added many over the last few years.
Maybe request an up to date list of APIs to see if they have what you want? If the list is a large as it should be now, that licence represents good value for the amount of development time (cost) within it, that’s just my opinion …
It is my understanding that Component Control do not support you making your own API’s without them or an authorized partner being part of that process.
If you do make your own unauthorized API’s you will not get any technical or upgrade support for them, as Quantum changes over time, you can expect that any unauthorized API’s could stop working at any time.
Worst case you might not notice, do an upgrade and then find things just don’t work properly. Understandably, with zero support from Component Control. Then what do you do?
That could be a risk to your business if you rely on those API’s to operate.
My mandate to developers here is that data being written to Quantum should be done via an authorized API wherever possible, always if it is a new record in a table.
Yes you can write your own or you could get an unauthorized third party to do it for you, but that will be a long term risk to your business operations that you need to consider carefully.
-
Yes we have the same issue. For every integration.
The argument would be that the payment made for the module does not include the user access license.
There is no issue with that – provided it is made clear when you purchase the module, that it potentially needs another $2.4k user license, not simply the module license cost
-
You probably do need more in depth instructions, which if required a developer here may be able to provide you help with.
If anyone needs that let me know and I will get someone to help you.
This new imaging maybe controlled by Component Control via licensing for 3rd party access. Please contact tech support to confirm.
We already, maybe, have access/authorization via our API module, our work is also supported by a developer from Component Control.
If you are using non-approved third party support or developers, you may find you need to do something to get the required access key for this feature. This may or may not be true – I cannot be 100% on this so you will need to check…
*** Update ***
You will need to contact Component Control for authorization to use any third party access to the new imaging module.
-
Randy- the SDF columms/fields are not changeable in the Quantum interface. Only the UDF fields can be modified. The SDF fields are for another purpose as Pietro points out (Screen Scripter module, which is not generally available).
-
Also worth noting all images stored on the old servers are now fully read only.
For example, if you goto a stockline with an image stored on the old server and try to delete the file/entry in Quantum, you will get a Read Only error.
So you cannot delete old image files within Quantum.
New ones are ok on the new server type.
-
You will need to generate an Image Access key for every request from the new imaging server.
There are some detailed instructions for this, as your code will need to deal with the old imaging and the new imaging setup.
We have been testing this new setup since Nov 2019 as we do a lot of read/write to the imaging servers.
-
I am pretty certain that this is the report..
-
Apologies for late reply.
No problems at all.
The stock controllers love these devices for stock relocation.
We have built in the app the ability to see what they have done recently etc.
We plan to do a lot more with them, ideally get as much as possible into a mobile device of this size.
The only thing to be careful with is Red labels and black text.
The user may need to get a little closer to the label.
The barcode recognition is great with these devices, but they are not as forgiving as the Worthdata devices.
-
Everyone will be different I am guessing …
For us it would be for procedures and training guides to have been fully written, fully tested by the users and then signed off by the users.
Check sheets should be created for this and signed off.
Make sure those staff testing feel responsible for what they are doing.
It is a good opportunity to make sure there is an up to date guide written for everything anyone does. It can sometimes make you question why things are being done the way they are.
We also have detailed IT only related checklists, including DR and all systems linked to Quantum.
I can’t share ours, as they contain everything about how we run our systems and business, which is not something I can share…
I assume others would be in the same situation.
-
Interesting – we are upgrading next week to 12.1.X
It maybe we do not use the modules with issues.
We have tested fairly extensively all processes we use without issues.
There were issues a few months ago, event manager was one of them.
We will have Konstantin here for 2 weeks to cover the upgrade, so if there are any issues we should get them resolved onsite.
-
Good to know, thank you Pietro. How is the current 10.11 release in terms of stability / bugs ?
-
What are companies doing with PowerBi and other visual reporting tools ? Can you post screen shots and or code from queries to share with others ?
-
Todd- you should be able to configure your barcode scanner to remove leading zeros. Quantum generic BC doesn’t do this and won’t find the employee id (as you discovered). I would google how to remove leading zeroes for your specific barcode scanner to see how this is done.
Otherwise, you could update all of the ID’s in Quantum to have the leading zeroes to match the badges. But not sure if that would cause other problems or not.
-
We are due to upgrade 19th Feb and it has been on test a while. First release and the upgrade process on our test system was a bit messy compared to previous. Issues have been resolved.
One important point, which I believe is mandatory, Quantum Imaging is being upgraded. So if you have any integrations with Imaging, be prepared to do some extra work.
We have alot of custom integrations with Quantum, some of which is imaging, that all needed upgrading. Ver 12.X now uses a more secure connection.
Any existing standard Quantum Imaging servers become read only forever, i.e. you cannot write to them from Quantum. So you will end up with all the old imaging locations/servers as they were and a new design for all the new images.
We have alot of CP coming with some new features…
-
Cyndy- this should work for you if you add “Work Order Main Component” or “Bill of Material” (which ever you need) to the part warning settings for that part. Look in the help file here to see how to set this:
Home > Chapter 4 – Inventory Management > Master Parts Global Options
Hope this helps !
-
Another idea is to use Windows’ workspaces/virtual desktop and put each Quantum in it’s own desktop that you can name appropriately.
-
Take a look at the properties for the shortcut that you use to start Quantum. I believe that you can change the icon in there. You can create a different color icon and point your other Quantum to it with the shortcut properties… it may get overridden by Quantum when it decides which color icon to use, based on prod vs test.
-
Nate- take a look at the QueSources in the members area, in the Forms Designer section. There is an entry there for querying the attributes.
Home/ Members-only /QUEsources/ Forms Designer
-
That’s great to hear about version 12. Can ‘t wait to hear how it goes you and others.
Can you elaborate or share any of the changes with report builder ?
-
Jake- Try scanning the working and then the non-working bar code into something like Excel and see what the difference is. We don’t have the mobile app, so i can’t test to see how it works.
When you right click on the bar code in the center of the forms designer and select “configure”, what do you have selected ? Look at everything in forms designer on your bar code and the one that works, to find the difference.
If you want, you can email your form to me and i can take a look at it (File, Save to File).
-
Jake- which app are you using and what field are you scanning into ? try typing the values for the bar code and see what it says- this will make sure that what you are scanning is that the bar code app is looking for. Maybe it is looking for a STM auto key for the stock line ? or the PNM auto key for the part number ? If you are using the genericbc.exe app, are you certain that it is pointing to the database that you are expecting ? check it’s INI file setting.
-
Jake- Take a look at any of the STD forms that have bar code labels. In the DetailsBeforePrint section, you will find the bar code variables being set. Here is the code from one of them, this should help you out.
if PN[‘CTRL_NUMBER’] > 99999 then
begin
if Parameters[‘LEAD_SPACE’] then
BarCodeCrtlNumID.Data := FloatToStr(PN[‘CTRL_NUMBER’]) +
LPad(FloatToStr(PN[‘CTRL_ID’]), 6)
else
BarCodeCrtlNumID.Data := FloatToStr(PN[‘CTRL_NUMBER’]) +
StrPadLeft(FloatToStr(PN[‘CTRL_ID’]), ‘0’, 6);
end
else begin
if Parameters[‘LEAD_SPACE’] then
BarCodeCrtlNumID.Data := LPad(FloatToStr(PN[‘CTRL_NUMBER’]), 6) +
LPad(FloatToStr(PN[‘CTRL_ID’]), 6)
else
BarCodeCrtlNumID.Data := StrPadLeft(FloatToStr(PN[‘CTRL_NUMBER’]), ‘0’, 6) +
StrPadLeft(FloatToStr(PN[‘CTRL_ID’]), ‘0’, 6);
end;
-
This happens in a few other places as well (you MUST set destination to printer, not preview) when printing attached documents and images… great tip !
-
I am guessing the earliest would be a 12.X.X version.
Maybe a few users maybe allowed to access the function to properly test it.
The suggestion has been that for this, a registry entry can be set on the local machine to enable or disable the feature. That would allow controlled testing.
When I hear more will update.
-
Had a demo on this today in development.
Test went well and we will spend some time on this feature this week.
-
TO add to this, I don’t like how pop up browses and windows block the UI, so that you have to close them in order to look at or operate on the previous windows / tabs.
-
This has been discussed at CC with developers last year and to their credit a proof of concept has been done for this.
There maybe some news on this in the future… but keep in mind it would be a 12.X + release and late next year if it does reach production.
-
Billy- here is how you can do the code so that it will show the SI_NUMBER for BOM or main component repair order detail lines.
var q: TOracleDataset;
begin
if (RO_DETAIL[‘WOB_AUTO_KEY’]<>0) then
begin
q := TOracleDataset.Create(nil);
q.SetSession;
q.SQL.Text:=’select SI_NUMBER from WO_OPERATION WOO, WO_BOM WOB where WOB.WOB_AUTO_KEY=’+RO_DETAIL[‘WOB_AUTO_KEY’] and WOO.WOO_AUTO_KEY = WOB.WOO_AUTO_KEY;
q.Open;
Text := q.FieldByName[‘SI_NUMBER’].AsString;
q.Free;
end
else
if (RO_DETAIL[‘WOO_AUTO_KEY’]<>0) then
begin
q := TOracleDataset.Create(nil);
q.SetSession;
q.SQL.Text:=’select SI_NUMBER from WO_OPERATION where WOO_AUTO_KEY=’+RO_DETAIL[‘WOO_AUTO_KEY’];
q.Open;
Text := q.FieldByName[‘SI_NUMBER’].AsString;
q.Free;
end
else
Text := ”;
end;
-
Can you post the code that you used to fetch and populate the WO number? I am guessing that the woo_auto_key is only populated in the data stream for main component repairs. For BOM repairs, you need use the wob_auto_key and tie that back to the woo_auto_key with the wo_bom table, then you can get the si_number from wo_operation using the woo_auto_key matched in wo_bom.
-
Craig- if you use templates for user security, you can just update the templates and then “refresh users” on each template.
Otherwise, you can indeed update this with SQL. The tables are user_fields and field_list. Set a field restriction for one user and look at these tables to see how they work. Then build SQL statements to do the rest. As always, test and check carefully in your test system first !
-
Vanessa- this isn’t exactly a search, but you can report on inventory items and filter by a lot of the UDF fields. On the Inventory Control drop down, select forms & reports, then stock listings, then master listing. If your UDF field is on the report settings window, then you can filter by them.
Your other option along this line is to create a Crystal Report that would filter by UDF fields.
-
Re-opening this post to ask a related question. If I create a tab on an existing window that does not have any tabs defined (like Purchase Request Header), it looks like I need to move all the existing fields into another newly created tab ? How would I do this ? If I just add a new tab, it overlays the fields in the window.
Would I need to add a tab for original fields and then cycle through all the fields and change the parent to the new tab ?
-
We are on 10.9.38 and i don’t see any column in the company_sites table for history or such… It also lets me delete a site from the company record that is used in a PO, which doesn’t seem right…
-
Nikki- this is fantastic- thank you ! Great resource to have.
Are there other Quick Guides available someplace ?
-
Nate- there are a few ways to do this, but the best is to “let Oracle do the work” in the query. Change your sql line to this and adjust the YYYY-MM-DD to your preferences, like MM/DD/YYYY for example)
q.Sql.text :=’select TO_CHAR(CLOSE_DATE, ‘YYYY-MM-DD’) from WO_OPERATION where SI_NUMBER = ”’ + WO_BILLING_HEADER[‘SI_NUMBER’]+””;
-
In Forms Designer, you can do something like this in the MemoShipToOnPrint (substitute the company code and the name of your UDA variable. This is only the first part of the code, the rest remains unchanged. I have not tested this, but it does compile cleanly.
var
lsLine: String;
qc : TOracleDataset;
begin
memoShipTo.Lines.Clear;
if (INVC_HEADER[‘COMPANY_CODE’] = ‘XXX1’) then
begin
qc := TOracleDataset.Create(nil);
qc.SetSession;
qc.Sql.text :=’select ATTRIBUTE_VALUE from uda_checked where auto_key = ‘ + INVC_HEADER[‘COMPANY_CODE’] +
‘ and uda_auto_key in (select UDA_AUTO_KEY from user_defined_attributes ‘ +
‘ where UDA_CODE = ”your-attribute-name” and auto_key_prefix = ”CMP”)’;
qc.Open;
lsLine := qc.FieldByName[‘ATTRIBUTE_VALUE’].AsString;
qc.Free;
end
else
lsLine :=INVC_HEADER[‘SHIP_NAME’];
if lsLine <> ” then
memoShipTo.Lines.Add(lsLine);
lsLine := INVC_HEADER[‘SHIP_ADDRESS1’];
-
Not a very elegant solution, but you can create a User Defined Attribute (these are different from UDF) on the Companies module to hold the name (max length of these is 250 char). Then in your forms that need to print the customer name, check to see if the UDA field is present and if so, use it for customer name instead of the customer_name field in the Companies table.
All of the UDF fields in Companies are less than 50 char, so you would need to use a UDA instead.
-
John- there are about 450 views in Quantum (depending on your version). You can view them using either SQL Developer (or most any other tool used to access the Oracle database) or the OCRunner.exe program in the server folder where Quantum lives.
You can also run this query from Quantum in Interactive SQL:
select view_name, text from SYS.ALL_VIEWS where owner =’QCTL’
-
Hi John- i updated my reply above to show the code for the view (VIEW_SPB_WO_MAINCOMPONENT). I originally posted the code for another Quantum PL/SQL that returns main component information, but it was not for the actual view. The view is the simplest way to view the main component info. It is a complex query because the main component can be on a repair order, or reconciled / returned to customer.
Hope this is a little more clear !
-
john..here is how i grab the work order main component. i use the view provided. i also included the code for the view,so you can see how it works and the relationships….
select * from view_spb_wo_maincomponent where woo_auto_key=379
The view is:
SELECT STR.WOO_AUTO_KEY, STR.stm_auto_key, STR.qty_reserved QTY,
STM.stock_line, STM.pn PART_NUMBER, STM.serial_number, STM.ctrl_number, STM.PNM_AUTO_KEY, STM.DESCRIPTION,
STM.gla_auto_key, STM.unit_cost, STM.ovhl_cost, STM.cmp_auto_key, STM.owner, STM.customer_owned,
0 QTY_RETURN,
STM.cnc_auto_key, STM.loc_auto_key ,STM.stc_auto_key, STM.whs_auto_key, STR.str_auto_key,
NVL(STM.TURNIN_REC, ‘T’) TURNIN_REC,
whs.warehouse_code, loc.location_code
FROM STOCK_RESERVATIONS STR , STOCK STM, warehouse whs, location loc
WHERE STM.stm_auto_key = STR.stm_auto_key
and STR.qty_reserved > 0
AND NOT EXISTS (SELECT ‘X’ FROM WO_STM_COMPLETE WHERE WOO_AUTO_KEY = STR.woo_auto_key
AND STM_AUTO_KEY = STR.stm_auto_key )
AND stm.whs_auto_key = whs.whs_auto_key(+)
AND stm.loc_auto_key = loc.loc_auto_key(+)
UNION ALL
SELECT WSC.woo_auto_key, WSC.stm_auto_key, WSC.qty_COMPLETE QTY,
STM.stock_line, STM.pn PART_NUMBER, STM.serial_number, STM.ctrl_number, STM.PNM_AUTO_KEY, STM.DESCRIPTION,
STM.gla_auto_key, STM.unit_cost, STM.ovhl_cost, STM.cmp_auto_key, STM.owner, STM.customer_owned,
0 QTY_RETURN,
STM.cnc_auto_key, STM.loc_auto_key ,STM.stc_auto_key, STM.whs_auto_key, TO_NUMBER(NULL) str_auto_key,
NVL(STM.TURNIN_REC, ‘T’) TURNIN_REC,
whs.warehouse_code, loc.location_code
FROM WO_STM_COMPLETE WSC, STOCK STM, warehouse whs, location loc
WHERE STM.stm_auto_key = WSC.stm_auto_key
AND stm.whs_auto_key = whs.whs_auto_key(+)
AND stm.loc_auto_key = loc.loc_auto_key(+)
UNION ALL
SELECT ROD.woo_auto_key, STR.stm_auto_key, STR.qty_reserved QTY,
STM.stock_line, STM.pn PART_NUMBER, STM.serial_number, STM.ctrl_number, STM.PNM_AUTO_KEY, STM.DESCRIPTION,
STM.gla_auto_key, STM.unit_cost, STM.ovhl_cost, STM.cmp_auto_key, STM.owner, STM.customer_owned,
0 QTY_RETURN,
STM.cnc_auto_key, STM.loc_auto_key ,STM.stc_auto_key, STM.whs_auto_key, STR.str_auto_key,
NVL(STM.TURNIN_REC, ‘T’) TURNIN_REC,
whs.warehouse_code, loc.location_code
FROM RO_DETAIL ROD, STOCK_RESERVATIONS STR , STOCK STM, warehouse whs, location loc
WHERE STM.stm_auto_key = STR.stm_auto_key
AND STR.rod_auto_key = ROD.rod_auto_key
and STR.qty_reserved > 0
AND stm.whs_auto_key = whs.whs_auto_key(+)
AND stm.loc_auto_key = loc.loc_auto_key(+)
union all — KI T1868
select woo.woo_auto_key, null stm_auto_key, null qty,
null stock_line, null part_number, act.serial serial_number, null ctrl_number, null pnm_auto_key, null description,
null gla_auto_key, null unit_cost, null ovhl_cost, null cmp_auto_key, null owner, null customer_owned,
0 qty_return,
null cnc_auto_key, null loc_auto_key, null stc_auto_key, null whs_auto_key, null str_auto_key,
null turnin_rec,
NULL warehouse_code, NULL location_code
from aircraft act, wo_operation woo
where act.act_auto_key = woo.act_auto_key
and WOO.wo_type = ‘Work Package’
-
The built in Quantum feature should be ok for this?
User / System Setup / Security / View User Security Profiles
You can view and export to excel as required.
-
Craig
I don’t have Work Package, so i cannot fully test this, but ran the SQL against a Work Order with tools and it retrieves what i expected. It looks for all reserved tools that match the task auto key (WOT).
For each of the 4 calc routines, you can use this code, with changes for field names on the memo and the sql field referenced. Because there can be multiple tools per task, you need to loop through the result set.
Hopefully this will solve your issue !!
var
q : TOracleDataset;
begin
MemToolCalDate.lines.clear;
q := TOracleDataset.Create(nil);
q.SetSession;
q.Sql.text :=’Select STM.PN,STM.DESCRIPTION,STM.SERIAL_NUMBER,STM.INSPECT_DUE_DATE from STOCK STM, STOCK_RESERVATIONS STR, WO_TASK_TOOLS WTT where ‘+
‘STM.STM_AUTO_KEY = STR.STM_AUTO_KEY and ‘+
‘STR.WTT_AUTO_KEY = WTT.WTT_AUTO_KEY and ‘+
‘WTT.WOT_AUTO_KEY = ‘ + WO_TASK[‘WOT_AUTO_KEY’];
q.Open;
while not q.eof do
begin
MemToolCalDate.lines.add(q.FieldByName[‘INSPECT_DUE_DATE’].AsString);
q.next;
end;
q.Free;
end;
If you want this report to me more efficient (and run faster), instead of running these queries for each field, you can combine them into the detail_before_print (and remove the 4 individual onprint routines) like this.
var
q : TOracleDataset;
begin
MemToolCalDate.lines.clear;
MemToolDesc.lines.clear;
MemToolPN.lines.clear;
MemToolSN.lines.clear;
q := TOracleDataset.Create(nil);
q.SetSession;
q.Sql.text :=’Select STM.PN,STM.DESCRIPTION,STM.SERIAL_NUMBER,STM.INSPECT_DUE_DATE from STOCK STM, STOCK_RESERVATIONS STR, WO_TASK_TOOLS WTT where ‘+
‘STM.STM_AUTO_KEY = STR.STM_AUTO_KEY and ‘+
‘STR.WTT_AUTO_KEY = WTT.WTT_AUTO_KEY and ‘+
‘WTT.WOT_AUTO_KEY = ‘ + WO_TASK[‘WOT_AUTO_KEY’];
q.Open;
while not q.eof do
begin
MemToolCalDate.lines.add(q.FieldByName[‘INSPECT_DUE_DATE’].AsString);
MemToolDesc.lines.add(q.FieldByName[‘DESCRIPTION’].AsString);
MemToolPN.lines.add(q.FieldByName[‘PN’].AsString);
MemToolSN.lines.add(q.FieldByName[‘SERIAL_NUMBER’].AsString);
q.next;
end;
q.Free;
end;
-
David- have you looked into using User Defined Attributes for this ? You can set these up as drop downs with predefined values.
-
Lisa
If you open most any form (invoice, PO, Sales Order, etc), you can see how they insert the logo. In the STD Purchase Order, it is the imgletterhead1. Look at the code iin the Calc tab for imgletterhead1 and you will see how they select it. In the design tab, you can set the size and placement of the image.
The 2 best ways to learn about Forms Designer is to review the many posts here in the forum and also look at the existing forms to see how they are done. You can learn many techniques and tricks from this !
-
Craig- sure no problem, email it to me…
-
Craig- can you post the entire form (.rtm file, using File, Save to File menu command) on here so we can look at it and help you out ?
-
Terri- would this be the AR_STATEMENT field in the Rolodex table ?
-
McAllister – could you elaborate on the Quantum settings needed to support GSuite ?