Results for “reason_code”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
PSP_SUB_LINE_REASONS is a table in the PSP (Labor Distribution) product schema within Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to store the reasons associated with the creation of payroll sublines from payroll lines. In the labor distribution model, payroll processing frequently produces multiple downstream sublines from a single payroll line — for cost allocation, encumbrance adjustments, distribution corrections, or retroactive processing. This table captures the explainable "why" behind each such subdivision, giving administrators and auditors a queryable audit trail of subline generation events. The table has eight documented columns and is classified as VALID in the ETRM repository.
From a Data Vault modeling perspective, the mined heuristic classifies PSP_SUB_LINE_REASONS as satellite-leaning. This suggests it is best treated as a descriptive satellite: its rows record attributes and context about a parent business entity (the payroll subline) rather than serving as an independent hub or a pure relationship link. Practitioners designing a warehouse layer over PSP should consider anchoring this table to PSP_PAYROLL_SUB_LINES as the driving parent and capturing REASON_CODE plus the accompanying audit columns as satellite payload.
Key Information Stored
The documented physical schema contains eight columns. The most significant are:
- PAYROLL_SUB_LINE_ID — The identifier of the payroll subline for which the reason is recorded. This column participates in the primary key and is the sole documented foreign key, referencing PSP_PAYROLL_SUB_LINES.
- REASON_CODE — The coded reason explaining why the subline was created from its originating payroll line. It forms the second component of the composite primary key and is the principal business-meaning attribute.
- PARENT_LINE_ID — Identifies the parent payroll line from which the subline lineage originates, supporting hierarchical tracing of line-to-subline derivation.
- LAST_UPDATE_DATE — The date the row was most recently modified; a standard EBS audit column used for incremental extraction.
- LAST_UPDATED_BY — The application user who performed the most recent update.
- LAST_UPDATE_LOGIN — The login session identifier associated with the last update.
- CREATED_BY — The user who originally created the reason record.
- CREATION_DATE — The timestamp of original record creation.
Two key structures are documented. The primary key, PSP_SUB_LINE_REASONS_PK, is the composite (PAYROLL_SUB_LINE_ID, REASON_CODE), combining the foreign key to the parent subline with the reason code. The unique index PSP_SUB_LINE_REASONS_U1 covers the same column pair and therefore represents the documented business-key candidate: no two identical reason codes may exist for the same payroll subline. There is no separate single-column surrogate key; identity is derived from the foreign key plus the reason code, which is consistent with the satellite-leaning classification.
Common Use Cases and Queries
Typical reporting scenarios include auditing why payroll costs were redistributed, reconciling subline volumes by reason, and tracing a subline back to its parent payroll line. A representative query joining the satellite to its parent is:
SELECT r.PAYROLL_SUB_LINE_ID, r.REASON_CODE, r.PARENT_LINE_ID, r.CREATION_DATE FROM PSP.PSP_SUB_LINE_REASONS r WHERE r.PAYROLL_SUB_LINE_ID = :sub_line_id;— retrieves all reasons recorded for a given subline.SELECT REASON_CODE, COUNT(*) FROM PSP.PSP_SUB_LINE_REASONS GROUP BY REASON_CODE ORDER BY 2 DESC;— profiles subline creation reasons across the enterprise.SELECT r.* FROM PSP.PSP_SUB_LINE_REASONS r, PSP.PSP_PAYROLL_SUB_LINES s WHERE r.PAYROLL_SUB_LINE_ID = s.PAYROLL_SUB_LINE_ID;— joins the reason rows to the parent subline for combined cost and reason reporting.- Incremental extracts should filter on LAST_UPDATE_DATE using a high-water mark, since the table carries the standard EBS WHO audit columns.
Related Objects
- PSP_PAYROLL_SUB_LINES — The parent table referenced by the documented foreign key PSP_SUB_LINE_REASONS.PAYROLL_SUB_LINE_ID; the primary join path.
- PSP_SUB_LINE_REASONS_PK / PSP_SUB_LINE_REASONS_U1 — The primary key constraint and unique index enforcing (PAYROLL_SUB_LINE_ID, REASON_CODE).
- Payroll line and distribution tables in the PSP/PAY schemas — PARENT_LINE_ID relates the reason record to the originating payroll line, enabling line-to-subline traceability.
- Labor distribution cost allocation and encumbrance processes — These processes populate the table when payroll lines are subdivided, making it a dependent audit object.
Because the documented metadata lists only one foreign key, PSP_PAYROLL_SUB_LINES is the definitive parent dependency; all other relationships should be validated against the customer's specific PSP implementation before being relied upon for reporting.
-
Lookup Type: REASON_CODE 12.1.1
Reason Code
-
Lookup Type: REASON_CODE 12.2.2
Reason Code
-
Stores reasons for creating payroll sublines from payroll lines
-
Stores the associated reasons for change types
-
Translations table table holding OPM reason code descriptions in multiple languages
-
Stores exception reasons.
-
Translations table table holding OPM reason code descriptions in multiple languages
-
- Retrofitted
APPS.ENGBV_ENG_CHANGE_REASONS·↳ ENG_CHANGE_REASONS·↳ HR_ALL_ORGANIZATION_UNITS·↳ MTL_PARAMETERS·Explore ENG module →
-
This table stores comment reason codes for scenario revisions.
-
This table stores comment reason codes for scenario revisions.
-
Contains details of reason codes
-
- Retrofitted
APPS.ENGBV_ENG_CHANGE_REASONS·↳ ENG_CHANGE_REASONS·↳ HR_ALL_ORGANIZATION_UNITS·↳ MTL_PARAMETERS·Explore ENG module →
-
Person Dependent Relationship Active Information
-
View: PAY_KR_SEP_HI_ADJ_V 12.2.2
APPS.PAY_KR_SEP_HI_ADJ_V·↳ HR_GENERAL·↳ HR_ORGANIZATION_INFORMATION·↳ HR_PERSON_NAME·Explore PAY module →
-
Stores information about how the stock list item was created.
-
This table holds the Exception portion of the ShowShipment message
-
This table stores information about which action to take based on the information that is included in trading partner's confirmation message.
-
Translation table for Reason.
-
Contains history of all lot conversions holding old and new values and date of change
-
Manual Entries Table
-
Contains history of all lot conversions holding old and new values and date of change
-
This table is used to store the opportunity routing history
-
The Reason Code table is used to store Reason Code definitions which provide information on the increase or decrease in inventory. Reason codes are used to flag transactions and attach reasons to them.
-
Table: MTH_EVENTS 12.2.2
This table stores information on Event Action setup for handling Events. It holds information like Event Type, Event action and Event notification setup.
-
View: JTF_IH_REASONS_VL 12.2.2
Translated view for JTF_IH_REASONS_B and JTF_IH_REASONS_TL.
APPS.JTF_IH_REASONS_VL·↳ JTF_IH_REASONS_B·↳ JTF_IH_REASONS_TL·Explore JTF module →
-
Stores reasons for creating payroll sublines from payroll lines
-
Reason Code Security Table
-
Reason Code Security Table
-
Extension table of HZ_CONTACT_PREFERENCES. This would be useful to store office hours for a staff, Faculty
APPS.IGSBV_PERSON_OFFICE_HOURS·↳ HZ_CONTACT_PREFERENCES·↳ IGS_PE_OFFICE_HRS·Explore IGS module →
-
Contains details for spreadsheet journal headers
-
Contains details for spreadsheet journal headers
-
APPS.OKL_CS_IH_ACTIVITIES_UV·↳ HR_GENERAL·↳ HR_PERSON_NAME·↳ HR_SECURITY·Explore OKL module →
-
Internal View for Escalation Reference Documents
APPS.JTF_EC_ESC_CONTACTS_REF_DOCS·↳ FND_GLOBAL·↳ JTF_ESCALATION_TASK_V·↳ JTF_TASK_CONTACTS·Explore JTF module →
-
Interection Reason Level Table .
-
Sales Order Detail Allocations view
APPS.GML_GPOAO_DETAIL_ALLOCATIONS_V·↳ IC_LOCT_MST·↳ IC_LOTS_MST·↳ IC_LOTS_STS·Explore GML module →
-
Error table for MTH_EQUIPMENT_REASON_SETUP
-
This table stores Reason code as well as the Expected Uptime for Equipments
-
Table: MTH_EVENT_SETUP 12.2.2
This table stores information on Event Action Setup for handling Events. It holds information like Equipment, Event Type and Reason.
-
Stores information about how the stock list item was created.
-
Cost Adjustments Reason Codes - Reason Codes will allow the user to define specific codes to record the reason for making the adjustment. These codes will be user defined.
-
- Retrofitted
APPS.ENGFV_ENG_CHANGE_REASONS·↳ ENG_CHANGE_REASONS·↳ HR_ALL_ORGANIZATION_UNITS·↳ MTL_PARAMETERS·Explore ENG module →
-
Contract status change history and history for any actions during contract life cycle
-
Based on IGI_BUD_JOURNAL_LINES
APPS.IGI_BUD_JOURNAL_LINES_V·↳ IGI_BUD_JOURNAL_LINES·Explore IGI module →
-
View: GMI_LOTS_EVENT_V 12.1.1
This view is used to populate the Lot Events tab of the Lot Genealogy Inquiry.
APPS.GMI_LOTS_EVENT_V·↳ IC_ITEM_MST·↳ IC_LOTS_MST·↳ IC_TRAN_VW1·Explore GMI module →