Results for “okc_conc_requests”

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

Overview

OKC_CONC_REQUESTS is a Contracts Core (OKC) table in Oracle E-Business Suite that serves as a staging and control structure for launching concurrent requests related to contract copy operations. Its documented purpose is to hold the parameters and identifiers required to submit and track concurrent programs that duplicate contract data — for example, copying a contract header, lines, or related components from a source contract to a target. The table resides in the OKC schema and is classified as VALID in the ETRM 12.2.2 repository, with a documented physical structure of 21 columns.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure is standalone. This suggests the table functions as an independent transient or operational record rather than a classic hub, link, or satellite. It carries its own surrogate primary key but does not participate in a dense web of referential relationships; its principal external dependency is a security group reference. In practice it behaves like a work-table supporting the copy concurrent program lifecycle.

Key Information Stored

The table is anchored by the surrogate primary key ID, enforced through the unique key OKC_CONC_REQUESTS_UK. The most significant columns include:

• ID — the surrogate primary key uniquely identifying each copy request record.
• SOURCE_ID — identifier of the source object (typically the contract being copied from).
• TARGET_CHR_ID — the target contract header identifier that the copy operation will populate.
• TARGET_CLE_ID — the target contract line or entity identifier.
• LSE_ID — a line/entity reference used to scope the copy.
• COMPONENT_TYPE — indicates which contract component (header, line, term, etc.) is being copied.
• PROCESS_NAME — the name of the concurrent process to be launched.
• LINE_EXISTS_YN and LINE_EXP_YN — flags controlling whether lines exist or should be expanded during the copy.
• ORG_ID — the operating unit context for multi-org security.
• REQUEST_ID — the concurrent request identifier returned by the concurrent manager, enabling status tracking.
• SECURITY_GROUP_ID — foreign key referencing FND_SECURITY_GROUPS, governing data visibility.
• PROGRAM_ID and PROGRAM_APPLICATION_ID — identify the executable concurrent program definition.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.

Business-key candidates are limited; the unique index is defined on ID, making it the sole documented uniqueness constraint.

Common Use Cases and Queries

Typical scenarios involve monitoring and troubleshooting contract copy submissions. A support analyst may query outstanding or failed copy requests with:

• SELECT id, source_id, target_chr_id, component_type, request_id FROM okc_conc_requests WHERE request_id IS NULL; to find requests that never reached the concurrent manager.
• Correlating to FND_CONCURRENT_REQUESTS via REQUEST_ID to inspect completion status and error output.
• Auditing copy activity per operating unit using ORG_ID, or restricting by SECURITY_GROUP_ID for data security.
• Reporting on component types copied across a migration or mass-cloning exercise.

Related Objects

The documented FK links SECURITY_GROUP_ID to FND_SECURITY_GROUPS. Beyond that, functional dependency exists with the concurrent manager tables, principally FND_CONCURRENT_REQUESTS (joined on REQUEST_ID) and FND_CONCURRENT_PROGRAMS (via PROGRAM_ID and PROGRAM_APPLICATION_ID). The target and source identifiers (TARGET_CHR_ID, SOURCE_ID, TARGET_CLE_ID, LSE_ID) logically reference the OKC contract header and line tables such as OKC_K_HEADERS and its associated line structures, though these are not enforced as documented foreign keys. Because the table is classified standalone, its relationships are primarily functional rather than declarative.