Welcome, Guest. Please Login.
05/19/25 at 22:44:57
News:
Home Help Search Login


Pages: 1
Send Topic Print
SHIPPER # (Read 1576 times)
wtsconnects
Full Member
***




Posts: 113
Gender: female
SHIPPER #
12/03/03 at 14:06:15
 
We are on the 11/04 ISTech update and have default set to set packslip same as invoice.  Mostly this works quite nicely.  Grin
 
Lately we have found that on some SO's when released in SO-E, the shipper number comes in as an old number from ???  and is out of sequence with the next invoice number  ???  Also, the ship date is filled in as 11/14/03.   We have always had random dates pop-up.  I can blank out the ship date but can't change the shipper number.  Why would this happen??
 
Thanks for the feedback.
Back to top
 
 

Jackie O.
WTS Connects
DBA Classic 2004.1
IStech update 6/20/05
Workgroup Server NT4.0
Email WWW   IP Logged
wtsconnects
Full Member
***




Posts: 113
Gender: female
Re: SHIPPER and Invoice # Duplication
Reply #1 - 12/05/03 at 11:39:25
 
Related to the same issue previouly posted we have now discovered that DBA has duplicated an invoice # Shocked  on a sales order that had 2 shipments on different dates ( 11/10 and 11/18), different part numbers.  
 
I can't duplicate the original invoices as 2 shipments (which is not a surprise to me) and can only reprint the invoice with both lines  shown 2x each.  Also, when viewing information  in SO-I both lines show 2x as if we double shipped each line.  Do I clean up the records in maintain database BKARHIVL ( or some other file)- and assign a new number to the second shipment?  The first shipment has been paid by the customer.   I need to quickly resolve this in order for our customer to process the second payment.
 
Help anyone!
Thanks  
 
Back to top
 
 

Jackie O.
WTS Connects
DBA Classic 2004.1
IStech update 6/20/05
Workgroup Server NT4.0
Email WWW   IP Logged
Lynn_Pantic
Administrator
*****


evolution (n) -
gradual change to a
different form

Posts: 5663
Re: SHIPPER #
Reply #2 - 12/05/03 at 11:47:03
 
Yes, I would suggest Maintain Database on BKARHIVL to get rid of the extra lines and reassign the one from the second shipment to a new BKARHINV record with a new invocie number.
Back to top
 
 

Lynn Pantic
IS Tech Support
lynn@istechsupport.com
Email   IP Logged
wtsconnects
Full Member
***




Posts: 113
Gender: female
Re: SHIPPER #
Reply #3 - 12/06/03 at 17:01:22
 
Thanks.  I'll give it a try.
 
Back to top
 
 

Jackie O.
WTS Connects
DBA Classic 2004.1
IStech update 6/20/05
Workgroup Server NT4.0
Email WWW   IP Logged
wtsconnects
Full Member
***




Posts: 113
Gender: female
Re: SHIPPER # doesn't Work
Reply #4 - 01/05/04 at 15:12:46
 
We are still having a heck of a time with the feature to coordinate invoice and packing slip numbers.  
 
In addition to having random sales orders pull in a really old (previously used) packing number in SOE,  we have found that once a release is done in SOE, DBA grabs the next invoice number AND, if the release is cancelled (with no invoice or packing slip printed) the invoice number is not made available for the next shipment ( we have an invoice number which appears to be lost).  
 
To fix the first part of the problem I have gone into SDQ to reset the feature and have tried to reset the next packing slip number. This seemed to work for awhile but again SO releases pull up old ship dates and old shipper numbers.  
 
Don't know what to do about the last part.
 
Is this feature working ok for  everyone  else???  No one responded to my previous post
 
Lynn, Perhaps we have set this up the wrong way? - I hope so but can't figure.
 
thanks.
Back to top
 
 

Jackie O.
WTS Connects
DBA Classic 2004.1
IStech update 6/20/05
Workgroup Server NT4.0
Email WWW   IP Logged
Lynn_Pantic
Administrator
*****


evolution (n) -
gradual change to a
different form

Posts: 5663
Re: SHIPPER #
Reply #5 - 01/05/04 at 17:38:02
 
Jackie -
 
Once you release an order and the invoice/shipper number is pulled, that number is assigned to that sales order the same as if you printed an invoice so canceling the shipment will not release the number.  Eventually when you process the next shipment against the sales order, it will use that invoice/shipper number.  If that won't be for some time and you want to keep your invoice numbers in close to chronological order, you can add a $0 type N item to the sales order and process the $0 invoice to use the number and keep things in sequence.
 
As for occasionally pulling in an old shipper number, not sure why that would be but if you can post ALL released invoices so there are no sales orders that should have any invoice/shipper numbers pending, we can clear all the shipper numbers by using UT-K-B, file BKARINV, field BKAR.INV.SHIPPR and replace all values with blank.
Back to top
 
 

Lynn Pantic
IS Tech Support
lynn@istechsupport.com
Email   IP Logged
wtsconnects
Full Member
***




Posts: 113
Gender: female
Re: SHIPPER #
Reply #6 - 01/06/04 at 15:06:59
 
Lynn -
I took a peek but did not proceed.  I definitely need more direction on this.  What do you mean by   "replace all values with blank"?  
 
JO
Back to top
 
 

Jackie O.
WTS Connects
DBA Classic 2004.1
IStech update 6/20/05
Workgroup Server NT4.0
Email WWW   IP Logged
aricon
Active Member
*****


Systems
Consulting-See
website for
products!

Posts: 1283
Gender: male
Re: SHIPPER #
Reply #7 - 01/06/04 at 16:27:21
 
She means, using the Global field replace on that file and that field, in the box that says value to replace with you would simply leave it blank. And replace all values.
Back to top
 
 

Sincerely,

Lorne Rogers
President
Aria Consulting & Implementers Ltd.
Phone: (780) 471-1430
Fax: (780) 471-4918
E-mail: lrogers@ariaconsulting.net
Email WWW   IP Logged
wtsconnects
Full Member
***




Posts: 113
Gender: female
Re: SHIPPER #
Reply #8 - 01/06/04 at 17:32:51
 
I understand the steps but I trying to make sure I understand what we end up with after this process - don't know what  the  field BKAR.INV.SHIPPR refers to. Would I be replacing shipper data in all open sales orders?
 
 
thanks
Back to top
 
 

Jackie O.
WTS Connects
DBA Classic 2004.1
IStech update 6/20/05
Workgroup Server NT4.0
Email WWW   IP Logged
wtsconnects
Full Member
***




Posts: 113
Gender: female
Re: SHIPPER #
Reply #9 - 01/06/04 at 20:14:24
 
We did it just before releaseing another SO where the shipper # came up with an out of sequence # - cleared it up and  everything seems to work!
 
thanks for he help
Back to top
 
 

Jackie O.
WTS Connects
DBA Classic 2004.1
IStech update 6/20/05
Workgroup Server NT4.0
Email WWW   IP Logged
rlevasseur
Member
**


This forum is a
great help!!

Posts: 72
Gender: male
Re: SHIPPER #
Reply #10 - 01/16/04 at 10:37:55
 
We are also having a difficult time in the coordination of shipper no's and invoice no's.
 
We have a number of customers who do not receive invoices from us but use the shipper no to generate their own internal invoices. We print a invoice here to file with the job folder and also to help track payments, therefor, it is alot easier to track by Invoice number rather than referencing a shipper no.
 
This update works great, BUT, everyonce in awhile, the counters get out of whack and when caught we go into SD-N and reset the numbers.  
 
I wonder if it would be easier to be able to change the shipper no at the realease screen and when saved the shipper would automatically pull the matching invoice?
 
Rick   undecided
Back to top
 
 

DBA 2018.2 w/ IS TECH SUPPORT UPDATE
EVO/ERP 2018.2 Build - 7/23/2018 T7 - 7iR11
Pervasive Version 11.30 Peer-to-Peer
XP Pro, Windows 7 Professional
  IP Logged
wtsconnects
Full Member
***




Posts: 113
Gender: female
Re: SHIPPER # - more problems
Reply #11 - 07/20/04 at 12:38:11
 
Same problem occured again today.  A group of sales orders being released (various customers, dates, etc) came up in  SO-E with preassigned/previously used shipper #'s.    ???
 
We just happened to notice because the # sequence was way off.  
 
We used the same method (described in previous post) to clear and reset, but are left a bit concerned about future occurences that won't get caught before shipments/invoices go out.
 
Any insights?
 
Back to top
 
 

Jackie O.
WTS Connects
DBA Classic 2004.1
IStech update 6/20/05
Workgroup Server NT4.0
Email WWW   IP Logged
wtsconnects
Full Member
***




Posts: 113
Gender: female
Re: SHIPPER #
Reply #12 - 08/31/04 at 16:07:39
 
We have just had occurence of old shipper/invoice  numbers being reused (randomly) by DBA.  Just released about 13 sales orders and 4 of them picked up old numbers  Angry
 
 
We could really use help to fix this once and for all.
 
thanks
Back to top
 
 

Jackie O.
WTS Connects
DBA Classic 2004.1
IStech update 6/20/05
Workgroup Server NT4.0
Email WWW   IP Logged
Pages: 1
Send Topic Print