Search Results discount_amount_taken

Overview

The JL_BR_AP_INVOICES_SHIP_V view is a Latin America Localizations (JL) database object owned by the APPS schema, provided as part of the Brazilian Payables localization functionality within Oracle E-Business Suite 12.1.1 and 12.2.2. As indicated by its documented status of "Retrofitted," the object is a legacy construct that has been carried forward into the current release line, with its definition aligned to the AP_INVOICES entity identifier columns rather than contributing new business logic of its own.

Functionally, the view exposes the core Payables invoice record together with shipping-relevant attributes such as freight amount, goods received date, and invoice received date. In practice, the view acts as a lightweight projection over the standard Oracle Payables invoice table, allowing Brazilian localization reports, concurrent programs, and outbound integrations to retrieve invoice header information without joining the broader AP_INVOICES_ALL structures directly. Because it is a simple view defined against a synonym, it carries no independent storage and inherits the read consistency, security, and performance characteristics of the underlying transaction table.

Underlying Base Objects

The documented referenced base objects for JL_BR_AP_INVOICES_SHIP_V are AP_INVOICES and AP_TERMS, both accessed through public synonyms in the APPS schema. The view text selects from AP_INVOICES using the alias APIN, taking the row identifier along with a comprehensive list of invoice header columns. The join to AP_TERMS on the payment terms identifier supplies the terms-related context used by the Brazilian localization for due date and settlement reporting.

Because the view is defined over a synonym rather than the base table directly, it remains insulated from physical table reorganizations and continues to resolve against the multi-organization partitioned invoice table in 12.2.2. The object retains its VALID status, confirming that the definition compiles cleanly in both the 12.1.1 and 12.2.2 code lines. No additional localization-specific tables are documented as contributing to this view, so its content is entirely a function of the standard Payables invoice header and terms data.

Key Columns

• INVOICE_ID — Primary identifier of the invoice header, used for all downstream joins.
• INVOICE_NUM — The supplier-facing invoice number entered or imported into Payables.
• VENDOR_ID / VENDOR_SITE_ID — Supplier and supplier site identifiers associated with the invoice.
• INVOICE_DATE / GOODS_RECEIVED_DATE / INVOICE_RECEIVED_DATE — Key dates supporting localization tax and reporting logic.
• INVOICE_AMOUNT / BASE_AMOUNT / TAX_AMOUNT / FREIGHT_AMOUNT — Monetary amounts in entered and functional currency, including the shipping-related freight component.
• APPROVAL_STATUS / APPROVAL_DESCRIPTION — The approval state and its textual description, directly relevant to the search term "approval_description."
• PAYMENT_STATUS_FLAG / PAYMENT_METHOD_LOOKUP_CODE — Payment state and method used for settlement reporting.
• DESCRIPTION / ATTRIBUTE1–15 / ATTRIBUTE_CATEGORY — Descriptive and flexfield-attribute columns available for localization-specific data capture.

Common Use Cases and Queries

Typical consumption patterns involve identifying invoices requiring approval attention, reconciling freight and received-date values for Brazilian reporting, and extracting approval status for integration feeds. The following query retrieves approval context for invoices within a date range:

SELECT invoice_id, invoice_num, vendor_id, invoice_date, approval_status, approval_description, invoice_amount
FROM apps.jl_br_ap_invoices_ship_v
WHERE invoice_date BETWEEN :p_start AND :p_end
AND approval_status = 'N';

A second common pattern joins the view back to AP_TERMS for terms-based aging, using the terms identifier exposed by the view to reconcile due dates for localization settlement reports. Because the view does not enforce organization security by itself, callers should restrict results using the operating unit context where the underlying Payables security model requires it.