Unit of Measure

Prev Next

Why Consistent Units of Measure Are Critical in Intercompany Transactions

When processing intercompany transactions, it is essential that both companies use the same Unit of Measure (UoM) codes for items. Misalignment can lead to data errors and failed transactions.

Key Principles

  1. Unit of Measure Code Must Exist in Both Companies
    The UoM code you send must be set up on the corresponding item in the receiving company. This applies in both directions.

  2. Consistency Across Items

    • If the sales company uses PCS and the inventory company uses STK, the system will use PCS throughout the order flow.

    • If you manually change the UoM on an order in the inventory company, the sales company must also recognize that code.
      Example: If you change to STK in the inventory company, then STK must exist in the sales company.

  3. Translations for Clarity
    If you need to display a translated UoM (e.g., PCS → STK), you can:

    • Set up translations on Units of Measure.

    • Add the field Unit of Measure (instead of Unit of Measure Code) to item lines for better readability.


Best Practices

  • Align UoM codes during setup for all intercompany items.

  • Avoid manual changes unless both companies have matching codes.

  • Use translations for user-friendly display without breaking system logic.