Results for “ind_cost_code”

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

Overview

GMS_CDL_BURDEN_DETAIL_V is an APPS-owned database view within the Oracle E-Business Suite (EBS) Grants Accounting (GMS) module. It exposes burden (indirect cost) calculation detail by joining Grants Accounting award distribution records in GMS_AWARD_DISTRIBUTIONS to the Oracle Projects cost distribution, expenditure, and indirect costing infrastructure in PA. The view presents one row per awarded and active expenditure item burden line, combining project/task identifiers, raw cost, compiled multiplier, cost base, indirect cost code, and rate schedule revision information. Its principal role is to support grants burden processing and reporting — most notably driven by the GMS_BURDEN_COSTING package, which references this view when creating burden cost distributions for sponsored awards. In EBS 12.1.1 and 12.2.2 the object remains VALID and is deployed under the APPS schema, making it queryable by reporting tools, custom concurrent programs, and integration extracts. The view is particularly relevant when diagnosing why an award distribution line did not yield a burden entry, because the join predicates govern which rows qualify for inclusion.

Underlying Base Objects

The view is defined over a set of PA and GMS synonyms. The primary Grants-side object is GMS_AWARD_DISTRIBUTIONS (ADL), which supplies AWARD_ID, AWARD_SET_ID, ADL_STATUS, ADL_LINE_NUM, RAW_COST, BURDENABLE_RAW_COST, IND_COMPILED_SET_ID, and CDL_LINE_NUM. The PA side contributes PA_COST_DISTRIBUTION_LINES_ALL (CDL), PA_EXPENDITURE_ITEMS_ALL (EI), PA_EXPENDITURES_ALL (E), PA_PROJECTS_ALL (P), PA_PROJECT_TYPES (PT), and PA_TRANSACTION_SOURCES (PTS), plus the indirect costing structures PA_IND_COST_CODES, PA_COMPILED_MULTIPLIERS, PA_IND_COMPILED_SETS, PA_COST_BASE_EXP_TYPES, PA_COST_BASES, PA_IND_RATE_SCH_REVISIONS, and PA_IND_RATE_SCHEDULES_ALL_BG. Joins pivot on IND_COMPILED_SET_ID, IND_RATE_SCH_REVISION_ID, COST_PLUS_STRUCTURE, COST_BASE, EXPENDITURE_TYPE, and ORGANIZATION_ID, enforced through the NVL of EI.OVERRIDE_TO_ORGANIZATION_ID and E.INCURRED_BY_ORGANIZATION_ID. The package GMS_BURDEN_COSTING is also documented as a referenced object, reflecting the view's operational use in burden generation.

Key Columns

• PROJECT_ID, TASK_ID, SEGMENT1 — project, task, and project number context.
• ORGANIZATION_ID, GL_DATE, PA_DATE — incurring organization and accounting/tie-back dates.
• AWARD_ID, AWARD_SET_ID, ADL_LINE_NUM, LINE_NUM — award distribution line identity.
• ADL_STATUS, LINE_TYPE, BURDEN_SUM_SOURCE_RUN_ID, BURDEN_SUM_REJECTION_CODE — status and burden summarization diagnostics; the ADL_STATUS column is central to the user search "adl_status".
• IND_COST_CODE, IND_RATE_SCH_ID, IND_RATE_SCH_REVISION_ID — indirect cost code and rate schedule/revision.
• COST_BASE, COMPILED_MULTIPLIER, BURDENABLE_RAW_COST — the base, multiplier, and burdenable amount combined by NVL(ADL.BURDENABLE_RAW_COST,0) * CM.COMPILED_MULTIPLIER.
• EI_EXPENDITURE_TYPE, ICC_EXPENDITURE_TYPE, RAW_COST, EXPENDITURE_ITEM_ID, EXPENDITURE_ITEM_DATE, SYSTEM_LINKAGE_FUNCTION — project expenditure attributes.

Common Use Cases and Queries

Typical scenarios include reconciliations of burdened versus raw award cost, troubleshooting rejected burden sum lines, and auditing which award distributions have ADL_STATUS = 'A'. The view's WHERE clause forces ADL_STATUS = 'A', FC_STATUS = 'A', DOCUMENT_TYPE = 'EXP', BURDENABLE_RAW_COST not equal to zero, and a burdenable cost distribution line, so rejected or inactive distributions are excluded.

Example query — active burden detail by project:

• SELECT project_id, task_id, award_id, adl_line_num, ind_cost_code, compiled_multiplier, raw_cost, adl_status FROM apps.gms_cdl_burden_detail_v WHERE project_id = :project_id;

Example query — investigate burden rejection:

• SELECT award_id, adl_line_num, burden_sum_source_run_id, burden_sum_rejection_code FROM apps.gms_cdl_burden_detail_v WHERE burden_sum_rejection_code IS NOT NULL;

Because ADL_STATUS is filtered to 'A' within the view, queries intended to inspect other statuses must query GMS_AWARD_DISTRIBUTIONS directly rather than this view.