MSC_ATP_RULES
This table stores rules and options that are used in Available To Promise computation.
Details
-
Schema: FUSION
-
Object owner: MSC
-
Object type: TABLE
-
Tablespace: APPS_TS_TX_DATA
Primary Key
| Name | Columns |
|---|---|
|
MSC_ATP_RULES_PK |
RULE_ID |
Columns
| Name | Datatype | Length | Precision | Not-null | Comments |
|---|---|---|---|---|---|
| RULE_ID | NUMBER | 18 | Yes | Rule identifier for the ATP rule. | |
| SPLIT_ORDER_FLAG | NUMBER | 1 | This column indicates whether order can split whenever first supply becomes available. | ||
| MINIMUM_SPLIT_QUANTITY | NUMBER | This column indicates minimum split quantity. Default value is 1 and applicable only if SPLIT_ORDER_FLAG is enabled. | |||
| ATP_TIME_FENCE | NUMBER | Indicates the number of days from horizon start date during which ATP is preferred over CTP. Outside ATP time fence, CTP is favored over ATP. | |||
| ATP_TIME_FENCE_UD | NUMBER | ATP time fence user defined (days). | |||
| PROFITABLE_TO_PROMISE_CODE | NUMBER | Flag indicates whether profitable to promise code is set. 1-Yes, 2-No. | |||
| SUPPLY_CHAIN_SEARCH_CODE | NUMBER | Supply chain search code specified at the ATP rule. 1-Yes, 2-No. Used in order promising. | |||
| SEARCH_COMPONENTS_CODE | NUMBER | Flag indicating the value of search components code. Make CTP Yes/No. | |||
| INCLUDE_PLANNED_SUPPLY | NUMBER | Indicates whether to include Planned Supply Yes/No | |||
| LEAD_TIME_CODE | NUMBER | Flag indicates whether lead time processing is to be considered. 1-Yes, 2-No. | |||
| LEAD_TIME_TYPE | NUMBER | Type of the lead time defined in ATP rule. | |||
| LEAD_TIME_DAYS_UD | NUMBER | User defined lead time defined in ATP rule. | |||
| ALLOCATED_ATP_CODE | NUMBER | Flag indicates whether Allocated ATP is used (Yes/No). | |||
| SR_INSTANCE_ID | NUMBER | 18 | Yes | Identifier of the source system from where the data is collected. | |
| RULE_NAME | VARCHAR2 | 80 | Yes | Name of the Available to Promise rule. Used in order promising. | |
| LAST_UPDATE_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the last update of the row. | ||
| LAST_UPDATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who last updated the row. | |
| CREATION_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the creation of the row. | ||
| CREATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who created the row. | |
| LAST_UPDATE_LOGIN | VARCHAR2 | 32 | Who column: indicates the session login associated to the user who last updated the row. | ||
| DESCRIPTION | VARCHAR2 | 240 | Description of the available to promise rule | ||
| PAST_DUE_DEMAND_CUTOFF_FENCE | NUMBER | Demand before the specified number of days are not to be considered in ATP computation | |||
| PAST_DUE_SUPPLY_CUTOFF_FENCE | NUMBER | Supplies before the specified number of days are not to be considered in ATP computation | |||
| INFINITE_AVAILABLE_CODE | NUMBER | Infinite availability promising Yes/No | |||
| INFINITE_SUPPLY_FENCE_CODE | NUMBER | Source code for infinite supply time fence | |||
| INFINITE_SUPPLY_TIME_FENCE_UD | NUMBER | Infinite supply time fence days only when user-defined is specified in the time fence code | |||
| ACCEPTABLE_EARLY_FENCE | NUMBER | Identifier for acceptable early fence. | |||
| ACCEPTABLE_LATE_FENCE | NUMBER | Identifier for acceptable late fence. | |||
| DEFAULT_ATP_SOURCES | NUMBER | Indicate which subinventories to use for on-hand quantities | |||
| DEMAND_CLASS_ATP_FLAG | NUMBER | Yes/No flag for ATP computation to consider Demand Class when selecting supply and demand | |||
| INCLUDE_SALES_ORDERS | NUMBER | Yes | Yes/No flag for ATP computation to include demand from sales orders | ||
| INCLUDE_DISCRETE_WIP_DEMAND | NUMBER | Yes/No flag for ATP computation to include demand from WIP discrete jobs | |||
| INCLUDE_DEPENDENT_WIP_DEMAND | NUMBER | Yes/No flag for ATP computation to include demand from dependent WIP jobs | |||
| INCLUDE_REP_WIP_DEMAND | NUMBER | Yes/No flag for ATP computation to include demand from WIP repetitive discrete jobs | |||
| INCLUDE_NONSTD_WIP_DEMAND | NUMBER | Yes/No flag for ATP computation to include demand from WIP non-standard jobs | |||
| INCLUDE_DISCRETE_MPS | NUMBER | Yes/No flag for ATP computation to include supply from discrete MPS schedule | |||
| MPS_DESIGNATOR | VARCHAR2 | 10 | The column is currently not being used. | ||
| INCLUDE_USER_DEFINED_DEMAND | NUMBER | Yes | Yes/No flag for ATP computation to include user defined demand | ||
| USER_ATP_DEMAND_TABLE_NAME | VARCHAR2 | 30 | This column is currently not being used. | ||
| INCLUDE_PURCHASE_ORDERS | NUMBER | Yes | Yes/No flag for ATP computation to include supply from purchase orders | ||
| INCLUDE_DISCRETE_WIP_RECEIPTS | NUMBER | Yes | Yes/No flag for ATP computation to include supply from WIP discrete jobs | ||
| INCLUDE_REP_WIP_RECEIPTS | NUMBER | Yes | Yes/No flag for ATP computation to include supply from WIP repetitive schedule jobs | ||
| INCLUDE_NONSTD_WIP_RECEIPTS | NUMBER | Yes | Yes/No flag for ATP computation to include supply from WIP non-standard jobs | ||
| INCLUDE_INTERORG_TRANSFERS | NUMBER | Yes | Yes/No flag for ATP computation to include supply from inter-organization transfers | ||
| INCLUDE_ONHAND_AVAILABLE | NUMBER | Yes | Yes/No flag for ATP computation to include supply from on-hand inventory | ||
| INCLUDE_USER_DEFINED_SUPPLY | NUMBER | Yes | Yes/No flag for ATP computation to include supply from user defined source | ||
| USER_ATP_SUPPLY_TABLE_NAME | VARCHAR2 | 30 | This column is not being used currently. | ||
| ATTRIBUTE_CATEGORY | VARCHAR2 | 30 | Descriptive Flexfield: structure definition of the user descriptive flexfield. | ||
| ATTRIBUTE1 | VARCHAR2 | 150 | Descriptive Flexfield: segment of the user descriptive flexfield. | ||
| ATTRIBUTE2 | VARCHAR2 | 150 | Descriptive Flexfield: segment of the user descriptive flexfield. | ||
| ATTRIBUTE3 | VARCHAR2 | 150 | Descriptive Flexfield: segment of the user descriptive flexfield. | ||
| ATTRIBUTE4 | VARCHAR2 | 150 | Descriptive Flexfield: segment of the user descriptive flexfield. | ||
| ATTRIBUTE5 | VARCHAR2 | 150 | Descriptive Flexfield: segment of the user descriptive flexfield. | ||
| ATTRIBUTE6 | VARCHAR2 | 150 | Descriptive Flexfield: segment of the user descriptive flexfield. | ||
| ATTRIBUTE7 | VARCHAR2 | 150 | Descriptive Flexfield: segment of the user descriptive flexfield. | ||
| ATTRIBUTE8 | VARCHAR2 | 150 | Descriptive Flexfield: segment of the user descriptive flexfield. | ||
| ATTRIBUTE9 | VARCHAR2 | 150 | Descriptive Flexfield: segment of the user descriptive flexfield. | ||
| ATTRIBUTE10 | VARCHAR2 | 150 | Descriptive Flexfield: segment of the user descriptive flexfield. | ||
| ATTRIBUTE11 | VARCHAR2 | 150 | Descriptive Flexfield: segment of the user descriptive flexfield. | ||
| ATTRIBUTE12 | VARCHAR2 | 150 | Descriptive Flexfield: segment of the user descriptive flexfield. | ||
| ATTRIBUTE13 | VARCHAR2 | 150 | Descriptive Flexfield: segment of the user descriptive flexfield. | ||
| ATTRIBUTE14 | VARCHAR2 | 150 | Descriptive Flexfield: segment of the user descriptive flexfield. | ||
| ATTRIBUTE15 | VARCHAR2 | 150 | Descriptive Flexfield: segment of the user descriptive flexfield. | ||
| ACCUMULATION_WINDOW | NUMBER | Maximum number of days that available supply should be accumulated. Only has impact if accumulate available = Yes | |||
| INCLUDE_REP_MPS | NUMBER | Yes/No flag for ATP computation to include supply from repetitive MPS schedules | |||
| INCLUDE_REQUISITION | NUMBER | Flag indicates whether requisition supplies are valid supplies in ATP check. | |||
| INCLUDE_INTERNAL_REQS | NUMBER | Yes/No flag for ATP computation include from internal requisitions | |||
| INCLUDE_VENDOR_REQS | NUMBER | Identifier to indicate if vendor requisitions to be included. | |||
| INCLUDE_INTERNAL_ORDERS | NUMBER | Yes/No flag for ATP computation to include demand from internal orders | |||
| INCLUDE_FLOW_SCHEDULE_DEMAND | NUMBER | Yes/No flag for ATP computation to include demand from flow schedule | |||
| INCLUDE_FLOW_SCHEDULE_RECEIPTS | NUMBER | Yes/No flag for ATP computation to include supply from repetitive MPS schedules | |||
| AGGREGATE_TIME_FENCE_CODE | NUMBER | Source code for aggregate order promising time fence | |||
| AGGREGATE_TIME_FENCE | NUMBER | Identifier for aggregate time fence days. | |||
| OBJECT_VERSION_NUMBER | NUMBER | 9 | Yes | Used to implement optimistic locking. This number is incremented every time that the row is updated. The number is compared at the start and end of a transaction to detect whether another session has updated the row since it was queried. | |
| THRESHOLD_VALUE | NUMBER | Identifier to indicate the threshold value. | |||
| ATP_UOM | VARCHAR2 | 20 | Indicates the number of days from horizon start date during which ATP is preferred over CTP. Outside ATP time fence, CTP is favored over ATP. | ||
| REFRESH_NUMBER | NUMBER | 18 | Refresh identifier populated by the collection program. | ||
| INCLUDE_PLANNED_DEMAND | NUMBER | Indicates whether to include Planned Demand. | |||
| IS_INDIVISIBLE | NUMBER | Indicates if order quantity is indivisible |
Foreign Keys
| Table | Foreign Table | Foreign Key Column |
|---|---|---|
| msc_atp_assignments | msc_atp_rules | ATP_RULE_ID |
Indexes
| Index | Uniqueness | Tablespace | Columns |
|---|---|---|---|
| MSC_ATP_RULES_U1 | Unique | Default | RULE_ID |
| MSC_ATP_RULES_U2 | Unique | Default | RULE_NAME |