Results for “inc_exc_flag”

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

Overview

PSP_ENC_PAYROLLS_V is a reporting view owned by the APPS schema within the Oracle E-Business Suite environment, associated with the PSP (Labor Distribution) product module. Its documented purpose is to support the setup of payrolls for labor encumbrance, providing a denormalized, read-only presentation of the payroll-to-encumbrance configuration records that govern how payroll costing results are treated when generating labor encumbrance entries. The view exists to simplify both end-user reporting and programmatic integration by joining the encumbrance payroll configuration table to the payroll definition table and resolving the internal payroll identifier into a user-recognizable payroll name. It is marked VALID and is present in both EBS 12.1.1 and 12.2.2. Because it is a view rather than a table, no direct DML should be performed against it; all maintenance is performed on the underlying base table, PSP_ENC_PAYROLLS.

Underlying Base Objects

The documented view text defines PSP_ENC_PAYROLLS_V over two base objects: the synonym PSP_ENC_PAYROLLS and the table PAY_PAYROLLS_F, with a secondary dependency on the PSP_GENERAL package in the documented metadata. The join links the encumbrance payroll record to the payroll definition on three keys: PAYROLL_ID, BUSINESS_GROUP_ID, and a set-of-books condition in which the encumbrance record's SET_OF_BOOKS_ID must equal the payroll's GL_SET_OF_BOOKS_ID. The predicate GL_SET_OF_BOOKS_ID IS NOT NULL restricts output to payrolls that are actually associated with a general ledger set of books, excluding payrolls that are not yet configured for GL costing. The DISTINCT keyword eliminates duplicate rows that may arise where a payroll is defined across multiple effective-dated or overlapping set-of-books contexts. PSP_ENC_PAYROLLS stores the administrative configuration that determines which payrolls participate in labor encumbrance processing, while PAY_PAYROLLS_F supplies the descriptive payroll name.

Key Columns

• ENC_PAYROLL_ID — Primary identifier of the encumbrance payroll configuration row in PSP_ENC_PAYROLLS; used as the unique key for the setup record.
• BUSINESS_GROUP_ID — The business group (HR security organization) that owns both the payroll and the encumbrance configuration, enforcing multi-tenant separation.
• SET_OF_BOOKS_ID — The general ledger set of books to which the encumbrance payroll configuration applies; must match the payroll's GL set of books.
• PAYROLL_ID — Identifier of the payroll defined in PAY_PAYROLLS_F, linking the configuration to a specific payroll.
• INC_EXC_FLAG — The include/exclude flag that determines whether the associated payroll is included in or excluded from labor encumbrance processing. This is the column most frequently targeted by users searching for the inc_exc_flag term, since it drives the core behavioral decision of the setup.
• PAYROLL_NAME — The user-facing payroll name sourced from PAY_PAYROLLS_F, providing readable identification in reports and inquiries.

Common Use Cases and Queries

Typical usage centers on auditing which payrolls are configured for encumbrance and whether they are included or excluded. A standard inquiry lists all active encumbrance payroll setups for a business group with readable names:

• SELECT enc_payroll_id, business_group_id, set_of_books_id, payroll_id, inc_exc_flag, payroll_name FROM apps.psp_enc_payrolls_v WHERE business_group_id = :p_bg_id ORDER BY payroll_name;
• Filtering by the include/exclude flag to isolate included payrolls: ... WHERE inc_exc_flag = 'I'; (verify the lookup meaning in PSP_GENERAL before relying on a literal value).
• Reconciling setup coverage against PAY_PAYROLLS_F to detect payrolls that lack an encumbrance configuration row.
• Feeding downstream integration or reconciliation extracts that require the resolved payroll name alongside the configuration identifiers.

Because the view is read-only and filtered to payrolls with a valid GL set of books, it is well suited to validation queries and reporting extracts, while all inserts, updates, and deletions must be directed to PSP_ENC_PAYROLLS.