Table Detail Report
BR_SCHED_APPT_TYPE_ORD
Column Section | Top of Page |
Table-level Detail
Description: | Bedrock Scheduling Appointment Type Order |
Definition: | Hold orders for appointment types that are orders based |
Table Type: | REFERENCE |
Column Detail - BR_SCHED_APPT_TYPE_ORD
Column Name | Type | Null? | Definition |
---|---|---|---|
ACTIVITY_SUBTYPE_CD | DOUBLE | N | Activity subtype of the default orders the department type can be scheduled for |
ACTIVITY_TYPE_CD | DOUBLE | N | Activity type of the default orders the department type can be scheduled for |
APPT_TYPE_ID | DOUBLE | N | identifier of the appointment type |
BR_CLIENT_ID | DOUBLE | N | Identifies which bedrock client data belongs to |
CATALOG_TYPE_CD | DOUBLE | N | Catalog type of the default orders the department type can be scheduled for |
CONCEPT_CKI | VARCHAR(255) | N | Concept_cki to link the order to order_catalog table |
DURATION | DOUBLE | Y | number to define the duration on sch_order_duration when the appointment type/order relationship is created |
PRIMARY_MNEMONIC | VARCHAR(100) | Y | Description of the order |
UPDT_APPLCTX | DOUBLE | N | The application context number from the record info block. |
UPDT_CNT | DOUBLE | N | Set to 0 on insert. Incremented by 1 on update. Used to recognize update conflict where data in a row updated by one application is at risk of being lost by a second application attempting to update the row. |
UPDT_DT_TM | DATETIME | N | The date and time the row was last inserted or updated. |
UPDT_ID | DOUBLE | N | The person_id of the person from the personnel table (prsnl) that caused the last insert or update of the row in the table. |
UPDT_TASK | DOUBLE | N | The registered (assigned) task number for the process that inserted or updated the row. |
BR_SCHED_DEPT
Column Section | Top of Page |
Table-level Detail
Description: | Bedrock Schedule Department |
Definition: | Stores scheduling departments with its prefix and department type. |
Table Type: | REFERENCE |
Column Detail - BR_SCHED_DEPT
Column Name | Type | Null? | Definition |
---|---|---|---|
BR_CLIENT_ID | DOUBLE | N | Identifies which bedrock client data belongs to |
DEPT_PREFIX | VARCHAR(4) | Y | 4 character prefix for department |
DEPT_TYPE_ID | DOUBLE | N | ID of associated department type from br_sched_dept_type table |
LOCATION_CD | DOUBLE | N | Code value of the department |
START_VERSION_NBR | DOUBLE | Y | Identifies which version of start has been loaded |
UPDT_APPLCTX | DOUBLE | N | The application context number from the record info block. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
UPDT_CNT | DOUBLE | N | Set to 0 on insert. Incremented by 1 on update. Used to recognize update conflict where data in a row updated by one application is at risk of being lost by a second application attempting to update the row. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
UPDT_DT_TM | DATETIME | N | The date and time the row was last inserted or updated. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
UPDT_ID | DOUBLE | N | The person_id of the person from the personnel table (prsnl) that caused the last insert or update of the row in the table. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
UPDT_TASK | DOUBLE | N | The registered (assigned) task number for the process that inserted or updated the row. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
BR_SCHED_DEPT_ORD_R
Column Section | Top of Page |
Table-level Detail
Description: | Bedrock Schedule Department Order R |
Definition: | Stores relationship between departments and the order types they can be scheduled for |
Table Type: | REFERENCE |
Column Detail - BR_SCHED_DEPT_ORD_R
Column Name | Type | Null? | Definition |
---|---|---|---|
ACTIVITY_SUBTYPE_CD | DOUBLE | N | Activity subtype of the orders the department can be scheduled for |
ACTIVITY_TYPE_CD | DOUBLE | N | Activity type of the orders the department can be scheduled for |
BR_CLIENT_ID | DOUBLE | N | Identifies which bedrock client data belongs to |
CATALOG_TYPE_CD | DOUBLE | N | Catalog type of the orders the department can be scheduled for |
LOCATION_CD | DOUBLE | N | Code value of the department |
START_VERSION_NBR | DOUBLE | Y | Identifies which version of start has been loaded |
UPDT_APPLCTX | DOUBLE | N | The application context number from the record info block. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
UPDT_CNT | DOUBLE | N | Set to 0 on insert. Incremented by 1 on update. Used to recognize update conflict where data in a row updated by one application is at risk of being lost by a second application attempting to update the row. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
UPDT_DT_TM | DATETIME | N | The date and time the row was last inserted or updated. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
UPDT_ID | DOUBLE | N | The person_id of the person from the personnel table (prsnl) that caused the last insert or update of the row in the table. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
UPDT_TASK | DOUBLE | N | The registered (assigned) task number for the process that inserted or updated the row. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
BR_SCHED_DEPT_TYPE
Column Section | Top of Page |
Table-level Detail
Description: | Bedrock Schedule Department Type |
Definition: | Stores default bedrock scheduling department types. |
Table Type: | REFERENCE |
Column Detail - BR_SCHED_DEPT_TYPE
Column Name | Type | Null? | Definition |
---|---|---|---|
DEPT_TYPE_DISPLAY | VARCHAR(40) | Y | Display of department type |
DEPT_TYPE_ID | DOUBLE | N | Department type identification |
DEPT_TYPE_PREFIX | VARCHAR(4) | Y | Default prefix for department type |
UPDT_APPLCTX | DOUBLE | N | The application context number from the record info block. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
UPDT_CNT | DOUBLE | N | Set to 0 on insert. Incremented by 1 on update. Used to recognize update conflict where data in a row updated by one application is at risk of being lost by a second application attempting to update the row. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
UPDT_DT_TM | DATETIME | N | The date and time the row was last inserted or updated. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
UPDT_ID | DOUBLE | N | The person_id of the person from the personnel table (prsnl) that caused the last insert or update of the row in the table. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
UPDT_TASK | DOUBLE | N | The registered (assigned) task number for the process that inserted or updated the row. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
BR_SCHED_DEPT_TYPE_R
Column Section | Top of Page |
Table-level Detail
Description: | Bedrock Scheduling Department Type R |
Definition: | Stores relationship between bedrock department types and the order types it can be scheduled for. |
Table Type: | REFERENCE |
Column Detail - BR_SCHED_DEPT_TYPE_R
Column Name | Type | Null? | Definition |
---|---|---|---|
ACTIVITY_SUBTYPE_CD | DOUBLE | N | Activity subtype of the default orders the department type can be scheduled for |
ACTIVITY_TYPE_CD | DOUBLE | N | Activity type of the default orders the department type can be scheduled for |
CATALOG_TYPE_CD | DOUBLE | N | Catalog type of the default orders the department type can be scheduled for |
DEPT_TYPE_ID | DOUBLE | N | ID of the department type |
UPDT_APPLCTX | DOUBLE | N | The application context number from the record info block. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
UPDT_CNT | DOUBLE | N | Set to 0 on insert. Incremented by 1 on update. Used to recognize update conflict where data in a row updated by one application is at risk of being lost by a second application attempting to update the row. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
UPDT_DT_TM | DATETIME | N | The date and time the row was last inserted or updated. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
UPDT_ID | DOUBLE | N | The person_id of the person from the personnel table (prsnl) that caused the last insert or update of the row in the table. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
UPDT_TASK | DOUBLE | N | The registered (assigned) task number for the process that inserted or updated the row. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |