Table Detail Report
ORDER_NOTIFICATION
Column Section | Relationship Section | Top of Page |
Table-level Detail
Description: | Order Notification |
Definition: | This table stores all Order Notifications for a user and the history of the notification. |
Table Type: | ACTIVITY |
Column Detail - ORDER_NOTIFICATION
Column Name | Type | Null? | Definition |
---|---|---|---|
ACTION_SEQUENCE | DOUBLE | N | The order action that caused this notification to occur. An action_sequence = 0 signifies that should be applied to the order rather than the order action. |
ASSIGNED_PRSNL_ID | DOUBLE | N | The identifier of the personnel who is assigned to the notification from within the personnel group context. |
CAUSED_BY_FLAG | DOUBLE | N | Action that causes the notification to be created. 0 = New; 1 = Forward; 2 = Refuse |
FROM_PRSNL_GROUP_ID | DOUBLE | N | The identifier of the personnel group which created the notification by forwarding or refusing the "parent" notification. This field will be 0 when the original notification is created. |
FROM_PRSNL_ID | DOUBLE | N | The user that is responsible for forwarding or refusing the "parent" notification. This field will be 0 when the original notification is created. |
NOTIFICATION_COMMENT | VARCHAR(255) | Y | The free text comment associated with the notification. |
NOTIFICATION_DISPLAY_DT_TM | DATETIME | Y | Stores the date on which a notification should be displayed. For renewal notifications (notification_type_flag=1), this field will be set to projected_stop_dt_tm minus renewal period associated to order's policy and duration. For other types of notifications, this field will be the date that the notification is created. |
NOTIFICATION_DISPLAY_TZ | DOUBLE | Y | Time zone associated with the corresponding NOTIFICATION_DISPLAY_DT_TM column. |
NOTIFICATION_DT_TM | DATETIME | Y | The time that the notification is created. |
NOTIFICATION_REASON_CD | DOUBLE | N | The reason associated with the notification. |
NOTIFICATION_STATUS_FLAG | DOUBLE | N | The status of the notification. 1 = Pending; 2 = Completed; 3 = Refused; 4 = Forwarded; 5 = Admin-Cleared; 6 = No Longer Needed |
NOTIFICATION_TYPE_FLAG | DOUBLE | N | The type of notification stored. 1 = Renew; 2 = Cosign; 3 = Med student; 4 = Incomplete Order; 5 = Refusal |
NOTIFICATION_TZ | DOUBLE | Y | Time zone associated with the corresponding DT_TM column. |
ORDER_ID | DOUBLE | N | The order that caused this notification to occur |
ORDER_NOTIFICATION_ID | DOUBLE | N | Unique ID for Order_Notification. |
PARENT_ORDER_NOTIFICATION_ID | DOUBLE | N | The Link to a "parent " notification when it has been forwarded or refused. |
STATUS_CHANGE_DT_TM | DATETIME | Y | The time that the status was updated on the notification. |
STATUS_CHANGE_TZ | DOUBLE | Y | Time zone associated with the corresponding DT_TM column. |
TO_PRSNL_GROUP_ID | DOUBLE | N | The identifier of the personnel group which the notification in intended for. |
TO_PRSNL_ID | DOUBLE | N | The user this notification is intended for. For renew notifications that are suppressed, this field will be 0. |
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. |
Relationship Detail - ORDER_NOTIFICATION
Child Column in ORDER_NOTIFICATION(FK) | Parent Table Name | Parent Column Name | |
---|---|---|---|
Parents: | ORDER_ID | ORDERS | ORDER_ID |
PARENT_ORDER_NOTIFICATION_ID | ORDER_NOTIFICATION | ORDER_NOTIFICATION_ID | |
ASSIGNED_PRSNL_ID | PRSNL | PERSON_ID | |
FROM_PRSNL_ID | PRSNL | PERSON_ID | |
TO_PRSNL_ID | PRSNL | PERSON_ID | |
FROM_PRSNL_GROUP_ID | PRSNL_GROUP | PRSNL_GROUP_ID | |
TO_PRSNL_GROUP_ID | PRSNL_GROUP | PRSNL_GROUP_ID |
Parent Column in ORDER_NOTIFICATION (PK) | Child Table Name | Child Column Name | |
---|---|---|---|
Children: | ORDER_NOTIFICATION_ID | HIM_UNSIGNED_ORDERS | ORDER_NOTIFICATION_ID |
ORDER_NOTIFICATION | PARENT_ORDER_NOTIFICATION_ID |
ORDER_OPS
Column Section | Relationship Section | Top of Page |
Table-level Detail
Description: | Order Operations |
Definition: | Contains all the orders that need to be affected by an orders operations job. |
Table Type: | ACTIVITY |
Column Detail - ORDER_OPS
Column Name | Type | Null? | Definition |
---|---|---|---|
OPS_FLAG | DOUBLE | N | This tells us which operations job that will be updating the order.1 - ORM Continuing Order Update2 - ORM AUTO Complete Orders3 - ORM Cleanup Transfer/Canceled Orders |
ORDER_ID | DOUBLE | N | The is the primary key of the orders table that will help us have a direct link to the orders that we need to change in our operations job. |
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. |
Relationship Detail - ORDER_OPS
Child Column in ORDER_OPS(FK) | Parent Table Name | Parent Column Name | |
---|---|---|---|
Parents: | ORDER_ID | ORDERS | ORDER_ID |
ORDER_ORDER_RELTN
Column Section | Relationship Section | Top of Page |
Table-level Detail
Description: | Order Order Relation |
Definition: | This table stores the different types of relationships between two orders. For example, a relationship between an existing order and a new order that is created by a reconciliation action on a new order. |
Table Type: | ACTIVITY |
Column Detail - ORDER_ORDER_RELTN
Column Name | Type | Null? | Definition |
---|---|---|---|
ENTERED_BY_PRSNL_ID | DOUBLE | N | The ID of the person who created the order to order relation. (a row in this table) |
ORDER_ORDER_RELTN_ID | DOUBLE | N | The primary key of this table. |
RELATED_FROM_ACTION_SEQ | DOUBLE | N | The action sequence on the existing order from which the relationship to another order has been created. Along with order_ id, this field is a foreign key back to the order_action table. |
RELATED_FROM_ORDER_ID | DOUBLE | N | The existing order _id from which the relationship to another order has been created. This field is a foreign key back to the orders table. |
RELATED_TO_ORDER_ID | DOUBLE | N | The order to which the other existing order (related_from_order_id) is related to. This too is a foreign key back to the orders table. |
RELATION_CREATED_DT_TM | DATETIME | N | The date and time when the relationship between the two orders was created. |
RELATION_CREATED_TZ | DOUBLE | N | The time zone associated with the relation_created_dt_tm column. This is a user centric time zone. |
RELATION_TYPE_CD | DOUBLE | N | Codified value that indicates the type of relationship that exists between the two orders. For example, Covert, etc. |
RELTN_GROUP_ID | DOUBLE | Y | The relation group id for the order to order relationship grouping. |
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. |
Relationship Detail - ORDER_ORDER_RELTN
Child Column in ORDER_ORDER_RELTN(FK) | Parent Table Name | Parent Column Name | |
---|---|---|---|
Parents: | RELATED_FROM_ORDER_ID | ORDERS | ORDER_ID |
RELATED_TO_ORDER_ID | ORDERS | ORDER_ID | |
RELTN_GROUP_ID | ORDERS | ORDER_ID | |
ENTERED_BY_PRSNL_ID | PRSNL | PERSON_ID |
ORDER_PROPOSAL
Column Section | Relationship Section | Top of Page |
Table-level Detail
Description: | Order Proposal |
Definition: | This table stores proposal to create new orders and proposals to change existing orders. For a proposal to create a new order, there is no corresponding row on the orders table until the proposal is accepted. For all other types of proposals, there will be a corresponding row on the orders table. |
Table Type: | ACTIVITY |
Column Detail - ORDER_PROPOSAL
Column Name | Type | Null? | Definition |
---|---|---|---|
BILLING_PROVIDER_FLAG | DOUBLE | N | Flag indicates which provider was specified as the billing provider. 0 - Not specified, 1 - Order provider, 2 - Supervising provider. |
CATALOG_CD | DOUBLE | N | The catalog code from the Order_Catalog table. For a proposal to alter an existing order, this field will be in sync with the Catalog_CD field on the Orders table. |
CLINICAL_DISPLAY_LINE | VARCHAR(2000) | Y | A formatted display line of user selected order proposal details. The field is truncated and will contain a maximum of 1999 characters. When the field is truncated, it will be terminated with ellipsis. |
COMMUNICATION_TYPE_CD | DOUBLE | N | Codified value that identifies the means of communication which was used to generate the order proposal (how it was communicated to the proposal creator). |
CREATED_DT_TM | DATETIME | N | The date and time when the proposal was entered into the system. |
CREATED_TZ | DOUBLE | N | Time zone associated with the created_dt_tm column. |
DOSING_METHOD_FLAG | DOUBLE | Y | Indicates the type of dosing that is applied to the order proposal. Values: 0 - No special dosing applies to this order proposal, 1 - variable dosing exists for the ingredients of this order proposal (which is only applicable for medication order proposals). |
ENCNTR_ID | DOUBLE | N | The person's encounter id. If the proposal is not associated to an encounter, the field is set to 0. For a proposal to alter an existing order, this field will be in sync with the encntr_id field on the orders table. |
ENTERED_BY_PRSNL_ID | DOUBLE | N | The ID of the person who created this proposal. |
FUTURE_LOCATION_FACILITY_CD | DOUBLE | N | The future facility location that is proposed to be used for this order. The facility can change while the order is in a Future status; however, once the order is activated on an encounter, this field will retain its value and will not be altered. |
FUTURE_LOCATION_NURSE_UNIT_CD | DOUBLE | N | The future nurse unit location that is proposed to be used for this order. The nurse unit can change while the order is in a Future status; however, once the order is activated on an encounter, this field will retain its value and will not be altered. |
HNA_ORDER_MNEMONIC | VARCHAR(1000) | Y | The primary mnemonic of the orderable item from which the order proposal is created. This is the common name recognized by all clinicians who provide services to patients. For Pharmacy order proposals, this is the legal generic name. It normally is carried forward from primary_mnemonic field in order_catalog table. The field is truncated and will contain a maximum of 999 characters. Ellipses are not appended if the field is truncated. |
INCOMPLETE_PROPOSAL_BIT | DOUBLE | N | A bitmask which indicates if an order proposal is incomplete in its composition. If the mask is 0, the order proposal is complete in its initial state to represent a proposed action of an order. If the mask is valued, it indicates aspects of the order proposal are incomplete and requires additional information at the time of accepting to complete its composition. Each bitmask indicates a different aspect of the proposal is incomplete (meaning, multiple aspects could be incomplete). |
IV_SET_SYNONYM_ID | DOUBLE | N | The ID that uniquely identifies the IV set used to place the proposed order action. This field may only be valued for a proposal to create a new order with an IV set or an existing order with an IV set already established. |
MED_ORDER_TYPE_CD | DOUBLE | N | Codified value that categorizes a medication order. For example, IV, Intermittent. For a proposal to alter an existing order, this field will be in synch with the med_order_type_cd field on the Orders table (except for Sliding Scale orders, which is identified by the rx_mask field). |
OE_FORMAT_ID | DOUBLE | N | The ID of the order entry format that is associated to this proposal. For a proposal to alter an existing order, this field will be in sync with the OE_Format_ID field on the Orders table. |
ORDERED_AS_MNEMONIC | VARCHAR(1000) | Y | The mnemonic used by direct care providers (physicians, nurses, etc.) when they place orders in applications such as PowerOrders. This field is important for free text orderables, since hna_order_mnemonic is a generic name and ordered_as_mnemonic carries specific information about the order. The field is truncated and will contain a maximum of 999 characters. Ellipses are not appended if the field is truncated. |
ORDER_ID | DOUBLE | N | The ID of the order associated with this proposal. If the proposal is to create a new order, the field will initially be 0 as the order does not yet exist. If the proposal is accepted, this field will be updated to the ID of the newly created order. A proposal to alter an existing order will always have a valued order id. |
ORDER_MNEMONIC | VARCHAR(1000) | Y | The mnemonic mostly used by department personnel, for example, Lab Technicians, Pharmacists. For Pharmacy orders, this field is not populated until product is assigned by Pharmacy Technician or Pharmacist. The field is truncated and will contain a maximum of 999 characters. Ellipses are not appended if the field is truncated. |
ORDER_PROPOSAL_ID | DOUBLE | N | The primary key of this table. |
ORDER_PROPOSAL_STATUS_RSN_BIT | DOUBLE | Y | Bitset describing why the proposal is in a given status: Bit 0 - Invalidated due to expiration agent processing. |
ORDER_SCHEDULE_PRECISION_BIT | DOUBLE | N | A bitmask which indicates the precision of the order schedule (start and stop date/times). If this mask is 0, the start and stop date/time are precise. If the mask is valued, it indicates aspects of the order schedule are estimated (not precise). The 1st bit (2^0) indicates if the start date/time is estimated. The 2nd bit (2^1) indicates if the stop date/time is estimated. |
ORDER_STATUS_REASON_BIT | DOUBLE | Y | A bitmask which indicates additional reason details about the status of the proposed order. If this mask value is null, there are no additional details about the status. Bits are reserved for usage with various workflows or functionality defined below. The first bit (2^0) indicates if incomplete status has been resolved. The 2nd bit (2^1) indicates if incomplete status is due to no matching synonym. The 3rd bit (2^2) indicates if incomplete status is due to missing required details. |
ORIGINATING_ENCNTR_ID | DOUBLE | Y | For future orders (used for requests for consultation), Meaningful Use requires documentation of the encounter that created the future order. Since encntr_id is null for future orders (because the order will be assigned to a future encounter), a new field to track the originating encounter is needed. |
ORIG_ORD_AS_FLAG | DOUBLE | N | This flag indicates how this order proposal was originally placed. For a proposal to alter an existing order, this field will be in synch with the orig_ord_as_flag on the orders table. 0 - Normal order, 1 - Prescription/Discharge order, 2 - Recorded/Home meds, 3 - Patient owns meds (this value is deprecated and will be removed in the future), 4 - Pharmacy charge only, 5 - Satellite (Super Bil) meds |
PERSON_ID | DOUBLE | N | The ID of the person for whom this proposal was made. For a proposal to alter an existing order, this field will be in sync with the person_id on the orders table. |
PROJECTED_CS_ORDER_ID | DOUBLE | N | The projected ID of the parent Care Set order (valued if the proposed order is a Care Set child). The ID is considered to be projected since the Care Set parent order does not have to exist in the system. |
PROJECTED_ORDER_ID | DOUBLE | N | This field is populated only for proposals to create new orders. If the proposal is accepted, the value from this field will become the order_id of the newly created order. |
PROPOSAL_FROM_ACTION_SEQ | DOUBLE | N | If the proposal is to create a new order this field will be 0. For proposals to alter an existing order, this field is the order action sequence on which this proposal is based. This is the action from which this proposal is branching. |
PROPOSAL_GROUP_ID | DOUBLE | N | This field is a group ID assigned if two or more proposals were processed as a group. Obsolete column |
PROPOSAL_SOURCE_TYPE_CD | DOUBLE | N | Codified value that indicates by what work flow the proposal was created. For example, "PHONE MESSAGE". |
PROPOSAL_STATUS_CD | DOUBLE | N | Codified value that indicates the status of the order proposal. |
PROPOSAL_TO_ACTION_SEQ | DOUBLE | N | This field will initially be set to 0. If the proposal is accepted, this field will be set to the order action sequence that is generated when the proposal is accepted. If the proposal is not accepted (rejected, withdrawn, invalidated, or never resolved) this field will remain 0. |
PROPOSED_ACTION_TYPE_CD | DOUBLE | N | Codified value that indicates what order action this proposal is intended to trigger. |
RELATED_ACTION_SEQ | DOUBLE | N | The action sequence of the existing order from which the relationship was created. Along with order_id, this field is a foreign key back to the order_action table. |
RELATED_ORDER_ID | DOUBLE | N | The order_id of the existing order from which the relationship was created. This field is a foreign key back to the orders table. |
RELATED_TYPE_CD | DOUBLE | N | Codified value that indicates the type of relationship that exists between the order and proposal. For example, Covert, etc. |
RELTN_GROUP_ID | DOUBLE | Y | The relation group id for the order related to the proposal. |
RESOLVED_BY_PRSNL_ID | DOUBLE | N | The ID of the person who resolved the proposal. |
RESOLVED_DT_TM | DATETIME | Y | The date and time when a subsequent action was taken to resolve the proposal. |
RESOLVED_TZ | DOUBLE | Y | Time zone associated with the resolved_dt_tm column. |
RESPONSIBLE_PRSNL_ID | DOUBLE | N | The ID of the person who is targeted to act on the proposal. |
SIMPLIFIED_DISPLAY_LINE | VARCHAR(1000) | Y | A simplified display line of user selected order proposal details. The information in this field will be hard coded and only written for pharmacy order proposals. The field is truncated and will contain a maximum of 999 characters. When the field is truncated, it will be terminated with ellipsis. |
SUPERVISING_PROVIDER_ID | DOUBLE | N | Unique identifier represents a physician in the system who is responsible for the proposal that is placed by the mid-level provider or resident. |
SYNONYM_ID | DOUBLE | N | The ID that uniquely identifies the orderable associated to this proposal. For a proposal to alter an existing order, this field will be in synch with the synonym_id field on the orders table. |
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. |
Relationship Detail - ORDER_PROPOSAL
Child Column in ORDER_PROPOSAL(FK) | Parent Table Name | Parent Column Name | |
---|---|---|---|
Parents: | ENCNTR_ID | ENCOUNTER | ENCNTR_ID |
ORIGINATING_ENCNTR_ID | ENCOUNTER | ENCNTR_ID | |
ORDER_ID | ORDERS | ORDER_ID | |
RELTN_GROUP_ID | ORDERS | ORDER_ID | |
CATALOG_CD | ORDER_CATALOG | CATALOG_CD | |
IV_SET_SYNONYM_ID | ORDER_CATALOG_SYNONYM | SYNONYM_ID | |
SYNONYM_ID | ORDER_CATALOG_SYNONYM | SYNONYM_ID | |
OE_FORMAT_ID | ORDER_ENTRY_FORMAT_PARENT | OE_FORMAT_ID | |
PERSON_ID | PERSON | PERSON_ID | |
ENTERED_BY_PRSNL_ID | PRSNL | PERSON_ID | |
RESOLVED_BY_PRSNL_ID | PRSNL | PERSON_ID | |
RESPONSIBLE_PRSNL_ID | PRSNL | PERSON_ID | |
SUPERVISING_PROVIDER_ID | PRSNL | PERSON_ID |
Parent Column in ORDER_PROPOSAL (PK) | Child Table Name | Child Column Name | |
---|---|---|---|
Children: | ORDER_PROPOSAL_ID | ORDER_PROPOSAL_ADHOC_TIME | ORDER_PROPOSAL_ID |
ORDER_PROPOSAL_COMMENT | ORDER_PROPOSAL_ID | ||
ORDER_PROPOSAL_DETAIL | ORDER_PROPOSAL_ID | ||
ORDER_PROPOSAL_DIAG_RELTN | ORDER_PROPOSAL_ID | ||
ORDER_PROPOSAL_INGREDIENT | ORDER_PROPOSAL_ID | ||
ORDER_PROPOSAL_NOTIF | ORDER_PROPOSAL_ID | ||
ORDER_PROPOSAL_THER_SBSTTN | ORDER_PROPOSAL_ID | ||
ORDER_RECON_DETAIL | ORDER_PROPOSAL_ID | ||
TASK_SUBACTIVITY | ORDER_PROPOSAL_ID |
ORDER_PROPOSAL_ADHOC_TIME
Column Section | Relationship Section | Top of Page |
Table-level Detail
Description: | Order Proposal Adhoc Time |
Definition: | This table stores adhoc frequency times that are being proposed for a new or existing order. |
Table Type: | ACTIVITY |
Column Detail - ORDER_PROPOSAL_ADHOC_TIME
Column Name | Type | Null? | Definition |
---|---|---|---|
ADHOC_TIME_SEQUENCE | DOUBLE | N | Signifies the order of the ad hoc frequency time supplied for a proposal. This is assigned by the system. |
ORDER_PROPOSAL_ADHOC_TIME_ID | DOUBLE | N | The primary key of this table. It is internally assigned by the system. |
ORDER_PROPOSAL_ID | DOUBLE | N | The order proposal ID associated to this ad hoc frequency time instance. |
TIME_OF_DAY | DOUBLE | N | Ad hoc time of day which is represented as the number of minutes within a day. The valid range of values for this field is 0 to 1439 (inclusive). |
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. |
Relationship Detail - ORDER_PROPOSAL_ADHOC_TIME
Child Column in ORDER_PROPOSAL_ADHOC_TIME(FK) | Parent Table Name | Parent Column Name | |
---|---|---|---|
Parents: | ORDER_PROPOSAL_ID | ORDER_PROPOSAL | ORDER_PROPOSAL_ID |