Posting Goods Mvt in future

[bhushan_bivalkar]

I observed that system allows to post goods movement in future date in current open period . Example : Todays date is 03.03.2010 then system allows me to post goods movements ( also PGI ) on 04 . 03. 2010 or even I can post goods movements on 31.03 2010.

How its possible ? Is there any option to restrict such future date entries ?

Also I need end user should not allow to post back dated entries. These back dated posting must be posted by only selected users .

Regards

Bhushan

[Former Member]

Hi Bhushan,

If you want to avoid posting of GR of back dated or future date , then you can introduce a field exit. where in, if the user enters the date (MKPF-BUDAT /BLDAT) greater than or less than system date, it should throw an error message hence stopping the user from posting the GR.

In this way you can restrict the user for entering the GR only for the current date.

You can get more input from your ABAPer.

regards

Vinay

[Former Member]

Hi,

go to T-code MIGO , in the menu system-services-jobs-define a job,

where you define a job and schedule it for required date,

rgds

[bhushan_bivalkar]

I think you have not understood the question . Please read it carefully , System should not allow posting in future .

[Former Member]

Hello Bhushan ,

This is the standard behaviour of the system .

The system allows postings in the potsable periods , whether in past or in future . But the key is that at the time of posting the stock should be consistent. That is there should be enough stock coverage.

There is no way that this could be avoided .

Also future postings may affect the stock ledger & there may be instances where the closing/opening balances may be in negative.

User discipline is teh only solution .

Moreover , the system always defaults the current date as the posting date . Hence anyone making a posting in future/past is assumed to be fully aware of the repercussions.

Regards

Anis

[bhushan_bivalkar]

Ok , I agree with you but user disipline is bit a critical issue with my client so this requrement is raised . Also we want to avoid back dated postings by common end users ( only selected 1 or 2 people can do back dated postings) so I am looking for options to restrict that