Unable to Print SO_PickingSheet1.rpt

We have been getting this error when we run the "Picking Sheet Printing" function in SO, it will print a few SO's and then through up this error.

The printing stops, we have multiform checked off to print another report for the SO's and that one doesn't print.  The rest of the SO's that should print don't either.  Thought it might have something to do with the order that it stops on, but I don't see anything that stands out?

  • 0

    Received this error twice this morning, again, worrying that the print pick sheet box is getting checked off but the picking ticket is not getting printed.  We are using Cloud at work to host SAGE and we have two servers sharing the user load, could this be causing some issue?  The only similar issues I could find are the location of directories, but I wouldn't think that is this case since the picking sheets are saved on the main server.  I did notice a report with the same name just in this location,

    E:\Sage\Sage100V2022\MAS90\Reports

    And the picking sheet that we should be referring to is under, E:\Sage\Sage100V2022\MAS90\MAS_ACT\Reports\SO_PICKINGSHEETPRINTING

  • 0

    The Knowledge Base indicates this has to do with a date field.  

    Error: "Unable to print AP_InvoiceRegisterJC.rpt. The operation completed successfully."

    Created on  | Last modified on  Highlight Matches

    Cause

    There is an invalid date in one of the date fields.

    Resolution

    Locate and correct the affected record in Data File Display and Maintenance.

    Note: Use caution when working with Data File Display and Maintenance.

    1. Open Modules, Library Master,click Data File Display and Maintenance.
    2. Browse to ..\Mas90\Mas_xxx\APxxx (xxx = company code), and open either AP_InvoiceHeader.m4t or AP_InvoiceDetail.m4t.
    3. Locate the affected record, and correct the invoice date.

    Note: The date should have the following format: YYYYMMDD. For example June 17, 2013 is formatted as 20130617.

  • 0 in reply to BigLouie

    Question if we have an UDF with date/time would that cause an issue?  We populate this field anytime an order moves through production so I would think if it causes issues we would have more issues than a few a week.  We probably have had this error 4-5 times this week and it just started doing this, as I type this I am going through emails to see when we started writing to this UDF straight through SQL.  Might try to pin point an order that is getting the "pick ticket" printed again with a value in this field.

  • 0

    Error popped up again this morning, I checked the UDF field and the UDF is not set as a date field, it is multi line format.  When we printed this morning only one order printed and it only printed the first part of the multi-part form printing, the copy that printed also showed page 2 of 2 at the top, which it should of only been page 1 of 1, weird, when I manually printed from the SO the pick ticket it was correct.  There were 7-8 orders that the picksheet printing flag was changed to "Y" but none of those orders were printed, as you can imagine this could cause a serious issue, if orders never print but in SAGE say they were already printed.

  • 0 in reply to BigLouie

    Still can't seem to pinpoint the issue, we changed the frequency of a stored procedure that we had running in SQL, which was updating a field that I thought was causing the problem, but we still received the error.  Got the error on Monday and haven't gotten it again this week.  Sent to SAGE and they were no help. 

    Is there a way to store or see all of the SO #'s that are in the work file when you run the print picking sheet function?  Trying to see if I can get a list of orders that were suppose to print, that way we can check to make sure the flags are getting checked "off".

  • 0 in reply to jland47

    You can only see the work file contents if you Preview instead of Print.  (Leave the Preview open and use DFDM to open the temp M4T... or on Premium you query the tempdb in SQL).

  • 0 in reply to Kevin M

    We are on Premium, is it possible to query the tempdb and output it to a table anytime the tempdb is updated?

  • 0 in reply to jland47

    The temp tables are created / and destroyed automatically.  Hold the Preview open, and the deletion is delayed until it's closed.  If you want to capture tempdb contents automatically... you'd have better luck seeking answers from a technical SQL resource / forum.