Reduction strategy in scheduling

1     The following is true for reduction strategy in scheduling
A     Wait time can be reduced to minimum wait time from standard wait time
B     Move time can be reduced to minimum move time from standard move time
C     Processing time can be reduced up to 6 level by certain percentage in each level
D     Floats can be reduced as per the setting for reduction strategy in scheduling parameter for order type

The question is with respect to reduction strategy in scheduling what are all correct.
I think the wait time cannot be reduced.
Can u clarify?

Similar Messages

Reduction strategy or Overlapping.

Hi
we have maintained 10 operations in Routing. But i need to pick only 2 operations machine timing for the calculation for schedlng.
how to achieve this. Whether i need to user Overlapping or Reduction Strategy.
Thanks
vraj

Hi,
In Work Center Scheduling Tab leave the Setup formula and Procession formula fields blank for the operations where you dont want to consider the operations for scheduling.
If Formula fields are blank then system will take Set up and Procession times as zero.
With best regards
Shankarling.

Release strategy for Schedule lines in SD

Hello All
Can we create a release strategy for Schedule Lines in Scheduling Agreement? If Yes How?
I have already maintained a release strategy for Item Level... which I want to put it for Schedule line as well....
Thanks in advance.

Hello,
I think you are in the wrong forum. Please choose the right forum category and post it there.
Matthias

Release strategy for Scheduling Agreement(SA)

Dear Forum,
This issue is with regards to the release strategy for Scheduling Agreement(SA)
Until now release has only been applicable to contracts at our client site. But we now plan to introduce it for SA as well. Such a feature is available in SAP but the problem is that with the given release strategy GR is not allowed until the release is affected. The system allows you to post the delivery schedule.
Now what I want is that after making the SA the system should not allow to make delivery schedule if release is not affected.
We also have MRP run at client site..Kindly suggest the procedure as, how to configure it.Are der any User Exit for the same,if so please discuss..
Warm Regards
Nainesh
SAP ECC 6.0

Hi,
What's the SA Type that was created via MRP.
If it's LP (without release document), release will not do anything BUT
If it's LPA (release document), then you will not be able to Post the GR until release is affected.
Thanks.
Scheduling Agreement can be categories as
1) LP (without release document) and
2) LPA (with release document)
If use LP, you can do GR without release but with LPA, you need to release the schedule line via ME38.
Thanks.
NanoSAP
Posts: 58
Registered: 1/5/09
Forum Points: 6
   Re: release strategy for Scheduling Agreement(SA)
Posted: Jun 26, 2009 8:32 AM    in response to: sathish.kumar           Reply
Dear Mr.Satish,
Thanks a lot for your earliest reply...But my point is i want the system should not allow to make delivery schedule if release is not affected...Though schedule lines are generating through MRP run...Is is possible,by any chance...??

Appluing release strategy for scheduling agreement

Dear Sapguru,
Can anybody explain.How to apply release strategy to scheduling agreement.I'm working on MRP implementation project.
Here already release strategy using for PO.
Pls explain steps of release strategy to scheduling agreement.

Hi,
Welcome you post on the forum.
Have you searched the forum already? Such as:
http://forums.sdn.sap.com/search.jspa?threadID=&q=%22applyreleasestrategy%22&objID=f245&dateRange=all&numResults=15&rankBy=10001
Thanks,
Gordon

Reduction strategy in Rate routing.

Hi
I have a Rate routing with 3 WC for 3 operations
Each operation take 30 mints to finsh
If i want to produce 5 qty in the 3 WC.
time taken for the machining is = 30 mins * 5 qty(WC1) + 30 mins * 5 qty(WC2) + 30 mins * 5 qty(WC3)
                                                 = 71/2 HRS to finsh the 5qty jobs
but as per normal -                            w1      w2      w3
                       JOBS          1       9:00 AM       9.30 am     10.00 am
                                         2       9.30 am     10.00 am     10.30 am
                                         3     10.00 am     10.30 am      11.00 am
                                         4     10.30 am      11.00 am     11.30 am
                                         5     11.00 am     11.30 am     12.00 am
Total it will take 3 hrs to finish
how to do this reduction in the Routing.
what REDUCTION STRATEGY WE NEED TO USE . PLS EXPLAIN.
Can i use the Contioud flow prod in the overlapping tab in the operation details
Thanks
vraj

Hi,
Yes, U can use Overlap strategy to meet your requirements. Please maintain all the values correctly and do some work around and test properly before doing it in production client.
Regards
Suri

Approval process (Release strategy of scheduling agreement)

Hi,
Recently we are trying to implement the approval process of scheduling agreements.
Client requirement is when ever there is a change in price irrespective of the following
1. Retrospective price change in any line item
2. Current price change in any line item
3. Future price updation in SA in any line item
4. New addition of line item
the system should trigger the release process (i.e. Approval process).
Our idea is to design the approval process based on document type and net value of SA. Based on which trigger should happened. But when we test it we find the following issues.
1. Trigger is not happening for future date price change or price for new period as the net value of SA is based on validity time.
Becuase the net value change will happen only on that onwards..
Also we are not using any cumulative pallned values in agreements.
Any can suggest the best solution to over come this..or Any user exit is avaliable to handle this issue.
regards,
K.Sundaresan.

Below are the (changed) item fields :
Purchasing Document Item Change Date AEDAT
Item Delivery Date EINDT
Schedule Line is "Fixed "FIXKZ
Below are the (changed) header fields :
Release Indicator: Purchasing Document FRGKE
Release status FRGZU
Purchasing document processing state PROCSTAT
Item and header changes have same "Change document number " and transaction code "ME38" , this happened only in some cases,Rel Strategy is on document type level ,I am also confused on this .
Please assist on this

ME38 resets Release strategy of Scheduling agreement

Hello,
It seems when the users change the delivery date in the delivery schedule (transaction ME38), the system in some cases resets the release strategy of the scheduling agreement from "Release" to "Not Release".It happened only in some case,release indicator set to "4" in our case.
I cannot understand why this happens.
Has anyone encountered such a problem before.
Thanks
Sunil

Below are the (changed) item fields :
Purchasing Document Item Change Date AEDAT
Item Delivery Date EINDT
Schedule Line is "Fixed "FIXKZ
Below are the (changed) header fields :
Release Indicator: Purchasing Document FRGKE
Release status FRGZU
Purchasing document processing state PROCSTAT
Item and header changes have same "Change document number " and transaction code "ME38" , this happened only in some cases,Rel Strategy is on document type level ,I am also confused on this .
Please assist on this

Release strategy for Schedule Lines

Hi,
The requirement is MRP should not run for Line item unless it is released by an authorized user. Logically availability check has to happen at the time release of the requirement line for the consideration of realistic manufacturing time. Also, user should not be able to cancel the release, or edit the schedule line once Planned or Production Order is generated for the requirement line.
What we want is a Release Strategy in sales order for each schedule line individually similar to PO Release.
I have currently set up a status profile, which has 2 levels Processing and approved, which effectively block creation of DELIVERY doc, but I am unable to control the schedule line.
Any ideas?
Cheers.
Edited by: Sowmya Mohan on Sep 12, 2008 1:14 PM
Edited by: Sowmya Mohan on Sep 17, 2008 10:17 AM
Edited by: Sowmya Mohan on Sep 17, 2008 1:03 PM

Hello,
I think you are in the wrong forum. Please choose the right forum category and post it there.
Matthias

ERROR While network creation

Hi Experts,
While creating the network for any WBS in my project , it is giving an error msg "No parameters for network type PS05 exist (Check entry)." I checked it in network profile, the network type is assigned there.Please tell me how should i proceed.
regards:
Nishu

Hi,
Parameters for network types:
1.a standard distribution rule for settlement
2.a reduction strategy for scheduling
3.the costing variants for planned costs and actual costs
4.a strategy for determining the settlement rule
5.whether the network has header or activity account assignment
6.indicator whether a workflow is to be created for changes to quantities or dates of non-stock components, externally .
8.indicator whether the net price is to be copied from the purchase requisition into the purchase order without any changes.
Muzamil

Scheduling - Min. queue time & work center / reduction

Hello,
I have a small issue with scheduling of production order.
I have maintained in a work center with Std. queue time = 15 days and Min. queue time = 7 days.
Means less then 7 days it should be not reduced and by enough time it should be calculated with 15 days.
I know the forward scheduling production takes 20 days ( 5 days for first operation plus 15 days Std. queue time for second operation)
By backwards I schedule the finish date which is less then 20 days in the future.
I would expect system would take 7 days (Min. queue time) instead of 15 days with using reduction strategy.
But system throws the message "Start date is in the past: today scheduling" and increases the finish date, with queue time = 15 day, instead to take
7 days!
I dont see system takes Min. queue time in account. Please help to find the error. Thansk!

Hi
Yes .Reduction strategy is only for floats to carry out detail scheduling
Reduction in the float before and after production in the order, expressed as a
percentage of the original float.
For example :
The original float before and after production was 10days in both cases. You
have entered level 2 as the maximum reduction level. The reduction of the float
is in the first level 40 and in the second level 60.
This means that in the first level the float is reduced by 40% of the
original value, that is 6 days. In the second level the float is reduced by 60% of
the original value, that is to 4 days
Regards
JH

Planned order scheduling in mrp

hi
iam trying to run MRP at my client place
facing problem in planned order dates
i choosen tequirement type BSF and strategy group as 11
in md 61 pir was given in a month of june2008(monthly)
after mrp run at modo4 iam getting planned order with
execption message 64 called order date in past
means iam getting planned order START DATE AND END DATE IN THE MONTH OF JUNE
where as i need to my planned order satar date in MAY MONTH and
end date must be 1st of june
means i given PIR which is my start of my june month
checked scheduling parameters which says backword scheduling, and i choosed planning mode 3 and leddtime scheduling
plz suggest which setting effects the planned order start and end dates??
regards
sasikanth

hi
i selected schedule margine key with 0 flots (key000)
and chossed *LEED TIME SCHEDULING (in mrp controll parameters :-scheduling 2 at MD02 )
how the reduction strategy helps in this case ,casue i am doing lead time scheduling system has to consider only routing time ??? right ??
plz suggest how to arrest message 64
regards
sasikanth
message 64 diagnosis enclosed
64: Production finish after order finish (P4)
Message no. MD427
Diagnosis
The production finish date calculated using the routing lies after the order finish date that was calculated using the in-house processing time in the material master record.
As the system uses the order finish date in the planning run, this situation may lead to material shortages if production is not finished until the production finish date calculated by the system.
System Response
This exception is displayed in the MRP list and in the current stock/requirements list.
Procedure
Check the times in the material master record and in the routing.
Check whether the order has to be rescheduled in.

Forward Bacward Scheduling.

Dear All,
For material-A
I run mrp using MD02.
For material A i set master data as below:
MRP TYPE:PD
LOT SIZE: EX
PROCUREMENT TYPE : E
IN HOUSE PRODUCTION TIME:2 Days.
GR PROCESSING TIME: 16 Days.
Strategy group:10
Consumption mode:1
Fwd consumption per. :45 Days.
Insert requirement 08.03.2009 -10,000 quan.
After MRP run i got result
In Planned order Hdr tab with following dates :
                     BasicDates      Production dates       Other dates
Ord.finish       15.03.2009      17.03.2009 10:12:46    Available for plng   31.03.2009
Start              13.03.2009      17.03.2009 00:00:00    GR processing time   16
Plnd open.      13.03.2009
And in planned order Det Scheduling Tab contains:
Parameters :
Scheduling type:1 Forwards
Reduction:NO reduction Carried out
Scheduling margin :Z05
So,can any one explain In planned order last tab Det Scheduling.
Scheduling type:1 Forwards How it comes?
Bcz i already define in my master Consumption mode:1 Backward consumption only
So,its how trigger with Forwards.
Is it any relation with master or its come with any customizing setting?
and also plz explain in master we define consumption mode when it trigger?
Plz help.

Hi,
I suspect the Start in past check box is not ticked for your plant.
So go to
spro - pp - mrp - planning - scheduling & capacity parameters - parameters for determining the basic dates
Here tick the check box for start in past.
You can do the same via OPPQ as well. After making the settings, re-run MRP with plng mode as 3.
Check & revert if it resolves the issue.
Regards,
Vivek

Urgent : scheduling in Routing

Hi all ,
I am using Grouping of work center that is in capacity header No od Ind capacity : 6 , start and finish time of the work center is : 07:00:00 to 07:00:00 so the capacity available in the Hour is : 24 x 6 = 144 hr
In the Routing : Required split and no of split is = 6 .
base qty = 200 , setup = 60 , machine = 210 , labor = 105 min
Formulas used in work center scheduling tab :
setup: SAP001 that is setup parameter only .
processing : SAP002 that is
machine * Operation quantity / Base quantity / Operation splits.
when in routing i am carrying out FRWD scheduling for start date 15.06.2008 and lot size 1200 (multiple of base qty ) scheduling earliest start time is: 07:00:00 and 2400 is also 07:00:00 (start time in work center capacity header tab ) BUt for 3600 qty it is : 20:00:00
and for lot size 4800 it is 16:00:00 date is not the issue but the earliest start time is issue here , what ever qty is it why it is not starting at 07:00:00 ??
Regards..
Edited by: venky shree on Feb 20, 2008 6:52 AM
Edited by: venky shree on Feb 20, 2008 7:39 AM

Hi,
This is because you might have assigned Reduction startegy
either to the operation or in the order type dependent parameters.
If the lot size is higher your Production dates may go outside
the basic dates.
In such case the system tries to reduce the lead time based on the setting defined in the OPU3and OPU5.
That is why your earliest time is 20:00 in the case of qty 3600
For further clarifications you can go thru topics Reduction strategy.
Regards,
nandha

Change in scheduling agreement schedule lines .

Dear All ,
        We have activated release strategy for scheduling agreement .Previously while maintaining schedule lines it was not going for release .
         But now while maintaining schedule lines in ME38 it is going for release .I want to know what is the reason and I want to stop this .
         We have made some changes in Closed PO amendment ,like we have changed the release indicator value R -6- 10% to R - 6 -0% .
Like whenever we make change in price of a PO even a 1paise
it should go for release .
          The release strategy for SA and PO is same .

Hi,
Since you have changed the release indicator it is again going for release for any change.
Please change the release indicator to 2 from 6 so that you can change the schdeule lines or any modiifcation again release will not set
Please check the release indicator in P.O and SA
G.Ganesh Kuamr

Reduction strategy in scheduling

Similar Messages

Maybe you are looking for