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.PQH_TEM_BUS dependencies on PQH_TRANSACTION_CATEGORIES

Line 246: l_freeze_status_cd pqh_transaction_categories.freeze_status_cd%type;

242: --
243: l_proc varchar2(72) := g_package||'chk_transaction_category_id';
244: l_api_updating boolean;
245: l_dummy varchar2(1);
246: l_freeze_status_cd pqh_transaction_categories.freeze_status_cd%type;
247: --
248: cursor c1 is
249: select nvl(freeze_status_cd,hr_api.g_varchar2)
250: from pqh_transaction_categories_vl a

Line 250: from pqh_transaction_categories_vl a

246: l_freeze_status_cd pqh_transaction_categories.freeze_status_cd%type;
247: --
248: cursor c1 is
249: select nvl(freeze_status_cd,hr_api.g_varchar2)
250: from pqh_transaction_categories_vl a
251: where a.transaction_category_id = p_transaction_category_id;
252: --
253: Begin
254: --

Line 268: -- pqh_transaction_categories table

264: <> nvl(pqh_tem_shd.g_old_rec.transaction_category_id,hr_api.g_number)
265: or not l_api_updating) then
266: --
267: -- check if transaction_category_id value exists in
268: -- pqh_transaction_categories table
269: --
270: open c1;
271: --
272: fetch c1 into l_freeze_status_cd;

Line 278: -- raise error as FK does not relate to PK in pqh_transaction_categories

274: if c1%notfound then
275: --
276: close c1;
277: --
278: -- raise error as FK does not relate to PK in pqh_transaction_categories
279: -- table.
280: --
281: pqh_tem_shd.constraint_error('PQH_TEMPLATES_FK');
282: --