Home
Login
Sign Up
 
 

Forum | Message

Fri, March, 29th 2024
Message Link »
10
View »
Jeremy Bull *MUGA
BC:

Forum Question/Topic:

Article:

Delivery document output by warehouse/stock zone

Situation: I'm in warehouse ABC pick/pack/shipping a picking list through FactoryTrack. At the end of the process, I'm outputting delivery documents to accompany the shipment (BOL and delivery note). There is one printer in my warehouse where all these documents should print to. There are also warehouses DEF and GHI, whose docs should print to their respective printers.

Question: What am I missing in M3 that can hardcode a specific printer by the stock zone/warehouse of a picking  Read more...list/delivery for a document? Pre-Cloud we managed this via Streamserve scripting and the maintenance was a pain/open to errors. Yet, I don't see a better solution in CE.

I don't want to manage through MNS205 by user as that's way too much administration. I don't want to let users define their own printers in FT as they will screw it up. I don't see a way of managing through CRS945 (doc 900/00, for example, seems tailored only for distributing the document to a customer's email). MMS040 printer definition is only for the picking list.

What is everyone else doing that expects this doc output automation and has multiple warehouses? Show less...
Delivered Read
10
John Panzenhagen
What about MMS040 - Stock Zone. You can identify a printer there.
Jeremy Bull
Only functional for the picking list though
Steve Bartlett
Jeremy, MNS205 by User has been our process. Using a role type user due to potential turnover but as you mention that can be a bit more administration.
Elise Sheppard
For package labels, we have the users set their printers in FT settings, and it shows as the default as they're processing in FactoryTrack. We have printers assigned to printer groups, and assign printer groups to users so they can see the printers in their warehouse. Right now, the output docs we use are picking lists (but we're phasing these out), delivery note, and package label. We're in the process of rolling out InterForm and I'm 95% sure you could do it there.
Jeremy Bull
@eshepp that's the direction we were going but others thought the wrong printer would still be selected. Follow up question then--FT settings has two fields for 'label printer' and 'document printer'. Do you know how M3/FT distinguishes what is a label and what is a document? 2 of 3 of our delivery docs can come off a standard office printer but 1 is a 4x6 label that would need to be routed elsewhere. How would M3 know though that's a & Read more...quot;label" versus a document? Show less...
Elise Sheppard
I went digging in M3 for the label vs. doc question... checked CMS004, 005, 006, MNS205, 210, 204... I'm not seeing where that distinction lives. I thought I'd seen it somewhere before, but I can't re-find it. 😕

All of that being said, I don't think it necessarily matters. Only place I know it's used is in a FactoryTrack screen (oh maybe THAT's where it is!!)--if it's printing what it thinks is a label, it pulls the default label printer from the user's FT parameters and displays  Read more...it in that FT screen. Show less...
Jeremy Bull
But how does it know what to think is a label 😀
William Bolin
We're trying to confirm how it knows what's a label, but it's implied in all the functional documentation that Factory Track has hard-coded which documents are "labels" and which are "documents".
Elise Sheppard
that sounds about right, William.
William Bolin
It seems that as a general rule Factory Track treats everything as a label except for "Delivery Documents" (Delivery Note, Bill of Lading, etc) printed via the pick and pack process.

Online