Operation Start Date

Hi Experts,
Which are the binding Dates within which a Order should be start :
Is it Basic Start and finish Date
Or
Schedule start and Finish Date.
Regards
Kavvya

Hi Kavya00,
Well the afore mentioned dates in a maintenance order signify the following:
Basic Start/Basic Finish date: These are the dates in which the maintenance planner expects the maintenance order to be executed and completed. They may not be the actual dates.
Scheduled Start/Scheduled Finish: These are the current system date on which the order was scheduled. It may be after the Basic Start/Finish Date.
None of these dates are binding for the order, the order may be started/confirmed on a later date than Basic Start/Finish date.
Regards,
Muhammad Usman Kahoot
Edited by: Usman Kahoot on Sep 17, 2011 7:35 AM

Similar Messages

Set the dependant requirement dates to be scheduled to order start date

Dear Experts,
The components have been assigned to the relative operations in the routing.
During the lead time scheduling, is it possible to set all the required date of the components to the order start date instead of the operation start date? How to configure?
Thanks,
Dawson

Hi,
In lead time scheduling, the precise production times, that is, the target start date and the target finish date, are specified for materials that are produced in-house. Capacity Requirements are also created during lead time scheduling and the date that the components must be provided is also determined.
You have maintained the following parameters for lead time scheduling in Customizing for MRP by choosing Define scheduling parameters for planned orders:
Parameters for determining the routing
Parameters that determine if and how scheduling is carried out
Parameters that indicate if and how basic dates are to be adjusted
Then
You have assigned a scheduling margin key in the material master record.
You can define the scheduling margin key in Customizing for MRP by choosing Define floats (scheduling margin key).
If You Assign BOM components to the first Operation then all the components are provided on the Basic start date of the production considering all the floats
OR
In a situation where different operations are assigned with different BOM components then we define Lead time off set(+ve on u2013ve value) to have material provision on the basic start date of production order
pavan

How does the GR processing time affect the scheduling of the process order & the latest start date in the operation.

Hi
Can anyone explain how does the GR processing time affect the scheduling of the process order & the latest start date in the operation overview.

Hi
GR processing time means number of workdays required after receiving the material in storage.
Check this link:GR Processing time
Regards,
Anupam Sharma

Need to update the actual start date & time of a operation in workorder

Hi Experts,
I need to update the Actual Start date and Actual start time of a Operation of a WorkOrder through a Function Module.
I was looking into the BAPI_ALM_ORDER_MAINTAIN FM, but i couldn't find any field relating to the actual start date and start time of a operation.
Kindly Suggest me which Function module i can use to complete my task.
Thanks in Advance
bye

Hi,
It is system's standard behavior and no other MRP type will help you in moving the start date outside the planning time fence. With MRP type P3 new requirements are covered at the end of the fixing period, the end date is set and planed order is scheduled backword. Hence the start date will lie within the planning time fence.
Rgds,

Error while starting data loading on InfoPackage

Hi everybody,
I'm new at SAP BW and I'm working in the "Step-By-Step: From Data Model to the BI Application in the web" document from SAP.
I'm having a problem at the (Chapter 9 in the item c - Starting Data Load Immediately).
If anyone can help me:
Thanks,
Thiago
Below are the copy of the error from my SAP GUI.
<><><><><><><><><><<><><><><><><><><><><><><><><><><><><><><><>
Runtime Errors         MESSAGE_TYPE_X
Date and Time          19.01.2009 14:41:22
Short text
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
Short text of error message:
Batch - Manager for BW Processes ***********
Long text of error message:
Technical information about the message:
Message class....... "RSBATCH"
Number.............. 000
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"MESSAGE_TYPE_X" " "
"SAPLRSBATCH" or "LRSBATCHU01"
"RSBATCH_START_PROCESS"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
System environment
SAP-Release 701
Application server... "sun"
Network address...... "174.16.5.194"
Operating system..... "Windows NT"
Release.............. "5.1"
Hardware type........ "2x Intel 801586"
Character length.... 8 Bits
Pointer length....... 32 Bits
Work process number.. 2
Shortdump setting.... "full"
Database server... "localhost"
Database type..... "ADABAS D"
Database name..... "NSP"
Database user ID.. "SAPNSP"
Terminal.......... "sun"
Char.set.... "English_United State"
SAP kernel....... 701
created (date)... "Jul 16 2008 23:09:09"
create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
Database version. "SQLDBC 7.6.4.014 CL 188347 "
Patch level. 7
Patch text.. " "
Database............. "MaxDB 7.6, MaxDB 7.7"
SAP database version. 701
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
NT 6.0"
Memory consumption
Roll.... 8112
EM...... 11498256
Heap.... 0
Page.... 65536
MM Used. 6229800
MM Free. 1085264
User and Transaction
Client.............. 001
User................ "THIAGO"
Language key........ "E"
Transaction......... "RSA1 "
Transactions ID..... "CD47E6DDD55EF199B4E6001B782D539C"
Program............. "SAPLRSBATCH"
Screen.............. "SAPLRSS1 2500"
Screen line......... 7
Information on where terminated
Termination occurred in the ABAP program "SAPLRSBATCH" - in
"RSBATCH_START_PROCESS".
The main program was "RSAWBN_START ".
In the source code you have the termination point in line 340
of the (Include) program "LRSBATCHU01".
Source Code Extract
Line
SourceCde
310
endif.
311
l_lnr_callstack = l_lnr_callstack - 1.
312
endloop.      " at l_t_callstack
313
endif.
314
315
*---- Eintrag für RSBATCHHEADER -
316
l_s_rsbatchheader-batch_id    = i_batch_id.
317
call function 'GET_JOB_RUNTIME_INFO'
318
importing
319
jobcount        = l_s_rsbatchheader-jobcount
320
jobname         = l_s_rsbatchheader-jobname
321
exceptions
322
no_runtime_info = 1
323
others          = 2.
324
call function 'TH_SERVER_LIST'
325
tables
326
list           = l_t_server
327
exceptions
328
no_server_list = 1
329
others         = 2.
330
data: l_myname type msname2.
331
call 'C_SAPGPARAM' id 'NAME' field 'rdisp/myname'
332
id 'VALUE' field l_myname.
333
read table l_t_server with key
334
name = l_myname.
335
if sy-subrc = 0.
336
l_s_rsbatchheader-host   = l_t_server-host.
337
l_s_rsbatchheader-server = l_myname.
338
refresh l_t_server.
339
else.
>>>>>
message x000.
341
endif.
342
data: l_wp_index type i.
343
call function 'TH_GET_OWN_WP_NO'
344
importing
345
subrc    = l_subrc
346
wp_index = l_wp_index
347
wp_pid   = l_s_rsbatchheader-wp_pid.
348
if l_subrc <> 0.
349
message x000.
350
endif.
351
l_s_rsbatchheader-wp_no           = l_wp_index.
352
l_s_rsbatchheader-ts_start        = l_tstamps.
353
l_s_rsbatchheader-uname           = sy-uname.
354
l_s_rsbatchheader-module_name     = l_module_name.
355
l_s_rsbatchheader-module_type     = l_module_type.
356
l_s_rsbatchheader-pc_variant      = i_pc_variant.
357
l_s_rsbatchheader-pc_instance     = i_pc_instance.
358
l_s_rsbatchheader-pc_logid        = i_pc_logid.
359
l_s_rsbatchheader-pc_callback     = i_pc_callback_at_end.

Hi,
i am also getting related this issue kindly see this below short dump description.
Short text
    The current application triggered a termination with a short dump.
What happened?
    The current application program detected a situation which really
    should not occur. Therefore, a termination with a short dump was
    triggered on purpose by the key word MESSAGE (type X).
What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
        Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
Error analysis
    Short text of error message:
    Variant RSPROCESS0000000000705 does not exist
    Long text of error message:
     Diagnosis
         You selected variant 00000000705 for program RSPROCESS.
         This variant does not exist.
     System Response
     Procedure
         Correct the entry.
    Technical information about the message:
    Message class....... "DB"
Number.............. 612
    Variable 1.......... "&0000000000705"
    Variable 2.......... "RSPROCESS"
    Variable 3.......... " "
    Variable 4.......... " "
How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
"MESSAGE_TYPE_X" " "
"SAPLRSPC_BACKEND" or "LRSPC_BACKENDU05"
"RSPC_PROCESS_FINISH"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
(Unconverted)".
   2. Corresponding system log
      Display the system log by calling transaction SM21.
      Restrict the time interval to 10 minutes before and five minutes
   after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
   3. If the problem occurs in a problem of your own or a modified SAP
   program: The source code of the program
      In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
   4. Details about the conditions under which the error occurred or which
   actions and input led to the error.
System environment
    SAP-Release 701
    Application server... "CMCBIPRD"
    Network address...... "192.168.50.12"
    Operating system..... "Windows NT"
Release.............. "6.1"
    Hardware type........ "16x AMD64 Level"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 0
    Shortdump setting.... "full"
    Database server... "CMCBIPRD"
    Database type..... "MSSQL"
    Database name..... "BIP"
    Database user ID.. "bip"
    Terminal.......... "CMCBIPRD"
Char.set.... "C"
SAP kernel....... 701
created (date)... "Sep 9 2012 23:43:54"
create on........ "NT 5.2 3790 Service Pack 2 x86 MS VC++ 14.00"
Database version. "SQL_Server_8.00 "
Patch level. 196
Patch text.. " "
Database............. "MSSQL 9.00.2047 or higher"
SAP database version. 701
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
   NT 6.0, Windows NT 6.1, Windows NT 6.2"
Memory consumption
Roll.... 16192
EM...... 4189840
Heap.... 0
Page.... 16384
MM Used. 2143680
MM Free. 2043536
User and Transaction
Client.............. 001
User................ "BWREMOTE"
    Language Key........ "E"
Transaction......... " "
    Transactions ID..... "9C109BE2C9FBF18BBD4BE61F13CE9693"
Program............. "SAPLRSPC_BACKEND"
Screen.............. "SAPMSSY1 3004"
    Screen Line......... 2
    Information on caller of Remote Function Call (RFC):
System.............. "BIP"
    Database Release.... 701
    Kernel Release...... 701
    Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
    Call Type........... "asynchron without reply and transactional (emode 0, imode
     0)"
    Inbound TID.........." "
    Inbound Queue Name..." "
    Outbound TID........." "
    Outbound Queue Name.." "
Information on where terminated
    Termination occurred in the ABAP program "SAPLRSPC_BACKEND" - in
"RSPC_PROCESS_FINISH".
    The main program was "SAPMSSY1 ".
    In the source code you have the termination point in line 75
    of the (Include) program "LRSPC_BACKENDU05".
Source Code Extract
Line SourceCde
   45         l_t_info        TYPE rs_t_rscedst,
   46         l_s_info        TYPE rscedst,
   47         l_s_mon         TYPE rsmonpc,
   48         l_synchronous   TYPE rs_bool,
   49         l_sync_debug    TYPE rs_bool,
   50         l_eventp        TYPE btcevtparm,
   51         l_eventno       TYPE rspc_eventno,
   52         l_t_recipients TYPE rsra_t_recipient,
52 l_t_recipients TYPE rsra_t_recipient,
53         l_s_recipients TYPE rsra_s_recipient,
54         l_sms           TYPE rs_bool,
55         l_t_text        TYPE rspc_t_text.
56
57   IF i_dump_at_error = rs_c_true.
58 * ==== Dump at error? => Recursive Call catching errors ====
59     CALL FUNCTION 'RSPC_PROCESS_FINISH'
60       EXPORTING
61         i_logid       = i_logid
62         i_chain       = i_chain
63         i_type        = i_type
64         i_variant     = i_variant
65         i_instance    = i_instance
66         i_state       = i_state
67         i_eventno     = i_eventno
68         i_hold        = i_hold
69         i_job_count   = i_job_count
70         i_batchdate   = i_batchdate
71         i_batchtime   = i_batchtime
72       EXCEPTIONS
73         error_message = 1.
74     IF sy-subrc <> 0.
>>> MESSAGE ID sy-msgid TYPE 'X' NUMBER sy-msgno
76               WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
77     ELSE.
78       EXIT.
79     ENDIF.
80   ENDIF.
81 * ==== Cleanup ====
82   COMMIT WORK.
83 * ==== Get Chain ====
84   IF i_chain IS INITIAL.
85     SELECT SINGLE chain_id FROM rspclogchain INTO l_chain
86            WHERE log_id = i_logid.
87   ELSE.
88     l_chain = i_chain.
89   ENDIF.
90 * ==== Lock ====
91 * ---- Lock process ----
92   DO.
93     CALL FUNCTION 'ENQUEUE_ERSPCPROCESS'
94       EXPORTING
If we do this
Use table RSSDLINIT and in OLTPSOURCRE: enter the name of the data source
And in the logsys enter the name of the source system and delete the entry for that info package. what will happen is process chain will run suceesfully and short dump will not come or what kindly give the detail explanation about this RSSDLINIT.
Regards,
poluru

Making Period Start Date read-only on Appraisal page

Hi,
I have a requirement to default Appraisal Period Start Date and Period End Date and make these fields non-editable. I am able to default the values for these fields by extending CO. When I make these fields read-only and performs any operation on page, getting error
+'You must enter a value for Period Start Date as criteria for the List Of Values.'+
Please suggest a solution to resolve this error.
Thanks.
Edited by: user12037955 on May 12, 2011 9:26 PM

public void processRequest(OAPageContext pageContext, OAWebBean webBean)
super.processRequest(pageContext, webBean);
java.util.Date dateValue1 = null;
java.util.Date dateValue2 = null;
java.util.Date date = null;
OAApplicationModule oaapplicationmodule = pageContext.getApplicationModule(webBean);
OAMessageDateFieldBean bean1=(OAMessageDateFieldBean)webBean.findIndexedChildRecursive("StartDate");
OAMessageDateFieldBean bean2=(OAMessageDateFieldBean)webBean.findIndexedChildRecursive("EndDate");
String startDate=bean1.getText(pageContext);
String endDate=bean2.getText(pageContext);
String strDate1=null;
String strDate2=null;
if((startDate==null||startDate.equals(""))&& (endDate==null||endDate.equals("")))
date=pageContext.getCurrentDBDate();
SimpleDateFormat simpledateformat = new SimpleDateFormat("yyyy-MM-dd");
String dateValue=simpledateformat.format(date);
String year=dateValue.substring(0,4);
try
String sqlStatement = "";
CallableStatement cs = null;
// OAApplicationModule oaapplicationmodule = pageContext.getApplicationModule(webBean);
OADBTransactionImpl txn = (OADBTransactionImpl)oaapplicationmodule.getOADBTransaction();
cs = txn.createCallableStatement(" ",1);
sqlStatement = "SELECT to_char(to_date(ffv.attribute1,'RRRR/MM/DD HH24:MI:SS'),'DD-MON-YYYY') attribute1, " +
" to_char(to_date(ffv.attribute2,'RRRR/MM/DD HH24:MI:SS'),'DD-MON-YYYY') attribute2 " +
" FROM apps.fnd_flex_value_sets ffvs,apps.fnd_flex_values ffv " +
" WHERE ffv.flex_value_set_id = ffvs.flex_value_set_id " +
" AND ffvs.flex_value_set_name = 'XXX_PMP_Fiscal_Date_VS' " +
" AND (SYSDATE BETWEEN NVL(ffv.start_date_active,SYSDATE) AND NVL(ffv.end_date_active,SYSDATE)) " +
" AND flex_value= " + year +
" AND ffv.enabled_flag = 'Y' ";
ResultSet rset = cs.executeQuery(sqlStatement);
if (rset.next())
strDate1 = rset.getString(1);
strDate2= rset.getString(2);
catch(Exception e)
throw new OAException("Error:" + e.toString(), OAException.ERROR ) ;
SimpleDateFormat convertFormat = new SimpleDateFormat("dd-MMM-yyyy");
if(strDate1!= null || strDate2!=null)
try
dateValue1 = convertFormat.parse(strDate1.toString());
dateValue2 = convertFormat.parse(strDate2.toString());
catch(Exception exception)
bean1.setValue(pageContext,dateValue1);
bean2.setValue(pageContext,dateValue2);
bean1.setReadOnly(true);
bean2.setReadOnly(true);
}

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.

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

Use of field 'StartPoint' in work order operation's 'Dates' tab

Hi,
Can someone please explain me on the uase of field 'StartPoint' on work order operation's Dates tab.
Regards.

Start point will be used in case of scheduling for the operation.
By mentioning the condition & date, while doing automatic scheduling, system will change the start date of the operation & correspondingly finish date.
Note: This will work only when Automatic scheduling is ticked for the control key.
Regards,

PP DataSource 2LIS_04_P_ARBPL - Incorrect extraction of latest scheduled start dates (SSAVD)

Hi experts,
we use the SAP Business Content Standard DataSource 2LIS_04_P_ARBPL "Work Center View PP" and need the latest scheduled start date each production order operation.
In the production order operation overview (t/code CO03) on the ERP-side we have the expected latest scheduled start (Source AFVGD-SSAVD)
But in the DataSource 2LIS_04_P_ARBPL (PSA-Table) we become the incorrect latest scheduled start dates (DataSource field SSAVD)
Any ideas or experiences why the latest scheduled start date not up-to-date?
Many thanks and best regards,
Michael

Hi,
I have tested the scenario again...
At the header level of test production order 1000381 I have changed the basic dates (Start/End) from 22.04.2014 to 24.04.2014.
As a result the start dates at operation level also changed...
After the above changes I have extracted the Data. The Delta-Queue (RSA7) for the relevant DataSource 2LIS_04_P_ARBPL looks nearly good.
For the both operations 20 and 30 the delta update for the field "Latest start date" (SSAV) works correct. But the delta update for the first operation "10" not processed.
Is it possible that the delta update only works for specific system status? Or any other ideas?
Many thanks and best regards,
Michael

WO basic start date - requirement date

Good morning folks,
Would anyone be able to shed some light on any config that would be suitable for the following:
The materials are assigned to a task list that is then assigned to a plan. That plan is then scheduled and the work orders are generated.
When the materials are added to the work order their requirement date is automatically assigned as the work order basic start date - can this requirement date be pulled from the scheduled dates instead?
The problem is that the material may not be required at the beginning of the WO, so the defaulted basic start date of the WO would not be the way forward.
Thanks
Mantas

hi Mantas
you can set in scheduling parameters with following possibilities
<b>Path Plant maintenance and customer service->Maintenance and service order->scheduling->set scheduling parameter</b>
1)The basic dates are adjusted and the dependent requirements are scheduled for the start dates of the relevant operations.
2)The basic dates are not adjusted and the dependent requirements are scheduled for the start dates of the relevant operations.
3)The basic dates are adjusted and the dependent requirements are scheduled for the order basic start date.
4)The basic dates are not adjusted and the dependent requirements are scheduled for the order basic start date.
so when you add the components you have to assign the operations,after selecting the operation you can change the operation date, after you change the operation dates,the material scheduled dates will be changed to the operation date
(using the option <b>1</b>)
regards
thyagarajan

Early start & lates start date

Hi experts,
I want to change the early start & latest start date which are in grey mode of maintenance order operation direcly instead of changing the order basic start date .How can I do it? please through some clues.thanks

Hi,
Can you please try this.
1. IW32, go to Operations tab, Select Operation 10 (assuming you only have one operation)
2. Click the "Dates" button from the buttons at teh bottom
3. On the Restrictions tab, StartPoitn, Select "Must Start On", then specify the Date you want to start the work on the right
4. Save the Work Order
Regards,
Joey

Latest and finish start dates.

Dear all,
1.What is actually meant by latest and finish start dates?
2.In my maintenance order, when i am using my workcenter against each operations, the earliest start date, earliest end date, earliest start time, and its finish time is calculating based on the WORK not on DURATION. How it normally take ?
3.Even if we are using indian calendar in the workcenter (Also capacity uitilization is 100%) system is not calculating the actual time (Scheduled done manually also by click the scedule icon in the order screen.)
Regards,
Prasanna.

hi prasanna
latest and finish start date is based on the notification which is assigned to the order, in IMG for notification priorities you would specify the sch,start & finish days for each priority which will calculated the start and finish dates
in maintenance order the sch,start and finsih date will be calcualted based on the duration only ( which has calcualted based on work and number of employees).in your case in capacity master data you have specified 100% and start and finish times as 08.00 and 17.00, length of break 1.00 hr,then in the maintenance order if you specify your work and number as 1, the duration will be calculated as 1 and the dates will be calculated as
stard date & time 14/12/07, 08:00
End date & time 14/12/07, 09:07
sytem has calculated the times ( total working time-operating time)/Operating time for each HR, in this case 9-8/8 which is 0.125 hr or 7.5 minutes
regards
thyagarajan

Floats for order start dates

Dear Experts,
Please throw some light on Earliest start / End dates and Latest start / End dates . Will they affect scheduled dates . How the buffer Total float and free float affect these dates . In our system the field for total float and free float are in display mode . How to edit these fields.

Hi
Scheduled dates are affected by the Earliest start and finish dates as they are dependent on these dates.
Float fields are the Calculated fields base on Basic dates and scheduled dates
Definition of Total Float is "The time that an activity can be moved to the future starting from its earliest dates without affecting the latest dates of its successor or the latest finish date of the network."
Similarly for Free Float "The time that an activity can be moved into the future starting from its earliest dates without affecting the earliest dates of its successor or the earliest finish date of the network.
The free float must not be less than zero or greater than the total float."
Hence these dates can not be in display mode as they cannot and should not be changed.
Based on your basic start date and the duration of operations the scheduled dates will change on scheduling and Float will be calculated .
Also Adjust Dates Setting in OPU7 plays an important role in scheduling.You may explore these settings in your IDES sytem
Regards
Manish
Edited by: Manish Chachra on Feb 26, 2010 3:15 PM

Operation Start Date

Similar Messages

Maybe you are looking for