Search Results jtf_fm_request_grp




Overview
Explore in AI Chat

Overview

JTF_FM_OCM_REQUEST_GRP is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified as a Group (GRP) API. It belongs to the Oracle Fusion Middleware / Fulfillment Management (JTF_FM) family of components that support order capture, order fulfillment, and outbound request processing across the EBS application stack. In EBS 12.1.1 and 12.2.2, the package functions as a coordination layer within the Order Capture and Fulfillment Management flow, specifically the OCM (Order Capture Management) request handler. Its principal responsibility is to govern the creation and lifecycle of fulfillment requests generated from captured orders and related documents.

The package occupies a central position in the fulfillment dependency graph. It sits above lower-level request primitives such as JTF_FM_REQUEST_GRP and JTF_FULFILLMENT_PUB, and it is consumed by higher-level rendering, rule, and fulfillment orchestration components. This layering makes it a stable integration point for applications that must convert business transactions into fulfillment requests without directly manipulating the underlying request tables.

Key Procedures and Functions

  • CREATE_FULFILLMENT — The single documented program unit in this package. It is the public entry point used to establish a fulfillment request for a given business document or order context. The procedure encapsulates the request creation logic, delegating low-level persistence and validation work to the underlying JTF_FM_REQUEST_GRP and JTF_FULFILLMENT_PUB packages. As a GRP-classified API, the procedure does not expose an extensive perimeter: callers invoke it with an order or request identifier and receive the created fulfillment reference, while the internal handling of status, history, and error reporting remains encapsulated.

Because the metadata for this object lists only one documented program unit, the ETRM record should be treated as an abbreviated interface description rather than a complete specification. Implementers should inspect the package body in the target instance to confirm any additional private helpers.

Tables Accessed

The package reaches its data through APPS synonyms, which is standard for seeded EBS code. The documented table references are:

  • JTF_FM_REQUEST_HISTORY_ALL — The fulfillment request history table. The package reads and writes here to record the audit trail of fulfillment requests, capturing state transitions and timestamps as requests progress. This is the primary persistent store for request lifecycle data.
  • JTF_FM_TEST_REQUESTS — A test or diagnostic table used to hold fulfillment requests exercised outside normal production flow. Access to this table supports unit testing and validation of fulfillment request creation without committing live business data.
  • PLITBLM — A PL/SQL index-by table type (PL/SQL Integer Table) used internally for in-memory collections rather than as a physical database table. It appears in the metadata because it is a referenced database object type, but its role is transient within the PL/SQL execution context.

Usage Notes

JTF_FM_OCM_REQUEST_GRP is invoked programmatically rather than through a dedicated form. It is referenced by seven dependent packages, including AMS_CT_RULE_PVT and AMS_FULFILL_PVT (the Marketing/TeleSales fulfillment and rule components), JTF_FM_OCM_REND_REQ and its _W variant, JTF_FM_REQUEST_GRP, and JTF_FM_UTL_V. This dependency pattern indicates that the package is called during order capture fulfillment, marketing campaign fulfillment, and fulfillment request rendering.

Typical invocation occurs when a captured or confirmed order requires the generation of downstream fulfillment work. Concurrent programs and business events that process order capture output route through JTF_FM_OCM_REQUEST_GRP.CREATE_FULFILLMENT to persist the request and its initial history record. Custom code should call the package only through its documented procedure and should rely on FND_API-based error handling, consistent with the package's dependency on FND_API. Direct DML against JTF_FM_REQUEST_HISTORY_ALL is discouraged, as it bypasses the validation and history logic encapsulated by this API. Support and upgrade planning should note that the object status is VALID in both 12.1.1 and 12.2.2, indicating no known invalidation issues.