Options

Field "Doc. No. Occurrence" in Sales Line Archive

ib000904ib000904 Member Posts: 19
Anyone got a clue as to what the field "Doc. No. Occurrence" in table "Sales Line Archive" is used for?
When entering a new order, and after releasing it, this field "Doc. No. Occurrence" in table 5108 always contains '1'. Subsequently opening and rereleasing the order only changes the value of field 'Version No.". Repeated testing never resulted in any other "Doc. No. Occurrence"-value than '1'.

Somehow however, in older records in our live-system i sometimes encounter "Doc. No. Occurrence" -values of '0' (or even '0' and '1' records within the same ordernr).

Could anyone tell:
- what the purpose of this field is
- under what circumstances a value of '0' can occur
- or even why sometimes '0' and '1'values exist within the same ordernr.

Comments

  • Options
    Revolution1210Revolution1210 Member Posts: 161
    The Doc. No. Occurence field specifies the number of times a document no. has been used/archived.

    e.g.,

    Say you create a Sales Order with a document no. of 001

    The Doc. No. Occurence on this Sales Order will be 1

    You then archive the Sales Order and subsequently post it.

    You then create another Sales Order with a document no. of 001 - the Doc. No. Occurence on this Sales Order will be 2.
    Ian

    www.NextEqualZero.com
    A technical eye on Dynamics NAV
  • Options
    ib000904ib000904 Member Posts: 19
    Ok, i understand that. But, the problem is, we never re-use old ordernumbers.
    Let me present you with the figures i found in the Sales Line Archive file.
    The '0' occurence appears even after the '1'occurence.
    Could anyone figure out the sequence of events that might have lead
    to such data?

    Table 5108 - Sales Line Archive
    Doc. No. Occ - Version - Archive Date - Line Nr. - Customer
    0 1 18-01-2008 1000 30732
    0 2 21-01-2008 1000 30732
    0 3 21-01-2008 1000 30732
    0 3 21-01-2008 2000 30732
    1 1 15-01-2008 1000 11098
    1 1 15-01-2008 2000 11098
    1 1 15-01-2008 3000 11098
    1 1 15-01-2008 5000 11098
    1 2 15-01-2008 1000 11098
    1 2 15-01-2008 2000 11098
    1 2 15-01-2008 3000 11098
    1 2 15-01-2008 5000 11098
  • Options
    SonGoten13SonGoten13 Member Posts: 44
    Hi,

    I have the same problem as ib000904.
    Anyone an idea?

    €: Version 5.01 with SQLServer2005
Sign In or Register to comment.