Search Results get_total_sub_process
Overview
The APPS.AMW_ORG_PROC_CERT_DATED_SUMM package belongs to the Oracle E-Business Suite Enterprise Transaction Risk Management (ETRM) module, historically referenced as the Application Management Workspace (AMW) schema. Its principal business function is to provide aggregated, date-bounded summary counts of organizational risk and control activity associated with a specific certification. The package answers fundamental compliance questions such as: how many unmitigated risks exist for a given organization, how many risk evaluations have been captured within a defined period, and how many controls have been tested or found ineffective. These counts feed certification reporting, management dashboards, and audit defensibility evidence used during Sarbanes-Oxley (SOX) and internal control over financial reporting (ICFR) initiatives. The _DATED_SUMM suffix indicates that results are filtered by evaluation dates, which distinguishes this package from non-temporal aggregations elsewhere in the ETRM schema. All functions are read-only; the package contains no DML and is classified as an OTHER API, meaning it is invoked internally rather than exposed as a public integration interface.
Key Procedures and Functions
The package exposes twenty-five documented functions and procedures. The most prominent group answers risk-related questions at the organization level. GET_UNMIT_RISK_FOR_ORG, the function surfaced by the user's search term, returns the count of unmitigated risks for a certification and organization, optionally restricting to evaluations created within a date range and optionally restricted to material risks only. GET_EVAL_RISK_FOR_ORG returns the count of evaluated risks over the same filters, while GET_TOTAL_RISKS_FOR_ORG returns the total risk population for the organization. Entity risks are included in all three.
A parallel family operates at the organization-process level, using the _FOR_ORG_PROC suffix: GET_UNMIT_RISK_FOR_ORG_PROC, GET_EVAL_RISK_FOR_ORG_PROC, and GET_TOTAL_RISKS_FOR_ORG_PROC. Control-oriented equivalents include GET_EVAL_CTRLS_FOR_ORG, GET_TOTAL_CTRLS_FOR_ORG, GET_INEFF_CTRLS_FOR_ORG, and the process-scoped variants GET_INEFF_CTRLS_FOR_ORG_PROC, GET_EVAL_CTRLS_FOR_ORG_PROC, and GET_TOTAL_CTRLS_FOR_ORG_PROC. The control counts accept a key-controls flag to restrict results to key controls. Structural and issue-tracking functions round out the package, including GET_ALL_PROCESS_IN_ORG, GET_CERT_PROCESS_IN_ORG, GET_PROCESS_CERT_ISSUES_IN_ORG, GET_TOTAL_ORG, GET_TOTAL_ORG_CERT_ISSUES, GET_TOTAL_ORG_CERT, GET_TOTAL_SUB_PROCESS, and GET_CERT_SUB_PROCESS. These enumerate the processes, sub-processes, organizations, and certification issues within scope.
Tables Accessed
The package reads from ten documented tables via APPS synonyms. Risk data is sourced from AMW_RISKS_B and correlated through AMW_RISK_ASSOCIATIONS. Control data originates in AMW_CONTROLS_B with relationships held in AMW_CONTROL_ASSOCIATIONS. Organizational and process structure is resolved through AMW_PROCESS, AMW_PROCESS_ORGANIZATION, and AMW_ENTITY_HIERARCHIES, the latter enabling entity-level roll-ups. Certification state and history are captured in AMW_OPINIONS_LOG, while AMW_EXECUTION_SCOPE defines which organizations and processes fall within the assessment boundary for a given certification cycle. Each query is read-only and aggregate in nature.
Usage Notes
Because the package is classified as OTHER and is referenced by no other PL/SQL packages, it is invoked directly rather than through a layered API. Typical callers include Oracle ETRM certification summary forms, OAF-based certification dashboards, and concurrent programs that generate certification status reports. The documented p_from_date and p_to_date parameters allow reporting over defined evaluation windows, while p_material_risks_flag and p_key_ctrls_flag filter risk and control populations to significant items. Custom code should call these functions only after resolving valid certification_id and org_id values from the certification configuration tables, and should treat return values as point-in-time counts, since no caching or staging is performed by the package itself.