Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

A pending transaction can have one of the following statuses.

StatusDescription
PENDINGDefault. Identifies a Pending transaction that requires evaluation before you release it to the STAR accounting engine for processing. You can modify transactions with a Pending status.
HOLDIndicates that you assigned the transaction a Hold status, making the transaction ineligible for release to the STAR accounting engine. You can modify transactions with a Hold status.
PROCESSINGIndicates that the system is temporarily processing the transaction.
RELEASEDIndicates that the transaction was successfully released from the PENDING_TRADES table to the STAR accounting engine for processing. You cannot modify transactions with a Released status.
FAILEDIdentifies a transaction that was unsuccessfully released from the PENDING_TRADES table. You cannot update or release failed transactions. You can repair a failed transaction in the Exceptions workspace and submit it to the STAR accounting engine for processing.
CANCELEDIdentifies a canceled event directed to the Pending Trades table. When a transaction has a status of CANCELED in the Pending Trades table, it is ineligible for release to the STAR accounting engine going forward.
FOF_ALLOCATIONIdentifies trades created by the fund of funds allocation process for use with Fund of Funds (FOF) workflows in Eagle's mutual fund accounting solution. For more information, see Manage Fund of Funds Cash Allocations. A transaction with this status requires evaluation before you release it to the STAR accounting engine for processing. You can modify transactions with an FOF_ALLOCATION status. 
<CUSTOM STATUS>

You can add additional custom statuses to group different types of "pending" transactions. The system provides the default values of Pending and Hold in the PEND_TRD_STATUS code category, but you can add your own code values.

You cannot add the statuses of Released and Failed because those statuses are already used internally by pending trade processing. If you use custom statuses with pending transactions, be aware that you cannot use pending trade rule details to assign custom statuses. Pending trade rule details enable the system to assign transactions a status of Pending. If you use custom statuses, the system can receive transactions from an upstream system that have a custom pending transaction status assigned.

The incoming transaction's Pending Trade Flag field (tag 3695) has a value of Y and the transaction's Pending Trade Status field (tag 3720) has a value equal to the custom status code value. You can then use the pending trade process to release that transaction in order for the STAR accounting engine to process the transaction.

  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.