Settings and scheduling of ERP data loads

Management › Settings. This screen gathers your company’s settings; at the top, the Scheduling of ERP data loads card says when each ERP’s data is copied into the tool. The purchasing manager and the administrator set things; management reads. Allow three minutes.

1. Reading the table

One row per entity and per family of data (articles, prices and volumes; stock; orders; invoices; quotes; sales; exchange rates): the frequency and window in force, the last load, the next one, the status (up to date, late, stale data, manual, suspended, off), the reason when nothing started (source unchanged, outside the time window, another load running, backup or administration operation, retry after a failure), the lock time (the milliseconds during which the write could get in other users’ way) and the rows written. For sales, “copied by day” (one row per reference and customer per day, with the number of movements) or “monthly source”.

Note

If the scheduler is off, a banner says so: nothing starts by itself. Switch it on once with the Scheduler on setting (whole company), lower on the same screen.

2. Setting an entity’s frequency and hours

Open the entity’s row, click Set up…, then choose:

• the frequency: by hand, once a day, every 2 h, every hour, every 30 min, or a number of minutes;
• the window: start and end hour, in the entity’s local time (a start after the end means night, for example 22 then 6); outside the window nothing starts, and when the window reopens a single pass catches up;
• the days: every day, Monday to Friday, Monday to Saturday, or the weekend only;
• whether this applies to this data only or to all the entity’s data; the reason (at least 10 characters).

A value already in force is not rewritten; each setting applied is a new version, which can be cancelled from the history at the bottom of the screen. A minimum safety interval exists (15 minutes by default): a shorter frequency is raised to that floor.

3. Run now

Run now asks for an immediate load of the row, with a reason. The scheduler picks it up at its next pass (under a minute); it follows the same safeguards as the scheduled loads: never at the same time as another, never during a backup. If the source has not changed, the load is recorded as “unchanged” and nothing is written.

Why this slows nobody down

The ERP is read without blocking users; only the short final write takes the lock, and its time is measured and shown. An unchanged source costs no write and no growth of the database. See also the operations guide (§ 5.2) and rule RF-161.