Search Results get_message_name
Overview
APPS.BSC_OBJECTIVE_METADATA_SETUP is a public PL/SQL package body belonging to the Oracle Balanced Scorecard (BSC) product family within Oracle E-Business Suite. The package, stored in the source file BSCOBMDB.pls and created in August 2007 by Ajitha Koduri under Bug 6083208, exists to support diagnostic testing of objective reports. Objectives form the core of the Balanced Scorecard strategy model, and reliable reporting against them depends on the health of the underlying metadata. This package therefore acts as a diagnostics harness rather than as a business transaction API: it exposes the standard diagnostic test interface (initialization, execution, description, and cleanup routines) so that the objective reporting subsystem can be validated through the Oracle Diagnostics framework.
Key Procedures and Functions
- GET_MESSAGE_NAME — A public function that returns a message name in
VARCHAR2form for a message passed in asVARCHAR2. It is the entry point most often referenced by callers searching for message-name resolution within the objective diagnostics flow. - INIT — Standard diagnostics initialization hook. In this public version it performs no work, reserving the slot so test writers can insert special setup code if required.
- CLEANUP — Companion teardown hook, likewise a no-op stub in the public version, available for custom cleanup logic.
- GETDEFAULTTESTPARAMS — Supplies the default parameter set used when the diagnostic test is launched without explicit inputs.
- RUNTEST — The executable core of the diagnostic; orchestrates the actual validation logic for the objective report.
- GETCOMPONENTNAME — Returns the component identifier under which the diagnostic is registered.
- GETTESTNAME — Returns the display name of the diagnostic test.
- GETTESTDESC — Returns the descriptive text shown to the user explaining what the test verifies.
- GETTESTMODE — Returns the execution mode governing how the test is run.
Tables Accessed
The only documented table reference is BSC_SYS_INIT, accessed through an APPS synonym. BSC_SYS_INIT is a system-initialization table used by the Balanced Scorecard modules to store setup and configuration state. The diagnostics package reads it to confirm that the objective reporting environment has been initialized correctly. No other application tables are documented against this package body.
Usage Notes
Because the package conforms to the Oracle Diagnostics test interface, it is typically invoked from the Diagnostics responsibility or from the "Diagnostics" menu path attached to the objective report region, rather than from ordinary business forms or concurrent programs. The framework calls GETCOMPONENTNAME, GETTESTNAME, GETTESTDESC, and GETTESTMODE to register and present the test, then GETDEFAULTTESTPARAMS, INIT, RUNTEST, and CLEANUP to execute it. Custom code may call GET_MESSAGE_NAME directly to resolve a stored message identifier into a displayable name. Wrapped with the standard EBS header guard, the package body should be compiled against APPS and is supported on both 12.1.1 and 12.2.2; it is referenced by five other packages, so changes should be regression-tested across those dependents.
-
PACKAGE BODY: APPS.BSC_OBJECTIVE_METADATA_SETUP
12.1.1
-
PACKAGE BODY: APPS.GL_PUBLIC_SECTOR
12.1.1
-
PACKAGE BODY: APPS.GL_PUBLIC_SECTOR
12.2.2
-
PACKAGE: APPS.GL_PUBLIC_SECTOR
12.2.2
-
PACKAGE: APPS.GL_PUBLIC_SECTOR
12.1.1
-
APPS.BSC_OBJECTIVE_METADATA_SETUP SQL Statements
12.1.1
-
PACKAGE: APPS.BSC_OBJECTIVE_METADATA_SETUP
12.1.1
-
PACKAGE: APPS.AMS_CPYUTILITY_PVT
12.1.1
-
PACKAGE: APPS.AMS_CPYUTILITY_PVT
12.2.2
-
PACKAGE: APPS.OE_MSG
12.2.2
-
PACKAGE: APPS.OE_MSG
12.1.1
-
PACKAGE: APPS.PON_RESPONSE_PVT
12.2.2
-
PACKAGE: APPS.PON_RESPONSE_PVT
12.1.1
-
PACKAGE BODY: APPS.IRC_NOTIFICATION_WORKFLOW_PKG
12.2.2
-
PACKAGE BODY: APPS.AMS_CPYUTILITY_PVT
12.1.1
-
PACKAGE BODY: APPS.AMS_CPYUTILITY_PVT
12.2.2
-
PACKAGE BODY: APPS.OE_MSG
12.1.1
-
PACKAGE BODY: APPS.OE_MSG
12.2.2
-
PACKAGE BODY: APPS.PON_RESPONSE_PVT
12.1.1
-
PACKAGE BODY: APPS.PON_RESPONSE_PVT
12.2.2
-
APPS.BSC_OBJECTIVE_METADATA_SETUP dependencies on JTF_DIAGNOSTIC_ADAPTUTIL
12.1.1
-
APPS.PON_RESPONSE_PVT dependencies on PON_INTERFACE_ERRORS
12.2.2
-
APPS.PON_RESPONSE_PVT dependencies on PON_INTERFACE_ERRORS
12.1.1
-
APPS.GL_PUBLIC_SECTOR dependencies on GL_PUBLIC_SECTOR
12.1.1
-
APPS.GL_PUBLIC_SECTOR dependencies on GL_PUBLIC_SECTOR
12.2.2
-
APPS.BSC_OBJECTIVE_METADATA_SETUP dependencies on JTF_DIAG_INPUTTBL
12.1.1
-
APPS.BSC_OBJECTIVE_METADATA_SETUP dependencies on JTF_DIAGNOSTIC_COREAPI
12.1.1
-
APPS.IRC_NOTIFICATION_WORKFLOW_PKG dependencies on FND_NEW_MESSAGES
12.2.2
-
APPS.GL_PUBLIC_SECTOR dependencies on FND_USER
12.2.2
-
APPS.BSC_OBJECTIVE_METADATA_SETUP dependencies on FND_MESSAGE
12.1.1
-
APPS.IRC_NOTIFICATION_WORKFLOW_PKG dependencies on FND_USER
12.2.2
-
APPS.GL_PUBLIC_SECTOR dependencies on FND_USER
12.1.1
-
APPS.IRC_NOTIFICATION_WORKFLOW_PKG dependencies on DBMS_SESSION
12.2.2
-
PACKAGE: APPS.BENUTILS
12.1.1
-
PACKAGE: APPS.BENUTILS
12.2.2
-
APPS.BEN_DETERMINE_COMMUNICATIONS SQL Statements
12.2.2
-
APPS.BEN_DETERMINE_COMMUNICATIONS SQL Statements
12.1.1
-
APPS.IRC_NOTIFICATION_WORKFLOW_PKG dependencies on FND_PROFILE
12.2.2
-
APPS.PON_RESPONSE_PVT dependencies on PON_BID_HEADERS
12.2.2
-
APPS.PON_RESPONSE_PVT dependencies on PON_BID_HEADERS
12.1.1
-
APPS.BEN_DETERMINE_COMMUNICATIONS dependencies on BENUTILS
12.2.2
-
APPS.BEN_DETERMINE_COMMUNICATIONS dependencies on BENUTILS
12.1.1
-
PACKAGE BODY: APPS.BENUTILS
12.1.1
-
PACKAGE BODY: APPS.BENUTILS
12.2.2
-
PACKAGE BODY: APPS.BEN_DETERMINE_COMMUNICATIONS
12.1.1
-
PACKAGE BODY: APPS.BEN_DETERMINE_COMMUNICATIONS
12.2.2
-
APPS.IRC_NOTIFICATION_WORKFLOW_PKG dependencies on HR_UTILITY
12.2.2