Use when designing SAP business processes during Explore or Realize phases. Triggers on requests to map current processes, design future-state processes, define process variants, assign process owners, set KPIs, or align to SAP Best Practices.
Use when starting a new SAP project, setting up governance, defining scope, identifying stakeholders, creating a project charter, or establishing a RACI matrix for any SAP Activate engagement.
Use when designing SAP solution landscapes, defining integration architecture, making BTP vs on-premise decisions, creating extensibility strategies, or producing solution architecture documents for any SAP implementation.
Use when building a business case, calculating ROI or TCO, quantifying SAP project benefits, validating savings claims, or producing value realization frameworks for any SAP investment decision.
Use when planning, sequencing, or executing SAP cutover activities including go-live weekend tasks, system switchover, data migration execution, interface activation, rollback planning, or cutover rehearsal. Triggers on any request involving cutover, production go-live execution, T-minus schedule, or cutover runbook.
Use when planning, designing, or executing SAP data migration. Triggers on requests involving data migration strategy, data mapping, LTMC, BODS, legacy data conversion, reconciliation, trial migration, or cutover data load.
Use when assessing SAP go-live readiness, producing a Go/No-Go decision, or evaluating whether a system is ready for production. Triggers on any request involving go-live approval, readiness assessment, go/no-go checklist, production launch sign-off, or cutover gate review.
Use when managing SAP post-go-live hypercare, setting up a hypercare war room, triaging live production issues, tracking stabilization, planning hypercare exit, or transitioning support to BAU. Triggers on any request involving post-go-live support, day-one issues, hypercare period, stabilization criteria, or support…
Use when designing, planning, or executing a testing strategy for an SAP implementation, upgrade, or change project. Triggers on any request involving test planning, UAT, test cases, test automation, defect management, or sign-off readiness.
Use when releasing transport requests through the SAP transport landscape. Enforces pre-release checks, dependency validation, and proper CTS workflow — DEV → QAS → PRD with quality gates at each stage.
Use when the user wants end-to-end autonomous ABAP development — from idea to tested, activated, transport-ready code. Chains through requirements → design → generate → test → activate → verify in a single pipeline.
Use when generating ABAP, CDS, RAP, Fiori Elements, or BTP CAP code for SAP systems. Enforces cloud-ready, clean-core-compliant, testable code generation — not quick-and-dirty prototypes.
Use when reviewing ABAP code, SAP development artifacts, CDS views, or any custom SAP code before transport release, pull request approval, or go-live sign-off.
Use when starting SAP development work, creating transports, moving objects across landscapes, structuring packages, or any task involving DEV→QAS→PRD change management.