Maintenance Strategy 

The duration of R/3 Plug-In maintenance depends on the maintenance of the corresponding R/3 release. If this R/3 release is no longer maintained, the corresponding Plug-In version is also no longer maintained. R/3 Plug-Ins will be completely maintained in six months maximum (R/3 Plug-In Support Packages and/or R/3 Plug-In CRTs). After six months, the maintenance is taken care of by a new release. You can continue to use older component releases, thanks to the backward compatibility of the R/3 Plug-In. For the previous R/3 Plug-In release, maintenance is restricted to notes, and these are removed after a further six months, after the new release. This means your R/3 Plug-Ins are always guaranteed to be completely maintained.

 

For the best possible maintenance, we recommend that you always use the most up-to-date version of the R/3 Plug-In. A Plug-In upgrade is usually available at the same time as a component upgrade. However, a component upgrade does not have to be carried out, because all R/3 Plug-Ins are backwards-compatible with previous component releases.

If Support Packages or Legal Change Packages are applied to a system in which a modified Plug-In is installed, the appropriate Conflict Resolution Transports (CRT) are required. From R/3 Plug-In release 2000.1, there will be modified shipments only for R/3 3.1l. In the course of developing plug-ins, it is impossible to avoid modifications to the Standard. These modifications are not delivered, but they must be included in a certain support package. Consequently, future Plug-In shipments require this special support package level. If you wish to have the most up-to-date Plug-In release, you require the appropriate support package level.

For further information see Support Package Strategy.

The requirement for an unmodified version of the R/3 Plug-In is only the minimum R/3 Support Package level.

 

For further information, see R/3 Plug-In.