In backward scheduling system is asking starting date in planning Boar

In my project i am using backward scheduling ,before going for scheduling i am delete the basic start date of project and network header .then i go to planning board and carrying scheduling now system is give me a popup "start date ".than i maintain the start date and carry the scheduling , in the backward scheduling starting is not required and system is determine starting date also , why system is asking starting date please let me know any configuration changes in Planing board or scheduling parameter.
Regards
Rao

Dear Abdul ,
In opu6 in maintain starting in past 999
and opu6 configurations
adjust basic date -2
scheduling type -backward
start in past -999
and check automatic scheduling,latest staging date
in the control parameter for wbs scheduling also
scheduling type -backward
starting date -999
scheduling method -wbs determine dates
and check-adjust basis date
Regards
Rao

Similar Messages

Same station resource with same schedule squence but the start date is diff

We are running ASCP capacity planning but found "Same station resource with same schedule squence but the start date is different". Does anyone know which parameters/setup may impact on this result or the root causes?
Regards,
Edward

Wesley,
I am a little confused about your scenario. I will assume that you are talking about the Planned orders that are generating the dependent requirements that are being seen by your Raw Material.
So, you have a material (not the Raw Material) that has the Material master settings that you mentioned above. This material has been planned, and MRP created two planned orders. These two planned orders have the same start date, but the dependent requirements dates that have been generated against your Raw Material are different. You do not want this to happen. Please confirm.
Dependent requirements of planned orders can be influenced by:
1. Dependent Rqments Settings in OPU5
2. Distribution Strategy OPB3/OPB4/OPB5
3. Lead Time offsets in the BOM
Ensure that these settings meet your business requirements.
Best Regards,
DB49

Scheduled system maintenance on US data center - November 23rd 2014

To ensure the highest levels of performance and reliability, we've scheduled a database server upgrade on our US data center. To minimize the customer impact, the upgrade is scheduled at the most convenient hours and will take up to 8 hours to complete. During the maintenance procedure, creating and updating content, Partner registration, trial site creation, publish from Muse, sFTP, APIs and some site admin sections will not be available. Additionally, during the 8 hours maintenance procedure, all sites on the US data center will experience 4 sessions of 15 minutes downtime. Except for the 4 scheduled downtime sessions, the website front-ends will not be impacted by the maintenance.
Maintenance schedule:
Start date and time: Sunday, November 23rd, 3:00 AM EST (check data center times)
Duration: We are targeting a 8 hours maintenance window
Customer impact:
Partner registration, Trial site creation, Adobe Muse publish, APIs, FTP and some admin section will not be available through the entire maintenance window on all data centers
All websites and services on US data center will experience 4 sessions of 15 minutes downtime sometimes within the maintenance window
Creating or updating content on sites located on US data center will be unavailable during the maintenance procedure
For up to date information about system status, check the Business Catalyst System Status page. We apologize for any inconvenience caused by these service interruptions. Please make sure that your customers and team members are made aware of these important updates.
Thank you for your understanding and support,
The Adobe Business Catalyst Team

agents will be online for update from console.
Method 1: Update the protection agents from the Data Protection Manager Administrator Console
Open the Data Protection Manager Administrator Console.
Click the Management tab, and then click the
Agents tab.
In the Protected Computer
list, select a computer, and then click Update on the Action pane.
Click Yes, and then click
Update Agents.
Note You may have to restart the computer after you install the agent upgrades.
Method 2:Update the protection agents on the protected computers
Obtain the update protection agent package from the following directory on the System Center 2012 R2 Data Protection Manager server:
<var>Data_Protection_Manager_installation_location</var>\DPM\DPM\Agents\RA\4.2.1217.0
The installation packages are as follows:
For x86-based updates: i386\1033\DPMAgentInstaller_KB2904687.exe
For x64-based updates: amd64\1033\DPMAgentInstaller_kb2904687_AMD64.exe
Run the appropriate DPMAgentInstaller.exe package on each protected computer, based on the architecture of the agent.
Open the Data Protection Manager Administrator Console on the System Center 2012 R2 Data Protection Manager server.
Click the Management tab, and then click the
Agents tab. Select the protected computers, update the information, and then verify that the agent version number is 4.2.1217.0
Have a nice day !!!

Scheduled system maintenance on EU data center - October 26th, 2014

To ensure the highest levels of performance and reliability, we've scheduled a database server upgrade on our EU data center. To minimize the customer impact, the upgrade is scheduled at the most convenient hours and will take up to 6 hours to complete. During the maintenance procedure, creating and updating content, Partner registration, trial site creation, publish from Muse, sFTP, APIs and some site admin sections will not be available. Additionally, all sites on the EU data center will experience a 20 minutes downtime sometimes during the maintenance window. Except for the scheduled 20 minutes downtime, the website front-ends will not be impacted by the maintenance.
Maintenance schedule:
Start date and time: Sunday, October 26th, 9:00 AM UTC (check data center times)
Duration: We are targeting a 6 hours maintenance window
Customer impact:
Partner registration, Trial site creation Muse Publish, APIs, FTP and some admin section will not be available through the entire maintenance window on all data centers
All websites and services on EU data center will experience a 20 minutes downtime sometimes within the maintenance window
Creating or updating content on sites located on EU data center will be unavailable during the maintenance procedure
For up to date information about system status, check the Business Catalyst System Status page. We apologize for any inconvenience caused by these service interruptions. Please make sure that your customers and team members are made aware of these important updates.
Thank you for your understanding and support,
The Adobe Business Catalyst Team

Congrats to Alan! Only one article, but it's a good one!
System Center Technical Guru - October 2014
Alan do Nascimento Carlos
ALM and IT Operations - Management 360 with System Center Operations Manager
in 06 Steps
Ed Price: "Lots of images. Great job breaking up the steps! Could benefit from a TOC and References. Great article!"
GO: "Thanks for the only article. great btw. :-)"
Ed Price, Azure & Power BI Customer Program Manager (Blog,
Small Basic,
Wiki Ninjas,
Wiki)
Answer an interesting question?
Create a wiki article about it!

Scheduled system maintenance on US data center - March 15th 2015

To ensure the highest levels of performance and reliability, we've scheduled a database server upgrade on our US data center. To minimize the customer impact, the upgrade is scheduled at the most convenient hours for the region and will take up to 6 hours to complete. During the maintenance procedure, Partner registration, trial site creation, publish from Muse, sFTP, APIs and some site admin sections will not be available for sites on all data centers (including EU and AU). Additionally, during the 6 hours maintenance procedure, all sites on the US data center will experience 2 sessions of 1 minute downtime. Except for the 2 scheduled downtime sessions, the website front-ends will not be impacted by the maintenance.
Maintenance schedule:
Start date and time: Sunday, March 15th, 6:00 AM UTC (check data center times)
Duration: We are targeting a 6 hours maintenance window
Customer impact:
Partner registration, Trial site creation, Adobe Muse publish, APIs, FTP and some admin sections will not be available through the entire maintenance window on all data centers
All websites and services on US data center will experience 2 sessions of 1 minute downtime sometimes within the maintenance window
For up to date information about system status, check the Business Catalyst System Status page. We apologize for any inconvenience caused by these service interruptions. Please make sure that your customers and team members are made aware of these important updates.
Thank you for your understanding and support,
The Adobe Business Catalyst Team

Congrats to Noah and Mr. X!
System Center Technical Guru - March 2015
Noah Stahl
Make System Center Orchestrator Text Faster than a Teenager using PowerShell
and Twilio
Ed Price: "Wow, I love the breakdown of sections. As Alan wrote in the comments, "Wow! Great article!""
Mr X
How to educate your users to regularly reboot their Windows computers
Ed Price: "I love the table and use of code snippets and images! Great article!"
Ed Price, Azure & Power BI Customer Program Manager (Blog,
Small Basic,
Wiki Ninjas,
Wiki)
Answer an interesting question?
Create a wiki article about it!

Dynamic update of Planning Start Date in Planning Book

Hello.
Has anyone ever created a program to update the Planning Start Date of a Planning Book dynamically to the next Friday of the month for example?
The help information available for this field mentions a PDATE userexit, but I can not find it. Has anyone ever used it and has some examples to share?
Many thanks.
Aline Passos

Hi there,
I have never done this earlier. However i know that planning start date is stored in table /SAPAPO/PBDVWHDR-TBID_START. I tried changing this entry in the table and it correctly updated the dataview plannig start date.
So you may write a small program to update this field and it shall update the dataview.
Please let me know if this helps you.

Calculation of start date with backward scheduling

Dear all,
I am facing an issue related to backward scheduling. I have requirement in which whenever backward scheduling is used, system should calculate from last activity to first for calculation of schedules which is fine. But when running scheduling i am giving finish date as input and system is always using start date as current date and not calculation last date from last. For example if i input finish date as 15 feb 2015, and there is only one activity of 15 days, system should count start date from 1 feb 2015. Please help me how i can achieve this, currently its always putting start date as current date.
My current settings are--
Project definition- WBS Scheduling profile- Backward scheduling
                              scheduling scenario- Free scheduling
Network-      Planning type- basic dates
                    Scheduling type- Backward
Please help.
Thanks

Dear all, this issue is resloved. Reason was that by default i am using forward scheduling for all project but in case of backward scheduling, user change schedule type at project definition and network. I was removing start date and putting finish date and running scheduling. Missing step from my side was i need to first copy date from top to down than run scheduling again.
Thanks.

Problem-planned order start date in the past

I use PP-PI - After MRP run, planned order was created and has exception message "06-start date in the past" its make me wonder because before this problem occur we already tested many time and never found this message(06). then i check in OPPR- field "start in past" is blank, OPPQ- field "Start in past" are not check, OPUZ-Scheduling Type is backwards and field "Start in the Past" is blank, OPU5-Scheduling Type is backwards and field "Start in the Past" is blank.
do any guru know why system not use forward scheduling when found that start date in the past? or have any config of other module which may lead to this issue?
thank in advance.

In OPU5,
Check the setting for correct MRP group which is assigned in material master or in the SPRO node
Production >Material Requirements Planning>MRP Groups-->Define MRP Group for Each Material Type.
check and come back

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

In plant parameters how the start date in past will be applicable for order

Hi All,
Can any one explain me in detail start in past for plant parmeters (OPPQ).
Regards
sailendra

Hi,
Start date of order proposals allowed in the past
This indicator defines that the system does not automatically switch to forward scheduling if the order start date lies in the past for determining the basic dates. With this indicator, backward scheduling is always used to determine the basic dates, even if the start date lies in the past.
e.g Bacward scheduling type, Today date is 08.06.2009
If u give basic finish date say 25.06.2009,and system propose you basic start date in 06.06.2009. That is 06.06.2009 is lies in past date.In this case system propose you forward scheduling.Means order basic start date is 08.06.2009 .If you don't want to system propose you for forward scheduling tick mark Start in past in OPPQ.
Hope this clear you.
Regards,
Raja.

Forward and Backward Scheduling

I have a couple of related questions.
1. Where can I configure if I want Forward/Backward Scheduling in Customization? and if I leave it blank will it do forward or backward scheduling?
2. Does the system not perform backward scheduling if Replenishment Lead Time (RLT) is setup? If yes why?

Hi,
Backward scheduling is the calculation of deadline dates: the arrival time at the customer site is calculated as the earliest
possible goods receipt time at the customers unloading point on the requested delivery date. All four of the delivery and
transportation scheduling lead times are subtracted from the customeru2019s requested delivery date to determine if this date can
be met.
The transit time, loading time, and pick/pack time are subtracted from the customeru2019s requested delivery date to calculate the
required material availability date.
The system calculates backward scheduling as follows:
Requested delivery date minus transit time = Goods issue date
Goods issue date minus loading time = Loading date
Loading date minus transportation lead time = Transportation scheduling date
Loading date minus pick/pack time = Material availability date
Forward scheduling is also done if no product is available on the material availability date calculated by backward
scheduling. The system does an availability check to determine the first possible date when product will be available. This
new material availability date forms the starting point for scheduling the remaining activities. The loading time, pick/pack time,
transit time, and transportation lead time are added to the new material availability date to calculate the confirmed delivery
date.
Regards
Ram

Dirrerence between backward scheduling and forward scheduling

hi Friends,
This is madhusudhan i need diff b/w backward scheduling and forward scheduling
plz do the needfull asap

Hi,
Backward scheduling is the calculation of deadline dates: the arrival time at the customer site is calculated as the earliest possible goods receipt time at the customers unloading point on the requested delivery date. All four of the delivery and transportation scheduling lead times are subtracted from the customers requested delivery date to determine if this date can be met.
The transit time, loading time, and pick/pack time are subtracted from the customers requested delivery date to calculate the required material availability date.
The system calculates backward scheduling as follows:
Requested delivery date minus transit time = Goods issue date
Goods issue date minus loading time = Loading date
Loading date minus transportation lead time = Transportation scheduling date
Loading date minus pick/pack time = Material availability date
Forward scheduling is also done if no product is available on the material availability date calculated by backward scheduling. The system does an availability check to determine the first possible date when product will be available. This new material availability date forms the starting point for scheduling the remaining activities. The loading time, pick/pack time, transit time, and transportation lead time are added to the new material availability date to calculate the confirmed delivery date.
Reward points if it helps

Re : Backward Scheduling

Hi
How to set transit time, Picking time, Packing time for the required delivery date in Backward Scheduling Process.
Thanks
Mani

Dear Mani,
Example of Backward Scheduling for In-House Production
Example Data
Requirements date
25.6. (Friday)
Goods receipt processing time
2 days (workdays)
In-house production time for the material:
6 days (workdays)
Opening period
6 days (workdays)
Workdays = Monday to Friday, no bank holiday
Scheduling
Requirements data minus goods receipt processing time = order finish date
25.6. (Friday) minus 2 workdays = 23.6. (Wednesday)
Order finish date minus in-house production time = order start date
23.6. (Wednesday) minus 6 workdays = 15.6. (Tuesday)
Order start date minus opening period = order opening date
15.6. (Tuesday) minus 6 workdays = 7.6. (Monday)
Example of Backward Scheduling for External Procurement
Example Data
Requirements date
31.10. (Monday)
Planned delivery time of the material
10 days (calendar days)
Processing time for purchasing
1 day (workdays)
Goods receipt processing time
2 days (workdays)
Opening period
10 days (workdays)
Workdays = Monday to Friday
Scheduling
Requirements data minus goods receipt processing time = order finish date (provision date for vendor)
31.10. (Tuesday) minus 2 workdays = 27.10. (Friday)
Order finish date minus planned delivery time minus processing time for purchasing = release date for purchase requisition or order start date of planned order for external procurement.
27.10. (Friday) minus 10 calendar days minus 1 workday = 16.10. (Monday)
Release date minus opening period for planned order = opening date of planned order
16.10. (Monday) minus 10 workdays = 2.10. (Monday)
I hope it will help you,
Regards,
Murali.

Difference in Maintenance Plan date to Order basic start date

If i creat a strategy plan and schedule, i am getting difference in PLan date in Maint plan to Basic start date. What is making this difference. How to overcome this. I need Order start date same as PLan date.
Plz help me frnds.
Guruprasad

hi
can you explain in details with your maintenance plan with the dates.Normally your call date and plan date will be different becase of call horizon ,but the order basic start date and plan date will be equal only
kindly revert back
regards
thyagarajan
your order basic date will be when you have maintenance call is generated.kindly check
Edited by: thyagarajan krishnamurthy on Feb 25, 2009 9:46 AM

Basic finish date earlier than basic start date while backward scheduling

I am encountering an issue where in when I am selecting backward scheduling for a process order and I am entering the Basic finish date, afte which system is giving me a Basic startdate which is after the basic finish date.
For eg:- When i give the basic finish date as 08.12.2011, system is giving me basic start date as 09.12.2011
I have checked the recipe of the material. In the recipe one major flaw that i found out was that all the activity timings were maintained as 0. But when i created a similar scenario in the testing client, i am not getting the issue.
Please help.

Hi,
Check what is maintawined in number of days the start day is allowed to be in the past in scheduling parameters of the order type, in OPU3. If there is an opening float defined in schedule margin key of the order, and concerning this float backward scheduling finds a start date which falls into past, lead time scheduling will automatically switch to forward scheduling starting from today. 9.12.2011 could have been deducted this way. Also check the factory calendar if days upto 9.12.2011 are defined as working days.
Regards.

In backward scheduling system is asking starting date in planning Boar

Similar Messages

Maybe you are looking for