Why would a FedExx FXI-A integration profile created to access a Sage 100 order table require multiple credential logins when processing orders during the day?

Why would a FedEx FXI-A profile created to access a Sage 100 order table require multiple credential logins when processing orders during the day?

A  FedEx FXI-A integration data file mapping profile was created to allow access to a Sage 100 order Table on the customer's network. Other than the 45 minutes for each connection to the 2436 tables within Sage to be surveyed for field values, the import works fine once all the required mapping was completed. The main issue right now is that once the shipper first connects to the Sage order table in the AM, the integration is requiring multiple credential logins to be porrformed before the profile will populate the FSM screen. I advised the customer that this is probably an individual User permissions policy being enforced by the Sage order table, or by the customer's network policy. How can this be resolved? I do not see conditional coding with FXI-A correcting this.

  • 0

    Is the integration querying Sage 100 through the ODBC driver?  If it is, you should set up a system DSN with the login credentials and company code to be accessed saved in the DSN.  Kind of sounds like it might be trying to use the SOTAMAS90 user DSN which will clear saved credentials anytime a Sage 100 report is processed.

    For the initial mapping, it is recommended to set up an Access database with either linked tables or pass-through queries set up for just the tables that FedEx needs to query.  Then point FedEx to the Access database instead of the Sage 100 database.  This eliminates the time it takes for the mapping to run through EVERY sage 100 table as it will only run through the ones set up in the Access database.