[Home] [Help]
151: p_confirm_date,
152: l_acctd_amount,
153: l_receipt_clearing_ccid);
154:
155: -- call do_confirm to process the individual applications and
156: -- update the payment schedule of the receipt.
157: -- Note: This functionality was grouped together in one function,
158: -- because it basically represents the functionality of the
159: -- confirm user exit in Rel. 10. Do_confirm is called from
295: l_acctd_amount,
296: l_batch_id,
297: l_crh_id_rev);
298:
299: -- call do_unconfirm to process the individual applications and
300: -- update the payment schedule of the receipt.
301: -- Note: This functionality was grouped together in one function,
302: -- because it basically represents the functionality of the
303: -- confirm user exit in Rel. 10. Do_unconfirm is called from
1454: FOR l_unapp_rec in get_rec_records LOOP
1455:
1456: --Retrieve sequence id for receivable application id of UNAPP record
1457: --Note as this procedure creates a single UNAPP record hence this kind
1458: --of select from dual for sequence id is done
1459:
1460: SELECT ar_receivable_applications_s.nextval
1461: INTO l_unapp_id
1462: FROM dual;
1458: --of select from dual for sequence id is done
1459:
1460: SELECT ar_receivable_applications_s.nextval
1461: INTO l_unapp_id
1462: FROM dual;
1463:
1464: --Insert negative UNAPP record for confirmed APP record
1465: INSERT INTO ar_receivable_applications (
1466: receivable_application_id,
2095:
2096: --retrieve sequence
2097: SELECT ar_receivable_applications_s.nextval
2098: INTO l_new_app_id
2099: FROM dual;
2100:
2101: --Create actual reversing apps
2102: INSERT INTO ar_receivable_applications
2103: (receivable_application_id,