Results for “service_category_code”

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

Overview

The ZX_API_OWNER_STATUSES table is a registration control object within the Oracle E-Business Tax (ZX) application schema. It records the registration status of application programming interfaces (APIs) for each registered API owner, broken down by service category. In effect, the table acts as a state register that E-Business Tax consults to determine whether a given calling application or external system is authorized and active for a specific category of tax service.

The object resides in the ZX schema and carries a VALID status in ETRM 12.1.1 and 12.2.2. Its physical structure is documented with eight columns and one unique index in addition to the primary key. From a dimensional modeling perspective, the mined relationship data classifies this object as standalone, meaning no foreign key dependencies were detected. As a modeling suggestion rather than a documented fact, this pattern aligns most closely with a satellite structure: the composite key identifies the owner-and-category combination, while the status and audit columns describe the changing state of that combination over time.

Key Information Stored

Each row represents the registration status of one API owner for one service category. The most significant columns are:

• API_OWNER_ID — Identifier of the registered API owner (the calling application or integration). Part of the composite primary key.
• SERVICE_CATEGORY_CODE — The service category against which the owner's API registration is evaluated. Part of the composite primary key.
• STATUS_CODE — The current registration status value for the owner/category pair; this is the operative business flag that downstream tax processing reads.
• CREATION_DATE, CREATED_BY — Standard WHO columns capturing when and by whom the registration status row was first created.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO columns capturing the most recent modification and the session that performed it.

The surrogate primary key is ZX_API_OWNER_STATUSES_PK, defined over (API_OWNER_ID, SERVICE_CATEGORY_CODE). A separate unique index, ZX_API_OWNER_STATUSES_U1, is defined over the same two columns; because the unique index columns match the primary key exactly, the table has no additional business-key candidate beyond the composite key itself.

Common Use Cases and Queries

The principal use case is diagnostic and configuration validation: confirming that a given API owner is registered and active for a required service category before tax calculation or integration calls are attempted. A typical query retrieves the registration state for a specific owner:

• SELECT api_owner_id, service_category_code, status_code, last_update_date FROM zx.zx_api_owner_statuses WHERE api_owner_id = :owner_id;
• Reporting scenarios enumerate all owners whose status is not active: SELECT api_owner_id, service_category_code, status_code FROM zx.zx_api_owner_statuses WHERE status_code <> 'ACTIVE';
• Audit and troubleshooting queries filter on the WHO columns to identify recently modified registrations, for example by last_update_date range.
• Joins to owner-level reference data (such as ZX_API_OWNERS) on API_OWNER_ID support ownership and responsibility reporting.

Because the table is standalone with no detected foreign keys, reporting is generally driven by these two key columns rather than by relational navigation.

Related Objects

The mined relationship data indicates no enforced foreign key dependencies, so related objects are identified by shared key semantics rather than by declared constraints:

• ZX_API_OWNERS — Owner-level reference table; joins on API_OWNER_ID.
• ZX_SERVICE_CATEGORIES — Reference data for SERVICE_CATEGORY_CODE.
• ZX_API_OWNER_STATUSES_PK — Primary key constraint object over (API_OWNER_ID, SERVICE_CATEGORY_CODE).
• ZX_API_OWNER_STATUSES_U1 — Unique index over the same composite key columns.
• Additional ZX registration and setup tables (for example ZX_SERVICE_TYPES and ZX_PARTY_TAX_PROFILE) that share the API owner and service category vocabulary within the E-Business Tax configuration model.

Because referential integrity is not enforced at the database level, integrators should treat these relationships as logical and validate them explicitly in query logic.