We have a need to print picking labels to put on the components during kitting before it goes to the floor. I was thinking of creating a SSRS report and create an auto print routing to print to the zebra printer. However, has anyone done something similar with bartender and can provide some insight?
Hereβs a whole thread about me figuring out how to write out drop files for bartender. Works great for what we do. You should be able to modify whatβs there to what you want to do if you have a C# experience.
Thanks Brandon. I will take a look.
I followed along on that thread. We now have a button on our sales order screen to print multiple labels that goes out with our picking lists which are printed at the same time (although a different button). It works well.
We do the same thing at my company. Iβve actually built everything that way and I donβt really know how Epicor and Bartender are supposed to interact otherwise.
Just saw this thread and thought Iβd add that we have done this via an SQL stored procedure as well. We output a bartender text file that the integration services picks up to create a label to be added to our drawings. This allows the floor to match the drawing back to a traveler if they get separated.
To do this you use C# and call a couple of stored procedures in a side cart database on our server. In this side cart database, we call Epicor tables and build output. The C# code calls these two different stored procedures. The results are fed into a .BT file output to the proper integration folder on the Bartender server.
Code from first SP which builds the Bartender command line structure. You can use a variable for the printer workstation for Bartender, or just create different SPs.
select β%BTW% /AF=βC:\Bartender\Documents\JobReleaseTag.btwβ /D="" /PRN=βNAS-LBL53β /DBTEXTHEADER=3 /R=3 /Pβ as [BartenderCommander]
UNION ALL
select β%END%β as [BartenderCommander]
Code from the second SP which builds the record that is printed on the tag. You can see the first query just builds the column titles. The second query after the union actually gets data from Epicor, and an external releasing tool we have.
select β"_JobTitle"β as [JobTitle]
,β"_JobNum"β as [JobNum]
,β"_WBSJobNum"β as [WBSJobNum]
,β"_PartNum"β as [Partnum]
,β"_RevisionNum"β as [RevisionNum]
,β"_PartDescription"β as [PartDescription]
,β"_DrawingNumber"β as [DrawingNumber]
,β"_DrawingRevision"β as [DrawingRevision]
,β"_DueDate"β as [DueDate]
,β"_ProdQty"β as [Qty]
,β"_Created"β as [Created]
,β"_Printed"β as [Printed]
UNION ALL
select distinct β"β + βJob Release / β + A1.JobNum + β"β as [JobTitle]
,β"β + A1.JobNum + β"β as [JobNum]
,β"β + ISNULL(A2.WBSJobNum,ββ) + β"β as [WBSJobNum]
,β"β + A1.PartNum + β"β as [Partnum]
,β"β + A1.RevisionNum + β"β as [RevisionNum]
,β"β + A1.PartDescription + β"β as [PartDescription]
,β"β + A1.DrawingNumber_c + β"β as [DrawingNumber]
,β"β + A1.DrawingRevision_c + β"β as [DrawingRevision]
,β"β + ISNULL(CAST(CAST(A1.DueDate as date) as nvarchar(11)),ββ) + β"β as [DueDate]
,β"β + CAST(CAST(A1.ProdQty as float) as nvarchar(100)) + β"β as [Qty]
,β"β + ISNULL(A2.RelEng,ββ) + β"β as [Created]
,β"β + @Printed + β"β as [Created]
from EpicorDatabase.dbo.JobHead with (nolock) A1
left outer join βSidecartdatabaseβ.dbo.vJobRelation A2 on A1.JobNum = A2.JobNum and A1.PartNum = A2.PartNum
where A1.JobNum = @JobNum
Interesting Josh. Can you provide the C# to call out the stored procedure as well? Would love to try this as well.