[Home] [Help]
263: -- EXECUTE AUDIT TRAIL REPORTING -- FUNCTIONAL FLOW
264: -- ================================================
265: --
266: -- This prog is used to created the Change history for each timecard, whose
267: -- information is retrieved from HXC_TIME_ATTRIBUTES, HXC_TIME_BUILDING_BLOCKS
268: -- and HXC_TRANSACTIONS.
269: --
270: -- The processing is done per timecard -- meaning the table HXC_RPT_TC_DETAILS_ALL
271: -- table is grouped by resource_id, start_time and stop_time for each iteration
292: -- Approvals
293: -- ---------
294: --
295: -- Timecard approvals normally are captured by the APPLICATION_PERIOD scope records
296: -- from hxc_time_building_blocks. A join with our Details_all table and hxc_time_building
297: -- blocks will give you this information. Once you get all the approvals, these has to be placed
298: -- so that the reporting table will get this info in proper place. For this, the submissions
299: -- captured above are browsed thru and a most appropriate submission is found out.
300: -- The transaciton_id of this submission is taken in as the transaction id of the approval
639: 'LIGHT_APPROVAL','Approval On Submit',
640: 'AUTO_APPROVE', 'Auto Approved',
641: comment_text),
642: ' '
643: FROM hxc_time_building_blocks hxc,
644: fnd_user fnd
645: WHERE scope = 'APPLICATION_PERIOD'
646: AND resource_id = p_resource_id
647: AND p_start_time BETWEEN start_time
678:
679: BEGIN
680:
681: -- Private Procedure record_approvals
682: -- Queries against HXC_TIME_BUILDING_BLOCKS and FND_USER
683: -- for all the APPLICATION_PERIOD records for this timecard.
684: -- The application periods are joined with BETWEEN & AND
685: -- conditions to pull up those timecards whose Approval period
686: -- spans across multiple timecard periods.