Question:
I am getting different dates on the production orders between APO PPDS and R3. The strategy profile is correct (according to note 423626), and I am now considering the automatic back update (/SAPAPO/CP3).
Has anybody got any advice when using this please? does it really affect performance, is it best to set for all transfers or just delta?
Answer:
I have seen where the dates don't match on md04 in r3 and apo product master. this was caused by r3 adding the recieving time to the end of the order and apo did not.
also planned orders can be off in time of day becuase r3 only considers them on a day or 00:00 and apo may have an actual time.
and time zones can cause problems.
George
Answer:
I am getting different dates on the production orders between APO PPDS and R3. The strategy profile is correct (according to note 423626), and I am now considering the automatic back update (/SAPAPO/CP3).
Has anybody got any advice when using this please? does it really affect performance, is it best to set for all transfers or just delta?
You may have also problems when due to different calendars used for planning in APO and in R/3.
Of course, R/3 and APO may show data in different time zones (system, location, user....). good luck
Answer:
R/3 will re-schedule orders received from APO if there is no capacity available for the order during the times given by APO. This could be due to other materials being planned in R/3 and not in APO. This depends upon the strategy that you employ in R/3.
Also, make sure that you are not running MRP in R/3 with a scheduling key of 2 as this will re-schedule orders that have already been scheduled by APO. If this is the case you must exclude all APO planned materials from your MRP run.
Mark
Answer:
I'm agree with Mark.
This should be your problem.
Answer:
Check with the GR processing time parameter
Probably the GR times of R/3 and APO are getting added-up while CIFing
Cheers