CINCH Customer Documentation

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »






CINCH Software
What's New – CINCHX Document Exchange
Version 16.0 M15
March 10, 2017


Introduction
Supported Version
Dynamics GP
AgWorks
Feed Mill Manager
Chapter 1: Cinch Document Exchange
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 Import

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.

Supported Version

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

Dynamics GP

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

AgWorks

AgWorks AgOS v3

Feed Mill Manager

Is currently not supported.

 

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

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. AgXML 4.0 Sales Contract Export

(Creates file for the Sales contract pricing records for selected customers.)

    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.


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.

  1. AgXML 4.0 Sales Contract Import

(Processes file to create or update Sales contract pricing records for selected customers.)

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

Processing Note:

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

New OneWeigh Ship Company Export

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

  1. OneWeigh Ship Company Export
    1. Service Settings
      1. Message Label Extension
        1. The file extension of the export file. It is recommended to use FIL.
      2. Name ID Type
        1. Choose which character to use for the Name/Address record "Name ID Type".
          1. This will default to S, but can be changed to whatever is setup in OneWeigh. Possible OneWeigh values are:
            1. C – Customer
            2. F-Farmer
            3. J- Joint
            4. S-Shipper
      3. Send ID Number
        1. Determine which identification number from the vendor (if any) to send.
          1. Choose EIN for the Electronic Identification Number to be sent, Employer ID# from Vendor Extensions Maintenance.
          2. Choose SSN for the social security number to be sent, Social Security # from Vendor Extensions Maintenance.
          3. Leave set to None to not export an identification number.
      4. User Defined1
        1. Used to map OneWeigh's user defined fields to Cinch's user defined/contact fields. Valid values are USERDEF1, USERDEF2, and CONTACT.
      5. User Defined2
        1. Used to map OneWeigh's user defined fields to Cinch's user defined/contact fields. Valid values are USERDEF1, USERDEF2, and CONTACT.
      6. User Defined3
        1. Used to map OneWeigh's user defined fields to Cinch's user defined/contact fields. Valid values are USERDEF1, USERDEF2, and CONTACT
      7. Vendor Class Filters
        1. If entered this must be a valid Microsoft Dynamics GP vendor class and each imported vendor will be assigned to this class
          1. Blank – all customer classes will be sent. Default = Blank
          2. * – all customer classes will be sent.
          3. Enter a single customer class or enter a comma separated list of customer classes.


Processing Note:

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


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 Export
    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.
  • No labels

✦✦✦

3820 Mansell Road, Suite 350 ✦ Alpharetta, GA 30022 ✦ www.GreenstoneSystems.com
© 2013 - 2024 Cultura Technologies, LLC. All Rights Reserved Worldwide.  Products and company names mentioned herein may be trademarks or registered trademarks of their respective owners.