Aide · silicon ioi

Warehouse Stock - Stamp scheduler

Fiche

Introduction #

You need a periodic snapshot of your stock levels—weekly or monthly—to track their evolution. Site by site, warehouse by warehouse, item by item, lot by lot.

This module allows you to easily take periodic stock snapshots, with or without details. These data can then be used to build BI analyses (charts, dashboards, etc.). Performance is optimized for direct use.

Warning #

This process is disk-space intensive. It is recommended to monitor disk usage on your hosted server.

In many cases, several databases are hosted (additional companies, production database, sandbox, demo, etc.).

Astuce

  • Disk space may be occupied by other databases or configurations.
  • The system will automatically stop the snapshot creation if disk space is insufficient (see the threshold defined in the general ioi settings).
  • Consider setting alert email addresses in the general settings to be notified of these issues.

Scheduling (Scheduler) #

Schedule your stock snapshots #

Define here the frequency of the snapshot and the execution time.

Two cycles are available:

  • Weekly
  • Monthly

Attention

If both cycles coincide, the snapshot process will run only once.

Why choose a low-activity time? #

  • Your analyses will be skewed if stock movements occur during the snapshot.
  • This process is CPU-intensive on the server side.
  • This process is also intensive in terms of disk writing.

Special cases #

Is your factory active at night?\nIn that case, schedule the snapshot early in the morning, on the day after the end of the month, and check the [x] Execute the next day option.

Info

The recorded pivot date will remain the end of the month if the snapshot occurs before 5:00 a.m.

Astuce

Does your business operate without interruption? Consider using the ioi module Stock variation over a period instead.

Immediate execution #

Manually launch the snapshot #

You can launch the snapshot immediately.

Attention

Make sure to choose a low-activity time to ensure the relevance of the analysis.

Here you can see if a process is already running, along with the last execution message.

Detailed view and summary view #

In the Warehouse Summary tab, you can access either a summarized or detailed view of the snapshots:

“Warehouse Summary” view #

  • Only valuation is displayed (not quantities).
  • Available axes:
    • Pivot date
    • Division
    • Site
    • Warehouse

“Item Detail” view #

  • Available information: total quantity and valuation.
  • Available axes:
    • Pivot date
    • Division
    • Site
    • Warehouse
    • Location
    • Item reference
    • Lot or serial number (if used)
    • External lot or SN reference (if used)

Analysis, BI and data export #

Access analysis, BI and export options via the following two modules:

  • ioi Warehouse Stock Stamp
  • ioi Warehouse Summary Stamp

Post-snapshot cleanup #

Given the high disk-space consumption, it is strongly advised to regularly delete old snapshots.

A cleanup process can be scheduled periodically.

Info

You can delete only detailed snapshots (items) and keep the global snapshots (warehouses).

Astuce

  • A full disk can crash your server. No operation will be possible anymore. The database may be damaged beyond recovery.
  • This is a critical incident to avoid at all costs.

Preventing a full disk #

In the general ioi settings, define the alert notifications.

Two alert levels:

  • Warning alert
  • Critical alert

Astuce

  • Free disk space < 20% = critical alert.

  • Space may be consumed by other databases or configurations.

  • Define multiple notification email addresses to include backup managers.

Snapshot quality #

Some bad practices can distort your stock analysis. A snapshot reflects a real-world situation. Clean and reliable data are essential.

Item valuation #

From the start, define the valuation method:

  • In the ioi item settings, choose the default method for all new creations.

Best practices to adopt #

  • Never record purchase orders without a purchase price.
  • Close production orders before registering the stock entry.

Avoid backdated or postdated documents #

If operators enter backdated or postdated documents, the reliability of the snapshot will be compromised.

Astuce

If your business requires modified dates, use the Stock variation over a period module, which requires accounting skills and clean initial values.

Avoid unvalued movements #

If stock movements are not valued, the snapshot valuation will be invalid. A single unvalued line can break the entire consistency.

Concerned movements:

  • Purchase receipt (cost comes from the order)
  • Sales delivery
  • Stock out
  • Stock in (cost calculated from production)
  • Stock qualification (changing from one state to another, e.g., from “bad” to “good”)

Astuce

Inventory counts concern quantities only, not valuation.