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_SHIPTO_TERMS_ALL

Object Details

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

This table contains new R-12 customer address attributes which are dependent upon the ship-from/ship-to relationship. Some attributes from Phase 1 were carried forward from VEH_RA_ADDRESSES, which is being eliminated in Phase 2.
This table has one row for each ship-from location associated with a ship-to address.

Storage Details

Tablespace:	APPS_TS_TX_DATA
PCT Free:	10
PCT Used:

Indexes

Index	Type	Uniqueness	Tablespace	Column
RLM_CUST_SHIPTO_TERMS_U1	NORMAL	UNIQUE	APPS_TS_TX_IDX	CUSTOMER_ID ADDRESS_ID SHIP_FROM_ORG_ID ORG_ID
RLM_CUST_SHIPTO_TERMS_U2	NORMAL	NONUNIQUE	APPS_TS_TX_IDX	CUST_SHIPTO_TERMS_ID

Columns

Name	Datatype	Length	Mandatory	Comments
CUST_SHIPTO_TERMS_ID	NUMBER		Yes	Customer Ship To Terms unique Identifier
ADDRESS_ID	NUMBER			Ship-To Address unique identifier. FK to RA_ADDRESSES
CUSTOMER_ID	NUMBER			Customer unique identifier. FK to RA_CUSTOMERS
SHIP_FROM_ORG_ID	NUMBER		Yes	Ship-from Organization unique identifier. FK to MTL_PARAMETERS
CUM_CONTROL_CODE	VARCHAR2	(30)	Yes	CUM Management control code. Determines if and how CUM Management is done with this customer address shipments. If CUM Management is done by Purchase Order, the PO number must be included for every item in shipment. If CUM Management is done by Record keeping year, the current Record keeping year must be included in every shipment.. Validated against FND_LOOKUPS.LOOKUP_TYPE = RLM_CUM_CONTROL_CODE
SHIP_METHOD	VARCHAR2	(30)		Unique identifier for the shipment method. FK to MTL_INTERORG_SHIP_METHODS
INTRANSIT_TIME	NUMBER			In-transit Lead Time between ship-from and ship-to locations, based on default ship method and expressed in time UOM
TIME_UOM_CODE	VARCHAR2	(3)		UOM in which in-transit lead time is expressed
SHIP_DELIVERY_RULE_NAME	VARCHAR2	(30)	Yes	Default shipment/delivery rule name for this customer address. FK to RLM_SHIP_DELIVERY_CODES
CUM_CURRENT_RECORD_YEAR	VARCHAR2	(35)		Customer Current Record keeping year code if applicable to CUM_CONTROL_CODE value. It will be attached to all items on ASNs to this destination
CUM_PREVIOUS_RECORD_YEAR	VARCHAR2	(240)		Customer Previous Record keeping year code if applicable to CUM_CONTROL_CODE value. It will be attached to all items on ASNs to this destination
CUM_CURRENT_START_DATE	DATE			Current CUM calculation starting date if applicable to CUM_CONTROL_CODE value. It will be attached to all items on ASNs to this destination.
CUM_PREVIOUS_START_DATE	DATE			Previous CUM calculation starting date if applicable to CUM_CONTROL_CODE value. To be used in building the CUM key if shipment date is earlier than Current CUM calculation starting date
CUM_ORG_LEVEL_CODE	VARCHAR2	(30)		If CUM Management is on, is the business entity levels at which the cum is calculated between the customer and supplier. Validated against FND_LOOKUPS.LOOKUP_TYPE = RLM_CUM_ORG_LEVEL
CUM_SHIPMENT_RULE_CODE	VARCHAR2	(30)		If CUM Management is on, this specifies the most recent shipment which should be included in CUM: current, last, or yesterday's shipment. Validated against FND_LOOKUPS.LOOKUP_TYPE = RLM_CUM_SHIPMENT_RULE
CUM_YESTERD_TIME_CUTOFF	NUMBER			If CUM Management is on, and yesterday's shipment. is the last shipment to include, this is the cutoff time for yesterday's shipments to be included
CUST_ASSIGN_SUPPLIER_CD	VARCHAR2	(35)		The code the customer uses to identify you as a supplier, transmitted by the customer in the N1 segment
CUSTOMER_RCV_CALENDAR_CD	VARCHAR2	(10)		Customer receiving calendar code. Used in conjunction with the supplier shipment calendar code. If populated, the Demand Stream Processor will use this calendar when applying ship/delivery pattern rules to ensure the customer site is open for receiving on a calculated shipment arrival date. FK to BOM_CALENDARS
FREIGHT_CODE	VARCHAR2	(25)		Default freight code, to be used by the demand processor to populate the freight carrier on the inbound demand. This can be defaulted from the profile option RLM_default_carrier. FK to ORG_FREIGHT
SUPPLIER_SHP_CALENDAR_CD	VARCHAR2	(10)		Supplier shipping calendar code. If populated, the Demand Stream Processor will use this calendar when applying ship/delivery pattern rules and lead time offsets to ensure the supplier site is available for shipping on calculated scheduled shipment date. FK to BOM_CALENDARS
UNSHIP_FIRM_CUTOFF_DAYS	NUMBER			If UNSHIPPED_FIRM_DISP_CD = DELETE_AFTER_N_DAYS, the number of days before the current date where the requirement is eligible for cancellation.
UNSHIPPED_FIRM_DISP_CD	VARCHAR2	(30)		Indicates disposition of old unshipped firm demand when the Demand Stream Processor has new immediate firm demand, since this type of demand cannot be accurately matched by date/quantity. Validated against FND_LOOKUPS.LOOKUP_TYPE = RLM_FIRM_DISP_CODE
USE_EDI_SDP_CODE_FLAG	VARCHAR2	(1)	Yes	Flag that indicates whether you want to used the ship delivery pattern code that the customer sends in on the EDI transactions, if it is populated
DEMAND_TOLERANCE_ABOVE	NUMBER			Positive tolerance (high end) for changes to Customer Item demand
DEMAND_TOLERANCE_BELOW	NUMBER			Negative tolerance (low end) for changes to Customer Item demand
INACTIVE_DATE	DATE			Date when this ship from/ship to terms relationship is no longer active
HEADER_ID	NUMBER			Unique identifier of the default sales order to which the customer item is linked. Demand for items is placed on this sales order by the Release Management demand processor unless a different SO is specified at the ship-from customer item level. It will be cleared if the Sales Order is purged. FK to OE_ORDER_HEADERS
ORG_ID	NUMBER			Operating unit unique ID. FK to HR_ORGANIZATION_UNITS
PRICE_LIST_ID	NUMBER			Unique identifier for default price list associated with this ship-from/ship-to relationship if pricing agreement contract is not used. FK to OE_PRICE_LISTS
CRITICAL_ATTRIBUTE_KEY	VARCHAR2	(80)		ASCII string of characters which identify the optional matching attributes which are enabled as critical attributes, which must contain a value for the Demand Processor. An exception (warning) will be generated if one of these is missing on Firm demand.
CUSTOMER_CONTACT_ID	NUMBER			Customer Contact. FK to RA_CONTACTS
PLN_FIRM_DAY_FROM	NUMBER			First day from the Planning Schedule horizon start date from which demand will be considered Firm (Shippable).
PLN_FIRM_DAY_TO	NUMBER			Last day from the Planning Schedule horizon start date to which demand will be considered Firm (Shippable).
PLN_FORECAST_DAY_FROM	NUMBER			First day from the Planning Schedule horizon start date from which demand will be considered Forecast to Order Management.
PLN_FORECAST_DAY_TO	NUMBER			Last day from the Planning Schedule horizon start date to which demand will be considered Forecast to Order Management.
PLN_FROZEN_DAY_TO	NUMBER			Last day from the Planning Schedule horizon start date to which demand will be considered Frozen (cannot be changed).
PLN_FROZEN_DAY_FROM	NUMBER			First day from the Planning Schedule horizon start date from which demand will be considered Frozen (cannot be changed).
SEQ_FIRM_DAY_FROM	NUMBER			First day from the Sequenced Schedule horizon start date from which demand will be considered Firm (Shippable) .
SEQ_FIRM_DAY_TO	NUMBER			Last day from the Sequenced Schedule horizon start date to which demand will be considered Firm (Shippable).
SEQ_FORECAST_DAY_TO	NUMBER			Last day from the Sequenced Schedule horizon start date to which demand will be considered Forecast to Order Management.
SEQ_FORECAST_DAY_FROM	NUMBER			First day from the Sequenced Schedule horizon start date from which demand will be considered Forecast to Order Management.
SEQ_FROZEN_DAY_FROM	NUMBER			First day from the Sequenced Schedule horizon start date from which demand will be considered Frozen (cannot be changed)
SEQ_FROZEN_DAY_TO	NUMBER			Last day from the Sequenced Schedule horizon start date to which demand will be considered Frozen (cannot be changed)
SHP_FIRM_DAY_FROM	NUMBER			First day from the Shipping Schedule horizon start date from which demand will be considered Firm (Shippable).
SHP_FIRM_DAY_TO	NUMBER			Last day from the Shipping Schedule horizon start date to which demand will be considered Firm (Shippable) .
SHP_FROZEN_DAY_TO	NUMBER			Last day from the Shipping Schedule horizon start date to which demand will be considered Frozen (cannot be changed).
SHP_FROZEN_DAY_FROM	NUMBER			First day from the Shipping Schedule horizon start date from which demand will be considered Frozen (cannot be changed).
SHP_FORECAST_DAY_TO	NUMBER			Last day from the Shipping Schedule horizon start date to which demand will be considered Forecast to Order Management.
ROUND_TO_STD_PACK_FLAG	VARCHAR2	(1)		Indicates whether requirements should be rounded up.
SUPPLIER_CONTACT_ID	NUMBER			Supplier Contact. FK to PER_PEOPLE_F.
AGREEMENT_NAME	VARCHAR2	(240)		The default Pricing Agreement contract associated with this ship-from/ship-to relationship. The Demand Processor will use this to determine Customer PO Number and pricing unless a different Pricing Agreement is specified at the ship-from customer item level. FK to OE_AGREEMENTS.
STD_PACK_QTY	NUMBER			If the requirements should be rounded up to standard packs in the Demand Processor, the quantity per pack expressed in the customer UOM.
FUTURE_AGREEMENT_NAME	VARCHAR2	(240)		The future default Pricing Agreement contract associated with this ship-from/ship-to relationship to be used when the current Pricing Agreement expires. The Demand Processor will use this to determine Customer PO Number and pricing if demand is dated after the expiration date of the current Pricing Agreement unless a different future Pricing Agreement is specified at the ship-from customer item level. FK to OE_AGREEMENTS.
SHP_FORECAST_DAY_FROM	NUMBER			First day from the Shipping Schedule horizon start date from which demand will be considered Forecast to Order Management
SCHEDULE_HIERARCHY_CODE	VARCHAR2	(240)		Hierarchy of schedule types for demand consumption from PLN/SHP/SEQ schedule. Validated against FND_LOOKUPS.LOOKUP_TYPE = RLM_SCHEDULE_HIERARCHY. Mandatory at Customer level
COMMENTS	VARCHAR2	(240)		Comments related to the Organization relationship to the Customer, Ship-To Address, or Customer Item. Optional at all levels.
LAST_UPDATED_BY	NUMBER		Yes	Standard Who column
LAST_UPDATE_DATE	DATE		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
MATCH_ACROSS_KEY	VARCHAR2	(240)		ASCII string of characters which identify the enabled optional demand matching attributes when demand from different schedule types is being compared. The ASCII character assigned to the matching column is stored in FND_LOOKUPS.LOOKUP_CODE after the comma delimiter.
MATCH_WITHIN_KEY	VARCHAR2	(240)		ASCII string of characters which identify the enabled optional demand matching attributes when demand from the same schedule type is being compared. The ASCII character assigned to the matching column is stored in FND_LOOKUPS.LOOKUP_CODE after the comma delimiter.
PLN_MRP_FORECAST_DAY_FROM	NUMBER			First day from Planning Schedule horizon start date from which the demand is considered forecast to MRP.
PLN_MRP_FORECAST_DAY_TO	NUMBER			Last day from Planning Schedule horizon start date to which the demand is considered forecast to MRP.
SHP_MRP_FORECAST_DAY_FROM	NUMBER			First day from Shipping Schedule horizon start date from which the demand is considered forecast to MRP.
SHP_MRP_FORECAST_DAY_TO	NUMBER			Last day from Shipping Schedule horizon start date to which the demand is considered forecast to MRP.
SEQ_MRP_FORECAST_DAY_FROM	NUMBER			First day from Sequenced Schedule horizon start date from which the demand is considered forecast to MRP.
SEQ_MRP_FORECAST_DAY_TO	NUMBER			Last day from Sequenced Schedule horizon start date to which the demand is considered forecast to MRP.
INTRANSIT_CALC_BASIS	VARCHAR2	(15)		Used to determine whether receipt or shipment info. should be used to calculate intransit quantities.
DEFAULT_SHIP_FROM	VARCHAR2	(1)		Used to designate a default processing rule when multiple Ship-From Organizations exist at customer or address level setup
PLN_FROZEN_FLAG	VARCHAR2	(1)		If this field is set to Y, the Demand Stream Processor rolls forward the dates on the incoming planning schedule to a non-frozen bucket.
SHP_FROZEN_FLAG	VARCHAR2	(1)		If this field is set to Y, the Demand Stream Processor rolls forward the dates on the incoming shipping schedule to a non-frozen bucket.
SEQ_FROZEN_FLAG	VARCHAR2	(1)		If this field is set to Y, the Demand Stream Processor rolls forward the dates on the incoming sequenced schedule to a non-frozen bucket.
ISSUE_WARNING_DROP_PARTS_FLAG	VARCHAR2	(1)		For future use
BLANKET_NUMBER	NUMBER			Blanket Sales Agreement
RELEASE_RULE	VARCHAR2	(2)		Release Rule
RELEASE_TIME_FRAME	NUMBER			Release Time Frame
RELEASE_TIME_FRAME_UOM	VARCHAR2	(3)		Release Time Frame UOM
AGREEMENT_ID	NUMBER			Stores the agreement_id of the Pricing Agreement contract with the customer. The Demand Stream Processor will use this to determine Customer PO Number and pricing. FK to OE_AGREEMENTS.
FUTURE_AGREEMENT_ID	NUMBER			Stores the agreement_id of future Pricing Agreement contract with the customer to be used when the current Pricing Agreement expires. The Demand Stream Processor will use this to determine Customer PO Number and pricing . FK to OE_AGREEMENTS.
EXCLUDE_NON_WORKDAYS_FLAG	VARCHAR2	(1)		Stores the Value for Option to Exclude Non-workdays from Intransit Time Calculations
DISABLE_CREATE_CUM_KEY_FLAG	VARCHAR2	(1)		Stores the Value for Option to Disable Auto-creation of CUM keys

Query Text

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


SELECT CUST_SHIPTO_TERMS_ID
,      ADDRESS_ID
,      CUSTOMER_ID
,      SHIP_FROM_ORG_ID
,      CUM_CONTROL_CODE
,      SHIP_METHOD
,      INTRANSIT_TIME
,      TIME_UOM_CODE
,      SHIP_DELIVERY_RULE_NAME
,      CUM_CURRENT_RECORD_YEAR
,      CUM_PREVIOUS_RECORD_YEAR
,      CUM_CURRENT_START_DATE
,      CUM_PREVIOUS_START_DATE
,      CUM_ORG_LEVEL_CODE
,      CUM_SHIPMENT_RULE_CODE
,      CUM_YESTERD_TIME_CUTOFF
,      CUST_ASSIGN_SUPPLIER_CD
,      CUSTOMER_RCV_CALENDAR_CD
,      FREIGHT_CODE
,      SUPPLIER_SHP_CALENDAR_CD
,      UNSHIP_FIRM_CUTOFF_DAYS
,      UNSHIPPED_FIRM_DISP_CD
,      USE_EDI_SDP_CODE_FLAG
,      DEMAND_TOLERANCE_ABOVE
,      DEMAND_TOLERANCE_BELOW
,      INACTIVE_DATE
,      HEADER_ID
,      ORG_ID
,      PRICE_LIST_ID
,      CRITICAL_ATTRIBUTE_KEY
,      CUSTOMER_CONTACT_ID
,      PLN_FIRM_DAY_FROM
,      PLN_FIRM_DAY_TO
,      PLN_FORECAST_DAY_FROM
,      PLN_FORECAST_DAY_TO
,      PLN_FROZEN_DAY_TO
,      PLN_FROZEN_DAY_FROM
,      SEQ_FIRM_DAY_FROM
,      SEQ_FIRM_DAY_TO
,      SEQ_FORECAST_DAY_TO
,      SEQ_FORECAST_DAY_FROM
,      SEQ_FROZEN_DAY_FROM
,      SEQ_FROZEN_DAY_TO
,      SHP_FIRM_DAY_FROM
,      SHP_FIRM_DAY_TO
,      SHP_FROZEN_DAY_TO
,      SHP_FROZEN_DAY_FROM
,      SHP_FORECAST_DAY_TO
,      ROUND_TO_STD_PACK_FLAG
,      SUPPLIER_CONTACT_ID
,      AGREEMENT_NAME
,      STD_PACK_QTY
,      FUTURE_AGREEMENT_NAME
,      SHP_FORECAST_DAY_FROM
,      SCHEDULE_HIERARCHY_CODE
,      COMMENTS
,      LAST_UPDATED_BY
,      LAST_UPDATE_DATE
,      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
,      MATCH_ACROSS_KEY
,      MATCH_WITHIN_KEY
,      PLN_MRP_FORECAST_DAY_FROM
,      PLN_MRP_FORECAST_DAY_TO
,      SHP_MRP_FORECAST_DAY_FROM
,      SHP_MRP_FORECAST_DAY_TO
,      SEQ_MRP_FORECAST_DAY_FROM
,      SEQ_MRP_FORECAST_DAY_TO
,      INTRANSIT_CALC_BASIS
,      DEFAULT_SHIP_FROM
,      PLN_FROZEN_FLAG
,      SHP_FROZEN_FLAG
,      SEQ_FROZEN_FLAG
,      ISSUE_WARNING_DROP_PARTS_FLAG
,      BLANKET_NUMBER
,      RELEASE_RULE
,      RELEASE_TIME_FRAME
,      RELEASE_TIME_FRAME_UOM
,      AGREEMENT_ID
,      FUTURE_AGREEMENT_ID
,      EXCLUDE_NON_WORKDAYS_FLAG
,      DISABLE_CREATE_CUM_KEY_FLAG
FROM RLM.RLM_CUST_SHIPTO_TERMS_ALL;

Dependencies

[top of page]

RLM.RLM_CUST_SHIPTO_TERMS_ALL does not reference any database object

RLM.RLM_CUST_SHIPTO_TERMS_ALL is referenced by following:

APPS: RLM_CUST_SHIPTO_TERMS; RLM_CUST_SHIPTO_TERMS_ALL