Search Results get_interloc_transit_time




Overview
Explore in AI Chat

Overview

MSC_ATP_FUNC is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Advanced Supply Chain Planning (ASCP) and available-to-promise (ATP) functional area within the MSC (Supply Chain Planning) product family. The package header carries the source control identifier $Header: MSCFATPS.pls 120.1 2007/12/12 10:27:30 sbnaik ship $, indicating a long-standing member of the planning code base.

The package encapsulates a broad set of lookup and conversion utilities that planning and ATP engines rely on when evaluating whether a given item, organization, or plan combination is ATP-enabled, when resolving calendar and time-fence information, and when translating surrogate identifiers (item IDs, location IDs, supplier IDs) into meaningful codes and names. It effectively acts as a shared service layer for ATP rule evaluation and planning-data presentation across MSC modules. In the ETRM classification it is registered as an OTHER API rather than a public or private API, meaning it is intended for internal consumption by Oracle planning code rather than as a published integration interface.

Key Procedures and Functions

The package exposes twenty-four documented procedures and functions. A prominent group answers ATP-related questions: GET_ATP_FLAG and GET_ATP_COMP_FLAG determine whether ATP, or component-level ATP, applies for a given item/organization/plan context. GET_INFINITE_TIME_FENCE_DATE returns the infinite time fence date used to bound planning calculations.

A second group performs identifier resolution. GET_LOCATION_ID derives a location identifier from customer, supplier, and organization attributes. GET_ORG_CODE returns the organization code, while GET_INV_ITEM_NAME and GET_INV_ITEM_ID translate between item names and inventory item identifiers. GET_SUPPLIER_NAME, GET_SUPPLIER_SITE_NAME, and GET_LOCATION_CODE provide display-friendly descriptors. GET_SD_SOURCE_NAME resolves source names from a source type and source type identifier.

Calendar helpers include PREV_WORK_DAY and NEXT_WORK_DAY_SEQNUM, which support working-day arithmetic used in scheduling and lead-time logic. Additional routines cover designator and plan context (MPS_ATP, GET_DESIGNATOR), demand classification (GET_MPS_DEMAND_CLASS), tolerance handling (GET_TOLERANCE_PERCENTAGE), order attributes (GET_ORDER_NUMBER, GET_ORDER_TYPE), and transit-time lookup (GET_INTERLOC_TRANSIT_TIME). The searched term "get_session_id" does not correspond to a documented entry point in this package; session context is instead supplied through the p_instance_id parameter carried by most functions.

Tables Accessed

All table references are made through APPS synonyms. MSC_ATP_RULES supplies the ATP rule definitions that drive GET_ATP_FLAG and GET_ATP_COMP_FLAG. MSC_SYSTEM_ITEMS and MSC_ITEM_ID_LID support item name and identifier resolution, while MSC_LOCATION_ASSOCIATIONS and MSC_TP_SITE_ID_LID back the location and trading-partner lookups. Calendar functions draw on MSC_CALENDAR_DATES. Supplier-related lookups use MSC_SUPPLIER_FLEX_FENCES and MSC_TRADING_PARTNERS. MSC_PLANS and MSC_PROCESS_EFFECTIVITY provide plan and effectivity context. Additional reads come from MSC_BOM_TEMP, MSC_INTERORG_SHIP_METHODS, MSC_DESIGNATORS, MSC_REGIONS_TEMP, and MSC_SUPPLIES.

Usage Notes

Because MSC_ATP_FUNC is classified as OTHER rather than a public API, it is normally invoked by Oracle's own planning and ATP processing logic, including the ASCP planning engine and ATP rule evaluation during scheduling. Twelve other packages reference it, confirming its role as a shared internal utility. Custom code should call these functions only with full awareness that signatures may change between point releases. Typical direct use includes resolving item names, organization codes, or supplier names in custom planning reports, and evaluating ATP flags prior to committing a promise date. Developers should always pass a valid p_instance_id obtained from the current planning session context rather than attempting to derive one independently.