on 05-13-2011 12:31 PM
Hello experts,
First of all I was confused whether this question should be posted in this forum or it should be for ECC forum. But I thought since I am from APO and Preqs are created in APO, I will be better to put this question here.
Here is the case.
We are generating Purchase Requisition in APO and CIF this Preq to ECC, Planned Delivery Time is calculated in Preq and accordingly requirement date is calculated. But we are observing some issue in Planned Delivery Time calculation.
Our understanding was
Planned Delivery Time is equal to GOODS ISSUE time in APO + Transportation Duration in Means of Transport in APO
But what we are observing are Planned Delivery time = Goods Issue + Transportation duration + 1
Yes we are concern about this "+1" days. Not sure whre is this additional one day is coming from.
We tried multiple option and in every case, where we are using GI time, one additional day is getting added to Planned Delivery Time. If we do not use GI time then Planned Delivery Time = Transportation Duration in Means of Transport, which is perfectly fine.
So question is, when using GI time, why one extra day is getting added. Because of this requirement date at supplying plant in ECC is not matching with requirement date in APO.
Any hint, pointer, input is all welcome.
Thanks
Pavan Sarda
Hello Pavan,
the similar issue i am facing. did you get any resolution of this issue.
please share if any.
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
removed because posted twice.
Regards,
Nitin Thatte
Edited by: Nitin Thatte on May 13, 2011 6:38 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
According to me, the planned delivery time of PR is picked up by the system from PIR or scheduling agreement. If you have CIFed these to create T-Lanes, this Planned delivery time will appear in the T lane.
So total time = Planned delivery time + GR processing time
Just check this.
Regards,
Nitin Thatte
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Pavan,
There are a number of issues that can cause general date mismatches between APO and ECC. There are even more issues that are specific to the integration of purchase docs.
Read the online help about date comparisons between R/3 and APO
http://help.sap.com/saphelp_scm70/helpdata/EN/98/763442d692ac04e10000000a1550b0/frameset.htm
There are also a bunch of OSS notes on the subject. Start with
https://service.sap.com/sap/support/notes/333386
For STOs/STPrqs
https://service.sap.com/sap/support/notes/1342195
https://service.sap.com/sap/support/notes/361308
and many more.
Best Regards,
DB49
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
8 | |
4 | |
3 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.