SNP: Planned Delivery Time vs Transportation Time in SNP heuristics

[thomas_schulze2]

Hello experts,

I have a simple SNP heuristic scenario where I would like tom overcome an scheduling issue with stock transfer requisitions.

Example & Master data:

LocA --> is the central DC in Germany which is feeding the regional DC in the U.S,

LocB --> regional DC in the U.S. which is being replenished by LocA

TranspLane from LocA (Germany) -> LocB (US) has 25 days transport time without a calendar (ocean shipment).

Product "ABC" in LocB (US) has PlannedDeliveryTime of 30 days. These 30 days are meant to cover for 25 days transport (ocean) and another 5 days processing in the central DC LocA (Germany).

Issue:

running an SNP location heuristic creates a PurchReq (StockTransferRequisition) from LocB to LocA. But ... now APO takes the 30 days PlndDeliveryTime in LocB against the ProductionCalendar of the SourceLocation ("PP" calender of LocA in Germany) ... which at the end translates in SNP to a leadtime for the PurchReq of ~ 47 days (since the ProdCalendar has weekends as non-working days). This makes no sense since a major portion of the PlndDeliveryTime is for an ocean shipment where the ship doesn't stop on the water just because of weekends.

Any idea how to model / overcome this ? Boundary conditon I have is that I can't change / remove the production calendar of the SourceLocation LocA in APO and I want to avoid setting the PlndDeliveryTime of Product ABC in LocB in R3 Material Master down to artifically 20 days in order to achieve 30 days lead time in APO at the end (which is more a guess than a concious lead time).

Best Regards

Thomas Schulze

Edited by: Thomas Schulze on Jun 1, 2010 12:57 PM

[Former Member · Accepted solution]

Thomas,

PDT is calculated as 7Days/Week. Also Transportation Duration is sued to calculate Start Data whereas the PDT comes into picture for opening date.

Difference b/w End date and Delivery Date = GR Processing Time based on Calendar of Handling Resource

Difference b/w Delivery Date and Start Date = Transportation Duration based on calendar of transportation resource

Difference b/w Delivery Date and Opening date = PDT (7Days/Week) + Opening Period

Match it to this and check again

Abhi

[Former Member]

Dear Thomas,

Try using a calender without holidays and weekends and assign it to the transportation lane.

If you are using the routes/transit in time in ECC then you have to maintain the Trans in APO thru the transaction code /SAPCND/AU11 - Create Scheduling Step

Regards,

Srinivas.S

[thomas_schulze2]

Dear Srinivas,

thanks for the hints.

>> Please make a calender without holidays and weekends and assign it to the transportation lane.<<

We have no calendar assigned in TLane which has same effect (25 Days Duration = 25 CalendarDays). Thats APO Standard --> no calendar in TLane means the transport duration is in CalendarDays.

>> If you are using the routes/transit in time in ECC then you have to maintain the Trans in APO thru the transaction code /SAPCND/AU11 - Create Scheduling Step<<

We do not use GATP for this process - I'm looking for a way to schedule SNP PurchReqs correctly. I think /SAPCND/AU11 is more for GATP Scheduling Conditons but not for SNP Scheduling of PREQs.

Regards

Thomas

[Former Member]

Thomas,

from the looks of it the possible 'woprkaround' is to remove the PDT and include a GR processing time. The flipside being that ECC and APO will be out of sync as you cannot remove the PDT from ECC. Ideally the usage of PDT in ECC and APO is similar and the values are so asisgned to bring about a consistency between PAO and ECC. Nevertheless if you are using a GR time please make sure to have a look at the calendar assigned to the Handling Resource at the receiving location as that will decide how those 5 days are used.

Abhi

[thomas_schulze2]

Hi Abhi,

>>from the looks of it the possible 'woprkaround' is to remove the PDT and include a GR processing time. The flipside being that ECC and APO will be out of sync as you cannot remove the PDT from ECC. Ideally the usage of PDT in ECC and APO is similar and the values are so asisgned to bring about a consistency between PAO and ECC.<<

PDT in ECC is in CalendarDays and in APO in WorkingDays of the SourceLoc's ProductionCalendar - thats a fundamental difference which cannot truly be synched between ECC and APO. I believe you need to decide if you plan procurement / replenishement in ECC OR APO for this part into the target location. If you do this on both sides (which does not make sense) then you are right - there is a synching issue.

>>Nevertheless if you are using a GR time please make sure to have a look at the calendar assigned to the Handling Resource at the receiving location as that will decide how those 5 days are used.<<

I'll use a GI time in the SourceLoc (oubound processing time) and not GR Time in the Target location (already used)... the 5 days needed in my example are meant for the outbound warehouse processing in the SourceLocation LocA. Since I have no handling resource modeled I believe the GI-Time in LocA will be calculated using the ShippingCalendar in the APO Location Master. That should make it.

Thanks!

Regards

Thomas

Edited by: Thomas Schulze on Jun 2, 2010 1:24 PM

[Former Member]

Dear Thomas,

Please make a calender without holidays and weekends and assign it to the transportation lane.

If you are using the routes/transit in time in ECC then you have to maintain the Trans in APO thru the transaction code /SAPCND/AU11 - Create Scheduling Step

Regards,

Srinivas.S

[Former Member]

Hi Thomas,

This is to elaborate on Vaibhav's point.

You keep planned delivery lead time for the location-product where the product procurement at your source location is from external network and you have less visibiity on that. So, do not set planned delivery lead time at regional DC because it is fed by a central DC, which is inside your network.

Once you are inside your network, you have a fair visiblity of your supply chain and hence you keep transportation time in transport lane and GR / GI time at your respective product-location, as these are the settings which are set when the supply chain parameters are not guess, but a more correct measure.

So, as Vaibhav said, simply keep transportation time as 25 days, GR time at regional DC as 5 days and remove planned delivery time, as the field is not relevant for this use. This setting will not consider your production calendar. But make sure that your shipping calendar and receiving calendars are of 7 days/week.

regards,

biplab

[thomas_schulze2]

Hello,

tks for the detailed responses !

I'll use and test the following changes as recommended:

(1) on the Regional DC side (LocB - US) remove PDT in APO Locationproduct Master (I can't remove it in R3 since SD-ATPcheck is using it)

(2) on the Central DC (LocA - Germany) introduce a GIPRT (Goods Issue Processing Time) in APO Locationproduct Master

of 5 days to model the processing time for Pick/Pack etc.

Regards

Thomas

[Former Member]

Hi Thomas,

Remove planned delivery time. Keep transportation time as 25 days and add GR time of 5 days at DC in US.

Best regards,

Vaibhav