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: RLM.RLM_CUST_ITEM_CUM_KEYS_ALL

Object Details

Object Name:	RLM_CUST_ITEM_CUM_KEYS_ALL
Object Type:	TABLE
Owner:	RLM
FND Design Data:	RLM.RLM_CUST_ITEM_CUM_KEYS_ALL
Subobject Name:
Status:	VALID

This table stores the CUM key values associated with a particular ship-to/ship-from/item combination according to the CUM Management rules defined for the trading partners which are supported in Oracle Release Management.

Storage Details

Tablespace:	APPS_TS_TX_DATA
PCT Free:	10
PCT Used:

Indexes

Index	Type	Uniqueness	Tablespace	Column
RLM_CUST_ITEM_CUM_KEYS_U1	NORMAL	UNIQUE	APPS_TS_TX_IDX	CUM_KEY_ID SHIP_FROM_ORG_ID SHIP_TO_ADDRESS_ID BILL_TO_ADDRESS_ID INTRMD_SHIP_TO_ID CUSTOMER_ITEM_ID CUM_START_DATE CUST_RECORD_YEAR PURCHASE_ORDER_NUMBER
RLM_CUST_ITEM_CUM_KEYS_N1	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	CUSTOMER_ITEM_ID SHIP_TO_ADDRESS_ID

Columns

Name	Datatype	Length	Mandatory	Comments
CUM_KEY_ID	NUMBER		Yes	Customer Item cum KEY unique ID
CUSTOMER_ITEM_ID	NUMBER		Yes	Customer Item unique ID. FK to MTL_CUSTOMER_ITEMS
SHIP_TO_ADDRESS_ID	NUMBER			Ship to Address unique ID, if the customer-side CUM Org Level defined for the Ship-from/Ship-to relationship to which this cum key belongs is Ship-to. One of the three address Ids (Ship to, Bill to, or Intermediate Ship to) must be specified
BILL_TO_ADDRESS_ID	NUMBER			Bill to Address unique ID, if the customer-side CUM Org Level defined for the Ship-from/Ship-to relationship to which this cum key belongs is Bill-to. One of the three address Ids (Ship to, Bill to, or Intermediate Ship to must be specified.
INTRMD_SHIP_TO_ID	NUMBER			Intermediate Ship to Address unique ID, if the customer-side CUM Org Level defined for the Ship-from/Ship-to relationship to which this cum key belongs is Intermediate Ship to. One of the three address Ids (Ship to, Bill to, or Intermediate Ship to) must be specified.
SHIP_FROM_ORG_ID	NUMBER			Ship-from organization unique ID. FK to MTL_PARAMETERS. Null only if CUM Org Level is SHIP_TO_ALL_SHIP_FROMS
CUM_START_DATE	DATE			If CUM Management is being done, CUM period start date
CUST_RECORD_YEAR	VARCHAR2	(35)		If CUM management is being done with Record keeping year significance, the specific record keeping year associated with the cum period
ORG_ID	NUMBER			Operating unit unique ID. FK to HR_ORGANIZATION_UNITS.
PURCHASE_ORDER_NUMBER	VARCHAR2	(50)		If CUM management is being done with purchase order significance, the specific PO to which this CUM belongs
CUST_UOM_CODE	VARCHAR2	(3)		Unit of measure used for CUM calculations related to this CUM Key. FK to MTL_UNITS_OF_MEASURE
CUM_QTY	NUMBER			Indicates CUM calculated quantity as per shipment inclusion rule. This column can be used directly, without any further processing, to display current CUM.
CUM_QTY_AFTER_CUTOFF	NUMBER			Indicates all shipments that occurred after cut-off time, which are not included in because of shipment inclusion rules.
CUM_QTY_TO_BE_ACCUMULATED	NUMBER			Indicates all shipments made for this CUM Key, which are not included in CUM_QTY due to shipment inclusion rule and not included in CUM_QTY_AFTER_CUTOFF. This quantity gets added to CUM_QTY on next shipment or next day, depending on the shipment inclusion rule, when LAST_CUM_QTY_UPDATE_DATE is less than the CUM as-of date and time
LAST_CUM_QTY_UPDATE_DATE	DATE			The date/time when CUM_QTY was last updated by shipments and adjustments
LAST_UPDATE_DATE	DATE		Yes	Standard Who column
LAST_UPDATED_BY	NUMBER		Yes	Standard Who column
CREATION_DATE	DATE		Yes	Standard Who column
CREATED_BY	NUMBER		Yes	Standard Who column
ATTRIBUTE_CATEGORY	VARCHAR2	(30)		Descriptive Flexfield context column
ATTRIBUTE1	VARCHAR2	(150)		Descriptive Flexfield segment column
ATTRIBUTE2	VARCHAR2	(150)		Descriptive Flexfield segment column
ATTRIBUTE3	VARCHAR2	(150)		Descriptive Flexfield segment column
ATTRIBUTE4	VARCHAR2	(150)		Descriptive Flexfield segment column
ATTRIBUTE5	VARCHAR2	(150)		Descriptive Flexfield segment column
ATTRIBUTE6	VARCHAR2	(150)		Descriptive Flexfield segment column
ATTRIBUTE7	VARCHAR2	(150)		Descriptive Flexfield segment column
ATTRIBUTE8	VARCHAR2	(150)		Descriptive Flexfield segment column
ATTRIBUTE9	VARCHAR2	(150)		Descriptive Flexfield segment column
ATTRIBUTE10	VARCHAR2	(150)		Descriptive Flexfield segment column
ATTRIBUTE11	VARCHAR2	(150)		Descriptive Flexfield segment column
ATTRIBUTE12	VARCHAR2	(150)		Descriptive Flexfield segment column
ATTRIBUTE13	VARCHAR2	(150)		Descriptive Flexfield segment column
ATTRIBUTE14	VARCHAR2	(150)		Descriptive Flexfield segment column
ATTRIBUTE15	VARCHAR2	(150)		Descriptive Flexfield segment column
LAST_UPDATE_LOGIN	NUMBER			Standard Who column
REQUEST_ID	NUMBER			Standard Who column
PROGRAM_APPLICATION_ID	NUMBER			Standard Who column
PROGRAM_ID	NUMBER			Standard Who column
PROGRAM_UPDATE_DATE	DATE			Standard Who column
TP_ATTRIBUTE1	VARCHAR2	(150)		Trading Partner Flexfield segment column
TP_ATTRIBUTE2	VARCHAR2	(150)		Trading Partner Flexfield segment column
TP_ATTRIBUTE3	VARCHAR2	(150)		Trading Partner Flexfield segment column
TP_ATTRIBUTE4	VARCHAR2	(150)		Trading Partner Flexfield segment column
TP_ATTRIBUTE5	VARCHAR2	(150)		Trading Partner Flexfield segment column
TP_ATTRIBUTE6	VARCHAR2	(150)		Trading Partner Flexfield segment column
TP_ATTRIBUTE7	VARCHAR2	(150)		Trading Partner Flexfield segment column
TP_ATTRIBUTE8	VARCHAR2	(150)		Trading Partner Flexfield segment column
TP_ATTRIBUTE9	VARCHAR2	(150)		Trading Partner Flexfield segment column
TP_ATTRIBUTE10	VARCHAR2	(150)		Trading Partner Flexfield segment column
TP_ATTRIBUTE11	VARCHAR2	(150)		Trading Partner Flexfield segment column
TP_ATTRIBUTE12	VARCHAR2	(150)		Trading Partner Flexfield segment column
TP_ATTRIBUTE13	VARCHAR2	(150)		Trading Partner Flexfield segment column
TP_ATTRIBUTE14	VARCHAR2	(150)		Trading Partner Flexfield segment column
TP_ATTRIBUTE15	VARCHAR2	(150)		Trading Partner Flexfield segment column
TP_ATTRIBUTE_CATEGORY	VARCHAR2	(30)		Trading Partner Flexfield context column
INACTIVE_FLAG	VARCHAR2	(1)		A flag to indicate whether CUM is active.
CUM_NOTE_TEXT	VARCHAR2	(4000)		Comments (or) Reason for inactivating the CUM.

Query Text

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


SELECT CUM_KEY_ID
,      CUSTOMER_ITEM_ID
,      SHIP_TO_ADDRESS_ID
,      BILL_TO_ADDRESS_ID
,      INTRMD_SHIP_TO_ID
,      SHIP_FROM_ORG_ID
,      CUM_START_DATE
,      CUST_RECORD_YEAR
,      ORG_ID
,      PURCHASE_ORDER_NUMBER
,      CUST_UOM_CODE
,      CUM_QTY
,      CUM_QTY_AFTER_CUTOFF
,      CUM_QTY_TO_BE_ACCUMULATED
,      LAST_CUM_QTY_UPDATE_DATE
,      LAST_UPDATE_DATE
,      LAST_UPDATED_BY
,      CREATION_DATE
,      CREATED_BY
,      ATTRIBUTE_CATEGORY
,      ATTRIBUTE1
,      ATTRIBUTE2
,      ATTRIBUTE3
,      ATTRIBUTE4
,      ATTRIBUTE5
,      ATTRIBUTE6
,      ATTRIBUTE7
,      ATTRIBUTE8
,      ATTRIBUTE9
,      ATTRIBUTE10
,      ATTRIBUTE11
,      ATTRIBUTE12
,      ATTRIBUTE13
,      ATTRIBUTE14
,      ATTRIBUTE15
,      LAST_UPDATE_LOGIN
,      REQUEST_ID
,      PROGRAM_APPLICATION_ID
,      PROGRAM_ID
,      PROGRAM_UPDATE_DATE
,      TP_ATTRIBUTE1
,      TP_ATTRIBUTE2
,      TP_ATTRIBUTE3
,      TP_ATTRIBUTE4
,      TP_ATTRIBUTE5
,      TP_ATTRIBUTE6
,      TP_ATTRIBUTE7
,      TP_ATTRIBUTE8
,      TP_ATTRIBUTE9
,      TP_ATTRIBUTE10
,      TP_ATTRIBUTE11
,      TP_ATTRIBUTE12
,      TP_ATTRIBUTE13
,      TP_ATTRIBUTE14
,      TP_ATTRIBUTE15
,      TP_ATTRIBUTE_CATEGORY
,      INACTIVE_FLAG
,      CUM_NOTE_TEXT
FROM RLM.RLM_CUST_ITEM_CUM_KEYS_ALL;

Dependencies

[top of page]

RLM.RLM_CUST_ITEM_CUM_KEYS_ALL does not reference any database object

RLM.RLM_CUST_ITEM_CUM_KEYS_ALL is referenced by following:

RLM: RLM_CUST_ITEM_CUM_KEYS_ALL#