OKC_BUS_DOC_TYPES_B
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.
Details
-
Schema: FUSION
-
Object owner: OKC
-
Object type: TABLE
-
Tablespace: REFERENCE
Primary Key
| Name | Columns |
|---|---|
|
OKC_BUS_DOC_TYPES_B_PK |
DOCUMENT_TYPE |
Columns
| Name | Datatype | Length | Precision | Not-null | Comments |
|---|---|---|---|---|---|
| DOCUMENT_TYPE | VARCHAR2 | 30 | Yes | Unique Code that identifies business document type | |
| OBJECT_VERSION_NUMBER | NUMBER | 9 | Yes | Used to implement optimistic locking. This number is incremented every time that the row is updated. The number is compared at the start and end of a transaction to detect whether another session has updated the row since it was queried. | |
| DOCUMENT_TYPE_CLASS | VARCHAR2 | 30 | Yes | Document Class to which the document type belongs. Refers to the LOOKUP_CODE in FND_LOOKUPS where LOOKUP_TYPE = OKC_DOCUMENT_CLASS | |
| PROVISION_ALLOWED_YN | VARCHAR2 | 1 | Yes | Flag to indicate whether provisions are allowed for this document type or not. Possible values are Y and N | |
| DOC_PREVIEW_FUNCTION | VARCHAR2 | 30 | The FND Form function that points to the page used to launch Contract Preview. | ||
| INTENT | VARCHAR2 | 1 | Intent of the document type. Possible values are Buy and Sell | ||
| DOC_VIEW_DETAILS_FUNCTION | VARCHAR2 | 30 | FND Form function used for viewing document details from Manage Deliverables page. This is only used in Procurement Contracts | ||
| NOTIFICATION_HEADER_FUNCTION | VARCHAR2 | 2000 | FND Form Function to be used to display notification header region in deliverable notification.This region will include document specific attributes to provide a context to the notification. This is only used in Procurement Contracts | ||
| CONTRACT_TERMS_FUNCTION | VARCHAR2 | 30 | FND Form Function for contract terms structure page. This function will be used in the terms authoring sub flows to navigate back to structure page | ||
| SHOW_EXT_VAR_FLAG | VARCHAR2 | 1 | Yes | Flag to indicate whether supplier updateable flag is to be shown on the UI or not. Possible values are Y and N. This is only used in Procurement Contracts | |
| APPLICATION_ID | NUMBER | Yes | Unique Identifier of the application/product to which the document type belongs. | ||
| MODULE_ID | VARCHAR2 | 32 | Seed Data Framework: indicates the module that owns the row. A module is an entry in Application Taxonomy such as a Logical Business Area. When the MODULE_ID column exists and the owner of the row is not specified, then the Seed Data Framework will not extract the row as seed data. | ||
| ENABLE_AMEND_SUMMARY_YN | VARCHAR2 | 1 | Yes | Flag to indicate whether to display View amendment summary action on the Contract Terms page or not. Possible values are Y and N. This is only used in Procurement Contracts | |
| ENABLE_DELIVERABLES_YN | VARCHAR2 | 1 | Yes | Flag to indicate whether deliverables functionality should be enabled for the document type or not. Possible values are Y and N. This is only used in Procurement Contracts | |
| DOC_VERSION_VIEW | VARCHAR2 | 90 | Database View name for the document versions. This view will be used to render the version poplist in Manage Contract Documents page | ||
| ENABLE_ATTACHMENTS_YN | VARCHAR2 | 1 | Yes | Flag to indicate whether to enable Contract Documents functionality or not. Possible values are Y and N | |
| CREATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who created the row. | |
| CREATION_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the creation of the row. | ||
| LAST_UPDATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who last updated the row. | |
| LAST_UPDATE_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the last update of the row. | ||
| LAST_UPDATE_LOGIN | VARCHAR2 | 32 | Who column: indicates the session login associated to the user who last updated the row. | ||
| EXTERNAL_USERLIST_PROC | VARCHAR2 | 90 | Name of the routine for retrieving external user list on the document to send notifications while managing deliverables. This is only used in Procurement Contracts | ||
| SHOW_IN_LOV_YN | VARCHAR2 | 1 | Flag to indicate whether to show the business document type in business document type LOVs while defining allowable Template Usage. Possible values are Y and N. | ||
| SHOW_IN_WORKBENCH_FLAG | VARCHAR2 | 1 | Flag to indicate whether this document type should be displayed on the Deliverable Workbench or not. Possible values are Y and N. This is only used in Procurement Contracts | ||
| SHOW_PREVIEW_BTN_YN | VARCHAR2 | 1 | Flag to indicate whether to display Preview Contract action on the contract terms page or not. Possible values are Y and N | ||
| TARGET_RESPONSE_DOC_TYPE | VARCHAR2 | 30 | Stores target document type for a given document. For example, Bid is a response document for Auction. This information is used to drive logic in the Copy during response process in Sourcing. | ||
| DISABLE_AMEND_YN | VARCHAR2 | 1 | Flag to indicate whether to enable amendments feature for the business document or not. Possible values are Y and N | ||
| START_DATE | DATE | Document Type effective date. | |||
| END_DATE | DATE | Document Type end date. | |||
| SHOW_AUTH_PARTY_FLAG | VARCHAR2 | 1 | Flag to indicate if the Authoring Party field is relevant to this business document. Default value is `Y`. If set to `N`, the field will be not be displayed in the UI and the value for Authoring Party will be defaulted to `Internal`. | ||
| ENABLE_ATTACHED_DOC_FLAG | VARCHAR2 | 1 | Flag to indicate if Attached Document based contract terms authoring is allowed for this business document. Default value is Y. If set to N, the Contract Source can not be changed to Attached Document for this business document type. | ||
| VARIABLE_RESOLUTION_AM | VARCHAR2 | 255 | Application Module Definition. This will be used to instantiate and resolve the system variables | ||
| MULTIPARTIES_ALLOWED_FLAG | VARCHAR2 | 1 | Flag to indicate whether the Business Document Type Supports Multiparties. | ||
| VARIABLE_RESOLUTION_HEADER_VO | VARCHAR2 | 255 | Header VO. This will be used to resolve the system variable values | ||
| VARIABLE_RESOLUTION_LINES_VO | VARCHAR2 | 255 | Line VO. This will be used to resolve the line system variable values | ||
| SEED_DATA_SOURCE | VARCHAR2 | 512 | Source of seed data record. A value of 'BULK_SEED_DATA_SCRIPT' indicates that record was bulk loaded. Otherwise, specifies the name of the seed data file. | ||
| ORA_SEED_SET1 | VARCHAR2 | 1 | Yes | Oracle internal use only. Indicates the edition-based redefinition (EBR) context of the row for SET1. Context values are Y or N. | |
| ORA_SEED_SET2 | VARCHAR2 | 1 | Yes | Oracle internal use only. Indicates the edition-based redefinition (EBR) context of the row for SET2. Context values are Y or N. |
Foreign Keys
| Table | Foreign Table | Foreign Key Column |
|---|---|---|
| okc_template_usages_h | okc_bus_doc_types_b | DOCUMENT_TYPE |
| okc_doc_qa_lists | okc_bus_doc_types_b | DOCUMENT_TYPE |
| okc_review_upld_header | okc_bus_doc_types_b | DOCUMENT_TYPE |
| okc_template_usages | okc_bus_doc_types_b | DOCUMENT_TYPE |
| okc_allowed_tmpl_usages | okc_bus_doc_types_b | DOCUMENT_TYPE |
| okc_k_variables_h | okc_bus_doc_types_b | DOCUMENT_TYPE |
| okc_k_variables | okc_bus_doc_types_b | DOCUMENT_TYPE |
| okc_variable_doc_types | okc_bus_doc_types_b | DOC_TYPE |
| okc_k_articles_b | okc_bus_doc_types_b | DOCUMENT_TYPE |
| okc_review_upld_terms | okc_bus_doc_types_b | DOCUMENT_TYPE |
| okc_k_articles_b_h | okc_bus_doc_types_b | DOCUMENT_TYPE |
| okc_bus_doc_events | okc_bus_doc_types_b | BUS_DOC_TYPE |
| okc_bus_doc_types_tl | okc_bus_doc_types_b | DOCUMENT_TYPE |
Indexes
| Index | Uniqueness | Tablespace | Columns |
|---|---|---|---|
| OKC_BUS_DOC_TYPES_B_N1 | Non Unique | Default | DOCUMENT_TYPE_CLASS |
| OKC_BUS_DOC_TYPES_B_U1 | Unique | Default | DOCUMENT_TYPE, ORA_SEED_SET1 |
| OKC_BUS_DOC_TYPES_B_U11 | Unique | Default | DOCUMENT_TYPE, ORA_SEED_SET2 |