Agenda and Minutes

Main Topics

Use

1. Review Existing Documentation & Resources

   1. Topic Leader:

   2. The desired outcome is that the audience is informed about the background/purpose of the project and current resources available.

   3. Pre-meeting notes and references:

      1. https://aggateway.atlassian.net/l/cp/sszZGhqW (Notes on Retail Order Summary Request / Report enhancement from S&G discussion)

         1. 

   4. Minutes:

2. Discussion

   1. Topic Leader: Ben Craker, Theresa.Fitzsimmons

   2. The desired outcome is that group discusses general need for an updated message, documents initial requirements and preference for message or REST implementation, …

   3. Pre-meeting notes and references:

   4. Minutes:

      1. Support stock transfer process for parties that are external to the dealer sending the transfer

         1. Would use this lookup to find the right identifier for the recipient of the transfer

      2. Info used for lookup

         

      3. Both for looking up to see if an identifier from a previous transfer is still current

      4. Also the more common use case that there will be some demographic info needed to find the right identifier for a transfer

      5. Is there an instance with one physical address with multiple GLNs

         1. e.g. a warehouse and fuel bulk tanks at the same facility

         2. Need implementation guide on returning only valid account

            1. Discussed the manufacturer would only include “rank 1” GLN that is active

            2. Manufacturer would only return GLN for location with seed dealer agreement, not the grain elevator entity even at the same location, etc.

      6. Would the lookup be only for that instance or would retailer want to store the GLN for some future use

         1. That would mean there needs to be a way to lookup an ID to confirm it is still valid, e.g. the next season

      7. Status
         colour Red title decide

         General interest in having the lookup

      8. Is the preferred solution a message update or is REST a better solution

         1. Likely will be looking up one-off, and probably not storing

         2. Will maybe store some IDs for frequent transfers or hubs, maybe more common for other locations in the same organization

      9. For message there is a lookup for Growers

         1. AgreementStatus message did not make it into the published standard, where this issue was discovered

         2. Retrofitting existing message for this purpose probably not a great fit

         3. Dealer info and validity not part of the grower message

         4. Not really anything in an XML standard that would support this the people on the call are aware of

      10. Looks like it should be pretty straight forward to know out in a quick WG

          1. Not sure we can wedge it in at Annual Meeting

          2. Likely do not need to have a series of meetings, a couple shorter sessions should work

3. …

Closing Topics