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 279: -- PRIVATE - copied from dt_api

275: -- ----------------------------------------------------------------------------
276: -- |------------------------< Return_Max_End_Date >---------------------------|
277: -- ----------------------------------------------------------------------------
278: --
279: -- PRIVATE - copied from dt_api
280: --
281: -- Description: Function returns the maximum effective_end_date for the
282: -- specified table and primary key.
283: -- NOTE: if the maximum end date doesn't exist (i.e. no rows

Line 737: -- PRIVATE - copied from dt_api

733: -- ----------------------------------------------------------------------------
734: -- |-----------------------< Lck_Future_Rows >--------------------------------|
735: -- ----------------------------------------------------------------------------
736: --
737: -- PRIVATE - copied from dt_api
738: --
739: -- Description: Locks the entity from the effective_date to the end-of-time.
740: -- No processing will be completed if the p_key_value is
741: -- null because the column could be defined as nullable.

Line 846: -- PRIVATE - copied from dt_api

842: -- ----------------------------------------------------------------------------
843: -- |----------------------------< Lck_Child >---------------------------------|
844: -- ----------------------------------------------------------------------------
845: --
846: -- PRIVATE - copied from dt_api
847: --
848: -- Description: Locks the specified child entity maximum row for the specified
849: -- parent key value:
850: --

Line 965: -- PRIVATE - copied from dt_api

961: -- ----------------------------------------------------------------------------
962: -- |-------------------------< Get_Insert_Dates >-----------------------------|
963: -- ----------------------------------------------------------------------------
964: --
965: -- PRIVATE - copied from dt_api
966: --
967: -- Description: Locks and parental entity rows (if supplied) and Returns
968: -- the validation start and end dates for the DateTrack
969: -- INSERT mode

Line 1445: -- PRIVATE - copied from dt_api

1441: -- ----------------------------------------------------------------------------
1442: -- |--------------------------< Get_Delete_Dates >----------------------------|
1443: -- ----------------------------------------------------------------------------
1444: --
1445: -- PRIVATE - copied from dt_api
1446: --
1447: -- Description: Returns the validation start and end dates for the
1448: -- DateTrack DELETE mode if allowed.
1449: --

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

1840: -- ---------------------------------------------------------------------------
1841: -- |-------------------------< validate_dt_mode >----------------------------|
1842: -- ---------------------------------------------------------------------------
1843: --
1844: -- PRIVATE - copied from package dt_api. 20 procedures/functions have been
1845: -- dopied from dt_api, to get around the invalid column error caused by the
1846: -- assumption in dt_api.lck_child, that a child table's key will be the same
1847: -- name as the parent table's foreign key.
1848: --

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

1841: -- |-------------------------< validate_dt_mode >----------------------------|
1842: -- ---------------------------------------------------------------------------
1843: --
1844: -- PRIVATE - copied from package dt_api. 20 procedures/functions have been
1845: -- dopied from dt_api, to get around the invalid column error caused by the
1846: -- assumption in dt_api.lck_child, that a child table's key will be the same
1847: -- name as the parent table's foreign key.
1848: --
1849: -- As these 20 functions are copied for use only with pay_run_type_usages_f,

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

1842: -- ---------------------------------------------------------------------------
1843: --
1844: -- PRIVATE - copied from package dt_api. 20 procedures/functions have been
1845: -- dopied from dt_api, to get around the invalid column error caused by the
1846: -- assumption in dt_api.lck_child, that a child table's key will be the same
1847: -- name as the parent table's foreign key.
1848: --
1849: -- As these 20 functions are copied for use only with pay_run_type_usages_f,
1850: -- some of the code has been changed slightly to use hard coded values.

Line 2181: dt_api.find_dt_upd_modes

2177: hr_utility.set_location('Entering:'||l_proc, 5);
2178: --
2179: -- Call the corresponding datetrack api
2180: --
2181: dt_api.find_dt_upd_modes
2182: (p_effective_date => p_effective_date
2183: ,p_base_table_name => 'pay_run_types_f'
2184: ,p_base_key_column => 'run_type_id'
2185: ,p_base_key_value => p_base_key_value

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

2190: );
2191: --
2192: -- As run_type_name and shortname are the only updatable columns in the table,
2193: -- and these are limited to update mode of 'CORRECTION', following the call
2194: -- to dt_api.find_dt_upd_modes, if any of the parameters other than
2195: -- p_correction are returned as 'true' then hardcode them to false.
2196: -- NOTE: if columns are added in the future that need to have other update
2197: -- modes, then this will need to be changed.
2198: -- RET 12-DEC-2001 Note: run_type_name is now non-updatable, due to it being

Line 2234: dt_api.find_dt_del_modes

2230: hr_utility.set_location('Entering:'||l_proc, 5);
2231: --
2232: -- Call the corresponding datetrack api
2233: --
2234: dt_api.find_dt_del_modes
2235: (p_effective_date => p_effective_date
2236: ,p_base_table_name => 'pay_run_types_f'
2237: ,p_base_key_column => 'run_type_id'
2238: ,p_base_key_value => p_base_key_value

Line 2270: dt_api.get_object_version_number

2266: -- Because we are updating a row we must get the next object
2267: -- version number.
2268: --
2269: l_object_version_number :=
2270: dt_api.get_object_version_number
2271: (p_base_table_name => 'pay_run_types_f'
2272: ,p_base_key_column => 'run_type_id'
2273: ,p_base_key_value => p_base_key_value
2274: );

Line 2416: dt_api.validate_dt_mode

2412: --
2413: -- Validate the datetrack mode mode getting the validation start
2414: -- and end dates for the specified datetrack operation.
2415: --
2416: dt_api.validate_dt_mode
2417: (p_effective_date => p_effective_date
2418: ,p_datetrack_mode => p_datetrack_mode
2419: ,p_base_table_name => 'pay_run_types_f'
2420: ,p_base_key_column => 'run_type_id'

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

2428: ,p_validation_end_date => l_validation_end_date
2429: );
2430: --
2431: -- now call local validate_dt_mode for pay_run_type_usages_f
2432: -- Note: dt_api.validate_dt_mode cannot be used as it assumes that the
2433: -- child table key column has the same name as the parent table fk.
2434: --
2435: validate_dt_mode
2436: (p_effective_date => p_effective_date