Results for “org_organization_code”

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

Overview

CSP_CARRIER_DELIVERY_TIMES_V is a PL/SQL view owned by the APPS schema within the Oracle E-Business Suite Spares Management (CSP) product family. Its documented purpose is to "show carrier delivery times," consolidating freight, shipping-method, and timezone attributes into a single denormalized projection. In practice, the view answers operational questions such as how long a given carrier or ship method takes to move goods between locations, and how lead time, delivery time, and cutoff time interact with the receiving timezone.

Because it joins carrier ship-method definitions to organization definitions and timezone labels, the view is suited to reporting and integration: downstream tools, custom concurrent programs, and carrier-selection logic can read a ready-made, human-readable picture of shipment timing rather than re-deriving it from the raw configuration tables.

Underlying Base Objects

The documented base objects underlying the view are CSP_CARRIER_DELIVERY_TIMES (synonym), FND_LOOKUP_VALUES_VL (view), HR_ALL_ORGANIZATION_UNITS (synonym), HZ_TIMEZONES_VL (view), MTL_INTERORG_SHIP_METHODS (synonym), MTL_PARAMETERS (synonym), and MTL_SECONDARY_INVENTORIES (synonym). The primary driver in the view text is CSP_CARRIER_DELIVERY_TIMES (aliased CDT), which holds the per-organization, per-freight-code, per-shipping-method timing configuration. WSH_CARRIER_SHIP_METHODS (CSM) supplies organization, freight code, and ship method, joined to CDT with outer joins (CDT.ORGANIZATION_ID (+), CDT.FREIGHT_CODE (+), CDT.SHIPPING_METHOD (+)) so all configured ship methods appear even when timing data is absent. ORG_ORGANIZATION_DEFINITIONS (OOD) provides the organization code and is joined non-outerwise to CSM. HZ_TIMEZONES_VL (TN) is outer-joined on TIMEZONE_ID to supply the timezone name, and the result set is ordered by organization code.

Key Columns

• ORGANIZATION_ID / WSH_ORGANIZATION_ID and ORG_ORGANIZATION_CODE: identify the warehouse or inventory organization for which carrier timing is defined.
• FREIGHT_CODE / WSH_FREIGHT_CODE and SHIP_METHOD_CODE / SHIPPING_METHODE: the carrier freight term and shipping method pairing.
• LEAD_TIME and LEAD_TIME_UOM: the configured lead duration and its unit of measure.
• DELIVERY_TIME, CUTOFF_TIME, and TIMEZONE_ID/TIMEZONE: the delivery window, the daily cutoff after which an order slips to the next cycle, and the applicable timezone (resolved through HZ_TIMEZONES_VL).
• RELATION_SHIP_ID and ROW_ID: relationship and row identifiers used for update tracking.
• SAFETY_ZONE (documented as COMFORT_ZONE in the column listing) and the ATTRIBUTE1–15 / ATTRIBUTE_CATEGORY flexfield columns: descriptive or extensibility fields.
• CREATED_BY / CREATION_DATE / LAST_UPDATED_BY / LAST_UPDATE_DATE / LAST_UPDATE_LOGIN: standard audit columns.

Common Use Cases and Queries

A typical reporting scenario is determining how many days a courier takes between two locations, for example an "Erode to Karur ST courier" lane. The view supplies the configured lead/delivery timings per organization and ship method, which an analyst can filter and combine with transit offsets.

SELECT org_organization_code, freight_code, shipping_methode,
       lead_time, lead_time_uom, delivery_time, cutoff_time, timezone
FROM   apps.csp_carrier_delivery_times_v
WHERE  org_organization_code = :org_code
AND    freight_code = :freight_code
ORDER  BY shipping_methode;

Additional uses include validating that no organization has missing timing rows (the outer joins from WSH_CARRIER_SHIP_METHODS deliberately expose such gaps), feeding carrier-selection logic, and auditing timezone or cutoff configuration. Because the view is defined in the APPS schema, it should be queried with the APPS or a suitably privileged reporting account.