on 08-29-2009 1:01 AM
Hi Friends,
We are facing one problem regarding production order date mish match between R3 and APO systems specific to a product.
The product is planned in PPDS and the order automatically transfer to R3 through online CIF.
PPM has got two operations 0010 and 0020 and activity relationships are like this:
P(0010) - P(0020) Start - Start relation ship
S(0010) - P(0010) End - Start relationship.
In PPDS dates are shown as :
on operation 0010 the start/end dates are shown as 08.15.09 to 08.22.09
on operation 0020 the start/end dates are shown as 08.15.09 to 08.22.09
Overall order start date is 08.15.09
Overall order finish date is 08.22.09
and in R3 dates are shown as:
on operation 0010 the start/end date are shown as 08.15.09 to 08.22.09
on operation 0020 the start/end dates are shown as 08.22.09 to 08.29.09
Overall order start date is 08.15.09
Overall order finish date is 08.29.09
The order is off one week (APO vs R3) with start and finish dates.
if we change DS Board settings to ignore internal relationships manually then the dates are matching exactly in APO and R3.
We want the production order dates to be matched without manual intervention.
Could some one please provide some hints on what is happening here and how to correct it.
Thanks.
Krish
Hi Krish,
Please check the Publication Settings on R/3 and APO side. In R/3 side please remove the plant from the Distribution Fuction in Publication (SPRO) for In House Production for the related Plant. On APO side maintain "Maintain Object-Specific Settings" for In House Production Settings as No Retransfer.
Try this and let me know if it helps resolve the issue.
Thanks,
Harsh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Krish,
1) Check SAP notes 423626 and 394113
2) Check your settings in /SAPAPO/CP3
Regards,
R. Senthil Mareeswaran.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
If both operation start at same time in R/3 it is represented by parallel sequences. I mean when you CIF Production version with this routing from R/3 to APO you will represent these activites by start start relationship.
Probable reson in difference in dates can be as follows-:
R/3 Routing and APO PPM are not in sink. There is no parralel sequence maintained in R/3 but there is start start relationship for activity in APO.
Kindly check and revert if reason is not this.
Regards,
Siddharth
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Friends,
Thanks a lot for your valuable replies in this regard.
Actually this problem is in production environment and it took some time to test the problem with the master data modifications
you suggested.
As DB and Siddhrath mentioned, the problem was with routing definition. There is no parallel sequence maintained in the routing but there is start-start relation maintained in APO PPM.
We corrected the routing definition and checked the order dates. Now the dates are matching in R3 and APO.
I am awarding DB and Siddharth each five points in this regard.
Once again thank you all for your time and valuable replies.
-Regards
Krish.
Krish,
I will assume that you have already checked and discarded the idea that someone has made manual changes to the order in R/3.
It sounds like you are allowing R/3 to continue to schedule the orders, and that the metthods used by R/3 are different from the methods used by APO. R/3 looks as if the routing is set up to have op 20 setup begin after the conclusion of op 10 production, yet in yr PPM you have 10/20P with 'start to start'. Decide which is correct, and then change the other.
Alternatively, turn off all scheduling in R/3, and let PPDS be the 'master'
Rgds,
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 |
---|---|
7 | |
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.