Availability Date calculation in SNP Heuristics

Dear Experts,
I am using weekly bucket profile. In the SNP PPM, period factor is set as 0. Lets say I create a PIR on date 09.11.2010 which is Tuesday.
If I run Location Heuristics, it should schedule the Planned Order on 08.11.2010 12:00. But system is scheduling it on 11.11.2010 23:59:59 i.e. Thrusday. No matter on which day I create the PIR, it somehow always schedules it on Thrusday. Please help to understand how it is happening.
(Though it should not matter here but Location-Product data also has period factor as 0)
Regards
Rinju
Edited by: Rinju Mukherjee on Sep 27, 2010 7:38 PM

Hello Micky and Amol,
Thanks for your response. It seems F1 help for field 'Period factor' is not correct. Anyway, if system is taking 0.5, I have further two questions:
Then it should be scheduled in the middle i.e. Monday + 2.5 = Wednesday. Why is it scheduling on Thrusday.
(ii) In SNP Heuristics, period factor only caculate the date. It sets by-default Time as 12:00, but here system is setting 23:59:59, why?
Thanks a lot in advance.
Regards
Rinju

Similar Messages

Lead Time Calculation in SNP Heuristics

Dear All,
Please let me know how the lead times are determined in SNP heuristics?
Ex: Distribution Center to Production Plant and
Production Plant to Supplier.
Thx,
Ram.

Hi,
Please check the below link for help: [Scheduling|http://help.sap.com/saphelp_scm70/helpdata/EN/05/f8923945b12c4de10000000a114084/frameset.htm]
Best Regards,
Ada

SNP planned order availability date difference between APO and ECC

Hi,
I have observed that SNP Planned order availability date is not matching between APO and ECC. Details are as follows.
I ran SNP Optimizer with bucket offset of 0.5. After publishing the optimizer created planned orders to ECC, only start date is matching.
Example:
I am using PDS as a source of supply.
Fixed production activity in SNP PDS is 1 day.
GR processing time: 3 day
After running optimizer planned order is created with dates explained below.
Start date/time: 09.05.2011 00:00:00
End date/time: 12.05.2011 23:59:59
Availability date: 16.05.2011 00:00:00
Because of bucket offset defined as 0.5 optimizer planned order availability is start of next monday.
After publishing this planned order to ECC dates on the planned order is as follows.
Start date: 09.05.2011
End date: 09.05.2011
Availability date: 12.05.2011
I have not maintained any scheduling margin key in ECC. Also if I dont define the GR processing time, planned dates between APO and ECC always match. Can anyone explain the impact of GR time on the availability date.
Regards,
Venkat

Hi Venkadesh,
What's "state stamp"? Do you mean different time zone?
note : 645597 mentioned by Nandha is very helpful:
In standard, CCR will use duedate - "the available date of the output product".
Nandha's words "In SAP APO, if the receipt date of the primary product deviates from the
end date of the last activity of the order, the receipt date
always identifies this as inconsistent. You cannot rectify
inconsistencies of this type by using CCR."
I guess in your PDS or PPM, the output product is not assigned to the End of the last activity. Someone changed it?
Please CIF the PDS or PPM again.
If you really want to apply a note, please use note 815509 as you're using planned order,
and system will use order end date in CCR instead.
GR time is always considered. BR/Tiemin

SNP heuristics and optimiser using transport lane validity dates

I am using APO SNP 5.1.
In particular I am trying to use the SNP heuristics and optimiser for supply planning.
Can anyone confirm whether transport lane validity dates are respected by (a) SNP heuristics and (b) SNP optimiser, ie no transport requisitions will be created during times when the transport lane is not 'open' in terms of validity dates.
Thanks for any advice on this...

Hi,
Irrespective of the SNP planning engine you are using, a t-lane will only be considered if the t-lane is active as per the validity dates.
Regards,
Umesh

Reorder Point Planning via SNP heuristics based on ACTUAL stock

Hi All,
In R/3 there is the option in reorder point planning to take into account external requirements (MRP type V1) or not to take into account external requirements (VB). When using reorder point planning in APO SNP Heuristics, the reorder point is being determined in time based on the PROJECTED stock (so taking into account external requirements) so the result is the same as in R/3 when using MRP type V1. In the future horizon, everytime the projected stock goes below the reorder point, a replenishment is triggerd via a planned order or purchase requisition.
I would like to know if (and how) it is possible to perform reorder point planning in APO SNP via heuristics (can be location or network) only taking into account the ACTUAL stock (and no external requirements in the past or in the future). So, the same behavior as the MRP type VB in R/3. The difference is that only on the short term, 1 time replenishment is triggered (via planned order or purchase requisition) if the current stock is below the reorder point.
Remarks: this needs to be able to be set product specific, because not all products at the location will need to use this logic.
Any help or thoughts for a solution direction (preferably without programming or user exits) are appreciated.
Thanks in advance,
Dennis

If you really just want a pure re-order point scenario based on current stock, I'd suppose that you'd want to create a new data view and modify the total demand macro so that it doesn't generate any sort of future requirements (total demand will essentially be zero). Then the reorder point will be the only thing driving planning when compared to the initial bucket SOH, which is presumably calculated through the standard macro and according to the stock cat. group you indicate in the location/product master.
You could set some specific filter in the material master using the MATLOC freely definable attributes to create selection profiles and govern in which data view you process the planning for certain materials. That is to say, you'd assign all materials which are pure current stock ROP and tag them with some attribute and use that to create selections for your Heuristic variants.

Schedule Line Delivery Date Calculation with Transportation Scheduling

Hi All,
We are currently running into a problem where our Sales Order Schedule Line delivery dates are being pushed out too far into the future - because of the Calendar being used to determine the transit time.
We have 'Delivery Scheduling' and 'Transportation Scheduling' activated for our Sales Document type
We have Routes that are configured with a 'Transit Time' and a 'Factory Calendar'
Order Scenario:
'Factory Calendar' assigned to our 'Route' is setup with only one 'Workday' in a given week e.g. Wednesday
Our 'Route' has a Transit Time of 2 days
We create a Sales Order on Monday for a Material that is available in our Plant
The 'Goods Issue' date is being determined correctly for the next Workday - being Wednesday
The 'Delivery Date' is extending out over 15 days (2 Wednesdays into the future) - since it is working on 'Calendar Days' and not 'Actual Days'
Does anyone know of a way (config or other) to only influence the 'Goods Issue' date with the 'Factory Calendar' assigned to the Route, and have the 'Delivery Date' calculated using the Transit Time on the Route and 'Actual Days' rather than Calendar days?
All help greatly appreciated.
Thanks,
Ravelle<i></i>

Hi Pathik,
Thanks for your reply. I have already maintained the Calendars I'm using for this business process in <SCAL> - same as <OY05>.
The problem I'm having though is that by assigning a Calendar directly to my route (which I doing to influence the goods issue date - using a 1 Working Day Calendar) it is also taking precedence in determining the Transit time - which in this case I don't want, as I want my Transit time to be determined using a 5 Working Day Calendar.
I don't think this problem has a config option as a work around...I think the only possibility in this case is a development to achieve the results we need.
Thanks,
Ravelle

Material Availability date differs in R/3 & APO

Hi,
We are facing Issue with Material Avaialbility date for Planner order/Manufacturing Order in R/3 and APO.
We are using a Master Recipe for PDS Creation in APO which consists on 9-10 different operations, out of which only inbetween operation 4-5-6 is scheduled in APO.
So in APO Other Operations are not availble in PDS and hence not considered for scheduling as required. Also GR Processing Time is maintained on Product Master for which infinite Capcity Handling resource in created in APO.
When we schedule Operations in APO, the Scheduled dates for Operation 4-5-6 is sent back to R/3 and for other Operations based on relationship maintained takes addistional 1-2 Days.
In R/3 Availability Date for Planner Order/Manufacturing Order is calculating by adding a GR time after Operation 10 end time, while in APO as ony operation 4-5-6 is available a GR time is added after Operation 6, which is resulting in Differnet availability date for Order in R/3 and APO.
Kindly suggets a way to same date in R/3 and APO, if anyone has faced same Issue.
Thanks for your Help !!!

Hi Senthil,
I completly understand, that APO Material Availability date is GR end Date while in R/3 its a Process Order end date.
But Problem is not that.
Problem is not all operation of Process order are in APO, so assume u have 5 operations in Process order out of which only first 3 are relevant for schedulilng in APO. So APO schedules these 3 Operation and adds the GR time to Show the avaiablity date.
While in R/3 GR Time is added after end of Operation 5 which is right, so GR end date in R/3 and APO dont match.
Let me know if you think some more on this...!!!
Thanks and Appreciated !!!

How is delivery date calculated

How can anyone please explain how delivery date is calculated using forward and backward scheduling
I want to have it broken down into the following steps
for eg for delivery date calculation following dates are used
Material Availabilty Date
Material Staging Date
Pick/pack time
Transportation PLanning date
Loading date
Goods issue date
Transit Date
Delivery Date
Can some one please give me an example and explain wht these dates are
for eg customer needs delivery date on 11/20/2008
how would the system cacluate whether it can meet the delivery date using backward scheduling
and if it doesnt meet how does the system do the forward scheduling
also i am not clear with the following dates
material avaialibilty date
material staging date
transportation date
can some one please explain me all this in detail
Also i have another question at the sales order creation when is shipping point and route determined
coz based on the ATP check only material avaialabilty date is determined and if we have a bacjground job running every 1 hours for atp then immediately when we create a sales order is a route and shipping point determined (just before we save the sales order)
Let me be more clear
Suppose customer representative recevies a order on the phone
he enters sold to party, ship to party ,PO number,delivery date and material number and then hits enter
so at tht time the shipping point and route is determined ?
also when an atp check runs and if the delivery date is not met then the system will propose a new delivery date but if we have a different route configured say for eg overnight so we can meet the delivery date and we want to change this route to overnight what must we do?
should we change the shipping condition in the header?
I am not very sure about the process can you please also explain me this in detail?
Thanks

Hi there,
When a sales order is logged & the user enters the requested delivery date, system 1st does the backward scheduling date. Pla note that the factory calender mentioned in the shipping point & route plays a crutial role in defining the working days & confirmed delivery date.
For eg: Customer has raised an order on 11/15 & requests delivery on 11/20/2008.
the following times are important in delivery scheduling.
Transit time: maintained in route
Loading time maintained in the shipping point
Transportation planing time maintained in the transportation planning point.
pick pack time maintained in the shipping point.
Material availability time maintained in MM02 --> MRP screens. This is the time that the material can be manufactured (for inhouse producted items) or external processing time (for externallly procured materials like TAS items).
From the requested delivery date 11/20 system does the backward scheduling & determines the following dates:
Goods issue date, loading date, pick pack date, transportation planning date & material availability date.
Time between:
goods issue date - reqested delivery date: transit time
Goods issue date - loading date: loading time
transportation planning date - pick pack date: picking pack time
Material availability date - transportation date: transportation planning time.
Consider that the factory calender has all days of the week as working dates (to make it simple to explain). Also transit time is 3 days, loading time is 1 day,pick pack time is 1 day, material availability time is 3 days.
From 11/20 ussing backward scheduling system determines the following dates:
Goods issue date: 11/17
Loading date: 11/16
Pick pack date: 11/15
System will check if material is available on the 11/15 to start pick / pack. If it is available then system will confirm the reqested delivery date. Else it will check when the material is available. For eg basing on the MRP settings mnaterial is available only on 11/18. So from 18th system does forward scheduling & redetermines all the dates. So pick / pack date is 11/18. Loading date is 11/19, goods issue date is 11/20 & possible delivery date is 11/23. So system will confirm the delivery date on 11/23. This is when complete delivery is required. If partial delivery is allowed, then system will check how much quantity is available on 11/15. Accordingly it will give 2 delivery dates.
In the above example include teh factory calender which will have 5 day week with Fri & Sat as holidays. Accordingly dates will change.
Here replenishment lead time also plays an imp role. Pls refer http://help.sap.com/erp2005_ehp_03/helpdata/EN/6b/2785347860ea35e10000009b38f83b/frameset.htm for further information
Regards,
Sivanand

Material Availability Date

HI ALL,
I have a client..
She requested to configure a route for two new customer..
I configured the new route: R1, it has 22 calendar days transit time, and 3 working days transportation Lead time.
Then she create an Export Order on 12/01.
Indicating the Required Delivery Date of 12/30.
Then Automatically the:
Material Availability DAte defaulted to 12/8;
Goods issue date 12/8;
Loading Date 12/8;
Transportation Planning Date 12/3.
1. Am I right in saying that the computation for the Material Availability date for the above example is based on the indicated Required Delivery Date which is 12/30? Is it 12/30 - 22 days (transit time) = 12/08 MAD? Considering also that the material will have a stock that time (based on Planned orders)?
2. And then regarding the transportation Planning date, am I right in saying that it was computed 3 working days from MAD 12/8? (weekend 12/6 and 12/7)
3. How can I possibly configure the Material Availability Date to be 25 days from the Required Delivery Date without any impact to Transit time of 22 days? Is there any other way? Its like 22 days - Transit time and 3 days for material preparations?
I'll appreciate any prompt response. Thanks!
-Jisley-

Hi there,
1) Transportation lead time TLT is the time that is required by the transport planning point to finalise & prepare for the tramsport (like finailise the carrier, route, costs etc).
So the TLT is 3 days from the order load date. The system need not wait till the MAD & then calculate MAD + 3 days for transportation planning time. Even tough material is available or not TLT is 3 days from order date.
2) When you mean 3 days, it need not necessarily mean 3 working days. Check the factory calender assigned to the route & the shipping point. Check what are definied as working days / holidays. System will calculate accordingly. If Sat & Sun are holidays in the factory calender, then it would take 3 working days. Else it is 3 calender days weekends not included.
3) MAD is calculated by the time mantained in MM02 -> MRP 2 screen. You will maintain the inhouse processing time for finished goods (internallly produced goods) & planned delivery time / GR processing time for trading goods (externally procured goods). If you are aware, MAD is calculated through backward scheduling from the requested delivery date RDD. From the RDD, system will go backwards & propose GI date, loading date, pick pack date basing on the times maintaind in shipping points & routes. Goods should be available on the pick pack date. Else it will check the new MAD (basing on MRP 2 values in MM02) & then carriers forward scheduling to propose a new confirmed delivery date. If you want to have MAD of 25 days, then maintain 25 in MM02 --> MRP 2 values & check it.
Regards,
Sivanand

Material availability Date - User Exit

Dear All,
Can any one help me in finding out User Exit to change Material Availability date in VA01, which system propose automatically.
The Problem is I need to assign Mat aval. date as say SY_DATUM + 60. Then system should take this date for ATP calculation(for eg: Loading date,Goods issue date,Transport.plan.date) and finally it should propose Delivery date.
It would be great helpfull for me if any one help me in this issue ASAP.
Advance Thanks for your help
With Regards
K.Babu

Hi,
Try using USEREXIT_AVAILABILITY_IN(RV03VFZZ) or USEREXIT_ADD_FIELD_TO_LINE(FV45VFZZ) exits in SD. Due to various combinations possible (for example if you use route-scheduling it may behave differently than otherwise), it may not be possible to apply a common logic.
I would suggest using USEREXIT_ADD_FIELD_TO_LINE to modify the date fields in the structure MVERF (field EDATU : Delivery date, MBDAT : Material avail. date and so on). At this point, system has already calculated the first set of dates based on customer requested delivery date, so you will need to do adjustments in all fields accordingly.
Eg in this exit:
w_date = sy-datum + 60.
offset = w_date - mverf-mbdat.
mverf-mbdat = mverf-mbdat + offset.
mverf-lddat = mverf-lddat + offset.
mverf-edatu = mverf-edatu + offset.
Please note it will need some adjustments if you have a shipping calendar (eg sundays off..) in which case the offset may be a little different for EDATU.
cheers,

Enable "dynamic date calculation" variable type

When saving reporting date/period in a report variant, we may use "dynamic date calculation" to specific date as selection parameter. But the "Dynamic date calculation" is not visible in some ABAP reports - only "Table Variable from TVARVC" type is available for selection.
For those reports that are missing that variable type, how can we enable the "Dynamic date calculation" variable type to be visible?

Hi Paco:
Yes, they are z-reports, both have the same almost everything, created by the same ABAPer, for the same application SD, just grouping the data differently.
It seems a screen (#100?) is missing, In the old version, it's screen 100 where to activate the "D" and "B" variable types. Now it goes to screen 281.
Stacy

Material available date in cross-company business

Hello guys,
I encountered a question in <b>cross-company business</b>.
1. create PO with ME21N;
2. create outbound delivery against PO with VL10B.
I found material available date in outbound delivery is always the same as delivery date in PO. why? by my understanding, material available date should got base on ATP.
could you give me any suggestion?

I assume that you manually created the PO. If so, then you are right in your observation.
When PO's are created as a result of a planning run , then the MAD calculation takes ATP into account

How are APO/R3 dates calculated

Hi All,
In APO, for a PO, we have ' Requirement date', 'Availability date' and in R3, we have reqmnt/rect date and delivery date.
How are these dates calculated from a reference?
My understanding- System takes the requirement date( date on which there is a reqmnt for the material), subtracts a time equal to GR+GI time and arrives at Availability date. the same Availability date is transferred to R3 as 'Reqmnt/Rect date'. But how is the delivery date in R3 calculated?
suppose I have a requirement date in APO, what are the details that I need to calculate successive dates?
Regards
Manotosh

Hi,
I have one confusion pls. clarify.
Requirement date=Date of demand on which material is required.
Delivery date= Date of demand- planned delivery time /transportation duration
Availability date= Delivery date+GR process time.
In product veiw in APO you will see as availability date and receipt date.
For more information follow the link
http://help.sap.com/saphelp_scm50/helpdata/en/cd/6dec39554c7f58e10000000a11402f/frameset.htm
Santosh

Reg: Material Availability Date

Dear All,
I find difficult to understand the logic behing arriving Material Availability Date.
It is not a basic question. Because I know the Availability check process and Backward scheduling process. But I am not able to understand the link between the process to arrive Material Availability Date.
Availability chek is carried with Checking group + Checking rule combination. With that we can conclude the Available quantity to promise the Customer.
But how does the Backward scheduling or Forward scheduling comes into the picture. How does the Backward or Forward scheduling getting triggered? Is it part of Availability check?
Because the quantities are confirmed by Availability check and the dates are confirmed by Backward or Forward scheduling. How does the systems synchronizes the quantity and date? Could you please explain.
I am not able to understand how does the Material confirmed on particular date and how does the Availability check helping to fix it?
Kindly explain.
Regards,
Raja Durai

     1. Basic doubt; I could see a graph with Inward and Outward movements in the given link, is it
         populated based on the movements in CO09?
Yes, the inwards & outward movements that are considered in the ATP check are displayed in CO09. Transaction OVZ9 determines which inward & outward movements are included.
     2. What is the base date for RLT? Is it calculated from Order date or Requested delivery date?
As per response from Phanikumar, check the F1 help of the field in CO09. This is the best explanation available for RLT.
     3. Is forward scheduling considered if we have RLT active?
Yes. RLT is only relevant if there is no available quantity so forward scheduling can be used.
     4. While system does the Backward scheduling, there are possibilites, system can derive the
         Material availability date in the past, Is Availability check can happen on past days?
Yes, this depends on the customising in OVLY mentioned by G. Lakshmipathi.
Take the following example:
Requested delivery date = today (17th) February
There is a route with 5 days transit time.
RDD (27th) - 5 days transit = GI date of 22nd February.
This is a date in the past. If OVLY allows dates in the past, then 22nd will be accepted. If OVLY does not allow dates in the past, then a forwards scheduling must be executed. This will take todays date as requested material availability date and forwards schedule. 22nd + 5 days = delivery date of 4th March.

Late Demand Fulfillment with SNP Heuristics

Hello all,
It is well known that SNP Heuristics does a bucket level planning and demands in each bucket are treated independent of the future bucket demands while creating the receipt elements. The receipts are created within the bucket unless there are sufficient receipts available in the past buckets that can be used.
Now, my question is, if we can force Heuristics to have the receipts in future buckets consumed with current bucket demand and not have to create additional receipts within the current bucket during planning run.
In a nut shell, can we influence heuristics not to plan receipts if there are fixed receipts available in future buckets?
Please note that settings like fixed pegging, maximum lateness of receipt, and late demand fulfillment do not work for heuristics. I have tested extensively using all of these settings.
Is there a way we can influence it to look into the future and if there are receipts available in any future bucket, say 30 days or 4 buckets ahead, in a weekly planning situation, it should not plan receipts in the current bucket and consume the receipts of future.
If any one has done such a thing earlier and can provide pointers, that will be grateful.
One option that came through discussions is changing standard macros to influence the way receipts are seen by heuristics during bucketed planning. Has someone explored this option? Please revert.
Thanks and warm regards,
Chandra

Hi Dieter,
Please check if the plan order is tied to your SO (t.code /SAPAPO/CTMVIEWER or in the /SAPAPO/RRP3). Also check in CTM profile (tab Supplies) what is your settings in the supply control section (Build Up Safety Stock and Stock is available). They should be active.
In the Planning Strategy tab what is the scheduling direction and pegging type?
Also check the Planning Strategy (planning mode & delete mode).
Thanks, Marius

Availability Date calculation in SNP Heuristics

Similar Messages

Maybe you are looking for