Non Transportable Change

Non-Transportable Changes that do not relate to specific transports, as well as non-SAP changes that need to be delivered at the same time as related SAP changes, can both be managed within ActiveControl. Managing them via ActiveControl ensures visibility and auditability of such changes, and also means they can also adhere to an approvals workflow in the same manner as SAP Change being delivered through ActiveControl. These types of changes will still use the concept of transports and paths and so will follow the existing process and logic in ActiveControl. They can either be sent down an existing SAP transport path or a new path created specifically for each non-SAP system.

Within ActiveControl, non-Transportable Changes are called Manual Activities. These and non-SAP changes are both logged within the Windows GUI or Web UI via the Create Transport Form button.

Figure: Adding Manual Activities and Non-Transportable Deployments via the Windows GUI

Figure: Adding Manual Activities and Non-Transportable Deployments via the Web UI

*Manual Activity (SAP or non-SAP system) can be used for the creation of a number range or RFC destination or for non-SAP systems, this could be the installation of a printer or any other manual action. Non-Transport Deployment (SAP or non-SAP system) can be used to deploy a script or executable to any system.