APPS.ARP_PROCESS_RCTS dependencies on AR_PAYMENT_SCHEDULES

Line 279: | ar_payment_schedules |

275: | 28-Dec-98 DJANCIS added call to set posted flag to deterime if |
276: | receipt was posted before deleting it |
277: | 08-Nov-01 DJANCIS Modified for mrc trigger elimination project |
278: | added call to ar_mrc_engine for deletes to |
279: | ar_payment_schedules |
280: +===========================================================================*/
281:
282: PROCEDURE delete_cash_receipt(
283: p_cash_receipt_id IN NUMBER,

Line 314: FROM ar_payment_schedules

310: cash_receipt_id,
311: customer_id,
312: customer_site_use_id,
313: trx_date
314: FROM ar_payment_schedules
315: WHERE cash_receipt_id = p_cash_receipt_id;
316:
317: CURSOR cReceiptDtls IS
318: SELECT receipt_number,

Line 473: DELETE AR_PAYMENT_SCHEDULES

469: CLOSE get_existing_ps;
470:
471: -- delete AR_PAYMENT_SCHEDULE record created for this receipt:
472:
473: DELETE AR_PAYMENT_SCHEDULES
474: WHERE cash_receipt_id = p_cash_receipt_id
475: RETURNING payment_schedule_id
476: BULK COLLECT INTO l_ar_ps_key_value_list;
477:

Line 485: p_table_name => 'AR_PAYMENT_SCHEDULES',

481: +---------------------------------*/
482:
483: ar_mrc_engine.maintain_mrc_data(
484: p_event_mode => 'DELETE',
485: p_table_name => 'AR_PAYMENT_SCHEDULES',
486: p_mode => 'BATCH',
487: p_key_value_list => l_ar_ps_key_value_list);
488: --
489:

Line 877: ar_payment_schedules ps

873: WHERE cr.cash_receipt_id = p_cr_id
874: AND exists
875: (select 1
876: from ar_receivable_applications ra,
877: ar_payment_schedules ps
878: where ra.cash_receipt_id = cr.cash_receipt_id
879: and ra.applied_payment_schedule_id = ps.payment_schedule_id
880: and ps.invoice_currency_code <> cr.currency_code
881: and ra.reversal_gl_date is NULL

Line 899: * in AR_PAYMENT_SCHEDULES table. Also check to see if the CB has

895:
896: /* --------------------------------------------------------------------
897: * Check if a 'CB' was created against this PMT to be reversed.
898: * Check if there are any PMT, ADJ, or CM or CB against this 'CB' records
899: * in AR_PAYMENT_SCHEDULES table. Also check to see if the CB has
900: * already been posted. If any of these 2 conditions is TRUE, then
901: * PMT can only be reversed using DM Reversal.
902: *
903: * Make sure that the adj which is automatically created against the CB

Line 911: FROM ar_payment_schedules ps,

907:
908:
909: SELECT COUNT(payment_schedule_id)
910: INTO l_dummy
911: FROM ar_payment_schedules ps,
912: ra_cust_trx_line_gl_dist rctlg
913: WHERE ps.associated_cash_receipt_id = p_cr_id
914: AND ps.class = 'CB'
915: AND ps.customer_trx_id = rctlg.customer_trx_id