Orchimate / Community /

SFC-DSOL1.0

The indicator of the event type as defined by the enumeration specifications.

The creation time of the event. In-Scope Brokers should record the most accurate time they can get closest to the actual time.

This field is used in conjunction with the eventDateTime, if the timestamp in eventDateTime is not granular enough to accurately reconstruct the sequence of events.

The date and time that the acknowledgement or response was sent to the upstream system or to the client.

Indicates the type of logical response of the recorded Order or Split event. If the Order or Split event has no actual response, use the 'null' filler (i.e. null).

Text associated with an event response to record any additional details (e.g. the reject reason in the case of a rejection).

An identifier assigned to the top parent order which should be unique throughout its life cycle.

The ID of the order generated by a system, this should be unique during a trading day but can be reused over time. In Split events, it is the order ID of the child order split itself. In Execution events, it is the order ID of the corresponding order or child order.

Indicates the original order ID on Modify event if the order ID changes after the modification. This field is not necessary if such order ID does not change after modification.

Indicates the security to be traded by the order, e.g. '0001.HK'.

Specifies the type of the ID used in the securityID field, e.g. RIC, SEDOL, ISIN, etc. as defined by the Data Standards enumeration specifications.

The account ID assigned to an order. This must map to the In-Scope Broker’s Reference Data Dictionary. Not required if the account is not known, or it is an aggregated order.

Key string used to identify the client defined by the In-Scope Broker. This must map to the In-Scope Broker’s Reference Data Dictionary provided by the broker which may include other client-related identification such as LEI, entity name, or other detailed information about the client or internal desk. Not required if it is an aggregated order.

In Order and Split events, it indicates the intended trading capacity of an order, i.e 'A - agency' or 'P - principal'. In Order Summary event, it also allows additional value 'AP - agency/principal' to indicate cases when an order is intended to trade partially in an agency capacity and partially in a principal capacity.

The price value for limit based order types, for market order types, a 'zero' value should be used.

For day orders, it is the quantity of the order. For multi-day orders, this can be the rolled over quantity from the previous trading day or the original order quantity. In Modify events, this indicates the intended or target order quantity of the modification, regardless of whether the order was partially filled or not.

Indicates the type of order as defined by the enumeration specifications.

Indicates the lifetime of the order, e.g. today only, valid until specified date, valid until it is cancelled or completed, as defined by the Data Standards enumeration specifications.

The key value of the referenced Algo strategy, e.g. 'VWAP', 'percentage of volume', etc. as defined by the In-Scope Broker.

Algo parameters as part of order requests as specified by the client. The In-Scope Broker can concatenate all specified parameters into a single string with proper delimiters.

Used in conjunction with GTD orders to indicate the order expiry date.

Indicates any In-Scope Broker defined order instruction that is not already captured in the orderType and/or algoAttributes fields. This must map to the In-Scope Broker’s Reference Data Dictionary.

Captures any free text fields on an order new or modify message. This usually contains information from client order instructions, or inter-desk instructions other than the data supplied in the orderInst field. For a child order split that does not have its own instructions, copy the value from its parent order if available.

A free text string name or identifier of the primary system recording the event, e.g. OMS, Algo, etc. as defined by the In-Scope Broker.

Indicates the name or identifier of the trader processing or monitoring the order. An In- Scope Broker can use a system user name (or a valid filler value) for automated trade processes such as low touch order. This must map to the In-Scope Broker’s Reference Data Dictionary.