Search Results wip_bis_common




Overview

WIP_BIS_COMMON is an Oracle E-Business Suite PL/SQL package owned by the APPS schema, classified under the ETRM as an OTHER API rather than a public or private interface. It belongs to the Work in Process (WIP) Business Intelligence System (BIS) family of objects, which supplies the reporting and analytical layer used by discrete manufacturing dashboards, Work in Process / WIP Business Intelligence reports, and related Oracle Business Intelligence (OBIEE) or Discoverer-based performance views. The "COMMON" suffix indicates that the package centralizes utility logic shared across the WIP BIS object set rather than implementing a single business transaction.

The package sits within the standard EBS dependency web: it references SYS.STANDARD (evidence that it exposes ROWTYPE or cursor constructs and adheres to PL/SQL typing conventions) and is itself referenced by WIP_BIS_PROD_VAL_EMP_V, a production value / employee view used in WIP BIS reporting. It is also self-referencing, which is consistent with internal calls or overloaded declarations within the package specification and body. The ETRM record shows the object status as VALID and documents five packaged procedures or functions.

Key Procedures and Functions

  • GET_SEGMENT — Retrieves a key flexfield (KFF) segment value, most plausibly the organization or accounting segment used to qualify manufacturing and inventory transactions in WIP BIS reporting. It provides the segment-resolution logic consumed by other WIP BIS objects.
  • AVG_EMPLOYEE_NUM — Returns an averaged employee headcount figure for a given organizational or accounting scope, supporting productivity and resource-utilization metrics in production value reporting.
  • GET_LEGAL_ENTITY — Resolves the legal entity associated with the current session or organizational context, returning the legal entity identifier used to partition reporting data.
  • SET_LEGAL_ENTITY — Sets or registers the legal entity context for the session, allowing subsequent calls within the same database session to operate against a consistent legal entity.
  • GET_PERIOD_TARGET — Returns the target value (production or output volume) defined for a given accounting period, providing the denominator or benchmark against which actual results are compared in WIP BIS reporting.

Parameter signatures for these routines are not published in the ETRM metadata; consumers should treat them as internal-support APIs and avoid hard-coding call signatures derived from assumption.

Tables Accessed

  • ORG_ACCT_PERIODS — The open/closed accounting period definition for an inventory organization. GET_PERIOD_TARGET relies on this table to determine valid periods and their associated date ranges and status, and the legal entity and segment lookups may also resolve period-aware context.
  • PER_ALL_ASSIGNMENTS_F — The effective-dated assignment table in Oracle HRMS. AVG_EMPLOYEE_NUM uses this table to derive headcount averages over a specified period, respecting date-effective assignment records.

Both tables are accessed through APPS synonyms, so the package runs under the APPS schema and benefits from standard EBS data security and MOAC (Multi-Org Access Control) behavior where applicable.

Usage Notes

WIP_BIS_COMMON is an internal support package rather than a form-level API or concurrent program entry point. Its primary documented consumer is the view WIP_BIS_PROD_VAL_EMP_V, which is queried by WIP BIS reports, performance views, and OBIEE or Discoverer analyses. Custom BI extracts and any customer-built reporting that mimics the WIP production value by employee model may invoke these routines directly.

Because the package is classified as OTHER and has no public API contract in the ETRM, it should be treated as subject to change between releases and patches. Customizations should not call it where a supported public API exists; where it is unavoidable, callers should rely on the documented procedures as read-only helpers and should not depend on exception text or undocumented parameter defaults. Administrators validating availability can confirm the package status through the ETRM record or by querying ALL_OBJECTS for owner APPS and object name WIP_BIS_COMMON.