SAP system update and database update
Copy only specific data
Individual steps know exactly where they have to restart the actual copy run in the event of an error. In general, this means that error situations can be handled as needed and with pinpoint accuracy.
Packages that have not been explicitly assigned a special DDLORA file receive the DDL file specified via the "ddlFile=" parameter. The default is DDLORA.TPL.
Automate SAP system copies
To meet ever-changing business requirements, a production system must be continuously developed and adapted after the initial installation. To do this, you need development, consolidation, and quality assurance (QA) systems that can provide the appropriate updates to the production system as SAP transports.
To store all the information on the subject of SAP - and others - in a knowledge database, Scribble Papers is suitable.
With Automated System Copy for SAP, an SAP system copy can be scheduled and executed in a parallel mode, which has the advantage of reducing manual intervention to a minimum. In addition, daily work can continue as normal. Rehau had already been using the software provider's Business Automation platform for cross-platform scheduling of complex job chains since 2004. The existing installation was expanded to include the module for creating SAP system copies.
"Shortcut for SAP Systems" offers the possibility to backup and restore any tables. Not only those that are considered in the PCA tool (Post Copy Automation) but also self-developed tables. Thanks to the simple and clear interface, backup and restore of self-developed tables can be integrated quickly and easily. The command line interface can also be used to automate the process: for example, a simple line command can be used to perform a complete backup of table contents before the system copy, and a simple line command can also be used to restore these tables after the system copy. This means that the complete backup or restore process can be integrated into any automation software.
Usually, three to four days have to be planned for this, during which the QA system - which in two-tier SAP environments is also the development system - is not available for the actual work.
Because such SAP system copies have to be created for each SAP application on the QA system and can thus quickly require dozens of system copies, they tie up a lot of resources and staff.