APPS.JAI_RCV_RT_TRIGGER_PKG dependencies on JAI_RCV_TRANSACTIONS

Line 358: lv_parent_trx_type JAI_RCV_TRANSACTIONS.transaction_type%type;

354:
355: r_mtl_trx c_mtl_trx%ROWTYPE;
356:
357: /* start bgowrava for forward porting Bug#5636560 */
358: lv_parent_trx_type JAI_RCV_TRANSACTIONS.transaction_type%type;
359: CURSOR c_parent_trx_type is
360: SELECT transaction_type
361: from JAI_RCV_TRANSACTIONS
362: where transaction_id = pr_new.parent_transaction_id;

Line 361: from JAI_RCV_TRANSACTIONS

357: /* start bgowrava for forward porting Bug#5636560 */
358: lv_parent_trx_type JAI_RCV_TRANSACTIONS.transaction_type%type;
359: CURSOR c_parent_trx_type is
360: SELECT transaction_type
361: from JAI_RCV_TRANSACTIONS
362: where transaction_id = pr_new.parent_transaction_id;
363: /* End bgowrava for Bug#5636560 */
364: /*Bug 14010660 - Start*/
365: CURSOR c_excise_inv_number(p_shipment_header_id NUMBER)

Line 410: FROM jai_rcv_transactions

406: /* Added for bug #14852106*//*Start*/
407: CURSOR get_claim_details(p_shipment_line_id NUMBER)
408: IS
409: SELECT CENVAT_AMOUNT, CENVAT_CLAIMED_PTG
410: FROM jai_rcv_transactions
411: WHERE shipment_line_id = p_shipment_line_id
412: AND transaction_type = 'RECEIVE';
413:
414: ln_cenvat_amt NUMBER := 0;

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

555: modified an if condition to assign a proper value to lv_called_from variable. if a wrong value is assigned, then
556: India RTP may not process the transaction
557:
558: 22 25/03/2005 Vijay Shankar for Bug#4250171. Version:115.11
559: Code is modified to populate JAI_RCV_TRANSACTIONS even if the transaction is created through an
560: OPM Receipt/Return. This modification is done, so that VAT Processing of OPM Receipt happens through Discrete code
561:
562: 23 07/04/2005 Harshita for Bug #4285064 Version : 115.12
563:

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

565: through a DFF : invoice no, invoice_date, Claim Cenvat On Receipt etc.
566: This DFF is provided at two places, header and line.
567: Information from the header DFF is captured into the rcv_shipment_headers table.
568: Information from the lines DFF is captured into the rcv_transactions table.
569: This information is retrieved into our base tables JAI_RCV_TRANSACTIONS and JAI_RCV_LINES.
570: At this time, a facility has been provided for the user to default the information
571: given at the header level DFF to all the lines only if these columns are null at the
572: line level. Else the information in the line level DFF is sustained.
573: For this NVL conditions have been added where this information gets defaulted.

Line 746: jai_rcv_transactions_pkg.insert_row(

742: /* following insert is moved from bottom to here to take care of OPM Functionality also */
743: IF pr_new.transaction_type in ( 'RECEIVE', 'DELIVER', 'RETURN TO RECEIVING',
744: 'RETURN TO VENDOR', 'CORRECT', 'MATCH')
745: THEN
746: jai_rcv_transactions_pkg.insert_row(
747: P_SHIPMENT_HEADER_ID => pr_new.shipment_header_id,
748: P_SHIPMENT_LINE_ID => pr_new.shipment_line_id,
749: P_TRANSACTION_ID => pr_new.transaction_id,
750: P_TRANSACTION_DATE => pr_new.transaction_date,