Author Topic: CUST.LN.NUM in the ORDER.HISTORY file  (Read 2460 times)

DonQuixote

  • Rock Star
  • *****
  • Posts: 204
  • To Dream the Impossible Dream...
CUST.LN.NUM in the ORDER.HISTORY file
« on: July 20, 2017, 02:13:07 PM »
What is the CUST.LN.NUM (field 92) in the ORDER.HISTORY.LINE file?
Why would it ever be blank?
I notice there is a CUST.LN.NUM.CTR in ORDER.HISTORY (field 81) is CUST.LN.NUM.CTR which is the last number used.

precisonline

  • President
  • Administrator
  • Rock Star
  • *****
  • Posts: 1612
    • Precision Solutions
Re: CUST.LN.NUM in the ORDER.HISTORY file
« Reply #1 on: July 20, 2017, 04:00:31 PM »
When a customer order is from a customer's printed (or transmitted P/O), the customer line number on each line on the sales order refers back to the customer's P/O line number.
-Kevin
Accidents "happen"; success, however, is planned and executed.

DonQuixote

  • Rock Star
  • *****
  • Posts: 204
  • To Dream the Impossible Dream...
Re: CUST.LN.NUM in the ORDER.HISTORY file
« Reply #2 on: July 20, 2017, 04:09:48 PM »
I've noticed two things.
1. comment lines do not get a customer line number
2. if a line is split all related lines get the same line number.
  (e.g. You can take an order for 1200 items in line 1 and ask to split the line into 12 separate required dates.  Some how Prelude will take your one line and create 12 lines out of it but it keeps the same customer line number)

Normally, the customer line number just increments.

precisonline

  • President
  • Administrator
  • Rock Star
  • *****
  • Posts: 1612
    • Precision Solutions
Re: CUST.LN.NUM in the ORDER.HISTORY file
« Reply #3 on: July 20, 2017, 04:26:39 PM »
Is that a concern?  If I had one P/O with one line on it and I typed it into Prelude over 12 order lines, wouldn't I want all 12 to point back to the same line number on the P/O?
-Kevin
Accidents "happen"; success, however, is planned and executed.

DonQuixote

  • Rock Star
  • *****
  • Posts: 204
  • To Dream the Impossible Dream...
Re: CUST.LN.NUM in the ORDER.HISTORY file
« Reply #4 on: July 20, 2017, 04:33:04 PM »
 :-\   Maybe.  I just don't have control over that number and its all dependent on the order of entry. 

precisonline

  • President
  • Administrator
  • Rock Star
  • *****
  • Posts: 1612
    • Precision Solutions
Re: CUST.LN.NUM in the ORDER.HISTORY file
« Reply #5 on: July 20, 2017, 04:37:16 PM »
I think it's just there as a convenience.  How are you wanting to use it?
-Kevin
Accidents "happen"; success, however, is planned and executed.

DonQuixote

  • Rock Star
  • *****
  • Posts: 204
  • To Dream the Impossible Dream...
Re: CUST.LN.NUM in the ORDER.HISTORY file
« Reply #6 on: July 20, 2017, 04:49:49 PM »
I've been asked to extract data for each order line but using the Customer Line number instead of the Order's line number.  But, that isn't unique and that's the issue.  To keep it unique the user has to understand I need to use the order line number and live with the fact it doesn't reference the Customer's line number.   :-X

precisonline

  • President
  • Administrator
  • Rock Star
  • *****
  • Posts: 1612
    • Precision Solutions
Re: CUST.LN.NUM in the ORDER.HISTORY file
« Reply #7 on: July 20, 2017, 04:52:09 PM »
Why not use the line sequence instead; that is, the line number that appears in /SOE?  I would load up the order header, locate the key in <200.M>, and use that position.
-Kevin
Accidents "happen"; success, however, is planned and executed.

DonQuixote

  • Rock Star
  • *****
  • Posts: 204
  • To Dream the Impossible Dream...
Re: CUST.LN.NUM in the ORDER.HISTORY file
« Reply #8 on: July 31, 2017, 07:42:26 PM »
They finally accepted the fact that lines number were unique but complicated the situation by making me replace kits with the kit parts.  My solution was to use the line number and .1, .2, .3... for the kit part positions.   :o

precisonline

  • President
  • Administrator
  • Rock Star
  • *****
  • Posts: 1612
    • Precision Solutions
Re: CUST.LN.NUM in the ORDER.HISTORY file
« Reply #9 on: July 31, 2017, 07:57:00 PM »
Sounds like a fantastic solution.
-Kevin
Accidents "happen"; success, however, is planned and executed.