Hi,

I have added a new table field tdsls045.flag (Yes/No) in table tdsls045. It's default value at table level is tcyesno.no
We are doing partial delivery of an order & making this flag (tdsls045.flag) to "Yes" after release outbound.
We are doing partial delivery so we have back orders. While confirming back orders, session is inserting a new sequence in table tdsls045 for that particular order & position (Standard Functionality).

My problem is if a new sequence is added in table tdsls045, field tdsls045.flag should be "No" because it's default at table level; but system is making it "Yes". I don't want to customize standard session "Confirm Backorder Quantity".
I just want to understand that what may be the reason of making field tdsls045.flag to "Yes" even though its default value at table level is "No".

Quick reply would be appreciated.

If you have source code can you debug it to see what it is doing? I know the one time I did something like this I did a find of the last record, updated the sequence and another field, then did an insert. That was a lot easier than setting all the fields. We don't own source code so I can't look to see how they are doing it.

Yes, I think before a new record is inserted to tdsls045 the "confirm back orders" session did not do a db.set.to.default and use the value of the last read record for the new table field.

If you make the tdsls045.flag to "Yes" after confirming the backorder then the new sequence will get the tdsls045.flag "No".
This is just a work around.