Results for “jtf_fulfillment_pub”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

JTF_FULFILLMENT_PUB is a public PL/SQL API packaged in the APPS schema that supports fulfillment processing for order and quote-driven deliverables within Oracle E-Business Suite. Its central responsibility is to create the physical fulfillment records that link customer-facing deliverables — such as ordered items, configured kits, and service or warranty lines — to the supply chain objects that satisfy them. The package operates as a public interface (API classification PUB), meaning it is intended to be called from other application modules, forms, or custom code rather than being an internal private utility.

The dependency profile confirms the package sits at the intersection of Oracle Advanced Supply Chain (AMS), Oracle Order Management and Quoting (ASO), and Oracle Inventory (MTL). It relies on the standard EBS API infrastructure — FND_API, FND_MSG_PUB, and FND_PROFILE — for error handling, message stacking, and profile option lookups, which is consistent with a documented, supported public API that returns a standard API return status rather than raising unhandled exceptions.

Key Procedures and Functions

The ETRM documentation records a single public procedure for this package body:

• CREATE_FULFILL_PHYSICAL — Creates the physical fulfillment record associated with a deliverable or deliverable kit item. In practice this procedure is invoked during fulfillment processing to write the inventory-level or shipment-level record that corresponds to an ordered or quoted deliverable, and it applies the standard FND_API messaging and return-status conventions so callers can evaluate success and retrieve error messages.

No further parameter-level documentation is exposed in the metadata; developers should obtain the exact signature from the package specification (JTF_FULFILLMENT_PUB spec) in the target instance before coding against it.

Tables Accessed

The documented tables referenced through APPS synonyms are:

• AMS_DELIVERABLES_ALL_B — the base deliverable definition table. The package reads deliverable attributes to determine what must be fulfilled and to associate the physical fulfillment with the correct deliverable.
• AMS_DELIV_KIT_ITEMS — the deliverable kit component table. Used to resolve kit structures so that each component of a deliverable kit can receive its own physical fulfillment record.
• MTL_SYSTEM_ITEMS_B — the inventory item master. Referenced to validate and resolve inventory items corresponding to deliverable lines, including item-based attributes required for fulfillment.
• PLITBLM — the PL/SQL index-by table type used by EBS APIs to carry multi-row message text and other bulk collections; its presence indicates the package accumulates and returns messages in bulk through the FND message stack.

Additional dependencies on ASO_ORDER_INT, ASO_QUOTE_PUB, JTF_REQUEST_HISTORY_PVT, and JTF_FULFILLMENT_PUB itself confirm that fulfillment is driven from order interface and quoting data, and that requests may be logged for history and auditing.

Usage Notes

JTF_FULFILLMENT_PUB is a foundational API: it is not referenced by any other database object according to ETRM, but seven other packages are documented as referencing it, which places it among the lower-level building blocks of the fulfillment stack rather than a top-level entry point. Typical invocation paths include order and quote fulfillment workflows, service deliverable processing, and custom extensions that need to persist physical fulfillment records in a supported manner instead of writing directly to AMS tables. Because it is a PUB API using FND_API and FND_MSG_PUB, callers should initialize the message stack (FND_MSG_PUB.INITIALIZE), call CREATE_FULFILL_PHYSICAL, and then inspect the returned status and FND_MSG_PUB message count before committing. Behavior is controlled partly by FND_PROFILE settings, so environments should be validated against the profile configuration present in 12.1.1 and 12.2.2 before relying on the API in custom code.