Results for “fnd_conc_pp_temp_memb_pk”

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

Overview

FND_CONC_PP_TEMPLATE_MEMBERS is an Application Object Library (FND) table owned by the APPLSYS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the individual member rows that make up a concurrent program request template used by the Concurrent Manager's "Request Templates" / request set-style grouping feature (Enable Concurrent Program Templates). Each row represents one concurrent program (plus its execution sequence and argument set) that participates in a given template, together with per-member status flags that describe how the member behaves at submission time.

The ETRM metadata classifies this object, heuristically, as a link (relationship) table based on its foreign-key structure. Under a Data Vault modeling lens, FND_CONC_PP_TEMPLATE_MEMBERS is best understood as the link between a template header (FND_CONC_PP_TEMPLATES) and the individual concurrent program definitions it contains, with its own descriptive attributes (arguments, flags, active dates) behaving like satellite data on that link. This "Retrofitted" status in the ETRM indicates the table was added to the documented schema after the original release documentation and should be treated as a supported, valid object.

Key Information Stored

The physical schema documents 17 columns. The most significant are:

• TEMPLATE_ID — Foreign-key reference to the parent template header. Part of the composite primary key.
• SEQUENCE — Ordering position of the member within the template. Part of the composite primary key and the natural business identifier alongside TEMPLATE_ID.
• PROGRAM_APPLICATION_ID and PROGRAM_ID — Identify the concurrent program (application + program) that this member row represents.
• ARGUMENTS — The stored argument string passed to the concurrent program when the template is submitted.
• ACTION_TYPE — Determines how the member is processed (for example, whether it is submitted, skipped, or conditionally executed) within the template flow.
• ENABLED_FLAG — Indicates whether this member is currently active for the template.
• STATUS_S_FLAG, STATUS_W_FLAG, STATUS_F_FLAG — Status-related control flags governing member behavior on success, warning, and failure outcomes respectively.
• START_DATE_ACTIVE and END_DATE_ACTIVE — Effective dating that bounds when the member is valid.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS WHO columns capturing audit trail and the login session that last touched the row.

The primary key is FND_CONC_PP_TEMP_MEMB_PK, defined on the composite of TEMPLATE_ID and SEQUENCE. There is no separate surrogate key; the business key and the primary key coincide, meaning TEMPLATE_ID plus SEQUENCE uniquely identifies each member.

Common Use Cases and Queries

Typical scenarios include: confirming which concurrent programs belong to a template and in what order they run; verifying the argument string assigned to a specific member; and auditing who created or last modified a template member. A representative query joins the member table to the concurrent program definition:

• List members of a template: SELECT TEMPLATE_ID, SEQUENCE, PROGRAM_APPLICATION_ID, PROGRAM_ID, ENABLED_FLAG FROM FND_CONC_PP_TEMPLATE_MEMBERS WHERE TEMPLATE_ID = :id ORDER BY SEQUENCE;
• Resolve program names, joining FND_CONCURRENT_PROGRAMS on PROGRAM_APPLICATION_ID and PROGRAM_ID.
• Audit activity, joining CREATED_BY and LAST_UPDATED_BY to FND_USER to map user IDs to usernames.
• Filter on ENABLED_FLAG or date ranges to report currently active members.

Because the table is narrow and highly selective on TEMPLATE_ID, these queries are efficient and are commonly used in support and upgrade validation reports.

Related Objects

The following objects are most significant for this table based on its documented relationships:

• FND_CONC_PP_TEMPLATES — Parent template header; joined on TEMPLATE_ID (implied by the primary key name and template model).
• FND_USER — Referenced twice: CREATED_BY and LAST_UPDATED_BY both point to FND_USER.
• FND_LOGINS — Referenced via LAST_UPDATE_LOGIN.
• FND_CONCURRENT_PROGRAMS — Holds the program definition matched through PROGRAM_APPLICATION_ID and PROGRAM_ID.
• FND_APPLICATION — Resolves PROGRAM_APPLICATION_ID to an application short name.