Symptom
-
After using the function utc_to_local or local_to_utc on a datetime column, subsequent mappings of that column are showing the wrong datetime
- i.e. The result of local_to_utc(<column_name>,<time-zone>) and Query.<column_name> are the same, and one should be different
Environment
SAP Data Services 4.x
Cause
When call a function on a column, you are permanently altaring the value of that column for the duration of the job.
Resolution
To resolve this issue, you have three options:
-
Create multiple copies of the input column and use a seperate function call for each one.
- Use utc_to_local after calling local_to_utc on the same column, and vice versa.
- If you are using multiple mappings of the column but only using one function, put the function call on the very bottom of the schema out, which will call it last.
Keywords
BODS, time, date, unexpected, wrong , KBA , EIM-DS-EXE , Job Execution , Problem
Product
SAP BusinessObjects Dashboards 4.0