Bloomberg Functions
- FXQT - Access the Bloomberg Beta environment.
- FXPV - Maker function to configure deal-code(s) and clients for ESP and RFS.
- FXPF - In order to test RFQ BRL split settlement., untick "Non-deliverable Strict Mode" if you wish to support and test On/Off-shore trading. Under the general tab select "Flexible Spot Out to SPOT" and "Allow Split Settlement". NOTE: This is a specialized and custom setup, with only a handful of regional Brazilian banks supporting it for LATAM clients trading USD/BRL onshore.
- FXTB - FX Trade Blotter
- FXTG - FX trading Grid (ESP)
- BGPI - Bloomberg Global Person Identifier administration screen. The Maker manages the necessary MiFID EDM/IDM "Natural Person" values here. NOTE: Algo IDs are maintained by Bloomberg.
- APOD - User/Terminal Administration.
- FXBM - FX Batch Manager. Taker function for Batch/Block trading.
- FXEM - FX Execution Manager. Taker function, also used for Batch trading.
- FX - FX Information Portal.
- EC - Enterprise Console, used to maintan TLS Certs for FIX sessions. Typically, MarketFactory will use use this on behalf of our Clients. If this should not work, use https://console.bloomberg.com/#/firm/ODkyODQ3/creg-tls-ui/fix-tls-mgr
- HELP <XXX> - opens Bloomberg Help page for a given function, e.g. HELP FXGO
Web Admin
https://service.bloomberg.com/portal/welcome - Used to administer contracts renewals etc.
Functionality
RFS
- Spot transactions are conducted in XOFF environment only
- BMTF, BTFE and BSEF environments must be specifically enabled by Bloomberg
- BMTF and BTFE environments are used for MTF and EMIR regulatory trades
- NDF and NDS may be traded in BSEF environment only
- Algo ID must be provided by Bloomberg; Short Code ID(s) may be created by Bloomberg users via BGPI function
- Components marked in Spec, which tied to specific environments must be used only for those environments. For example, components required for SEF must be used in BSEF only.
- Commodities - regulatory fields N/A
- CASH - presently not supported; Depo-related fields N/A
- Split Settlement requires special setup from Bloomberg; Tag 22432 - SettlQualifier - is used only for Split Settlement transactions
- A client may reject request for quote or cancel previously submitted quote
- "Reg Reporting" and "Pre WVR Post DEF" fields are available only when BMTF or BTFE environments chosen
- Improperly built messages will result in either error reports from Bloomberg or won't be processed
- Some fields are required for 2-legged transactions only
- Bloomberg ID Source is the same for both Regulatory Trade IDs and Allocation Regulatory Trade IDs
BRL Split Settlement
- Available only for Spot transactions in XOFF environment
- Available in RFS mode only
- A client must be specifically enabled for Split Settlement by Bloomberg
- Applicable only to specific currency pairs, like USD/BRL
- An enabled client can launch his RFQ FXGO icon and select "Subtype" as "Split Settlement"
- Then a client can change change base currency Settlement Date, which has "Flexible" label to the right, as on the screen shot below
BRL is deliverable onshore.
Split settlement infers different tenors for each currency in the trade. I agree that if it's split settlement, with the same tenor, then it's not really split settlement at all although we allow the same value date to be applied to both currencies. Maybe I should consider an enhancement to product team that states that a split settlement trade should not have one value date.
I think we provide those for tags also when trades were done under MIFID.. Please refer to our FIX spec.
FXTG (FX Trading Grid)
FXSPOT for SPOT ccy pairs, G10's etc
FXFWD are for pre spot ccy pairs Example EUR/RUB (russian/baltic regional banks) - Only a handful of our dealers are enabled for this. This wouldn't be relevant for you.
FXNDF - Can be traded if supported OFF-FACILITY and ON /SEF / MTF / TFE
SWAPS are not supported at all in FXTG and can be ignored.