Search Results generate_approver_table_html

Overview

APPS.BEN_CWB_RSGN_EMP is the Compensation Workbench (CWB) reassignment of employee package in Oracle E-Business Suite, delivered as part of the Advanced Benefits (BEN) product family. Its principal responsibility is to support the reassignment of employees between managers and hierarchies during the Compensation Workbench approval cycle. The package encapsulates the server-side logic used by the CWB reassignment workflow, including verification of the acting approver's authority, persistence of approval decisions, storage and removal of employee detail rows, and generation of the HTML notification bodies used in workflow messages.

The package is declared with AUTHID CURRENT_USER and its header carries the revision string bencwbre.pkh 120.0.12000000.1, indicating that the specification has been stable since the 11.5.10 code line and is shipped unchanged in the 12.1.1 and 12.2.2 releases. The header comment block records the historical evolution of the package from its creation in July 2002, through Global Budgeting changes in 2004, to the addition of the NOCOPY hint and CWB Itemization support. The package is classified as OTHER in the ETRM registry and is referenced by no other documented packages, which indicates that it is an entry point called by Oracle Workflow rather than by other PL/SQL APIs.

Key Procedures and Functions

The package exposes sixteen documented procedures. The two most relevant to the "check_approver" search term are described first.

• CHECK_APPROVER — This is a standard Oracle Workflow function activity signature (itemtype, itemkey, actid, funcmode, result). It evaluates whether the current user or role is entitled to act as the approver for the reassignment workflow at the current activity, returning the workflow result code that determines the branch taken by the process.
• STORE_APPROVAL_DETAILS — Persists the approval action taken by the approver, using the same five-parameter workflow function signature.
• SET_APPROVAL and SET_REJECTION — Record the approve or reject decision made by the approver against the transaction.
• CURR_WS_MGR_CHECK and PROP_WS_MGR_CHECK — Validate the current workspace manager and the proposed workspace manager respectively, supporting the manager reassignment path.
• IS_IN_COMP_MANAGER_ROLE — Determines whether the acting user holds the compensation manager role, returning a boolean-style result used by the approval checks.
• STORE_EMP_DETAILS and REMOVE_EMP_DETAILS — Insert and delete the employee rows that constitute the reassignment set.
• START_WORKFLOW and SEND_FYI_NOTIFICATIONS — Launch the reassignment workflow and dispatch informational notifications to interested parties.
• WHICH_MESSAGE — Resolves the appropriate notification message name.
• GENERATE_DETAIL_HTML, GENERATE_EMPLOYEE_TABLE_HTML, GENERATE_APPROVER_TABLE_HTML, and GENERATE_ERROR_HTML — Render the HTML fragments embedded in the workflow notification bodies.

Tables Accessed

The package reads and writes CWB configuration and transaction data through APPS synonyms. BEN_CWB_GROUP_HRCHY, BEN_CWB_PERSON_GROUPS, BEN_CWB_PL_DSGN and BEN_PER_IN_LER supply the group hierarchy, person group, plan design and eligibility context that determine which employees may be reassigned. BEN_TRANSACTION and BEN_TRANSACTION_S hold the transaction header and lines updated when an approval or rejection is recorded. Workflow state is read from WF_ITEM_ACTIVITY_STATUSES, while approval and role determination use PQH_ROLES, FND_USER and PER_PEOPLE_EXTRA_INFO. PER_ALL_PEOPLE_F provides the employee and manager attributes, FND_NEW_MESSAGES supports message lookup, and DUAL is used for scalar evaluations. All access is subject to the standard APPS security model inherited through AUTHID CURRENT_USER.

Usage Notes

BEN_CWB_RSGN_EMP is not intended for direct invocation by custom code. It is registered as the PL/SQL implementation behind the Compensation Workbench reassignment workflow, and Oracle Workflow invokes its function activities (CHECK_APPROVER, STORE_APPROVAL_DETAILS, and the associated result-returning routines) through the standard itemtype/itemkey/actid/funcmode/result interface. The HTML generation routines are called from the notification message templates, and the workflow start and FYI routines are triggered when a reassignment request is submitted or completed. Because the ETRM registry shows no referencing packages and no public API classification, customers extending Compensation Workbench reassignment should call the documented procedures only from within a Workflow function activity context, and should treat the package signature as fixed across 12.1.1 and 12.2.2 unless a patch or the 12.2 Online Patching editioning view changes the underlying object.