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.

[Home] [Help]

APPS.AP_IMPORT_UTILITIES_PKG dependencies on STANDARD

Line 1583: shipment_type could be 'PREPAYMENT' or 'STANDARD'. For 'PREPAYMENT'

1579: /*-----------------------------------------------------------------------------------------+
1580: --For the case of complex works, following scenarios are possible:
1581: 1.Matching Basis at PO Line = 'AMOUNT' and
1582: shipments could have matching_basis of 'QUANTITY'/'AMOUNT'. And within that
1583: shipment_type could be 'PREPAYMENT' or 'STANDARD'. For 'PREPAYMENT'
1584: we need to go off of financed columns and
1585: for 'STANDARD' we need to go off of Billed columns.
1586: 2.Matching Basis at PO Line = 'QUANTITY'
1587: and then shipments can have the matching basis of only 'QUANTITY'. And within that

Line 1585: for 'STANDARD' we need to go off of Billed columns.

1581: 1.Matching Basis at PO Line = 'AMOUNT' and
1582: shipments could have matching_basis of 'QUANTITY'/'AMOUNT'. And within that
1583: shipment_type could be 'PREPAYMENT' or 'STANDARD'. For 'PREPAYMENT'
1584: we need to go off of financed columns and
1585: for 'STANDARD' we need to go off of Billed columns.
1586: 2.Matching Basis at PO Line = 'QUANTITY'
1587: and then shipments can have the matching basis of only 'QUANTITY'. And within that
1588: shipment_type could be 'PREPAYMENT' or 'STANDARD'. For 'PREPAYMENT'
1589: we need to go off of financed columns and

Line 1588: shipment_type could be 'PREPAYMENT' or 'STANDARD'. For 'PREPAYMENT'

1584: we need to go off of financed columns and
1585: for 'STANDARD' we need to go off of Billed columns.
1586: 2.Matching Basis at PO Line = 'QUANTITY'
1587: and then shipments can have the matching basis of only 'QUANTITY'. And within that
1588: shipment_type could be 'PREPAYMENT' or 'STANDARD'. For 'PREPAYMENT'
1589: we need to go off of financed columns and
1590: for 'STANDARD' we need to go off of Billed columns.
1591: +------------------------------------------------------------------------------------------*/
1592:

Line 1590: for 'STANDARD' we need to go off of Billed columns.

1586: 2.Matching Basis at PO Line = 'QUANTITY'
1587: and then shipments can have the matching basis of only 'QUANTITY'. And within that
1588: shipment_type could be 'PREPAYMENT' or 'STANDARD'. For 'PREPAYMENT'
1589: we need to go off of financed columns and
1590: for 'STANDARD' we need to go off of Billed columns.
1591: +------------------------------------------------------------------------------------------*/
1592:
1593: SELECT
1594: DECODE(pl.matching_basis, 'QUANTITY',

Line 2088: by the user, then "Standard Invoices" category will be used for

2084: invoice will be rejected for 'Override Disabled', if the user populates
2085: AP_INVOICES_INTERFACE.DOC_CATEGORY_CODE (and override is "No").
2086:
2087: If the profile value is "Always" and no document category is specified
2088: by the user, then "Standard Invoices" category will be used for
2089: standard invoices and "Credit Memo Invoices" category will be used
2090: for credits.
2091: We assume that a valid automatic sequence exists for such categories.
2092:

Line 2089: standard invoices and "Credit Memo Invoices" category will be used

2085: AP_INVOICES_INTERFACE.DOC_CATEGORY_CODE (and override is "No").
2086:
2087: If the profile value is "Always" and no document category is specified
2088: by the user, then "Standard Invoices" category will be used for
2089: standard invoices and "Credit Memo Invoices" category will be used
2090: for credits.
2091: We assume that a valid automatic sequence exists for such categories.
2092:
2093: If the payables option of Invoice Document Category override is

Line 2110: If the document category is "Standard Invoices" and the invoice amount

2106: 'REC INV',
2107: 'WIRE PAY',
2108: 'EXP REP INV')
2109:
2110: If the document category is "Standard Invoices" and the invoice amount
2111: is less than zero, or, the document category is "Credit Memo Invoices"
2112: and the invoice amount is greated than zero then the invoice will be
2113: rejected for 'Invalid Category'.
2114:

Line 2221: p_invoice_rec.invoice_type_lookup_code <> 'STANDARD')

2217: -- Contract Payments: Modified the below IF condition to add logic for
2218: -- 'Prepayment' type invoices.
2219:
2220: IF ( ( p_invoice_rec.doc_category_code = 'STD INV' and
2221: p_invoice_rec.invoice_type_lookup_code <> 'STANDARD')
2222: OR
2223: ( p_invoice_rec.doc_category_code = 'PAY REQ INV' and
2224: p_invoice_rec.invoice_type_lookup_code <> 'PAYMENT REQUEST')
2225: OR

Line 2355: IF (p_invoice_rec.invoice_type_lookup_code = 'STANDARD') THEN

2351: --Contract Payments: Modified the IF condition to look at the invoice_type
2352: --rather than the sign of the invoice_amount in deciding which category to
2353: --apply, and also added the logic for 'PREPAYMENT' invoices.
2354:
2355: IF (p_invoice_rec.invoice_type_lookup_code = 'STANDARD') THEN
2356: l_doc_category_code := 'STD INV';
2357: ELSIF (p_invoice_rec.invoice_type_lookup_code = 'PAYMENT REQUEST') THEN
2358: l_doc_category_code := 'PAY REQ INV';
2359: ELSIF (p_invoice_rec.invoice_type_lookup_code = 'CREDIT') THEN