what if deals

8/10/2019 What if Deals

1/8

What If Deal Processing in FXTE

Version3.1

Shweta Mohaatra


2/8

Action Name Date Comments Version

Created Shweta Mohapatra 06Jan2012 Created the intial version 1.0


3/8

What If Deal rocessing in FXTE

!VE"VIEW

The prpose o! what i! deal is !or hed"in" the deal. This will allow the

trader to see the a!!ect o! h#pothetical trades on his $ % & and hispositions. 'e can re!ine and chan"e his strate"# (e!ore committin"the deals.

The a(ilit# to enter )what i!* trades where all the deal in!ormation is

not +nown. So the ser can amend the deal with re,ired in!ormation

and can convert the deal to a real transaction. The trader will not have access to e-istin" )what i!* deals !rom the

deal entr# screens.

/hat ! deals are sed to pdate the traders positions and $& !or

the crrent (ranch processin" date and removed at the end o! da#drin" the DD (atch processin".

Cstomer /hat ! deals do not pdate the traders positions or $&

and are not removed drin" (atch processin". These deals areremoved when the ser removes them !rom the in,ir#.

The docment covers static data related to what i! deals3 deal

processin"3 ta(les and (atch processin" related to /hat i! deal.

The !ollowin" transactions will not (e allowed in the initial phase4

57 ta+edowns

5nter (ranch transactions

Static #ata Set $%


4/8

ADNM Screen5 The Alternate Deal Nm(er Maintenance screen will

(e modi!ied to add the new data o! /hat i! deal nm(er !or the(ranch. The !ront o!!ice 8 will (e sed !or the what i! deals per!ormedon the particlar (ranch.

ADNM data set up should be done for what if deal entry.

Processing%

Deal Entr&%

The FXTE screen is used for the deal entry. Deal entry programs will be modified to allow the entry of deals tagged

as what if. Deal entry program procedures will be modified to create interface deal records instead of normal

database deal records. The corresponding deal and position blotter records will also be created.

The user is allowed to view the current what if deals! turn them into real deals! modify them or remove them in the

deal blotter T"D#.

The user can enter a $hat if deal by enabling the %ending Deal type field to $hat if or &ustomer $hatif! in

the %rocessing option tab in the FXTE screen. 'll the other data entries are same as FX deal entries.


5/8

The user can modify the what if deal to real deal using the deal blotter T"D#.

Interface table: $hen the what if deal is entered! the user should not be getting the deal number as it is

interfaced to the ()T* table.

The ()T* records will be created with a new status of +, and the module specific interface record will be

generated with a deal number based on the 'D)- what if deal number record for that branch.

(f a what if deal is modified! the ()T* status code for the corresponding deal will be updated from +, to +. '

new ()T* record will be created with a new 'D)- what if deal number and a status code of +,.

The ()/0T()D of the what if deal will be updated as $ where as the ()/0T()D for customer what if deal will

be updated as X.

TREV Table1 The deal entry will be updating T"E2 table with status code $ for whatif deals.(f for $hatif deal

pending deal type field is amended from 3E4 to )/! a reversal T"E2 record is create with status code

-. 'nd new T"E2 will be created with a new 'D)- what if deal number and a status code of $.

(t also updates the T"%D blotter with status code $ and X for $hatif and &ustomer$hatif deal

respectively.


6/8

TRDB Blotter:

The T"D# #lotter will be modified to display the number of what if transaction available. Drilling down on a

displayed record will access the Tr/%(&4 deal entry screens and allow the deal to be turned into a real deal or to be

amended. The list of $hat if and &ustomer$hatif deals will be displaying in the T"D# blotter.

(t will ta5e the user to the list of deals by clic5ing on the particular deal.

(t will navigate the user to the FXTE screen by Double clic5ing the deal number displaying in the blotter.

The user can do the amendment and will get a new deal number.

The reversal of the deals also can be performed from T"D# blotter.

The T"%#! Tr/%(&4 %osition #lotter will be modified to have an (nclude what if option. (f this option is selected!

T"%# will include what if deals in the position display.

Batches :

The #D#D #atch Deal #lotter Delete program will be modified to delete all T"E2! T"%D! ()T*! and

module specific interface records for what if deals for a given branch #ut the &ustomer what if deals

will be presenting in the deal blotter.

The #%#0 #atch %osition #lotter 0pdate program will be modified to ignore all T"%D records for what

if deals for a given branch.

##FT for #D#D #atch1


7/8

Status Codes:

What IF Deal

Actions INTH Table TREV Table

Status

code

Inoutind

Deal Entr !" W The #hat if deal #ill be

dis$lain% #ith status code W&

A'end'ent !( W What if deal #ill re'ain the

sa'e #ith status W& Ne# realdeal #ill be created&Re)ersal*The real

deal created after

a'end'ent+

NA The #hat if deal status #ill be ,

and the real deal status #ill be

dis$lain% as R&

What If Custo'er Deal:

Actions INTH Table TREV Table

Status

code

Inoutind

Deal Entr !" - The #hat if custo'er deal #ill

be dis$lain% #ith status code

.-/&


8/8

A'end'ent !( - What if deal #ill be #ith status

.N/& Ne# real deal #ill be

created&Re)ersal*The real

deal created after

a'end'ent+

NA The #hat if deal status #ill be

.N/ and the real deal status #ill

be dis$lain% as R&

what if deals

Documents