eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

DBA Data [Home] [Help] [Dependency Information]

TABLE: OKS.OKS_K_ORDER_DETAILS

Object Details

Object Name:	OKS_K_ORDER_DETAILS
Object Type:	TABLE
Owner:	OKS
FND Design Data:	OKS.OKS_K_ORDER_DETAILS
Subobject Name:
Status:	VALID

OKS_K_ORDER_DETAILS contains information about the merging and renewal rules for each Service order line. The rules indicating if the service ordered should be created as a new Contract or merged into an existing Contract are captured in this table. The service order line can also inherit the rules of another service order line belonging to the same order.
The Contract renewal rules for a new contract created are also defined in this table.
This details can be entered through Contract details form, which can be invoked for a Service Order line, from Sales order form.
Each row includes the service order line id, the order header id, the merge type, the renewal rules, the quote to contact details and the contract information.
When a service order line is interfaced to Contracts, this information is used to create a Contract.
COD_TYPE is used to identify the merge type. It can be defined as one of the following
''NEW'' - To create a new Contract
''LTC'' (Link to Contract) - The Service order line will be merged into an existing contract.
''LTO'' (Link to Order) - The Service order line will inherit the same rules as the order line it is linked to.
LINK_ORDER_LINE_ID field stores the order line id to which the current service order line is linked.
APPLY_ALL_YN field if set to ''Y'', indicates that the rules defined for the current service order line
are applicable to all the order lines of the current order.
When MERGE_TYPE is ''LTC'' (Merge to an existing contract), CHR_ID field stores the Contract ID to which the service order line is merged.
In the case where the MERGE_TYPE is ''NEW'' or ''LTO'' (Link to Order), the CHR_ID field gets updated with the Contract ID of the new Contract, when the Service order line is interfaced to create a Contract.
LINK_ORD_LINE_ID1 field contains the linked order line id and is populated only when the current service order line MERGE_TYPE is ''LTO'' (Link To Order). The Merging/Renewal rules defined for the linked Order line are copied over to the current order line.
LINK_CHR_ID field is populated only for ''LTC'' (Link To Contract) merge type and stores an existing Contract ID. The current service order line will be merged to the contract defined in the field, when interfaced to Contracts.

Storage Details

Tablespace:	APPS_TS_TX_DATA
PCT Free:	10
PCT Used:

Indexes

Index	Type	Uniqueness	Tablespace	Column
OKS_K_ORDER_DETAILS_U1	NORMAL	UNIQUE	APPS_TS_TX_IDX	ID
OKS_K_ORDER_DETAILS_U2	NORMAL	UNIQUE	APPS_TS_TX_IDX	ORDER_LINE_ID1 ORDER_LINE_ID2
OKS_K_ORDER_DETAILS_N1	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	CHR_ID CLE_ID
OKS_K_ORDER_DETAILS_N3	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	LINK_ORD_LINE_ID1
OKS_K_ORDER_DETAILS_N4	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	LINK_ORDER_HEADER_ID

Columns

Name	Datatype	Length	Mandatory	Comments
ID	NUMBER		Yes	Surrogate key used for primary unique identifiers
COD_TYPE	VARCHAR2	(3)	Yes	Merge type identifier. Valid values 'NEW' - To create a new Contract 'LTC' (Link to Contract) - The Service order line will be merged into an existing contract. 'LTO' (Link to Order) - The Service order line will inherit the same rules as the order line it is linked to.
LINK_ORDER_HEADER_ID	NUMBER			The Order header id of the current service order line, for which the Contract details are created (References OE_ORDER_HEADERS_ALL.Header_id)
ORDER_LINE_ID1	VARCHAR2	(40)	Yes	Order line id of the current Service order line, for which the Contract details are created (References OE_ORDER_LINES_ALL.Line_id)
ORDER_LINE_ID2	VARCHAR2	(40)	Yes	Not used
APPLY_ALL_YN	VARCHAR2	(3)	Yes	Determines if the merging rules specified for a Service order line should be applied to all the other service lines within the order (Valid values 'Y','N')
RENEWAL_TYPE	VARCHAR2	(3)		Header Renewal type for the Contract created when the service order line is interfaced to Contracts. (Valid values 'DNR' Do Not Renew, 'EVN' Active Contract, 'NSR' Notify Salesrep, 'SFA' Submit For Approval) (References FND_LOOKUP.lookup_code with LOOKUP_TYPE='OKC_RENEWAL_TYPE'.)
LINE_RENEWAL_TYPE	VARCHAR2	(3)	Yes	Line renewal type of the contract line created when the service order line is interfaced to Contracts. ('FUL' Full Duration, 'KEP 'Keep Duration, 'DNR' Do not renew) References (References FND_LOOKUP.lookup_code with LOOKUP_TYPE='OKC_LINE_RENEWAL_TYPE' )
END_DATE	DATE			End date of the service order line. Used to display the end date in Contract details form
OBJECT_VERSION_NUMBER	NUMBER	(9)	Yes	Sequential number set at 1 on insert and incremented on update. Used by APIs to ensure current record is passed.
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.
PO_REQUIRED_YN	VARCHAR2	(3)		The renewal process will look for PO number at the time of Contract renewal, thus making PO Number mandatory for the renewed contract. This is a flag with valid values of either 'Y' or 'N'. If it is set to 'Y', and If RENEWAL_TYPE = 'ACTIVE', the following is the behaviour of this flag: At the time of renewal, the contract renewal process will look for a renewal PO Number. If it finds a renewal PO Number, it will automatically make the Contract Active otherwise it keeps the Contract in Entered Status. For all types of Renewal including ACTIVE, In the renewed contract, (OKC_K_HEADERS_B.CUST_PO_NUMBER_REQ_YN) PO Required flag gets set to 'Y' automatically.
RENEWAL_PRICING_TYPE	VARCHAR2	(3)		The renewal pricing method of the contract created when the service order line is interfaced to ContractsBased upon the value of this column, the contract price (Total value) is calcualted differently Valid Values are'LST': Makes OKS_K_HEADERS_B.RENEWAL_PRICE_LIST mandatory. OKS_K_HEADERS_B.RENEWAL_PRICE_LIST is used to price the contract at the time of renewal. 'MAN': Contract will not be priced at the time of renewal. User will have to open the renewed contract and manually price it.'PCT': Makes RENEWAL_MARKUP_PERCENT mandatory. At the time of contract renewal, the original contract's value is marked up or down by the percentage value stored in RENEWAL_MARKUP_PERCENT. At the same time, the renewed contract is also priced using price list stored in OKS_K_HEADERS_B.RENEWAL_PRICE_LIST or OKC_K_HEADERS_B.PRICE_LIST_ID. Value of the renewed contract is set to be the minimum of the two Contract values computed as mentioned above
MARKUP_PERCENT	NUMBER			Stores percentage value by which a Contract will be marked up, at the time of renewal.This is required If RENEWAL_PRICING_TYPE is 'PCT'
PRICE_LIST_ID1	VARCHAR2	(40)		Indicates the renewal price list for the Contract created.(References QP_LIST_HEADERS.LIST_HEADER_ID)
PRICE_LIST_ID2	VARCHAR2	(40)		Not used
LINK_ORD_LINE_ID1	VARCHAR2	(40)		Identifies the Order line id to which the current record is linked.(References OE_ORDER_LINES_ALL.LINE_ID)
LINK_ORD_LINE_ID2	VARCHAR2	(40)		Not used
LINK_CHR_ID	NUMBER			Identifies the Contract Header id (references OKC_K_HEADERS_B.ID) to which the service order line has to be merged into, when the merge type is Link to Contract.
LINK_CLE_ID	NUMBER			Not used
CHR_ID	NUMBER			Identifies the Contract created when the service order line is interfaced to Contracts. (References OKC_K_HEADERS_B.ID)
CLE_ID	NUMBER			Not used
COD_ID	NUMBER			Surrogate key used for primary unique identifiers
SECURITY_GROUP_ID	NUMBER			Used to create a Virtual Private Database which was originally designed to be used by Hosting services. Now obsolete.
CONTACT_ID	NUMBER			Holds customer account contact id to which the Quote letter will be sent, at the time of renewal. References HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ROLE_ID
SITE_ID	NUMBER			This column is used to store the Site id associated with Customer Account ID stored in OKS_K_HEADERS_B.QUOTE_TO_CONTACT_ID.. References HZ_CUST_ACCOUNTS.CUST_ACCT_SITE_ID
EMAIL_ID	NUMBER			This column is used to store the email address associated with Customer Account ID stored in OKS_K_HEADERS_B.QUOTE_TO_CONTACT_ID. References HZ_CONTACT_POINTS.CONTACT_POINT_ID where HZ_CONTACT_POINTS.CONTACT_POINT_TYPE = 'EMAIL'.
PHONE_ID	NUMBER			This column is used to store phone number of the contact point. Associated with Customer Account ID stored in OKS_K_HEADERS_B.QUOTE_TO_CONTACT_ID. References HZ_CONTACT_POINTS.CONTACT_POINT_ID Where HZ_CONTACT_POINTS.CONTACT_POINT_ID = 'PHONE'
FAX_ID	NUMBER			This column is used to store phone number of the contact point. Associated with Customer Account ID stored in OKS_K_HEADERS_B.QUOTE_TO_CONTACT_ID. References HZ_CONTACT_POINTS.CONTACT_POINT_ID Where HZ_CONTACT_POINTS.CONTACT_POINT_ID = 'FAX'
BILLING_PROFILE_ID	NUMBER			Unique identifier for specifying the billing profile which will be used at the time of Contract Renewal. References OKS_BILLING_PROFILES_B.ID
RENEWAL_APPROVAL_FLAG	VARCHAR2	(30)		Renewal Approval Flag

Query Text

Cut, paste (and edit) the following text to query this object:


SELECT ID
,      COD_TYPE
,      LINK_ORDER_HEADER_ID
,      ORDER_LINE_ID1
,      ORDER_LINE_ID2
,      APPLY_ALL_YN
,      RENEWAL_TYPE
,      LINE_RENEWAL_TYPE
,      END_DATE
,      OBJECT_VERSION_NUMBER
,      CREATED_BY
,      CREATION_DATE
,      LAST_UPDATED_BY
,      LAST_UPDATE_DATE
,      PO_REQUIRED_YN
,      RENEWAL_PRICING_TYPE
,      MARKUP_PERCENT
,      PRICE_LIST_ID1
,      PRICE_LIST_ID2
,      LINK_ORD_LINE_ID1
,      LINK_ORD_LINE_ID2
,      LINK_CHR_ID
,      LINK_CLE_ID
,      CHR_ID
,      CLE_ID
,      COD_ID
,      SECURITY_GROUP_ID
,      CONTACT_ID
,      SITE_ID
,      EMAIL_ID
,      PHONE_ID
,      FAX_ID
,      BILLING_PROFILE_ID
,      RENEWAL_APPROVAL_FLAG
FROM OKS.OKS_K_ORDER_DETAILS;

Dependencies

[top of page]

OKS.OKS_K_ORDER_DETAILS does not reference any database object

OKS.OKS_K_ORDER_DETAILS is referenced by following:

APPS: OKS_K_ORDER_DETAILS