Results for “freight_org_id”

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

Overview

APPS.WSH_CAL_ASG_DETAIL_V is a Shipping Execution (WSH) view that consolidates calendar assignments to vendor sites and vendor locations into a single denormalized result set. It presents, for each calendar assignment record held in WSH_CALENDAR_ASSIGNMENTS, the associated trading partner identity, the site or location name, and the full set of calendar attributes (calendar code, calendar type, enabled flag, freight code, freight organization, and descriptive flexfield attribute columns). The view is the reporting and integration surface through which Oracle Shipping, transportation planning, and downstream carrier-selection logic determine which pickup, drop-off, or transit calendar governs a given vendor site or vendor location.

The view is implemented as a UNION of two branches. The first branch resolves assignments whose ASSOCIATION_TYPE is VENDOR_SITE; the second resolves assignments whose ASSOCIATION_TYPE is VENDOR_LOCATION. Both branches emit a literal 'VENDOR' as the second column, a constant –1 as the third, and NULL as the fourth, producing a stable, uniform projection across both association types. The view's descriptive comment records a change driven by HR_LOCATIONS under Bug 1924581, dated 8/15/01, reflecting the historical migration of location data into the HR and HZ schemas.

Underlying Base Objects

The documented base objects for the view are WSH_CALENDAR_ASSIGNMENTS (synonym), PO_VENDORS (view), PO_VENDOR_SITES_ALL (view), HR_ORGANIZATION_UNITS (view), WSH_LOCATIONS (synonym), HZ_RELATIONSHIPS (synonym), HZ_PARTY_SITES (synonym), and HZ_PARTY_SITE_USES (synonym). Supporting metadata and security objects referenced are FND_GLOBAL, HR_GENERAL, and HR_SECURITY (packages), plus the HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, and HZ_CUST_SITE_USES_ALL synonyms.

WSH_CALENDAR_ASSIGNMENTS is the driving table in both branches and supplies the primary key CALENDAR_ASSIGNMENT_ID along with the audit columns and flexfield attributes. In the VENDOR_SITE branch, the assignment joins to PO_VENDOR_SITES_ALL on VENDOR_SITE_ID, to PO_VENDORS on VENDOR_ID, and to HR_ORGANIZATION_UNITS on ORG_ID. In the VENDOR_LOCATION branch, the assignment joins to WSH_LOCATIONS on LOCATION_ID, which in turn is linked through HZ_PARTY_SITES, HZ_PARTY_SITE_USES, and HZ_RELATIONSHIPS to resolve the underlying trading partner. Because several of these objects are views or synonyms over TCA (HZ) and Procurement (PO) entities, the view inherits the security and multi-org behavior of those layers.

Key Columns

• VENDOR_ID — the trading partner identifier; in the location branch it is derived from HZ_RELATIONSHIPS.OBJECT_ID.
• VENDOR_SITE_ID — the vendor site identifier for site-level assignments; in the location branch it is the WSH_LOCATIONS.WSH_LOCATION_ID value, allowing both branches to project into a common column.
• ASSOCIATION_TYPE — discriminates the row as VENDOR_SITE or VENDOR_LOCATION; this is the column most often filtered when querying the view.
• VENDOR_SITE_CODE || '-' || HR.NAME — a concatenated display name for site-level rows, combining the site code with the organization name; the location branch supplies WSH_LOCATIONS.UI_LOCATION_CODE instead. This column is the effective “site_type” descriptor users search for.
• CALENDAR_CODE, CALENDAR_TYPE, ENABLED_FLAG — the calendar definition, its type, and whether the assignment is active.
• CALENDAR_ASSIGNMENT_ID — the primary key of the driving assignment record.
• FREIGHT_CODE, FREIGHT_ORG_ID — the freight terms and organization context associated with the assignment.
• LOCATION_ID — the warehouse or location identifier carried through from the assignment.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the descriptive flexfield context and segments.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

The view is typically used to answer which calendar applies to a vendor site or vendor location, to audit assignments that are disabled, and to drive carrier or shipment scheduling logic. A common query filters by association type and enabled status:

• SELECT vendor_id, vendor_site_id, calendar_code, enabled_flag FROM wsh_cal_asg_detail_v WHERE association_type = 'VENDOR_SITE' AND enabled_flag = 'Y';
• Auditing all assignments for a single trading partner: SELECT * FROM wsh_cal_asg_detail_v WHERE vendor_id = :vendor_id;
• Identifying location-level assignments: SELECT vendor_site_id, calendar_code FROM wsh_cal_asg_detail_v WHERE association_type = 'VENDOR_LOCATION';
• Inspecting flexfield usage: SELECT calendar_code, attribute_category, attribute1 FROM wsh_cal_asg_detail_v WHERE attribute_category IS NOT NULL;

Because the view is a union over vendor-site and vendor-location branches, reports should always constrain ASSOCIATION_TYPE to avoid double counting when the same partner has assignments at both levels.