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.HRDYNDBI dependencies on FF_DATABASE_ITEMS_TL

Line 164: ff_database_items_tl rows (other child

160: database item translation from
161: process_pay_dyndbi_changes.
162: arashid 115.138 09-MAY-2006 Don't disable ff_user_entities delete
163: triggers as thay are required to delete
164: ff_database_items_tl rows (other child
165: rows are cascade deleted).
166: arashid 115.137 05-MAY-2006 Use substr to restrict names to 80
167: characters in routines that generate base
168: dbi names - this is to match the main

Line 222: to FF_DATABASE_ITEMS_TL.

218: 5. Changed code for generating element,
219: input, and defined balance DBIs to
220: handle full MLS where it is supported.
221: 6. Added update_xxx calls for MLS updates
222: to FF_DATABASE_ITEMS_TL.
223: Updates to FP.K and earlier should be
224: branched on 115.28.
225: alogue 115.128 07-OCT-2005 Performance fix to sel_ffci in
226: create_alternative_dbis. Bug 4658377.

Line 1292: l_tl_name ff_database_items_tl.translated_user_name%type;

1288:
1289: l_legislation_code varchar2(30);
1290: l_full_mls boolean;
1291: l_found boolean;
1292: l_tl_name ff_database_items_tl.translated_user_name%type;
1293: --
1294: begin
1295: --
1296: IF (g_triggers_altered) THEN

Line 2172: -- FF_DATABASE_ITEMS_TL, or FF_CONTEXT rows.

2168: IF c_dbi_exists%NOTFOUND then
2169: BEGIN
2170: --
2171: -- Make sure that the name does not clash with FF_DATABASE_ITEMS,
2172: -- FF_DATABASE_ITEMS_TL, or FF_CONTEXT rows.
2173: --
2174: check_for_dbi_clash
2175: (p_user_name => l_user_name
2176: ,p_ue_id => l_user_entity_id

Line 2265: -- FF_DATABASE_ITEMS_TL, or FF_CONTEXT rows.

2261: IF c_dbi_exists%NOTFOUND then
2262: BEGIN
2263: --
2264: -- Make sure that the name does not clash with FF_DATABASE_ITEMS,
2265: -- FF_DATABASE_ITEMS_TL, or FF_CONTEXT rows.
2266: --
2267: check_for_dbi_clash
2268: (p_user_name => l_user_name
2269: ,p_ue_id => l_user_entity_id

Line 8137: select /*+ ORDERED INDEX(a FF_DATABASE_ITEMS_TL_N2)

8133: )
8134: )
8135: or exists
8136: (
8137: select /*+ ORDERED INDEX(a FF_DATABASE_ITEMS_TL_N2)
8138: INDEX(b FF_USER_ENTITIES_PK) */ null
8139: from ff_database_items_tl a,
8140: ff_user_entities b
8141: where a.translated_user_name = p_user_name

Line 8139: from ff_database_items_tl a,

8135: or exists
8136: (
8137: select /*+ ORDERED INDEX(a FF_DATABASE_ITEMS_TL_N2)
8138: INDEX(b FF_USER_ENTITIES_PK) */ null
8139: from ff_database_items_tl a,
8140: ff_user_entities b
8141: where a.translated_user_name = p_user_name
8142: and (a.user_name <> p_user_name or a.user_entity_id <> p_ue_id)
8143: and a.user_entity_id = b.user_entity_id

Line 8763: -- This is for additions to FF_DATABASE_ITEMS_TL.

8759: --
8760: -- check_for_tl_dbi_clash
8761: --
8762: -- This keeps the database item clash checking code in one place.
8763: -- This is for additions to FF_DATABASE_ITEMS_TL.
8764: -- It also checks G_TRIGGERS_ALTERED.
8765: -- The code does not bother with FF_GLOBALS_F as that's the
8766: -- same as checking against database items.
8767: --

Line 8844: select /*+ ORDERED INDEX(a FF_DATABASE_ITEMS_TL_N2)

8840: )
8841: )
8842: or exists
8843: (
8844: select /*+ ORDERED INDEX(a FF_DATABASE_ITEMS_TL_N2)
8845: INDEX(b FF_USER_ENTITIES_PK) */ null
8846: from ff_database_items_tl a,
8847: ff_user_entities b
8848: where a.translated_user_name = p_tl_user_name

Line 8846: from ff_database_items_tl a,

8842: or exists
8843: (
8844: select /*+ ORDERED INDEX(a FF_DATABASE_ITEMS_TL_N2)
8845: INDEX(b FF_USER_ENTITIES_PK) */ null
8846: from ff_database_items_tl a,
8847: ff_user_entities b
8848: where a.translated_user_name = p_tl_user_name
8849: and (a.user_name <> p_user_name or a.user_entity_id <> p_user_entity_id)
8850: and a.user_entity_id = b.user_entity_id

Line 8972: l_tl_user_name ff_database_items_tl.translated_user_name%type;

8968: ,p_language in varchar2
8969: ,p_tl_user_name in varchar2
8970: ) is
8971: l_clash boolean;
8972: l_tl_user_name ff_database_items_tl.translated_user_name%type;
8973: l_got_error boolean;
8974: begin
8975: --
8976: -- G_TRIGGERS_ALTERED is true for the bulk generation of balance,

Line 8998: update ff_database_items_tl dbitl

8994: ,p_clash => l_clash
8995: );
8996:
8997: if not l_clash then
8998: update ff_database_items_tl dbitl
8999: set dbitl.translated_user_name = l_tl_user_name
9000: , dbitl.source_lang = p_language
9001: where dbitl.language = p_language
9002: and dbitl.user_name = p_user_name

Line 9076: l_tl_name ff_database_items_tl.translated_user_name%type;

9072: ,p_suffix in varchar2
9073: ,p_date_p in varchar2
9074: ) is
9075: --
9076: l_tl_name ff_database_items_tl.translated_user_name%type;
9077: begin
9078: for i in 1 .. p_prefixes.count loop
9079: if p_prefixes(i).found then
9080: --

Line 9120: l_tl_name ff_database_items_tl.translated_user_name%type;

9116: l_bal_id pay_defined_balances.balance_type_id%type;
9117: l_baldim_id pay_defined_balances.balance_dimension_id%type;
9118: l_base_name ff_database_items.user_name%type;
9119: l_ueid number;
9120: l_tl_name ff_database_items_tl.translated_user_name%type;
9121: l_found boolean;
9122: l_startup_mode varchar2(30);
9123: begin
9124: --