Solution : https://service.sap.com/sap/support/notes/379006 (SAP Service marketplace login required)
Summary :
This SAP Note addresses discrepancies in requirement dates for stock transfers and subcontracting components between APO and R/3 systems. In R/3, scheduled requirement dates are calculated using the planned delivery time, corresponding to vendor delivery commitments and excluding non-working days. However, APO system utilizes transport durations from transportation lanes, and calculations are based on working days, which may result in mismatched dates. To align both systems, users can maintain the transport duration in APO to correspond with R/3's planned delivery time using the /SAPAPO/PWB_SOS BADI, which allows substitution of transport duration with planned delivery time in both SNP and PPDS scheduling. This approach ensures consistent requirement dates across systems, even with different operational calendars.
Key words :
sap standards - business add ins, supplying plant-dependent transport duration, basis - abap workbench - changing, delivery date - planned delivery time, planned delivery time based, identical planned delivery time, transport duration solution maintain, date +planned delivery time, planned delivery time, terms /sapapo/rrp3
Related Notes :
1342195 | Stock transfers in purchasing: Scheduling in APO |
913804 | Requirements date on a non-working time |
722227 | BAdI: Ignore planned delivery time |
624982 | Incorrect dates for RBA controlled stock transfer |
565972 | FAQ: External procurement in PP/DS |
541092 | BADI: /SAPAPO/DM_PO_OPENING_DATE2 |
441622 | Supplying-plant-dependent planned del. time/trans. time |
426563 | CTP: Settings, system behavior and performance (docu) |
420648 | Scheduling of stock transfers and VMI orders |
393570 | BADI: Source determination for actual order |
361308 | Stock transf.releases:Scheduling via plnd dely time |
333386 | Availability date different in APO and R/3 |