Shared execution
Two operators requesting the same scope should follow a coherent execution, not trigger duplicate concurrent reads.
Organize observation, follow each execution and retain its result. Scheduling belongs to BetishOps; SAP remains read-only.
Scheduling is only the beginning. Value comes from knowing what was collected, whether it is valid and who can use it.
Schedule or run now through the same coordinator.
Authorized source, identifiable context and progress.
Completeness and fidelity before replacing the latest valid observation.
A traceable revision activates its consumers.
BetishOps Jobs are not SAP Jobs. Reading SM37 does not create, cancel or administer jobs in SAP.
Two operators requesting the same scope should follow a coherent execution, not trigger duplicate concurrent reads.
Recovering work must not publish twice or accept a response from an owner that lost its authority.
Queueing, extraction, validation, publication and outcome are distinct, so the status of each job is understandable.
The backend owns the operation. The browser requests and observes; closing a tab should not erase its context.
Let’s discuss your sources, your questions and the outcome you need. No credentials or sensitive data required.