Results for “bill_to_province”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

ECE_MVSTO_LOCATIONS_V is a private, active view owned by the APPS schema and registered under the EC — e-Commerce Gateway product, with an underlying inventory (INV) reporting product designation and a display name of "Movement Statistics Line Location View." Its documented purpose is to extract line location information for the outbound Movement Statistics (INTRASTAT) transaction. INTRASTAT is the statistical reporting system used within the European Union to track the movement of goods between member states, and Oracle EBS implements the corresponding outbound transaction through the e-Commerce Gateway so that qualifying shipment and receipt lines can be reported to the relevant statistical authority.

The view consolidates the three party contexts that participate in a movement statistics line — bill-to, ship-to, and vendor — into a single denormalized row. This is significant for users searching on terms such as ship_to_address1, because the view exposes SHIP_TO_ADDRESS1 directly rather than requiring a join back to HZ_LOCATIONS. The view does not store data; it is purely a read construct, so it is safe to query for extracts, custom reports, and reconciliation without risk of writing to EBS base tables.

Underlying Base Objects

The ETRM documentation for 12.2.2 lists the following referenced base objects: FND_GLOBAL (PACKAGE), HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_LOCATIONS, HZ_PARTIES, HZ_PARTY_SITES (all synonyms), plus the PO_VENDORS and PO_VENDOR_SITES views. The view text joins HZ_PARTIES to HZ_CUST_ACCOUNTS to resolve party name and internal customer identifiers, then to HZ_CUST_ACCT_SITES_ALL and HZ_CUST_SITE_USES_ALL to obtain site-use context, and finally to HZ_LOCATIONS for the address attributes. Vendor-side columns come from PO_VENDORS and PO_VENDOR_SITES. FND_GLOBAL supplies runtime session context such as organization or user, consistent with self-service and gateway extract behavior.

Key Columns

The column set follows a consistent naming convention per party role:

• BILL_TO_: BILL_TO_CODE_INTERNAL, BILL_TO_CODE_EXTERNAL, BILL_TO_NAME, BILL_TO_ADDRESS1 through BILL_TO_ADDRESS4, BILL_TO_CITY, BILL_TO_POSTAL_CODE, BILL_TO_COUNTRY, BILL_TO_STATE, BILL_TO_PROVINCE, BILL_TO_COUNTY, BILL_TO_ADDRESS_ID, BILL_TO_CUSTOMER_ID, BILL_TO_SITE_USE_ID.
• SHIP_TO_: SHIP_TO_ADDRESS1 is the column users most often search for; it is populated from LC2.ADDRESS1 in HZ_LOCATIONS. Also exposed are SHIP_TO_CODE_INTERNAL, SHIP_TO_CODE_EXTERNAL, SHIP_TO_NAME, addresses 2–4, city, postal code, country, state, province, county, plus SHIP_TO_ADDRESS_ID, SHIP_TO_CUSTOMER_ID, and SHIP_TO_SITE_USE_ID.
• VENDOR_: VENDOR_CODE_INT, VENDOR_CODE_EXT, VENDOR_CUSTOMER_NAME, VENDOR_ADDRESS1–4, VENDOR_CITY, VENDOR_POSTAL_CODE, and country/state/province/county variants derived from PO_VENDOR_SITES.
• TRANSACTION_HEADER_ID / TRANSACTION_LINE_ID: defined as NULL in the documented view text.

Common Use Cases and Queries

Typical uses include pre-extract validation for the INTRASTAT outbound gateway interface, investigation of missing or malformed addresses that cause gateway rejects, and ad hoc reporting that needs both ship-to and bill-to detail in one row. The following query targets the searched column:

• SELECT ship_to_name, ship_to_address1, ship_to_city, ship_to_postal_code, ship_to_country FROM apps.ece_mvsto_locations_v WHERE ship_to_address1 IS NULL; — identifies ship-to records lacking a primary address line.
• SELECT ship_to_code_external, bill_to_code_external, vendor_code_ext FROM apps.ece_mvsto_locations_v WHERE ship_to_postal_code IS NOT NULL; — supports code cross-checking across bill-to, ship-to, and vendor.

Because the view is a read-only projection, developers can safely embed it in BI Publisher datasets and OAF/ADF queries.