Sage 100

Also - they can have the same item on a shipment more than once.  For example, line 1 could have qty shipped 14 of item ABCDEF and then line 5 could have qty shipped 25 of item ABCDEF.

Also - they can have the same item on a shipment more than once.  For example, line 1 could have qty shipped 14 of item ABCDEF and then line 5 could have qty shipped 25 of item ABCDEF.

Also - they can have the same item on a shipment more than once.  For example, line 1 could have qty shipped 14 of item ABCDEF and then line 5 could have qty shipped 25 of item ABCDEF.

On the primary packing list the per unit item weight is SO_PackingListWrk.ItemWeight. On the additional packing lists I am using SO_AdditionalPackingListWrk.Weight.  Does anyone have a theory as to why the weight prints on the primary packing list and does not print on the additional packing lists? 

Also - they can have the same item on a shipment more than once.  For example, line 1 could have qty shipped 14 of item ABCDEF and then line 5 could have qty shipped 25 of item ABCDEF.

Well, if you've looked in the Wrk file and the field is empty, I'd say... BUG.

On the primary packing list the per unit item weight is SO_PackingListWrk.ItemWeight. On the additional packing lists I am using SO_AdditionalPackingListWrk.Weight.  Does anyone have a theory as to why the weight prints on the primary packing list and does not print on the additional packing lists? 

Also - they can have the same item on a shipment more than once.  For example, line 1 could have qty shipped 14 of item ABCDEF and then line 5 could have qty shipped 25 of item ABCDEF.

I'm about to pull a Wayne and lose my S*$% !!  Another one?? I was hoping the additional packing lists used actual weight that was somehow assigned during the shipping process and I was missing where that process occurred.

Well, if you've looked in the Wrk file and the field is empty, I'd say... BUG.

On the primary packing list the per unit item weight is SO_PackingListWrk.ItemWeight. On the additional packing lists I am using SO_AdditionalPackingListWrk.Weight.  Does anyone have a theory as to why the weight prints on the primary packing list and does not print on the additional packing lists? 

Also - they can have the same item on a shipment more than once.  For example, line 1 could have qty shipped 14 of item ABCDEF and then line 5 could have qty shipped 25 of item ABCDEF.

Somewhere, there is a HUGE pile of S* that people have lost over the years.  If only someone who NEEDED some S&! was able to find this lost pile and make use of it. Sad. Of course, this assumes the losers do not want their S^$ back, which may not be the case.

I'm about to pull a Wayne and lose my S*$% !!  Another one?? I was hoping the additional packing lists used actual weight that was somehow assigned during the shipping process and I was missing where that process occurred.

Well, if you've looked in the Wrk file and the field is empty, I'd say... BUG.

On the primary packing list the per unit item weight is SO_PackingListWrk.ItemWeight. On the additional packing lists I am using SO_AdditionalPackingListWrk.Weight.  Does anyone have a theory as to why the weight prints on the primary packing list and does not print on the additional packing lists? 

Also - they can have the same item on a shipment more than once.  For example, line 1 could have qty shipped 14 of item ABCDEF and then line 5 could have qty shipped 25 of item ABCDEF.

LOL!  What's frustrating is that this work table must not had been subject to even basic quality assurance testing.  The first test should be insuring all of the fields in the table could get populated with data from the permanent table!  Now it's supposed to be my job to explain it to Sage, reply to four or five of their emails, then wait for communication from a senior analyst.   This issue has more than likely been discovered before, but the person discovering it simply joined the CI_Item table to get the weight which is what I am going to do.

Somewhere, there is a HUGE pile of S* that people have lost over the years.  If only someone who NEEDED some S&! was able to find this lost pile and make use of it. Sad. Of course, this assumes the losers do not want their S^$ back, which may not be the case.

I'm about to pull a Wayne and lose my S*$% !!  Another one?? I was hoping the additional packing lists used actual weight that was somehow assigned during the shipping process and I was missing where that process occurred.

Well, if you've looked in the Wrk file and the field is empty, I'd say... BUG.

On the primary packing list the per unit item weight is SO_PackingListWrk.ItemWeight. On the additional packing lists I am using SO_AdditionalPackingListWrk.Weight.  Does anyone have a theory as to why the weight prints on the primary packing list and does not print on the additional packing lists? 

Also - they can have the same item on a shipment more than once.  For example, line 1 could have qty shipped 14 of item ABCDEF and then line 5 could have qty shipped 25 of item ABCDEF.

Unfortunately, I think that's what happens a lot - we find a way around it and don't bother letting Sage know about the issue.

LOL!  What's frustrating is that this work table must not had been subject to even basic quality assurance testing.  The first test should be insuring all of the fields in the table could get populated with data from the permanent table!  Now it's supposed to be my job to explain it to Sage, reply to four or five of their emails, then wait for communication from a senior analyst.   This issue has more than likely been discovered before, but the person discovering it simply joined the CI_Item table to get the weight which is what I am going to do.

Somewhere, there is a HUGE pile of S* that people have lost over the years.  If only someone who NEEDED some S&! was able to find this lost pile and make use of it. Sad. Of course, this assumes the losers do not want their S^$ back, which may not be the case.

I'm about to pull a Wayne and lose my S*$% !!  Another one?? I was hoping the additional packing lists used actual weight that was somehow assigned during the shipping process and I was missing where that process occurred.

Well, if you've looked in the Wrk file and the field is empty, I'd say... BUG.

On the primary packing list the per unit item weight is SO_PackingListWrk.ItemWeight. On the additional packing lists I am using SO_AdditionalPackingListWrk.Weight.  Does anyone have a theory as to why the weight prints on the primary packing list and does not print on the additional packing lists? 

Also - they can have the same item on a shipment more than once.  For example, line 1 could have qty shipped 14 of item ABCDEF and then line 5 could have qty shipped 25 of item ABCDEF.

@Doug Higgs - This sounds so familiar with what I encountered in the late aughts when I lived in Iowa (also sometimes confused with heaven in movies).  I needed a field in AdditionalPackingListWrk table (it was available in the PackingListWrk table) and there was no workaround.  I had two options at the proverbial fork in the road - report it to Sage and then move on or just move on.  I chose the easier path by simply moving on.  Sad but true.  Client was happy with what was accomplished.

FWIW, maybe the Minds could convince Sage of the need of a simple bug report website for RESELLERS only.  More often than not, bugs reported are determined to be Working As Designed instead of Working As Desired!!!  Worth a shot.  Chances are slimmer than a snowball in Hades (the pushback for the reversing JE date still burns in memory) but call me Pollyanna....  Maybe one day.

Unfortunately, I think that's what happens a lot - we find a way around it and don't bother letting Sage know about the issue.

LOL!  What's frustrating is that this work table must not had been subject to even basic quality assurance testing.  The first test should be insuring all of the fields in the table could get populated with data from the permanent table!  Now it's supposed to be my job to explain it to Sage, reply to four or five of their emails, then wait for communication from a senior analyst.   This issue has more than likely been discovered before, but the person discovering it simply joined the CI_Item table to get the weight which is what I am going to do.

Somewhere, there is a HUGE pile of S* that people have lost over the years.  If only someone who NEEDED some S&! was able to find this lost pile and make use of it. Sad. Of course, this assumes the losers do not want their S^$ back, which may not be the case.

I'm about to pull a Wayne and lose my S*$% !!  Another one?? I was hoping the additional packing lists used actual weight that was somehow assigned during the shipping process and I was missing where that process occurred.

Well, if you've looked in the Wrk file and the field is empty, I'd say... BUG.

On the primary packing list the per unit item weight is SO_PackingListWrk.ItemWeight. On the additional packing lists I am using SO_AdditionalPackingListWrk.Weight.  Does anyone have a theory as to why the weight prints on the primary packing list and does not print on the additional packing lists? 

Also - they can have the same item on a shipment more than once.  For example, line 1 could have qty shipped 14 of item ABCDEF and then line 5 could have qty shipped 25 of item ABCDEF.