Hi,

can anybody explain the function of the field "lseq" in tdpur401 of Baan5?

In what a relationship is it to the field sqnb of the same table?

Hi Spartacus,

thats`s what I found in LN.

This field is filled with the sequence number of the newly created purchase order line detail in which the backorder is copied when the active backorder is confirmed.

Regards,
Juergen

I can't tell you for a 100% sure, but I think it has to do with backorders. When there is a backorder on that line, then the first line for that position (pono) will have seqn = 0, the first backorder-line will be seqn 10, the second backorder will be seqn 20 etc. In this case, the first record will have lseq 1, indicating there is a next record for backorder to it with seqn 10, the second line will have lseq = 2, indicating that another backorder line is existing with seqn 20...

Hope this clearifies a bit...?


Regards,
Eli Nager

Hi,

thanks for your support. I agree with you. lseq increases with with every confirmed backorder. Normaly at the last sequence of a pone lseq = 0.

Now we have some orderpositions from which more than one sequence has and entry with lseq = 0. I think that may come from the use of session tdpur4501m300 and whinh3121s000 (Correction)

This should be a normale case:
orno: 1
pono:1
sqnb:0
lseq:1

orno:1
pono:1
sqnb:1
lseq:2

orno:1
pono:1
sqnb:2
lseq:3

orno:1
pono:1
sqnb:3
lseq:0

After us of tdpur4501m300 (which deletes the last sequence) and then make a correction of an amount, with whinh3121s000 (which add's sqnb 3 again) we have something like this:

orno: 1
pono:1
sqnb:0
lseq:3 <--??

orno:1
pono:1
sqnb:1
lseq:2

orno:1
pono:1
sqnb:2
lseq:0 <--??

orno:1
pono:1
sqnb:3
lseq:0

You see: the both last records have: "lseq = 0" and even worse: the first record got: "lseq = 3"

Hard to explain. But I hope you understand what I mean.

Heya,

Understand what you mean, seems strange to me too.. Is this the case only for one order, or do you have more/many orders with this pattern..? If you have a support contract, maybe log a case for some functional explanation...


Regards,
Eli Nager

Hi Eli,

thank, you. We have a support contract, but the people who are responsible for the contacts to Baan are not that happy with the support ;-) specially for that problem. It is also not desired to install solution after solution... however...

We will analyse this problem (or feature) in future a little deeper. Therefore my question for a person with a good knowledge about the function of this "lseq"-Field.
Of course, if we get no results we will contact Baan, but first we try without ;-)

And.. just forgott, we have such records also on production system, but a really small amount.
I think our system generates such records in case of deleteing records with the session tdpur4501m300.

kind regards
Richard