Search Results flm_ekb_summary_util

Overview

FLM_EKB_SUMMARY_UTIL is a utility package in the Oracle E-Business Suite (EBS) Application Object Library (APPS) schema that supports the e-Kanban (EKanban) Summary feature. EKanban is the Oracle e-Commerce Gateway / manufacturing replenishment mechanism used within Oracle Manufacturing and Oracle Purchasing to model supplier-facing kanban signals. The package is classified by ETRM as a UTIL object, meaning it exposes reusable helper logic rather than a transactional API. The package is declared with AUTHID CURRENT_USER, so its SQL statements execute with the privileges of the invoking session rather than the definer, which is significant when the package is called from custom code running under a non-APPS schema.

Functionally, FLM_EKB_SUMMARY_UTIL provides the data-retrieval primitives required by the EKanban Summary page. The Summary page displays consolidated detail rows (document number, creation date, supplier, and pull-sequence information) drawn from requisitions, purchase orders, and WIP entities. Rather than embedding this query logic inside the OAF page or concurrent program that renders the summary, Oracle centralizes the lookups here so that the Summary Detail table and related views remain consistent.

Key Procedures and Functions

The documented package specification exposes five functions. No public procedures are documented, and the specification does not expose any package-level variables or cursors.

• GET_DOC_NUM — retrieves the human-readable document number for a row in the EKanban Summary Page Detail table. The caller supplies a document type indicator together with the document header and detail identifiers; the function returns the corresponding document number as a VARCHAR2. This is the function referenced by the user search term "get_doc_num".
• GET_DOC_CREATION_DATE — returns the creation date of the document associated with a kanban card. It shares the same three-part identification scheme (document type, header identifier, detail identifier) and returns the date as a VARCHAR2.
• GET_SUMMARY_QUERY — returns a SQL query string used to populate the EKanban Summary, parameterized by organization, supplier, and supplier site.
• GET_SUPPLIER_QUERY — returns a SQL query string that resolves supplier information for the same organization/supplier/supplier-site combination.
• GET_PULL_SEQ_DETAILS_QUERY — returns a SQL query string for pull-sequence detail rows, parameterized by organization.

Tables Accessed

The query-building functions resolve their data through APPS synonyms over the following base tables:

• PO_REQUISITION_HEADERS_ALL and PO_REQUISITION_LINES_ALL — source of requisition document numbers and creation dates.
• PO_HEADERS_ALL and PO_DISTRIBUTIONS_ALL — source of purchase order document numbers, dates, and supplier/site attribution.
• MTL_TXN_REQUEST_HEADERS and MTL_TXN_REQUEST_LINES — source of move-order (intra-org transfer) document numbers, which kanban replenishment uses for internal supply.
• WIP_ENTITIES — source of work-in-process entity information used when a kanban card is sourced from a discrete job.

The document-type parameter passed to GET_DOC_NUM and GET_DOC_CREATION_DATE determines which of the requisition, purchase order, or move-order tables is consulted.

Usage Notes

FLM_EKB_SUMMARY_UTIL is not an application-facing API; its functions are called from the EKanban Summary region of the Oracle iSupplier / Oracle Manufacturing OAF pages and, potentially, from concurrent-program or custom code that reproduces that summary. ETRM records no other package referencing it, so callers are expected to be page-level or extension code. Because the package is AUTHID CURRENT_USER, custom code must run as a user with EXECUTE on the package and SELECT on the underlying synonyms, normally satisfied by running as APPS. The query-string functions return SQL text intended to be executed dynamically by the caller; they must not be treated as returning result sets directly. Oracle's header indicates revision 120.3 dated 2011, and the object is marked "noship", reflecting that it is a supporting utility rather than a productized public interface.