Open EPM ← Back to openepm.dev

execute_v2_calendar_program

Writes an explicit Year and Period mapping with inclusive start and exclusive end. Use the current mapping change ID, or an empty string for an undefined mapping, and current metadata revision. Returns a mapped range and receipt. Overlap or stale revisions block the write.

These signatures come from local MCP tool discovery. Use the signature registered by your deployment and confirm your identity and permissions before calling the tool.

Endpoint signatures and example arguments

Examples show the arguments to the tool. Replace placeholder IDs and illustrative revisions with values from your authorized disposable scope.

Bound application

Set an explicit Year/Period date range and ordinal.

Required arguments
program, idempotency_key
Optional arguments
None
{
  "program": {
    "languageVersion": 2,
    "function": "metadata.calendar.period.set",
    "arguments": {
      "yearId": "Y2027",
      "periodId": "P01",
      "ordinal": 1,
      "startsOn": "2027-01-01",
      "endsBefore": "2027-02-01",
      "expectedChangeId": "",
      "expectedMetadataRevision": 0
    }
  },
  "idempotency_key": "docs-example-0001"
}
Exact JSON input schema
{
  "properties": {
    "program": {
      "additionalProperties": true,
      "title": "Program",
      "type": "object"
    },
    "idempotency_key": {
      "title": "Idempotency Key",
      "type": "string"
    }
  },
  "required": [
    "program",
    "idempotency_key"
  ],
  "title": "execute_v2_calendar_programArguments",
  "type": "object"
}

Application router

Set an explicit scoped fiscal period through fixed validation.

Required arguments
workspace_id, application_id, program, idempotency_key
Optional arguments
None
{
  "workspace_id": "{{workspace_id}}",
  "application_id": "operating-cube",
  "program": {
    "languageVersion": 2,
    "function": "metadata.calendar.period.set",
    "arguments": {
      "yearId": "Y2027",
      "periodId": "P01",
      "ordinal": 1,
      "startsOn": "2027-01-01",
      "endsBefore": "2027-02-01",
      "expectedChangeId": "",
      "expectedMetadataRevision": 0
    }
  },
  "idempotency_key": "docs-example-0001"
}
Exact JSON input schema
{
  "properties": {
    "workspace_id": {
      "title": "Workspace Id",
      "type": "string"
    },
    "application_id": {
      "title": "Application Id",
      "type": "string"
    },
    "program": {
      "additionalProperties": true,
      "title": "Program",
      "type": "object"
    },
    "idempotency_key": {
      "title": "Idempotency Key",
      "type": "string"
    }
  },
  "required": [
    "workspace_id",
    "application_id",
    "program",
    "idempotency_key"
  ],
  "title": "execute_v2_calendar_programArguments",
  "type": "object"
}
Supported application-language functions

Handling errors

MCP_TOOL_CAPACITY_NOT_DISPATCHED means the server did not dispatch this call. MCP_TOOL_DEADLINE_OUTCOME_UNKNOWN or MCP_TOOL_PROCESS_FAILED_OUTCOME_UNKNOWN leaves the outcome unknown. For a call with effects, reconcile the original request before starting a new one. For a scoped denial, verify the caller's grant and the selected target.

Module guidelines Β· Related workflow Β· Application-language function catalog

Discussion

Discussing execute_v2_calendar_program

The discussion service requires JavaScript and a connection to Firebase.