Schedule finish date

Dear Gurus,
In my current system, I am using activity elements with in the activity to plan my resources.
The activity elements take the start and finsih date (earliest) from the parent activity.
Now, during partial confirmation of the activity, I enter the forecast duration to get the next realistic finish date of the actvity. Now when i reschedule my project, the activity element's finish dates are exceeding the parent activity's finish date by one day. The noteable difference i can see before and after the confirmation and schedule update is that, the execution finish time before confirmation was 24:00:00 and after confirmation, its 00:00:00 of the next day of the activity finish date.
For example
Activity finish date is 03.08.2009 with execution time 24:00:00
Activity element finish date is 04.08.2009 with execution time 00:00:00.
Regards,
VDS

Hi Rupesh,
I don't think there is any difference... 03.08.2009 - 24:00:00 is Midnight of 03 and 04 whereas 04.08.2009, 00:00:00 is same as that of the earlier one (i.e... midnight of 03 & 04) ... Where is the difference of one day ... if it is 04.08.2009 - 24:00 then what you have said is correct..
Regards,
Bala

Similar Messages

Trying to update Project scheduled finish date - newbie help needed!

Guys, I am super new to Oracle Projects, I have never used it before. I've just learned a few things in the UI and read through the docs documenting the stored procs. My question is simple (hopefully) In the UI I choose a responsibility, then under "Projects : Delivery" I choose "Search Projects", I enter the Project ID in the field and click Go, I am able to see all the project details and the Tasks. No problem there! What I would like to do through the Update_Project API is to change the "Scheduled Finish Date" of the Project.
I have the following information that I have managed to scrape up:
Project_id, Responsibility_id, User_id, Resp_Appl_Id
I retrieved the project id using:
         Select project_id,name from pa_projects_all
          where name = 'My Project';
So first I call set_global_info with the appropriate parameters, then this:
    -- SET GLOBAL VALUES
     pa_interface_utils_pub.set_global_info(
     p_api_version_number => 1.0,
     p_responsibility_id => fnd_profile.value('57203'),
     p_user_id => fnd_profile.value('1013415'),
     p_msg_count => l_msg_count,
     p_msg_data => l_msg_data,
     p_return_status => l_return_status);
     l_project_in.pa_project_id := 4608;
     l_project_in.scheduled_finish_date := to_date('2008-02-27', 'YYYY-MM-DD');
--UPDATE_PROJECT
          pa_project_pub.UPDATE_project(
                    l_api_version_number,
                    p_commit => l_commit,
                    p_init_msg_list => l_init_msg_list,
                    p_msg_count => l_msg_count,
                    p_msg_data => l_msg_data,
                    p_return_status => l_return_status,
                    p_workflow_started => l_workflow_started,
                    p_pm_product_code => null,
                    p_project_in => l_project_in,
                    p_project_out => l_project_out,
                    p_key_members => l_key_members,
                    p_class_categories => l_class_categories,
                    p_tasks_in => l_tasks_in,
                    p_tasks_out => l_tasks_out);
What I am getting is the message "error :Project ID is invalid" and the status is "E"
I'm not sure why it is invalid as it is the exact Project ID from the projects table. The only thing I can think of is that the p_pm_product_code is set to null but I am not sure where this value comes from and why it even matters. I checked the documents and it says it refers to some external system. Why does the external system code matter if I am changing data within Oracle Projects?

Hello,
Looks like you are not setting the Initialization values correctly. Oracle Project APIs are Org specific and require proper initialization before being called for them to work.
Few things i noticed from the code is :
1. The following is being used to set the User ID and Responsibility ID :
     p_responsibility_id => fnd_profile.value('57203'),
     p_user_id => fnd_profile.value('1013415'),
I think the call should be like this. This should be used only if you are going to call the API through a concurrent program from the submit request window (Oracle Apps environment). fnd_profile.value will get the responsibility id and the used id of the user running the program and assign it to the variables.
     p_responsibility_id => fnd_profile.value('RESP_ID'),
     p_user_id => fnd_profile.value('USER_ID'),
Or If you are directly passing the IDs hardcoded then, This can be used if you are running the script from a Non-Oracle Applications environment, for example from SQL*Plus.
     p_responsibility_id => 57203
     p_user_id => 1013415
2. I notice that you are not passing P_OPERATING_UNIT_ID parameter in the call to pa_interface_utils_pub.set_global_info. This is fine if you are not using MOAC and you have set MO: Operating Unit profile for the responsibility being passed. If you are using MOAC or are not sure, then it is always a good practice to explicitly pass the P_OPERATING_UNIT_ID parameter in the call to pa_interface_utils_pub.set_global_info.
Note : DO NOT use fnd_profile.value('ORG_ID') to set the P_OPERATING_UNIT_ID parameter. In a MOAC environment this may not work.
3. Always ensure you check the return status of the pa_interface_utils_pub.set_global_info for success before calling the Project APIs. This will save you a lot of frustration when testing.
4. You might find the following note useful
Project API Overview and Reference (Doc ID 1424156.1)
Regards,
Raghavan Gopalakrishnan

Process Order Basic Finish Date and Scheduled Finish Date

Folks,
I have a requirement from the business to be able to update the Process Order Basic Finish Date and Scheduled Finish Date independently from each other.
In other words, update the Basic Finish Date and the Scheduled Finish Date cannot change or update the Scheduled Finish Date and the Basic Finish Date cannot change.
I believe the reason for this is to be able to use the Basic Date to maintain the ATP accurately and keep the Scheduled Date to mark when the order was originally due from the shop floor to be able to measure if orders are being completed on time or late.
I have worked in tnx OPUZ and had some success with other issues with these dates but I can't seem to make them work independently from each other.
Or does anyone have any ideas how to measure proces order performance to the production schedule?
Thank you for your help,
Greg

Rajesha, thank you for your reply but it doesn't solve my problem.
Let me restate my scenario:
I start a process order and both the basic and scheduled finish dates are the same, June 1.
At some point, shop floor tells me they will be late and cannot deliver until June 15.
I need to update a date in the system so the ATP and the MRP planning runs have correct information for promising customers, I will update the Basic Finish date with June 15.
I also need to keep the original June 1 date in order to measure the shop floor performance to the production schedule to measure how early or late the order was delivered. How can I keep the original finish date or how can I measure if a process order is early or late??
Thank you for your help,
Greg

Scheduled finish date for process orders not updating in BW

We are having problems with the scheduled finish date (GLTRS) for process orders. When the process order is already released, changes done in R/3 on the scheduled finish date will not result to a delta hence data in BW is not updated. Table AFKO, where data is coming from, is always updated with the changes though. 2LIS_04_P_MATNR is used in extracting the data.
Has anyone experienced the same problem? We are looking for possible ways on how to have a delta whenever there are changes on the process order even after it is already released.
Any help would be greatly appreciated...

Hi Donna,
If I've understood your problem correctly, you can increase the load frequency as Sriee has pointed out.
If you want latest data frequently and if you are on BI 7.0 then you can look at Real Time Data Acquisition(RDA)
Regards,
Tom.

Production Orders - Scheduled Finished Date Basic Finish Date

In production orders, it is being noticed scheduled finished date lies further than basic finish date, what could be the
reason? what configuration should we need to do in order to make scheduled finish date matches (or) lies before basic finish date

Eshwer,
Basic dates of production orders can be made to match scheduled date.
Config is at OPU3. Under the "adjust scheduling" section, select either 1 or 'blank'.
Best Regards,
DB49

GLTRS - Scheduled Finish Date and 2LIS_04_P_MATNR extractor

Hi Experts,
Its a strange situation. I have one process order which is showing GLTRS as 3/3/2009 in AFKO but when I extract this order (after filling up setup table for full load) using 2LIS_04_P_MATNR the record doesnt bring the same date; instead in the field "Scheduled Finish Date" it displays date 2/25/2009.
when I see in Tx COR3 date 2/25/2009 is schedule start date.
Can anyone help me on this?
thanks,
Purvang

Same problem here except for field GLTRP. I realize this is old post, but were you able to find solution?

Process Order Schedule Finish date before Schedule Start date

On rare occasions, the process order Schedule Finish date is before the Schedule Start date. This causes an error on the APO system when the process order is CIF to APO. Does anyone have any ideas how this occur?
Thanks.
Best regards,
Sandy

Rajesha, thank you for your reply but it doesn't solve my problem.
Let me restate my scenario:
I start a process order and both the basic and scheduled finish dates are the same, June 1.
At some point, shop floor tells me they will be late and cannot deliver until June 15.
I need to update a date in the system so the ATP and the MRP planning runs have correct information for promising customers, I will update the Basic Finish date with June 15.
I also need to keep the original June 1 date in order to measure the shop floor performance to the production schedule to measure how early or late the order was delivered. How can I keep the original finish date or how can I measure if a process order is early or late??
Thank you for your help,
Greg

Early schedule start date, early schedule finish date

I want early schedule start date, early schedule finish date and project cost plan in my report. This is a PS requirement. In the standard cube (0PS_C02) I can find actual start date and actual finish date. Has anybody used early schedule start date and early schedule finish date in the reports? If yes then did you get it using standard cube/ODS or you went for enhancement?

HI,
He have to go for few tables in which u can find all the data.
Firstly u have to enhance the datasource .
First go to table AFKO here you insert AFUNR (Order Number) this table you will get AUFPL .
Then take AUFLP and go to AFVV table and insert AFUPL . you will get all the activites and all dates of each activity for example early start date ,early finish date, foirecost date etc.
Thanks and Regards
Dinesh

BAPI_PROCORD_CHANGE need to change GLTRS (scheduled finish date)

Hello -
I am writing a program where I need to change the scheduled finish date (field GLTRS) in a process order (transaction COR2). I would like to use the bapi BAPI_PROCORD_CHANGE but it does not contain that field in the input structure.
Does anyone have any ideas how I can change that field without writing a BDC? I am also curious to know why it was excluded from the bapi in the first place.
Thanks!

Hi Ferry,
Thank you for your quick reply!
That is very close to what I need, but it only updates GSTRS (scheduled start) and I need to update GLTRS (scheduled finish).
Can you think of any other suggestions? I have also looked at BAPI_ALM_ORDER_MAINTAIN, but it doesn't have GSTRS as an input either, and doesn't seem to work for the order type I need.
Thanks again,
Susanna

Basic start date and scheduled finished date...can we have Planned date?

Is there any "Plan Start Date" in SAP, the date where scheduler must put manually in the system to determine the "committed" date for the work to be executed - based on earliest and latest start date which automatically calculated by SAP?
Our plant must keep the Basic Finish Date unchanged since it is the Required Date of the Work to finish. We found that the Plan Date does not change and I was wondering if there is any way we can have the Planned date on the order header or have the basic finish date unchanged?
Appreciate your advices

Hi
As per your query screen variant is the better option to be choose so that here you can go with user id based restriction
Attaching the complete the scenario
Transaction and Screen variants with an Example
http://scn.sap.com/docs/DOC-39667
Try these document & try to configure if you have any further please revert back.
Thanks & Regards
Sandeep Kumar Praharaj

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

Scheduling start date and end dates

Hello Gurus,
I am trying to understand the schedule start date and schedule end date functionality in Plant Maintenance. I do understand the basic start and end dates. Currently I set up u201C3.Do not adjust basic dates, dep rqmts to order startu201D and set the scheduling type as u201CForwardsu201D . Please note we donu2019t do any capacity planning or leveling.
So my question is, why the scheduling start date is defaults to the basic start date for forwards and scheduling finish date defaults to basic finish date for backwards ? I tried adding couple of operations and save the work order. It did not change anything in schedule dates.
Do we really need to care about scheduling dates if we donu2019t use capacity planning ?
Please advise
Mahee

Hi,
As per priority, final dates would be calculated as we will define the duration based on the priprity. Either current date or basic date only applied to Scheduling start date.
You can change the scheduling start date so that based on priority, final date would be calculated.
Regards,
Maheswaran.

Compare finish date with target date

Would like to keep track of late Projects by comparing the finish date with the target date but are unable to do so. The idea is just to filter and count the summary tasks which have a later Finish date than the target date and present that as a the number
of late Projects. However it does not work, when trying to setup the filter Project tells that the target value can not be used for comparasion against the finish date.
Does anyone have a workaround or maybe a better solution to keep track of late Projects. Please note that we are talking about Projects that risk to be late compared to a date promised to a customer. When we plan we always add some extra time at the
end to have some extra when the Project is delayed at a certain department, however we want to keep track of how many late Projects we have and how late they are. Are not after seeing the status for each departments, only how we are doing in relation to what
we have promised our customers.
Kind regards //Anders

Anders,
Trevor and Dale have tried to steer you towards the normal tracking fields and methods already available in Project, but let me take a more direct approach to your exact question. First of all, you didn't tell us what field you are using as the "target date".
I'll assume it is the Date1 field manually entered for each summary line.
You could probably produce something close to the report you want with custom field formulas, filters and some manual counting but let me offer a more automated approach. The following macro will examine each summary task in your project and determine if
the finish date is before or on the target date (Date1), or if it is after the target date. If it is after the target date, that will count as one late project/order and add it to a running count of late orders. The difference in days will also be tracked
and added to a running total of delay. At the end, a message will appear in the exact format you describe.
Sub LateReport()
Dim t As Task
Dim LateCount As Integer
Dim LateDays As Integer
Dim TotDelay As Integer
For Each t In ActiveProject.Tasks
    If Not t Is Nothing Then
        If t.Summary = True Then
            If DateValue(t.Finish) > DateValue(t.Date1) Then
                LateCount = LateCount + 1
                LateDays = DateValue(t.Finish) - DateValue(t.Date1)
                TotDelay = TotDelay + LateDays
            End If
        End If
    End If
Next t
MsgBox "Number of late orders: " & LateCount & " (" & TotDelay & " days of total delay)"
End Sub
Note, in my view, and I'm sure in Trevor and Dale's also, the Finish field of the summary line does not indicate completion, it simply indicates the scheduled finish date of the last task in the subtasks under that summary. I think you should use the Actual
Finish date as the comparison value since it indicates when the project/order is complete. If you do decide, actual finish is a better choice, then substitute t.ActualFinish for t.Finish in the above macro.
My input.
John

Scheduled start and Finish date .

Hi Everyone,
I am facing a problem in dates in creating a process order in Production .
In the tcode COR1, when input the BASIC START DATE manually, the BASIC FINISH DATE ,scheduled start date and finished dates should get calculated automatically as per standard SAP.
The problem that I am facing is that , if I input the BASIC START DATE in future , the scheduled start date and finished dates are always coming as the system date.
whatever date I input in the BASIC START DATE the scheduled start date and finished dates are always coming as the system date.
But this is not happening in quality and development server .
Please help me if you have any solution
Thanks
Bijay

Dear ,
1.Scheduling parameter for new process order type and plant combination, to be defined at OPUZ . U can copy the settings at standard order type PI01.Here you should keep Backward Scheduling as Scheduling Type and Keep the adjustment Scheduling as Adjust to Basic Date , depenent requirement Date .
Now Order Basic finish date = Order Basic start date + float before prod + Lead Time of Operations (operation time from routing )+ float after prod.
These floats are predefined in SMK and assinged to material master .It comes through Planned Order after MRP run andcoped to Production Order .
.2.Check and Define Scheduling Margine key in MRP -Carry All over all palnt paremtres (OPPQ)
If you are MTS process , then Keep the Scheudling Type as Forward .Enter the Basic Start date and Scheduling Margine Days ( Opening periods , FBP, FAP) and then hit the Scheduling Indicator .It will calcuate all the dates based on the SMK and operation setup and propose you Basic Finish Date .
So adjust the Flaots in SMK tab in process order , enter Basic Finish Date , Choose Bacward Scheduling to arraive Basic Start or Go in reverse direction by choosing Forward scheduling .
Hope its clear
Regards
JH

Scheduled Maintenance basic start and finish date

Hi Expert,
I'm using WO type say PM04 for schedule maintenance. In its maintenance plan i'm using prioity "medium" that starts form 7 - 14 days.I also have already set the scheduling type in OPU7 - adjust scheduling into "Do not adjust basic dates, dep. reqmts to order start"
after run deadline monitoring WO PM04 that generated is resulted as per below:
basic start date: 13.08.2010
basic finish date: 13.08.2010
the basic dates does not reflect the priority "medium"
pls help how can i configure the basic dates setting that align to its priority.
Thanks
Rgds,

Hi ,
plz check if the below user exit is helpful or no
IWO10012 :Maintenance Order: Priority Handling on Central Header
i think priority does not influence the basic start or end dates for order generated from MP ..
regrds
pushpa

Schedule finish date

Similar Messages

Maybe you are looking for