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.HZ_BES_BO_UTIL_PKG dependencies on HZ_CUST_ACCT_SITES_ALL

Line 2103: 1. HZ_CUST_ACCT_SITES_ALL (CUST_ACCT_SITE)

2099: p_module =>'ei_actsiteuse');
2100: END IF;
2101: /*
2102: HZ_CUST_SITE_USES_ALL has following parent
2103: 1. HZ_CUST_ACCT_SITES_ALL (CUST_ACCT_SITE)
2104:
2105: Hence, HZ_CUST_SITE_USES_ALL can exist in 3 different scenarios.
2106: The different combinations of (parent, grand parent) are :
2107: 1. (CUST_ACCT_SITE, CUST_ACCT)

Line 2152: child_bo: CUST_ACCT_SITE_USE, parent_bo: CUST_ACCT_SITE, parent_entity_name: HZ_CUST_ACCT_SITES_ALL,

2148: example:
2149:
2150: child record:
2151: child_id: 123, child_entity_name: HZ_CUST_SITE_USES_ALL,
2152: child_bo: CUST_ACCT_SITE_USE, parent_bo: CUST_ACCT_SITE, parent_entity_name: HZ_CUST_ACCT_SITES_ALL,
2153: parent_id: 234
2154:
2155: The "inner select" fetches above record from BOT and identifies
2156: its parent, grand parent information and present it as follows:

Line 2159: parent_entity_name aliased as child_entity_name: HZ_CUST_ACCT_SITES_ALL

2155: The "inner select" fetches above record from BOT and identifies
2156: its parent, grand parent information and present it as follows:
2157:
2158: parent_id aliased as child_id: 234
2159: parent_entity_name aliased as child_entity_name: HZ_CUST_ACCT_SITES_ALL
2160: parent_bo aliased as child_bo: CUST_ACCT_SITE
2161: grand_parent_id aliased as parent id: 456
2162: grand_parent_entity_name aliased as parent_entity_name: HZ_CUST_ACCOUNTS
2163: grand_parent_bo aliased as parent_bo: CUST_ACCT

Line 2167: child_id: 234, child_entity_name: HZ_CUST_ACCT_SITES_ALL,

2163: grand_parent_bo aliased as parent_bo: CUST_ACCT
2164:
2165: Insert statement will take this result and write it as
2166: child record:
2167: child_id: 234, child_entity_name: HZ_CUST_ACCT_SITES_ALL,
2168: child_bo: CUST_ACCT_SITE, parent_bo: CUST_ACCT, parent_entity_name: HZ_CUST_ACCOUNTS,
2169: parent_id: 456
2170: 6. It is non-trivial to figure out the business object codes for both parent
2171: and grand parent, grand parent identifier or grand parent entity name.

Line 2202: FROM HZ_BUS_OBJ_TRACKING t, HZ_CUST_ACCT_SITES_ALL s

2198: ,t.LAST_UPDATE_DATE
2199: ,RANK()
2200: OVER (PARTITION BY PARENT_BO_CODE, PARENT_ID
2201: ORDER BY t.LAST_UPDATE_DATE, child_id) as acrrank
2202: FROM HZ_BUS_OBJ_TRACKING t, HZ_CUST_ACCT_SITES_ALL s
2203: WHERE t.CHILD_ENTITY_NAME = 'HZ_CUST_SITE_USES_ALL'
2204: AND t.event_id IS NULL
2205: AND t.parent_id = s.CUST_ACCT_SITE_ID) temp
2206: WHERE NOT EXISTS

Line 2236: Procedure name: PROCEDURE ei_HZ_CUST_ACCT_SITES_ALL()

2232: RAISE FND_API.G_EXC_UNEXPECTED_ERROR;
2233: END ei_HZ_CUST_SITE_USES_ALL;
2234: -----------------------------------------------------------------
2235: /*
2236: Procedure name: PROCEDURE ei_HZ_CUST_ACCT_SITES_ALL()
2237: Purpose: Writes the parent node record for HZ_CUST_ACCT_SITES_ALL in BOT
2238: Scope: internal
2239: Called From: This pkg
2240: Called By: populate_missing_links()

Line 2237: Purpose: Writes the parent node record for HZ_CUST_ACCT_SITES_ALL in BOT

2233: END ei_HZ_CUST_SITE_USES_ALL;
2234: -----------------------------------------------------------------
2235: /*
2236: Procedure name: PROCEDURE ei_HZ_CUST_ACCT_SITES_ALL()
2237: Purpose: Writes the parent node record for HZ_CUST_ACCT_SITES_ALL in BOT
2238: Scope: internal
2239: Called From: This pkg
2240: Called By: populate_missing_links()
2241: */

Line 2244: PROCEDURE ei_HZ_CUST_ACCT_SITES_ALL IS

2240: Called By: populate_missing_links()
2241: */
2242: -----------------------------------------------------------------
2243:
2244: PROCEDURE ei_HZ_CUST_ACCT_SITES_ALL IS
2245:
2246: -- local variables
2247: l_debug_prefix VARCHAR2(40) := 'EI_HZ_CUST_ACCT_SITES_ALL';
2248:

Line 2247: l_debug_prefix VARCHAR2(40) := 'EI_HZ_CUST_ACCT_SITES_ALL';

2243:
2244: PROCEDURE ei_HZ_CUST_ACCT_SITES_ALL IS
2245:
2246: -- local variables
2247: l_debug_prefix VARCHAR2(40) := 'EI_HZ_CUST_ACCT_SITES_ALL';
2248:
2249: BEGIN
2250: IF fnd_log.level_procedure>=fnd_log.g_current_runtime_level THEN
2251: hz_utility_v2pub.DEBUG

Line 2252: (p_message=>'ei_HZ_CUST_ACCT_SITES_ALL+',

2248:
2249: BEGIN
2250: IF fnd_log.level_procedure>=fnd_log.g_current_runtime_level THEN
2251: hz_utility_v2pub.DEBUG
2252: (p_message=>'ei_HZ_CUST_ACCT_SITES_ALL+',
2253: p_prefix=>l_debug_prefix,
2254: p_msg_level=>fnd_log.level_procedure,
2255: p_module_prefix => 'HZ_BES_BO_UTIL_PKG',
2256: p_module =>'ei_actsite');

Line 2259: HZ_CUST_ACCT_SITES_ALL has following parent

2255: p_module_prefix => 'HZ_BES_BO_UTIL_PKG',
2256: p_module =>'ei_actsite');
2257: END IF;
2258: /*
2259: HZ_CUST_ACCT_SITES_ALL has following parent
2260: 1. HZ_CUST_ACCOUNTS (CUST_ACCT)
2261:
2262: Hence, HZ_CUST_ACCT_SITES_ALL can exist in 2 different scenarios.
2263: The different combinations of (parent, grand parent) are :

Line 2262: Hence, HZ_CUST_ACCT_SITES_ALL can exist in 2 different scenarios.

2258: /*
2259: HZ_CUST_ACCT_SITES_ALL has following parent
2260: 1. HZ_CUST_ACCOUNTS (CUST_ACCT)
2261:
2262: Hence, HZ_CUST_ACCT_SITES_ALL can exist in 2 different scenarios.
2263: The different combinations of (parent, grand parent) are :
2264: 1. (CUST_ACCT, PERSON_CUST) -- tested
2265: 2. (CUST_ACCT, ORG_CUST) -- tested
2266:

Line 2267: The following SQL gets the Parent and Grand parent info of each HZ_CUST_ACCT_SITES_ALL

2263: The different combinations of (parent, grand parent) are :
2264: 1. (CUST_ACCT, PERSON_CUST) -- tested
2265: 2. (CUST_ACCT, ORG_CUST) -- tested
2266:
2267: The following SQL gets the Parent and Grand parent info of each HZ_CUST_ACCT_SITES_ALL
2268: record that was not already processed in BOT.
2269:
2270: Test Cases for the following SQL are:
2271: Create HZ_CUST_ACCT_SITES_ALL rec in BOT with (Parent, Grand Parent)

Line 2271: Create HZ_CUST_ACCT_SITES_ALL rec in BOT with (Parent, Grand Parent)

2267: The following SQL gets the Parent and Grand parent info of each HZ_CUST_ACCT_SITES_ALL
2268: record that was not already processed in BOT.
2269:
2270: Test Cases for the following SQL are:
2271: Create HZ_CUST_ACCT_SITES_ALL rec in BOT with (Parent, Grand Parent)
2272: combinations existing in TCA data model
2273: 1. (CUST_ACCT, PERSON_CUST) -- tested
2274: 2. (CUST_ACCT, ORG_CUST) -- tested
2275: */

Line 2306: child_id: 123, child_entity_name: HZ_CUST_ACCT_SITES_ALL,

2302:
2303: example:
2304:
2305: child record:
2306: child_id: 123, child_entity_name: HZ_CUST_ACCT_SITES_ALL,
2307: child_bo: CUST_ACCT_SITE, parent_bo: CUST_ACCT, parent_entity_name: HZ_CUST_ACCOUNTS,
2308: parent_id: 234
2309:
2310: The "inner select" fetches above record from BOT and identifies

Line 2351: WHERE t.CHILD_ENTITY_NAME = 'HZ_CUST_ACCT_SITES_ALL'

2347: ,RANK()
2348: OVER (PARTITION BY PARENT_BO_CODE, PARENT_ID
2349: ORDER BY t.LAST_UPDATE_DATE, child_id) as acrrank
2350: FROM HZ_BUS_OBJ_TRACKING t, HZ_CUST_ACCOUNTS ac, HZ_PARTIES p
2351: WHERE t.CHILD_ENTITY_NAME = 'HZ_CUST_ACCT_SITES_ALL'
2352: AND t.event_id IS NULL
2353: AND t.parent_id = ac.CUST_ACCOUNT_ID
2354: AND ac.party_id = p.party_id) temp
2355: WHERE NOT EXISTS

Line 2369: (p_message=>'ei_HZ_CUST_ACCT_SITES_ALL-',

2365: -- save the records populated
2366: COMMIT;
2367: IF fnd_log.level_procedure>=fnd_log.g_current_runtime_level THEN
2368: hz_utility_v2pub.DEBUG
2369: (p_message=>'ei_HZ_CUST_ACCT_SITES_ALL-',
2370: p_prefix=>l_debug_prefix,
2371: p_msg_level=>fnd_log.level_procedure,
2372: p_module_prefix => 'HZ_BES_BO_UTIL_PKG',
2373: p_module =>'ei_actsite');

Line 2378: LOG( message => 'ei_HZ_CUST_ACCT_SITES_ALL:'||SQLERRM,

2374: END IF;
2375: EXCEPTION
2376: WHEN OTHERS THEN
2377: ROLLBACK;
2378: LOG( message => 'ei_HZ_CUST_ACCT_SITES_ALL:'||SQLERRM,
2379: p_prefix =>l_debug_prefix,
2380: p_module =>'ei_actsite');
2381: RAISE FND_API.G_EXC_UNEXPECTED_ERROR;
2382: END ei_HZ_CUST_ACCT_SITES_ALL;

Line 2382: END ei_HZ_CUST_ACCT_SITES_ALL;

2378: LOG( message => 'ei_HZ_CUST_ACCT_SITES_ALL:'||SQLERRM,
2379: p_prefix =>l_debug_prefix,
2380: p_module =>'ei_actsite');
2381: RAISE FND_API.G_EXC_UNEXPECTED_ERROR;
2382: END ei_HZ_CUST_ACCT_SITES_ALL;
2383: -----------------------------------------------------------------
2384: /*
2385: Procedure name: PROCEDURE ei_HZ_CUST_ACCOUNT_ROLES()
2386: Purpose: Writes the parent node record for HZ_CUST_ACCOUNT_ROLES in BOT

Line 2409: 1. HZ_CUST_ACCT_SITES_ALL (CUST_ACCT_SITE)

2405: p_module =>'ei_actroles');
2406: END IF;
2407: /*
2408: Party Site has following parents
2409: 1. HZ_CUST_ACCT_SITES_ALL (CUST_ACCT_SITE)
2410: 2. HZ_CUST_ACCOUNTS (CUST_ACCT)
2411:
2412: Hence, HZ_CUST_ACCOUNT_ROLES can exist in 3 different scenarios.
2413: The different combinations of (parent, grand parent) are :

Line 2459: child_bo: CUST_ACCT_CONTACT, parent_bo: CUST_ACCT_SITE, parent_entity_name: HZ_CUST_ACCT_SITES_ALL,

2455: example:
2456:
2457: child record:
2458: child_id: 123, child_entity_name: HZ_CUST_ACCOUNT_ROLES,
2459: child_bo: CUST_ACCT_CONTACT, parent_bo: CUST_ACCT_SITE, parent_entity_name: HZ_CUST_ACCT_SITES_ALL,
2460: parent_id: 234
2461:
2462: The "inner select" fetches above record from BOT and identifies
2463: its parent, grand parent information and present it as follows:

Line 2466: parent_entity_name aliased as child_entity_name: HZ_CUST_ACCT_SITES_ALL

2462: The "inner select" fetches above record from BOT and identifies
2463: its parent, grand parent information and present it as follows:
2464:
2465: parent_id aliased as child_id: 234
2466: parent_entity_name aliased as child_entity_name: HZ_CUST_ACCT_SITES_ALL
2467: parent_bo aliased as child_bo: CUST_ACCT_SITE
2468: grand_parent_id aliased as parent id: 456
2469: grand_parent_entity_name aliased as parent_entity_name: HZ_CUST_ACCOUNTS
2470: grand_parent_bo aliased as parent_bo: CUST_ACCT

Line 2474: child_id: 234, child_entity_name: HZ_CUST_ACCT_SITES_ALL,

2470: grand_parent_bo aliased as parent_bo: CUST_ACCT
2471:
2472: Insert statement will take this result and write it as
2473: child record:
2474: child_id: 234, child_entity_name: HZ_CUST_ACCT_SITES_ALL,
2475: child_bo: CUST_ACCT_SITE, parent_bo: CUST_ACCT, parent_entity_name: HZ_CUST_ACCOUNTS,
2476: parent_id: 456
2477: 6. It is non-trivial to figure out the business object codes for both parent
2478: and grand parent, grand parent identifier or grand parent entity name.

Line 2514: FROM HZ_CUST_ACCT_SITES_ALL

2510: END parent_entity_name -- this is grand parent tbl name of acct roles, written as parent entity name
2511: ,CASE PARENT_BO_CODE
2512: WHEN 'CUST_ACCT_SITE' THEN
2513: (SELECT CUST_ACCOUNT_ID
2514: FROM HZ_CUST_ACCT_SITES_ALL
2515: WHERE CUST_ACCT_SITE_ID = PARENT_ID)
2516: WHEN 'CUST_ACCT' THEN
2517: (SELECT PARTY_ID
2518: FROM HZ_CUST_ACCOUNTS

Line 2804: grand_parent_entity_name aliased as parent_entity_name: HZ_CUST_ACCT_SITES_ALL

2800: parent_id aliased as child_id: 234
2801: parent_entity_name aliased as child_entity_name: HZ_CUST_ACCT_SITE_USES_ALL
2802: parent_bo aliased as child_bo: CUST_ACCT_SITE_USE
2803: grand_parent_id aliased as parent id: 456
2804: grand_parent_entity_name aliased as parent_entity_name: HZ_CUST_ACCT_SITES_ALL
2805: grand_parent_bo aliased as parent_bo: CUST_ACCT_SITE
2806:
2807: Insert statement will take this result and write it as
2808: child record:

Line 2810: child_bo: CUST_ACCT_SITE_USE, parent_bo: CUST_ACCT_SITE, parent_entity_name: HZ_CUST_ACCT_SITES_ALL,

2806:
2807: Insert statement will take this result and write it as
2808: child record:
2809: child_id: 234, child_entity_name: HZ_CUST_ACCT_SITE_USES_ALL,
2810: child_bo: CUST_ACCT_SITE_USE, parent_bo: CUST_ACCT_SITE, parent_entity_name: HZ_CUST_ACCT_SITES_ALL,
2811: parent_id: 456
2812: 6. It is non-trivial to figure out the business object codes for both parent
2813: and grand parent, grand parent identifier or grand parent entity name.
2814: To do this, "inner select" uses case statement on parent_entity_name.

Line 2842: WHEN 'CUST_ACCT_SITE_USE' THEN 'HZ_CUST_ACCT_SITES_ALL'

2838: ,RANK()
2839: OVER (PARTITION BY PARENT_BO_CODE, PARENT_ID
2840: ORDER BY LAST_UPDATE_DATE, child_id) as acrrank
2841: ,CASE PARENT_BO_CODE
2842: WHEN 'CUST_ACCT_SITE_USE' THEN 'HZ_CUST_ACCT_SITES_ALL'
2843: WHEN 'CUST_ACCT' THEN 'HZ_PARTIES'
2844: ELSE NULL
2845: END parent_entity_name -- this is grand parent tbl name of acct roles, written as parent entity name
2846: ,CASE PARENT_BO_CODE

Line 3437: 15. HZ_CUST_ACCT_SITES_ALL

3433: 11. HZ_ORG_PROFILES_EXT_VL
3434: 12. HZ_CUST_ACCOUNT_ROLES
3435: 13. HZ_CUSTOMER_PROFILES
3436: 14. HZ_CUST_SITE_USES_ALL
3437: 15. HZ_CUST_ACCT_SITES_ALL
3438: 16. HZ_CUST_ACCOUNTS
3439: */
3440: -- Insert the parent record
3441: -- 1. HZ_CONTACT_PREFERENCES

Line 3665: -- 15. HZ_CUST_ACCT_SITES_ALL

3661: p_module =>'pop_missing_lnks');
3662: END IF;
3663:
3664: ei_HZ_CUST_SITE_USES_ALL;
3665: -- 15. HZ_CUST_ACCT_SITES_ALL
3666: /*
3667: LOG(
3668: message => 'bfr calling ei_HZ_CUST_ACCT_SITES_ALL()',
3669: p_prefix =>l_debug_prefix,

Line 3668: message => 'bfr calling ei_HZ_CUST_ACCT_SITES_ALL()',

3664: ei_HZ_CUST_SITE_USES_ALL;
3665: -- 15. HZ_CUST_ACCT_SITES_ALL
3666: /*
3667: LOG(
3668: message => 'bfr calling ei_HZ_CUST_ACCT_SITES_ALL()',
3669: p_prefix =>l_debug_prefix,
3670: p_module => l_module);
3671: */
3672: IF fnd_log.level_procedure>=fnd_log.g_current_runtime_level THEN

Line 3674: (p_message=>'bfr calling ei_HZ_CUST_ACCT_SITES_ALL()',

3670: p_module => l_module);
3671: */
3672: IF fnd_log.level_procedure>=fnd_log.g_current_runtime_level THEN
3673: hz_utility_v2pub.DEBUG
3674: (p_message=>'bfr calling ei_HZ_CUST_ACCT_SITES_ALL()',
3675: p_prefix=>l_debug_prefix,
3676: p_msg_level=>fnd_log.level_procedure,
3677: p_module_prefix => 'HZ_BES_BO_UTIL_PKG',
3678: p_module =>'pop_missing_lnks');

Line 3681: ei_HZ_CUST_ACCT_SITES_ALL;

3677: p_module_prefix => 'HZ_BES_BO_UTIL_PKG',
3678: p_module =>'pop_missing_lnks');
3679: END IF;
3680:
3681: ei_HZ_CUST_ACCT_SITES_ALL;
3682: -- 16. HZ_CUST_ACCOUNTS
3683: /*
3684: LOG(
3685: message => 'bfr calling ei_HZ_CUST_ACCOUNTS()',