Results for “dates_negative_tolerance”

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

Overview

OE_SHIP_TO_ORGS_V is a read-only view owned by the APPS schema in Oracle E-Business Suite, defined within the Order Management (ONT) product family. Its documented purpose is to present "Ship To Organizations." In practice, it exposes ship-to site information as organization-like records, allowing callers to resolve the ship-to organizations associated with a customer account and site. The view is available in both 12.1.1 and 12.2.2, with a status of VALID in the 12.2.2 data dictionary.

The view exists primarily to support reporting and integration. It supplies a stable, denormalized shape over the Oracle Receivables/HZ customer model and, importantly, carries the Order Management shipping attributes that drive order entry and scheduling behaviour. Because it flattens customer account, site use and location data into a single result set, it is convenient for extracts, LOV-style lookups and custom reports that need ship-to context without joining four or more base tables manually.

Underlying Base Objects

The documented base objects for this view are HZ_CUST_ACCT_SITES, HZ_CUST_SITE_USES_ALL, HZ_LOCATIONS and HZ_PARTY_SITES, all referenced through APPS synonyms. These are the Trading Community Architecture (TCA) entities that hold customer accounts, their site uses, address details and party-site relationships respectively.

The definition selects from HZ_CUST_SITE_USES_ALL (aliased SITE), joined outward to HZ_CUST_ACCT_SITES (aliased ACCT_SITE) and HZ_LOCATIONS (aliased LOC). The site use row supplies the ship-to identification, shipping controls and tolerance attributes, while the account-site and location rows supply the customer account identifier and the formatted address components. The view presents each site use as an "organization," mapping SITE_USE_ID to both ORGANIZATION_ID and LOCATION_ID, and SITE.LOCATION to NAME and LOCATION_CODE. Many legacy columns such as BUSINESS_GROUP_ID, COST_ALLOCATION_KEYFLEX_ID, TYPE and the ATTRIBUTE1–20 series are explicitly projected as NULL to preserve a fixed column layout.

Key Columns

• ORGANIZATION_ID / LOCATION_ID / SITE_USE_ID — all populated from SITE.SITE_USE_ID, giving the ship-to identity.
• SITE.CUST_ACCT_SITE_ID and ACCT_SITE.CUST_ACCOUNT_ID — link the ship-to back to the account site and customer account.
• OVER_SHIPMENT_TOLERANCE, UNDER_SHIPMENT_TOLERANCE — permitted quantity variances at the ship-to.
• DATES_NEGATIVE_TOLERANCE, DATES_POSITIVE_TOLERANCE, DATE_TYPE_PREFERENCE — the date tolerance controls, which are frequently referenced when users search for scheduling and ship-date windows.
• OVER_RETURN_TOLERANCE — return quantity tolerance.
• PRICE_LIST_ID, PAYMENT_TERM_ID — default pricing and terms for the site.
• FOB_POINT_CODE, FREIGHT_TERMS_CODE, SHIPPING_METHOD_CODE — shipping defaults derived from FOB_POINT, FREIGHT_TERM and SHIP_VIA.
• SHIP_PARTIAL_ALLOWED — partial shipment flag.
• SOLD_FROM_ORG_ID / SHIP_FROM_ORG_ID — both sourced from SITE.WAREHOUSE_ID.
• ADDRESS_LINE_1..4, TOWN_OR_CITY, POSTAL_CODE, COUNTRY — formatted location columns.

Common Use Cases and Queries

Typical uses include resolving the ship-to organization for an order, extracting shipping tolerances for downstream planning, and validating freight and FOB defaults. A common query retrieves the date tolerance and shipping controls for a customer account:

• SELECT organization_id, name, over_shipment_tolerance, under_shipment_tolerance, dates_negative_tolerance, dates_positive_tolerance, date_type_preference FROM oe_ship_to_orgs_v WHERE cust_account_id = :p_account_id;
• SELECT organization_id, location_code, fob_point_code, freight_terms_code, shipping_method_code FROM oe_ship_to_orgs_v WHERE status = 'A';

Because the view inherits TCA site-use rows, filters on STATUS, PRIMARY_FLAG and warehouse identifiers are the usual ways to narrow results to active, primary or organization-specific ship-to records.