Results for “result_code”

8 results




Overview
Explore in AI Chat

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

Overview

GMS_RESG_BC_V is a view owned by the APPS schema in Oracle E-Business Suite, belonging to the GMS – Grants Accounting product family. It is documented as a retrofitted object, meaning it was carried forward from an earlier release and re-registered against the current data model rather than being designed anew for Release 12.1.1 or 12.2.2. The view presents budget and actual packet information from Grants Accounting combined with resource list member hierarchy data sourced from Oracle Projects. Its principal function is to expose resource list member activity alongside the parent member identifier, which is derived by resolving each resource list member to its parent in the resource list structure.

Because the view filters on transferred packets whose result code begins with the letter "F", it functions as a reporting and integration surface for finalized, transferred budget or cost packet lines. In practice this supports downstream reporting, reconciliation between Grants Accounting and Oracle Projects, and any custom interface that needs to attribute amounts to a parent resource list member rather than only to the leaf member.

Underlying Base Objects

The view text is defined over two documented base objects, both exposed to APPS as synonyms:

The join is an equality join between GBC.RESOURCE_LIST_MEMBER_ID and PRM.RESOURCE_LIST_MEMBER_ID. The PARENT_MEMBER_ID column is computed with an NVL expression: when the resource list member has a parent, the parent identifier is returned; when it does not, the member's own identifier is returned. This yields a self-referencing parent key that is always populated, simplifying grouping and roll-up logic in downstream queries. Two predicates further restrict the row set: the result code must begin with "F", and the transfer flag must equal "Y".

Key Columns

  • PROJECT_ID, AWARD_ID, TASK_ID, TOP_TASK_ID – project, award, task, and top task context for the packet line.
  • RESOURCE_LIST_MEMBER_ID – the leaf resource list member associated with the packet line.
  • PARENT_MEMBER_ID – the resolved parent member, or the member itself when no parent exists; central to roll-up reporting.
  • BUDGET_VERSION_ID – identifies the budget version against which the line is recorded.
  • EXPENDITURE_ITEM_DATE – the expenditure item date for the line, used for period-based reporting.
  • STATUS_CODE and RESULT_CODE – processing status and outcome; the view only returns result codes beginning with "F".
  • ACTUAL_FLAG – distinguishes actual versus budgetary amounts.
  • ENTERED_DR and ENTERED_CR – entered debit and credit amounts, in the entered currency.

Common Use Cases and Queries

Typical usage includes rolling up transferred amounts from leaf members to parents, reconciling Grants Accounting packets against Projects resource lists, and feeding custom extracts that require a guaranteed parent member key. Because the view already applies the transferred and result code filters, callers do not need to repeat them.

A representative query returns parent-level totals for a project:

  • SELECT project_id, parent_member_id, actual_flag, SUM(entered_dr) dr, SUM(entered_cr) cr FROM gms_resg_bc_v WHERE project_id = :p_project_id GROUP BY project_id, parent_member_id, actual_flag;

A second pattern lists packet lines within a date range for a budget version:

  • SELECT project_id, award_id, task_id, resource_list_member_id, parent_member_id, expenditure_item_date, result_code, entered_dr, entered_cr FROM gms_resg_bc_v WHERE budget_version_id = :p_version_id AND expenditure_item_date BETWEEN :p_from AND :p_to;

Queries should account for the entered amounts being in the entered currency, and should join to relevant Projects or Grants tables when descriptions or currency codes are required, since the view exposes identifiers and amounts only.