MSC_ST_CALENDAR_ASSIGNMENTS
This table keeps the association between trading partners and calendars
Details
-
Schema: FUSION
-
Object owner: MSC
-
Object type: TABLE
-
Tablespace: INTERFACE
Columns
Name | Datatype | Length | Not-null | Comments |
---|---|---|---|---|
ASSOCIATION_TYPE | NUMBER | 1 - VENDOR 2 - CUSTOMER 3 - ORGANIZATION 4 - CARRIER 5 - VENDOR_SITE 6 - CUSTOMER_SITE 7 - CARRIER_VENDOR 8 - CARRIER_CUSTOMER 9 - CARRIER_ORGANIZATION 10 - CARRIER_VENDOR_SITE 11 - CARRIER_CUSTOMER_SITE | ||
CALENDAR_CODE | VARCHAR2 | 22 | CALENDAR_CODE of the given Calendar | |
CALENDAR_TYPE | VARCHAR2 | 10 | Type of the calendar. RECEIVING, SHIPPING, CARRIER | |
PARTNER_ID | NUMBER | This value indicates the trading partner identifier generated during planning collections. | ||
PARTNER_SITE_ID | NUMBER | FK to msc_trading_partner_sites | ||
ORGANIZATION_ID | NUMBER | This column indicates the organization identifier. | ||
SR_INSTANCE_ID | NUMBER | Source application instance identifier | ||
CARRIER_PARTNER_ID | NUMBER | FK to msc_trading_partners.partner_id | ||
PARTNER_TYPE | NUMBER | 1 - Supplier 2 - Customer 3 - Organization 4 - Carrier | ||
ASSOCIATION_LEVEL | NUMBER | 1 - CARRIER_VENDOR_SITE, CARRIER_CUSTOMER_SITE 2 - CARRIER_VENDOR, CARRIER_CUSTOMER, CARRIER_ORGANIZATION 3 - VENDOR_SITE, CUSTOMER_SITE 4 - VENDOR, CUSTOMER, ORGANIZATION, CARRIER | ||
SHIP_METHOD_CODE | VARCHAR2 | 30 | Ship Method Code (eg: UPS-2ndday-Air) | |
SERVICE_LEVEL | VARCHAR2 | 100 | Service level specified in the shipping method. | |
MODE_OF_TRANSPORT | VARCHAR2 | 80 | This value indicates Mode of transport specified in the shipping method. | |
REFRESH_NUMBER | NUMBER | Refresh number populated by the collection | ||
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. | |
PARTNER_NAME | VARCHAR2 | 360 | Trading partner(supplier/customer/carrier) name collected from source system. | |
PARTNER_SITE_CODE | VARCHAR2 | 240 | This value indicates the partner site code for the supplier/customer. | |
ORGANIZATION_CODE | VARCHAR2 | 18 | This value indicates Organization Code | |
SR_INSTANCE_CODE | VARCHAR2 | 30 | The value indicates the source system code from where the data is collected. | |
COMPANY_NAME | VARCHAR2 | 255 | Party name with which the company is registered. | |
BATCH_ID | NUMBER | Batch identifier generated during processing | ||
PROCESS_FLAG | NUMBER | Processing Flag indicating the status of records during pre-processing. 1- Complete Record, 2- Error Record, 3- Warning Record, 4- Retry Record, 5- New Record. | ||
ST_TRANSACTION_ID | NUMBER | Transaction id generated during pre-processing to uniquely identify a record in staging table | ||
DATA_SOURCE_TYPE | VARCHAR2 | 15 | Source type indicating the source of records | |
DELETED_FLAG | NUMBER | Yes/No flag indicates whether corresponding record in ODS will be deleted | ||
CARRIER_PARTNER_CODE | VARCHAR2 | 360 | Name of the carrier to which calendar is assigned. | |
MESSAGE_ID | NUMBER | This value indicates Message id | ||
ERROR_TEXT | VARCHAR2 | 2000 | Error text for functional validation errors in the record | |
RETRY_COUNT | NUMBER | Number of retries to process failed records. | ||
ERROR_CODE | VARCHAR2 | 150 | Error code for functional validation errors in the record | |
CUST_ACCOUNT_NUMBER | VARCHAR2 | 30 | Account number associated to the customer | |
PARTY_SITE_NUMBER | VARCHAR2 | 30 | Unique party site number generated on the source system for the trading partner site. | |
OPERATION_TYPE | VARCHAR2 | 2 | This value indicates Operation type. | |
LOAD_REQUEST_ID | NUMBER | It Stores the Request ID of Job that loaded the data. |