WMS Storage Index Setup Guide

Your complete guide to configuring and managing the Storage Index

What is the Storage Index?
Quick Start
Field Explanations
Actions and Operations
Recommended Settings
Troubleshooting
Frequently Asked Questions

What is the Storage Index?

The Storage Index is a system that pre-calculates and stores warehouse storage data. This makes reports and invoices generate much faster because the system doesn't need to recalculate everything each time.

Understanding the Index Tables

The Storage Index consists of six interconnected tables that store data at different levels of detail:

Period Table - Daily totals for the entire warehouse
Customer Table - Daily totals per customer
Batch Table - Daily totals per batch with basic info
Batch Content Table - Detailed batch information (item, dates, attributes)
Handling Unit Table - Daily totals per handling unit (pallet/container)
Handling Unit Content Table - Detailed handling unit content lines

Benefits

Fast reports - No more waiting times
Accurate invoices - Always correct storage charges
Automatic - Works by itself after configuration
Reliable - Less chance of errors

Quick Start

Step 1: Initial Configuration

For new installations:

Open Storage Index Setup
Set Index Starting Date to today
Choose Read Method: "Table (Accuracy)"
Set Auto Update Before Invoicing to "Yes"
Click Create Job Queue Task

Step 2: Email Notifications

Enter your email address in Mail Storage Index to receive alerts.

Step 3: Activate

Go to Job Queue Entries and set the status to "Ready" to start automatic processing.

Field Explanations

Main Settings

Last Item Ledger Entry No.

Shows the last processed transaction number. This field is automatically updated.

Action required: None, for information only

Read Method

Determines how the system reads data.

Table (Accuracy) ← Recommended choice
- Fully accurate
- Slightly slower but more reliable
Query (Performance)
- Only use for very large databases
- Faster but less accurate

Calculation Method

Determines when the index is updated.

Direct ← Always choose this
- Updates happen immediately
- Data is always current

Index Starting Date

The date from which the index will be built.

New installation: Choose today or go-live date
Existing system: Choose a date that fits your reporting needs
Note: The further back, the longer the initial build takes

Rebuild From Date

Rebuilds the index from a specific date by first deleting all data from that date forward.

When to use: After data corrections that affect historical storage data
How it works: Deletes all index data from this date forward, then rebuilds it
Warning: This is a heavy operation that can take significant time
Leave empty: In normal situations
Note: Field is automatically cleared after use

Invoicing Settings

Auto Update Before Invoicing

Ensures the index is current before creating invoices.

Yes ← Always keep enabled
No: Only in exceptional cases

Invoicing Before Starting Date

What happens if you try to invoice before the starting date?

Error ← Recommended
- Prevents invoicing without index data
Allowed
- Only if you have an alternative invoicing method

Item Ledger Entry Table Filter

Allows you to exclude certain transactions from the index.

When to use: For test data or specific exceptions
Example: Customer No.: <>TEST*
Advice: Use filters sparingly

Monitoring

Mail Storage Index

Email address for system alerts.

What you'll receive:
- Problem notifications
- Maintenance warnings
Tip: Use a group email for better coverage

Last Item Ledger Entry Checked

Shows integrity check progress.

Action required: None, informational only

Compression Settings

Compress Index After

After how much time old detailed index data is removed.

-30D: For busy warehouses with limited storage
-90D: For warehouses needing 3 months of detail
-1Y: Default setting (1 year) ← Recommended
-2Y: If you need long-term historical data

Compression Method

What exactly is removed during compression?

Method	What gets removed	When to use
Delete Batch/Batch Content/Handling Unit/Handling Unit Content	Handling Unit details + Batch details (keeps Period & Customer data)	Standard choice
Delete Batch Content/Handling Unit Content	Handling Unit details + Batch line details (keeps Batch headers)	Keep batch summary info
Delete Batch/Batch Content/Handling Unit Content	All details except handling unit summaries	Keep handling unit tracking
Delete Handling Unit Content	Only handling unit line details (keeps all summaries)	Maximum summary retention
Delete All	All tables: Period, Customer, Batch, Handling Unit, and all details	Maximum space saving

Date Compression

Which dates are kept after compression?

Keep Last Day of Week/Month ← Recommended
- Keeps week and month ends
- Ideal for most reporting

Important: What happens during compression?

When compression runs (based on your "Compress Index After" setting):

Handling Unit Content lines are ALWAYS deleted for dates older than the compression period
Other tables are deleted based on your "Compression Method" setting
The "Date Compression" setting determines which specific dates are removed

Progress Fields

Update Item Ledger Entry No. & Update Progress Date

These fields show progress during large updates.

Action required: None, for monitoring only

Actions and Operations

Main Actions

Create Job Queue Task

Creates an automatic task that maintains the index.

What it does: Checks for new transactions every minute
How to use:
1. Click the button
2. Go to Job Queue Entries
3. Set status to "Ready"

Reset Index

WARNING: Completely removes ALL index data and rebuilds from scratch.

Option 1: Direct Reset

For small databases (< 100,000 transactions)
Blocks the system during execution
Use outside office hours
Can take 1-4 hours depending on data volume

Option 2: Reset via Job Queue ← Recommended

For production environments
Splits work across multiple background tasks
System remains available during reset
Progress can be monitored in Job Queue Entries

When to use Reset Index:

After major data corrections in historical transactions
When changing Index Starting Date
If integrity check shows persistent errors
System upgrade requiring index rebuild

Test Functions

Simulate Historical Index

Tests index building without real changes.

Use for: Testing new settings

Recommended Settings

For New Installations

Index Starting Date: Today
Read Method: Table (Accuracy)
Calculation Method: Direct
Auto Update Before Invoicing: Yes
Compress Index After: -1Y
Compression Method: Delete Batch/Batch Content/Handling Unit/Handling Unit Content
Date Compression: Keep Last Day of Week/Month

For Existing Systems

Same as above, but choose an Index Starting Date that fits your reporting needs.

Maintenance Tasks

Daily

Check if Job Queue is active
Review any error messages

Weekly

Check Last Item Ledger Entry No.
Verify index is up-to-date

Monthly

Evaluate compression settings
Check index size

Troubleshooting

Index is not current

Symptoms: Reports show old data

Solution:

Check Job Queue status
Review Last Item Ledger Entry No.
Restart Job Queue if needed

Job Queue not working

Symptoms: Automatic updates stop