Actions: End of Planning Process & ERP Export

Actions: End of Planning Process & ERP Export

This article is part of the Actions series, split from the original Actions article.

End of Planning Process





Snapshot Report Data Sources

Create a snapshot of demand and planning data to use as report data sources.





Update Geo Locations

Update the stored latitude and longitude coordinates for each location for mapping features. 



Snapshot - ERP Export Tables

Snapshot Orbit transactions to the export schema for downstream ERP integration.



Status: DRAFT — pending screenshots and final review at code freeze.

Snap - ERP Export Tables

Snap - ERP Export Tables lets you snapshot Orbit transaction data into a dedicated PostgreSQL export schema, and push the latest snapshot out to a SQL Server target on a schedule — so downstream ERP or reporting systems always have a clean, up-to-date, row-level copy of your transaction data without touching Orbit's operational tables.

What gets snapshotted
Production, Procurement, Demand, Transfer, and Stock Adjustment transaction data, taken per scenario. Each new snapshot for a scenario replaces the previous one — snapshots are not versioned or kept in history, and the snapshot's metadata (timestamp and statistics) updates each time.

1. How the data is structured

  • Snapshots are written to a dedicated, read-only PostgreSQL output schema — separate from Orbit's operational tables, so exports never affect live planning data.
  • Data is exported one row per transaction — there is no aggregation. Each row includes the required fields: Order ID, Type, Date, Quantity, SKU, Location, and any required custom or composite properties.

2. Demand snapshots require a filter

Demand snapshots are the one exception to a straightforward snapshot: you must specify at least one demand type filter before running a Demand snapshot. If no demand type filter is set, the snapshot will not run.

3. Setting up a SQL Server export target

  1. Go to Settings → Data.
  2. Configure your MS SQL Server export target — this is the destination the latest snapshot will be pushed to.
  3. Once a target is configured, you can export the latest scenario snapshot to it at any time, or set up a recurring schedule (see below).

4. Scheduling refreshes

Batch refresh timing is configurable per data type, so you can match the schedule to how often each transaction type actually changes. For example, one tenant might refresh production data multiple times a day, while refreshing transfers only once daily. Set the cadence that fits your own reporting needs for each snapshot type.

5. Connectivity

Before relying on scheduled exports, confirm connectivity between your SQL Server target and the PostgreSQL output schema — this should be validated during UAT so scheduled refreshes don't fail silently once you're in production.

Source: Snap - ERP Export Tables acceptance criteria. Last updated: draft, pending screenshots.



Transfer ERP Export to Target

Bulk-copy he exported Orbit transactions for a scenario to a configured customer database.




Job Dependency between SQL and Arkieva 

When executing an action on a schedule from a task with a predecessor, Arkieva will check completion/action status of predecessor and only execute action if predecessor completed/successful.

The following API are exposed to trigger for Public:

Configuration 
protocol: https://
hostname: api.staging.arkieva.com
public_api_client: arkieva.public
public_api_secret: [REDACTED - request from your Arkieva contact]
identityhost:svc.staging.arkieva.com

Get workflow task details
{{protocol}}{{hostname}}/api/sop/workflows/public/task/{workflowTaskId}

Invoke workflow task and mark complete
{{protocol}}{{hostname}}/api/sop/workflows/public/task/{workflowTaskId}/invoke?markComplete=true

Search workflowTask ID by Name
{{protocol}}{{hostname}}/api/sop/workflows/public/process/{workflowProcessId}/tasks?taskName=Segmentation&contains=true

Get children workflow ID
{{protocol}}{{hostname}}/api/sop/workflows/public/task/{workflowTaskId}/children

Get predecessor workflow ID
{{protocol}}{{hostname}}/api/sop/workflows/public/task/{workflowTaskId}/predecessor




Actions series