Can you give us some example menus and or functions?

I was already afraid this question would be asked. Unfortunately I can't, because this is only experienced in a form/query that was made for us to print palletlabels, so no other menus or functions like that. Therefor my questions was pretty general if someone was familiar with this problem.

But I guess I better rest my case and first wait if the solution I created may be sufficient. Maybe all this is then not necessary to investigate.

Hi,

I guess your request has to see with working in shifts ? We have a similar situation where people register hours spent on a machine.

We have a parameter in some control file, where we can indicate the 'end of day' shift. If it is set to 6, then everything registered till 6AM is posted with an effective date set to the day before.

I read your progam is a customized program, maybe yyou can add this simple change to it also ?

kr,

Francis 

Hi Francis,

I'm afraid that is not a solution.

As far as I've been able to analyze the code that is ran, in the usr_workfl there is a record with a value that is the base for calculating the new expiry date. This new expiry date should be recalculated every night at 00:00h. It appeared that a range of items was not in scope with this recalculation. I modified the code and hope this is the solution. However, the problem did only appear every now and then, depending on what item was produced at 00:00h. So far I haven't heard anything about it, so I hope the issue is solved.

Thanks for all the thinking.

Now I understand, what you call the "Actual Date" is called "Effective Date" in QAD. Example: create the Expire date based on the "Effective Date".

The "Effective Date" is the date the transactions did happen. The Transaction day is the day you actually "keyed in" the transaction. In transaction history you will note that these two dates are separetely  stored. (3.21.1/3.21.2)

I know their are certain menus that will keep the "Efective Date" if this menu is not closed or renewed.

Let me know if this is what you meant. Thanks, Raymond

Hi Raymond,

I guess this indeed is the sort of problem I mean.

It appears we have two customization fields :

- one to record the days before expiration (for example "365")

- one to record special customer-demands for the notation (for example 1st day of the next month)

Based on these 2 fields every night the new value for the field pt_shelflife is recalculated and now (2nd jan 2018) it says :

2-jan-2018 --> + 365 = 2-jan-2019 --> 1st day next month = 1-feb-2019 --> 1-feb-2019 -/- today = 395.

Tonight at 00:00h this is recalculated and will become 394.

This value "395" is used to calculate the date that needs to be printed on the package and pallet labels. However, gaining that new value appeared to be the problem. For some items (not all, only some) did not get that new value.

As mentioned, I hope that I've already fixed the problem, the future will tell. If not, I might be back, but with your reply in the back of my mind, it could be there's no other solution than to close the menu. Once again thanks.

I have seen these kind of customizations before. The interesting this is where the data "2018-01-02" is stored! Is this in the "effective date" or the "transaction date"!  Good luck and thanks for the reply.