Supply Lens

Create a Mapping

Lesson 16 of 21 7 min read

Create a Mapping record, set its core fields, and use the matching, target and miscellaneous settings to control exactly when it runs.

In this lesson you will create a Mapping and learn every setting on the Mapping screen, with guidance on when to use each one and when to leave it blank.

Create a Mapping

  1. Open Settings → Integration setup → Mappings.
  2. Click + ADD in the top-right.
  3. Set the Map (document type), From, As and To fields.
  4. Set Automatic and Enabled as needed.
  5. Click SAVE.
The Mapping screen: Matching on the left, Target and Miscellaneous on the right.

The screen has three areas.

Matching: which Documents this Mapping applies to

If all the values you set match a Document, the Mapping runs. Leaving a value empty applies to all Documents.

Document typeThe document type to convert from. Required.
From integrationThe Integration the Document came from. Required.
CustomerOnly run for this customer. Blank for all customers.
SupplierOnly run for this supplier. Blank for all suppliers.
Ship toOnly run for this ship-to Party. Blank for all.
Ship to locationOnly run for this ship-to Location. Blank for all.
Ship fromOnly run for this ship-from Party. Blank for all.
Ship from locationOnly run for this ship-from Location. Blank for all.
TagsOnly run for Documents carrying these tags, one per line. Blank to match regardless of tags.

These filters use your master data. The Customer filter only works if the customer's Documents are matched to the right Party, and a Location filter only works if the Location is recognised.

Target: what to produce and where to send it

Map toTarget Data (send directly) or Document (produce an intermediate Supply Lens Document). Required.
To integrationThe Integration to send the data to. Required.
Target tagsTags to apply to the item produced at the target, one per line.

Miscellaneous

Status update types lists the status updates this Mapping should respond to, one per line. Use it when a Mapping should only fire on particular status changes rather than every matching Document. If you're unsure what values your Integrations use, ask Support.

Hilltop's Warehouse Order Mapping

Priya creates the Mapping that sends warehouse orders to Brookside:

SettingValueWhy
Document typeWarehouse OrderThe fulfilment instruction
From integrationUnleashedUnleashed produces the warehouse orders
Matching filtersBlankEvery warehouse order goes to Brookside; Hilltop has one warehouse
Map toTarget DataBrookside's system takes warehouse orders directly
To integrationBrookside (Mintsoft)The 3PL
AutomaticOff for testing, on at go-liveSo she can check each test order first
EnabledOn

When Hilltop opens a second warehouse, she'll add a Ship from location filter so each warehouse's orders go to the right 3PL.

Blank is powerful

Every blank filter means "all". Start with filters blank and add them only when you need to split a flow. A filter set by mistake is a common reason a Mapping silently doesn't run for some Documents.

Recap

  • Create Mappings from Settings → Integration setup → Mappings → + ADD.
  • Matching fields decide which Documents the Mapping applies to; blank means all.
  • Target fields decide whether to produce Target Data or a Document, and where to send it.
  • Filters rely on your master data being matched correctly.
  • Status update types let a Mapping respond only to specific status changes.

Quick guides for this topic

Complete and continue

Your progress is saved in this browser. Create a free account to keep it everywhere, take quizzes and earn certificates.

What a Mapping doesCommon Mapping patterns