cancel
Showing results for 
Search instead for 
Did you mean: 

Actual Goods Movement Date in VL06G

Former Member
0 Kudos

Hi Experts,

We have a requirement of restricting the ability of changing the actual goods movement date when performing the Post Goods Issue in VL06G. At the time of recording the PGI in VL06G, a dialog box appears with the current calendar date asking the user to specify the actual goods movement date.

At present, user can edit the data and do the PGI. We want to disable this facility and record the PGI at the actual date where it has been performed. Could anyone let us know how we can disable the edit-ability of Actual Goods Movement Date.

Thanks in Advance !



Regards,

PradeepJ  

Accepted Solutions (0)

Answers (2)

Answers (2)

Prasoon
Active Contributor
0 Kudos

Hi,

   Create a transaction variant for VL06G in SHD0 transaction and maintain the field as "output only" and activate the variant. Now, the field wont be editable.

   If you required, you can activate the variant for specific users as well, through user groups.

Regards,

AKPT

JL23
Active Contributor
0 Kudos

Isn't your desire to restrict maintenance contradictory to your aim to post with the exact Goods Issue date?

What if the user forgot to perform goods issue yesterday while the goods have left your plant yesterday. Which date would you want then want in your movements? today or yesterday?

What if the the posting period gets closed early e.g. Christmas time we often close the books December 23nd, but an extraordinary delivery may occur between then and January first.

Former Member
0 Kudos

As per our business requirement, there shouldn't be any delays between physical goods issue and system updating of PGI. User should perform the PGI and physical issuing at once.

JL23
Active Contributor
0 Kudos

Between dream and reality is often a big gap. If everything goes well, why do you even have to fear that a user touches this field for a change, because in this case he would on purpose do something wrong and could directly get fired, isn't it?

Have you already tried with a screen variant?