Start date in past

Hi all ,
What for the need / concept of the Stat date in past has been given in Scheduling paramters ?
or why i have to create the order in past date when practically i can not mfg the prodcut in past ?
Thanks in adv .
Regards

Hi,
For every production order we are scheduling with some cushion time because of many interruptions. These cushion timings given in schedule margin key.
As per system schedule , production start date in the past. We can not start production from the past date.
But with these cushion timings float before production, opening period we can eleminate & possible to start production from today.
So no need to reschedule the order.
Hope this helps you.
Regards,
Dharma

Similar Messages

SNP Planned Order start date in past

Hi
After SNP run, for the past requirements it is giving avaiablilty data as today but the planned order start date is in past. Now this order fails in CIF as the production version in R/3 is valid from today.
In the strategy profile we have backward+reverse with infinite scheduling. In this case the start date should be todays date for past requrirements... am I correct?
Regards
Abhishek Rai

Hello Abhishek,
We are also facing the same issue. Did you find any solution to this issue?
We are on SCM 7.0 with EHP1.
Thanks,
Mangesh

In plant parameters how the start date in past will be applicable for order

Hi All,
Can any one explain me in detail start in past for plant parmeters (OPPQ).
Regards
sailendra

Hi,
Start date of order proposals allowed in the past
This indicator defines that the system does not automatically switch to forward scheduling if the order start date lies in the past for determining the basic dates. With this indicator, backward scheduling is always used to determine the basic dates, even if the start date lies in the past.
e.g Bacward scheduling type, Today date is 08.06.2009
If u give basic finish date say 25.06.2009,and system propose you basic start date in 06.06.2009. That is 06.06.2009 is lies in past date.In this case system propose you forward scheduling.Means order basic start date is 08.06.2009 .If you don't want to system propose you for forward scheduling tick mark Start in past in OPPQ.
Hope this clear you.
Regards,
Raja.

Scheduling Start Date in Past for PurchReq settings

Experts,
for work orders the range of how many days I allow the system to schedule in past is located in OPU3 and OPU5, Section: Scheduling Control for Detailed scheduling; Field Start in Past.
Where are these settings for purchase requisitions located ?
Thanks in advance
Jörg

HI
Go to T code OPPQ Maintain plant parameter > select your plant then > Start in Past> select check box for start in past also chekc as suggested by Mr Mangalraj In T code OMIT.
Setting form OPPQ will overwrite in OMIT.
Check at your end.
Regards
Anupam Sharma

Start date is in the past: today scheduling

Dear all,
How can I fix that error:
*Start date is in the past: today scheduling*
*Message no. C7030*
Diagnosis
The start date determined in scheduling is in the past.
In customizing, you have defined the number of days that the start date is allowed to be in the past. This number is exceeded.
System Response
"Today" scheduling is carried out.
how can i definea new number of days ???????????

Open ur project in Planning board then go to "Settings->options"
and enter number of days in the "Start in past" filed more than difference between todays date and Project Start date. Then Scheduling will consider the Project start date as Scheduling start date. Otherwise system will do "Todays scheduling" and it will reset the Project start date to todays date.
Venkat

Problem-planned order start date in the past

I use PP-PI - After MRP run, planned order was created and has exception message "06-start date in the past" its make me wonder because before this problem occur we already tested many time and never found this message(06). then i check in OPPR- field "start in past" is blank, OPPQ- field "Start in past" are not check, OPUZ-Scheduling Type is backwards and field "Start in the Past" is blank, OPU5-Scheduling Type is backwards and field "Start in the Past" is blank.
do any guru know why system not use forward scheduling when found that start date in the past? or have any config of other module which may lead to this issue?
thank in advance.

In OPU5,
Check the setting for correct MRP group which is assigned in material master or in the SPRO node
Production >Material Requirements Planning>MRP Groups-->Define MRP Group for Each Material Type.
check and come back

Basic start date and finish date changing in the past

Hello Gurus,
I set the scheduling parameters as " Do not adjust basic dates, dep rqmts to order start " and also assigned the priority to populate the basic finish date. System does calculate the finish date based on the priority and start date as current date but it does allow me to change both dates in past or future which should not happen.
Please do note that I activated the defaulted date as current date as well. Even I removed this mark and did not work.
Please let me know if there is any way to restrcit the changing it alteast in the past.
Mahee

This can be prevented using one the following ways depending upon your needs
---> Set the "start in past" field to appropriate value using transaction OPU7 for order type /Plant combination
---> Make the "Basic start date and Basic end date" fields as "Display only" through the Field selection config for the order type.
---> Use the user exit on "SAVE" of the order to check for the same
Regards
Narasimhan

Planned order start date is in the past

Hi Experts,
I am running MRP with lead time scheduling (2) at my production plant. The planned orders are generated against the requirements but the start date of the planned order is in the past. I have not mentioned anywhere in the configuration allowing the scheduling in past. I cross checked plant parameters, MRP group, settings for determining basic dates & scheduling parameters and every where start in the past check is blank.
Since the planned order basic dates are calculated based on in house production time in material master, I maintained the lot dependant times in work scheduling view (Set up & processing time with base qty). But system is not considering this in MRP run. But its considering the lot independant inhouse prod time maintained in work scheduling view in MRP.
Is there any other check to be maintained or system limitations? Your expert view on this please.
Appreciate an early reply.
Thanks & Regards
Prathib

Check OPU5
S Anil

Start date in the past

In the process orders scheduling parameters there is a field called allow start in past when backward scheduled. Under what scenario would one allow an order to start in the past ?

In SAP "allow start in past when backward scheduled" comes when it is backward sheduled. Now you have two options.
1) If order is already physically processed you can allow it so that this order will not consume capacity in future which is not required.
2) if order is not physically processed you can change it to forward scheduling.
If the end user is doing all the transaction On-line this kind of problem will not generate.
Regards
AM

Restriction of Validity start date in Scheduling agreement

Hi,
I am not able to convert the message 06 170( Start of validity period is in the past) in error message , when i am going to define attributes of system messages in purchasing and converting this message into error , system still does not give error message when i am selecting back validity start date in the header of Scheduling agreement (me32l)
What can be the possible reason.
Regards
Sachin

Hi,
I believe the message 06-170 is hard-coded in Include "MM06EFRP_EKKO-KDATE" in the Program SAPMM06E
Laufzeitbeginn in der Vergangenheit -
    IF ekko-kdatb < sy-datlo.
      MESSAGE w170 INTO gl_dummy.
      mmpur_message 'W' '06' '170' '' '' '' ''.
Please consul your ABAP Team on this to change it to Error.
But SAP does not recommend changing standard Programs, so please discuss this and see that its really required and will not have any effects to your business process, because there may be instances wherein you might require to create scheduling agreements with a past validity date sometime in future based on business requirement.
Regards
Chandra Shekhar

Call object was called with start date in the previous month

We have a single cycle maintenance plan for 30 days.
Shift Factor Late Compl.   : 100%
Tolerance                    : 10%
Shift Factor Early Compl. : 100%
Tolerance                    :    10%
Cycle modification factor:    1
Factory calendar            : NIL
Call horizon                    : 100%
Scheduling period          : 90 DAY
Scheduling indicator       : Time
Call no . 11 was a plan date of 14.08.2009 has completion date 14.08.2009. Schedule type/status has "scheduled complete".
Call no. 12 was called on 13.09.2009 which is in the past.
Can someone explain why the system called the order with a starting date in the previuos month , that is , 13.09.2009.
And how to rectify it to make it current date for the next call object?
Thanks,
Manohar

I checked the algorithm for call no. 12
Start of Cycle                07.08.2008
Last planned date         14.08.2009
Compl.Predecess           14.08.2009        Absolute shift                +   0 Da
Planned cycle/offset      +    30 Da          Relative shift            0 % =   0 Da
Shift                                 +     0 Da           erance value           0 % =   0 Da
Planned Dates Due   13.09.2009    Completed on
Last call on              15.10.2009    Called by               IP1020091015
Workorder generated has start date 13.09.2009.
Should we restart this plan , as the start dates in call object are at least 1 month old ?
Thanks,
Manohar

QM_Control on Required start date in quality notifications

Dear QM experts,
Requirement is,
For Q2 notification type the entries in required start date filed (QMEL-STRMN) to be restricted in such a way so that user can not do entry for last month.
Foe example,
1.     Today is June 12, 2009. If a user is creating Q2 notification today he/she may change the required start date in the past but not before 1st June 2009.
2.     User should be in a position to enter back date in required filed only for the current month
3.     The concept is just similar to period closing activities.
I tried through SPRO-Quality Management-Quality notifications-Notification creation u2013Notification types-Define screen templates-Field Selection: General Screens. Here there is facility to make the field grey, hide or required. One of the limitations is that this is client level setting.
Can the requirement be mapped for particular plant and for perticular notification type?
Thanks is advance
Best Regards,
Anand Rao

Dear Anand
Here are some of the thoughts. Please check and then come back with your feedback
1) Make Priority button mandatory for Q2 notification .VIQMEL-PRIOK. You can do only for Notification type Q2 by using the influencing fields
2) Make required date in grey so that no changes can be done . do this notification Q2
2) Maintain QM priorities SPRO >Quality Notifications > Notification Processing>Response Control> Define Priorities
3) Maintain Priorities in the QM priority in the same config
When you set the priority in the notification required from and end date is updated in the system automatically
4) Use this exit QQMA0018 Deadline setting based on entered priority to make sure that always the date doesnt fall on past date
Hope this gives some idea
Regards
gajesh

Production order Basic start date calculation

Hello PP Sapperu2019s,
I have an production order for total qty - 865,00.This production order created on 11.08.2011 and I could able to see the Basic start date as 26.06.2011.Please let me know how this basic start date gets calculated. I mean what are all the parameters included for calculating this basic start date.
My Observation:
I have checked in OPU3 for the respective plant and order type the scheduling type mentioned as Backward.
SMK u2013 903 (ie, opening period for planned order u2013 3 days)
In Routing we have two operations.
Requesting from forum people to give me the detailed calculation part on how this basic start date gets calculated / arrived.
Please let me know if you need any more inputs.
Cheers,
Kumar.S

Hi Kumar,
As per my understanding this is all decided/maintained through scheduling parameters which are defined in Customizing per order type, plant and production scheduler (from the material master) (Customizing for Shop Floor Control, by choosing Operations > Scheduling > Define Scheduling Parameters). In what follows the parameters are described that affect the scheduling of a production order. Further control parameters are described in the course of this section.
According to your query I suggests ,In Customizing you can specify that an order is rescheduled as soon as it is a certain number of days late (Start in the past indicator). The system then automatically carries out today scheduling when the basic start date of the order is more than the given number of days in the past. This scheduling is a type of forward scheduling starting from todayu2019s date and where the necessary reduction measures are applied .
Else you can also specify that a production order is to be rescheduled automatically whenever it is saved (indicator Automatic scheduling). If changes relevant to scheduling are made in the order and this indicator is not set then the order is given the status NTER (dates not current).
Hope this would be useful for you at some extent.
Please revert if required .
Regards
Chandra

Order basic start date.

Hi,
We are updating the basic start da of order using FM BAPI_ALM_ORDER_MAINTAIN.
We are deleting the basic finish date and then updating the basic start date.
I am observing the following:
1) For some orders, the basic finish date is recalculated, whille for some it is not, and the basic finish date get deleted and the field becomes blank.
2) For some orders, the basic start date is updated when the start date is in the past and in some cases, it is not?
Please explain the reason.

Hi,
The following settings are there in OPU7:
Do not adjust basic dates,dep reqmts to operation dates
Scheduling type - forward scheduling
Automatic scheduling is checked
start in past = 0
Can you please explain what to check when saving in the FM?
Regards

Basic finish date earlier than basic start date while backward scheduling

I am encountering an issue where in when I am selecting backward scheduling for a process order and I am entering the Basic finish date, afte which system is giving me a Basic startdate which is after the basic finish date.
For eg:- When i give the basic finish date as 08.12.2011, system is giving me basic start date as 09.12.2011
I have checked the recipe of the material. In the recipe one major flaw that i found out was that all the activity timings were maintained as 0. But when i created a similar scenario in the testing client, i am not getting the issue.
Please help.

Hi,
Check what is maintawined in number of days the start day is allowed to be in the past in scheduling parameters of the order type, in OPU3. If there is an opening float defined in schedule margin key of the order, and concerning this float backward scheduling finds a start date which falls into past, lead time scheduling will automatically switch to forward scheduling starting from today. 9.12.2011 could have been deducted this way. Also check the factory calendar if days upto 9.12.2011 are defined as working days.
Regards.

Start date in past

Similar Messages

Maybe you are looking for