Creating Tou Schedules In Eip Results In Incorrect Tou Periods
Last updated on OCTOBER 19, 2016
Applies to:LODESTAR EIP - Version 18.104.22.168 and later
Information in this document applies to any platform.
=== ODM Issue Clarification ===
When creating a TOU schedule in EIP, the user interface expects the period date ranges to be inclusive, however this is not how the RL functions expect them to be. For example, if you attempt to create a TOU schedule that just has one TOU period (all periods) and you tick off Monday through Holidays, and choose start time as 00:00 and end time as 23:59, this is validated as a correct TOU period. However, when you pass the name of this TOU schedule and period into INTDCREATETOUPERIOD the application returns an empty handle for any curve. If you look in the debug output of Data Manager, you can also see that there is an error returned when the INTDCREATETOUPERIOD function is called.
If, however, you try to set the TOU period in EIP to be 00:00 through 24:00 (as is the norm for Data Manager), the validation complains that Monday has overlapping periods.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms