Search Results xdp_service_val_acts




Overview
Explore in AI Chat

Overview

The XDP_SERVICE_VAL_ACTS table is a core data object within the Oracle E-Business Suite Provisioning (XDP) module, applicable to both the 12.1.1 and 12.2.2 releases. It serves as a central repository for defining and managing the permissible actions that can be performed on a specific service. In the context of service provisioning, a service represents a deliverable product or offering, and this table establishes the catalog of executable actions—such as "Activate," "Suspend," or "Upgrade"—that are valid for that service. This definition is critical for enforcing business rules, guiding workflow processes, and ensuring that only authorized operations can be initiated against a service instance within the provisioning lifecycle.

Key Information Stored

The table's structure is designed to link services with their actionable operations and associated processing logic. While the full column list is not detailed in the provided metadata, the primary and foreign key relationships highlight its essential components. The primary identifier is the SERVICE_VAL_ACT_ID. The table uniquely constrains the combination of SERVICE_ID and ACTION_CODE_ID, which together define which action code is valid for a given service. Key relational columns include INVENTORY_ITEM_ID and ORGANIZATION_ID, which link to inventory items in MTL_SYSTEM_ITEMS_B, potentially for material or component associations. The WI_MAPPING_PROC column references a procedure (XDP_PROC_BODY) that likely contains the business logic or workflow mapping instructions for the specific service action.

Common Use Cases and Queries

This table is primarily accessed during the design and execution phases of service provisioning. Administrators use it to configure the action menu for services. A common reporting need is to list all valid actions for a specific service, which can be achieved with a query joining XDP_SERVICES. During order fulfillment, provisioning engines query this table to validate if a requested action (e.g., "DISCONNECT") is permitted for the service type being processed. A typical validation SQL pattern would be:

  • SELECT COUNT(*) FROM xdp_service_val_acts vsa, xdp_services s WHERE vsa.service_id = s.service_id AND s.service_code = '&SERVICE_CODE' AND vsa.action_code_id = (SELECT action_code_id FROM xdp_action_codes_b WHERE action_code = '&ACTION_CODE');

This ensures the action is authorized before triggering downstream workflows.

Related Objects

The XDP_SERVICE_VAL_ACTS table is a nexus within the XDP schema, with documented relationships to several key objects. It references parent tables to pull in master data:

  • XDP_SERVICES via SERVICE_ID: The master definition of the service.
  • MTL_SYSTEM_ITEMS_B via INVENTORY_ITEM_ID and ORGANIZATION_ID: Links to Inventory items.
  • XDP_PROC_BODY via WI_MAPPING_PROC: References the procedural logic for workflow mapping.

Conversely, it is referenced as a parent table by:

  • XDP_SERVICE_VAL_ACTS_TL via SERVICE_VAL_ACT_ID: The Translation table for multilingual support.
  • XDP_SERVICE_WI_MAP via SERVICE_VAL_ACT_ID: Likely stores specific workflow instance mappings for the valid action.

These relationships underscore its role as a control point between service definition, inventory, business logic, and workflow execution.