Anchor
_Toc476646621 _Toc476646621

Introduction

What's New is your guide to enhancements in CINCH Software.
We add enhancements based on feedback we receive from customers, as well as on market research. Your willingness to help us build better products makes this a more complete solution, putting you in a better position to manage your organization successfully. We encourage you to share your thoughts and reactions with us at any time.
Some enhancements described in this documentation are optional and can be purchased through your CINCH software sales representative. If you currently have a license for one of these modules and have an active enhancement program, you will automatically receive the enhancements contained in that module.
This document describes enhancements that were added to CINCH Software since General Release 16.0.
Description of the enhancements in this chapter relate to
Chapter 1, "Cinch Document Exchange," describes the miscellaneous changes made to Cinch Document Exchange.

Anchor
_Toc476646622 _Toc476646622

Supported Version

The following is a list of the Dynamics GP version we will be supporting for this release.

Anchor
_Toc476646623 _Toc476646623

Dynamics GP

Software Version: 16.0 (16.00.0579 R2)
KB3218072
Dex Version: (16.00.0034) 

Anchor
_Toc322593148 _Toc322593148

Anchor
_Toc350346800 _Toc350346800

Anchor
_Toc419708838 _Toc419708838

Anchor
_Toc458174621 _Toc458174621

Anchor
_Toc476646624 _Toc476646624

AgWorks

AgWorks AgOS v3

Anchor
_Toc350346801 _Toc350346801

Anchor
_Toc419708839 _Toc419708839

Anchor
_Toc458174622 _Toc458174622

Anchor
_Toc476646625 _Toc476646625

Feed Mill Manager

Is currently not supported.

Anchor
_Toc380746015 _Toc380746015

Anchor
Chapter1 Chapter1

Anchor
_Toc476646626 _Toc476646626

Chapter 1: Cinch Document Exchange

This chapter describes the miscellaneous changes made to Cinch Document Exchange.

This chapter contains the following modifications:

• New AgXML 4.0 Sales Contract Export
• New AgXML 4.0 Sales Contract Import
• New OneWeigh Ship Company Export
• New AgXML 4.0 In Transit-In Export

Anchor
NewAgXML40SalesContractExport NewAgXML40SalesContractExport

Anchor
_Toc476646627 _Toc476646627

New AgXML 4.0 Sales Contract Export

AgXML 4.0 Sales Contract Export has been created to generate an XML file for the Sales Contract and pricing records for selected customers.

...

1. 1. Supported Exchange Partner Filters
      1. LOCNCODE is optional.
         1. Blank or * will send all sites.
         2. Enter a Site ID filters all documents on an exact Site match. Only one Site ID can be entered per service partner.
      2. IRRegionID is optional.
         1. Blank or * will send all regions.
         2. Enter a Region ID filters all documents on an exact Region match. Only one Region ID can be entered per service partner.
      3. IRBranchID is optional.
         1. Blank or * will send all branches.
         2. Enter a Branch ID filters all documents on an exact Branch match. Only one Branch ID can be entered per service partner
   2. Service Line Setting
      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 seller 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.
            1. Company will translate to the GP Company main address. Default = Company
            2. Branch will translate to the Cinch Branch address.
            3. Location will translate to the address on the Site ID.
      3. Export Posted Changes
         1. Yes, when selected updates to a posted sales contract will export.
         2. No, when selected updates to a posted sales contract will NOT be exported. Default = No
      4. Export Sub Items
         1. Yes, will add CINCH specific fields.
         2. No, will conform to AgXML version 4 specifications AgXML_v4.0.xsd (schema). Default = No
      5. 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 contract 1234 will write a file called 1234.xml).
      6. XML Namespace Prefix
         1. Recommended to leave this field blank.
            1. For specific XML naming requirements. Prefixes each tag with this value.
      7. XML Namespace URL
         1. Recommended to leave this field blank.
            1. Puts the XML namespace URL in the header of each document.

Anchor
NewAgXML40SalesContractImport NewAgXML40SalesContractImport

Anchor
_Toc476646628 _Toc476646628

New AgXML 4.0 Sales Contract Import

AgXML 4.0 Sales Contract Import has been created to create Sales Contracts and contract pricing records based on the XML file.

...

• Spot and Other Contract Types are not currently supported.
• Edits are only allowed for unposted contracts. Edits sent to a posted contract will be stopped within Document Monitor stating "Editing of posted Contracts is not supported in this version of eConnect."
• During import of contract records generated from the Excel Purch Ctr Import 01 adapter:
  • The discount schedule on the contract will get defaulted from Branch/Item Default maintenance.
    • This will only happen if the Consume Pricing Info setting is set to "Yes", and if it hasn't been included in the xml.
  • The program schedule on the contract will get defaulted from the Vendor extensions.
    • This will only happen if the Consume Pricing Info setting is set to "Yes", and only if it hasn't been included in the xml.
      • • The Contract Type will default to Cash.

Anchor
_Toc469034931 _Toc469034931

Anchor
OneWeighShipCompanyExport OneWeighShipCompanyExport

Anchor
_Toc476646629 _Toc476646629

New OneWeigh Ship Company Export

OneWeigh Ship Company Export has been created to export Cinch Ship Companies in the OneWeigh Name/Address record format.

...

• 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.

...