DBA Data[Home] [Help]

APPS.JAI_RCV_RT_TRIGGER_PKG dependencies on JAI_RCV_TRANSACTIONS

Line 289: lv_parent_trx_type JAI_RCV_TRANSACTIONS.transaction_type%type;

285:
286: r_mtl_trx c_mtl_trx%ROWTYPE;
287:
288: /* start bgowrava for forward porting Bug#5636560 */
289: lv_parent_trx_type JAI_RCV_TRANSACTIONS.transaction_type%type;
290: CURSOR c_parent_trx_type is
291: SELECT transaction_type
292: from JAI_RCV_TRANSACTIONS
293: where transaction_id = pr_new.parent_transaction_id;

Line 292: from JAI_RCV_TRANSACTIONS

288: /* start bgowrava for forward porting Bug#5636560 */
289: lv_parent_trx_type JAI_RCV_TRANSACTIONS.transaction_type%type;
290: CURSOR c_parent_trx_type is
291: SELECT transaction_type
292: from JAI_RCV_TRANSACTIONS
293: where transaction_id = pr_new.parent_transaction_id;
294: /* End bgowrava for Bug#5636560 */
295:
296: --Function Added by Sanjikum for Bug #4105721

Line 437: Code is modified to populate JAI_RCV_TRANSACTIONS even if the transaction is created through an

433: modified an if condition to assign a proper value to lv_called_from variable. if a wrong value is assigned, then
434: India RTP may not process the transaction
435:
436: 22 25/03/2005 Vijay Shankar for Bug#4250171. Version:115.11
437: Code is modified to populate JAI_RCV_TRANSACTIONS even if the transaction is created through an
438: OPM Receipt/Return. This modification is done, so that VAT Processing of OPM Receipt happens through Discrete code
439:
440: 23 07/04/2005 Harshita for Bug #4285064 Version : 115.12
441:

Line 447: This information is retrieved into our base tables JAI_RCV_TRANSACTIONS and JAI_RCV_LINES.

443: through a DFF : invoice no, invoice_date, Claim Cenvat On Receipt etc.
444: This DFF is provided at two places, header and line.
445: Information from the header DFF is captured into the rcv_shipment_headers table.
446: Information from the lines DFF is captured into the rcv_transactions table.
447: This information is retrieved into our base tables JAI_RCV_TRANSACTIONS and JAI_RCV_LINES.
448: At this time, a facility has been provided for the user to default the information
449: given at the header level DFF to all the lines only if these columns are null at the
450: line level. Else the information in the line level DFF is sustained.
451: For this NVL conditions have been added where this information gets defaulted.

Line 609: jai_rcv_transactions_pkg.insert_row(

605: /* following insert is moved from bottom to here to take care of OPM Functionality also */
606: IF pr_new.transaction_type in ( 'RECEIVE', 'DELIVER', 'RETURN TO RECEIVING',
607: 'RETURN TO VENDOR', 'CORRECT', 'MATCH')
608: THEN
609: jai_rcv_transactions_pkg.insert_row(
610: P_SHIPMENT_HEADER_ID => pr_new.shipment_header_id,
611: P_SHIPMENT_LINE_ID => pr_new.shipment_line_id,
612: P_TRANSACTION_ID => pr_new.transaction_id,
613: P_TRANSACTION_DATE => pr_new.transaction_date,