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.

[Home] [Help]

APPS.HRDYNDBI dependencies on FF_DATABASE_ITEMS_TL

Line 161: ff_database_items_tl rows (other child

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

Line 219: to FF_DATABASE_ITEMS_TL.

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

Line 1289: l_tl_name ff_database_items_tl.translated_user_name%type;

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

Line 2169: -- FF_DATABASE_ITEMS_TL, or FF_CONTEXT rows.

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

Line 2262: -- FF_DATABASE_ITEMS_TL, or FF_CONTEXT rows.

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

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

8056: )
8057: )
8058: or exists
8059: (
8060: select /*+ ORDERED INDEX(a FF_DATABASE_ITEMS_TL_N2)
8061: INDEX(b FF_USER_ENTITIES_PK) */ null
8062: from ff_database_items_tl a,
8063: ff_user_entities b
8064: where a.translated_user_name = p_user_name

Line 8062: from ff_database_items_tl a,

8058: or exists
8059: (
8060: select /*+ ORDERED INDEX(a FF_DATABASE_ITEMS_TL_N2)
8061: INDEX(b FF_USER_ENTITIES_PK) */ null
8062: from ff_database_items_tl a,
8063: ff_user_entities b
8064: where a.translated_user_name = p_user_name
8065: and (a.user_name <> p_user_name or a.user_entity_id <> p_ue_id)
8066: and a.user_entity_id = b.user_entity_id

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

8682: --
8683: -- check_for_tl_dbi_clash
8684: --
8685: -- This keeps the database item clash checking code in one place.
8686: -- This is for additions to FF_DATABASE_ITEMS_TL.
8687: -- It also checks G_TRIGGERS_ALTERED.
8688: -- The code does not bother with FF_GLOBALS_F as that's the
8689: -- same as checking against database items.
8690: --

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

8763: )
8764: )
8765: or exists
8766: (
8767: select /*+ ORDERED INDEX(a FF_DATABASE_ITEMS_TL_N2)
8768: INDEX(b FF_USER_ENTITIES_PK) */ null
8769: from ff_database_items_tl a,
8770: ff_user_entities b
8771: where a.translated_user_name = p_tl_user_name

Line 8769: from ff_database_items_tl a,

8765: or exists
8766: (
8767: select /*+ ORDERED INDEX(a FF_DATABASE_ITEMS_TL_N2)
8768: INDEX(b FF_USER_ENTITIES_PK) */ null
8769: from ff_database_items_tl a,
8770: ff_user_entities b
8771: where a.translated_user_name = p_tl_user_name
8772: and (a.user_name <> p_user_name or a.user_entity_id <> p_user_entity_id)
8773: and a.user_entity_id = b.user_entity_id

Line 8895: l_tl_user_name ff_database_items_tl.translated_user_name%type;

8891: ,p_language in varchar2
8892: ,p_tl_user_name in varchar2
8893: ) is
8894: l_clash boolean;
8895: l_tl_user_name ff_database_items_tl.translated_user_name%type;
8896: l_got_error boolean;
8897: begin
8898: --
8899: -- G_TRIGGERS_ALTERED is true for the bulk generation of balance,

Line 8921: update ff_database_items_tl dbitl

8917: ,p_clash => l_clash
8918: );
8919:
8920: if not l_clash then
8921: update ff_database_items_tl dbitl
8922: set dbitl.translated_user_name = l_tl_user_name
8923: , dbitl.source_lang = p_language
8924: where dbitl.language = p_language
8925: and dbitl.user_name = p_user_name

Line 8999: l_tl_name ff_database_items_tl.translated_user_name%type;

8995: ,p_suffix in varchar2
8996: ,p_date_p in varchar2
8997: ) is
8998: --
8999: l_tl_name ff_database_items_tl.translated_user_name%type;
9000: begin
9001: for i in 1 .. p_prefixes.count loop
9002: if p_prefixes(i).found then
9003: --

Line 9043: l_tl_name ff_database_items_tl.translated_user_name%type;

9039: l_bal_id pay_defined_balances.balance_type_id%type;
9040: l_baldim_id pay_defined_balances.balance_dimension_id%type;
9041: l_base_name ff_database_items.user_name%type;
9042: l_ueid number;
9043: l_tl_name ff_database_items_tl.translated_user_name%type;
9044: l_found boolean;
9045: l_startup_mode varchar2(30);
9046: begin
9047: --