MSAMM
Back to course

Oracle Integration Cloud: Building Integrations That Survive Production · Module 5 · Mappings and transformations

Dates and time zones, carefully

Lesson 51 of 175 · 2 min

A date is a date until an integration crosses a zone boundary. Then it is a date, a time, and an assumption. WHERE THE SHIFT HAPPENS. A source system records a date in its own zone. The payload carries it — sometimes with an offset, sometimes without. OIC interprets it in whatever zone the runtime or the function assumes. The target then stores it in ITS zone. Every one of those steps can move the value by a few hours, and a few hours is enough to change the DATE when the original time was near midnight. WHY AN INVOICE CAN LAND A DAY EARLY FOR HALF THE YEAR: daylight saving. A conversion that is correct in winter is an hour out in summer, and where the value sits near a boundary that hour changes the day. The symptom is a defect that appears in March and disappears in October,…

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.

See the course and enrol9 free lessons

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

In this module: Module 5 · Mappings and transformations

  1. 1What a mapping really isFree preview
  2. 2The mapper, practically
  3. 3Required, optional and the empty element
  4. 4Repeating elements and loops
  5. 5Conditional mapping
  6. 6Functions: strings, numbers and dates
  7. 7Dates and time zones, carefully
  8. 8Numbers, precision and currency
  9. 9Lookups inside a mapping
  10. 10Testing a mapping with real data
  11. 11Namespaces, and the errors they cause
  12. 12Keeping a mapping maintainable
  13. 13What breaks: five mapping failures
  14. 14Lab briefing · Map two schemas that disagree