Search Results get_test_scenario_details

Overview

EDR_MSCA_UTIL is a utility package body owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM (E-Records and Transaction Manager) product family. Its header timestamp ($Header: EDRVMTLB.pls 120.1.12000000.1 2007/01/18) confirms it is a long-standing component retained across both Oracle EBS 12.1.1 and 12.2.2. The package provides supporting services for the e-records and electronic signature framework, notably the retrieval of e-record text from the evidence repository and the resolution of lookup values used throughout the EDR modules. It does not implement business transactions itself; rather it supplies reusable helper routines consumed by other EDR components and by custom extensions that need to surface e-record or lookup data.

Key Procedures and Functions

• GET_ERECORD_TEXT — Retrieves the text representation of an e-record for a given e-record identifier. Internally it delegates to EDR_PSIG.getDocumentDetails to obtain the document, its parameters and signatures, and raises EDR_PSIG_DOCERR when the underlying call returns a non-null error number. If the document format is TEXT or text/plain, the procedure reads a bounded portion of the LOB via DBMS_LOB.SUBSTR, otherwise it returns a blank placeholder. Errors are captured through SQLERRM and re-raised to the caller.
• GET_LOOKUP — Resolves a lookup value by opening an explicit cursor over FND_LOOKUP_VALUES_VL, filtering on LOOKUP_TYPE and a case-insensitive prefix match (LIKE) against the supplied meaning, returning the MEANING and LOOKUP_CODE. This routine directly addresses the user's get_lookup search term and is the standard mechanism within EDR_MSCA_UTIL for translating descriptive meanings into lookup codes.
• GET_APPROVERS — Returns the set of approvers associated with an e-record or signature context, sourcing data from the EDR signature tables. It supports workflow and signing-cycle determination for e-records.
• GET_TEST_SCENARIO_DETAILS — Supplies the detail rows for inter-event test scenarios, drawn from EDR_INTER_EVENT_TEST_SCENARIOS. This is used primarily for configuration validation and testing of e-record event handling.

Tables Accessed

• FND_LOOKUP_VALUES_VL — the core Oracle EBS lookup view, read by GET_LOOKUP to map meanings to lookup codes.
• EDR_ERECORDS — the master e-record table, read to resolve e-record identifiers and related attributes.
• EDR_ESIGNATURES — the electronic signature table, consulted by GET_APPROVERS to determine signatories or approvers.
• EDR_INTER_EVENT_TEST_SCENARIOS — the test scenario configuration table used by GET_TEST_SCENARIO_DETAILS.
• DBMS_LOB — the Oracle-supplied LOB package invoked by GET_ERECORD_TEXT to read document content safely within size limits.

Usage Notes

EDR_MSCA_UTIL is a pure utility package with no concurrent program or form of its own, and the metadata records zero other packages referencing it directly, which indicates it is invoked from UI-layer or custom code rather than from a tightly coupled EDR API chain. Typical invocation points include OAF or Forms-based EDR screens that display e-record text or require lookup resolution, and custom PL/SQL wrappers that call GET_LOOKUP before rendering a value list. In 12.1.1 and 12.2.2 the package behaves identically since the header carries the 120.1.12000000.1 version across both releases. Because the procedures rely on OUT NOCOPY parameters and raise exceptions rather than returning status codes, callers must declare matching PL/SQL types (l_genref, VARCHAR2) and handle the propagated errors. Extensions should treat GET_LOOKUP as read-only against FND_LOOKUP_VALUES_VL and should not bypass it in favour of direct SQL where consistent meaning-to-code resolution is required.