Results for “initiator_apps_name”

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

Overview

PSP_EFFORT_REPORT_TEMPLATES is a Labor Distribution (PSP) table within the Oracle E-Business Suite 12.1.1 and 12.2.2 data model. It stores the criteria and template definitions used to generate effort reports, which are the instruments by which sponsored-project institutions certify that salaries charged to grants reflect actual effort. Each row represents a reusable template that governs which population, expenditures, awards, projects, and organizations an effort reporting cycle will cover, together with the scheduling attributes that determine when the report is produced.

The table is owned by the PSP schema and is documented with 47 columns. Its primary key is PSP_EFFORT_REPORT_TEMPLATES_PK, defined on TEMPLATE_ID, and a unique index PSP_EFFORT_REPORT_TEMPLATES_U1 also exists on TEMPLATE_ID. From a dimensional-modeling perspective, the foreign-key structure suggests a satellite-leaning classification: the table carries descriptive template attributes and effective-dating columns while being anchored, through its relationships, to core business entities such as people groups, projects, awards, and organizations. This classification is a heuristic modeling suggestion rather than a physical constraint in the EBS schema.

Key Information Stored

The surrogate primary key is TEMPLATE_ID, an internal system-generated identifier with no business meaning; the unique index on the same column confirms it is the sole enforced uniqueness constraint. Business identity is expressed through TEMPLATE_NAME together with the qualifying attributes rather than through a natural key column.

• TEMPLATE_ID — surrogate primary key; referenced by all dependent effort-reporting tables.
• TEMPLATE_NAME — user-facing name of the effort report template.
• EFFORT_REPORT_PERIOD_NAME — the reporting period the template applies to; foreign key to PSP_EFFORT_REPORT_PERIODS.
• BEGIN_DATE / END_DATE — the date range over which the template selects effort transactions.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — date-tracked validity of the template definition.
• PEOPLE_GROUP_ID — restricts the employee population; foreign key to PAY_PEOPLE_GROUPS.
• PERSON_ID / SUPERVISOR_ID / REPORT_INITIATOR_ID — personnel scoping and workflow routing targets.
• PROJECT_TYPE_CLASS_CODE / PROJECT_TYPE / AWARD_TYPE / FUNDING_SOURCE_ID — award and project inclusion criteria; FUNDING_SOURCE_ID references OKE_K_FUNDING_SOURCES.
• TASK_ID — task-level restriction; foreign key to PA_TASKS.
• ELEMENT_TYPE_ID — expenditure type filter; foreign key to PA_EXPENDITURE_TYPES.
• GL_CODE_COMBINATION_ID — accounting flexfield filter; foreign key to GL_CODE_COMBINATIONS.
• ENABLE_WORKFLOW_FLAG / USER_TEMPLATE_FLAG / REPORT_TYPE — control flags governing approval routing and report variant.
• BUSINESS_GROUP_ID / SET_OF_BOOKS_ID — organizational and ledger context.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS descriptive flexfield columns.
• LAST_UPDATE_DATE / CREATED_BY / CREATION_DATE / LAST_UPDATED_BY / LAST_UPDATE_LOGIN — standard EBS audit columns.

Common Use Cases and Queries

Administrators and reporting specialists query this table to audit active templates, identify the criteria behind a generated report, and reconcile template coverage against organizational funding structures. Because PSP_EFFORT_REPORTS stores TEMPLATE_ID, generating a report can be traced back to its governing template definition.

SELECT t.template_id, t.template_name, t.effort_report_period_name,
       t.begin_date, t.end_date, t.report_type
FROM   psp_effort_report_templates t
WHERE  TRUNC(SYSDATE) BETWEEN t.effective_start_date AND NVL(t.effective_end_date, TRUNC(SYSDATE))
ORDER  BY t.template_name;

A second pattern joins generated reports to their source templates to review volume by period:

SELECT t.template_name, t.effort_report_period_name, COUNT(r.template_id) report_count
FROM   psp_effort_report_templates t,
       psp_effort_reports r
WHERE  r.template_id = t.template_id
GROUP  BY t.template_name, t.effort_report_period_name;

Error diagnosis is another frequent scenario: PSP_EFFORT_ERRORS carries TEMPLATE_ID, allowing failed effort reports to be traced to the template whose criteria were in force. Templates scoped by award, project, or organization are commonly extracted through the child tables PSP_TEMPLATE_AWARDS, PSP_TEMPLATE_PROJECTS, and PSP_TEMPLATE_ORGANIZATIONS for compliance reporting.

Related Objects

The following objects are the most significant dependencies derived from the documented foreign-key relationships:

• PSP_EFFORT_REPORTS (TEMPLATE_ID) — the generated effort reports produced from a template.
• PSP_EFFORT_ERRORS (TEMPLATE_ID) — errors raised during effort report processing.
• PSP_TEMPLATE_AWARDS (TEMPLATE_ID) — awards included in the template scope.
• PSP_TEMPLATE_PROJECTS (TEMPLATE_ID) — projects included in the template scope.
• PSP_TEMPLATE_ORGANIZATIONS (TEMPLATE_ID) — organizations included in the template scope.
• PSP_EFFORT_REPORT_PERIODS (EFFORT_REPORT_PERIOD_NAME) — the period definition referenced by the template.
• PAY_PEOPLE_GROUPS (PEOPLE_GROUP_ID) — the people group defining the covered population.
• PA_TASKS (TASK_ID) and PA_EXPENDITURE_TYPES (ELEMENT_TYPE_ID) — project task and expenditure type filters.
• GL_CODE_COMBINATIONS (GL_CODE_COMBINATION_ID) and GL_SETS_OF_BOOKS_11I (SET_OF_BOOKS_ID) — accounting and ledger context.
• HR_ALL_ORGANIZATION_UNITS (BUSINESS_GROUP_ID) and OKE_K_FUNDING_SOURCES (FUNDING_SOURCE_ID) — business group and funding source references.