MSC_ST_ATP_RULES
The staging table used by the collection program to validate and process data for table MSC_ST_ATP_RULES.
Details
-
Schema: FUSION
-
Object owner: MSC
-
Object type: TABLE
-
Tablespace: INTERFACE
Columns
| Name | Datatype | Length | Precision | Not-null | Comments |
|---|---|---|---|---|---|
| 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). | |||
| CREATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who created the row. | |
| CREATION_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the creation of the row. | ||
| DESCRIPTION | VARCHAR2 | 240 | Description of the available to promise rule | ||
| INCLUDE_DEPENDENT_WIP_DEMAND | NUMBER | Yes/No flag for ATP computation to include demand from dependent WIP jobs | |||
| INCLUDE_DISCRETE_WIP_DEMAND | NUMBER | Yes/No flag for ATP computation to include demand from WIP discrete jobs | |||
| INCLUDE_DISCRETE_WIP_RECEIPTS | NUMBER | Yes/No flag for ATP computation to include supply from WIP discrete jobs | |||
| INCLUDE_INTERNAL_REQS | NUMBER | Yes/No flag for ATP computation include from internal requisitions | |||
| INCLUDE_INTERORG_TRANSFERS | NUMBER | Yes/No flag for ATP computation to include supply from inter-organization transfers | |||
| INCLUDE_NONSTD_WIP_RECEIPTS | NUMBER | Yes/No flag for ATP computation to include supply from WIP non-standard jobs | |||
| INCLUDE_ONHAND_AVAILABLE | NUMBER | 1 | Yes/No flag for ATP computation to include supply from on-hand inventory | ||
| INCLUDE_PLANNED_SUPPLY | NUMBER | 1 | Indicates whether to include Planned Supply Yes/No | ||
| INCLUDE_PURCHASE_ORDERS | NUMBER | 1 | Yes/No flag for ATP computation to include supply from purchase orders | ||
| INCLUDE_REQUISITION | NUMBER | 1 | Flag indicates whether requisition supplies are valid supplies in ATP check. | ||
| INCLUDE_SALES_ORDERS | NUMBER | 1 | Yes/No flag for ATP computation to include demand from sales orders | ||
| INCLUDE_USER_DEFINED_DEMAND | NUMBER | 1 | Yes/No flag for ATP computation to include user defined demand | ||
| INCLUDE_USER_DEFINED_SUPPLY | NUMBER | Yes/No flag for ATP computation to include supply from user defined source | |||
| INFINITE_AVAILABLE_CODE | NUMBER | 1 | Infinite availability promising Yes/No | ||
| INFINITE_SUPPLY_FENCE_CODE | NUMBER | 1 | 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 | |||
| LAST_UPDATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who last updated the row. | |
| LAST_UPDATE_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the last update of the row. | ||
| LAST_UPDATE_LOGIN | VARCHAR2 | 32 | Who column: indicates the session login associated to the user who last updated the row. | ||
| LEAD_TIME_CODE | NUMBER | 1 | Flag indicates whether lead time processing is to be considered. 1-Yes, 2-No. | ||
| LEAD_TIME_DAYS_UD | NUMBER | User defined lead time defined in ATP rule. | |||
| LEAD_TIME_TYPE | NUMBER | 1 | Type of the lead time defined in ATP 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 | |||
| PROFITABLE_TO_PROMISE_CODE | NUMBER | Flag indicates whether profitable to promise code is set. 1-Yes, 2-No. | |||
| RULE_NAME | VARCHAR2 | 80 | Name of the Available to Promise rule. Used in order promising. | ||
| SEARCH_COMPONENTS_CODE | NUMBER | 1 | Flag indicating the value of search components code. Make CTP Yes/No. | ||
| SR_INSTANCE_CODE | VARCHAR2 | 30 | The value indicates the source system code from where the data is collected. | ||
| SUPPLY_CHAIN_SEARCH_CODE | NUMBER | 1 | Supply chain search code specified at the ATP rule. 1-Yes, 2-No. Used in order promising. | ||
| REFRESH_NUMBER | NUMBER | Refresh identifier populated by the collection program | |||
| PROCESS_FLAG | NUMBER | Processing Flag indicating the status of records during pre-processing. 1-Compete Record, 2- Error Record, 3- Warning Record, 4- Retry Record, 5- New Record. | |||
| ERROR_TEXT | VARCHAR2 | 2000 | This will describe the reason for the error if any. | ||
| ERROR_CODE | VARCHAR2 | 150 | Error code for functional validation errors in the record | ||
| DELETED_FLAG | NUMBER | Flag that indicates if the record should be deleted in collections | |||
| LOAD_REQUEST_ID | NUMBER | Contains the request id of job that loaded the data. | |||
| ALLOCATED_ATP_CODE | NUMBER | Flag indicates whether Allocated ATP is used (Yes/No). | |||
| INCLUDE_REP_WIP_RECEIPTS | NUMBER | Yes/No flag for ATP computation to include supply from WIP repetitive schedule jobs | |||
| IS_INDIVISIBLE | NUMBER | Indicates if order quantity is indivisible | |||
| 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. | |||
| INCLUDE_PLANNED_DEMAND | NUMBER | 1 | Indicates whether or not to include Planned Demand. The valid values are 1 (Yes) and 2 (No). |