Zero Downtime Option for SAP S/4HANA

Naming Conventions

This section deals with the most important naming conventions used in this document.

For more naming conventions, see the SUM Guide mentioned in Required SAP Notes and Further Documentation.

Term

Description
bridge subsystem The state of the customer system when all existing application servers are reconnected to the bridge database schema. From a technical perspective, the bridge database schema reuses the shadow database schema.
customer buffer A file that contains the list of customer transports.
FDCT Short for: fast data copy transfer. Refers to copying content of changed tables to a target version table.
original system A customer system as combination of an SAP ABAP system and a database schema (including all related objects, that is, repository and application tables) for which the maintenance event is planned.
SAPup An executable that is called internally by SUM.
shadow system and shadow database schema The shadow system is used to prepare the repository and the dictionary objects of the target release in the shadow database schema.
SLT and CDC replication

SLT is short for: SAP landscape transformation

CDC is short for: change data capturing

SLT is an extraction, transformation, and loading (ELT) tool that allows you to load and replicate data in real time, or to schedule data from a source system and a non-source system into the SAP HANA database.
SUM Short for: Software Update Manager
SUM directory

Directory that is created when the SUM archive is unpacked on the host where the tool is initially started. During the unpacking, data and programs are copied to this directory.

The recommended standard path of the SUM directory is: Start of the navigation pathusr  Next navigation step  sap  Next navigation step  <SID>  Next navigation step  SUMEnd of the navigation path
target system Final system state running on the target release. The system is connected again to the original database schema.

update

A collective term for all the software logistics processes that you can perform using SUM (such as performing release upgrades, installing enhancement packages, or updating a system with support package stacks).

In this document, the term is used in the context of

  • release upgrades

  • application of feature package stacks

  • application of support package stacks

using SUM.
upgrade subsystem Finalization of the repository of target release. The upgrade subsystem operates on the original database schema.
UPL Short for: usage and procedure logging. It is used to log all called and executed ABAP units such as programs, function modules, classes, methods, and subroutines.
V1 Stands for version 1 and represents the source release.
V2 Stands for version 2 and represents the target release.
ZDO Short for: Zero Downtime Option. A procedure to minimize the technical downtime during the maintenance event.