Back to MCP Main Module

MCP Transaction / Job Control Tower

Job-centric view: dmf_jobs ↔ service_workflow_executions ↔ service_executions. Tool name (e.g. create_orders_from_excel) from workflow or dmf_jobs.workflow_code. object_id → dm_object_new. Transaction codes from dmf_job_module_codes.module_ref_code.

Job ID MCP Client Tool name Service (id / type) Job status Production Operation code(s) Transaction codes DMF_OBJECT (dm_object_new.code) Order / Booking ref Container / Other ref Created (date/time) Actions

Job detail

dmf_jobs

service_workflow_executions

service_executions

Transaction codes (dmf_job_module_codes) — module_ref_code = transaction code

dmf_object_codeoperation_codemodule_ref_code (transaction code)
Further transaction details (drill-down) — Order/Booking ref and Container/Other ref are shown as extra columns above; you can guide how to load more (e.g. from order, booking, or container tables by module_ref_code). A full drill-down view per transaction can be added later.

Open MCP Configuration Control Tower to see config for this workflow / service.

stc_development_v1: dmf_jobs, dmf_job_module_codes, service_workflow_executions. Data is loaded from the MCP database (backend MCP_DATABASE_* or same host + this schema). If your job is missing, ensure the backend points to the same server/schema where the job was created — set MCP_DATABASE_HOST in backend .env when the job runner uses a different server.

Table link chain (for maintenance)