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.ARW_SEARCH_CUSTOMERS dependencies on HZ_PARTIES

Line 30: hz_parties party

26: -1 org_id,
27: 'N' selected,
28: TO_CHAR(NULL) location
29: FROM hz_cust_accounts cust,
30: hz_parties party
31: WHERE cust.party_id = party.party_id AND
32: cust.cust_account_id = p_customer_id
33:
34: UNION ALL

Line 56: HZ_PARTIES HP

52: -- HZ_LOC_ASSIGNMENTS LOC_ASSIGN ,
53: HZ_LOCATIONS LOC ,
54: FND_TERRITORIES_VL T,
55: HZ_CUST_ACCOUNTS HCA,
56: HZ_PARTIES HP
57: WHERE ACCT_SITE.PARTY_SITE_ID = PARTY_SITE.PARTY_SITE_ID
58: AND LOC.LOCATION_ID = PARTY_SITE.LOCATION_ID
59: AND PARTY_SITE.PARTY_ID = HCA.PARTY_ID
60: AND HCA.CUST_ACCOUNT_ID = ACCT_SITE.CUST_ACCOUNT_ID

Line 90: hz_parties party,

86: 'N' selected,
87: '' location
88: FROM
89: hz_cust_accounts cus,
90: hz_parties party,
91: ra_customer_trx ct
92: WHERE
93: ct.trx_number = p_search_criteria
94: and ct.bill_to_customer_id = cus.cust_account_id

Line 114: hz_parties party

110: -1 org_id,
111: 'N' selected,
112: TO_CHAR(NULL) location
113: FROM hz_cust_accounts cust,
114: hz_parties party
115: WHERE cust.party_id = party.party_id AND
116: cust.ACCOUNT_NUMBER LIKE p_customer_name_number
117:
118: UNION

Line 134: hz_parties party

130: -1 org_id,
131: 'N' selected,
132: TO_CHAR(NULL) location
133: FROM hz_cust_accounts cust,
134: hz_parties party
135: WHERE cust.party_id = party.party_id
136: AND party.PARTY_NAME LIKE p_customer_name_number
137: )
138:

Line 160: HZ_PARTIES HP

156: -- HZ_LOC_ASSIGNMENTS LOC_ASSIGN ,
157: HZ_LOCATIONS LOC ,
158: FND_TERRITORIES_VL T,
159: HZ_CUST_ACCOUNTS HCA,
160: HZ_PARTIES HP
161: WHERE ACCT_SITE.PARTY_SITE_ID = PARTY_SITE.PARTY_SITE_ID
162: AND LOC.LOCATION_ID = PARTY_SITE.LOCATION_ID
163: AND PARTY_SITE.PARTY_ID = HCA.PARTY_ID
164: AND HCA.CUST_ACCOUNT_ID = ACCT_SITE.CUST_ACCOUNT_ID

Line 195: HZ_PARTIES HP

191: -- HZ_LOC_ASSIGNMENTS LOC_ASSIGN ,
192: HZ_LOCATIONS LOC ,
193: FND_TERRITORIES_VL T,
194: HZ_CUST_ACCOUNTS HCA,
195: HZ_PARTIES HP
196: WHERE ACCT_SITE.PARTY_SITE_ID = PARTY_SITE.PARTY_SITE_ID
197: AND LOC.LOCATION_ID = PARTY_SITE.LOCATION_ID
198: AND PARTY_SITE.PARTY_ID = HCA.PARTY_ID
199: AND HCA.CUST_ACCOUNT_ID = ACCT_SITE.CUST_ACCOUNT_ID

Line 218: -- hz_parties.

214: --
215: -- srajasek 06-APR-00 Changed ra_addresses_all to hz_cust_acct_sites_all because of tca changes in 11.5.1
216:
217: -- modified for tca uptake. replaced ra_customers with hz_cust_accounts and
218: -- hz_parties.
219:
220: -- Bug 2094233
221: -- krmenon 28 Dec 2001 Removed the order by clause for performance issues
222: /*--

Line 229: hz_parties party,

225: CURSOR ctx_cur (p_keyword VARCHAR2) IS
226: SELECT adr.cust_acct_site_id address_id, adr.cust_account_id customer_id, score(1) total_score
227: FROM hz_cust_acct_sites_all adr,
228: hz_cust_accounts cus,
229: hz_parties party,
230: ar_system_parameters_all sys
231: WHERE ctxsys.CONTAINS (address_text, NVL(p_keyword, '%') , 1) > 0
232: AND adr.cust_account_id = cus.cust_account_id
233: AND cus.party_id = party.party_id