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_PROC_RCT_UTIL dependencies on AR_RECEIVABLE_APPLICATIONS

Line 261: | Creates a new record in AR_RECEIVABLE_APPLICATIONS table for a cash |

257: | PROCEDURE |
258: | insert_ra_rec_cash |
259: | |
260: | DESCRIPTION |
261: | Creates a new record in AR_RECEIVABLE_APPLICATIONS table for a cash |
262: | receipt. |
263: | |
264: | SCOPE : PRIVATE |
265: | |

Line 292: | AR_RECEIVABLE_APPLICATIONS |

288: | impact for the existing functionality. |
289: | 03-Sep-2002 Debbie Jancis Modified for MRC trigger replacement |
290: | Added calls to AR_MRC_ENGINE3 for |
291: | for processing inserts into |
292: | AR_RECEIVABLE_APPLICATIONS |
293: | |
294: +===========================================================================*/
295:
296: PROCEDURE insert_ra_rec_cash(

Line 302: ar_receivable_applications.acctd_amount_applied_from%TYPE,

298: p_amount IN ar_cash_receipts.amount%TYPE,
299: p_apply_date IN DATE,
300: p_status IN ar_cash_receipts.status%TYPE,
301: p_acctd_amount IN
302: ar_receivable_applications.acctd_amount_applied_from%TYPE,
303: p_gl_date IN DATE,
304: p_ccid IN
305: ar_receivable_applications.code_combination_id%TYPE,
306: p_payment_schedule_id IN

Line 305: ar_receivable_applications.code_combination_id%TYPE,

301: p_acctd_amount IN
302: ar_receivable_applications.acctd_amount_applied_from%TYPE,
303: p_gl_date IN DATE,
304: p_ccid IN
305: ar_receivable_applications.code_combination_id%TYPE,
306: p_payment_schedule_id IN
307: ar_payment_schedules.payment_schedule_id%TYPE,
308: p_application_rule IN ar_receivable_applications.application_rule%TYPE,
309: p_reversal_gl_date IN DATE default null,

Line 308: p_application_rule IN ar_receivable_applications.application_rule%TYPE,

304: p_ccid IN
305: ar_receivable_applications.code_combination_id%TYPE,
306: p_payment_schedule_id IN
307: ar_payment_schedules.payment_schedule_id%TYPE,
308: p_application_rule IN ar_receivable_applications.application_rule%TYPE,
309: p_reversal_gl_date IN DATE default null,
310: p_ra_id OUT NOCOPY ar_receivable_applications.receivable_application_id%TYPE,
311: p_called_from IN VARCHAR2 DEFAULT NULL -- jrautiai BR project
312: ) IS

Line 310: p_ra_id OUT NOCOPY ar_receivable_applications.receivable_application_id%TYPE,

306: p_payment_schedule_id IN
307: ar_payment_schedules.payment_schedule_id%TYPE,
308: p_application_rule IN ar_receivable_applications.application_rule%TYPE,
309: p_reversal_gl_date IN DATE default null,
310: p_ra_id OUT NOCOPY ar_receivable_applications.receivable_application_id%TYPE,
311: p_called_from IN VARCHAR2 DEFAULT NULL -- jrautiai BR project
312: ) IS
313:
314: l_ra_rec ar_receivable_applications%ROWTYPE;

Line 314: l_ra_rec ar_receivable_applications%ROWTYPE;

310: p_ra_id OUT NOCOPY ar_receivable_applications.receivable_application_id%TYPE,
311: p_called_from IN VARCHAR2 DEFAULT NULL -- jrautiai BR project
312: ) IS
313:
314: l_ra_rec ar_receivable_applications%ROWTYPE;
315: l_ra_id ar_receivable_applications.receivable_application_id%TYPE;
316: --BUG#2750340
317: l_xla_ev_rec arp_xla_events.xla_events_type;
318:

Line 315: l_ra_id ar_receivable_applications.receivable_application_id%TYPE;

311: p_called_from IN VARCHAR2 DEFAULT NULL -- jrautiai BR project
312: ) IS
313:
314: l_ra_rec ar_receivable_applications%ROWTYPE;
315: l_ra_id ar_receivable_applications.receivable_application_id%TYPE;
316: --BUG#2750340
317: l_xla_ev_rec arp_xla_events.xla_events_type;
318:
319: BEGIN