Search Results as_utility_pvt




Overview
Explore in AI Chat

Overview

OSM.AS_CONC_REQUEST_MESSAGES is a transactional table in the Oracle Sales and Marketing (OSM) schema of Oracle E-Business Suite, holding the log of messages produced by Oracle Sales and Marketing concurrent programs. Its FND Design Data reference is AS.AS_CONC_REQUEST_MESSAGES, and it is created in the APPS_TS_TX_DATA tablespace with a PCT Free of 10. Every row is anchored to a concurrent request through the standard REQUEST_ID column, which identifies the last concurrent program that inserted or updated the record.

The table carries particular significance for the AS_UTILITY_PVT package, which is the seeded OSM utility API that performs dynamic index and table maintenance. Columns such as INDEX_NAME, INDEX_OWNER, TABLE_NAME, TABLE_OWNER, INDEX_TEXT and INDEX_DATA exist exclusively to support that package, allowing it to record which database objects were touched, the DDL executed, and diagnostic output associated with the operation. Administrators searching for as_utility_pvt are typically tracing this diagnostic trail.

Under the heuristic Data Vault classification supplied in the metadata, this object is modeled as a standalone structure rather than a hub, link or satellite. That classification reflects the absence of foreign keys other than the security group reference, suggesting a self-contained logging entity rather than a core business transaction.

Key Information Stored

The surrogate primary key is CONC_REQUEST_MESSAGE_ID, defined by the unique constraint AS_CONC_REQUEST_MESSAGES_PK. No separate business-key unique index is documented, so the ordinal identifier is the only guaranteed unique key.

  • REQUEST_ID — the concurrent request identifier used to correlate messages back to FND_CONCURRENT_REQUESTS.
  • TYPE and ERROR_NUMBER — message classification and optional Oracle error code, used to distinguish informational output from exceptions.
  • TEXT — the short, 255-character message body surfaced in concurrent program output.
  • INDEX_NAME / INDEX_OWNER — the index targeted or inspected by AS_UTILITY_PVT.
  • TABLE_NAME / TABLE_OWNER — the table associated with that index.
  • INDEX_TEXT — the DDL or definition text for the index (4000 characters).
  • INDEX_DATA — a CLOB holding the larger index data payload generated by the utility.
  • CREATION_DATE / CREATED_BY — standard who columns recording when and by whom the row was written.
  • SECURITY_GROUP_ID — the subscriber identifier, foreign-keyed to FND_SECURITY_GROUPS, used for CRM Online Services partitioning.
  • OBJECT_VERSION_NUMBER — optimistic locking column maintained by the framework.

Common Use Cases and Queries

The primary diagnostic use case is reviewing the output of a Sales and Marketing concurrent program that invokes AS_UTILITY_PVT. A typical query filters by request to reconstruct the exact index and table maintenance performed:

  • Request log review: SELECT TYPE, ERROR_NUMBER, TEXT, INDEX_NAME, TABLE_NAME FROM OSM.AS_CONC_REQUEST_MESSAGES WHERE REQUEST_ID = :request_id ORDER BY CONC_REQUEST_MESSAGE_ID;
  • Error triage: filter on TYPE = 'ERROR' or non-null ERROR_NUMBER to isolate failures from informational messages.
  • Index audit: query by TABLE_NAME and INDEX_NAME to determine when a given index was last processed and what INDEX_TEXT was generated.
  • Multi-tenant reporting: group results by SECURITY_GROUP_ID to isolate messages belonging to a specific subscriber.

Both nonunique indexes, AS_CONC_REQUEST_MESSAGES_N1 and AS_CONC_REQUEST_MESSAGES_N2, are built in APPS_TS_TX_IDX to support these access paths efficiently.

Related Objects

  • FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID, providing the subscriber definition for CRM Online Services rows.
  • AR_CONC_REQUEST_MESSAGES — references this table through CONC_REQUEST_MESSAGE_ID, indicating Receivables maintains a parallel message store keyed to this surrogate key.
  • AS_UTILITY_PVT — the OSM utility package that writes and consumes the index and table metadata columns.
  • FND_CONCURRENT_REQUESTS — source of the REQUEST_ID used for correlation (implicit relationship).
  • FND_CONCURRENT_PROGRAMS — identifies the concurrent program that produced the messages.