Changing Operattion Earliest Start/Finish Dates?

Hi EAM Gurus,
I want to change the operation Earliest start/finish dates & times also. Is it possible?
Also I am thinking if I create a custom report (similar to IW37n) which allows me to change operation earliest start/finish dates.
Is there a USER EXIT/BADI which will allow me to change the dates?
I can change the operation date & time in capacity planning table (tabular form - CM34) by using manual dispatch button. I want to incorporate same kind of functionality in a custom report.
I am waiting for your expert advice/suggestions.
Thanks in Advance
Adi

Hi,
In the end, yes, once actuals are recorded, all these values are the same - but before that they can all be different!
Before an actual start is recorded, the column shows "NA" (wich obviously is different from Start :-)). To the scjheduling engine, thsi means the start can be freely calculated (from predecessors or resource leveling, f.i.) whereas when a date
appears in Actual Start, Project will take that value as carved in granite - it is supposed to show past reality, and reality is more powerful than values calculated by the scheduling engine!
So these two values are not Always identical!
As for Scheduled start, that is indeed meaningless for automaticlly calculated tassk. But for manually scheduled tasks it does play a role. For a manually schduled task, you can set any start value you want (even a litteral such as "when we have
the time"). Still, there is an option to make manually scheduled tasks obey links - the result of that calculation is then put into scheduled start - and so there can be a difference between these two columns as well.
So, no, these 4 values do not have the same function. They are ony identical as soon as actuals are recorded but what do you expect? There is only one past reality, Project does not work with a parallel universum :-)
Hope this helps,

Similar Messages

Basic Start/Finish Date and Requirment Date in Maintenance Order

Sir,
We want to know the link between Order Start/finish date and requirement date in Maintenance Order.
As we are facing problem during change in dates.
When we change either start date or finish date in the order, the system automatically change the requirment date as of ondate of all the materials which has been earlier issued and also consider the today date.
Like in Maintenance Order
Basic Start Date - 01.04.2009
Basic End Date - 31.05.2009
We have issued materials on the order at different date by putting offset value for the requirement date.
Now if we increase the Basic End Date of order to n30.062.009 or whatelse, the system automatically changes the requirement dates of all the materials issue based on current date. Suppose we changed the Basic End date on 10.11.2009, the system changes all the requirement dates by calulating offset value from 10.11.2009. However these materials has been issued earlier.
I want to know if there is any remedy to stop to change the requirement dates automatically.
With Regards
Mudit Gupta

HI
In general the requirement date will get changed only when the IMG settings in OPU7 permits the requirments dates should be adjusted towards the order basic start and end dates
kinldy check and adjust as per the requirement
regards
thyagarajan

Production order scheduled start/finish dates

Hello experts!
I have a problem with prod. order scheduling. I set the date '07.05.2007' as order start/finish date. If I run Functions -> Schedule -> Order (or save the order) SAP set these dates to '02.01.2008', and scheduling also to '02.01.2008'. The scheduling type is Forwards in time. Scheduling margin: everything is 0.
I have checked the work center capacity:
from 20.04.2007 to 31.12.2007
Lenght of cycle: 1 Start: 06:00:00 End: 23:00:00 Break: 00:00:00 Cap. util.: 100
from 01.01.2008 to 31.12.9999
Standard avail. capacity
(01.01.2008 is non-working day)
Routing exists for this material (valid from 02.03.2007).
Based on what does SAP calculates these dates?
(SAP 46B)

Hello guys!
I have found the reason and also the solution. It's a bug in SAP (46B). When it happens?
1) Open work center
2) Create interval with minimum 2 shifts and save
3) Delete first shift of the interval
4) Check table kapa -> field SCHNR (shift sequence number) for the 1st shift in this interval will contain number 2.
If SAP calculates the scheduled date for order it excludes this interval from calculation. We had an interval 20.04.2007 to 31.12.2007 with deleted first shift, so the next workday for SAP was 02.01.2008.
I have created a function, which can solve this problem:
FUNCTION z_pp_fix_capacity_data.
*"*"Local interface:
*" IMPORTING
*" VALUE(I_WERKS) TYPE WERKS_D
*" VALUE(I_ARBPL) TYPE ARBPL
*" EXPORTING
*" VALUE(E_CHANG) TYPE INT4
*" EXCEPTIONS
*" FOREIGN_LOCK
*" SYSTEM_FAILURE
*" NOT_VALID_WORK_CENTER
*" DATABASE_UPDATE_FAILED
DATA: l_kapid LIKE crhd-kapid,
 l_schnr LIKE kapa-schnr,
 l_error TYPE c.
DATA: ikap LIKE kapa OCCURS 200 WITH HEADER LINE.
CLEAR: e_chang.
COMMIT WORK.
*- Get the Capacity ID of the work center
SELECT SINGLE kapid
 INTO l_kapid
 FROM crhd
 WHERE werks = i_werks
 AND arbpl = i_arbpl.
IF sy-subrc <> 0.
 RAISE not_valid_work_center.
ENDIF.
*- Lock the work center
CALL FUNCTION 'ENQUEUE_ECARPL'
 EXPORTING
 arbpl = i_arbpl
 werks = i_werks
 EXCEPTIONS
 foreign_lock = 1
 system_failure = 2
 OTHERS = 3.
IF sy-subrc <> 0.
 CASE sy-subrc.
 WHEN 1.
 RAISE foreign_lock.
 WHEN 2.
 RAISE system_failure.
 ENDCASE.
ENDIF.
*- Select the whole capacity into internal table
SELECT *
 FROM kapa
 INTO TABLE ikap
 WHERE kapid = l_kapid.
*- Sort
SORT ikap BY versn datub tagnr schnr.
*- Set the correct sequence number
LOOP AT ikap.
 ON CHANGE OF ikap-versn
 OR ikap-datub
 OR ikap-tagnr.
 l_schnr = 1.
 ENDON.
 IF ikap-schnr NE l_schnr.
 ikap-schnr = l_schnr.
 e_chang = e_chang + 1.
 MODIFY ikap.
 ENDIF.
 l_schnr = l_schnr + 1.
ENDLOOP.
IF e_chang NE 0. " If change found, recreate data
*- Clear error indicator
 CLEAR l_error.
*- Delete old data
 DELETE FROM kapa WHERE kapid = l_kapid.
*- Insert data
 IF sy-subrc EQ 0. " Delete OK, insert
 INSERT kapa FROM TABLE ikap.
 IF sy-subrc EQ 0. " Insert OK, commit
 COMMIT WORK AND WAIT.
 clear: l_error.
 ELSE. " Insert failed, rollback
 ROLLBACK WORK.
 l_error = 'X'.
 ENDIF.
 ELSE. " Delete failed, rollback
 ROLLBACK WORK.
 l_error = 'X'.
 ENDIF.
ENDIF.
*- Unlock the work center
CALL FUNCTION 'DEQUEUE_ECARPL'
 EXPORTING
 arbpl = i_arbpl
 werks = i_werks.
IF l_error NE space.
*- Raise exception
 RAISE database_update_failed.
ENDIF.
ENDFUNCTION.
I hope this helps someone! Anyway! Thank you for your answers!

Revised Project Start & Finish Dates

Dear All,
Where i can see Project orignal start & finish dates and Revised start & finish dates
Is their any report or transaction available.
Pls confirm me.
Thanks in Advance.
Regards,
Sandeep N.Theurkar

Hi Sandeep,
The project system does not keep the original dates somehwere automatically. If you would like to have such 'baseline', a option is using version as mentioned above. An alternative is just transfer the basic dates to the forecast dates as base line, after the planning is finish. In this way, you get two sets dates of the same object.
Kind regards,
Zhenbo

Schedule start & finish dates - Project Management

All
Will there be any implications on performance /status reporting etc if we personolise Schedule start & finish dates.
The reason to personlise is to have Transaction Start & Finish date instead of Schedulate start & finish dates.
Needs your inputs....
Thanks in advance.
Regards
Ajith

Marc,
When Project was first released there were only two basic start field, Start and Actual Start (in addition of course to the Baseline Start field and a few others). With the release of Project 2010, a manual scheduling mode was introduced. That's when things
got a little more confusing. Instead of leaving the Start date as is, the Start field was converted to a text field and the old Start field was renamed as Scheduled Start. When in auto-schedule mode, both Start and Scheduled Start are exactly the same.
Now to answer your questions. To keep it simple, let's assume you are using auto-scheduling.
1. In order to keep the schedule dynamics intact, it is necessary to update the Start field to agree with what really happened, namely with the Actual Start date. If you do not enter anything into the Actual Start field, Project automatically assumes the
task started as scheduled, on the Start date.
2, Yes, Project does its scheduling based on the current plan which is represented by start, finish and other data. Once the project starts, that current plan must be updated so the actual date values come into play. As noted in the lead in paragraph, Scheduled
Start and Start are the same for auto-scheduled tasks.
3. Earned value is based on the actual values and the saved baseline data. The "point in time" you refer to is the timescaled data as of the status date.
Hopefully, this clear up at least some of your confusion.
John

Why do Start/Finish dates automatically change to match Actual Start/Finish dates?

Please excuse my ignorance, but what is the
rationale for MS Project automatically changing the "Start" and "Finish" dates to match the "Actual Start" and "Actual Finish" dates when they are inputted? Can this "feature" be disabled?
Thanks in advance for any assistance.

Hi,
In the end, yes, once actuals are recorded, all these values are the same - but before that they can all be different!
Before an actual start is recorded, the column shows "NA" (wich obviously is different from Start :-)). To the scjheduling engine, thsi means the start can be freely calculated (from predecessors or resource leveling, f.i.) whereas when a date
appears in Actual Start, Project will take that value as carved in granite - it is supposed to show past reality, and reality is more powerful than values calculated by the scheduling engine!
So these two values are not Always identical!
As for Scheduled start, that is indeed meaningless for automaticlly calculated tassk. But for manually scheduled tasks it does play a role. For a manually schduled task, you can set any start value you want (even a litteral such as "when we have
the time"). Still, there is an option to make manually scheduled tasks obey links - the result of that calculation is then put into scheduled start - and so there can be a difference between these two columns as well.
So, no, these 4 values do not have the same function. They are ony identical as soon as actuals are recorded but what do you expect? There is only one past reality, Project does not work with a parallel universum :-)
Hope this helps,

How can I change the default start-up date for a new functional location?

Is there a way to change the default date when creating a functional location? Whenever we create a new functional location, there is a date populated in the start-up date field. This date is our go-live date from last year and I cannot find the location in the IMG (if there is one) to stop the date from automatically populating with the date from the superior functional location. I tried setting the field from input to required but the date still populates automatically. Does anyone have any suggestions on how to leave the start-up date field blank when creating a new functional location?

That field is generally picked up from the immediate superior FL in the hierarchy through the inheritance functionality.You will have to overwrite this date.I dont think you can clear this field through Configuration functionality.
If you are in Ecc 6.0, you could get the help of developer to use implicit enhancement to initialize the field contents.
Regards
Narasimhan

Schedule run issue: Late dates earlier than start/finish dates

Hi,
I am running into an issue with one of my contractors. When the contractor sends the xer file, all the critical late start dates are a day earlier than the start date i.e. if the start date is Mar 03, 2011 then the late start date is Mar 02, 2011. I am able to fix it at my end when I run the schedule but the contractor is not. Is there some feature in the global setting that the contractor has to fix in his end to resolve this issue? Any help or advice would be great.
Thanks.

Marc,
When Project was first released there were only two basic start field, Start and Actual Start (in addition of course to the Baseline Start field and a few others). With the release of Project 2010, a manual scheduling mode was introduced. That's when things
got a little more confusing. Instead of leaving the Start date as is, the Start field was converted to a text field and the old Start field was renamed as Scheduled Start. When in auto-schedule mode, both Start and Scheduled Start are exactly the same.
Now to answer your questions. To keep it simple, let's assume you are using auto-scheduling.
1. In order to keep the schedule dynamics intact, it is necessary to update the Start field to agree with what really happened, namely with the Actual Start date. If you do not enter anything into the Actual Start field, Project automatically assumes the
task started as scheduled, on the Start date.
2, Yes, Project does its scheduling based on the current plan which is represented by start, finish and other data. Once the project starts, that current plan must be updated so the actual date values come into play. As noted in the lead in paragraph, Scheduled
Start and Start are the same for auto-scheduled tasks.
3. Earned value is based on the actual values and the saved baseline data. The "point in time" you refer to is the timescaled data as of the status date.
Hopefully, this clear up at least some of your confusion.
John

Basic start date & Basic finish date based on Priority

Dear Experts,
When I am creating Notification & selecting Priority, System gives pop-up “do you want to specify new dates?” If I select yes system automatically change required start & required end based on Priority.
Now my question is do we have same functionality for Maintenance order as priority field is available there (If we are directly creating a MO)?
Even if we are creating WO from notification, required start & end dates copies to Basic start & Basic finish but if we change priority then no change in basic start & finish dates. Why?

Greetings Parag,
You may select the Priority in the initial screen of IW31 and the dates will shift accordingly, if you maintained the Relative Start &/or Relative End in
SPRO > Plant Maintenance > Maintenance Processing > Maintenance & Service Orders > General Data > Define Priorities > Define Priorities for Each Priority Type
If you want to change date based on Priority on the Order header screen, it's not possible in the standard to my knowledge, but you may easily develop an enhancement utilizing the user exit
IWO10012 Maintenance order: Priority handling on central header
or
IWO10009 PM Order: Customer Check for 'Save' Event

PM Orders Basic & schedule finish date

Hi Experts,
I want the basic start & finished date similar to schedule start & finishe date in any condition.For e.g. if i change the basic start & finished date the schedule start & finished date should become similar to basic start & finish date and vise versa.May I know how to do the customization setting.
AR

AR,
This can be done through transaction OPU7.
For the plant and order type combination, set the Adjust dates field to either"Adjust dates, Adjust dependent requirements to operation start" or "Adjust dates, Adjust dependent requirements to Order start".
Regards
Narasimhan

The system could not calculate the fiscal year start or finish date message

While running the transaction FMO1 and FMOA in funds management we have confronted with the following problem.
Message no. FI 500
The system could not calculate the fiscal year start or finish date.
WE are using year dependent fiscal year and are implementing Funds Management for the first time.
SAP Version 4.0 B
Priority Urgent
For the same problem in Version 4.5 and 4.6 there is a note number 213713 available on service.sap.com.

No, there is no bug.
Those activities that have asterisks (Stars) next to their start or finish dates (despite having no constraints) have "External Early Start" or "External Late Finish" dates, respectively, assigned to them. These dates get imported with XER and represent links to activities of those projects that are not in your database but in the external database where the XER originated from.
To remove, filter out all such activities (with stars) and delete their "External" dates. However, be aware that Start or Finish dates of such activities might change if you delete theire External dates. If getting rid of asterisks does alter your schedule, ask the person who sent you the XER to confirm start/finish dates of all such (starred) activiites.
Cheers

Changes in Retroactive account time date not possible error

Hi
This employee is joined on date 20.01.1969 after that this employee prejoin on 09/04/2009 and we are trying to change the join date by using transaction code PA41. i am getting the below error message.
'Change in earliest retroactive accounting date time not possible!.'.
I checked the table (T569R) and i changed the value in Time evaluation fields like 01.01.1900 through table level after that I am not getting error message I am able to create the employee but I want to do the configuration level for that
Please provide me the step by step procedures do to the configuration.
before changes in table T569R
01 01 01.01.1990 Incentive wages
01 02 01.01.1990 Time evaluation
01 03 01.01.1990 Time statement
01 04 01.01.1990 Pair formation
after changes in table T569R
01 01 01.01.1990 Incentive wages
01 02 01.01.1900 Time evaluation
01 03 01.01.1990 Time statement
01 04 01.01.1990 Pair formation
Please help me to resolve the above issue.

This error comes due to 2 dates set in the system
1> Employee level restriction - PU03
2> Payroll Level restriction - PA03
Since you are not going too retro (4/9/2009) so most likely it would be employee level.
Check his IT0003 and edit the dates using tcode PU03 or PA30 -> Utilities -> Change payroll status.
Also when you are trying to change the infotype, make sure you give the correct date as start date (04/09/2009)
Regards,
SC.

Start/Finish vs Schedule Start/Finish vs Actual Start/Finish

Hi,
I'm new to MSP 2013 and I'm confused on the way MSP handles Start/Finish dates. While I understand the rational of it adjusting the schedule so you see how actual dates impact the schedule, I find it confusing that there are multiple columns with different
labels performing the same function?
"Scheduled Start" would lead you to believe this is your initial planned start date and remains static while "Actual Start" would be, well, the Actual Start date. So one value by definition would be different than the other, yet when any
of these dates, "Scheduled Start", "Actual Start", or "Start" are changed, they all change to the same value.
My questions are:
Why do the "Scheduled Start", "Actual
Start", and "Start" dates all change to the "Actual Date" when entered?
Is there a scheduling technique or purpose for this to work this way?
Also, since the "Scheduled Start" date changes, how does MSP 2013 handle Earned Value?
Since Earned Value calculations rely on your Planned Value which would be based on the Budgeted Cost of Work Scheduled and the Earned Value which is
the Budgeted Cost of Work Performed vs. the Actual Cost of the Work Performed at "a point in time," how could it provide a reliable figure if the scheduled date is moving? Is it using the "Baseline Start/Finish"?
I hope you can answer this for me or direct me to a resource that can. Thank you for your consideration.
Marc

Marc,
When Project was first released there were only two basic start field, Start and Actual Start (in addition of course to the Baseline Start field and a few others). With the release of Project 2010, a manual scheduling mode was introduced. That's when things
got a little more confusing. Instead of leaving the Start date as is, the Start field was converted to a text field and the old Start field was renamed as Scheduled Start. When in auto-schedule mode, both Start and Scheduled Start are exactly the same.
Now to answer your questions. To keep it simple, let's assume you are using auto-scheduling.
1. In order to keep the schedule dynamics intact, it is necessary to update the Start field to agree with what really happened, namely with the Actual Start date. If you do not enter anything into the Actual Start field, Project automatically assumes the
task started as scheduled, on the Start date.
2, Yes, Project does its scheduling based on the current plan which is represented by start, finish and other data. Once the project starts, that current plan must be updated so the actual date values come into play. As noted in the lead in paragraph, Scheduled
Start and Start are the same for auto-scheduled tasks.
3. Earned value is based on the actual values and the saved baseline data. The "point in time" you refer to is the timescaled data as of the status date.
Hopefully, this clear up at least some of your confusion.
John

Resource Durations (Start /finish) are not align with activity durations

Gurus,
My Resource Durations (Start /finish) are not align with activity durations and hence the Budgeted % are going crazy. Any idea?

hi,
the default start/finish dates for resource assignments are the activity start/finish dates. if for any reason you changed that, you can check and reset both Original Lag and Remaining Lag to 0 for all/ some of your resource assignments by adding the columns in the Resource Assignments window and performing either a fill down or a Global Change operation. let me know if you need help with any of these.
best of luck.

Need to count the number of times the Basic Finish data chages

HI Expertes,
I have a requirement I need to count number of times the Basic finish date chaged for PM work order. I went throug our forums I got some info like using a standard function module
CHANGEDOCUMENT_READ_HDRS_ONLY
CHANGEDOCUMENT_READ_HEADERS
CHANGEDOCUMENT_READ_POSITIONS
But all the above function module will not be suitable for my requirement since CHANGEDOCUMENT_READ_HDRS_ONLY it gives whole changes but my requirement is just need number of changes occurred in Basic Finish date but CHANGEDOCUMENT_READ_POSITIONS can give the filed number which has been changed but still I need change id.
So kindly suggest me wether there is any other Standard FM to get number of changes occurred in Basic Finish date?
Thanks,
Rajesh

Hi Debbie,
     To count the number of groups please try the folling steps:
1) Create a formula @reset and place this formula in the page header
    whileprintingrecords;
    numbervar i:=0;
2) Create another formula @evalgroup place this in the group header where you want to count the values.
    whileprintingrecords;
    numbervar i:= i+1;
3) Create another formula @display and place this in report footer.
    whileprintingrecords;
    numbervar i;
In order to display the count of details which are printing in the detail section place the eval formula in the detail section and the @display formula in the group footer.
Hope this helps!!!
Regards,
Vinay

Changing Operattion Earliest Start/Finish Dates?

Similar Messages

Maybe you are looking for