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 <i>Functions -> Schedule -> Order</i> (or save the order) SAP set these dates to '02.01.2008', and scheduling also to '02.01.2008'. The scheduling type is <b>Forwards in time</b>. Scheduling margin: everything is 0.
I have checked the <b>work center capacity</b>:
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!

Similar Messages

  • 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

  • Daily production order scheduling

    Hi Experts,
    i am using maximum lot size procedure  for the MRP Run and after MRP ,planned orders are generated based on the maximum lot size and these planned orders are further converted in to production orders.
    my requirement is how to schedule the production order on daily basis,please suggest me an appropriate solution.
    Thaks in advance.
    Regards
    Srinivas

    Hi,
    Production orders scheduled start dates are generating for the whole month for a material as same date like first working day of the month (Here i am using maximum lot size) and the orders can be only scheduled for the particular date in order dispatching transaction.
    Example,
    Material : X
    Maximum lot size : 1000 in MRP 1 view
    PIR Qty : 01.08.2008  1000 Pcs
    after MRP,
    10 Planned orders are generating with schedlued start date as 01.08.2008.
    after converting all the 10 planned orders in to production orders , then all the 10 production order are generated with scheduled stat date as 01.08.2008.
    While dispatching the production orders in CM25, the system is showing all the work centres are overloaded on 01.08.2008, because system is considering all the production order are start date as 01.08.2008.
    But  i want get the production order scheduled start dates based on the capacity availability  ,so please suggest me the appropriate solution.
    Thanks in advance.
    Regards
    Srinivas

  • Auto TECO Orders for which finished date has been reached-Periodic Job

    Dear PP GURUS N EXPERTS,
    My company want to TECO all the production order automatically for which finished date has been reached or (Finish date is before current date).
    On SDN, I have found that it can be carried our by scheduling the variant of PPIO_ENTRY or COHV. and it will be a periodic job.
    I want to know that for this which parameters I have to select and where / how I mention that order finish date has been reached. Since it will be a periodic job.
    Early response will be highly appreciated.
    With thanks,
    DSC

    Dear DSC
    You can use tranaction code CO44, define a variant for periodic job.
    Important selection parameters :
    Status selection profile : define which kind of production orders you want to set TECO indicator, for example with status CNF or DLV.
    Basic finish date : define basic finish date, for example if you want to TECO the production orders whose basic finish date is less than or equal current date, when you create the variant, selection variable can be D ( D: Dynamic date calculation ), name of variable can be "current date"
    Actions : please select the indicator "complete Technically".
    You can have a try, please let me know the result.
    Qiu

  • 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

  • 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

  • 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,

  • Create a production order with variant configurator data

    Hello,
    Can anyone tell me the way to create a production order with variant configurator data. Is there a BAPI ? an IDOC ?
    Is there several steps ?
    I have to create an interface which creates automatically PP orders. The data input is a file.
    Thanks for your help

    Hi,
    There are fews BAPI's available for creation of Production Order. They are:
    BAPI_PRODORD_CREATE
    This bapi will suit to your requirement, as input will be provided from file.
    Others are
    BAPI_PRODORD_CREATE_FROM_PLORD " this converts planned order to production order
    BAPI_PRODORD_CREATE_FROM_REF      " this creats production order considering other production order as reference.
    Hope your query is answered.
    Regards,
    Brajvir

  • 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

  • TCODE TO FIND OUT SETTLED PRODUCTION ORDER ON A GIVEN DATE

    What is the Tcode to find out settled Production Orders on a given date?

    Hi Debasish,
    Have you tried with COOIS,
    regards
    pardeep

  • 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

  • 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

  • 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

  • Production Orders: Scheduling Problem

    Hello
    I have a scheduling problem.  I want the system to calculate the production order dates.
    I have maintained the following
    1.      Work Center:  A formula to calculate the duration.  I have marked the u201Crelevant to finite indicatoru201D in the Capacity Header Tab.  I have also maintained the available capacity as 24 Hrs.
    2.     Routing:  I have maintained the values for the standard value keys
    3.     SPRO:  In scheduling parameters for the order type, I have marked u201CGenerate cap requirementsu201D and u201CSchedulingu201D;  In the production scheduling profile, I have marked u201CSchedule orderu201D (on release) & u201CFinite Schedulingu201D (Availability check).
    But the production order is not getting scheduled & the start & end times are the same.  I get the error u201CNo req/capacity exists or not relevant for finite schedulingu201D.
    Can anyone guide me as to what I am missing?
    Best regards
    Tom

    Dear Tom,
    Please check following;
    1. Your operation contol key; whether it allows scheduling.
    2. scheduling parameters for production order on OPU3: Please select proper combination of plant and order type and tick scheduling and generate capacity requts indicators in detailed scheduling tab.
    Please revert back if problem persist.
    Best Regards
    Uday

  • 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,

Maybe you are looking for

  • Credit Related Issue

    Hello friends, My customer no is 1000, for him no open orders in VA05 and no deliveries pending in VL06 for customer 1000..But when I see in FD33 for customer 1000 in Environment-Sale and distribution documents---open orders=18000 value and open deli

  • Adding object to collection outside of unit of work?

    Hi, Tried to find the answer in this forum but difficult to know what keywords to use...anyway What I am trying to do is so simple I can only believe I am missing the point somewhat ;-) I have an object Licence that has a Set of LicenceHolders. I hav

  • Dir listing with umlauts / special characters

    I've got a directory tree, where several files have umlauts or french accented characters in their names. When I do 'ls' in such a directory, I can see the umlauts fine in Terminal, e.g.: Die rote Wüste - Michelangelo Antonioni.avi Nazarin - Luis Buñ

  • Not allow to add condition type, if it already existing

    How to setting, if I want to control that not allow to add same condition type, if it already existing in the transaction. For example, PR00    100.00 USD/MT ZDIS       10.00 USD/MT ZDIS         8.00  USD/MT (Not allow to enter or add condition type)

  • I18n support?

    Hi, does Flex offer I18n support? I mean in the meaning of  bundling all texts from the application into several txt or properties files and translate them for the different languages. As I'm planing to develop business applications this is a crucial