Runbooks, not heroics
Every SAP team has procedures that live in one person's head: the kernel update steps, the client copy checklist, the sequence that has to be followed after a failed transport, in exactly that order.
When that person is on holiday
The procedure is either delayed or improvised, and neither is great on a production system. Written documentation helps, but it drifts from reality and nobody checks the prerequisites the same way twice.
Unattended scripts are not the answer either. They hide what happened, and on SAP systems the cost of a step that silently failed is high.
What a good SAP runbook does
- Checks prerequisites firstBefore the first step runs, not halfway through.
- Shows each stepThe operator sees what will run and what came back.
- Stops honestlyA failed step reports failure, rather than letting the procedure carry on as if it had succeeded.
- Leaves a recordEvery action attributable to a named person.
How FCC runs procedures
Guided runbooks
Prerequisites validated before execution, steps shown to the operator.
Audit trail
Every action written to the audit trail with the person who ran it.
Routine Basis operations
Including kernel patching and client copy procedures.
People stay in charge
Automation as guided procedures, not unattended scripts.
The benefit is not only speed. The third person to run a procedure gets the same result as the first, and the knowledge belongs to the team.
Go deeper
Common questions
Do runbooks run unattended?
What happens when a step fails?
Turn one procedure into a runbook.
Pick the procedure your team depends on one person for, and we will look at it together. FCC is in Beta.
"SAP" and SAP product names are used descriptively. Farrenio Cloud Control is a Farrenio product and implies no partnership with or endorsement by SAP.