Results for “psb_service_packages”

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

Overview

PSB_SERVICE_PACKAGES is a table within the Public Sector Budgeting (PSB) module of Oracle E-Business Suite, documented in ETRM for releases 12.1.1 and 12.2.2. The ETRM metadata explicitly flags the PSB product as Obsolete, and the implementation notes record the table as "Not implemented in this database." Its declared purpose is to hold service package definitions — the grouping construct by which budgeting services are bundled and associated with a global budgeting worksheet.

In terms of a Data Vault modeling heuristic, the mined foreign-key structure classifies this table as hub-leaning. This is a modeling suggestion rather than a physical design statement: the table carries a single-column surrogate primary key and anchors multiple dependent tables, while also referencing a parent worksheet. It therefore behaves more like a hub than a pure satellite, though it holds descriptive attributes that would normally be split into satellites in a formal Data Vault build.

Key Information Stored

The table is documented with 23 columns. The most significant are:

• SERVICE_PACKAGE_ID — the surrogate primary key, enforced by the unique index PSB_SERVICE_PACKAGES_U1 and by the constraint PSB_SERVICE_PACKAGES_PK.
• GLOBAL_WORKSHEET_ID — foreign key to PSB_WORKSHEETS, tying each package to the global budgeting worksheet it belongs to.
• BASE_SERVICE_PACKAGE — reference to the base or source service package from which the current definition derives.
• NAME, SHORT_NAME, DESCRIPTION — the descriptive identity of the package, used in user-facing lists and lookups.
• PRIORITY — controls ordering or precedence of the package within its worksheet context.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — the standard EBS audit and "who column" set.
• ATTRIBUTE1 through ATTRIBUTE10 and CONTEXT — the standard EBS descriptive-flexfield placeholder columns.

A second unique index, PSB_SERVICE_PACKAGES_U2, is documented over the composite of GLOBAL_WORKSHEET_ID and SERVICE_PACKAGE_ID, making it a business-key candidate alongside the surrogate identifier.

Common Use Cases and Queries

Because the table is obsolete and absent from current schemas, its principal uses are historical reporting, data archiving, and analysis of legacy budgeting workloads.

• Listing active service packages for a worksheet: SELECT SERVICE_PACKAGE_ID, NAME, SHORT_NAME, PRIORITY FROM PSB_SERVICE_PACKAGES WHERE GLOBAL_WORKSHEET_ID = :worksheet_id ORDER BY PRIORITY;
• Counting packages per worksheet: SELECT GLOBAL_WORKSHEET_ID, COUNT(*) FROM PSB_SERVICE_PACKAGES GROUP BY GLOBAL_WORKSHEET_ID;
• Audit tracing of record creation and last modification: selecting CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE for compliance extracts.
• Resolving the composite business key via PSB_SERVICE_PACKAGES_U2 when reconciling legacy extracts against modern budgeting constructs.

Any query should first verify whether the table exists; the ETRM record states it is not implemented in the reference database.

Related Objects

The documented foreign-key topology identifies the following significant relationships:

• PSB_WORKSHEETS — parent table; joined on PSB_SERVICE_PACKAGES.GLOBAL_WORKSHEET_ID = PSB_WORKSHEETS.GLOBAL_WORKSHEET_ID.
• PSB_WS_ACCOUNT_LINES — child table; references this table through PSB_WS_ACCOUNT_LINES.SERVICE_PACKAGE_ID.
• PSB_WS_SUBMIT_SERVICE_PACKAGES — child/association table; references this table through PSB_WS_SUBMIT_SERVICE_PACKAGES.SERVICE_PACKAGE_ID, likely the submission or workflow link for service packages.

These three related tables, together with the two unique indexes PSB_SERVICE_PACKAGES_U1 and PSB_SERVICE_PACKAGES_U2, constitute the documented relational footprint of PSB_SERVICE_PACKAGES. No views, PL/SQL APIs, or concurrent programs are recorded in the supplied metadata.

Oracle Proprietary, Confidential Information — Legal Notices apply.