[Home] [Help]
1706: ----------------------------------------------------------------
1707: -- Now we rely on dynamic SQL to treat the bound string as an --
1708: -- expression for a Date object, and we call TO_CHAR on it to --
1709: -- turn it into a string version of that Date, formatted into --
1710: -- our standard format. --
1711: ----------------------------------------------------------------
1712: l_dynamic_sql := 'SELECT TO_CHAR('||l_formatted_string||', '''||
1713: EGO_USER_ATTRS_COMMON_PVT.G_DATE_FORMAT||''') FROM DUAL';
1714: Debug_Msg('In Format_Sysdate_Expression, l_dynamic_sql is as follows:', 3);
2007: ASSUMPTIONS:
2008: 1). the UI validates that Number default values with UOM are in the UOM base
2009: 2). the UI validates that Date default values are in
2010: EGO_USER_ATTRS_COMMON_PVT.G_DATE_FORMAT and that
2011: Standard Date default values are truncated appropriately
2012: ***/
2013:
2014: l_candidate_value := l_default_value;
2015:
10070:
10071: EXCEPTION
10072:
10073: ----------------------------------------------------------------------------
10074: -- We do not ROLLBACK in this procedure: standard behavior for Business --
10075: -- Objects is for each row being processed to succeed or fail independent --
10076: -- of the status of other rows, so we let Process_Row ROLLBACK any errors --
10077: -- it encounters. If callers want different behavior, they can establish --
10078: -- a SAVEPOINT prior to calling this procedure and ROLLBACK if we report --