Search Results ibe_atp_pvt




Overview
Explore in AI Chat

Overview

IBE_ATP_PVT is a private PL/SQL package in the Oracle E-Business Suite (EBS) iStore/Order Capture module. Its documented API classification is PVT (private), indicating that it is intended for internal use by Oracle's own code rather than for direct invocation by customer extensions. The package encapsulates the logic required to perform Available-to-Promise (ATP) checks against the lines of a quote header, resolving the ship-to site context and validating that a requested quantity can be fulfilled on a requested date.

The package is owned by APPS and is a single-procedure body, CHECK_AVAILABILITY. It accepts a quote header identifier, a date format, and a language code as inputs, and returns an error flag, error message, and a modified ATP line table. Business users experience this logic indirectly whenever iStore or Quoting displays scheduling or availability information for a configuration or line item.

Key Procedures and Functions

  • CHECK_AVAILABILITY — The sole documented procedure in the package. It drives the ATP validation for the quote lines associated with a given quote header. The procedure accepts a quote header identifier, a date format string, and a language code, and returns an error flag, an error message, and an ATP line table that is passed IN OUT (the ATP_Line_Tbl_Typ structure). Internally it normalizes the date format (defaulting to 'DD-MON-RRRR') and language code (defaulting to the session language) when null or empty values are supplied. The procedure declares internal exceptions for bad date format and for a missing previous date, and it works with a local shipment table and ATP table to stage results. It also contains a private cursor, get_site_use_id, which resolves a site_use_id from a party_site_id — this is the object most often sought by developers troubleshooting ship-to resolution failures in this package.

Tables Accessed

The documented package reads from the following tables via APPS synonyms:

  • HZ_PARTY_SITES — The party site is the anchor record used to resolve the ship-to context. The get_site_use_id cursor starts here.
  • HZ_CUST_ACCT_SITES_ALL — Provides the customer account site that links a party site to a specific account.
  • HZ_CUST_SITE_USES_ALL — Supplies the site use (for example, ship-to) that corresponds to the customer account site. The join across these three tables yields the site_use_id used downstream.
  • FND_LOOKUP_VALUES — Used to validate or translate coded values, including date format and language related lookups.
  • PLITBLM — A PL/SQL index-by table used to hold intermediate ATP line data during processing.

These tables are read; the procedure does not persist business data, it returns results in the output ATP line table for the caller to consume.

Usage Notes

Because IBE_ATP_PVT is classified PVT, it is invoked internally by other iStore and ATP integration packages rather than being called directly from forms, concurrent programs, or custom code. The ETRM metadata notes that the package is referenced by one other package, which is consistent with a private helper used by a parent public API. The get_site_use_id cursor is typically encountered by developers investigating why a quote line fails to resolve a ship-to site, since a mismatch between the party site and the customer account site use chain will cause the cursor to return no rows and the ATP check to fail. When troubleshooting ATP failures on quoted lines in EBS 12.1.1 or 12.2.2, verify the ship-to site use setup in the HZ tables before reviewing the ATP call itself. Custom code should call the documented public ATP API rather than this private package.