Versions Compared

Old Version 4

changes.mady.by.user Mike Terning

Saved on

compared with

New Version 5

changes.mady.by.user Mike Terning

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...


Anchor
NewAgXML40SalesContractExport
NewAgXML40SalesContractExport
Anchor
_Toc476646627
_Toc476646627
New AgXML 4.0 Sales Contract Export

...

    1. Supported Exchange Partner Filters
      1. No filters apply.
    2. Service Line Settings
      1. Batch Hours
        1. Represents the number of hours the batch is good for before a new batch number will be created. Used to limit batch sizes by creating multiple batches per day.
        2. If set to "0" the hours will not be included in the batch number.
      2. Batch Number
        1. If a batch number is entered it will be saved in that batch.
        2. If Batch Number is entered, Batch Prefix will not be used.
        3. Maximum number of characters 15.
        4. If the batch does not exist it will be added.
      3. Batch Prefix
        1. Default = AGXML
          1. If a batch prefix is entered it will be saved in a batch with a format of XXMMDDHH (XX is the Batch prefix, and MMDDHH is the user date (MM= Month, DD= Day and HH = Hour) of the transaction import if Batch hours is set.)
          2. If Batch Number is entered, Batch Prefix will not be used.
          3. Maximum number of characters is 15. This includes the branch prefix, the batch prefix and the date time suffix.
          4. If the batch does not exist it will be added.
      4. Consume Pricing Info
        1. Yes when selected allows the basic pricing information to be imported with the contract.
          1. Contract will be created with basic pricing (net price only, no basis or board) and the zero basis checkbox will be marked. Verify this
        2. No when selected no pricing record will get created. No is the default value and should only be changed if importing contracts generated from the Excel Purch Ctr Import 01 adapter.
      5. Default Branch
        1. A valid branch ID can be selected. If default branch is specified any unresolved seller/buyer addresses will be forced to this specified branch.
        2. If blank, the seller/buyer address in the AgXML must resolve to a location in the current company or the record will be rejected.
      6. Put Partner Doc# in Reference
        1. Yes, the contract number from the xml document will be placed in the "Reference No" field on the Sales Contract Entry window.
        2. No, the Reference No from the xml document will be placed in the "Reference No" field on the Sales Contract Entry window.
      7. Use Partner Doc#
        1. Yes, the contract will be created with the contract number from the xml document.
        2. No, the contract number will be auto generated based on the Sales Contract Number Setup (General Setup>Additional Setup>Sales Contract Type Numbering).
      8. User ID
        1. Document is created/updated on behalf of the specified user. This must be a valid Microsoft Dynamics GP user.
        2. If blank, User ID specified in CinchX Global Settings will be used.

...

  • The following will trigger a Ship Company Export
    • Add/Change of the Ship Method Detail Maintenance, the system will look to Cinch Ship method Companion table to see if a Vendor ID exists, if it does, then system will export the Shipper Information.
    • Change of Vendor Primary Address, if the Primary address for a vendor is tied to Ship Method Detail Maintenance, then any change to the address information will be exported.
  • File Translation for record type of "NAMA1":
    • Record Type (Position 1-5) = NAMA1
    • Name ID (Position 6-15) = Cinch Vendor ID (translated)
    • Name (Position 16-65) = Vendor Name
    • Address Line #1 (Position 66-95) = Address 1
    • Address Line #2 (Position 96-125) = Address 2
    • City (Position 126-145) = City
    • State (Position 146-154) = State
    • Zip Code (Position 155-164) = Zip Code
    • Country (Position 165-184) = Country
    • Phone Number (Position 185-204) = Phone 1
    • User Defined #2 (Position 205-229) = Contact, UD1 or UD2
    • User Defined #3 (Position 230-254) = Contact, UD1 or UD2
    • User Defined #1 (Position 255-264) = Contact, UD1 or UD2
    • Social Security/Fed ID (Position 265-275) = Soc Sec # or Employer ID number
    • Active/Inactive/Temporary (Position 276-276) = Vendor Status
      • Use A if Active, I if Inactive.
    • Name ID Type (Position 300-300) = "S" (shipper)
      • Setup inside OneWeigh by default C – Customer, F-Farmer, J- Joint, S-Shipper
    • Add/Update Option (Position 347-347) = 3
      • Set to 3. Agris will add the Shipper if it does NOT exist or if it does exist, Agris will update the existing.


Anchor
AgXML40InTransitInImport
AgXML40InTransitInImport
Anchor
_Toc476646630
_Toc476646630
New AgXML 4.0 In Transit-In

...

Export

AgXML 4.0 In Transit-In Import has been created to export Inbound In Transit Ticket records for selected customers.

  1. AgXML 4.0 In Transit-In ImportExport
    1. Supported Exchange Partner Filters
      1. Vendor filters apply
        1. Vendor ID is required. Only one vendor can be entered per service partner.
          1. Vendor can be vendor on the ticket or any ticket split owner. When a ticket for this vendor is entered in Cinch, it is exported by this service partner.
    2. Service Line Settings
      1. Cinch Consumer
        1. Yes, will add CINCH specific fields. Default = yes
        2. No, will conform to AgXML version 4 specifications AgXML_v4.0.xsd (schema).
      2. Company ID Source
        1. This value specifies how the buyer address is determined in the export file. Valid values are Company, Branch and Location. If the setting does not exist, or doesn't match one of the valid values, the Company ID will be sent. Default = Company
          1. Company will translate to the GP Company main address.
          2. Branch will translate to the Cinch Branch address.
          3. Location will translate to the address on the Site ID.
      3. Export Comments
        1. Yes, comments will be exported from the ticket. Default = yes
        2. No, comments will not be exported from the ticket.
      4. Export Notes
        1. Yes, notes will be exported from the ticket.
        2. No, notes will not be exported from the ticket. Default = no
      5. Internal Vendors Only
        1. Yes, only tickets vendors marked as Internal Customer will be exported.
        2. No, will have no effect on the exports.
      6. Message Label Extension
        1. The file extension of the export file.
          1. This extension can be anything but recommended to use XML for easy viewing in IE. (Example ticket 1234 will write a file called 1234.xml).
      7. Send All Updates
        1. Yes, system checks if the ticket has been previously exported and will send it again.
        2. No, system checks if the ticket has been previously exported and will not send updates to the exported tickets. Default = No
      8. Skip Freight
        1. Yes, will not send freight information from ticket. Default = yes
        2. No, will send freight information from ticket.
      9. Skip Gross Weight
        1. Yes, will not send gross weight from ticket. Net weight is sent regardless of this setting.
        2. No, will send gross weight from ticket. Net weight is sent regardless of this setting. Default = no
      10. Skip Tare Weight
        1. Yes, will not send tare weight from ticket. Net weight is sent regardless of this setting.
        2. No, will send tare weight from ticket. Net weight is sent regardless of this setting. Default = no
      11. Vendor Class Filters
  2. If entered this must be a valid Microsoft Dynamics GP vendor class and each imported vendor will be assigned to this class.
  3. Blank – all customer classes will be sent. Default = Blank
  4. * – all customer classes will be sent.
  5. Enter a single customer class or enter a comma separated list of customer classes.
      1. XML Namespace Prefix
        1. Recommended to leave this field blank.
          1. For specific XML naming requirements. Prefixes each tag with this value.
      2. XML Namespace URL
        1. Recommended to leave this field blank.
          1. Puts the XML namespace URL in the header of each document.

Processing Note:

  • In-Transit records will export on and insert or update, without any filtering on the posted or printed flags. The Setup All Updates can be used to limit the number of times the ticket gets exported.