In the world of EDI there are always exceptions. I can’t tell you how many times I’ve heard a client say “We always ship to our customers the same way”. Then quickly follow up that statement with “Oh, except for Target. We ship their items a bit differently”.
We have always tried to make MAPADOC as flexible as possible to handle these types of exceptions. A good example of this is a new feature we’ve added to the General Cross Reference. In the latest release of MAPADOC for Sage 100 versions 4.40, 4.50, and 5.00 there is a new “Exceptions Only Cross Reference” feature. During inbound and outbound document creation, if this feature is selected for a cross reference, cross reference not found exceptions are not reported if a value is not found in the cross reference. This can be particularly useful to handle special requirements, reduce the amount of records needed in the cross reference, and maintain the integrity of the valuable exception reporting in MAPADOC.
For example: A particular client always ships their orders using UPS. Oh wait, except for a few items that must be shipped via FedEx. The client was easily able to do this using the new “Exceptions Only Cross Reference” feature. A new “FedEx Items” general cross reference was created with this new feature selected. The cross reference only contained the few item numbers that needed to be shipped via FedEx. During Sale Order Creation if the particular item being ordered was found in the new cross reference the shipping method was assigned to FedEx, if not the shipping method was defaulted from the customer setup. Not only was the requirement met, the customer was not mislead by cross reference not found exceptions for the items that needed to ship via UPS.