Sage 100

Customer would like their inventory labels to print after PO ROG with job # and PO #. Has anyone done this? I presume the inventory label printing program is where this comes from? That program does not appear to have any ties back to ROG and seems to simply print fields related to inventory master. What am I missing here? When a customer wants their inventory labels to also print the PO # and possibly the Job # they were purchased for what are my options? I don't think I can do a UDF since the label printing appears to just draw from the item master and not individually identifiable inventory parts.

My first thought would be using a sub-report and adding a parameter for the PO number on the label form.

They'd like to print the labels after ROG. This seems like a sorta reasonable request -- customer wants a label that has some PO specific information or an indication of what job it was purchased for. I'm not entirely sure that without an enhancement that you can get here. I guess a workaround would be to propose the design of a custom crystal report which does not get linked to the ROG process and the user can manually go through and print labels based on PO number using the history files. Not sure if speed would be an issue here. Hopefully I've overlooking something blatantly obvious because this doesn't seem unreasonable.

@WayneSchulz I don't see a way to print the labels with the receiving information contained on a PO after the ROG process is posted and complete. An alternative would be to add a sub report to the daily receipts register so it prints labels at the same time the register prints. If they preview the report, they could send the different sections to different printers. (A little clunky but a cheap way of getting there.) An alternative would be to create a custom Crystal Report (or Access report using PTQ's- hey Jeff!). You could call the report from a custom button that you add to the Receipt of Goods form or from a menu item added to PO after to ROG's were entered but before they were updated. The issue with this is there is a good chance of forgetting to pring the receiving labels. Looking at the input form, I thought a third alternative of creating an Office Template might work but it appears the data only represents PO Receipt Header information and doesn't give you line details needed for labels. Hope this helps.

Thanks - this is what I'm slowly beginning to realize. I supposed they could also read from PO Receipt History though I'm not sure whether speed will be a factor there (my guess is yes). I like the subreport concept. Potentially there could be a UDF that flags whether to print a label for a particular item as well. It's too bad that so much of this becomes workaround and additional programming. The customer truly doesn't understand why something so seemingly simple becomes an extra cost project. Sadly I find that in most cases I agree with them.

For the money, Sage 100 is a good distribution system. That doesn't mean it's a complete, robust distribution system. There are many features that the tool is missing. However, it covers a lot of ground. The challenge is like most tools. There are features many people will never use. There are other features that don't exist that seem obvious to some, due to their business processes. However, those features would only be useful to a subset of a subset. If those same people purchased a product containing all the things they may want, they would probably complain about paying for a ton of features that they will never use just to get the few they want. It's like someone who wants a top of the line audio system that only comes in a Lexus but they don't want to pay for all the other features in the car. They want a Nissan Altima with a Lexus sound system. In this case, they have three options: 1) pony up for the Lexus, 2) buy the Altima and be happy with it's sound system, or 3) buy the Altima and install an after-market sound system. In this case, you are the provider of the after-market tunes!

Nice analogy @ShawnSlavin !!

@ShawnSlavin - Thanks for the shout out! @WayneSchulz - What kind of a bar code printer doe they have and do they have bar code software (e.g. bar tender, label matrix)? The client's desire is a slam dunk using Access PTQ's and bar code labeling software. Or a subreport as @ThereseLogeais & Shawn suggests. Unfortunately, people want sophistication but not any complexity (as defined by how their current processes are set up). My catch weight prospect want security (i.e. be able to catch the delivery drivers stealing), mobility (hand helds for the drivers and remote entry for their sales people. But they don't want complexity beyond the Sage 50 that they have been using for years. Education is so important these days in meeting expectations of users.

Hi Wayne, I have a client with the exact request - print from RoG. However, the RoG label only prints inventory label. I need Po# and line UDF info etc from RoG. Fortunately, they want to print on 8.5 x 11 label by using a laser printer. So I don't have to deal with a zebra printer. I am concerned that they will forget to print a custom crystal report (label) during RoG so I was thinking of writing a custom crystal report for them to print from receipt history. Did you come to a solution for your client back in 2014? (For another client, I wrote an Access query that dumps to a text file from Receipt History every 15 minutes. And they print from Bartender. It's worked for the last two/three years. But with this new request, I am trying to find out if there are better alternatives. Client is not ready for scan gun, etc., yet. ) Thanks, all, for the good discussion.

Never came up with anything. This question recently was asked again and there's some added info on why this may not be (easily) possible except for serialized inventory - https://90minds-com.socialcast.com/messages/39278380?ref=stream

I just tested a crystal report based on receipt history header/detail. It works pretty fast, it even prompts for number of ""pallets"" and it will print 1 of 5, 2 of 5, etc.- it will have to prompt the user to type in PO no and item code. I think it's safer to print from RoG history because I know the users will get distracted and will forget to print the label during RoG. Don't know what kind of feed back I'd get from the client. But this is the quickest and least expensive solution I have so far. (Client wants everything two weeks ago from yesterday.)