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.ARP_CMERGE_ARTRX dependencies on RA_CUSTOMER_TRX

Line 284: RA_CUSTOMER_TRX.customer_trx_id%TYPE

280: INDEX BY BINARY_INTEGER;
281: MERGE_HEADER_ID_LIST MERGE_HEADER_ID_LIST_TYPE;
282:
283: TYPE customer_trx_id_LIST_TYPE IS TABLE OF
284: RA_CUSTOMER_TRX.customer_trx_id%TYPE
285: INDEX BY BINARY_INTEGER;
286: PRIMARY_KEY_ID_LIST customer_trx_id_LIST_TYPE;
287:
288: TYPE bill_to_customer_id_LIST_TYPE IS TABLE OF

Line 289: RA_CUSTOMER_TRX.bill_to_customer_id%TYPE

285: INDEX BY BINARY_INTEGER;
286: PRIMARY_KEY_ID_LIST customer_trx_id_LIST_TYPE;
287:
288: TYPE bill_to_customer_id_LIST_TYPE IS TABLE OF
289: RA_CUSTOMER_TRX.bill_to_customer_id%TYPE
290: INDEX BY BINARY_INTEGER;
291: NUM_COL1_ORIG_LIST bill_to_customer_id_LIST_TYPE;
292: NUM_COL1_NEW_LIST bill_to_customer_id_LIST_TYPE;
293:

Line 295: RA_CUSTOMER_TRX.bill_to_site_use_id%TYPE

291: NUM_COL1_ORIG_LIST bill_to_customer_id_LIST_TYPE;
292: NUM_COL1_NEW_LIST bill_to_customer_id_LIST_TYPE;
293:
294: TYPE bill_to_site_use_id_LIST_TYPE IS TABLE OF
295: RA_CUSTOMER_TRX.bill_to_site_use_id%TYPE
296: INDEX BY BINARY_INTEGER;
297: NUM_COL2_ORIG_LIST bill_to_site_use_id_LIST_TYPE;
298: NUM_COL2_NEW_LIST bill_to_site_use_id_LIST_TYPE;
299:

Line 301: RA_CUSTOMER_TRX.paying_customer_id%TYPE

297: NUM_COL2_ORIG_LIST bill_to_site_use_id_LIST_TYPE;
298: NUM_COL2_NEW_LIST bill_to_site_use_id_LIST_TYPE;
299:
300: TYPE paying_customer_id_LIST_TYPE IS TABLE OF
301: RA_CUSTOMER_TRX.paying_customer_id%TYPE
302: INDEX BY BINARY_INTEGER;
303: NUM_COL3_ORIG_LIST paying_customer_id_LIST_TYPE;
304: NUM_COL3_NEW_LIST paying_customer_id_LIST_TYPE;
305:

Line 307: RA_CUSTOMER_TRX.paying_site_use_id%TYPE

303: NUM_COL3_ORIG_LIST paying_customer_id_LIST_TYPE;
304: NUM_COL3_NEW_LIST paying_customer_id_LIST_TYPE;
305:
306: TYPE paying_site_use_id_LIST_TYPE IS TABLE OF
307: RA_CUSTOMER_TRX.paying_site_use_id%TYPE
308: INDEX BY BINARY_INTEGER;
309: NUM_COL4_ORIG_LIST paying_site_use_id_LIST_TYPE;
310: NUM_COL4_NEW_LIST paying_site_use_id_LIST_TYPE;
311:

Line 313: RA_CUSTOMER_TRX.ship_to_customer_id%TYPE

309: NUM_COL4_ORIG_LIST paying_site_use_id_LIST_TYPE;
310: NUM_COL4_NEW_LIST paying_site_use_id_LIST_TYPE;
311:
312: TYPE ship_to_customer_id_LIST_TYPE IS TABLE OF
313: RA_CUSTOMER_TRX.ship_to_customer_id%TYPE
314: INDEX BY BINARY_INTEGER;
315: NUM_COL5_ORIG_LIST ship_to_customer_id_LIST_TYPE;
316: NUM_COL5_NEW_LIST ship_to_customer_id_LIST_TYPE;
317:

Line 319: RA_CUSTOMER_TRX.ship_to_site_use_id%TYPE

315: NUM_COL5_ORIG_LIST ship_to_customer_id_LIST_TYPE;
316: NUM_COL5_NEW_LIST ship_to_customer_id_LIST_TYPE;
317:
318: TYPE ship_to_site_use_id_LIST_TYPE IS TABLE OF
319: RA_CUSTOMER_TRX.ship_to_site_use_id%TYPE
320: INDEX BY BINARY_INTEGER;
321: NUM_COL6_ORIG_LIST ship_to_site_use_id_LIST_TYPE;
322: NUM_COL6_NEW_LIST ship_to_site_use_id_LIST_TYPE;
323:

Line 325: RA_CUSTOMER_TRX.sold_to_customer_id%TYPE

321: NUM_COL6_ORIG_LIST ship_to_site_use_id_LIST_TYPE;
322: NUM_COL6_NEW_LIST ship_to_site_use_id_LIST_TYPE;
323:
324: TYPE sold_to_customer_id_LIST_TYPE IS TABLE OF
325: RA_CUSTOMER_TRX.sold_to_customer_id%TYPE
326: INDEX BY BINARY_INTEGER;
327: NUM_COL7_ORIG_LIST sold_to_customer_id_LIST_TYPE;
328: NUM_COL7_NEW_LIST sold_to_customer_id_LIST_TYPE;
329:

Line 331: RA_CUSTOMER_TRX.sold_to_site_use_id%TYPE

327: NUM_COL7_ORIG_LIST sold_to_customer_id_LIST_TYPE;
328: NUM_COL7_NEW_LIST sold_to_customer_id_LIST_TYPE;
329:
330: TYPE sold_to_site_use_id_LIST_TYPE IS TABLE OF
331: RA_CUSTOMER_TRX.sold_to_site_use_id%TYPE
332: INDEX BY BINARY_INTEGER;
333: NUM_COL8_ORIG_LIST sold_to_site_use_id_LIST_TYPE;
334: NUM_COL8_NEW_LIST sold_to_site_use_id_LIST_TYPE;
335: l_profile_val VARCHAR2(30);

Line 347: FROM RA_CUSTOMER_TRX yt, ra_customer_merges m

343: ,ship_to_customer_id
344: ,ship_to_site_use_id
345: ,sold_to_customer_id
346: ,sold_to_site_use_id
347: FROM RA_CUSTOMER_TRX yt, ra_customer_merges m
348: WHERE ( (yt.bill_to_customer_id = m.DUPLICATE_ID AND
349: yt.bill_to_site_use_id = m.DUPLICATE_SITE_ID)
350: OR (yt.paying_customer_id = m.DUPLICATE_ID AND
351: yt.paying_site_use_id = m.DUPLICATE_SITE_ID)

Line 366: ARP_MESSAGE.SET_TOKEN('TABLE_NAME','RA_CUSTOMER_TRX',FALSE);

362: IF process_mode='LOCK' THEN
363: NULL;
364: ELSE
365: ARP_MESSAGE.SET_NAME('AR','AR_UPDATING_TABLE');
366: ARP_MESSAGE.SET_TOKEN('TABLE_NAME','RA_CUSTOMER_TRX',FALSE);
367: HZ_ACCT_MERGE_UTIL.load_set(set_num, req_id);
368: l_profile_val := FND_PROFILE.VALUE('HZ_AUDIT_ACCT_MERGE');
369:
370: open merged_records;

Line 431: 'RA_CUSTOMER_TRX',

427: LAST_UPDATE_LOGIN,
428: LAST_UPDATE_DATE,
429: LAST_UPDATED_BY
430: ) VALUES ( HZ_CUSTOMER_MERGE_LOG_s.nextval,
431: 'RA_CUSTOMER_TRX',
432: MERGE_HEADER_ID_LIST(I),
433: PRIMARY_KEY_ID_LIST(I),
434: NUM_COL1_ORIG_LIST(I),
435: NUM_COL1_NEW_LIST(I),

Line 459: UPDATE RA_CUSTOMER_TRX yt SET

455: hz_utility_pub.LAST_UPDATE_DATE,
456: hz_utility_pub.LAST_UPDATED_BY
457: );
458: END IF; FORALL I in 1..MERGE_HEADER_ID_LIST.COUNT
459: UPDATE RA_CUSTOMER_TRX yt SET
460: bill_to_customer_id=NUM_COL1_NEW_LIST(I)
461: ,bill_to_site_use_id=NUM_COL2_NEW_LIST(I)
462: ,paying_customer_id=NUM_COL3_NEW_LIST(I)
463: ,paying_site_use_id=NUM_COL4_NEW_LIST(I)