Search Results modify_modify

Overview

APPS.PA_SST_MODIFY_TIMECARD_V is a self-service timecard inquiry view in Oracle EBS Projects (PA). It presents a filtered, consolidated list of timecard-related expenditure records — those whose originating user reference is not null and whose status is either REJECTED or WORKING — and, critically, it generates the hyperlink action strings that allow a self-service user to modify, copy, or delete the corresponding timecard from an inquiry screen. In this sense the view functions less as a pure reporting source and more as a "presentation control" object: each row carries pre-built javascript:void window.open(...) expressions that invoke the PL/SQL agent routine PA_SELF_SERVICE_INQUIRIES_PVT.OpenWindowFromInquiry, passing an action code such as MODIFY_MODIFY or MODIFY_COPY, or the CheckDelete procedure for removal.

The user search term "modify_modify" corresponds directly to the p_action_code=MODIFY_MODIFY parameter embedded in the view's generated link, indicating the modify operation invoked from the Oracle Time and Labor / Projects self-service inquiry flow. Because the view hard-codes this action code, it services the modify-maintain path of the timecard lifecycle.

Underlying Base Objects

The view is owned by APPS and is defined over four documented base objects:

• PA_EXPENDITURES (referenced via synonym) — the driving table, aliased exp, holding timecard expenditure rows filterable by expenditure_class_code = 'PT' (timecard).
• PA_EI_DENORM (synonym) — the denormalized expenditure item table, aliased den, joined with an outer join on expenditure_id. Supplies the numeric quantity columns aggregated in the SELECT.
• PER_ALL_PEOPLE_F (synonym) — the HR people table, aliased per, providing the full name of the person who incurred the expenditure, joined on incurred_by_person_id and date-effectivity.
• PA_LOOKUPS (view) — aliased lookup, joined on lookup type 'EXPENDITURE STATUS' and code to translate the status code into a meaningful description.

The joins establish person identity, expenditure item quantities, and status meaning, while the WHERE clause restricts output to non-null originating user references and REJECTED/WORKING statuses.

Key Columns

• expenditure_id — unique key used in all generated action links.
• orig_user_exp_txn_reference — the user-supplied reference for the timecard, used to identify the source transaction.
• expenditure_group — grouping attribute for the timecard.
• meaning — decoded expenditure status (from PA_LOOKUPS).
• expenditure_ending_date — the date range of the timecard.
• full_name — person who incurred the timecard.
• incurred_by_person_id / incurred_by_organization_id — incurrence ownership identifiers.
• initial_submission_date, description, entered_by_person_id, overriding_approver_person_id — audit and routing attributes.
• SUM(NVL(quantity_1..quantity_7,0)) — aggregated hours/quantities per expenditure.
• JavaScript action columns — three derived expressions producing modify, copy, and delete link strings.

Common Use Cases and Queries

Typical use is in self-service timecard inquiry pages where the modify action must be offered for rejected or working timecards. A representative query is:

SELECT expenditure_id, orig_user_exp_txn_reference, meaning, full_name, expenditure_ending_date FROM apps.pa_sst_modify_timecard_v WHERE incurred_by_person_id = :person_id;

Administrators may also interrogate the view to audit rejected timecards or to verify that the generated MODIFY_MODIFY hyperlink targets are correctly formed before deploying a personalized inquiry page.