DBA Data[Home] [Help]

APPS.WMS_ARCHIVE_PVT dependencies on DUAL

Line 267: -- @@@ date arithmetic is being performed with the SELECT from dual.

263: -- @@@ "to_char(min(last_update_date), 'MM/DD/YY HH:MI:SS')"
264: -- @@@ Since the 'l_min_range_date_time' is a varchar, the fnd_date.displaydate_to_date()
265: -- @@@ is used to convert it to a date and assign to the l_from_date(date variable).
266: -- @@@ This only needs to be done the very first time since in the subsequence runs,
267: -- @@@ date arithmetic is being performed with the SELECT from dual.
268: -- @@@
269: -- @@@ The logic of deriving the 'l_from_date' and 'l_to_date' for each worker call is as follows:
270: -- @@@ 1. For the very first run, the 'l_from_date' is equal to the 'l_min_range_date_time'.
271: -- @@@ This is passed as a date variable to the first worker call.

Line 275: -- @@@ 'select (l_from_date + l_each_worker_chunk) into l_to_date from dual;'

271: -- @@@ This is passed as a date variable to the first worker call.
272: -- @@@ 2. The 'l_to_date' is computed as the 'l_from_date + l_each_worker_chunk' every time as follows:
273: -- @@@ The 'l_each_worker_chunk' stores the number of days for each worker.
274: -- @@@ Hence the
275: -- @@@ 'select (l_from_date + l_each_worker_chunk) into l_to_date from dual;'
276: -- @@@ effectively derives the l_to_date with a precision to the last second.
277: -- @@@ 3. In every subsequent run, date arithmetic is performed on the 'l_from_date' and 'l_to_date'
278: -- @@@ derived in the previous run prior to the worker call.
279: -- @@@

Line 308: select (l_from_date + l_each_worker_chunk) into l_to_date from dual;

304:
305: -- @@@ Get the max date range for the worker call.
306: -- @@@
307: --l_to_date := l_from_date + l_each_worker_chunk;
308: select (l_from_date + l_each_worker_chunk) into l_to_date from dual;
309:
310: if (l_debug = 1) then
311: trace(l_proc || ' i => ' || i);
312: trace(l_proc || ' l_to_date => ' || to_char(l_to_date, 'RRRR/MM/DD HH24:MI:SS'));

Line 1564: -- @@@ date arithmetic is being performed with the SELECT from dual.

1560: -- @@@ "to_char(min(last_update_date), 'MM/DD/YY HH:MI:SS')"
1561: -- @@@ Since the 'l_min_range_date_time' is a varchar, the fnd_date.displaydate_to_date()
1562: -- @@@ is used to convert it to a date and assign to the l_from_date(date variable).
1563: -- @@@ This only needs to be done the very first time since in the subsequence runs,
1564: -- @@@ date arithmetic is being performed with the SELECT from dual.
1565: -- @@@
1566: -- @@@ The logic of deriving the 'l_from_date' and 'l_to_date' for each worker call is as follows:
1567: -- @@@ 1. For the very first run, the 'l_from_date' is equal to the 'l_min_range_date_time'.
1568: -- @@@ This is passed as a date variable to the first worker call.

Line 1572: -- @@@ 'select (l_from_date + l_each_worker_chunk) into l_to_date from dual;'

1568: -- @@@ This is passed as a date variable to the first worker call.
1569: -- @@@ 2. The 'l_to_date' is computed as the 'l_from_date + l_each_worker_chunk' every time as follows:
1570: -- @@@ The 'l_each_worker_chunk' stores the number of days for each worker.
1571: -- @@@ Hence the
1572: -- @@@ 'select (l_from_date + l_each_worker_chunk) into l_to_date from dual;'
1573: -- @@@ effectively derives the l_to_date with a precision to the last second.
1574: -- @@@ 3. In every subsequent run, date arithmetic is performed on the 'l_from_date' and 'l_to_date'
1575: -- @@@ derived in the previous run prior to the worker call.
1576: -- @@@

Line 1609: select (l_from_date + l_each_worker_chunk) into l_to_date from dual;

1605: if (i = l_number_workers) then
1606: l_to_date := l_max_date;
1607: else
1608: --l_to_date := l_from_date + l_each_worker_chunk;
1609: select (l_from_date + l_each_worker_chunk) into l_to_date from dual;
1610: end if;
1611:
1612: if (l_debug = 1) then
1613: trace(l_proc || ' i => ' || i);