Scribd
Upload
38 views

Ret Deal Status

The document discusses the various status types for deals on the RET system. There are three main status types: 1) "in progress" which means the deal has not closed yet, 2) "closed" which includes statuses like completed, withdrawn, cancelled, and rejected, and 3) "other" statuses for other interpretations or order management. Statuses like submitted and negotiating are used for in progress deals, while completed, withdrawn, cancelled, and rejected are used for closed deals. Other statuses discussed include not completed and timeout.

Uploaded by

emirav2
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
38 views

Ret Deal Status

The document discusses the various status types for deals on the RET system. There are three main status types: 1) "in progress" which means the deal has not closed yet, 2) "closed" which includes statuses like completed, withdrawn, cancelled, and rejected, and 3) "other" statuses for other interpretations or order management. Statuses like submitted and negotiating are used for in progress deals, while completed, withdrawn, cancelled, and rejected are used for closed deals. Other statuses discussed include not completed and timeout.

Uploaded by

emirav2
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

RET DEAL Status

Overview
Once the deal got submitted into the system, the deal status can be various so as to indicate its state

The status of most deals can be considered into 3 main types;

A. the status for in progress deal = meaning the deal has not closed yet

B. the status for closed deal = meaning the deal is no longer valid for any action

C. Other statuses = meaning the status for other interpretations or for order management

Status for Deal In Progress


There are 2 valid statuses for a live RFQ deal
SUBMITTED

When client click submit button on client applet, the deal will be sent with status as submitted
This status indicates the deal is available on the RET system and ready for further actions

NEGOTIATING

After a deal submitted and trader negotiates the deal for new price

The deal has not yet finalised and it will show as negotiating

This status shows the deal is waiting for action from either client or trader to complete the deal

1
RET DEAL Status

Status for Closed Deal


All deal types have 3 valid statuses for a closed deal
COMPLETED

When client submitted the deal and trader has acceptted it


The deal is logged and closed as completed
<close submit_id="11" gid_id="167" state="Completed" transition="" type="" message="" />

WITHDRAWN

If the deal is closed or withdrawn BEFORE any trader pick it up, the deal status will become withdrawn

<close gid_id="169" state="Withdrawn" transition="" maker_name="" maker_full_name="" maker_role=""


type="" message="Client terminated price negotiation" />

CANCELLED

If the deal is closed or withdrawn AFTER any trader pick it up, the deal status will become cancelled
<close submit_id="13" gid_id="168" state="Cancelled" transition="" type="" message="Client
terminated price negotiation" />

Also, if trader stops the deal after picking up, the deal status will be cancelled

<close gid_id="164" submit_id="5" state="Cancelled" transition="" type="" message="Press own to


enable trading of this order" /

Note: Trader applet uses "message" information in <close/> for showing the reason of cancellation in Active
Deal Panel.

REJECTED

If a trader picks up the order and click the "Reject" button, the status becomes "Rejected".
This status is introduced in CFETS Phase 2 system. allowRejectStatusSearch is a parameter for searching the
"Rejected" deal status at Deal Log.

Other Status
NOT COMPLETED

This is NOT a real status for a deal and only available on deal log filter.
It is for RFQ (execution_style) deal with status NOT completed or TP/SL/OneClick deal with status NOT
completed nor withdrawn

2
RET DEAL Status

TIMEOUT

The timeout status is for order management or TP/SL when the limit order has passed the Good Till setting

However, in later version of RET, order will not be logged as deal - only "fill" order is logged as deal

To enable such logging, the following parameter must be enabled in LOMSServer.ini

[ ORACLE ]

3
RET DEAL Status

PersistentOrderData=1

Note: this timeout status is NOT valid for RFQ/OneClick deal

You might also like