When setting up a new trading partner or business integration process, thinking through the process beforehand can greatly decrease the implementation time and help minimize problems. Many integration projects can come to a grinding halt in the middle of implementation if it’s only later realized that required data is not configured in your backend application, or if your system doesn’t support the particular communication protocol your new trading partner intends to use. “Looking before leaping” will help alleviate potential problems later.
When setting up a process to translate data from your backend database to another format, it is common to realize that your source DB data is too disparate with how your target data format needs to be mapped/structured. Introducing database views can often simplify integration between two formats and reduce or eliminate the need for external programming.
A view is simply a named select statement that is stored in a database as an object. Using a view can simplify the mapping process by renaming fields (rows) to a purpose more easily understood. Continue reading