Search Results okc_rep_contracts_all
The OKC_REP_CONTRACTS_ALL
table in Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2 is a critical repository for contract data within the Oracle Contracts module. This table stores comprehensive information about contracts, serving as the backbone for contract management, reporting, and integration with other Oracle EBS modules. Below is a detailed analysis of its structure, purpose, and key attributes.
Overview
OKC_REP_CONTRACTS_ALL
is part of the Oracle Contracts (OKC) schema, designed to support contract lifecycle management (CLM). It acts as a reporting table, often populated via concurrent programs or database triggers, to consolidate contract-related data for analytical and operational purposes. Unlike transactional tables, it is optimized for read-heavy operations, ensuring efficient querying for reporting dashboards, compliance audits, and business intelligence.
Key Columns and Structure
The table includes columns that capture contract metadata, terms, parties, and lifecycle states. Notable columns include:
- CONTRACT_ID: Primary key, referencing the contract in transactional tables like
OKC_K_HEADERS_ALL
. - CONTRACT_NUMBER: Human-readable identifier for the contract.
- START_DATE/END_DATE: Defines the contract's validity period.
- STATUS: Tracks lifecycle stages (e.g., DRAFT, SIGNED, TERMINATED).
- PARTY_ID: Links to
HZ_PARTIES
for customer/vendor details. - TEMPLATE_ID: References standardized contract templates.
- ORG_ID: Supports multi-org structures, segregating data by operating unit.
Integration with Oracle EBS Modules
The table integrates with:
- Oracle Receivables/Payables: Ties contracts to invoices or payments via
CUST_ACCOUNT_ID
orVENDOR_ID
. - Oracle Projects: Links to project agreements through
PROJECT_ID
. - General Ledger: Captures financial attributes like
REVENUE_AMOUNT
for accounting.
Functional Significance
OKC_REP_CONTRACTS_ALL
enables:
- Compliance Reporting: Tracks contractual obligations for regulatory audits.
- Renewal Management: Flags expiring contracts via
END_DATE
. - Performance Analytics: Measures contract value, duration, and fulfillment metrics.
Technical Considerations
In EBS 12.2.2, the table may leverage Oracle RAC for scalability, while 12.1.1 relies on traditional indexing. Partitioning strategies (e.g., by ORG_ID
) improve query performance. Data is typically refreshed via concurrent programs like "Contract Reports Data Generation."
Customization and Extensions
Customers often extend the table with descriptive flexfields (DFFs) or custom columns to capture industry-specific attributes. However, direct DML operations are discouraged; updates should flow through Oracle Contracts' APIs to maintain data integrity.
Conclusion
OKC_REP_CONTRACTS_ALL
is a pivotal table in Oracle EBS Contracts, bridging transactional data with reporting needs. Its design reflects Oracle's emphasis on scalability, integration, and compliance, making it indispensable for organizations leveraging Oracle Contracts for CLM.
-
Table: OKC_REP_CONTRACTS_ALL
12.1.1
owner:OKC, object_type:TABLE, fnd_design_data:OKC.OKC_REP_CONTRACTS_ALL, object_name:OKC_REP_CONTRACTS_ALL, status:VALID, product: OKC - Contracts Core , description: This is the main Contracts table. This table stores the latest version of all Repository-authored contracts. , implementation_dba_data: OKC.OKC_REP_CONTRACTS_ALL ,
-
Table: OKC_REP_CONTRACTS_ALL
12.2.2
owner:OKC, object_type:TABLE, fnd_design_data:OKC.OKC_REP_CONTRACTS_ALL, object_name:OKC_REP_CONTRACTS_ALL, status:VALID, product: OKC - Contracts Core , description: This table is the main Contracts table. This table stores the latest version of all contracts authored in Contract Repository. , implementation_dba_data: OKC.OKC_REP_CONTRACTS_ALL ,
-
Table: OKC_REP_CONTRACT_RELS
12.2.2
owner:OKC, object_type:TABLE, fnd_design_data:OKC.OKC_REP_CONTRACT_RELS, object_name:OKC_REP_CONTRACT_RELS, status:VALID, product: OKC - Contracts Core , description: This table stores a relationship between two contracts that are created in Repository. , implementation_dba_data: OKC.OKC_REP_CONTRACT_RELS ,
-
Table: OKC_REP_CONTRACT_RELS
12.1.1
owner:OKC, object_type:TABLE, fnd_design_data:OKC.OKC_REP_CONTRACT_RELS, object_name:OKC_REP_CONTRACT_RELS, status:VALID, product: OKC - Contracts Core , description: Stores the relationship between two contracts. The two related contracts are CONTRACT_ID and RELATED_CONTRACT_ID. RELATED_CONTRACT_ROLE is the role of contract RELATED_CONTRACT_ID. , implementation_dba_data: OKC.OKC_REP_CONTRACT_RELS ,
-
Table: OKC_REP_CONTACT_ROLES_B
12.1.1
owner:OKC, object_type:TABLE, fnd_design_data:OKC.OKC_REP_CONTACT_ROLES_B, object_name:OKC_REP_CONTACT_ROLES_B, status:VALID, product: OKC - Contracts Core , description: Stores the user-defined contact roles. , implementation_dba_data: OKC.OKC_REP_CONTACT_ROLES_B ,
-
Table: OKC_REP_CONTRACT_ACCESS
12.1.1
product: OKC - Contracts Core , description: Stores the access control list information for a contract. , implementation_dba_data: Not implemented in this database ,
-
Table: OKC_REP_CON_APPROVALS
12.2.2
owner:OKC, object_type:TABLE, fnd_design_data:OKC.OKC_REP_CON_APPROVALS, object_name:OKC_REP_CON_APPROVALS, status:VALID, product: OKC - Contracts Core , description: This table stores a Contract's approval data. . , implementation_dba_data: OKC.OKC_REP_CON_APPROVALS ,
-
Table: OKC_REP_CONTACT_ROLES_B
12.2.2
owner:OKC, object_type:TABLE, fnd_design_data:OKC.OKC_REP_CONTACT_ROLES_B, object_name:OKC_REP_CONTACT_ROLES_B, status:VALID, product: OKC - Contracts Core , description: This table stores user-defined Contact Roles. , implementation_dba_data: OKC.OKC_REP_CONTACT_ROLES_B ,
-
Table: OKC_REP_CONTRACT_ACCESS
12.2.2
product: OKC - Contracts Core , description: Stores the access control list information for a contract. , implementation_dba_data: Not implemented in this database ,
-
Table: OKC_REP_CONTRACT_PARTIES
12.2.2
owner:OKC, object_type:TABLE, fnd_design_data:OKC.OKC_REP_CONTRACT_PARTIES, object_name:OKC_REP_CONTRACT_PARTIES, status:VALID, product: OKC - Contracts Core , description: This table stores the Parties in a Contract. The Party can be from PO_VENDORS, HZ_PARTIES, or HR_ALL_ORGANIZATION_UNITS. A PARTY_ID with a PARTY_ROLE_CODE of SUPPLIER-ORG comes from PO_VENDORS; A PARTY_ID with a PARTY_ROLE_CODE of CUSTOMER , implementation_dba_data: OKC.OKC_REP_CONTRACT_PARTIES ,
-
Table: OKC_REP_CON_STATUS_HIST
12.2.2
owner:OKC, object_type:TABLE, fnd_design_data:OKC.OKC_REP_CON_STATUS_HIST, object_name:OKC_REP_CON_STATUS_HIST, status:VALID, product: OKC - Contracts Core , description: This table stores the status changes history of a contract. Each version of a contract can have its own status history. , implementation_dba_data: OKC.OKC_REP_CON_STATUS_HIST ,
-
View: OKC_REP_DOC_VERSIONS_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:OKC.OKC_REP_DOC_VERSIONS_V, object_name:OKC_REP_DOC_VERSIONS_V, status:VALID, product: OKC - Contracts Core , description: This view returns repository contract versions , implementation_dba_data: APPS.OKC_REP_DOC_VERSIONS_V ,
-
View: OKC_REP_DOC_VERSIONS_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:OKC.OKC_REP_DOC_VERSIONS_V, object_name:OKC_REP_DOC_VERSIONS_V, status:VALID, product: OKC - Contracts Core , description: This view returns repository contract versions , implementation_dba_data: APPS.OKC_REP_DOC_VERSIONS_V ,
-
Table: OKC_BUS_DOC_TYPES_B
12.2.2
owner:OKC, object_type:TABLE, fnd_design_data:OKC.OKC_BUS_DOC_TYPES_B, object_name:OKC_BUS_DOC_TYPES_B, status:VALID, product: OKC - Contracts Core , description: Stores all business document types and preferences related to those documents. This information is seeded by each product team that integrates with Oracle Contracts to implement Contract authoring. , implementation_dba_data: OKC.OKC_BUS_DOC_TYPES_B ,
-
Table: OKC_BUS_DOC_TYPES_B
12.1.1
owner:OKC, object_type:TABLE, fnd_design_data:OKC.OKC_BUS_DOC_TYPES_B, object_name:OKC_BUS_DOC_TYPES_B, status:VALID, product: OKC - Contracts Core , description: Stores all business document types and preferences related to those documents. This information is seeded by each product team that integrates with Oracle Contracts to implement Contract authoring. , implementation_dba_data: OKC.OKC_BUS_DOC_TYPES_B ,
-
Table: OKC_REP_PARTY_CONTACTS
12.2.2
owner:OKC, object_type:TABLE, fnd_design_data:OKC.OKC_REP_PARTY_CONTACTS, object_name:OKC_REP_PARTY_CONTACTS, status:VALID, product: OKC - Contracts Core , description: This table stores the contacts for a party in a contract. The contact record can be from PO_VENDOR_CONTACTS, HZ_PARTIES, or PER_PEOPLE_F, depending on the party role of the contact party. A contact whose party has a role of SUPPLIER_ORG c , implementation_dba_data: OKC.OKC_REP_PARTY_CONTACTS ,
-
Table: OKC_REP_CONTRACT_PARTIES
12.1.1
owner:OKC, object_type:TABLE, fnd_design_data:OKC.OKC_REP_CONTRACT_PARTIES, object_name:OKC_REP_CONTRACT_PARTIES, status:VALID, product: OKC - Contracts Core , description: Stores the Parties in a contract. The party can be from PO_VENDORS, HZ_PARTIES, or HR_ALL_ORGANIZATION_UNITS. A PARTY_ID with a PARTY_ROLE_CODE of SUPPLIER comes from PO_VENDORS; A PARTY_ID with a PARTY_ROLE_CODE of CUSTOMER or PARTNER com , implementation_dba_data: OKC.OKC_REP_CONTRACT_PARTIES ,