3763281 - Dynamic Date 'Yesterday' evaluates incorrectly - SAP S/4HANA Cloud Public Edition

Dynamic Valuation Key Date of Post Credit Impairment job is valuated as:

• Two days in the past when using time zone earlier than UTC+0 (e.g. India Standard Time UTC+5.5), or
• Today when using time zone later than UTC+0 (e.g. Eastern Standard Time UTC-4)

The same behavior apply for other Job template with Dynamic Date like Dynamic Posting Date in Automatic Clearing or Dynamic Valuation Key Date in other Valuation apps (Foreign Currency Valuation, Post Discounting, Post B/S Reclassification, ...).

SAP S/4HANA Cloud Public Edition

1. Schedule the Post Credit Impairment job with Dynamic Valuation Key Date set to “Yesterday”.
2. Run the job at 10:00 PM Eastern Time (correspond to 02:00 AM UTC next day)
3. Observe that the dynamically evaluated key date is the same date as run date.

System time used for Dynamic Valuation Key Date is in UTC.

• Consider that dynamic date calculations use UTC (refer to system time conversion when interpreting “Yesterday”).
• Reschedule the job to an earlier or later time, depend on the relation between local time and UTC time.

KBA 3514300 - Time zone Explanation - SAP S/4HANA Cloud Public Edition

dynamic date, yesterday, key date, valuation date, utc, time zone, posting period, month-end, impairment job, post credit impairment, batch job scheduling, period-end close, date conversion, s/4hana cloud, local time, today, two days before, Foreign Currency Valuation, Automatic Clearing, dynamic valuation key date, dynamic balance key date, dynamic posting date, Post B/S Reclassification,  , KBA , BC-SRV-TIM-TZ , Time zones , FI-GL-GL-2CL , Basic Functions (Public Cloud) , Problem