back to top

SalesLogix ERP Link- How the sales order push to MAS determines which warehouse to use

If you have worked with ERP Link you have probably gotten use to seeing validation errors when attempting to push a sales order to MAS from SalesLogix. Something like this:

SalesLogix ERP Link Sales Order validation errors

But how do you know what the problem is?  What is ERP Link using to populate the warehouse value, causing it to fail?

ERP Link can be very confusing as to what value gets used, if it comes from data in SalesLogix, from one or more templates, or from MAS itself.  This is especially true of the Sales Order push and how the warehouse value is determined by ERP Link.  The following will hopefully help you understand how the warehouse values are set and what may cause a problem.

First of all you need to understand MAS has a warehouse value defined at both the header and line level of the sales orders.  ERP Link uses different logic at each level to determine what warehouse is used.  Here is the logic flow:

Header level

  • ERP Link first populates the warehouse with the value in the customer template.
  • It then checks to see if the address template has a warehouse value, if it does, it uses that value instead.
  • Finally, if neither the customer nor address template have a warehouse defined,  it uses the Warehouse of the default shipping address in MAS for the customer, using this query:

select timWarehouse.WhseID
from
timWarehouse INNER JOIN
tarCustAddr ON timWarehouse.WhseKey = tarCustAddr.WhseKey RIGHT OUTER JOIN
tarCustomer ON tarCustAddr.AddrKey = tarCustomer.DfltShipToAddrKey
where
tarCustomer.CustID = {Current customer}
And tarCustomer.CompanyID = {Current Company}

Line item level

  • If the address template warehouse is defined ERP Link uses this.
  • If the address does not have a warehouse defined ERP Link uses the customer template warehouse.
  • If neither template has a warehouse defined it uses the default warehouse defined at the product level, using this query:

select WhseID
from
timItem INNER JOIN
timWarehouse ON timItem.DfltWhseKey = timWarehouse.WhseKey
where
timItem.ItemID = {Line Item}
And timItem.CompanyID = {Company}

  • If it is still empty it will then pass an empty value.
Contact Customer FX for your CRM project
We let our expertise speak for itself - let us know how our all-star team can help on your CRM project
About the Author
Kris Halsrud
Kris Halsrud
Kris Halsrud is a Senior Analyst / Developer for Customer FX Corporation.

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Infor CRM Sync for Exchange: Action Required by August 31, 2026

Using Infor CRM Sync for Exchange with Microsoft 365? Your Exchange administrator must update tenant settings by August 31, 2026 to prevent sync disruption.

[Webinar] What’s Coming Next for Infor CRM SLX and Why v10 Matters

See what’s coming next for Infor CRM SLX, including new marketing workflows, automation improvements, and reasons to consider upgrading to v10.

Disable Caching in Infor CRM SLX Web Client

In the rare case caching is causing issues in the Infor CRM SLX web client, it is possible to disable specific types of caching by making edits using Application Architect, and then deploying.

Exploring AI Options for Infor CRM v10

I've started taking a closer look at the AI capabilities built into Infor CRM v10. Over the next several posts, I'll share what I learn. From the built-in features and supported AI providers to implementation considerations, costs, and practical use cases.

Infor CRM SLX 10.0: Delegate Ownership Changes for “Everyone” Records

Learn how the new EveryoneOwnerAssignment secured action in Infor CRM SLX 10.0 allows designated users to change ownership of Everyone-owned records without requiring Administrator access.

Related Articles

Infor CRM Sync for Exchange: Action Required by August 31, 2026

Using Infor CRM Sync for Exchange with Microsoft 365? Your Exchange administrator must update tenant settings by August 31, 2026 to prevent sync disruption.

[Webinar] What’s Coming Next for Infor CRM SLX and Why v10 Matters

See what’s coming next for Infor CRM SLX, including new marketing workflows, automation improvements, and reasons to consider upgrading to v10.

Disable Caching in Infor CRM SLX Web Client

In the rare case caching is causing issues in the Infor CRM SLX web client, it is possible to disable specific types of caching by making edits using Application Architect, and then deploying.

Exploring AI Options for Infor CRM v10

I've started taking a closer look at the AI capabilities built into Infor CRM v10. Over the next several posts, I'll share what I learn. From the built-in features and supported AI providers to implementation considerations, costs, and practical use cases.

Related Videos