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.JAI_RCV_RT_TRIGGER_PKG dependencies on JAI_RCV_LINES

Line 335: FROM JAI_RCV_LINES

331: lv_result BOOLEAN;
332:
333: CURSOR c_receipt_line(cp_shipment_line_id IN NUMBER) IS
334: SELECT tax_modified_flag
335: FROM JAI_RCV_LINES
336: WHERE shipment_line_id = cp_shipment_line_id;
337: lv_tax_modified_flag JAI_RCV_LINES.tax_modified_flag%TYPE;
338:
339: v_temp1 VARCHAR2(30);

Line 337: lv_tax_modified_flag JAI_RCV_LINES.tax_modified_flag%TYPE;

333: CURSOR c_receipt_line(cp_shipment_line_id IN NUMBER) IS
334: SELECT tax_modified_flag
335: FROM JAI_RCV_LINES
336: WHERE shipment_line_id = cp_shipment_line_id;
337: lv_tax_modified_flag JAI_RCV_LINES.tax_modified_flag%TYPE;
338:
339: v_temp1 VARCHAR2(30);
340: v_chk_form VARCHAR2(30); -- Vijay Shankar for Bug#3940588. RECEIPTS DEPLUG
341: lv_called_from VARCHAR2(30);

Line 539: - Updates flags of JAI_RCV_LINES with X value. updates transaction_id to MATCH transaction_id in case of

535: - Makes a call to jai_rcv_tax_pkg.default_taxes_onto_line incase of 'RECEIVE', 'UNORDERED', 'MATCH', 'RETURN TO VENDOR' transactions only
536: - a new parameter v_chk_form is added in call to jai_rcv_tax_pkg.default_taxes_onto_line based on which request for JAINRVCTP is submitted
537: incase of RECEIVE transaction
538: - Commented the call to ja_in_set_rvc_process_flags as it is redundant with RECEIPTS DEPLUG from Old Code
539: - Updates flags of JAI_RCV_LINES with X value. updates transaction_id to MATCH transaction_id in case of
540: UNORDERED transaction
541:
542: 19 03/02/2005 Vijay Shankar for Bug# 4159557, Version:115.7
543: Modified the code, so that users will be able to modify taxes of Receipt by Querying it in Localization Screen with the

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 994: UPDATE JAI_RCV_LINES

990: pr_new.attribute15 := null;
991:
992: -- added by Vijay Shankar for Bug#3940588
993: -- following is to take care that the old code will not be executed because
994: UPDATE JAI_RCV_LINES
995: SET
996: process_receiving = 'X', --DECODE(process_receiving, 'Y', 'Y', v_process_receiving),
997: process_delivery = 'X', --DECODE(process_delivery, 'Y', 'Y', v_process_delivery),
998: process_third_party_inv = 'X', --DECODE(process_third_party_inv, 'Y', 'Y', v_process_third_party_inv),