Sage 100

 View Only
  • 1.  Adding Serial Numbers to SO Additional Packing List

    Posted 06-13-2022 18:49
    Client (Sage 100 Std 2018) wants to add the Serial Numbers to the SO Additional Packing List.

    I went to create a sub-report intending to link SO_AdditionalPackingListWork to SO_TierDistribution but LineKey is missing from the work table.

    In looking through live invoice data in DFDM it appears that LineKey and LineSeqNo share the first 6 digits.
    What is SO_AdditionalPackingListWork.LineSeqNo used for and is it true that LineKey(1,6) will always equal LineSeqNo(1,6)?

    ------------------------------
    Greg Stiles
    S & W Microsystems
    ------------------------------


  • 2.  RE: Adding Serial Numbers to SO Additional Packing List

    Posted 06-13-2022 19:50
    LineSeqNo is the line sort order, and will be different than LineKey if you insert a line, or re-order the lines.

    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    ------------------------------



  • 3.  RE: Adding Serial Numbers to SO Additional Packing List

    Posted 06-15-2022 17:50
    Yep, not going to work. Thanks @Kevin Moyes.​

    ------------------------------
    Greg Stiles
    S & W Microsystems
    ------------------------------



  • 4.  RE: Adding Serial Numbers to SO Additional Packing List

    Posted 06-16-2022 09:27
    Edited by David Speck II 06-16-2022 09:34
    SO_AdditionalPackingListWrk doesn't have a LineSeqNo field but does have a LineNumber field.  Both are 14 characters long according to the FLOR.  I am not sure off the top of my head if the LineNumber is going to actually be the LineSeqNo from SO_InvoiceDetail or if it is a new number calculated on the fly when populating the work table.  If it actually is the LineSeqNo, then technically, you should be able to use it for on the fly report to link to SO_InvoiceDetail to get the LineKey and then to SO_InvoiceTierDistribution on the LineKey to get the distribution info.  What you would have to avoid is rely on cases where you would expect the LineSeqNo to remain the same, such as if you sourced it to the SO_InvoiceTierDistribution table into a UDF because the business object is not going to update the UDF in SO_InvoiceTierDistribution if a line is inserted/reordered.  I suppose you could always use a pre-write event script on SO_InvoiceDetail to keep the UDF in SO_InvoiceTierDistribution in sync with its line and then you would only have to include SO_InvoiceTierDistribution in your sub-report vs having to include both SO_InvoiceDetail and SO_InvoiceTierDistribution in the sub-report.  Although I can't imagine either table would ever get large enough to cause performance issues so it may not be worth concerning yourself over those two tables being joined in a sub-report.

    EDIT:  bad news, it appears the LineNumber field is calculated on the fly and does not equal the LineSeqNo.

    To make matters worse, you can't even add a UDF to the SO_AdditionalPackingListWork table to source either LineKey or LineSeqNo from SO_InvoiceDetail.

    I also tracked to see if a sourced UDF could be added to SO_PackageTrackingByItem and it doesn't even allow sourcing UDFs and since its primary key is InvoiceNo+PackageNo+ItemCode, it doesn't look like it was designed to be tracked at an individual line level but rather combines lines by item code.



    ------------------------------
    David Speck II
    Tennessee Software Solutions
    ------------------------------



  • 5.  RE: Adding Serial Numbers to SO Additional Packing List

    Posted 06-17-2022 10:39
    @David Speck II yep, same conclusion I came to​. I suggested Custom Programming to the client, haven't heard back. Probably not worth the cost.

    ------------------------------
    Greg Stiles
    S & W Microsystems
    ------------------------------