Results for “lp_12”

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

Overview

APPS.GMS_AWARDS_V is a reporting and integration view in the Oracle E-Business Suite Grants Management (GMS) module. It exposes a consolidated, denormalized representation of award records held in the GMS_AWARDS table, enriching each award with decoded lookup meanings, customer and party names, billing and invoicing attributes, funding summaries, and operating unit information. The view is owned by the APPS schema and is available in EBS 12.1.1 and 12.2.2.

The "lp_12" reference in the requested search string corresponds to one of the many lookup joins embedded in the view text. Specifically, LP_12.MEANING supplies the decoded value for AWD.AWARD_PURPOSE_CODE, which is the award purpose classification column. The view relies on several aliased lookup subqueries (LP_2, LP_4, LP_6 through LP_12), each resolving a different code column against GMS_LOOKUPS. Because the view pre-joins these lookups, report developers do not need to write separate lookup resolution logic when presenting award data.

The view functions primarily as a read-only source for operational reports, grants dashboards, and external integrations that need award header information together with descriptive text rather than raw codes.

Underlying Base Objects

The view is defined over the following documented base objects: FND_PROFILE (PACKAGE), GMS_ALLOWABILITY_SCHEDULES (SYNONYM), GMS_AWARDS (SYNONYM), GMS_LOOKUPS (VIEW), GMS_OPERATING_UNITS_V (VIEW), GMS_SECURITY (PACKAGE), HR_ALL_ORGANIZATION_UNITS (SYNONYM), HZ_CUST_ACCOUNTS (SYNONYM), HZ_PARTIES (SYNONYM), MO_GLOBAL (PACKAGE), PA_AGREEMENTS_ALL (SYNONYM), PA_IND_RATE_SCHEDULES (VIEW), PA_INVOICE_FORMATS (SYNONYM), PA_SUMMARY_PROJECT_FUNDINGS (SYNONYM), PA_UTILS (PACKAGE), RA_TERMS (SYNONYM), and DUAL (TABLE).

The centric object is GMS_AWARDS, aliased AWD, supplying the majority of columns. GMS_LOOKUPS is joined repeatedly to decode codes such as status, billing offset, amount type, boundary code, and the fund control level columns. HZ_CUST_ACCOUNTS and HZ_PARTIES provide the customer account identifier and party name, exposed twice (as Customer_name and CUSTOMER_NAME) to distinguish the award customer from the bill-to customer. PA_AGREEMENTS_ALL supplies the agreement number, PA_IND_RATE_SCHEDULES supplies the indirect rate schedule name, PA_INVOICE_FORMATS resolves both labor and non-labor invoice format names, and PA_SUMMARY_PROJECT_FUNDINGS provides accrued and billed amounts. HR_ALL_ORGANIZATION_UNITS contributes the operating unit name, and GMS_OPERATING_UNITS_V and the GMS_SECURITY and MO_GLOBAL packages enforce organizational security filtering.

Key Columns

• AWARD_ID / AWARD_NUMBER / AWARD_SHORT_NAME / AWARD_FULL_NAME — Primary identifiers and descriptive names for the award.
• AWARD_PROJECT_ID, AGREEMENT_ID, Transaction_number — Links to the associated project, agreement, and transaction reference.
• Customer_id, Customer_name, BILL_TO_CUSTOMER_ID, CUSTOMER_NAME — Customer and bill-to party identifiers and names.
• START_DATE_ACTIVE, END_DATE_ACTIVE, CLOSE_DATE, PREAWARD_DATE — Award lifecycle dates.
• TYPE, AWARD_PURPOSE_CODE, LP_12.MEANING — Award type and purpose, with the decoded purpose meaning supplied by LP_12.
• STATUS, LP_2.MEANING — Award status code and decoded status meaning.
• ALLOWABLE_SCHEDULE_ID, ALLOW_SCH_NAME, IDC_SCHEDULE_ID, IND_RATE_SCH_NAME — Allowability and indirect cost schedule references.
• BILLING_FREQUENCY, BILLING_CYCLE_ID, BILLING_OFFSET, LP_4.MEANING, Billing_term, RAT.NAME — Billing frequency, offset meaning, term, and payment terms name from RA_TERMS.
• LABOR_INVOICE_FORMAT_ID, NON_LABOR_INVOICE_FORMAT_ID and their NAME columns — Invoice format references and descriptions.
• FUND_CONTROL_LEVEL_AWARD/TASK/RES_GRP/RES with LP_8 through LP_11 — Fund control level codes and meanings at award, task, resource group, and resource levels.
• AMOUNT_TYPE, LP_6.MEANING, BOUNDARY_CODE, LP_7.MEANING — Amount type and boundary classifications with decoded meanings.
• AWARD_ORGANIZATION_ID, OL.NAME — Award organization and operating unit name.
• TOTAL_ACCRUED_AMOUNT, TOTAL_BILLED_AMOUNT — Funded amounts drawn from PA_SUMMARY_PROJECT_FUNDINGS.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE25 — Descriptive flexfield segments.

Common Use Cases and Queries

The view is typically used for award listings, funding analysis, billing configuration reports, and integration extracts. A basic listing of active awards with decoded purpose and status is shown below:

• Award master listing: SELECT award_number, award_short_name, customer_name, start_date_active, end_date_active, status_meaning FROM apps.gms_awards_v — using LP_2.MEANING aliased as status_meaning.
• Purpose analysis (lp_12): SELECT award_number, award_purpose_code, lp_12_meaning FROM apps.gms_awards_v ORDER BY award_purpose_code, filtering or grouping by the LP_12 decoded purpose.
• Funded vs. billed comparison: SELECT award_number, total_accrued_amount, total_billed_amount, (total_accrued_amount - total_billed_amount) remaining FROM apps.gms_awards_v.
• Billing configuration review: SELECT award_number, billing_frequency, bill_to_customer_id, customer_name, billing_term FROM apps.gms_awards_v WHERE billing_frequency IS NOT NULL.
• Operating unit reporting: SELECT award_organization_id, operating_unit_name, COUNT(*) FROM apps.gms_awards_v GROUP BY award_organization_id, operating_unit_name.

Because the view incorporates GMS_SECURITY and MO_GLOBAL, results are automatically filtered by the operating unit and security profile of the querying user, making it suitable for multi-org deployments without additional WHERE clause restrictions.