This page outlines the steps to help you:
Monitor the AGRIS integration with Hryvst
Balance the Position between AGRIS and Hrvyst
Prerequisites:
This document assumes that you have already:
Begun to use the Hryvst platform
TABLE OF CONTENTS (for RJO Hrvyst Hedge, AGRIS Configuration AGS-8899)
| Table of Contents |
|---|
...
Integration Overview
Transactions
...
sent from RJO Hrvyst Hedge to AGRIS
New contracts (Purchase or Sales)
Basis
Hedge-To-Arrive
Flat Price
AutoHedge Contracts
Changes to a contract (or a portion of a contract)
Edit contract details
Price a contract (including ability to price a portion of a delivery/price schedule)
Roll a contract
Cancel a contract
NOTE:
The 4 contract types mentioned above will be a one-to-one relationship between Hrvyst Hedge and AGRIS (Basis, HTA, Flat Price, Hedge). If there are more contract types configured in AGRIS, they will not be communicated from Hrvyst Hedge.
Information requested from AGRIS by RJO Hrvyst Hedge
Customer Storage Balances
These requests will be for specific customers, locations, and commodities, on an on-demand basis.
Transactions
...
sent to RJO Hrvyst Hedge from AGRIS
Name/Address Changes (When changes are made to Name, Address, Phone, Email, Active Status)
Hedge Transactions (Spot Contracts, Cancel Contracts, Contract Overfills)
Configurable by multiple Name ID Types, multiple Locations, and multiple Commodities.
NOTE:
All Contracts are expected to originate, be updated and priced from Hrvyst Hedge (except for Spot Contracts). As mentioned above, the only transactions that should originate from AGRIS would be Spot Contracts, Cancel Contracts, and Contract Overfills.
...
Add Contracts
Edit Contracts
Delete Contracts
Price Contracts
Applications To Contracts (regular applications, direct-haul applications, or cross-location applications)
Stock Transfers
Adjustment Tickets (bin measure-up, position shrink, daily handling loss adjustments)
Customer Vs. Stock Adjustments (adjusting the position for handling loss ticket-by-ticket)
Manual Edit of Inventory Stock On Hand
Sales/Invoicing of commodity items from the product invoicing module (Inventory Management System)
...
Steps to Monitor the RJO Hryvst Integration
Start/Stop the Service
Note: if any of the configuration options are changed (in the previous section), the service must be stopped and restarted in order for the configuration changes to take affect.
...
The display above will show the status of the CFT Service and the Transaction Service (SOGE Agent).
When you click the start/stop button, it will add the integration to the service and start the integration.
The AGRIS User who clicks the Start button above will be the User ID associated with all transactions extracted from AGRIS and sent to RJO Hrvyst Hedge.
Make sure you have enabled both message types prior to starting the service.
Communication Inquiry
CFT ->Communications ->AGRIS Web Service->Communication Inquiry - > RJO
...
You can also click on the Details button above to see the actual xml messages that have been submitted in and out of the AGRIS Web Service, for complete visibility of all messages that have been logged.
...
Status: Successful
CFT → Communications → AGRIS Web Service → Communication Inquiry → RJO → Sts=S
...
Successful transactions 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.
Status: Rejected
CFT → Communications → AGRIS Web Service → Communication Inquiry → RJO → Sts=R
...
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 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 up to 100 times, based on the integration interval setting in the CFT Configuration. If/when the error condition has been resolved, the Last Date/Time for that message type can be manually set back in time, to tell the system to process/send that transaction again.
Status: Unsuccessful
CFT → Communications → AGRIS Web Service → Communication Inquiry → RJO → Sts=U
...
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=W
...
Waiting transactions that are marked as SEND include Name IDs or Hedge Transactions that have been made in AGRIS and are in the queue, waiting to be sent to RJO via the local SOGE Agent and the hosted Greenstone Data Hub. In a normal situation, these entries will be in the queue for a very brief amount of time before they are marked as Successful. If the SOGE Agent or Data Hub are not available, then the Waiting transactions will remain in the queue. The Misc 1 field will show the response reason that the transaction was not able to be sent to the SOGE Agent. The AGRIS CFT Service will continue to attempt to send the transaction(s) until the Agent and Data Hub are available.
Communication Report
CFT → Communications → AGRIS Web Service → Communication Report → RJO
...
For contracts that have been received from Hrvyst Hedge, the AGRIS contract number will be displayed, as well as the Hrvyst Hedge contract number.
Balance the Position between AGRIS and Hrvyst
Hedge Transactions Received In AGRIS From RJO Hrvyst Hedge
GRN → Report Manager → Hedge Audit Reports → Print Standard Reports → Hedge Transactions Detail Report
Press the Sort/Print button. Sort by Commodity Code, Transaction Type. Filter Date/Time by the day/days needed, (ex: 020224000000 to 020224240000). Filter by External System “R” to “R”. Choose “N” for Print Hedge Audit Detail.
...
You could also print the report to include all detail lines that make up the totals. You might want to also sort/subtotal by location within each commodity. A user-defined report could also be created to print this report daily and add/remove the desired columns on the report.
Hedge Transactions Sent From AGRIS To RJO Hrvyst Hedge
GRN → Report Manager → Hedge Audit Reports → Print Standard Reports → Hedge Transactions Detail Report
Press the Sort/Print button. Sort by Commodity Code, Transaction Type. Filter Date/Time by the day/days needed, (ex: 020224000000 to 020224240000). Filter by External System blank to “A”. Transaction Types To Include: 7BCF. Choose “N” for Print Hedge Audit Detail.
...
You could also print the report to include all detail lines that make up the totals. You might want to also sort/subtotal by location within each commodity. A user-defined report could also be created to print this report daily and add/remove the desired columns on the report.
Hedge Transactions NOT Sent From AGRIS To RJO Hrvyst Hedge
GRN → Report Manager → Hedge Audit Reports → Print Standard Reports → Hedge Transactions Detail Report
Press the Sort/Print button. Sort by Commodity Code, Transaction Type. Filter Date/Time by the day/days needed, (ex: 020224000000 to 020224240000). Filter External System by blank to “A”. Transaction Types To Include: 1234568ADEGHIJKLMN. Choose “N” for Print Hedge Audit Detail.
...
You could also print the report to include all detail lines that make up the totals. You might want to also sort/subtotal by location within each commodity. A user-defined report could also be created to print this report daily and add/remove the desired columns on the report.
Edited by: Arlena Bannon 2/2/24
Related Content
| Page Tree | ||||||
|---|---|---|---|---|---|---|
|
...