dbroyles
Forum Replies Created
-
Hi Pietro, to answer your question, no. We keep our customer AR contacts out of marketing as the contact information changes very frequently and it is difficult enough to stay on top of changes. We re-scan the Rolodex for each company at each job execution to identify the AR contact at the company. Again, we do run a report before execution identifying any new companies that may not yet have an AR contact assigned.
-
We are on Quantum 10.9.19 and ended up modifying the package:
QC_SCHED_CUST_PKG.STD_0015_AR_PASTDUE
to pull in assigned company contacts from the ROLODEX table with a value of true in AR_STATEMENTS column.
We also run a report before each AR PAST DUE run that shows us which companies do not have a dedicated AR Statement contact, so we can work with sales or the customer to assign one before the past due notifications go out.
The modifications are pretty straight forward in the Package, but the version of Quantum you are on may impact this approach.
-
Not directly through Quantum that I can find, but indirectly, assuming you have “Allow Active Directory Based Login” checked. You can change everyone’s password in the system, which would disable their ability to change the password, since they don’t know the old one.
The check box for AD Based Login is located at Users – Security Module Settings – Enhanced Security in 10.9.7
-
Make sure you have:
Under Appearance:
MaintainAspectRa = checked
Under Layout – Dynamic:
Dont check AutoSize
Stretch = checked
-
Other than inserting DISTINCT into the query, it sounds like you could have a data anomaly. If this doesn’t work:
SELECT DISTINCT RPR.PNRANK
FROM RIM_PN_RANK RPR
WHERE PNM.PNM_AUTO_KEY = RPR.PNM_AUTO_KEY
If it’s still not working, then it’s time to start data mining, if you haven’t already. Here is something I start with to track down the root cause:
–FIRST DUMP THE DATA INTO A TEMP TABLE
create table test_table as
(
select pnm_auto_key,
(SELECT RPR.PNRANK
FROM RIM_PN_RANK RPR
WHERE PNM.PNM_AUTO_KEY = RPR.PNM_AUTO_KEY
) as new_ic_udf_017
FROM PARTS_MASTER PNM
WHERE PNM.PNM_AUTO_KEY = ANY
(SELECT RPR.PNM_AUTO_KEY FROM RIM_PN_RANK RPR
)
);
–NOW CHECK FOR DUPLICATES
select pnm_auto_key, count(*)
from test_table
group by pnm_auto_key having count(*) > 1;
–NOTE THAT NOE OF THE ABOVE IS CHECKED FOR EXECUTION SINCE I DON’T HAVE THE VIEW
If the data used to perform the update is truly unique, then you should receive no results with counts greater than 1.
If that’s the case, you may want to check for NULL handling in the view.
Don’t forget to drop the test table when you are done.
Hope this helps.
-
We are a Windows 10 Pro desktop environment, so we switched out our old LP 2844 printers to the Zebra ZD420 Barcode Printer (ZD42042-C01M00EZ). The LP 2844 printed a slightly darker label, but we are very satisfied with the ZD420.
If you need your part tags and bar codes to last a very long time I recommend you also get the Resin Ribbon Cartridge, it’s medical grade longevity.
We use the wax/resin with out of the box printer settings and have no issues with bar codes, bleeding, etc.
-
Please provide the code for the view.
-
In addition to Mikes question, what version of Quantum are you on?
-
Please provide the “Document” name under “Printing Options” that you are using.
-
What version of Quantum are you using?
-
Or do you mean this setting?
-
Hi Pietro,
Just to confirm, this is the setting you are referencing correct?
-
Thanks Pietro, I have not. I will give this a try.