Skip to content

Jarltech Automatic Processing

The Jarltech connector can process open orders and item synchronization on a schedule via the BC Job Queue.

Overview

There are two independent background pipelines:

Pipeline Codeunit Purpose
Auto-Sync Orders ALN MCJ Job Runner Update and process open orders
Item Sync (multilingual) ALN MCJ Item Sync Runner Maintain descriptions, minimum order quantity and vendor link

Data import is separate

The price/stock import is not part of this order pipeline. It is run via the DashboardExecute Import or the central import pipeline of the Hub. See Data Import (Prices & Stock).


Setting Up the Job Queue

Auto-Sync of Orders

Via the SetupCreate/update Job Queue.

Setting Value
Object Type / ID Codeunit ALN MCJ Job Runner
Recurring Job Yes
Run Days Monday–Friday
Run Window 06:00–20:00
Minutes Between Runs Sync Interval (Minutes) from the setup (default 60)
Max. Attempts / Retry Delay 3 / 60 seconds

Item Synchronization

Via the Item SynchronizationCreate Job Queue Entry.

Setting Value
Object Type / ID Codeunit ALN MCJ Item Sync Runner
Recurring Job Yes
Run Days Monday–Friday
Run Window 06:00–22:00
Minutes Between Runs 60

On hold at installation

Both Job Queue entries are created on hold at installation. Activate them via the Setup or the Item Sync Queue once your configuration is in place.


Order Auto-Sync Flow

The job processes all orders with a linked purchase order (except canceled ones). For each order, the following sequence runs:

  1. Update order data — Retrieve status, lines, shipments and tracking from the API; report the shipment number to the Hub.
  2. Synchronize invoices — Import new invoices from the shipments.
  3. Update purchase order — Set vendor invoice no., delivery note no., posting date and ship-to address.
  4. Assign serial numbers — From the invoice lines to the reservation entries.
  5. Shipping/insurance costs — Add and distribute as item charges.
  6. Update sales order — Set the expected shipment date.
  7. Post receipt — When fully delivered (Supplied) and Auto Post Receipt is active.

Each order is processed individually and in a transaction-safe manner. Switches such as Auto-update purchase order, Auto-assign serial no., Auto-add shipping costs and Auto-post receipt control which steps are executed.


Monitoring

The Connection & Sync FactBox on the Dashboard shows:

Display Meaning
API Status Connection status to the Jarltech API
Last Sync / Next Sync Last and next synchronization
Mode Live or Simulation
Pending Syncs Open item synchronizations
Errors (24h) Synchronization errors of the last 24 hours

Error Handling

Scenario Behavior
API not reachable Job ends with error, next run after the interval
Token expired Automatic token renewal, then retry
Single order faulty Error is counted/logged, other orders continue

With process notification enabled and a notification email maintained, you receive a summary after the run (only in case of changes or errors).


Configuration Recommendations

Field Recommendation
Enable Auto-Sync Enable for production operation
Sync Interval (Minutes) 60 minutes (default), possibly shorter for high volume
Auto-update purchase order Recommended: enable
Auto-assign serial no. Recommended: enable (for items requiring serial numbers)
Auto-add shipping costs Recommended: enable (maintain charge numbers in the setup)
Auto-post receipt Only enable if no manual receipt process is desired

Tips

Initial configuration

Keep Simulation mode enabled during the initial configuration.

Permissions

The user who runs the Job Queue needs write permissions on the Jarltech objects (PermissionSet ALN MCJ User or ALN MCJ Admin). Recommended: a dedicated service account.

License gate

The background runs check whether the connector is activated and licensed for the module JARLTECH. Without a valid license, the automatic processing is skipped.