The S2P Direct process for forward contracts derives several values to populate the TRADE and TRADE_detail tables in the TRADE database. It maintains each leg of the forward contract as a separate security. The forward contract generates two positions: the security position for the currency bought and the security position for the currency sold.
Note: | A forward contract can fracture into many lots in STAR, when the quantity of the closing forward contract closes more than the current quantity of the open forward contracts. The system stores fractured forward contracts in the STAR object as one transaction in the warehouse, as it does for all other security types. The TRADES database in the PACE data warehouse reflects the transaction sent to the STAR accounting application, after STAR to PACE Direct processing "rolls-up" the fractured contract into a single forward contract. |
STAR generates each currency leg position as an Open position and the long/short indicator and record type of the cost position must clearly bifurcate the Buy and Sell leg for the forward contract. S2P logic resolves any ambiguity for reporting Buy and Sell legs by inspecting the Buy/Sell Indicator (tag 1364) and Cancel Flag (tag 10045) to determine the correct signage on each leg:
- If Buy/Sell Indicator = 'S', then S2P flips trade fields to opposite signs (~ multiply by -1)
- If Buy/Sell Indicator = 'B', then S2P sets trade fields positive (~ absolute value)
- If Buy/Sell Indicator = 'S' and Cancel Flag = 'Y', then S2P sets trade fields positive
- If Buy/Sell Indicator = 'B' and Cancel Flag = 'Y', then S2P flips trade fields to opposite signs
If you do not store the Buy/Sell Indicator in the STAR object, the STAR to PACE Direct logic defaults to the logic described in the previous STAR to PACE Direct User Guide for your release.
The following table lists the fields, STAR tag number, and descriptions of the fields affected by the S2P derivation logic for forward contracts.
Option | Tag | Description |
---|---|---|
MTTYPE | 1 | TRADEFWD transactions are split into a closing transaction and an opening transaction. Options include:
|
Long Short Indicator | 15 | Specifies the long short indicator for the leg of the forward contract, as derived below:
|
Event Type | 55 | Specifies the event type for the leg, as derived below:
|
Reason Code | 56 | Specifies the client intent for the contract. A client may initiate a forward contract or close an existing contract position. As example:
|
Buy/Sell Indicator | 1364 | STAR populates the Buy/Sell Indicator on the position level of the object for both the legs of the forward contract. The value is established for the lifecycle of the position when STAR initially creates the new forward position (leg). |
Forward Close Eligible Indicator | 3924 | Specifies the entity option created during the Create Entity function to control forward close eligibility. Options include:
|
Cancel Flag | 10045 | Indicates whether a record in the warehouse is a cancel record. The field is not available or stored in the STAR core object. Options include:
|
Record Type | 5525 | Specifies the actual ESTAR cost object level where the forward trade is stored. Options include:
|
The following table lists the database fields established by S2P processing for forward contracts.
Event Type | Cash Category | Fields Used |
---|---|---|
TRADES | TRADE | COST_BASE |
TRADES | TRADE_DETAIL | DISP_BOOK_VALUE_GAAP |
Table 3: TRADES Database Tables and Fields Derived for Forwards
0 Comments