Search Results get_atp_comp_flag

Overview

The APPS.MSC_ATP_FUNC package body is a utility library within the Oracle Advanced Supply Chain Planning (ASCP) module of Oracle E-Business Suite. Its primary purpose is to support available-to-promise (ATP) and capable-to-promise (CTP) processing performed by the MSC (Manufacturing and Supply Chain) schema. The package consolidates a set of helper functions that resolve planning data required during ATP checks — such as item ATP flags, calendar-based time fence dates, location and supplier identifiers, and inter-org transit times. In the 12.1.1 and 12.2.2 environments, the package operates against APPS-owned synonyms that expose planning and master data tables owned by the MSC schema. The header comment indicates the body was last revised in late 2007 (script MSCFATPB.pls, version 120.1), so its logic predates the newer 12.2.x technology stack but remains in use because ATP calculations in ASCP still depend on these legacy helper routines. The package is classified as OTHER rather than a public API, meaning it is intended for internal consumption by other MSC packages and planning engines rather than for direct customer invocation.

Key Procedures and Functions

The documented package exposes 24 procedures and functions. Among the most relevant to ATP processing are:

• GET_ATP_FLAG — Returns the ATP flag for a given inventory item, organization, plan, and instance. It reads MSC_SYSTEM_ITEMS and joins MSC_BOM_TEMP to force the flag to 'N' for multi-level/multi-org CTO configurations where the BOM-level ATP check is disabled.
• GET_ATP_COMP_FLAG — Retrieves the ATP flag applicable to a component item within a configured bill of materials.
• GET_INFINITE_TIME_FENCE_DATE — Returns the infinite time fence date associated with a plan, defining the horizon beyond which ATP checks assume infinite supply.
• GET_LOCATION_ID and GET_LOCATION_CODE — Resolve internal location identifiers and their corresponding codes.
• GET_INV_ITEM_NAME and GET_INV_ITEM_ID — Convert between inventory item identifiers and descriptive item names.
• GET_SUPPLIER_NAME and GET_SUPPLIER_SITE_NAME — Return trading partner supplier and supplier site descriptions.
• GET_SD_SOURCE_NAME — Returns the source name for a supply/demand record.
• PREV_WORK_DAY and NEXT_WORK_DAY_SEQNUM — Compute working-day offsets using the planning calendar.
• MPS_ATP — Performs the master production schedule ATP evaluation, central to ATP-quantity determination.
• GET_DESIGNATOR — Returns a designator value used in ATP rule evaluation.
• GET_MPS_DEMAND_CLASS — Returns the demand class associated with an MPS demand.
• GET_TOLERANCE_PERCENTAGE — Retrieves the tolerance percentage configured for ATP/supply flexibility.
• GET_ORDER_NUMBER and GET_ORDER_TYPE — Resolve order identifiers and classification.
• GET_INTERLOC_TRANSIT_TIME — Returns the inter-org transit lead time between two organizations.

Tables Accessed

All access occurs through APPS synonyms over MSC-owned tables. MSC_SYSTEM_ITEMS and MSC_BOM_TEMP supply item master and BOM ATP attributes; MSC_PLANS provides plan definition context, including the infinite time fence. MSC_ATP_RULES stores ATP rule configurations, while MSC_CALENDAR_DATES and MSC_PROCESS_EFFECTIVITY drive working-day and effectivity calculations. MSC_SUPPLIES supplies supply records for ATP matching. Location resolution uses MSC_LOCATION_ASSOCIATIONS, MSC_REGIONS_TEMP, and MSC_ITEM_ID_LID. Supplier and trading partner data come from MSC_TRADING_PARTNERS, MSC_TP_SITE_ID_LID, MSC_SUPPLIER_FLEX_FENCES, and MSC_INTERORG_SHIP_METHODS. MSC_DESIGNATORS supports designator lookups. These tables are read during ATP/CTP planning runs; the package functions are predominantly read-only.

Usage Notes

MSC_ATP_FUNC is not a public interface. It is invoked internally by ASCP planning engines, ATP/CTP processing logic, and other MSC packages — the metadata indicates it is referenced by 12 other packages. Calls typically originate during plan execution (the plan manager and ATP scheduling programs) and through related MSC private packages such as MSC_ATP_PVT, with which this body shares session globals like G_SESSION_ID and G_COMP_LINE_ID. Debug output is controlled via the MSC_ATP_DEBUG profile option, routed through MSC_SCH_WB.ATP_DEBUG. Because it is undocumented as a public API, custom code should not depend on these routines; the same applies to the infinite time fence lookup, whose value should be obtained through supported ATP rule interfaces rather than direct calls. Any customization referencing this package risks breakage on patching, particularly when migrating from 12.1.1 to 12.2.2 where underlying MSC schema objects may be recompiled or renamed.