Results for “prc_code”

50+ results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AMW_EXPORT_PROCESS_V is a database view historically shipped with the Oracle Internal Controls Manager (ICM) module, registered under the AMW product short code. Internal Controls Manager was an E-Business Suite application used to document, test, and certify internal controls in support of regulatory compliance initiatives such as Sarbanes-Oxley. In ETRM 12.2.2 metadata the module is flagged as obsolete, and the object itself is documented as not implemented in the reference database, meaning the view is provided for historical and migration reference only and will not exist in a standard 12.1.1 or 12.2.2 installation unless ICM was previously licensed and installed.

Functionally, the view flattens the hierarchical relationship between parent and child business processes maintained in the AMW process repository. Rather than returning raw lookup codes, it resolves descriptive meanings through correlated subqueries against AMW_LOOKUPS, producing a reporting-friendly projection suitable for export routines. The name AMW_EXPORT_PROCESS_V reflects this role: it supplies the process-level dataset consumed by export, integration, or third-party reporting processes that extract ICM process definitions outside the application UI.

Underlying Base Objects

The view text references the following base objects:

  • ALHRV — the driving alias, supplying child and parent process identifiers, order numbers, codes, display names, approval status, process category, significant-process and standard-process flags, and the immediate parent relationship. This alias behaves as a denormalized process-hierarchy source.
  • APHD — joined to expose PROCESS_ID as PRNT_ID, the top-level parent identifier.
  • AMW_LOOKUPS — queried repeatedly via scalar subqueries to translate stored codes into user-facing meanings for revise, approval, type, category, significant, standard, and control activity attributes.
  • AMW_PROCESS — referenced in a nested subquery to retrieve the PROCESS_TYPE for a given child process where END_DATE and DELETION_DATE are null.

Because the view is defined over AMW process and lookup tables, its output is entirely dependent on the integrity and currency of the ICM process repository; no standard Oracle application tables such as FND_ or PER_ are involved.

Key Columns

Common Use Cases and Queries

Typical scenarios include exporting the ICM process inventory for external audit tooling, validating that every active process resolves to a valid enabled lookup meaning, and reconciling parent-child hierarchy for certification reporting.

SELECT prc_id, prc_code, prc_name, prc_sts, prc_type, prnt_name
FROM   amw_export_process_v
ORDER  BY seq_num;

To isolate approved significant processes for audit sampling:

SELECT prc_code, prc_name, prc_type
FROM   amw_export_process_v
WHERE  prc_sts = 'Approved'
AND    prc_sig = 'Yes';

When the user search term "pk1_value" appears in navigation or form metadata, it refers to a key-flexfield or primary-key surrogate used by the originating ICM form, not to a column exposed by this view, so queries should join back to the base process tables if that identifier is required. Note also that the subqueries enforce ENABLED_FLAG='Y' and current effective dates, so rows may disappear if lookup values are end-dated.