Restrict posting in future date

Dear All,
During VL01N,VF01 system is allowign me to post documents in future date than the current system date.
i want to put validation in system that it should not allow future posting date than current system date.
pls guide.

1) To implement lock in Delivery
The BADI definition name is LE_SHP_DELIVERY_PROC method name is CHANGE_DELIVERY_HEADER. Here consider the field "Actual GI Date"
2) To implement lock in Billing
Go to VTFL, select your item category for the combination of your delivery type and billing type and assign routine 11 for the field "Data: VBRK/VBRP"
thanks
G. Lakshmipathi

Similar Messages

Posting in future date

Dear expert,
In our client , one of our user has accidently posted certain document in future date. Since the period are open for 2 months so any one can post the document in any of the date. I want to restrict user so that he will not be able to post the document in future date.
Regards,
Kapil.

Dear sir,
For that u have to use the BADI.
Badi to control the future posing date in migo : MB_MIGO_BADI.
create in this badi it will work. in that interface you have to use is : STATUS_AND_HEADER.
and write below code in the interface : STATUS_AND_HEADER.
method IF_EX_MB_MIGO_BADI~STATUS_AND_HEADER.
data : v_date like is_gohead-budat.
if sy-tcode = 'MIGO'.
v_date = is_gohead-budat.
check v_date GT sy-datum.
message : 'posting Date is future than system date' type 'E'.
endif.
endmethod.
if any clarification please let me know.
regards
jrp

SAP Posting to Future Date

Dear Gurus
SAP as an standard allows posting to a future date. Our client requirement is that we need to restrict the same so that no user can post to a future date. What is the setting required to be done for the same?
Regards
Rahul Taneja

Hello,
There is no setting as such, unless you open 365 posting periods, which is not feasible, due to high maintenance.
You can write a validation in the system GGB0 saying that (at document header)
Posting data not greater than system date, say otherwise give ERROR.
Assign this validation in OB28 for your company code.
Hope this will solve your issue.
Regards,
Ravi

Invoices posted for future dates could not shown in Outgoing Payment table

Hi, Experts,
We posted an A/P invoice for the future date (next month), and then we'd like to pay it under Banking -> Outgoing Payment -> Outgoing Payment the current date. But when we selected the vendor account, we could not find the invoice listed in the table.
Would this be anyway to show all the invoices posted with a future post date in the outgoing payment table?
Thanks!
Lorrie

Hi,
As it seems to be the current behavior of the system, the best option could be Payment on Account.
You can create a Payment on Account for payment on currenct date and when the AP Invoice is added you can Link the same to the Invoice afterwards.
Look out for other options if provided here by the experts.
Regards,
Jitin

Forward scheduling auto post to future date

Hi all,
I have got a problem about post goods issue. When post to a past GI date, the system said "Delivery date cannot be met, forward scheduling to delivery date 10.07.05 00:00 Message no. VL127" and post to today date automatically. It should not allow to post.
Anyone know what is the problem?
Thank you.

See transaction OVM1
Also, check SAP Note
- Note 150576 - Error message VL127 on creating delivery from project.
- Note 154824 - Error in Customizing of controllable error msgs
Thanks & Regards
JP

Restrict from entering future billing date

Dear all,
I want to restrict to take future date in billing document. For that I have maintain routine 011 in copy control for Data VBRK/VBRP. But by this billing document is taking todayu2019s date as default date. This is ok but it is still taking future date if I enter in initial screen. I want to restrict user from entering future date. It shd not all future date.
Thanx

For that I have maintain routine 011 in copy control
In this routine itself, you also add the logic such that if user try to key in any date after the system date in FKDAT, system should throw an error message. Your ABAPer can achieve this.
thanks
G. Lakshmipathi

RWDPOSUP For future date articles postings.

Hi All,
Currently we are running the program RWDPOSUP for sending articles from sap to third party.
I have a query.the system will pick articles which have a valid date from today or a specified number of days for example 30 days
all the validity is stored in the field DATAB of table A073 for instance(Pricing condition tables)..
So if the pricing has to be changed on march first then it takes the data on feb first and runs the idoc and data is sent to third party.
So if i post a document today i.e., 21st march 2010with date of validity as march first 2011. then ideally it should not pick and create an IDOC.
It should pick on feb first or jan 29th(30days before) and then create idoc. will the program RWDPOSUP run as desired.
for me if the DATAB is more than 30 days it should not create an IDOC only articles withing 30days are to be sent to third party.
Can you please suggest on this. i am searching where it looks for date validation but not succesful in that search.
Any help would be appreciated.
Thanks,
RK.

Hi,
I have changed it from W to E and saved , still system is prompting any message at all
document is getting posted for future date also .
in MB1B screen posting date is changeble field and if i try to put tomorrow date and try posting its getting posted
please help
please try at your end once .
regards,
madhu kiran.
Edited by: madhu kiran on Apr 24, 2009 11:19 AM

Future Date Restriction in Transaction J2I5

Hi,
Is there a possibility to restrict "Excise Register Extraction" for Future Dates in J2I5 T code?
Please assist on this...

Issue resolved by ABAP changes

Restricting the Travel expense claims for future date

Hi,
We are configuring the BPs for ESS & MSS. Currently we are on NW portal 7.0 ,SPS15 and ECC6.0 at the backend.
Can anyone suggest us, how to restrict the users NOT to apply the Travel expense claims for the future dates (i.e.the portal system is expected to allow the users for the claims, till the current date or any past date but not any future date) through portal.
Currently, the system is allowing the users to apply the Travel Expense claims for the future dates also.
Any help on this will be appreciated.
Regards,
Venu

Hi Venu,
I am not sure whether there is any configuration through which it can be achieved or not. But you can use Badi TRIP_WEB_CHECK for WebDynpro.
Hope this will help.
Thanks & regards
Arun

Restrict Time Entry for Future Date in Portal

Hi Gurus,
My scenario is to restrict users from entering future date attendance in Portal.
I know the configurations for restrictiong the user from scrolling to future week.
But in my scenario users will be able to scroll to future weeks but should be restricted with an error message while trying to enter future time.
Please let me know if you have any suggestions.
Thanks.
Regards
Sairam Maharaj S
Please search in the ESS forum as I remember responding to a similar scenario some time back. Thread is moved.
~Suresh

Hi Srini,
Thanks for your reply.
I have achieved this by deselcting Release Future Time option. But user wants the future time to be restricted even from getting saved. Can I make changes to the default information message "1 out of 1 future time not released" to an error message so that the user will not be able to save. If so please let me know if this can be achieved from any configuration of messages or it should be done from the programming side.
Thanks.
Regards
Sairam Maharaj S

Posting period is showing in future date

Hi,
This is issue am facing in my IDES system.
The error it is showing is as below:
Posting only possible in periods 2015/03 and 2015/02 in company code z001 and message number M7053
other inputs: MMRV : Current peiod   : 03 2015
                                       Previous period: 03 2015
                                   Last period in previous .year 12 2014
And one more input about this is, in my system the system timing was showing 2011, this i did not recogbise, and when i tried to do the post goods issue(PGI) system shown some Posting error then i cloed the periods through MMPV t code, and closed upto 02 2015, then i reliazed why still system is allowoing to close the periods. then i checked the sytem timing and corrected it to current date.(13 th July 2014).
In OB29 my Fiscal year variant is K4 (number of posting periods 12 and no of Special periods 4) is assigned to my company code z001 in t code ob37
In OMSY "also showing the 2015 3
Now even after changing the sytem date to correct date still system is showing the periods problem, when i tried to initialize the periods in t code MMPI sytem is showing the below message "Follow the instruction note 487381 before initialiazation"
I found many treads similar to this issue, but all of them faced past date, needs to be closed the periods until current date, where as in my case the periods alredy open in future date.
am not much familiar with this periods problem as am SD consultant.
Please help to resolve this issue.
thanks,

Nobody needs help of an ABAPer to close or open periods, this is just normal customizing.
Goto service.sap.com/notes and read the content of the OSS note mentioned in your message and just follow it, as it is the only way to run period initialization. It does not matter it you rolled it to far into the future or if you still have stone old periods like in the hundreds of other discussions on the same issue.
And since this is that often discussed I am locking this thread.

Goods Receipt in future Date

Hi,
Please tell me if i can restrict the production order for doing GR for a future date???
If today is 22/10/2009, and i am trying to give the posting date in MIGO as 25/10/2009 then system should restrict it.
Thanks

HI
Check this Badi WORKORDER_GOODSMVT
In REM i have achieved the same with the help of BAdi RM_BFLUSH_GOODSMVT.
Check the first one with the help of ABAPer
Regards
Anupam Sharma

Purchase order error with future date

Hi,
Here one scenario like
We have created a sales order VA01-->Pur. Order ME21N with current date i.e., 05.09.2008. System able to post perfectly and post MIRO, cutomer invoice and finally released to accounting.
Now, same sales order VA01-->Pur. Order ME21N with future date i.e., 05.09.2009. System threws error message "Account requires an assignment to a cost object".
Here my question is, why system is asking this assignment if i gave future date(05.09.2009) and why system is not asking if i gave current date(05.09.2008) ? remaining all are same except date
Looking forward your comments/thoughts
thansk
anifi

Hi,
Thanks for your reply
regards
Edited by: Anifi on Sep 22, 2008 6:18 AM
Edited by: Anifi on Sep 29, 2008 2:05 PM

Future date not to be allowed in the tabular form

Hi,
I have a tabular form with 3 columns.. the first column name is DATE, the user is not allowed to enter a future date or a date greater than the sysdate, so as soon as the date value is entered I have to generate a javascript/dyanamic action that throws error... I don't want the alert message to pop up when the submit is pressed, when the user moves the cursor to the next column, error should be shown. Is this possible. I am using APEX 4.0

Hello Suzi,
I’m afraid I won’t be able to walk you through this issue as I need to leave the office, however I have some remarks for you.
First, if you intend to practice JavaScript you should really find the time to learn and understand it. I can promise you it will worth your while, otherwise you’ll just waste a lot of time.
Secondly, The values of the APEX items you are retrieving using JavaScript are strings. So, in your current code you are actually comparing two strings and not dates.
Next. When you are validating your data using JavaScript you have to make sure that the user will take the necessary measurements to fix the problem. For example, you must place the cursor back in the offending field. Using the following:
wwv_flow.f04[1].focus(); will set the cursor in the first cell of the ‘f04’ column. This code also suggest that wwv_flow.f04 is actually a JavaScript array that holds references (object pointers) to all the cells in the ‘f04’ column. You can go through them using a simple loop.
You should also not use the onchange event in this case. Imagine that after your first error alert, and setting the cursor back to the offending field, the user just press tab to move to the next field. This time around, the onchange event will not be fired (as the value of the field has not changed) and you lost your validation effect. To force the JavaScript validation to fire every time you should use the onblur event.
That’s all for now :)
Regards,
Arie.
&diams; Please remember to mark appropriate posts as correct/helpful. For the long run, it will benefit us all.
&diams; Author of Oracle Application Express 3.2 – The Essentials and More

O4NM or O4TEN Create & Actualize a Ticket with future date

Hi,
I would like to create a ticket with future date; in the tab 'Movement Details'....'Start Date', 'End Date' & 'Posting Date'.
Example: Ticket to be created with the start & end date as 05/20/02008.
System throws error : Cannot actualize a ticket for a future date or time.
Please suggest.
Thanks
Parveen

Hi Sandil,
During the ticket creation, when I'm entering the 'Start Date' and 'End Date' with a future date eg 05/30/2008; getting the error.
The requirement is to create & actualize the ticket with dates 'Start Date', 'End Date' and the 'Posting Date' with future date.
FYI, there is a significant number of tickets that are booked using end of the month date in order to avoid several fees. We also have to do closing and reconsolidations end of the month. These activities create a significant stress to complete tasks before deadlines. Along with that, we also have to complete ticketing that we scheduled for end of the month. Therefore, resolving the issue of been able to ticket and actualize tickets ahead of time would substantially make processes and procedures easy when we are stretched for time which we don't have towards the end of the month.
Please suggest.
Thanks
Parveen

Restrict posting in future date

Similar Messages

Maybe you are looking for