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: GML.OP_RELS_SCH

Object Details

Object Name:	OP_RELS_SCH
Object Type:	TABLE
Owner:	GML
FND Design Data:	GML.OP_RELS_SCH
Subobject Name:
Status:	VALID

Blanket Sales Order Release Schedules are maintained in this table. A release schedule can be established for a blanket sales order line. Once released, the release schedule line can not be re-released.

Storage Details

Tablespace:	APPS_TS_TX_DATA
PCT Free:	10
PCT Used:

Indexes

Index	Type	Uniqueness	Tablespace	Column
OP_RELS_SCH1_PK	NORMAL	UNIQUE	APPS_TS_TX_IDX	RELEASELINE_ID

Columns

Name	Datatype	Length	Mandatory	Comments
RELEASELINE_ID	NUMBER	(10)	Yes	Primary key; alternate key is presales_ordline_id + release_no.
CONTRACT_ID	NUMBER	(10)	Yes	Contract used to price release line; assumes contract will be effective during period this release line is in use.
SCHED_SHIPDATE	DATE		Yes	Ship date scheduled for this release line.
RELEASE_STATUS	NUMBER	(5)	Yes	Status of this release line. Valid values are: 0 = open/unreleased, 1 = released
REQD_DLVDATE	DATE		Yes	Required date of delivery for this release line.
ORDER_QTY1	NUMBER		Yes	Qty to be released on the order in order_um1. Defaults from standard release qty on blanket order.
ORDER_QTY2	NUMBER			Qty to be released on the order in order_um2.
ORDER_UM1	VARCHAR2	(4)	Yes	Unit of measure for order qty1. User defines in blanket order.
ORDER_UM2	VARCHAR2	(4)		Unit of measure for order qty2. Defaults as item_um2 of this item and can not be modified.
EXPECTED_NET_PRICE	NUMBER		Yes	Price of item; can be zero
FROM_WHSE	VARCHAR2	(4)	Yes	Shipping warehouse for release.
TO_WHSE	VARCHAR2	(4)		Receiving warehouse for release. For intra-enterprise orders.
SHIPADDR_ID	NUMBER	(10)	Yes	If shipping address varies for release line.
SHIP_MTHD	VARCHAR2	(4)	Yes	Ship method
SHIPPER_CODE	VARCHAR2	(4)	Yes	Carrier (shipper) code.
CREATED_BY	NUMBER	(15)	Yes	Standard who column
LAST_UPDATED_BY	NUMBER	(15)	Yes	Standard who column
CREATION_DATE	DATE		Yes	Standard who column
LAST_UPDATE_DATE	DATE		Yes	Standard who column
LAST_UPDATE_LOGIN	NUMBER	(15)		Standard who column
TRANS_CNT	NUMBER	(10)		Not currently used
DELETE_MARK	NUMBER	(5)	Yes	Standard: 0=Active record (default); 1=Marked for (logical) deletion.
TEXT_CODE	NUMBER	(10)		ID which joins any rows of text in this table to the Text Table for this Module
RELEASE_VALUE	NUMBER		Yes	Expected value of release line
RELEASE_NO	NUMBER	(5)	Yes	Release number to uniquely identify a release for a blanket sales order line. System-assigned.
PRESALES_ORDLINE_ID	NUMBER	(10)	Yes	The blanket order (presales order) line to which this release schedule has been established.

Query Text

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


SELECT RELEASELINE_ID
,      CONTRACT_ID
,      SCHED_SHIPDATE
,      RELEASE_STATUS
,      REQD_DLVDATE
,      ORDER_QTY1
,      ORDER_QTY2
,      ORDER_UM1
,      ORDER_UM2
,      EXPECTED_NET_PRICE
,      FROM_WHSE
,      TO_WHSE
,      SHIPADDR_ID
,      SHIP_MTHD
,      SHIPPER_CODE
,      CREATED_BY
,      LAST_UPDATED_BY
,      CREATION_DATE
,      LAST_UPDATE_DATE
,      LAST_UPDATE_LOGIN
,      TRANS_CNT
,      DELETE_MARK
,      TEXT_CODE
,      RELEASE_VALUE
,      RELEASE_NO
,      PRESALES_ORDLINE_ID
FROM GML.OP_RELS_SCH;

Dependencies

[top of page]

GML.OP_RELS_SCH does not reference any database object

GML.OP_RELS_SCH is referenced by following:

GML: OP_RELS_SCH#