Search Results get_target
Overview
WIP_BIS_ALERTS is an Oracle Work in Process (WIP) package that supports Business Intelligence System (BIS) alerting for manufacturing execution. Its purpose is to bridge WIP shop floor and period-based performance data with the BIS/Workflow notification infrastructure, allowing the application to evaluate period actuals against targets and to raise alerts when performance deviates from expectations. The package exposes procedures that post actual amounts into the BIS repository, resolve completed period information, retrieve actual and target values scoped by organization and period, evaluate alert conditions, and initiate Oracle Workflow notification processes.
In the Oracle EBS 12.1.1 and 12.2.2 releases, the package body is delivered under the APPS schema and is classified as OTHER in the ETRM metadata. The body carries a header revision of 120.1 dated 2005/10/04, indicating a stable, long-standing component of the WIP BIS integration layer. All documented procedures are declared with explicit parameter lists and contain a minimal implementation consisting of a RETURN statement, which is characteristic of stub or interface-defining package bodies in the EBS codebase.
Key Procedures and Functions
- POST_ACTUAL_TO_BIS — Posts an actual performance amount to the BIS layer. It receives a target short name, period set and period name, organization identifier, and the actual value, and is responsible for persisting that actual so it can be compared against a target.
- GET_LAST_COMP_PERIOD — Resolves the last completed accounting period for a given function, period set, and period type. It returns the period name together with its start and end dates as OUT parameters.
- GET_ACTUAL — Retrieves the actual value for a given function, period set, period name, and organization. The actual amount is returned through an OUT NOCOPY parameter. This is the procedure matched by the user's search for "get_actual".
- GET_TARGET — Retrieves the target for a specified target table, period set, period name, and organization. It returns the target amount along with the associated Workflow process, role, and role identifier used to route alerts.
- ALERT_CHECK — Evaluates alert conditions for a given function, providing the driving entry point that determines whether a notification should be generated for the period performance data.
- WIP_STRT_WF_PROCESS — Starts an Oracle Workflow notification process. It accepts subject, period, legal entity, organization, workflow process, role, actual, target, report name and parameter, and responsibility identifier, and returns a status value to the caller.
Tables Accessed
The ETRM metadata does not enumerate the base tables or APPS synonyms referenced by WIP_BIS_ALERTS. Because the package body is defined as a set of interface stubs, no SQL access paths are visible in the documented excerpt. Functionally, the procedures imply access to WIP and BIS period-balance and target data — actual amounts maintained for WIP organizations, period definitions from the accounting calendar, and a target table identified by the TRGT_TABLE parameter of GET_TARGET. The GET_LAST_COMP_PERIOD procedure depends on the GL/accounting period set to determine completed periods.
Usage Notes
WIP_BIS_ALERTS is typically invoked from BIS alert processing and Workflow-driven notification flows rather than from standard data entry forms. ALERT_CHECK acts as the orchestrating call, which in turn drives GET_LAST_COMP_PERIOD, GET_ACTUAL, and GET_TARGET before WIP_STRT_WF_PROCESS launches the notification workflow. POST_ACTUAL_TO_BIS is used to load actuals into the BIS repository so that comparisons and alerts can be performed. Because ETRM reports no packages referencing this body, integration is generally through concurrent programs, BIS/Workflow configuration, or custom code that calls the package procedures directly. In both 12.1.1 and 12.2.2, the package should be treated as an interface contract: callers rely on the documented signatures, while the shipped body provides no operational logic of its own.
-
PACKAGE BODY: APPS.WIP_BIS_ALERTS
12.1.1
-
PACKAGE BODY: APPS.WIP_BIS_ALERTS
12.2.2
-
PACKAGE: APPS.WIP_BIS_ALERTS
12.2.2
-
PACKAGE: APPS.WIP_BIS_ALERTS
12.1.1
-
PACKAGE: APPS.BIS_PMV_PMF_PVT
12.1.1
-
PACKAGE: APPS.BIS_TARGET_PVT
12.1.1
-
PACKAGE BODY: APPS.BIX_ALERT
12.1.1
-
PACKAGE: APPS.OZF_ALLOCATION_ENGINE_PVT
12.2.2
-
PACKAGE: APPS.OZF_ALLOCATION_ENGINE_PVT
12.1.1
-
PACKAGE: APPS.BISVIEWER_PMF
12.1.1
-
PACKAGE BODY: APPS.BSC_BIS_WRAPPER_PUB
12.1.1
-
PACKAGE BODY: APPS.BIS_TARGET_PVT
12.1.1
-
PACKAGE BODY: APPS.BISVIEWER_PMF
12.1.1
-
PACKAGE BODY: APPS.BIS_PMV_PMF_PVT
12.1.1
-
APPS.BIS_PORTLET_PMREGION dependencies on BIS_TARGET_PUB
12.1.1
-
APPS.BIS_INDICATOR_REGION_UI_PVT dependencies on BIS_TARGET_PUB
12.1.1
-
APPS.BISVIEWER_PMF dependencies on FND_MESSAGE
12.1.1
-
APPS.BIS_TARGET_PVT dependencies on BIS_TARGET_PUB
12.1.1
-
APPS.BIS_TARGET_PVT dependencies on BIS_TARGET_PUB
12.1.1
-
APPS.BIS_TARGET_PVT dependencies on HTP
12.1.1
-
PACKAGE BODY: APPS.BIS_PORTLET_PMREGION
12.1.1
-
PACKAGE BODY: APPS.BIS_INDICATOR_REGION_UI_PVT
12.1.1
-
APPS.BIS_PMV_PMF_PVT dependencies on BIS_PMV_UTIL
12.1.1
-
APPS.BIS_TARGET_PVT dependencies on BIS_UTILITIES_PUB
12.1.1
-
APPS.BIS_TARGET_PVT dependencies on FND_API
12.1.1
-
PACKAGE BODY: APPS.OZF_ALLOCATION_ENGINE_PVT
12.1.1
-
PACKAGE BODY: APPS.OZF_ALLOCATION_ENGINE_PVT
12.2.2