Search Results update_pcd_sent_dt
Overview
APPS.BEN_BENHIPAA_XMLP_PKG is the package body that supports the Oracle E-Business Suite benefits HIPAA (Health Insurance Portability and Accountability Act) report, a concurrent program used to monitor certificate-of-creditable-coverage and waiting-period data. In Oracle EBS 12.1.1 and 12.2.2, this package provides the PL/SQL formulas, report-level triggers, and data-maintenance logic required by the corresponding XML Publisher (BI Publisher) report definition. The package contains no standalone business entity of its own; instead it acts as a "report package," orchestrating calculations that format coverage and waiting-period dates for the HIPAA extract while also recording the date on which a participant's certificate was sent to the carrier. The header comment indicates a build of 120.1.12010000.3, dated 2009/02/04, which reflects the version lineage carried into the 12.x code lines. Because the package is classified as OTHER (not a public API), it is intended for internal runtime use by the report rather than as a callable integration interface.
Key Procedures and Functions
- CF_STANDARD_HEADERFORMULA — Returns the numeric literal 1 as the value of the report-standard header formula, a common XML Publisher placeholder used to signal that the header section should render.
- CF_WAIT_START_DTFORMULA — Calculates and formats the waiting-period start date. It first invokes UPDATE_PCD_SENT_DT to persist the certificate-sent date, then returns a formatted date string (MM/DD/RR) only when the coverage period spans fewer than 365 days; otherwise it returns 'N/A'.
- CF_WAIT_PERD_CMPLTN_DTFORMULA — Formats the waiting-period completion date using the same under-365-day business rule, returning 'N/A' when the coverage span is one year or more.
- UPDATE_PCD_SENT_DT — The procedure directly associated with the user's search term "update_pcd_sent_dt." It updates the SENT_DT column on BEN_PER_CM_PRVDD_F for the given participant/carrier-provided record and effective date, conditioned on SENT_DT being null and the effective date falling within the record's effective date range. Because of its PRAGMA AUTONOMOUS_TRANSACTION declaration, the update and its commit execute independently of the calling report transaction, ensuring the sent-date stamp persists even if the report later fails.
- AFTERREPORT — Returns TRUE; a hook for post-report processing (the standard HR report event call is commented out).
- BEFOREREPORT — Returns TRUE; a hook for pre-report processing.
Tables Accessed
The package references a single table via its APPS synonym: BEN_PER_CM_PRVDD_F (Benefits Person Communication Provided Fact). This is the benefits datastore that holds participant-level coverage and carrier-provided information, including the SENT_DT timestamp updated by UPDATE_PCD_SENT_DT. The report reads effective dates, coverage end dates, original enrollment dates, waiting-period start and completion dates, and the primary key PER_CM_PRVDD_ID from this table to drive both the date formatting functions and the autonomous update.
Usage Notes
Because the package contains no called-by relationships (referenced by 0 other packages), it is invoked exclusively by the BEN HIPAA XML Publisher report data template and concurrent program. The typical invocation flow is: the concurrent request runs the report, the XML Publisher engine calls CF_WAIT_START_DTFORMULA during row expansion, that function conditionally calls UPDATE_PCD_SENT_DT, and the autonomous commit writes SENT_DT immediately. Release 12.1.1 and 12.2.2 share the same package logic; no online forms, public APIs, or custom extensions should call these procedures directly, as the interface is undocumented and unsupported for external reuse. Administrators investigating a coverage certificate that never received a SENT_DT stamp should verify that the report executed and that the effective date fell within the record's effective date range.
-
APPS.BEN_BENHIPAA_XMLP_PKG SQL Statements
12.1.1
-
APPS.BEN_BENHIPAA_XMLP_PKG SQL Statements
12.2.2
-
APPS.BEN_BEN_US_COBNL_XMLP_PKG SQL Statements
12.1.1
-
APPS.BEN_BEN_US_COBNL_XMLP_PKG SQL Statements
12.2.2
-
PACKAGE BODY: APPS.BEN_BENHIPAA_XMLP_PKG
12.1.1
-
PACKAGE BODY: APPS.BEN_BENHIPAA_XMLP_PKG
12.2.2
-
PACKAGE: APPS.BEN_BENHIPAA_XMLP_PKG
12.1.1
-
PACKAGE BODY: APPS.BEN_BEN_US_COBNL_XMLP_PKG
12.2.2
-
PACKAGE: APPS.BEN_BENHIPAA_XMLP_PKG
12.2.2
-
PACKAGE BODY: APPS.BEN_BEN_US_COBNL_XMLP_PKG
12.1.1
-
PACKAGE: APPS.BEN_BEN_US_COBNL_XMLP_PKG
12.1.1
-
PACKAGE: APPS.BEN_BEN_US_COBNL_XMLP_PKG
12.2.2
-
APPS.BEN_BEN_US_COBNL_XMLP_PKG dependencies on DUAL
12.2.2
-
APPS.BEN_BENHIPAA_XMLP_PKG dependencies on STANDARD
12.1.1
-
APPS.BEN_BEN_US_COBNL_XMLP_PKG dependencies on DUAL
12.1.1
-
APPS.BEN_BENHIPAA_XMLP_PKG dependencies on BEN_PER_CM_PRVDD_F
12.1.1
-
APPS.BEN_BENHIPAA_XMLP_PKG dependencies on BEN_PER_CM_PRVDD_F
12.2.2
-
APPS.BEN_BEN_US_COBNL_XMLP_PKG dependencies on STANDARD
12.1.1
-
APPS.BEN_BEN_US_COBNL_XMLP_PKG dependencies on STANDARD
12.2.2
-
APPS.BEN_BENHIPAA_XMLP_PKG dependencies on STANDARD
12.2.2