[Home] [Help] [Dependency Information]
Object Name: | OKS_INSTANCE_HISTORY |
---|---|
Object Type: | TABLE |
Owner: | OKS |
FND Design Data: | OKS.OKS_INSTANCE_HISTORY |
Subobject Name: | |
Status: | VALID |
When any changes to an item instance which affect the associated contracts, are made in Install Base, Oracle Service Contracts is notified.OKS_INSTANCE_HISTORY contains information about the various transactions performed on item instances.This table is used only to display the history of transactions performed on an item instance affecting Contracts.The table is populated when any Contracts, Contract lines are updated or created as a result of changes done to an item instance.When any of the following actions are performed in Order Management and Install Base, Contracts are created or updated and the changes are recorded in this table.
* Warranty and Extended Contracts created when associated instances are interfaced to Install
Base from Sales order.
* Warranty Contracts created when instance is created from Install Base jsp
* RMA transactions performed in Order Management.
* Instance owner ship transfer in Install Base.
* Instance quantity updates, quantity split, instance termination in Install Base.
The text in PARAMTERS is used to identify the parameter values passed by Oracle Install Base API to Oracle Service Contracts API to process the transactions.
Tablespace: | APPS_TS_TX_DATA |
---|---|
PCT Free: | 10 |
PCT Used: |
Index | Type | Uniqueness | Tablespace | Column |
---|---|---|---|---|
OKS_INSTANCE_HISTORY_U1 | NORMAL | UNIQUE | APPS_TS_TX_IDX | ID |
OKS_INSTANCE_HISTORY_N1 | NORMAL | NONUNIQUE | APPS_TS_TX_IDX | REFERENCE_NUMBER |
OKS_INSTANCE_HISTORY_N2 | NORMAL | NONUNIQUE | APPS_TS_TX_IDX | TRANSACTION_TYPE |
OKS_INSTANCE_HISTORY_N3 | NORMAL | NONUNIQUE | APPS_TS_TX_IDX | BATCH_ID |
Name | Datatype | Length | Mandatory | Comments |
---|---|---|---|---|
ID | NUMBER | Yes | Primary key column | |
INSTANCE_ID | NUMBER | Unique ID that identifies an Item Instance (References CSI_ITEM_INSTANCE.INSTANCE_ID) | ||
TRANSACTION_TYPE | VARCHAR2 | (40) | Transaction Type (References FND_LOOKUP.lookup_code with LOOKUP_TYPE='OKS_TRANSACTION_TYPE'). Vakid values: 'TRM' Terminate Instance 'TRF' Transfer of Instance Ownership 'SPL', Instance quantity Split. 'UPD' Update Instance quantity 'RET' Return Instance 'NEW' New Instance 'IDC' Installation date change. | |
TRANSACTION_DATE | DATE | Date when a transaction on an Instance occurred. | ||
REFERENCE_NUMBER | VARCHAR2 | (30) | User key to the item instance number (References CSI_ITEM_INSTANCES.INSTANCE_NUMBER) | |
PARAMETERS | VARCHAR2 | (2000) | List of parameter values passed by Oracle Install Base API to Oracle Service Contracts API is stored as a concatenated string. Service Contracts uses this field to identify the parameter values, passed by Install Base for any transactions performed on an instance, for debugging purpose. | |
CREATED_BY | NUMBER | (15) | Yes | ID of the user whom created the record. |
CREATION_DATE | DATE | Yes | Date the record was created. | |
LAST_UPDATED_BY | NUMBER | (15) | Yes | ID of the last user who updated the record. |
LAST_UPDATE_DATE | DATE | Yes | Date the record was last updated. | |
LAST_UPDATE_LOGIN | NUMBER | (15) | OS ID of the user who last updated the record. | |
OBJECT_VERSION_NUMBER | NUMBER | Yes | Sequential number set at 1 on insert and incremented on update. Used by APIs to ensure current record is passed. | |
SECURITY_GROUP_ID | NUMBER | Used to create a Virtual Private Database which was originally designed to be used by Hosting services. Now obsolete. | ||
BATCH_ID | NUMBER | Foreign key to OKS_BATCH_RULES.BATCH_ID. Identifies the instances updated by a Mass Update batch. |
Cut, paste (and edit) the following text to query this object:
SELECT ID
, INSTANCE_ID
, TRANSACTION_TYPE
, TRANSACTION_DATE
, REFERENCE_NUMBER
, PARAMETERS
, CREATED_BY
, CREATION_DATE
, LAST_UPDATED_BY
, LAST_UPDATE_DATE
, LAST_UPDATE_LOGIN
, OBJECT_VERSION_NUMBER
, SECURITY_GROUP_ID
, BATCH_ID
FROM OKS.OKS_INSTANCE_HISTORY;
OKS.OKS_INSTANCE_HISTORY does not reference any database object
OKS.OKS_INSTANCE_HISTORY is referenced by following:
|
|
|