Twice in a week... the Address Type

I hit the Address table last Tuesday for the first time, with a Partner, while working on a brand new E-Business integration. Few days later, the Address table was the main topic in a monthly catchup with a German Customer in the middle of a Vendor Qualification process revamp.

For those not familiar with AMOS, the Address module is part of the core and it is used by all modules, to store information about: Makers, Suppliers, Authorities, Agencies, Charterer, and so forth. To make it simple, if we remove the Address module, there's no AMOS!

Every time we integrate with a third-party, chances are we'll do something with the Address tables, sometime we import Vendors from SAP, push out some Makers to IFS, get some Supplier from QuickBooks.

Historically, in every Technical Specification for such integrations, we used to define constraints all around AMOS to properly handle the Addresses. Small things, like "don't use if...", "use only for ... or ..., but not for ...", hardcoded and complex to maintain in the long term.

Cleaning my mailbox today, it was immediately clear to me how the Address module has been improved in the years, as well the gazillion words saved for every spec I wrote in the latest years.

I've just check couple of boxes on the Address Type attributes to deliver the solution expected. Everything in less than 30 minutes, hands-on with the Customer and without programmers.

If you are still reading, it means you've approved on the Technical Specification mentioned above. Drop me a message and let's figure out how to simplify your interfaces.