Search Results okc_bus_doc_types_tl
The OKC_BUS_DOC_TYPES_TL
table in Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2 is a critical component of the Oracle Contracts Core module. This table stores translated descriptions and names of business document types, enabling multilingual support within the application. It is part of the Oracle Contracts (OKC) schema, which manages contractual agreements, terms, and conditions across various business processes. The table works in conjunction with its base table, OKC_BUS_DOC_TYPES_B
, which contains non-translatable attributes, while the _TL
(Translation) table holds language-specific data.
Table Structure and Key Columns
TheOKC_BUS_DOC_TYPES_TL
table includes the following key columns:
- DOC_TYPE_ID: A foreign key referencing the base table, linking translated data to the corresponding business document type.
- LANGUAGE: Stores the ISO language code (e.g., 'US' for American English, 'FR' for French) to identify the translation.
- SOURCE_LANG: Indicates the original language of the record, used for synchronization during translation updates.
- NAME: The translated name of the business document type, displayed in the user interface.
- DESCRIPTION: A detailed description of the document type in the specified language.
Purpose and Functional Role
This table supports the globalization features of Oracle EBS by allowing organizations to maintain contract-related document types in multiple languages. For example, a document type like "Sales Agreement" can be displayed as "Contrato de Venta" in Spanish or "Contrat de Vente" in French, depending on the user's session language. This is particularly useful for multinational corporations operating in diverse linguistic regions.Integration with Oracle Contracts
TheOKC_BUS_DOC_TYPES_TL
table is referenced by other Contracts Core modules, including:
- Contract Authoring: Ensures document type names and descriptions appear correctly in the user's preferred language.
- Reporting and Analytics: Enables localized reporting by displaying document types in the appropriate language.
- Approval Workflows: Supports multilingual notifications and approvals by using translated document type names.
Technical Considerations
- Multi-Language Support (MLS): The table adheres to Oracle's MLS architecture, where each translated record is tied to a language code. The
SOURCE_LANG
column ensures data consistency when translations are updated. - Indexing: Typically indexed on
DOC_TYPE_ID
andLANGUAGE
for efficient querying during runtime. - Seed Data: Pre-populated with standard document types during Oracle EBS installation, with translations available for commonly supported languages.
Customization and Extensions
Customers can add custom document types and their translations by inserting records into both the base (OKC_BUS_DOC_TYPES_B
) and translation (OKC_BUS_DOC_TYPES_TL
) tables. However, direct DML operations should be avoided in favor of Oracle's APIs (e.g., OKC_BUS_DOC_TYPES_PKG
) to maintain data integrity.
Conclusion
TheOKC_BUS_DOC_TYPES_TL
table is a foundational element in Oracle Contracts, enabling seamless multilingual support for business document types. Its design aligns with Oracle's global business requirements, ensuring consistent and localized user experiences across geographies. Proper utilization of this table enhances contract management processes while maintaining compliance with internationalization standards.
-
Table: OKC_BUS_DOC_TYPES_TL
12.2.2
owner:OKC, object_type:TABLE, fnd_design_data:OKC.OKC_BUS_DOC_TYPES_TL, object_name:OKC_BUS_DOC_TYPES_TL, status:VALID, product: OKC - Contracts Core , description: This table stores the translatable attributes of the Business Document Types. , implementation_dba_data: OKC.OKC_BUS_DOC_TYPES_TL ,
-
Table: OKC_BUS_DOC_TYPES_TL
12.1.1
owner:OKC, object_type:TABLE, fnd_design_data:OKC.OKC_BUS_DOC_TYPES_TL, object_name:OKC_BUS_DOC_TYPES_TL, status:VALID, product: OKC - Contracts Core , description: This table stores the translatable attributes of the Business Document Types. , implementation_dba_data: OKC.OKC_BUS_DOC_TYPES_TL ,
-
APPS.OKC_BUS_DOC_TYPES_PVT dependencies on OKC_BUS_DOC_TYPES_TL
12.1.1
-
APPS.OKC_CA_UTIL_PVT dependencies on OKC_BUS_DOC_TYPES_TL
12.1.1
-
APPS.OKC_K_ENTITY_LOCKS_GRP dependencies on OKC_BUS_DOC_TYPES_TL
12.2.2
-
APPS.OKC_REP_UPD_CON_ADMIN_PVT dependencies on OKC_BUS_DOC_TYPES_TL
12.2.2
-
APPS.OKC_REP_QA_CHECK_PVT dependencies on OKC_BUS_DOC_TYPES_TL
12.1.1
-
APPS.OKC_CA_UTIL_PVT dependencies on OKC_BUS_DOC_TYPES_TL
12.2.2
-
APPS.OKC_ALLOWED_TMPL_USAGES_PVT dependencies on OKC_BUS_DOC_TYPES_TL
12.2.2
-
APPS.OKC_CA_UTIL_PVT dependencies on OKC_BUS_DOC_TYPES_TL
12.2.2
-
APPS.OKC_DELIVERABLE_WF_PVT dependencies on OKC_BUS_DOC_TYPES_TL
12.1.1
-
APPS.OKC_REP_UPD_CON_ADMIN_PVT dependencies on OKC_BUS_DOC_TYPES_TL
12.1.1
-
APPS.OKC_CA_UTIL_PVT dependencies on OKC_BUS_DOC_TYPES_TL
12.1.1
-
APPS.OKC_DELIVERABLE_WF_PVT dependencies on OKC_BUS_DOC_TYPES_TL
12.2.2
-
APPS.OKC_ALLOWED_TMPL_USAGES_PVT dependencies on OKC_BUS_DOC_TYPES_TL
12.1.1
-
APPS.OKC_TERMS_QA_PVT dependencies on OKC_BUS_DOC_TYPES_TL
12.1.1
-
APPS.OKC_TERMS_QA_PVT dependencies on OKC_BUS_DOC_TYPES_TL
12.2.2
-
APPS.OKC_BUS_DOC_TYPES_PVT dependencies on OKC_BUS_DOC_TYPES_TL
12.2.2
-
APPS.OKC_TERMS_MIGRATE_GRP dependencies on OKC_BUS_DOC_TYPES_TL
12.2.2
-
APPS.OKC_REP_QA_CHECK_PVT dependencies on OKC_BUS_DOC_TYPES_TL
12.2.2
-
APPS.OKC_BUS_DOC_TYPES_PVT SQL Statements
12.2.2
-
VIEW: OKC.OKC_BUS_DOC_TYPES_TL#
12.2.2
owner:OKC, object_type:VIEW, object_name:OKC_BUS_DOC_TYPES_TL#, status:VALID,
-
APPS.OKC_BUS_DOC_TYPES_PVT SQL Statements
12.1.1
-
APPS.OKC_BUS_DOC_TYPES_PVT dependencies on FND_LANGUAGES
12.1.1
-
APPS.OKC_BUS_DOC_TYPES_PVT dependencies on FND_LANGUAGES
12.2.2
-
APPS.OKC_REP_UPD_CON_ADMIN_PVT dependencies on HR_ALL_ORGANIZATION_UNITS_TL
12.1.1
-
APPS.OKC_REP_UPD_CON_ADMIN_PVT dependencies on HR_ALL_ORGANIZATION_UNITS_TL
12.2.2
-
APPS.OKC_REP_UPD_CON_ADMIN_PVT dependencies on OKC_TEMPLATE_USAGES
12.1.1
-
APPS.OKC_REP_UPD_CON_ADMIN_PVT dependencies on OKC_TEMPLATE_USAGES
12.2.2
-
APPS.OKC_REP_UPD_CON_ADMIN_PVT dependencies on HR_ALL_ORGANIZATION_UNITS
12.1.1
-
PACKAGE BODY: APPS.OKC_BUS_DOC_TYPES_PVT
12.2.2
-
APPS.OKC_REP_UPD_CON_ADMIN_PVT dependencies on HR_ALL_ORGANIZATION_UNITS
12.2.2
-
APPS.OKC_REP_UPD_CON_ADMIN_PVT dependencies on HZ_CUST_ACCOUNTS
12.2.2
-
SYNONYM: APPS.OKC_BUS_DOC_TYPES_TL
12.2.2
owner:APPS, object_type:SYNONYM, object_name:OKC_BUS_DOC_TYPES_TL, status:VALID,
-
TRIGGER: APPS.OKC_BUS_DOC_TYPES_TL+
12.2.2
owner:APPS, object_type:TRIGGER, object_name:OKC_BUS_DOC_TYPES_TL+, status:VALID,
-
PACKAGE BODY: APPS.OKC_BUS_DOC_TYPES_PVT
12.1.1
-
VIEW: OKC.OKC_BUS_DOC_TYPES_TL#
12.2.2
-
TRIGGER: APPS.OKC_BUS_DOC_TYPES_TL+
12.2.2
-
SYNONYM: APPS.OKC_BUS_DOC_TYPES_TL
12.1.1
owner:APPS, object_type:SYNONYM, object_name:OKC_BUS_DOC_TYPES_TL, status:VALID,
-
APPS.OKC_REP_UPD_CON_ADMIN_PVT dependencies on HZ_CUST_ACCOUNTS
12.1.1
-
APPS.OKC_REP_UPD_CON_ADMIN_PVT dependencies on HZ_PARTIES
12.1.1
-
APPS.OKC_REP_UPD_CON_ADMIN_PVT dependencies on HZ_PARTIES
12.2.2
-
APPS.OKC_DELIVERABLE_WF_PVT dependencies on OKC_BUS_DOC_TYPES_B
12.1.1
-
APPS.OKC_DELIVERABLE_WF_PVT dependencies on OKC_BUS_DOC_TYPES_B
12.2.2
-
VIEW: APPS.OKC_BUS_DOC_TYPES_V
12.1.1
-
VIEW: APPS.OKC_BUS_DOC_TYPES_V
12.2.2
-
TABLE: OKC.OKC_BUS_DOC_TYPES_TL
12.2.2
owner:OKC, object_type:TABLE, fnd_design_data:OKC.OKC_BUS_DOC_TYPES_TL, object_name:OKC_BUS_DOC_TYPES_TL, status:VALID,
-
VIEW: APPS.OKC_BUS_DOC_TYPES_VL
12.1.1
-
TABLE: OKC.OKC_BUS_DOC_TYPES_TL
12.1.1
owner:OKC, object_type:TABLE, fnd_design_data:OKC.OKC_BUS_DOC_TYPES_TL, object_name:OKC_BUS_DOC_TYPES_TL, status:VALID,
-
APPS.OKC_BUS_DOC_TYPES_PVT dependencies on OKC_BUS_DOC_TYPES_B
12.1.1