Results for “delivery_time”

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

Overview

CSP_CARRIER_DELIVERY_TIMES is a transactional configuration table owned by the CSP schema within the Oracle E-Business Suite Spares Management (CSP) module. Its documented purpose is to store delivery-time related information, meaning it holds the carrier-, freight-, and location-specific attributes that determine how long a shipment will take to reach its destination and when it must be cut off for dispatch. In practice, this table acts as the reference source for expected lead times, delivery windows, and carrier cutoff rules used by spares logistics planning and order promising logic.

The table is populated with 36 documented columns in ETRM 12.2.2 and carries the primary key constraint CSP_CARRIER_DELIVERY_TIMES_PK, defined on the RELATION_SHIP_ID column. A parallel unique index, CSP_CARRIER_DELIVERY_TIMES_U1, is also defined on RELATION_SHIP_ID. From a heuristic Data Vault modeling perspective, the mined foreign-key structure classifies this object as satellite-leaning: it captures descriptive, time-variant attributes attached to a relationship key rather than acting as an independent hub of business entities. The root identifier RELATION_SHIP_ID behaves as the parent relationship key, while columns such as LEAD_TIME and DELIVERY_TIME provide the descriptive context.

Key Information Stored

The most operationally significant columns fall into three groups.

• Identifier and tenant scope: RELATION_SHIP_ID is the primary key and business-key column. ORGANIZATION_ID scopes each row to an inventory organization, and SECURITY_GROUP_ID enforces multi-tenant data isolation through FND_SECURITY_GROUPS.
• Carrier and freight attributes: FREIGHT_CODE and SHIPPING_METHOD identify the carrier service level. LEAD_TIME with LEAD_TIME_UOM expresses the expected transit duration, while DELIVERY_TIME and CUTOFF_TIME define the daily commitment and dispatch boundary. SAFETY_ZONE and TIMEZONE_ID align those times to a valid HZ_TIMEZONES reference.
• Location and distance detail: SUBINVENTORY_CODE, LOCATION_ID, DISTANCE, and DISTANCE_UOM capture where the shipment originates and how far it must travel, enabling distance-based delivery estimates.
• Audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN follow the standard EBS WHO convention, and the ATTRIBUTE1 through ATTRIBUTE15 flex columns allow customer-specific extensions.

The surrogate/primary key RELATION_SHIP_ID is distinct from the business-key candidate confirmed by the unique index CSP_CARRIER_DELIVERY_TIMES_U1, which is also defined on RELATION_SHIP_ID.

Common Use Cases and Queries

Planners and developers query this table to resolve the lead time and cutoff information applicable to a given carrier, shipping method, and organization. A typical lookup retrieves delivery commitments for a specific shipping method:

• SELECT relation_ship_id, freight_code, shipping_method, lead_time, lead_time_uom, delivery_time, cutoff_time FROM csp_carrier_delivery_times WHERE organization_id = :org_id AND shipping_method = :method;
• Reporting the distribution of lead times by carrier: SELECT freight_code, AVG(lead_time) FROM csp_carrier_delivery_times GROUP BY freight_code;
• Joining to the timezone reference to present local delivery windows: SELECT c.relation_ship_id, t.tzname, c.cutoff_time FROM csp_carrier_delivery_times c, hz_timezones t WHERE c.timezone_id = t.timezone_id;

These patterns support order promising, carrier performance analysis, and subinventory-level dispatch planning.

Related Objects

• HZ_TIMEZONES — referenced via CSP_CARRIER_DELIVERY_TIMES.TIMEZONE_ID; resolves the timezone for cutoff and delivery times.
• FND_SECURITY_GROUPS — referenced via CSP_CARRIER_DELIVERY_TIMES.SECURITY_GROUP_ID; enforces data security.
• CSP_CARRIER_DELIVERY_TIMES_PK / CSP_CARRIER_DELIVERY_TIMES_U1 — the primary-key constraint and unique index defined on RELATION_SHIP_ID.
• HR_ORGANIZATION_UNITS / ORG_ORGANIZATION_DEFINITIONS — implied by ORGANIZATION_ID for inventory organization context.
• MTL_SYSTEM_ITEMS_B and shipping method reference tables — commonly joined for item and carrier service validation.