I agree with Suresh. Some functionality could be backported (for example, context sensitive authorizations, which was added in 4.7) but you'd have to pay SAP development to make each change. And SAP development is so busy working on the next release, they don't have time to figure out how to meld it with a 4.6 release. Even if it could be backported, the customer would still have to configure it/test it/etc. It would probably take more time to go this route than to wait for the release!
And some functionality (such as MBOs, Comp, LSO or E- recruiting) would definitely not be available as they are completely rewritten modules or brand new functionality. SAP doesn't have the developers to support that kind of backporting.
Another thought: In the case of LSO, for example, the customer could set up an ALE scenario between a higher release with the functions they need and keep their master data on the 4.6C system. However, that seems like a lot of work for little return. Depending on the scope of what they need from a higher release, they'd probably still be working on the ALE implementation when ERP2007 is available.
Probably the best thing you can do for your customer is review their pain points, see if you can alleviate any of them now (I bet you can - it's amazing how much stuff is implemented incorrectly) and counsel patience.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.