Results for “segment_number”

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

Overview

PSP_AUTO_SEGMENTS is a configuration table owned by the PSP schema within the Oracle E-Business Suite Labor Distribution module. It stores the Natural Account segment value that Labor Distribution uses to auto-populate accounting flexfield information when charging labor costs. Because Labor Distribution processes large volumes of expenditure transactions that must be transferred to Oracle General Ledger, the module requires a reliable default source for the account segment. PSP_AUTO_SEGMENTS fulfills that role by defining, for each combination of business group and set of books, the specific Natural Account segment that should be applied automatically.

From a Data Vault modeling perspective, the table exhibits characteristics of a link table. Its primary key is composed entirely of foreign key columns — SEGMENT_NUMBER, BUSINESS_GROUP_ID, and SET_OF_BOOKS_ID — which connect two independent business entities: the operating unit or business group context and the accounting set of books. This structure is diagnostic of a link construct, since it associates two hubs rather than storing descriptive attributes that belong to a single entity.

Key Information Stored

The documented physical schema contains eight columns. The essential business content resides in the following attributes:

• SET_OF_BOOKS_ID — Identifies the Oracle General Ledger set of books (or ledger in later releases) for which the automatic segment is defined. This column participates in the composite primary key and carries a foreign key to GL_SETS_OF_BOOKS.
• BUSINESS_GROUP_ID — Identifies the HR business group that owns the labor distribution configuration. It is part of the composite primary key and references HR_ALL_ORGANIZATION_UNITS.
• SEGMENT_NUMBER — Holds the Natural Account segment value used for auto-population. It completes the composite primary key.
• CREATED_BY, CREATION_DATE — Standard Oracle EBS audit columns capturing who created the configuration row and when.
• LAST_UPDATED_BY, LAST_UPDATE_DATE — Audit columns recording the most recent change and the user responsible.
• LAST_UPDATE_LOGIN — Identifies the login session associated with the last update.

The surrogate-style identity here is provided by the composite primary key constraint PSP_AUTO_SEGMENTS_PK, spanning all three business columns. No separate numeric surrogate key is documented, so the natural composite business key serves as the unique identifier.

Common Use Cases and Queries

Administrators and consultants query this table to verify or troubleshoot the automatic account segment assignment used during Labor Distribution processing. A typical verification query joins the table to GL_SETS_OF_BOOKS to confirm configuration across ledgers:

SELECT ps.set_of_books_id, ps.business_group_id, ps.segment_number FROM psp_auto_segments ps WHERE ps.set_of_books_id = :book_id;

Reporting scenarios include auditing which natural account is applied per business group, ensuring consistency across multiple operating units, and diagnosing transfer-to-GL failures caused by missing or incorrect segment configuration. Because the table is small and purely configurational, queries are typically supported by direct primary key lookups rather than range scans.

Related Objects

The following objects are referenced directly or are closely associated with PSP_AUTO_SEGMENTS:

• GL_SETS_OF_BOOKS — joined on PSP_AUTO_SEGMENTS.SET_OF_BOOKS_ID; defines the accounting book context.
• HR_ALL_ORGANIZATION_UNITS — joined on PSP_AUTO_SEGMENTS.BUSINESS_GROUP_ID; provides the business group definition.
• PSP_AUTO_SEGMENTS_PK — the primary key constraint enforcing uniqueness across the three business columns.
• PSP labor distribution transaction tables — consume the SEGMENT_NUMBER value during account derivation for interfacing to General Ledger.
• GL_CODE_COMBINATIONS — validates that the auto-populated Natural Account segment forms a valid accounting flexfield combination.

Together these relationships confirm the table's role as a focused configuration link between HR organizational structure and General Ledger accounting structure.