Migration of business object data in parallel with productive business application usage

A non-transitory, computer-readable medium storing computer-readable instructions executable by a data processing apparatus to:

• during uptime processing:
• generate at least one shadow database table corresponding to a new business object (BO) persistency model;
• establish change recording for at least one database table associated with an old BO persistency model, wherein a BO meta-model describes BO dependencies and BO relationships to the at least one database table and wherein each BO has a dedicated root database table containing header entries of all instances of the BO and database tables containing BO data associated with the BO that are dependent on the dedicated root database table, allowing user changes to the BO data on either the dedicated root database table or the dependent database tables being logged generically on a database level;
• retrieve, as changed data, using at least one computer, changed BO data from the at least one database table;
• transform, as transformed data, the changed data to correspond to the new BO persistency model;
• write the transformed data to the generated at least one shadow database table;
• and
• retrieve, as further changed data during a final uptime retrieval of the BO data, BO data from the at least one database table upon a determination that the BO data has changed in the at least one database table after a prior retrieval of the BO data from the at least one database table.

A system, comprising:

• at least one data processing apparatus configured, during uptime processing, to:
• generate at least one shadow database table corresponding to a new business object (BO) persistency model;
• establish change recording for at least one database table associated with an old BO persistency model, wherein a BO meta-model describes BO dependencies and BO relationships to the at least one database table and wherein each BO has a dedicated root database table containing header entries of all instances of the BO and database tables containing BO data associated with the BO that are dependent on the dedicated root database table, allowing user changes to the BO data on either the dedicated root database table or the dependent database tables being logged generically on a database level;
• retrieve, as changed data, using at least one computer, changed BO data from the at least one database table;
• transform, as transformed data, the changed data to correspond to the new BO persistency model;
• write the transformed data to the generated at least one shadow database table;
• and
• retrieve, as further changed data during a final uptime retrieval of the BO data, BO data from the at least one database table upon a determination that the BO data has changed in the at least one database table after a prior retrieval of the BO data from the at least one database table.