Guides for change managers and the CAB

These guides are for change managers, CAB members and change approvers, Basis administrators confirming imports, and the service desk handling SAP alerts. For background, see Transports and imports.

The Transports page of the SAP settings and the SAP import schedule panel on the Change page are English only for now, and the Transports page is not yet linked in navigation — open it by its address.

Control transport auto-sync and review drift

Decide whether new development transports create Changes, and see where SAP ran ahead of TENSOR. Prerequisite: integration.config.manage to switch, integration.config.read to view.

1. Open the Transports page of the SAP settings (address /settings/sap/transports).
2. Under Transport auto-sync, check Auto-create a change for every new development transport.
3. Select Turn auto-create off or Turn auto-create on as needed.
4. Under Transport drift, read Transport, Drift and Detected, and select Open change to review the affected Change.
5. Scroll to Linked Transports to see each TR with its type, SID, position and QA/PROD import marks.

Switching auto-create off stops new Changes only. Release and import facts of already linked transports are always recorded.

Review a transport Change

Understand the state of one transport before approving or scheduling it. Prerequisite: access to the Change; integration.config.read for the SAP cards.

1. Open the Change from Changes or via Open change on the drift list.
2. Check the SAP transport drift card, if shown, and review the Change before relying on its status.
3. Check the Transport collisions card: each SAP object with its Conflicting change. Select View change to open the other Change.
4. Check the SAP import schedule panel for planned and confirmed imports.
5. Approve the Change through the normal approval if you are an approver.

TENSOR refuses the approval if you created the Change. This is the developer-is-not-approver rule. Separation between the DEV-to-QA and QA-to-PROD approvers is not yet enforced.

Schedule a transport import

Plan an import into DEV, QA or PROD within a maintenance window. Prerequisite: sap.transport.schedule.

1. Open the transport Change and go to SAP import schedule.
2. Select Schedule import.
3. Enter Target system (SID), Scheduled at, Sequence order and, optionally, Maintenance window ID and Notes.
4. Select Schedule.
5. If TENSOR warns that the maintenance window does not cover the target system, either choose another window or enter an Override justification of at least 10 characters and select Schedule with override.

The import shows as Scheduled. An override is recorded in the audit log. TENSOR does not execute the import — the Basis team runs it in SAP STMS.

Confirm an executed import

Record that the Basis team executed the import in SAP STMS. Prerequisite: sap.transport.confirm_import; you did not create the Change.

1. Execute the import in SAP STMS as usual.
2. Open the transport Change in TENSOR and go to SAP import schedule.
3. Select Confirm import on the scheduled row.
4. Read Confirm import execution and confirm.

The row shows Confirmed with the timestamp. The confirmation cannot be undone. If you created the Change, TENSOR refuses with a separation-of-duties error.

Cancel a scheduled import

Withdraw a planned import. Prerequisite: sap.transport.schedule.

1. Open the transport Change and go to SAP import schedule.
2. Select Cancel on the scheduled row and confirm Cancel import schedule.

The row shows Cancelled.

Force an import despite a collision

Proceed with an import after you have checked that a collision is safe. Prerequisite: change.sap_transport.force_import.

1. Open the transport Change and go to the Transport collisions card.
2. Review every conflicting Change first.
3. Select Force import.... The dialog Force import despite collision opens.
4. Enter Annotation (required): why the import is safe despite the collision.
5. Select Force import. TENSOR confirms Override recorded.

An import may overwrite or be overwritten by the other transport. The override and your annotation are stored in the audit log.

Check SAP collisions in the change calendar

See all in-flight transport collisions at once. Prerequisite: integration.config.read.

1. Open Changes → Calendar.
2. Switch on SAP collisions.
3. Read In-flight SAP transport collisions: each Shared object with the transports involved.

Handle an incident from an SAP alert

Work incidents that SAP monitoring raised. Prerequisite: incident rights.

1. Open the incident from your queue. It shows SAP as reporting source and the alarm ID as reference.
2. Check the affected CI: the SAP system the alert came from.
3. Work and resolve the incident as usual. Repeated alerts while it is open increase its occurrence count; they do not create new incidents.

Resolving or acknowledging the incident does not clear the alarm in SAP; alert acknowledgement write-back is planned. After the incident is resolved, a new alert opens a new incident. See Incidents for the general incident process.