Skip to main content

Mapping Tables

Overview

Mapping Tables provide a centralized way to manage partner and supplier identifiers across all your Jakamo integrations. Instead of configuring the same vendor mappings separately for each integration, you can now create a single mapping table and use it across Purchase Orders, ASN, Invoices, and other integrations.

This guide explains how to use Mapping Tables to simplify your integration setup, migrate from existing mappings, and reduce duplicate configuration work.

Table of Contents​

  1. Why use Mapping Tables
  2. Prerequisites & Permissions
  3. Getting Started
  4. Creating and Managing Mapping Tables
  5. Adding Mapping Entries
  6. Migrating from Existing Integrations
  7. Connecting Mapping Tables to Integrations
  8. Troubleshooting
  9. FAQ

1. Why use Mapping Tables​

Previously, if you used Purchase Order, ASN, and Invoice integrations, you needed to configure the same 50 supplier mappings three separate times—once in each integration's settings. Mapping Tables solve this problem.

Before Mapping Tables:

  • Configure supplier "ACME-VENDOR-123" → "ABC Manufacturing Ltd" in PO integration
  • Configure the same mapping again in ASN integration
  • Configure it a third time in Invoice integration
  • Repeat for all 50+ suppliers ❌

With Mapping Tables:

  • Create one Mapping Table called "My Suppliers"
  • Add "ACME-VENDOR-123" → "ABC Manufacturing Ltd" once
  • Attach this table to PO, ASN, and Invoice integrations
  • Done! ✅

Key Benefits​

  • Centralized management - Maintain partner identifiers in one place
  • Reuse across integrations - One mapping table can be used by multiple integrations
  • Easy migration - Import existing mappings from an integration with one click
  • Better visibility - See all your partner mappings in a single view
  • Fewer errors - Update once, apply everywhere
When to move to Mapping Tables

If you currently manage the same partner mappings across multiple integrations, consolidating them into Mapping Tables will save significant time and reduce errors.

2. Prerequisites & Permissions​

Who can use Mapping Tables:

  • You must be a company admin to create and manage mapping tables
  • Your user account needs mapping tables management permissions

What you need:

  • At least one active integration (Purchase Order, ASN, Invoice, etc.)
  • A list of your partner companies and their identifiers from your ERP/internal system

The Jakamo UI will only show actions you're permitted to perform. If you don't see the Mapping Tables option, contact your company administrator.

3. Understanding Mapping Tables​

How They Work​

Mapping Tables connect your ERP codes to Jakamo companies. When your integration sends/receives messages, it uses these mappings to route data correctly.

Key benefit: One table shared by multiple integrations (PO, ASN, Invoice).

Two Tabs, Two Purposes​

Partner identifiers (main tab)

  • Your ERP vendor code → Partner company in Jakamo
  • Example: VENDOR-123 → ABC Manufacturing Ltd
  • Optional: Add partner's business unit if they have multiple locations
  • This is what routes messages

Own identifiers (rarely needed)

  • Your ERP code → Your own company's business unit
  • Example: PLANT-FIN → Your Company Finland BU
  • Used for: PDF footers, auto-confirmation, multi-location tracking
  • Skip this unless you have multiple business units

Business Units (Optional)​

Many companies don't use business units at all. If you don't, just map: ERP code → Partner company. Done.

If your partner has business units:

  • After selecting the company, a Business Unit dropdown appears
  • Select their specific location/division
  • Required if the dropdown shows options

If you have business units:

  • Use the Own identifiers tab
  • Maps your ERP codes to your locations
info

Business units must be activated in Jakamo (contact support). Most companies operate without them.

4. Creating Your First Mapping Table​

  1. Go to Company menu → Integrations → Mapping Tables

  1. Click + Add Mapping Table

  1. Enter a name in Mapping Table Name (for example, "Main Suppliers")
  2. Click Create

Naming tips:

  • Good: "Main Suppliers", "European Vendors"
  • Avoid: "Table 1", "Test"

5. Adding Partner Mappings​

Add an Entry (Partner identifiers tab)​

  1. Partner Number - Your ERP vendor/customer code
  2. Partner Company - Select from the dropdown
  3. Business Unit - Select if the dropdown appears (optional otherwise)
  4. Click + Add Entry

Example:

  • Partner Number: HYDR-001
  • Partner Company: Hydraulex Components Oy
  • Business Unit: Seinäjoki Plant (if they have multiple plants)

Managing Entries​

Search: Use the search box to find an entry by identifier, company name, or business unit

Delete: Click the trash icon. Confirm Delete mapping entry with Delete. Cancel keeps the row.

Edit: Delete old entry, add new one (no direct edit)

warning

Deletions take effect immediately. Messages with that code will fail until you add it back.

Common Errors​

"Mapping entry with this identifier already exists"

  • The code is already in this table
  • Search for it → delete if wrong → add correct one

"Failed to create mapping entry"

  • Company doesn't exist or no access
  • Refresh page and retry

6. Own identifiers (Skip if No Business Units)​

note

Most users skip this. Only needed if your company has multiple business units.

Where to Find It​

The Own identifiers tab is on the Mapping Tables page, next to Partner identifiers:

Navigation: Company menu → Integrations → Mapping Tables → Select your table → Own identifiers tab

You'll see two tabs at the top:

  • Partner identifiers (default tab - covered in Section 5)
  • Own identifiers (this section)

When You Need This​

If you have business units (Finland office, Germany office, and so on):

  1. Go to the Mapping Tables page
  2. Select your mapping table from the Mapping Table dropdown
  3. Click the Own identifiers tab (next to Partner identifiers)
  4. Identifier — the code in your ERP. Your own company is already selected
  5. Business Unit — choose your location. The field is shown when your company has business units, and it is required then
  6. Click + Add Entry
  7. Example: NHI_STO → Nordic Heavy Industries Stockholm

This identifies which of your locations sent the order. It does not route the message to a partner.

7. Connecting to Integrations​

Critical

Creating a mapping table does nothing until you connect it to an integration.

How to Connect​

From the Integrations page (not from the Mapping Tables page):

  1. Go to Company menu → Integrations
  2. Find your integration (for example, "Nordic Heavy PO")
  3. Under Mapping table, select your table. Use integration-tied mappings keeps the company strings that belong only to this integration
  4. Confirm Change mapping table. The dialog says integration messages may stop working correctly. OK saves the choice. Cancel restores the previous one
  5. View opens the selected table

The Mapping table dropdown is on these tags: PO, SO, FORECAST, ASN API, CLAIMS, OUTBOUND, CLAIMS REST API, BUYER_API, and SUPPLIER_API.

Multiple Integrations, One Table​

Connect the same table to multiple integrations:

  • PO integration → "Main Suppliers"
  • SO integration → "Main Suppliers"
  • ASN integration → "Main Suppliers"
  • Claim integration → "Main Suppliers"

Add one supplier = works in all connected integrations ✅

Buyer API identifiers​

Connect the table to your BUYER_API integration (or SUPPLIER_API, if that is the integration you use). Calls that name a partner company or a business unit send the identifier from this table and set the identifier type to MAPPING_TABLE_ENTRY.

The field lists are in the Buyer API:

Person identifiers are still user strings on the Integrations page.

What Happens After Connection​

Success: ERP sends VENDOR-123 → table maps to ABC Mfg → message routed ✅

Failure: ERP sends UNKNOWN-999 → not in table → message fails ❌

Fix: Add missing code to table → go to integration logs → click REQUEUE

Old Mappings​

When a mapping table is selected, company strings for other companies are hidden. Mappings to your own company stay in the list. The note on that list says they do not route messages. They remain for special features such as PDF footers and auto-confirmation. The hidden partner mappings are kept.

8. Migrating from Existing Integrations​

note

Skip this if starting fresh. This is for importing existing integration mappings.

Quick Process​

  1. Create an empty mapping table
  2. Select it on the Mapping Tables page
  3. Open Select Integration and choose the source integration
  4. Click Initialize from Integration
  5. If some rows were skipped, read Initialization Notices and click Close

Why Items Get Skipped​

Skip Reasons (click to expand)

"… is external identifier mapping, skipped."

  • Not supported in mapping tables
  • Cannot be added manually
  • Contact support if critical

"… is duplicate, skipped."

  • Same code mapped multiple times
  • First one imported, rest skipped
  • Check which was imported, adjust if needed

"… is in a business unit defined vendor mapping namespace, skipped."

  • You use different vendor codes per BU for same supplier
  • Not supported (requires one code per supplier)
  • Standardize vendor codes across BUs

After Migration​

  1. Verify imported entries
  2. Test with messages
  3. Connect table to integrations

Re-import: Delete all entries (or delete table) → create new empty table → initialize again

9. Managing Tables​

Editing Entries​

Delete the old entry (confirm Delete), then add the new one. There is no direct edit.

warning

Changes apply immediately to all integrations using the table.

Switching Tables​

Use the Mapping Table dropdown to open another table.

Deleting a Table​

Click the trash icon next to the Mapping Table dropdown. Confirm Delete mapping table with Delete. Cancel keeps the table.

Error: "This mapping table is referenced in one or more integrations. Disconnect this mapping table from any integrations before deleting."

  • Open each integration that uses the table
  • Set Mapping table to Use integration-tied mappings, or select another table
  • Then delete

10. Troubleshooting​

Top Issues​

"Mapping not found" in integration logs

  1. Note the identifier from error
  2. Add it to your mapping table
  3. Requeue the message

Cannot delete table

  1. Open each integration that uses it
  2. Set Mapping table to Use integration-tied mappings
  3. Delete the table

Duplicate identifier

  • Search for existing entry
  • Delete if wrong, add correct one

11. FAQ​

Can multiple integrations share one table?
Yes. Main benefit of mapping tables.

What if I update an entry?
Changes apply immediately to all integrations.

Can same identifier exist in different tables?
Yes. Only unique within one table.

What happens to old mappings?
Hidden permanently, cannot be deleted. Kept as backup.

Why can't I initialize into non-empty table?
Safety feature. Delete entries or create new empty table first.

When do I need Business Units?
Only if your partner (or you) have multiple divisions/locations in Jakamo. Most companies don't use them.

When do I need the Own identifiers tab?
Only if YOUR company has multiple business units. Otherwise skip it.

Can I rename a table?
No. Delete and create new one if needed.

Need Help?​

Jakamo Support: support@thejakamo.com

Quick Reference:

  • Can't see Mapping Tables? → Ask admin for permissions
  • Duplicate error? → Delete existing entry first
  • Can't delete table? → Set Mapping table to Use integration-tied mappings on each integration, then delete
  • Message failing? → Add missing identifier, requeue message
info

Mapping Tables simplify integration management. Set them up once, use across all integrations.