Search Results display_item
Overview
APPS.FLM_SCHEDULE_REPORT is a PL/SQL package body in Oracle E-Business Suite (12.1.1 / 12.2.2) that supports the Oracle Flow Manufacturing schedule reporting facility. Its primary role is to supply the computational logic used when formatting and printing flow schedules, particularly the revision lookup and the display-filtering decisions applied to components within an exploded bill of material. The package encapsulates two private functions that are invoked during report generation rather than being exposed as a public API. The header comment ($Header: FLMFSCHB.pls 115.6 2002/12/12) and the ETRM classification of OTHER confirm that this is an internal, report-oriented utility rather than a published interface. The package reads from BOM exploration and item master data to determine which rows should appear on the printed schedule, ensuring the report reflects the correct revision at a given effective date and suppresses components that should not be shown.
Key Procedures and Functions
- GET_REVISION — Returns the item revision as a VARCHAR2 value for a given organization, item, and effective date. It delegates the actual revision determination to the BOM_REVISIONS.Get_Revision API, passing a revision type of 'PART', an ECO status of 'ALL', and an examination type of 'ALL'. This function allows the schedule report to display the revision that was in effect on the report date.
- DISPLAY_ITEM — Returns a numeric flag (1 if the item should be displayed, 2 otherwise) that governs whether a component row appears on the schedule report. It is called for every item in the bill except for level 1. The logic suppresses phantom components themselves and suppresses items whose parent is not of phantom type, except in defined cases involving the top-level component. This function embodies the report's visibility rules.
Tables Accessed
- BOM_EXPLOSIONS — Read to resolve the component item, parent assembly item, and top item identifiers for a given top bill sequence ID and sort order, restricted to explosion type 'ALL'. These values drive the parent/component comparisons in DISPLAY_ITEM.
- MTL_SYSTEM_ITEMS — Read to retrieve the item_type attribute for both the component and its parent within the specified organization. These item types determine whether an item is phantom and therefore whether it should be displayed.
Because the package accesses these objects through APPS synonyms, it operates within the standard EBS data model and inherits the associated security and organization context. The ETRM metadata lists no other packages as callers or callees beyond the internal BOM_REVISIONS invocation.
Usage Notes
FLM_SCHEDULE_REPORT is not a general-purpose API and is not referenced by any other documented packages (referenced by 0 other packages). It is invoked internally by the flow manufacturing schedule reporting logic, most likely from a concurrent program or report that formats and prints flow schedules. The GET_REVISION function is called whenever a schedule line requires a date-effective revision, while DISPLAY_ITEM is called during the component iteration of the report to decide row visibility. The prominent sizing change to the local variables l_comp_type and l_parent_type (from 10 to 30 characters, per bug 2152161) indicates that deployment must ensure compatibility with the longer item type values supported in later releases. Customizations should not call these functions directly, since they depend on the caller having already populated BOM_EXPLOSIONS with an appropriate top_bill_sequence_id and sort_order for the schedule being reported.
-
PACKAGE BODY: APPS.FLM_SCHEDULE_REPORT
12.2.2
-
PACKAGE BODY: APPS.FLM_SCHEDULE_REPORT
12.1.1
-
Lookup Type: ITEM_TYPES
12.1.1
product: PER - Human Resources , meaning: ITEM TYPES ,
-
PACKAGE: APPS.FLM_SCHEDULE_REPORT
12.2.2
-
Lookup Type: ITEM_TYPES
12.2.2
product: PER - Human Resources , meaning: ITEM TYPES ,
-
PACKAGE: APPS.FLM_SCHEDULE_REPORT
12.1.1
-
PACKAGE BODY: APPS.HR_ITP_BUS
12.1.1
-
PACKAGE BODY: APPS.HR_ITP_BUS
12.2.2
-
APPS.HR_ITP_BUS SQL Statements
12.1.1
-
APPS.HR_ITP_BUS SQL Statements
12.2.2
-
PACKAGE BODY: APPS.HR_IPT_BUS
12.1.1
-
PACKAGE BODY: APPS.HR_IPT_BUS
12.2.2
-
APPS.FLM_SCHEDULE_REPORT dependencies on FLM_SCHEDULE_REPORT
12.1.1
-
APPS.FLM_SCHEDULE_REPORT dependencies on FLM_SCHEDULE_REPORT
12.2.2
-
APPS.HR_ITP_BUS dependencies on FND_MESSAGE
12.1.1
-
APPS.HR_ITP_BUS dependencies on FND_MESSAGE
12.2.2
-
APPS.HR_IPT_BUS dependencies on HR_API
12.1.1
-
APPS.HR_IPT_BUS dependencies on HR_API
12.2.2
-
APPS.HR_IPT_BUS dependencies on FND_MESSAGE
12.1.1
-
APPS.HR_IPT_BUS dependencies on FND_MESSAGE
12.2.2
-
APPS.ICX_REQ_SEARCH dependencies on ICX_REQ_SEARCH
12.1.1
-
APPS.HR_ITP_BUS dependencies on HR_UTILITY
12.2.2
-
APPS.ICX_REQ_SEARCH dependencies on ICX_REQ_SEARCH
12.2.2
-
APPS.HR_ITP_BUS dependencies on HR_UTILITY
12.1.1
-
APPS.ICX_REQ_SEARCH dependencies on HTP
12.2.2
-
APPS.ICX_REQ_SEARCH dependencies on HTP
12.1.1
-
PACKAGE BODY: APPS.PO_WF_REQ_NOTIFICATION
12.1.1
-
PACKAGE BODY: APPS.ICX_REQ_SEARCH
12.1.1
-
PACKAGE BODY: APPS.ICX_REQ_SEARCH
12.2.2
-
APPS.PO_WF_REQ_NOTIFICATION dependencies on PO_WF_UTIL_PKG
12.1.1
-
PACKAGE BODY: APPS.PO_WF_REQ_NOTIFICATION
12.2.2
-
APPS.PO_WF_REQ_NOTIFICATION dependencies on PO_WF_UTIL_PKG
12.2.2