Oracle Integration Cloud: Building Integrations That Survive Production · Module 5 · Mappings and transformations
Lookups inside a mapping
Lesson 53 of 175 · 2 min
Translating codes between systems WITHOUT hard-coding them into the map. That is what a lookup is for, and the argument is maintenance rather than elegance. A hard-coded translation inside an expression is a business rule only a consultant can change. The client adds a new payment term, a new country, a new legacy code — and a change that should be a row in a table becomes a change request, a deployment and a version. A LOOKUP IS CONFIGURATION. Somebody who is not you can add a row, see what the mappings are, and audit them. That is the same argument this catalogue makes for OTBI over BI Publisher and for HSDL over HDL: prefer the artefact the client's own team can maintain. WHAT BELONGS IN A LOOKUP: a translation between two systems' vocabularies, where the mapping is a list of pairs and it changes occasionally. Legacy code to Fusion…
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.
In this module: Module 5 · Mappings and transformations
- 1What a mapping really isFree preview
- 2The mapper, practically
- 3Required, optional and the empty element
- 4Repeating elements and loops
- 5Conditional mapping
- 6Functions: strings, numbers and dates
- 7Dates and time zones, carefully
- 8Numbers, precision and currency
- 9Lookups inside a mapping
- 10Testing a mapping with real data
- 11Namespaces, and the errors they cause
- 12Keeping a mapping maintainable
- 13What breaks: five mapping failures
- 14Lab briefing · Map two schemas that disagree