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_SUBSCR_PATTERNS

Object Details

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

Subscription Fulfillment Patterns are used for creating fulfillment schedule. The patterns can be modified to suspend the subscription for certain periods.
The patterns specify the years, months, weeks of the month, days of the week, and days of the month to schedule the subscription item delivery.
Schedule patterns consist of five components - Year, Month, Week, Weekday and Day. For each of these components, user can enter individual values or range of values separated by commas(,). The range is specified with a hyphen between lower and upper bounds. For example, the value 1,3-6,9 in the month component would mean January, March to June and September.
A value of * in any of the component means ''ALL''. For example, a ''*'' in the month field would mean January to December. Allowed values in the year component are in the range of years from the subscription start date to subscription end date. Month component allows values from 1 to 12, Week component from 1 to 5, Weekday component from 1 to 7 and Day component from 1 to 31.
In weekday component 1 stands for Sunday, 2 for Monday and so on till 7 for Saturday.
In patterns for yearly subscriptions only the Year component is allowed. For monthly subscriptions, the components Year and Month are allowed, for weekly subscriptions Year, Month and Week components are allowed and for daily subscriptions all the components are allowed. The combination or Week and Weekday components are mutually exclusive with the Day component. That is, for daily subscriptions, if the user specifies the day component, the week and weekday components will be disabled. Similarly, if the week or weekday component is entered, the day component will be disabled.
Initially when the subscription line is created, the system creates schedule based on the default pattern. The default pattern is ''*'' (meaning ALL) for each of the allowed components. Each subscription line can have multiple fulfillment patterns. Fulfillment schedule will be created for each of these patterns.

Storage Details

Tablespace:	APPS_TS_TX_DATA
PCT Free:	10
PCT Used:

Indexes

Index	Type	Uniqueness	Tablespace	Column
OKS_SUBSCR_PATTERNS_U1	NORMAL	UNIQUE	APPS_TS_TX_IDX	ID

Columns

Name	Datatype	Length	Mandatory	Comments
ID	NUMBER		Yes	Primary identifier.
OSH_ID	NUMBER		Yes	ID of the subscription header with which this subscription pattern is associated. Foreign Key to OKS_SUBSCR_HEADER_B.ID
DNZ_CHR_ID	NUMBER		Yes	Contract ID. Denormalized for performance.
DNZ_CLE_ID	NUMBER			Contract Line ID. Denormalized for performance.
SEQ_NO	NUMBER		Yes	Sequence Number. For future use.
YEAR	VARCHAR2	(240)		Year component of Subscription Pattern
MONTH	VARCHAR2	(240)		Month component of Subscription Pattern
WEEK	VARCHAR2	(240)		Week component of Subscription Pattern
WEEK_DAY	VARCHAR2	(240)		Weekday component of Subscription Pattern
DAY	VARCHAR2	(240)		Day component of Subscription Pattern
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.
LAST_UPDATE_LOGIN	NUMBER	(15)		OS ID of the user who last updated the record.
SECURITY_GROUP_ID	NUMBER			Used to create a Virtual Private Database which was originally designed to be used by Hosting services. Now obsolete.

Query Text

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


SELECT ID
,      OSH_ID
,      DNZ_CHR_ID
,      DNZ_CLE_ID
,      SEQ_NO
,      YEAR
,      MONTH
,      WEEK
,      WEEK_DAY
,      DAY
,      OBJECT_VERSION_NUMBER
,      CREATED_BY
,      CREATION_DATE
,      LAST_UPDATED_BY
,      LAST_UPDATE_DATE
,      LAST_UPDATE_LOGIN
,      SECURITY_GROUP_ID
FROM OKS.OKS_SUBSCR_PATTERNS;

Dependencies

[top of page]

OKS.OKS_SUBSCR_PATTERNS does not reference any database object

OKS.OKS_SUBSCR_PATTERNS is referenced by following:

APPS: OKS_SUBSCR_PATTERNS