Bartender Labels

I understand how commander listens to //path/ and commander processes those trigger lines, but the question is how could I get a string passed from the customer record to be used as the filename in that trigger command found in the .bt files? That is what I’m trying to solve for at the moment.



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of DD
Sent: Friday, January 06, 2012 3:07 PM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] Bartender Labels





YES - use Commander (Comes with Bartender) You put a line at the top that tells it which BTW label file and which printer to use.
ftp://ftp.seagullscientific.com/BarTender/Examples/Commander

This has a document on how to use commander with bartender.



%BTW% /AF="\\SERVER\epicor\mfgsys803\Server\reports\CustomReports\bbb.btw" /D="<Trigger File Name>" /PRN="\\SERVER\DDZebra1" /DBTEXTHEADER=3 /R=3 /P /close
%END%

________________________________
From: Anon <jgiese@... <mailto:jgiese%40wisconsinconverting.com> >
To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
Sent: Wednesday, January 4, 2012 1:42 PM
Subject: [Vantage] Bartender Labels


Is there any ways that anyone knows of to tell bartender to use a dynamic label format? We have labels that are specific to customers and it would be nice if I could specify at the customer level which btw file to use for printing. The data definition will never change, just the btw file. Any ideas?

[Non-text portions of this message have been removed]





[Non-text portions of this message have been removed]
Is there any ways that anyone knows of to tell bartender to use a dynamic label format? We have labels that are specific to customers and it would be nice if I could specify at the customer level which btw file to use for printing. The data definition will never change, just the btw file. Any ideas?
A very simple solution would be to just create an auto print rule for each dependent customer. It's free (and easy) - but probably a little cumbersome to maintain. It might work very well if you only have a few customers with custom labels; then all others could use a "standard" label format. Handle the exceptions with other auto print rules. The other option would be to control create a standard label name (example: <customer name>.shipmentlabel.btw) and instead of using the auto print rule, create a bpm to generate the output file using BPM code. I have done something similar for (some) custom label formats. This way the information is in "code". There are probably other ways, this is just a brain dump on my part.

Please report back to the group on what you decide and any progress you have made.

Thank you!


--- In vantage@yahoogroups.com, "Anon" <jgiese@...> wrote:
>
> Is there any ways that anyone knows of to tell bartender to use a dynamic label format? We have labels that are specific to customers and it would be nice if I could specify at the customer level which btw file to use for printing. The data definition will never change, just the btw file. Any ideas?
>
Shoot that's not the easy button I was looking for. I could create separate BPMs for each customer where it only auto prints if it matches the customer record correct? So on the JobHed table I would have, say 14 different BAMs. Each BAM is for a different customer where the rule is CustNum = ABCCOMP. Each BAM with a different style named the ID of the customer. That way everything is separated out and I could see each customers custom label at a high level in the trees.

--- In vantage@yahoogroups.com, "JCHenslee" <jhenslee@...> wrote:
>
> A very simple solution would be to just create an auto print rule for each dependent customer. It's free (and easy) - but probably a little cumbersome to maintain. It might work very well if you only have a few customers with custom labels; then all others could use a "standard" label format. Handle the exceptions with other auto print rules. The other option would be to control create a standard label name (example: <customer name>.shipmentlabel.btw) and instead of using the auto print rule, create a bpm to generate the output file using BPM code. I have done something similar for (some) custom label formats. This way the information is in "code". There are probably other ways, this is just a brain dump on my part.
>
> Please report back to the group on what you decide and any progress you have made.
>
> Thank you!
>
>
> --- In vantage@yahoogroups.com, "Anon" <jgiese@> wrote:
> >
> > Is there any ways that anyone knows of to tell bartender to use a dynamic label format? We have labels that are specific to customers and it would be nice if I could specify at the customer level which btw file to use for printing. The data definition will never change, just the btw file. Any ideas?
> >
>
I just implemented precisely this requirement.

I named my customer-specific label format files with the CustomerID, with 99999 as the default. The program checks for the presence of a customer format and if not found, falls back to 99999.

I had trouble switching formats "inline" within one commander script so I had to create separate script and data files. Also we have a "start" and "end" header/trailer we print surrounding each batch of carton labels so this allowed me to call those as well.

The script then looks like below, pointing to the .csv files with the corresponding data. Format is the WAVE#_ZONE_Cust#_Chunk#. I increment the chunk# between parts so that each part has its' own header/trailer label (we ship a lot of cartons of one part). We have multiple label printers in the warehouse and we use a UDCodes list to determine the correct label printer based on the zone.

We use a similar algorithm for pallet header labels (actually 8.5x11 laser-printed sheets designed in bartender) but use the shipping lane instead of the warehouse zone to determine the correct printer.

Good Luck!

Chris

Christopher Heins
Sr. Progress Programmer/Analyst
[cid:image001.png@01CCCB03.13FEAE20]
Desk# 973-560-5370
Cell# 908-256-3662
Skype: cheins.nj
cheins@...<mailto:cheins@...>


%BTW% /AF="\\erp-apmepm\bartender\forms\START.BTW" /D="\\erp-apmepm\bartender\data\16_DC_Start_001.CSV" /PRN="jefferson_Label" /R=1 /P /X /C=1
%BTW% /AF="\\erp-apmepm\bartender\forms\99999.BTW" /D="\\erp-apmepm\bartender\data\16_DC_99239_001.CSV" /PRN="jefferson_Label" /R=1 /P /X /C=1
%BTW% /AF="\\erp-apmepm\bartender\forms\END.BTW" /D="\\erp-apmepm\bartender\data\16_DC_End_001.CSV" /PRN="jefferson_Label" /R=1 /P /X /C=1
%BTW% /AF="\\erp-apmepm\bartender\forms\START.BTW" /D="\\erp-apmepm\bartender\data\16_DC_Start_002.CSV" /PRN="jefferson_Label" /R=1 /P /X /C=1
%BTW% /AF="\\erp-apmepm\bartender\forms\99999.BTW" /D="\\erp-apmepm\bartender\data\16_DC_99239_002.CSV" /PRN="jefferson_Label" /R=1 /P /X /C=1
%BTW% /AF="\\erp-apmepm\bartender\forms\END.BTW" /D="\\erp-apmepm\bartender\data\16_DC_End_002.CSV" /PRN="jefferson_Label" /R=1 /P /X /C=1
%END%

--------------------- Code snipped which tests for customer-specific label format. The line with SEARCH is the key. It returns null (?) if the parameter isn't found on disk:

if first-of (ttbt.custnum) then do:

vcCustID = fGetCustID (ttbt.company, ttbt.custnum). /* function defined above to return the CustID given the internal custnum */
if vcCustID = ? then vcCustID = "99999".

if pJobtype = "PalletHeader" /* the same code is used for Pallet Headers and Carton labels */
then vcFormName = vcPathname + "forms\PalletHeader.Btw".
else do:

vcFormName = vcPathname + "forms\" + vcCustID + ".BTW".

if search(vcFormName) = ? then do:
vcFormName = replace(vcFormName, vcCustID, "99999").
end.
end.

vcDataName = vcPathname + "data\" + vcPrefix + vcCustID + vcSuffix.
OUTPUT STREAM s-out TO VALUE(vcDataName).

ASSIGN /* the double quotes get tricky! But without them you are toast if UNC name or form name or printer share has embedded space */
BTscript = "%BTW% /AF=""" + vcFormName + """ /D=""" + vcDataName + """ /PRN=""" + (Prtname) + """ /R=1 /P /X /C=1".

PUT stream s-script UNFORMATTED BTscript skip. /* stream s-script writes the commander script */

EXPORT stream s-out DELIMITER "," /* stream s-out is for writing the data file with the label contents */
"ShipFromName"
"ShipFromAdd1"
"ShipFromCSZ"
"ShipToName"
"ShipToAdd1"
"ShipToAdd2"
"ShipToAdd3"
"ShipToCSZ"
"ShipToZIP"
"ShipToNum"
"ShipID"
"ShipFor"
"Type"
"Dept"
"PONum"
"SCAC"
"Carrier"
"BOLNum"
"Pallet#"
"Tot_Pallets"
"Carton#"
"Tot_Cartons"
"CustPN"
"OurPN"
"Description"
"UPC-12"
"Qty"
"SSCCNum"
"BoxWgt"
"PkgCode"
"GTIN"
"ShipComment"
"LabelComment"
"LineComment"
"WaveNum"
"Lane"
"ZoneID"
"Bin"
"OrderNum"
"MasterPack"
"DueDate"
"NumParts"
"PartList"
.

End. /* first of cust */




________________________________
NOT INTENDED AS A SUBSTITUTE FOR A WRITING
NOTHING IN THIS E-MAIL, IN ANY E-MAIL THREAD OF WHICH IT MAY BE A PART, OR IN ANY ATTACHMENTS THERETO, SHALL CONSTITUTE A BINDING CONTRACT, OR ANY CONTRACTUAL OBLIGATION BY PNY, OR ANY INTENT TO ENTER INTO ANY BINDING OBLIGATIONS, NOTWITHSTANDING ANY ENACTMENT OF THE UNIFORM ELECTRONIC TRANSACTIONS ACT, THE FEDERAL E-SIGN ACT, OR ANY OTHER STATE OR FEDERAL LAW OF SIMILAR SUBSTANCE OR EFFECT. THIS EMAIL MESSAGE, ITS CONTENTS AND ATTACHMENTS ARE NOT INTENDED TO REPRESENT AN OFFER OR ACCEPTANCE OF AN OFFER TO ENTER INTO A CONTRACT. NOTHING IN THIS E-MAIL, IN ANY E-MAIL THREAD OF WHICH IT MAY BE A PART, OR IN ANY ATTACHMENTS THERETO SHALL ALTER THIS DISCLAIMER.

This e-mail message from PNY Technologies, Inc. is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.


[Non-text portions of this message have been removed]
YES - use Commander (Comes with Bartender) You put a line at the top that tells it which BTW label file and  which printer to use.Â
ftp://ftp.seagullscientific.com/BarTender/Examples/Commander
Â
This has a document on how to use commander with bartender.Â
Â
Â
Â
%BTW% /AF="\\SERVER\epicor\mfgsys803\Server\reports\CustomReports\bbb.btw" /D="<Trigger File Name>" /PRN="\\SERVER\DDZebra1" /DBTEXTHEADER=3 /R=3 /P /close
%END%



________________________________
From: Anon <jgiese@...>
To: vantage@yahoogroups.com
Sent: Wednesday, January 4, 2012 1:42 PM
Subject: [Vantage] Bartender Labels


Â
Is there any ways that anyone knows of to tell bartender to use a dynamic label format? We have labels that are specific to customers and it would be nice if I could specify at the customer level which btw file to use for printing. The data definition will never change, just the btw file. Any ideas?




[Non-text portions of this message have been removed]