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

Similar Messages

Error for Project finish date earlier than forecast finish date

Hi Experts
I have the dates in Project definition as follows:
Forecast start (PROJ-SPROG): 31.01.2011
Forecast finish (PROJ-EPROG): 31.03.2011
If i enter date 30.03.2011 as Finish date (PROJ-PLSEZ), below error message appears: "Finish date is earlier than start date. CJ563"
The date i have entered is later than PROJ-SPROG, still not accepting.
It accepts entry of date beyond the date in field PROJ-EPROG.
Can anybody share thoughts on this?
Warm regards
ramSiva

Can you kindly verify the other sets of dates being maintained in your activity (i.e. earliest & latest)? Are you using default configurations for PS i.e. confirmation dates are checked against basic dates and not forecast dates?
Regards,
Syed Ammar Zaheer

The time on the weather widget on my home screen does not match the phone time. Initially it did, but one day it started being 1 hour earlier than the phone time. I went into Settings/Date

The time on the weather widget on my home screen does not match the phone time. Initially it did, but one day it started being 1 hour earlier than the phone time. I went into Settings/Date & Time & now the time on the weather widget is correct, but the phone time is 1 hour earlier. Any suggestions??

Settings | Date and Time then select Automatic date & time, and Automatic time zone. In this way, the carrier time will populate the phone. If it's still going 1hour off, then I'd call VZW and inquire if they have a tower issue, specially if it happens in one particular place.

Deliveries dropping early than allocated schedule line dates

Hi Gurus,
I have a Scenario, where the deliveries are dropping early than the delivery date assigned in the schedule lines of sales order.
Example, Order received on 14th with one line item and schedule lines allocated the delivery date as 19th. But for some reasons the deliveries are dropping early on 16th.May I know what might be the reasons.
Thanks in advance,
Sree

Hi,
Check in the below link.
relation between VBEP-ETENR and LIKP-VBELN
Thanks,
Sree.

Production finish date is later than order finish date?

In my company, most of the plan orders in MD04 have an exception message "64 Production finish date is later than order finish date". The plan strategy of the materials are 40. The plan orders are created from Scheduling Agreements or Independent Requirements. We set 'Scheduling' as 2(lead time) in the MD01/MD02. The self-production time in material master data is 0. The schedule margin code is 000 which all the parameters are 0.
For a example, we create a requirement on 2007.04.24. After MRP run, plan order generate. It's basic date will be 2007.04.24, but the production date IS 2007.04.25. All the plan order like that, the production date are always later than the basic date for one day.
Could someone tell me why? and how to settle this problem?
Thank you in advance!

Hi,
check scheduling parameters for planned orders and scheduling parameters
for production orders.In that set the various indicators like
adjust basic dates to order start date
do not adjust basic dates to order start dates and try.
Tcode opu3 / opu5
Thanks,
s.nandhakumar

The Basic Finish date is a Day earlier than Planned date

Dear Experts,
I am getting a strange behaviour about Maintenance order Basic Finish Date when generated from Maintenance Plan. I have Customizing settings (TCode : OPU7) Adjust: "Adjust Basic dates, adjust dep reqmts to order start date" and scheduling type : Backwards in Time. For this setting Order Basic Finish Date is a day earlier than Planned date , but when Schduling type is Backwards instead of Backwards in Time, Basic Finish date is same as Planned date.
Example: The start of cycle of a monthly plan is 14-Nov-2010, 1st Planned date is 14-Dec-2010. When Scheduling type is " Backwards in time" , the order generated is having Basic Finish Date as 13-Dec-2010 .And when Scheduling type is "Backwards" , Basic finish date is 14-Dec-2010.
Thank you.
-Malay-

Hi there,
Please check the primilinairy buffer in your strategy package. This field have an effect on your order start date.
But I agree on Pete, you should use a forward planning.
Regards,
Johan
Edited by: Johan Zeeman on Dec 17, 2010 11:29 AM

Eyetv 2.4 wakes up earlier than scheduled

I am using Eyetv 2.4 software, and the awaking function is behaving unusually. Whenever the software is open, but the computer is asleep, it wakes up the computer about 30 minutes earlier than scheduled, though recording starts at the right time. And so if i have kept my computer to sleep after 15 minutes of inactivity, the computer goes off to sleep before recording starts and does not wake at the right time. Somehow it does not happen when it has to open the software to record. And so if i have multiple recordings scheduled at night, it wakes up properly for the first one, records and then computer goes to sleep. Then it wakes earlier for the second recording, and before recording can start it sleeps and misses the second recording.
The last version of eyetv I used was 2.3.1 and this issue was not there. Anyone else having the same issue with version 2.4?
20" Intel imac Mac OS X (10.4.9) 2 GB RAM

I didn't experience this waking issue (but didn't have any schedules this week) however I noticed a serious performance drop in the quality of video on my 1.25GHz G4 (loads of digital noise visible and was seeing regular SBOD under v2.4 for no apparent reason) not sure if you'd notice this performance hit on a Core Duo machine.
I've reported these issues to Elgato and rolled back to using version 2.3.1 which works just great for me. (I don't need tv compatibility anyhow).
regards
mrtotes

After replacing the hard drive on my G4 Powerbook and reinstalling Tiger I am no longer able to synch between itunes and itunes, it seems that the software on the ipod is of later date than itunes and I am unable to update itunes to the state prior..

After replacing the hard drive on my G4 Powerbook and reinstalling Tiger I am no longer able to synch between itunes and my ipod (Classic 160gb) it would seem that the software on the ipod is of later date than itunes and I am unable to update itunes to the state prior to the original harddrive's failure for Tiger OSX 10.4.11
Any ideas on the subject would be most helpful
Thanks in advance
Dingoh

The last security update released for Tiger users was the 2009-005 update. The latest version of QuickTime is 7.6.4. The last version of iTunes that can run on Tiger is 9.2.1, because 10.0 only supports Mac OS X Leopard and later.
So, are you on version 9.2.1?
Was it Tiger or Leopard you had on the drive before?
iTunes 9.2.1 download...
http://support.apple.com/kb/DL1056

Asset Acquisition with Asset Value Date earlier than GI post.date

Dear all,
I am curently using SAP ECC 6.0. We are not creating AuC assets but directly capitalizing assets from investment accounts.
If a material is issued with a date in March and i try to acquire it with asset value date from a previous period, for example in February, the system doesnt issue any message and lets me post the transaction. The accountants claim that this hadnt been possible in the earlier version of SAP 4.6 that we had been using and that the system had issued an error message - "Posting not possible (Value date earlier than capitalization date)"
The accounting logic is that you cant capitalize an asset with a date earlier than the date when it has been in use, i.e. in our case it`s the date the material has been issued from the warehouse.
Does someone know what logic does SAP follow in this case - and if i can set a validation control that will check and compare the two dates?
Any opinion would be appreciated
KR
Severina Koleva

We are on ECC 5.0 and we do get that message, but it is a warning.
AA348...
that said, you can setup a validation using GGB0 and asset accounting

Error In Backdated Reservation Creation Base date earlier than current dat

Dear Experts,
Error while creating Reservation for back date.
Base date earlier than Current date.
Can we create backdated reservation ? and post goods issue to the same ?
if it need configuration please explain the steps for allowing creation of backdated reservations.
Thanks in Advance

What is the error message nos.?

Posting not possible (Value date earlier than capitalization date)

Hello , we are getting the error shown below. I'am not sure where to go to fix this can any offer any advice.
Thank you
Posting not possible (Value date earlier than capitalization date)
Message no. AA 322
Diagnosis
Asset 000000040048 0000 was first capitalized on 20080831.
You cannot post to an asset that was not yet capitalized.
Procedure
You have the following options:
Change the asset value date of your posting.
Capitalize the asset by posting an acquisition.

Generally this message will come , if you have created a asset with a capitalization date say 31/08/2008 and you are settling a Internal order for last period say 07 on with a posting date earlier than capitalization date , say 15/08/2008.
The System will not allow you to post because the value date cannot be earlier than capitalization date.
Change the value date to later than capitalization date and post.

Is it possible to stop auction earlier than scheduled?

Dear SAP gurus,
We are using SRM server 550 and SP08 and we are using LAC. As a purchaser, is it possible to stop auction earlier than scheduled? I see one stop button there, but if i click stop button before the time is up, the system just give me message that the specified time has not been reached.
Best regards,
John.

Hi John,
this is the standard behaviour. An auction cannot be stopped before the scheduled
end date. Only option is to make the time period longer, but not shorter. That's the
current standard with one has to live with.
Cheers,
Claudia

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!

Can GR date earlier than GI date?

Hi,
Good morning! I have a inquiry want to ask all the MM expert.
I have a Good Issues date is on 22 May, but the Good Receive date is on 1st May.
Is this flow acceptable?
Good receive come before good issues sound not logical right ? But my user able to do that, when I try to reverse back the GR with wrong date, it come out this warning "document flow for delivey cannot be updated.."
Is that my logic was wrong? Please guide.
Thank you very much.
Warm regards,
PC

Hello Peai ,
The will accept the posting dates which may sound illogical .. eg GI date is earlier that GR date for a procured material .
The system has the following logic :-
If there is sufficient stock coverage at the time ( system time ) of posting the document , the system will allow the posting in any date withing the same period . However if the period changes ( i.e , posting date is in the previous period ) then the system throws an error.
Eg .
GR thro Po done on 22nd May
GI for the same done on 1st May
Logically speaking ... the GI date cannot be earlier than the GR date , but the system allows this as these are in the same period .
Regards
Anis

MY PRE-ORDER IS COMING MUCH EARLIER THAN ESTIMATED DATE.

My order for Plus 64GB was supposed to ship on 10/24. And today I receive the notice that it was shipped yesterday.
It's coming on time. It happened to everyone? or Am I just lucky?

I am sure Verizon picked a overestimated the ship date under the principle it is better to deliver earlier than promised than later than promised. Since many wanted it on the go live date, it would have been bad to miss 2 dates! Pure psychology.

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

Similar Messages

Maybe you are looking for