eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

APPS.PAY_PRT_SHD dependencies on DT_API

Line 153: -- PRIVATE - copied from dt_api

149: -- ----------------------------------------------------------------------------
150: -- |-------------------------< Effective_Date_Valid >-------------------------|
151: -- ----------------------------------------------------------------------------
152: --
153: -- PRIVATE - copied from dt_api
154: --
155: -- Description: Procedure ensures that the effective date is not null and
156: -- exists on or after the start of time.
157: --

Line 256: -- PRIVATE - copied from dt_api

252: -- ----------------------------------------------------------------------------
253: -- |------------------------< Return_Max_End_Date >---------------------------|
254: -- ----------------------------------------------------------------------------
255: --
256: -- PRIVATE - copied from dt_api
257: --
258: -- Description: Function returns the maximum effective_end_date for the
259: -- specified table and primary key.
260: -- NOTE: if the maximum end date doesn't exist (i.e. no rows

Line 714: -- PRIVATE - copied from dt_api

710: -- ----------------------------------------------------------------------------
711: -- |-----------------------< Lck_Future_Rows >--------------------------------|
712: -- ----------------------------------------------------------------------------
713: --
714: -- PRIVATE - copied from dt_api
715: --
716: -- Description: Locks the entity from the effective_date to the end-of-time.
717: -- No processing will be completed if the p_key_value is
718: -- null because the column could be defined as nullable.

Line 823: -- PRIVATE - copied from dt_api

819: -- ----------------------------------------------------------------------------
820: -- |----------------------------< Lck_Child >---------------------------------|
821: -- ----------------------------------------------------------------------------
822: --
823: -- PRIVATE - copied from dt_api
824: --
825: -- Description: Locks the specified child entity maximum row for the specified
826: -- parent key value:
827: --

Line 942: -- PRIVATE - copied from dt_api

938: -- ----------------------------------------------------------------------------
939: -- |-------------------------< Get_Insert_Dates >-----------------------------|
940: -- ----------------------------------------------------------------------------
941: --
942: -- PRIVATE - copied from dt_api
943: --
944: -- Description: Locks and parental entity rows (if supplied) and Returns
945: -- the validation start and end dates for the DateTrack
946: -- INSERT mode

Line 1422: -- PRIVATE - copied from dt_api

1418: -- ----------------------------------------------------------------------------
1419: -- |--------------------------< Get_Delete_Dates >----------------------------|
1420: -- ----------------------------------------------------------------------------
1421: --
1422: -- PRIVATE - copied from dt_api
1423: --
1424: -- Description: Returns the validation start and end dates for the
1425: -- DateTrack DELETE mode if allowed.
1426: --

Line 1821: -- PRIVATE - copied from package dt_api. 20 procedures/functions have been

1817: -- ---------------------------------------------------------------------------
1818: -- |-------------------------< validate_dt_mode >----------------------------|
1819: -- ---------------------------------------------------------------------------
1820: --
1821: -- PRIVATE - copied from package dt_api. 20 procedures/functions have been
1822: -- dopied from dt_api, to get around the invalid column error caused by the
1823: -- assumption in dt_api.lck_child, that a child table's key will be the same
1824: -- name as the parent table's foreign key.
1825: --

Line 1822: -- dopied from dt_api, to get around the invalid column error caused by the

1818: -- |-------------------------< validate_dt_mode >----------------------------|
1819: -- ---------------------------------------------------------------------------
1820: --
1821: -- PRIVATE - copied from package dt_api. 20 procedures/functions have been
1822: -- dopied from dt_api, to get around the invalid column error caused by the
1823: -- assumption in dt_api.lck_child, that a child table's key will be the same
1824: -- name as the parent table's foreign key.
1825: --
1826: -- As these 20 functions are copied for use only with pay_run_type_usages_f,

Line 1823: -- assumption in dt_api.lck_child, that a child table's key will be the same

1819: -- ---------------------------------------------------------------------------
1820: --
1821: -- PRIVATE - copied from package dt_api. 20 procedures/functions have been
1822: -- dopied from dt_api, to get around the invalid column error caused by the
1823: -- assumption in dt_api.lck_child, that a child table's key will be the same
1824: -- name as the parent table's foreign key.
1825: --
1826: -- As these 20 functions are copied for use only with pay_run_type_usages_f,
1827: -- some of the code has been changed slightly to use hard coded values.

Line 2158: dt_api.find_dt_upd_modes

2154: hr_utility.set_location('Entering:'||l_proc, 5);
2155: --
2156: -- Call the corresponding datetrack api
2157: --
2158: dt_api.find_dt_upd_modes
2159: (p_effective_date => p_effective_date
2160: ,p_base_table_name => 'pay_run_types_f'
2161: ,p_base_key_column => 'run_type_id'
2162: ,p_base_key_value => p_base_key_value

Line 2171: -- to dt_api.find_dt_upd_modes, if any of the parameters other than

2167: );
2168: --
2169: -- As run_type_name and shortname are the only updatable columns in the table,
2170: -- and these are limited to update mode of 'CORRECTION', following the call
2171: -- to dt_api.find_dt_upd_modes, if any of the parameters other than
2172: -- p_correction are returned as 'true' then hardcode them to false.
2173: -- NOTE: if columns are added in the future that need to have other update
2174: -- modes, then this will need to be changed.
2175: -- RET 12-DEC-2001 Note: run_type_name is now non-updatable, due to it being

Line 2211: dt_api.find_dt_del_modes

2207: hr_utility.set_location('Entering:'||l_proc, 5);
2208: --
2209: -- Call the corresponding datetrack api
2210: --
2211: dt_api.find_dt_del_modes
2212: (p_effective_date => p_effective_date
2213: ,p_base_table_name => 'pay_run_types_f'
2214: ,p_base_key_column => 'run_type_id'
2215: ,p_base_key_value => p_base_key_value

Line 2247: dt_api.get_object_version_number

2243: -- Because we are updating a row we must get the next object
2244: -- version number.
2245: --
2246: l_object_version_number :=
2247: dt_api.get_object_version_number
2248: (p_base_table_name => 'pay_run_types_f'
2249: ,p_base_key_column => 'run_type_id'
2250: ,p_base_key_value => p_base_key_value
2251: );

Line 2393: dt_api.validate_dt_mode

2389: --
2390: -- Validate the datetrack mode mode getting the validation start
2391: -- and end dates for the specified datetrack operation.
2392: --
2393: dt_api.validate_dt_mode
2394: (p_effective_date => p_effective_date
2395: ,p_datetrack_mode => p_datetrack_mode
2396: ,p_base_table_name => 'pay_run_types_f'
2397: ,p_base_key_column => 'run_type_id'

Line 2409: -- Note: dt_api.validate_dt_mode cannot be used as it assumes that the

2405: ,p_validation_end_date => l_validation_end_date
2406: );
2407: --
2408: -- now call local validate_dt_mode for pay_run_type_usages_f
2409: -- Note: dt_api.validate_dt_mode cannot be used as it assumes that the
2410: -- child table key column has the same name as the parent table fk.
2411: --
2412: validate_dt_mode
2413: (p_effective_date => p_effective_date