Search Results src_ship_method




Overview
Explore in AI Chat

Overview

MSC_SATP_FUNC is an Oracle Applications (APPS) PL/SQL package that supports the Supply Chain ATP (Available-to-Promise) engine within Oracle Advanced Supply Chain Planning. Its primary business role is the calculation of source-side delivery lead time, encompassing location resolution, default ship method determination, intransit (transit) time computation, and working-day date arithmetic. The package header carries the identifier MSCSATPS.pls 120.2, dated 2007/12/12, and the package is classified under ETRM as an OTHER API rather than a public or private interface. In the context of Oracle EBS 12.1.1 and 12.2.2, the package functions as an internal planning utility layer: it resolves organizational, customer, and trading-partner attributes, then converts those attributes into the transit-time and shipping-method values the ATP engine consumes when promising order dates. The package is referenced by 25 other packages, indicating a widely leveraged dependency within the Advanced Supply Chain Planning and Order Management integration surface.

Key Procedures and Functions

The documented interface exposes 29 procedures and functions. The source-related functions form the delivery lead time core. SRC_LOCATION_ID resolves a source location identifier from organization, customer, and customer site inputs. SRC_INTERLOC_TRANSIT_TIME returns the transit time between two locations for a specified ship method, and SRC_DEFAULT_SHIP_METHOD returns the default ship method for a given from/to location pair. SRC_DEFAULT_INTRANSIT_TIME returns the corresponding default intransit time.

The organization-oriented SRC_SHIP_METHOD and SRC_INTRANSIT_TIME functions return ship method and intransit time respectively for a from-organization and to-organization pair and are the routines most directly associated with the src_ship_method search term that led to this package. Calendar-aware date arithmetic is provided by SRC_PREV_WORK_DAY, SRC_NEXT_WORK_DAY, and SRC_DATE_OFFSET, which accept an organization identifier and a date.

ATP record manipulation is handled by EXTEND_ATP, ASSIGN_ATP_INPUT_REC, ASSIGN_ATP_OUTPUT_REC, EXTEND_ATP_PERIOD, EXTEND_ATP_SUPPLY_DEMAND, and TRIM_ATP_SUPPLY_DEMAND. The Extend_Atp function was modified to accept a p_index parameter controlling how far the ATP_REC_TYP record is extended. Session and region resolution are provided by GET_SESSION_ID, GET_REGIONS_OLD, GET_REGIONS_SHIPPING, GET_SRC_TRANSIT_TIME, and GET_REGIONS.

Tables Accessed

The package reads and, in several cases, writes to the following tables via APPS synonyms: BOM_CALENDAR_DATES for working-day and offset calculations; HR_ALL_ORGANIZATION_UNITS for organization validation; HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_LOCATIONS, and HZ_PARTY_SITES for customer and site resolution; MSC_ATP_SRC_PROFILE_TEMP for transient source profile data; MSC_REGIONS, MSC_REGIONS_TEMP, MSC_REGION_LOCATIONS, MSC_REGION_SITES, and MSC_ZONE_REGIONS for region and zone-based sourcing logic; MSC_TP_SITE_ID_LID and MSC_TRADING_PARTNER_SITES for trading-partner site mapping; and MTL_INTERORG_SHIP_METHODS for inter-organization ship method definitions.

Usage Notes

MSC_SATP_FUNC is an internal planning API and is not typically called directly from Oracle Forms or standard concurrent program submissions. Its routines are invoked by other planning packages during ATP and scheduling processing; the ETRM metadata confirms it is referenced by 25 packages. Custom code that requires ship method, intransit time, or organization-calendar date arithmetic may call the relevant functions, but such calls should respect the DEFAULT NULL parameters documented for session and partner site identifiers, which were introduced in the September 24, 2001 revision. Because the package is classified as OTHER and its header is an internal planning source file, changes to its signatures are not governed by a formal public API contract.