Results for “fnd_stage_link_vertices”

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

Overview

FND_STAGE_LINK_VERTICES is a table owned by the APPLSYS schema within the FND (Application Object Library) product of Oracle E-Business Suite, and is documented as VALID in both release 12.1.1 and 12.2.2. The table stores the graphical and logical linkage metadata that defines how nodes (vertices) within a request set stage are connected when a request set is modelled as a directed graph in the Concurrent Manager request set builder interface. Each row represents a single vertex participating in a stage-link relationship, capturing both the identity of the stage and the spatial coordinates and sequencing information used to render the flow diagram.

From a Data Vault modelling perspective, the mined relationship structure suggests this object behaves as a link table. Its composite primary key references multiple parent entities — the request set stage definition plus the owning application and request set — making it a many-to-many associative construct rather than an independent hub or a descriptive satellite.

Key Information Stored

The table contains 13 documented columns. The most significant are:

• VERTEX_ID — Part of the composite primary key; the surrogate identifier for the vertex within the graph.
• SET_APPLICATION_ID, REQUEST_SET_ID, REQUEST_SET_STAGE_ID — The remaining primary key components; together they anchor the vertex to a specific request set stage owned by a given application, forming the business-key candidate for the parent stage.
• LINK — Describes the linkage semantics of the vertex within the stage graph.
• X, Y — Spatial coordinates used by the request set builder to position the vertex on the graphical canvas.
• SEQUENCE — Ordering value controlling the sequence in which linked vertices are processed or rendered.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns whose foreign keys reference FND_USER (CREATED_BY, LAST_UPDATED_BY) and FND_LOGINS (LAST_UPDATE_LOGIN).

The primary key constraint FND_STAGE_LINK_VERTICES_PK is defined over VERTEX_ID, SET_APPLICATION_ID, REQUEST_SET_ID, and REQUEST_SET_STAGE_ID.

Common Use Cases and Queries

Typical scenarios include auditing the layout and connectivity of request sets, reproducing the request set builder diagram, and diagnosing run-time behaviour where stage sequencing affects concurrent program execution. A representative query joining the vertex to its parent stage is:

• SELECT v.VERTEX_ID, v.SEQUENCE, v.X, v.Y, s.STAGE_NAME FROM FND_STAGE_LINK_VERTICES v, FND_REQUEST_SET_STAGES s WHERE v.SET_APPLICATION_ID = s.SET_APPLICATION_ID AND v.REQUEST_SET_ID = s.REQUEST_SET_ID AND v.REQUEST_SET_STAGE_ID = s.REQUEST_SET_STAGE_ID;
• Filter by REQUEST_SET_ID and SET_APPLICATION_ID to isolate all vertices belonging to one request set.
• Order by SEQUENCE to reconstruct the intended execution or display order.
• Join to FND_USER via CREATED_BY or LAST_UPDATED_BY to identify who last modified the vertex definition.

Related Objects

• FND_REQUEST_SET_STAGES — Parent table referenced through SET_APPLICATION_ID, REQUEST_SET_ID, and REQUEST_SET_STAGE_ID.
• FND_USER — Referenced via CREATED_BY and LAST_UPDATED_BY.
• FND_LOGINS — Referenced via LAST_UPDATE_LOGIN.
• FND_REQUEST_SETS — Provides the request set header that owns the stages and their vertices.
• FND_REQUEST_SET_PROGRAMS — Defines the concurrent programs that populate the stages connected by these vertices.