Results for “ops_instance”

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

Overview

FND_CONC_PP_ACTIONS is an Application Object Library (FND) table owned by the APPLSYS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented description identifies it as the "Post Concurrent Request processing actions table." In practice, the table stores the definitions of actions that Oracle Concurrent Manager executes after a concurrent request completes, including the action type, the status conditions under which the action fires, the arguments passed to the action, and the sequence in which multiple actions are evaluated for a single request.

Each row associates a set of post-processing actions with a specific concurrent request, referenced through CONCURRENT_REQUEST_ID. This supports features such as automatic notification, printing, re-running, or chaining of a request upon completion, driven by the outcome (success, warning, or failure) indicated by the status flag columns.

Based on the heuristic Data Vault classification derived from the foreign key structure, this table is best modeled as a link. It connects a concurrent request (via CONCURRENT_REQUEST_ID) to the users, login sessions, and original-system records involved in its post-processing lifecycle. This classification is a modeling suggestion rather than a documented Oracle attribute, and it reflects the table's role as a relationship-bearing entity rather than a pure descriptive satellite or standalone hub.

Key Information Stored

Among the 31 documented columns, the most significant are:

• CONCURRENT_REQUEST_ID — The primary key (FND_CONC_PP_ACTIONS_PK) and the foreign key to FND_CONCURRENT_REQUESTS. It identifies the request to which the post-processing action belongs.
• ACTION_TYPE — The category of post-processing action to be performed.
• STATUS_S_FLAG, STATUS_W_FLAG, STATUS_F_FLAG — Flags controlling whether the action is triggered on Success, Warning, or Failure completion states.
• ARGUMENTS, ARGUMENT1 … ARGUMENT10 — The parameter values supplied to the action, with the aggregate ARGUMENTS column complemented by ten discrete argument slots.
• COMPLETED, NUMBER_OF_COPIES — Completion state and the number of copies to produce where the action involves output.
• SEQUENCE — The evaluation order when several actions apply to one request.
• PROGRAM_APPLICATION_ID, PROGRAM_ID — The concurrent program context for the action.
• ORIG_SYSTEM, ORIG_SYSTEM_ID — The originating system reference, with ORIG_SYSTEM_ID linked to HZ_ORIG_SYSTEMS_B.
• PROCESSOR_ID, OPS_INSTANCE, PUBLISHER_RETURN_RESULTS — Processing and publishing metadata.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, with the user columns referencing FND_USER and LAST_UPDATE_LOGIN referencing FND_LOGINS.

The surrogate primary key is CONCURRENT_REQUEST_ID. Business-key candidates are the audit and origin columns, which participate in the documented foreign key relationships.

Common Use Cases and Queries

Typical uses include auditing and troubleshooting why a given post-processing action did or did not fire, and building reports on completion-triggered actions.

• Retrieve all actions for a specific request:

SELECT a.concurrent_request_id, a.action_type,
       a.status_s_flag, a.status_w_flag, a.status_f_flag,
       a.sequence, a.completed
FROM   applsys.fnd_conc_pp_actions a
WHERE  a.concurrent_request_id = :request_id
ORDER  BY a.sequence;

• Identify failed or incomplete actions:

SELECT a.concurrent_request_id, a.action_type
FROM   applsys.fnd_conc_pp_actions a
WHERE  a.completed = 'N';

• Join to FND_CONCURRENT_REQUESTS to correlate actions with program and phase:

SELECT r.request_id, r.phase_code, r.status_code, a.action_type
FROM   applsys.fnd_concurrent_requests r,
       applsys.fnd_conc_pp_actions a
WHERE  r.request_id = a.concurrent_request_id;

Related Objects

The documented foreign key relationships connect FND_CONC_PP_ACTIONS to the following significant objects:

• FND_CONCURRENT_REQUESTS — joined on CONCURRENT_REQUEST_ID; the parent request for each post-processing action.
• FND_USER — referenced twice, via CREATED_BY and LAST_UPDATED_BY.
• FND_LOGINS — referenced via LAST_UPDATE_LOGIN.
• HZ_ORIG_SYSTEMS_B — referenced via ORIG_SYSTEM_ID, linking to trading-community origin system definitions.

Together these relationships establish FND_CONC_PP_ACTIONS as a link entity interposed between concurrent request processing and the user, login, and origin-system records that govern it.