TABLE eTABLE OF CONTENTS
| Table of Contents |
|---|
...
CFT → Communications → AGRIS Web Service → Communication Inquiry → RJO → Sts=S
Successful transactions Received RECEIVED from Hrvyst Hedge will include new contracts and changes to contracts. The ID/Description field will indicate GRN Contract Post. The Document field will show the AGRIS Contract Number. The Misc 2 field will show the Hrvyst Hedge Contract Number. The Details button will show the contract information that was supplied from RJO.
Successful transactions Sent SENT to Hrvyst Hedge will include new Name IDs and changes to existing Name/Address information. The ID/Description field will indicate NAM Name ID Extract. The Document field will show the AGRIS Name ID. The Details button will show the Name/Address information that was sent to the local SOGE Agent. Only a small subset of the Name/Address data elements will be sent on to RJO by the hosted AGRIS Data Hub.
Successful transactions Sent SENT to Hrvyst Hedge will also include some hedge transactions that have been entered in AGRIS. These transactions will include Spot Contract applications, Pricing the overfill portion of a contract, or cancelling/under-filling a contract. The ID/Description field will indicate GRN Hedge Transaction Extract. The Document field will show the unique identification of the hedge transaction, including date/timestamp. The Details button will show the information that was sent.
...
CFT → Communications → AGRIS Web Service → Communication Inquiry → RJO → Sts=R
Rejected transactions RECEIVED from Hrvyst Hedge will include contract transactions that have been rejected by the AGRIS web service post/import process. The details of the rejection messages will be available under the Details button. Rejected messages will be sent back to RJO Hrvyst Hedge. There will be no option within the CFT Inquiry to re-post the transaction. It is the responsibility of Hrvyst Hedge or the AGRIS Data Hub to re-post the transaction after the reasons for the rejection(s) have been addressed.
There will be no Rejected transactions logged in the CFT Inquiry for information SENT from AGRIS.
Status: Failed
CFT → Communications → AGRIS Web Service → Communication Inquiry → RJO → Sts=F
...
Failed transactions RECEIVED from Hrvyst Hedge will include contract transactions that have encountered a system error within the AGRIS web service post/import process. The details of the error message will be available under the Details button. There is not currently any plan to provide an option within the CFT Inquiry to re-post the transaction after an error condition. It is the responsibility of the AGRIS Data Hub to re-post the transaction after the reasons for the error has been addressed.
Failed transactions that are marked as SEND include Name IDs or Hedge Transactions that encountered a system error within the AGRIS web service extract process. The details of the error message will be available under the Details button. When a Failed message occurs in the extracts, the system will automatically retry, based on the integration interval setting in the CFT Configuration.
Status: Unsuccessful
CFT → Communications → AGRIS Web Service → Communication Inquiry → RJO → Sts=W
...
U
Unsuccessful transactions RECEIVED from Hrvyst Hedge are similar to the Failed status. An Unsuccessful contract post would be a transaction that was received from Hrvyst Hedge, and then sent to the AGRIS Web Service post process, but a response was never received. Either a power outage or a termination of the system may result in an Unsuccessful status.
There will be no Unsuccessful transactions logged in the CFT Inquiry for information to be SENT from AGRIS.
Status: Waiting In Queue
CFT → Communications → AGRIS Web Service → Communication Inquiry → RJO → Sts=UW
Communication Report
CFT → Communications → AGRIS Web Service → Communication Report → RJO
...