What is the unit of measure (UOM) map?

The UnitOfMeasureMap.csv file serves following purposes:

• Maps each UOM value back to itself: If a UOM value is not mapped back to itself, and this UOM is used in a catalog or contract subscription, this can cause a processing failure on the generated subscription.
• Maps UOM from items in a supplier's static catalog (locally loaded) or PunchOut catalog to the system UOM defined in the UnitofMeasure.csv file (ex. DZ in the supplier's PunchOut catalog maps to DZN within SAP Ariba Buying).
• When exporting data from the site to your Enterprise Resource Planning (ERP) system, the Preferred column within the UnitOfMeasureMap.csv file determines which UOM to export on purchase order line items within the PurchaseOrderDetailsExport.csv file (Preferred = Yes).
  
  If no mappings are marked as preferred, your site uses the UOM mapping that maps the system UOM back to itself (ex. DZN maps to DZN). Note that this does not apply to shopping cart data sent from SAP Ariba Catalog to your ERP system.

The UOM map applies when working with catalogs that use United Nations Center for Trade Facilitation and Electronic Business (UNCEFACT) units of measure codes, effectively mapping the UOM back to the standard UOM codes used in SAP Ariba. SAP Ariba Procurement solutions use mappings to associate standard abbreviations for units of measure to canonical representations you might use.

You can adjust units of measure for catalogs that use United Nations Units of Measure (UNUOM) for their units of measurement:

• Catalogs in Commerce Extensible Markup Language (cXML) must use only UNUOM.
• Catalogs in Catalog Interchange Format (CIF) use American National Standards Institute (ANSI) by default, but can use UNUOM.
• Ariba does not validate catalogs that use ANSI for their units of measurement.

You can use the following steps to update the UOM mapping in your site:

1. Click Manage> Core Administration.
2. Click Site Manager > Data Import/Export.
3. Search for Export Unit of Measure Mapping task.
4. Click Export.
5. Make the necessary changes/additions to the UnitOfMeasureMap.csv file by adjusting the following columns:

• Key column: The external UOM value (supplier PunchOut catalog or incoming ERP UOM values).
• Value column: Represents the preloaded system UOM within the site. It must match with the UOM in UnitofMeasure.csv.
• Preferred column: Determines which UOM mapping to use for transactional export files, such as purchase order exports. If set to No, the system UOM is used in transactional exports.

The following example demonstrates proper mapping for the UOM value Dozen, which has a system value of DZN. DZN must be mapped to itself, and a separate row in the file is dedicated to map DZ to DZN. This allows supplier PunchOut catalog items with a UOM of DZ to be acceptable for purchasing in SAP Ariba Buying. Because Preferred = Yes for the DZ to DZN mapping, transactional export data to your ERP system show DZ for the UOM value (note that this does not apply to shopping cart data sent from SAP Ariba Catalog to your ERP system):

To import the UnitOfMeasureMap.csv file:

1. Click Manage> Core Administration.
2. Click Site Manager > Data Import/Export.
3. Search for Export Unit of Measure Mapping task.
4. Click Import.
5. Use the Load import operation type, browse for the updated file.
6. Click Run.
7. The data is created/updated accordingly within the site.

Anyone in the Customer Administrator group has access to import/export this file in Ariba, using the Import/Export Unit of Measure Mapping task (UnitOfMeasureMap.csv file).

You can also view and update the mappings within the Catalog Manager > Units of Measure Map section within the site.

Values for Key and Value columns must be in uppercase. The following content item explains why a catalog load might fail due to a UOM issue.

Catalog Management
Catalog Management > Catalog Administration > Catalog Units of Measure
Core Procurement > Core Administration > Receiving tolerance
Invoicing
Purchasing