Results for “structure_sharing_code”

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

Overview

PA_PROJECTS_AMG_V is an internal Oracle E-Business Suite view owned by the APPS schema in the Projects (PA) module. It is classified as a standard database VIEW with VALID status and is documented in ETRM for both release 12.1.1 and 12.2.2. The view exposes a wide projection of project master data drawn from the PA_PROJECTS synonym, presenting columns that describe project identity, structuring, billing, rate schedules, funding, scheduling, descriptive flexfields, and workflow status. Because it surfaces nearly the full column set of the underlying project entity rather than a curated reporting subset, it functions primarily as a denormalized access point used internally by Oracle Projects forms, concurrent programs, and integration logic rather than as a formally published reporting interface.

The "AMG" suffix and the object's Description field of "Internal" indicate that Oracle does not document this view for direct customer use, and it should be treated as a support object subject to change between point releases. Nevertheless, because it mirrors the PA_PROJECTS structure, it is frequently discovered and reused in custom reporting and reconciliation queries.

Underlying Base Objects

Per documented ETRM metadata for 12.2.2, PA_PROJECTS_AMG_V is defined over the following referenced base objects: PA_PROJECTS (SYNONYM), PA_PROJECT_STRUCTURE_UTILS (PACKAGE), PA_PROJ_ELEMENTS_UTILS (PACKAGE), and PA_WORKPLAN_ATTR_UTILS (PACKAGE). The PA_PROJECTS synonym resolves to the core APPS.PA_PROJECTS table, which supplies the bulk of the projected columns. The three referenced PL/SQL packages provide procedural logic — project structure handling, project element management, and workplan attribute derivation — that the view's defining SELECT invokes to populate or transform selected columns.

Consequently, the view is not a simple single-table projection; it embeds packaged function calls, which means query cost and behavior depend on the state of those packages and their underlying data.

Key Columns

• PROJECT_ID / NAME / LONG_NAME — Primary project identifier, short name, and descriptive long name.
• SEGMENT1–SEGMENT10 — The project's accounting key flexfield segments, used to build the project number and accounting combinations.
• PROJECT_TYPE, PROJECT_STATUS_CODE, PROJECT_CURRENCY_CODE — Classification, lifecycle status, and currency context.
• START_DATE, COMPLETION_DATE, CLOSED_DATE, ACTUAL_START_DATE, ACTUAL_FINISH_DATE, SCHEDULED_START_DATE, SCHEDULED_FINISH_DATE — Planned, actual, and scheduled project dates, including early/late start and finish variants used in scheduling.
• Billing columns — DISTRIBUTION_RULE, LABOR/NON_LABOR/RETENTION_INVOICE_FORMAT_ID, RETENTION_PERCENTAGE, BILLING_OFFSET, BILLING_CYCLE, BILLING_CYCLE_ID, INVOICE_COMMENT, UNBILLED_RECEIVABLE_DR, UNEARNED_REVENUE_CR.
• Rate schedule columns — COST_IND_RATE_SCH_ID, REV_IND_RATE_SCH_ID, INV_IND_RATE_SCH_ID and their fixed-date and override counterparts, plus LABOR/NON_LABOR_STD_BILL_RATE_SCHDL and associated discount and organization fields.
• Template and workflow columns — TEMPLATE_FLAG, TEMPLATE_START_DATE_ACTIVE, TEMPLATE_END_DATE_ACTIVE, WF_STATUS_CODE, ADW_NOTIFY_FLAG.
• Flags and attributes — PUBLIC_SECTOR_FLAG, SUMMARY_FLAG, ENABLED_FLAG, ALLOW_CROSS_CHARGE_FLAG, PROJECT_LEVEL_FUNDING_FLAG, LIMIT_TO_TXN_CONTROLS_FLAG, ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15.
• WHO and audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, plus ORG_ID and REQUEST_ID/PROGRAM_ID context.

Notably, the searched term baseline_as_of_date is not exposed by this view's documented column list; baseline "as of" reporting semantics are associated with Project Management baseline tables rather than this PA project projection.

Common Use Cases and Queries

Typical use cases include validating project setup during data conversion, reconciling billing and rate schedule assignments, and building custom project status reports. Because the object is internal, queries should be constrained and treated as read-only.

• Retrieve active projects for a given organization and status.
• Audit billing configuration across a project set.
• Report scheduled versus actual dates for portfolio tracking.

Sample SQL:

SELECT p.project_id,
       p.name,
       p.long_name,
       p.project_status_code,
       p.start_date,
       p.completion_date,
       p.billing_cycle
FROM   apps.pa_projects_amg_v p
WHERE  p.org_id = :org_id
AND    p.project_status_code = 'APPROVED'
ORDER BY p.name;

Because the definition invokes PL/SQL utility packages, users should expect additional execution overhead relative to a plain table query and should avoid unbounded full scans.