[Home] [Help]
152: p_confirm_date,
153: l_acctd_amount,
154: l_receipt_clearing_ccid);
155:
156: -- call do_confirm to process the individual applications and
157: -- update the payment schedule of the receipt.
158: -- Note: This functionality was grouped together in one function,
159: -- because it basically represents the functionality of the
160: -- confirm user exit in Rel. 10. Do_confirm is called from
312: l_acctd_amount,
313: l_batch_id,
314: l_crh_id_rev);
315:
316: -- call do_unconfirm to process the individual applications and
317: -- update the payment schedule of the receipt.
318: -- Note: This functionality was grouped together in one function,
319: -- because it basically represents the functionality of the
320: -- confirm user exit in Rel. 10. Do_unconfirm is called from
1471: FOR l_unapp_rec in get_rec_records LOOP
1472:
1473: --Retrieve sequence id for receivable application id of UNAPP record
1474: --Note as this procedure creates a single UNAPP record hence this kind
1475: --of select from dual for sequence id is done
1476:
1477: SELECT ar_receivable_applications_s.nextval
1478: INTO l_unapp_id
1479: FROM dual;
1475: --of select from dual for sequence id is done
1476:
1477: SELECT ar_receivable_applications_s.nextval
1478: INTO l_unapp_id
1479: FROM dual;
1480:
1481: --Insert negative UNAPP record for confirmed APP record
1482: INSERT INTO ar_receivable_applications (
1483: receivable_application_id,
2112:
2113: --retrieve sequence
2114: SELECT ar_receivable_applications_s.nextval
2115: INTO l_new_app_id
2116: FROM dual;
2117:
2118: --Create actual reversing apps
2119: INSERT INTO ar_receivable_applications
2120: (receivable_application_id,