Results for “batch_command”

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

Overview

RH_ACTN_TBL is a Process Manufacturing (OPM) table owned by the GMP schema in Oracle EBS 12.1.1 and 12.2.2. It stores the syntaxes — the command definitions and parameters — for the actions executed during data transfer between Oracle Process Manufacturing (OPM) and the Rhythm planning engine. In other words, it functions as a rule or template repository: each row defines a discrete action that the integration layer can perform, such as launching a batch command, invoking an interface routine, or sequencing a step within a data-load routine. The table underpins the GMP-to-Rhythm interoperability used by Process Planning, so its contents directly influence how planning data is extracted from and returned to the OPM application tables.

From a heuristic Data Vault modeling perspective, RH_ACTN_TBL is best described as a standalone reference or lookup structure. Because the mined foreign-key analysis shows no parent relationships and no dependent children, it does not behave as a transactional hub, nor as a satellite attached to a business hub. It is a self-contained configuration table whose composite primary key defines the grain of each action definition.

Key Information Stored

The table contains 11 documented columns. The composite primary key is enforced by the unique index RH_ACTN_TBL_PK, which covers ACTION_SET and SEQUENCE_NUMBER. These two columns therefore act as the business-key candidates as well as the physical row identifier; there is no separate surrogate key column.

• ACTION_SET — Groups related actions into a named set or routine; the first component of the primary key.
• SEQUENCE_NUMBER — Orders the actions within an action set; the second component of the primary key and the driver of execution order.
• ACTION_TYPE — Classifies the kind of action to be performed during the OPM–Rhythm transfer.
• ACTION_IND — Indicator flag qualifying how the action is applied or whether it is active.
• BATCH_COMMAND — The concrete command or syntax string executed by the integration process for this action.
• DESCRIPTION — Free-text explanation of the action's purpose, useful for maintenance and troubleshooting.
• CREATED_BY, CREATION_DATE — Standard WHO-column audit attributes recording row creation.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO-column audit attributes recording the most recent modification and the login context of the updater.

The WHO columns confirm that the table is maintained through normal EBS application processing rather than being a purely external staging object.

Common Use Cases and Queries

Typical usage centers on inspecting, auditing, and troubleshooting the OPM–Rhythm transfer configuration. A common pattern is to list all actions in execution order for a given set:

• SELECT sequence_number, action_type, action_ind, batch_command, description FROM gmp.rh_actn_tbl WHERE action_set = :action_set ORDER BY sequence_number;
• Identifying which action sets reference a particular command type using WHERE action_type = :type.
• Audit queries filtering on last_update_date or last_updated_by to detect recent configuration changes.
• Joining to the transfer or planning log tables to correlate a failed step with its defining row.

Reporting use cases include configuration documentation, change-control extracts, and pre-upgrade reviews that validate the syntax stored in BATCH_COMMAND ahead of a 12.1.1 to 12.2.2 migration.

Related Objects

The mined relationship data classifies RH_ACTN_TBL as standalone: no foreign keys reference it and it references no parent. Its primary key RH_ACTN_TBL_PK (ACTION_SET, SEQUENCE_NUMBER) is the only documented unique constraint. Consequently, related objects are functional rather than declarative, and join columns are inferred from the integration context:

• Other GMP RH_* control tables (for example action-set and transfer-log tables) joined on ACTION_SET to associate definitions with execution instances.
• Rhythm/OPM interface programs and concurrent programs that read ACTION_SET and BATCH_COMMAND at runtime.
• Planning engine staging tables populated as a result of the actions defined here.
• Standard EBS audit and security views referencing CREATED_BY and LAST_UPDATED_BY against FND_USER.

Because no enforced referential integrity exists, any such joins should be validated empirically before being relied upon in production reporting.