Change Recording may sound familiar to those of you who are doing development in ABAP. Also when working with Java in the Developer Studio, changes are recorded in activities. But what about Portal content developers? Change Recording may sound like a dream. Looks like Portal content developers need a well-working brain – they have to remember the objects that they touched and then add them to a transport package if the changes should be moved to another system.
But how about this: changes are recorded while working with them and the only thing that you have to do after having finished your changes is to activate a changelist and release it to a transport request in CTS+.
Sounds like telling fairy tales? No. It’s reality. Starting with SAP NetWeaver 7.3, there is a new functionality called Change Recording. The picture below shows how it works.
Whenever a user (a Portal content developer) creates objects or changes them, the objects become part of a so-called changelist. When activating a changelist, an epa-file which contains all the objects that were collected in the changelist, is automatically created. And when releasing the changelist, the epa-file is attached to a transport request in CTS+. What else do you need? Well… someone who executes the import into the test or productive system in CTS 😉
And another thing which may sound like a fairy tale: deletions are recorded as well. So if you have to delete an object, there is no need any more to do the deletion on your development, test and productive system. Simply record the deletion and transport it by the help of CTS+.
Note that Change Recording is available for Portal content only. KM is not supported.
Curious to learn more?
A video shows Change Recordin in use (turn on your speakers)
Take a look at the SAP Help Portal at http://help.sap.com/saphelp_nw73/helpdata/en/4d/5dc9eeba4741e8890670e4e418801a/frameset.htm
A guide providing more information on configuring and using Change Recording is available on SDN.