Search Results set_rec_status

Overview

EDR_FWK_TEST_POST_OP is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM (E-Business Suite Technical Reference Manual) taxonomy as an "OTHER" API. The package forms part of the EDR (Electronic Data Review or E-Records) framework, a subsystem that supports configuration and verification utilities referenced by the EDR_FWK_TEST_B base table. The package header carries the version identifier EDRFWTSS.pls 120.0.12000000.1, dated 18-JAN-2007, indicating an early-stage framework utility rather than a core transactional API.

The stated purpose of the package, expressed directly in its embedded comments, is to execute a "Post Operation API." In Oracle EBS terminology, a post-operation routine is invoked after a primary business process has completed its main work, typically to finalize state, record outcome status, or reconcile dependent records. EDR_FWK_TEST_POST_OP therefore serves a narrow but well-defined role: performing the post-processing step for records governed by the EDR framework test data model.

The package is small and self-contained. It exposes exactly one public program unit and references a single underlying table via an APPS synonym. It is not referenced by any other documented package, which indicates that it is invoked directly by external callers — concurrent programs, forms, or custom code — rather than composed into a larger package hierarchy.

Key Procedures and Functions

The metadata documents one procedure in the package specification:

• SET_REC_STATUS — the sole public program unit. As the name implies, this procedure sets the record status for a framework test record. It is declared to accept a single numeric argument naming the framework test identifier. Because the ETRM extract confirms only the procedure name and its documented argument of a numeric test identifier, parameter lists beyond this should not be inferred. The procedure is intended to be called as the post-operation step, meaning it runs after a preceding operation has completed and updates the status column of the identified test record to reflect the outcome.

No functions are declared in the specification, and no additional procedures are exposed. The package body is not documented in the ETRM excerpt, so any private helper logic remains an implementation detail.

Tables Accessed

The documented table reference is:

• EDR_FWK_TEST_B — the base table for EDR framework test records, accessed through its APPS synonym. The _B suffix conventionally denotes the base (non-translated) table in an EBS entity-attribute model, where a companion _TL table usually holds translated columns. SET_REC_STATUS operates against this table to update the status of the row identified by the incoming test identifier. This is consistent with the purpose of a post-operation API: the row already exists, and the procedure mutates its status rather than inserting new data.

No other tables are documented as referenced by this package, and no distributed or remote table access is indicated.

Usage Notes

EDR_FWK_TEST_POST_OP is a framework utility rather than an end-user-facing component. Because the package is referenced by zero other documented packages, invocation is expected to come from one of three sources:

• Concurrent programs or request sets that orchestrate EDR framework validation or testing sequences and require the post-operation status update.
• Oracle Forms or OAF pages that trigger the framework's test flow and call the post-operation API upon completion, passing the current framework test identifier.
• Custom or diagnostic code written by implementers to exercise the EDR framework test model during configuration and verification.

Since the API boundary described by the specification contains only SET_REC_STATUS, callers should treat the package as a single-purpose status setter and avoid depending on internal behavior. The 2007 header date and the "TEST" naming indicate that this object belongs to a verification framework shipped for configuration and regression purposes; it is not part of the core Order-to-Cash or Procure-to-Pay transaction path. In 12.1.1 and 12.2.2 the object remains identical, as it was not materially revised between those releases, and it continues to rely on an APPS synonym for its table access, meaning customizations should preserve the EDR_FWK_TEST_B synonym rather than hardcoding a schema qualifier.