Backout at Business Task level

Over the past 20+ years, ActiveControl Backout has been used by many Basis Technologies’ customers to revert out recent Production change that has inadvertantly resulted in knock-on business issues. This helps minimise production downtime (and the associated cost) by getting the business back up and running quickly whilst the root-cause of the issue is investigated and resolved.

ActiveControl Backout has always had somewhat of a limitation, in the sense that it was only possible to backout complete Import Runs. If a customer imported 100 transports to Production as part of an import run, they had to backout all 100 transports, even if they knew that it was actually only transport 50 that has caused the Production issue.

Over the last few years, several of Basis Technologies customers have requested that Backout be enhanced so it was possible to revert out individual Business Tasks, rather than an entire Import Run. ActiveControl 9.10 aims to acheve this via a new Business Task-level Backout capability. Business Task-level Backout will revert out all Transports associated with that Business Task that were deployed in that particular Import Run.

Business Task-level Backout can only be performed via the new Global View screen being delivered as part of ActiveControl 9.10 Web Platform. It is not possible to use Business Task level Backout via the legacy Windows GUI.

Figure: Business Task level backout is performed by authorised users via the Import History screen within the Global View.

Configuration Steps

Please refer to this online Knowledge Article for full details on the new Business Task-level Backout capability in ActiveControl.

*Business Task level Backout is a product-wide configuration setting – it is not possible to use a combination of Business Task level backout in some Targets, but Import Release backout in other Targets.

*Similar to the pre-existing Import Run level Backout, Business Task level Backout can only be used in ERP-type systems. It will not work in BW or non-ABAP systems such as Portal, PI or BTP applications such as Cloud Platform Integration.

! ActiveControl Backout is ultimately performed at the customer’s own risk. Basis Technologies strongly recommend that it is done as part of a controlled process with all appropriate due diligence performed. There are instances where the use of Backout can cause a bigger issue than the original issue, and therefore it is important that our customers carefully consider its usage based on the SAP changes that have been made.