Back dated PReqs created in ECC

[Former Member]

Hi Experts,

We have a situation where in the the PReqs in ECC are calculated in

past.

We have an example where by there was a requirement at C079 on 24th

February. There is GR Processing time of 5 days maintained at C079 and

transport duration of 24 minutes. After running deployment, a

Distribution Demand (Confirmed) was created on the source, C061 on 19th

February and a Distribution Receipt (Confirmed) was created on C079 for

24th Feb. This, we believe is as expected.

Now, in ECC we are able to see a PReq at C079 on 24th Feb, but the

corresponding PReq on C061 is showing on 2nd Feb in MD04. We need to

understand that as to why the PReq at C061 has been created in past.

Please note that there is a Planned Delivery Time of 17 days maintained

at C079. We understand that this should not cause any issue, but please

take a note of it.

Please advice. Thank you.

Regards,

Rishi

[former_member182502]

Dear Rishikesh,

It appears that the Purchase Info record in R3 and the Tlanes in APO are different. In APO the PR is picking the Tlane period but once its ciffed to R3 the PR time is recalculated . In standard if you have a Tlane in APO then the PDT is ignored or overwritten in APO.

The recalculation happens by fixing the availability date. Please ask your developer to debug if you have any exit or code which is influencing the behavior.

I would also suggest you to maintain the Transportation Duration in APO for atleast 1 day i.e. 24Hrs. The minimum bucket of planning in SNP is a day.

Thanks and Regards,

Gajanan Patki

[Former Member]

Hello,

For the benefits of the others consultants, please indicate the good or the helpful answer!

Thanks, Marius

[marianoc]

Hi,

I think you have a problem with the planned delivery time in ECC and the time from the transportation lane in APO.

Remove the planned delivery time in ECC, ensure it is also deleted in MAT1 and re-plan your code.

Also take a look of this thread:

And check these notes:

379006
- Transport duration and planned delivery time in APO and R/3

441622
- Supplying-plant-dependent planned del. time/trans. time

Kind Regards,

Mariano

[Former Member]

This certainly looks like a misalignment of one of the processing times between APO and ECC.

• Check the transportation zone assignment in ECC that defines the transportation time between the source and destination and compare that to the transportation time maintained in the APO transportation lane between the same source and destination
• Similarly compare the other processing times GR, GI, planned delivery etc. between ECC material master (MM03- MRP tabs) and the APO customer-location master ( /sapapo/mat1)

[Former Member]

Hi Rishi,

Why are you supposing that Planned.deliv.time (C079) doesn't have any influence on the delivery date at source location level (C061)?

Please see below (from SAP help).

Thanks, Marius

Planned Delivery Time in Days

Number of workdays required to acquire the product or service using external
procurement.

The system uses the supplier location's production calendar to determine the
planned delivery time. If a production calendar is not defined at the supplier
location, the system calculates the planned delivery time in calendar days.

Use

If you have various suppliers for a product, you have to specify an average
value. This also applies if you always order the product from the same supplier,
but the supplier's delivery times vary.

Use in Supply Network Planning (SNP)

The planned delivery time is used differently in heuristic-based
planning and optimization-based
planning:

• SNP heuristic: The system takes into account the planned delivery
  time with both types of external procurement; both when the source location is
  defined in the supply chain model and when it is not known. If you have also
  defined an SNP stock
  transfer horizon, the system uses the larger of the two
  horizons.
• SNP optimizer: The system only takes into account the planned
  delivery time if there is no source location for external procurement.

Use in Capable-to-Match (CTM)

The system only takes into account the planned delivery time if there is no
source location for external procurement.