Oracle Integration Cloud: Building Integrations That Survive Production · Module 11 · Lookups, libraries and reuse
Lookups: the cross-reference table
Lesson 110 of 175 · 2 min
Mapping codes between systems as DATA rather than as LOGIC. What belongs here, and who is allowed to change it. Every integration between two systems hits the same problem: the same thing has a different code on each side. The client's ERP calls a payment term NET30 and the bank calls it 30D. The supplier is SUP-4471 here and V4471 there. Somebody has to hold the correspondence. THE WRONG PLACE IS THE MAPPING. A chain of conditions comparing against literals works perfectly and turns every new code into a development change: edit the integration, test it, promote it through three environments, activate. A day of work for one row of data, and the person who knows the answer — somebody in finance — cannot supply it. THE LOOKUP IS THE RIGHT PLACE. A table of correspondences, columns per system, rows per code, editable in the console. The mapper reads it…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Integration Cloud: Building Integrations That Survive Production, with a certificate on completion and a fourteen-day refund window.