TABLE OF CONTENTS

• Overview
• Prerequisites
• Transaction File Format
• Validation Process
• Rejection Rules
  • 1) Invalid UOM Code
  • 2) Mandatory UOM Missing
  • 3) Warning Scenario
• UOM Conversion
  • Data Storage
  • Inspect Data
  • Error and Warning Reporting
• Best Practices

Overview

When Unit of Measure (UOM) support is enabled for a transaction entity, the application validates the UOM provided in each transaction record, converts the quantity to the product's base UOM, and stores the converted value for downstream planning.

This allows transaction files to be uploaded using different units (for example, Box, Pack, Each, Kg, Gram), while ensuring that all planning calculations use a single, consistent base unit for each product.

Prerequisites

Before uploading transaction data with UOM, ensure the following prerequisites are met:

• Unit of Measure has been configured for the tenant.
• All required UOMs are available in Inspect Data → Unit of Measure.
• The transaction entity is enabled for UOM support.
• The required quantity attributes (for example, Shipped Units, Returned Units, On Hand, Damaged Units, Recalled Units) are configured to use UOM.
• Product-specific UOM conversion factors have been loaded.

Transaction File Format

When UOM is enabled, the transaction file must include a UOM Code column.

Example:

The UOM Code identifies the unit in which the quantity is supplied.

Validation Process

During data load, the application validates the UOM Code for every transaction record.

The UOM Code :

• Should exist in the tenant's Unit of Measure configuration.
• Should be available in the Unit of Measure table
• Should have a valid conversion to the product's base UOM.

Only records that pass validation are eligible for UOM conversion.

Rejection Rules

A transaction record is rejected in the following scenarios.

1) Invalid UOM Code

If the UOM Code does not exist or is not enabled for the tenant, the record is rejected.

Example:

Reason

Invalid UOM code. 'PULL' is not enabled for this tenant.

2) Mandatory UOM Missing

If the UOM field is configured as mandatory and a quantity is provided without a UOM Code, the record is rejected.

Example:

Reason

UOM code is missing.

3) Warning Scenario

If the UOM field is optional and a quantity is provided without a UOM Code, the record is not rejected.

Instead, the application generates a warning.

Warning

UOM code is missing. UOM conversion not applied.

The record continues to load, but no unit conversion is performed.

Note: The display name of the UOM field may vary between tenants because it represents the display name of the configured UOM attribute.

UOM Conversion

After successful validation, the application converts the quantity from the uploaded UOM into the product's base UOM.

The conversion uses the product-specific conversion factors configured in the Unit of Measure Conversion entity.

Example:

Product Base UOM = Each

Conversion:

• 1 Box = 24 Each

Transaction File:

Stored Value:

1) Data Storage

Regardless of the unit supplied in the transaction file, the application stores all quantity measures in the product's base UOM.

This ensures that planning, replenishment, forecasting, analytics, and reporting use a consistent unit of measure across the application.

2) Inspect Data

The Inspect Data screen continues to display the original values exactly as they were received in the transaction file.

For example:

Uploaded File:

Inspect Data:

Although the application stores the converted value internally (120 Each), Inspect Data preserves the original uploaded value and UOM for auditing and troubleshooting purposes.

3) Error and Warning Reporting

Validation results are available in the data load rejection or warning output.

Each rejected or warned record includes a clear message describing the reason so that the source data can be corrected and reloaded.

Best Practices

• Load the Unit of Measure and Unit of Measure Conversion entities before loading transaction data.
• Ensure all required UOM Codes are enabled for the tenant.
• Configure the correct base UOM for every product.
• Verify that all quantity attributes requiring conversion are mapped for UOM support.
• Review the rejection and warning files after every data load to identify invalid or missing UOM Codes before rerunning the import.