Search Results src_default_ship_method

Overview

MSC_SATP_FUNC is a PL/SQL package in the APPS schema that provides the core calculation engine for Oracle Advanced Supply Chain Planning's Available-to-Promise (ATP) and Supply Chain ATP (SATP) functionality. Its header identifies the package as being concerned primarily with "calculating delivery lead time at the source," which is the foundation for determining how long goods physically take to move between locations before a promise date can be set. The package operates against the planning and order management data model — organization calendars, customer sites, regions, trading partners, and inter-org shipping methods — and returns normalized values (location IDs, ship methods, and transit times) that higher-level planning and scheduling APIs consume. Because it is registered in ETRM with an API classification of OTHER and is referenced by twenty-five other packages, MSC_SATP_FUNC is best understood as a shared utility layer rather than an end-user-facing API. It has been under active maintenance since at least 2001, as evidenced by inline comments crediting parameter additions (p_session_id, p_partner_site_id, and p_index) to specific developers and bug numbers.

Key Procedures and Functions

The documented interface comprises 29 procedures and functions, most of which resolve source-side shipping and transit attributes:

• SRC_LOCATION_ID — resolves the source location identifier for a given organization, customer, and customer site.
• SRC_DEFAULT_SHIP_METHOD — returns the default shipping method between two locations. This is the function associated with the search term "src_default_ship_method."
• SRC_DEFAULT_INTRANSIT_TIME and SRC_INTRANSIT_TIME — return default and resolved in-transit durations for a location pair or an organization pair.
• SRC_INTERLOC_TRANSIT_TIME — computes transit time between two locations, optionally using a supplied ship method plus session and partner site context.
• SRC_SHIP_METHOD — returns the shipping method between two organizations.
• SRC_PREV_WORK_DAY, SRC_NEXT_WORK_DAY, and SRC_DATE_OFFSET — calendar-aware date arithmetic utilities that shift a date backward, forward, or by a day count while honoring the organization's work calendar.
• GET_SESSION_ID, GET_REGIONS, GET_REGIONS_OLD, GET_REGIONS_SHIPPING, and GET_SRC_TRANSIT_TIME — region and session resolution helpers used to drive the transit-time logic.
• EXTEND_ATP, EXTEND_ATP_PERIOD, EXTEND_ATP_SUPPLY_DEMAND, and TRIM_ATP_SUPPLY_DEMAND — procedures that resize the ATP supply/demand working sets.
• ASSIGN_ATP_INPUT_REC and ASSIGN_ATP_OUTPUT_REC — record-mapping routines that translate between input and output structures.

Per the header comments, EXTEND_ATP was modified to accept a p_index parameter that determines the index length by which ATP_REC_TYP is extended, defaulting to one.

Tables Accessed

The package reads and writes a defined set of APPS synonyms:

• BOM_CALENDAR_DATES — supplies work-day information for the calendar functions.
• HR_ALL_ORGANIZATION_UNITS — supplies organization context for location and calendar resolution.
• HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_LOCATIONS, HZ_PARTY_SITES — the Trading Community Architecture tables used to resolve customer sites and addresses into location identifiers.
• MTL_INTERORG_SHIP_METHODS — supplies inter-org shipping method definitions used by SRC_SHIP_METHOD and SRC_DEFAULT_SHIP_METHOD.
• MSC_REGIONS, MSC_REGIONS_TEMP, MSC_REGION_LOCATIONS, MSC_REGION_SITES, MSC_ZONE_REGIONS — region and zone membership data for regional transit-time logic.
• MSC_TRADING_PARTNER_SITES, MSC_TP_SITE_ID_LID — trading partner site mappings.
• MSC_ATP_SRC_PROFILE_TEMP — the temporary profile store for source ATP parameters.

Usage Notes

MSC_SATP_FUNC is not invoked directly by end users. It is called programmatically by the Advanced Supply Chain Planning engine and by the twenty-five packages that reference it, including ATP scheduling and order promising flows that need to derive ship methods and transit times before committing a promise date to an order. Customizations should call the functions with the documented parameter signatures only; several signatures carry DEFAULT NULL session and partner-site parameters that must be populated when callers operate outside a planning session, or the region and session resolution logic will not return meaningful results. Because the package reads TCA and calendar tables, any custom integration must ensure those synonyms are visible in the calling schema. Its wide dependency footprint means changes should be validated against all downstream consumers before deployment.