TPVS upgrade from 5.0 to SCM 7.0

[former_member503200]

We are in the process of upgrading our TPVS from SCM 5.0 to SCM 7.0.  Due to limitations, we are not going for TM.

If you already did upgrade from SCM 5.0 to 7.0  would like to know issues you come across and any suggestions you can provide.

thanks

Jeff

[Former Member]

Hi Jeff,

I suppose upgrade is completed now. So may i ask you: Did you face any issues regarding transaction /sapapo/vs01, after setting a shipment from status C to status B, then unassigning a freight unit:  With the incorrect behaviour as a result, that unassigned freigh unit section is not automatically updated.

Means: the freight unit which was unassigned from the B shipment is not visible in unassigned freigh unit section (structure concered for ALV: VS_GRID_NZLF-OUTTAB, grid_nzlf ) until next refresh.

thanks in advance for any useful hint,

Arianna Aichwalder

[Former Member]

Our upgrade went fairly smoothly.  It appears that the "standard" SAP functions pretty much the same between 5 & 7. 

We have a lot of customizations and we use a lot of the constants that SAP defines.  During the upgrade they moved a lot of those to new includes and also created classes with Attributes for the constants.  This caused us a bit of work but the attributes is a much better solution for defining constants.

Our biggest issues wasn't really TPVS but they changed the way dynamic pegging works and this was a huge impact to our customizations in the Demand Scheduling area.

So in short - if your customizations are minimal - so should the upgrade impacts.

hope that Helps

Charles Ramey

[Former Member]

Dear Jeff,

we are now planning to upgrade as well, did you get any answer about your question?

Regards,

Itziar from Heineken Spain