Results for “original_line_flag”

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

Overview

PSP_ADJUSTMENT_LINES_HISTORY is a table in the PSP (Labor Distribution) product family within Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to store adjusted labor distribution lines that have been successfully transferred. Where the operational tables hold in-flight or pending adjustment activity, this table serves as the post-transfer record, capturing the state of each adjustment line once it has passed the transfer process. It is therefore the authoritative source for auditing and reporting on completed adjustment transfers rather than on current processing activity.

Based on the foreign key structure mined from the ETRM metadata, a heuristic Data Vault classification for this table is a link object. The table sits at the intersection of several business entities — payroll controls, effort reports, summary lines, projects and tasks, and general ledger accounts — and is keyed by a surrogate ADJUSTMENT_LINE_ID rather than by a natural composite key. This confirms its role as a transaction-level associative record joining distribution, effort reporting, and accounting context.

Key Information Stored

PSP_ADJUSTMENT_LINES_HISTORY contains 58 documented columns. The most significant are:

• ADJUSTMENT_LINE_ID — the primary key (PSP_ADJUSTMENT_LINES_HIST_PK) and also the sole documented unique-index business-key candidate (PSP_ADJUSTMENT_LINES_HISTORY_U). This is the surrogate identifier for the transferred adjustment line.
• PAYROLL_CONTROL_ID — links the line back to the originating payroll control record.
• PERSON_ID and ASSIGNMENT_ID — identify the employee and assignment whose labor is being redistributed.
• DISTRIBUTION_DATE and EFFECTIVE_DATE — the accounting and effective dating of the adjustment.
• DISTRIBUTION_AMOUNT and DR_CR_FLAG — the monetary value and debit/credit indicator for the line.
• GL_CODE_COMBINATION_ID and SET_OF_BOOKS_ID — the accounting flexfield and ledger targeted by the transferred distribution.
• PROJECT_ID, TASK_ID, AWARD_ID, EXPENDITURE_TYPE, EXPENDITURE_ORGANIZATION_ID — the project, task, award, expenditure type, and organization context that defines where the cost lands.
• EFFORT_REPORT_ID, VERSION_NUM, and SUMMARY_LINE_ID — links to the effort reporting and summary line structures that justified the adjustment.
• SOURCE_TYPE, SOURCE_CODE, TIME_PERIOD_ID, ORIG_SOURCE_TYPE, ORIG_LINE_ID — provenance fields identifying the source of the adjustment and its original line.
• REVERSAL_ENTRY_FLAG and ORIGINAL_LINE_FLAG — indicate whether the line is a reversal and whether it is the original entry.
• ADJUSTMENT_BATCH_NAME — foreign key to the adjustment control table, grouping lines by batch.

The ADJUSTMENT_LINE_ID is the surrogate primary key; no multi-column natural business key is documented beyond that single unique index.

Common Use Cases and Queries

Typical reporting and reconciliation scenarios include verifying that a batch of adjustments transferred completely, reconciling transferred amounts against the general ledger, and tracing an effort report-driven adjustment back to its original payroll line. A representative query joining the history table to payroll controls and the chart of accounts follows:

• SELECT h.ADJUSTMENT_LINE_ID, h.PERSON_ID, h.DISTRIBUTION_AMOUNT, h.DR_CR_FLAG, h.GL_CODE_COMBINATION_ID FROM PSP_ADJUSTMENT_LINES_HISTORY h WHERE h.ADJUSTMENT_BATCH_NAME = :batch AND h.REVERSAL_ENTRY_FLAG = 'N';
• Reconciliation by project: join PROJECT_ID, TASK_ID, and EXPENDITURE_TYPE to PA_PROJECTS_ALL, PA_TASKS, and PA_EXPENDITURE_TYPES to confirm transferred cost by award.
• Audit of effort-report-driven adjustments: join EFFORT_REPORT_ID and SUMMARY_LINE_ID to PSP_EFFORT_REPORTS and PSP_SUMMARY_LINES.
• Tracing source provenance: join SOURCE_TYPE and SOURCE_CODE to PSP_PAYROLL_SOURCES and ORIG_LINE_ID back to the originating summary line.

Related Objects

The most significant related objects, based on the documented foreign keys, are:

• PSP_PAYROLL_CONTROLS — joined via PAYROLL_CONTROL_ID; the parent payroll control for each transferred line.
• PSP_SUMMARY_LINES — joined via SUMMARY_LINE_ID; the summary distribution record.
• PSP_EFFORT_REPORTS — joined via EFFORT_REPORT_ID and VERSION_NUM; the effort certification driving the adjustment.
• PSP_ADJUSTMENT_CONTROL_TABLE — joined via ADJUSTMENT_BATCH_NAME; the batch definition governing the transfer.
• PA_PROJECTS_ALL and PA_TASKS — joined via PROJECT_ID and TASK_ID; project and task context for the cost.
• PA_EXPENDITURE_TYPES — joined via EXPENDITURE_TYPE; the expenditure classification of the line.
• GL_CODE_COMBINATIONS, GL_SETS_OF_BOOKS — joined via GL_CODE_COMBINATION_ID and SET_OF_BOOKS_ID; the accounting destination.
• HR_ALL_ORGANIZATION_UNITS — joined via EXPENDITURE_ORGANIZATION_ID and BUSINESS_GROUP_ID; the organization context.
• PSP_PAYROLL_SOURCES, PER_TIME_PERIODS, IGF_AW_AWARD_ALL — joined via SOURCE_TYPE/SOURCE_CODE, TIME_PERIOD_ID, and AWARD_ID; source, period, and award context.