Open

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. 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 the CINCH Software since General Release 18.57 MX.

Descriptions of the enhancements are divided into the following chapters:

Chapter 1, “CINCH Document Exchange“ describes miscellaneous enhancements made to CINCHX.

Chapter 2, “CINCH Grain Miscellaneous“ describes miscellaneous enhancements made to CINCH Grain.

Chapter 3, “New to Branch Transfer Entry “ describes an enhancement that allows the user to enter and/or require a Reason Code in Branch Transfer Entry.

Supported Version

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

Dynamics GP

Software Version: 18.6.1695 (2023)

KB4602608

Dex Version: (18.00.0028)

AgWorks

Is currently not supported.

Feed Mill Manager

Is currently not supported.

Chapter 1: CINCH Document Exchange

This chapter describes miscellaneous enhancements made to CINCHX.

This chapter contains the following section(s_:

Changes to AgXML 4.0 Purchase Load Export

Changes to AgXML 4.0 Sales Contract Import

Changes to AgXML 4.0 Ticket Import

Changes to AgXML 4.0 Purchase Load Export

A new setting has been added to the AgXML 4.0 Purchase Load Export service. (CIN-7859)

1. Write Farm Code in Reference

   1. Yes, the IRFarmID for the IRFarmCode, taken from the IRAGFarmMSTR table, will be added to the User Area Reference field within the XML only if there IS a Farm selected within the purchase load.

   2. No, the Purchase Load Order Reference will be set to the User Area Reference field (Existing functionality).

Changes to AgXML 4.0 Sales Contract Import

A new setting has been added to the AgXML 4.0 Sales Contract Import service. (CIN-6605)

1. Create Contract Amendment

   1. Yes, if an update is sent for a previously imported and posted sales contract, the system will update the contract and amendment records will be created.

   2. No, if an update is sent for a previously imported and posted sales contract, the system will update the contract, but an amendment record will not be created (existing functionality and default setting).

Changes to AgXML 4.0 Ticket Import

A new setting has been added to the AgXML 4.0 Ticket Import service. (CIN-7571)

1. Use Freight from Contract – works in conjunction with Ignore XML Freight.

   1. When Ignore Freight on XML is set to No and Use Freight from Contract is set to Yes, freight from XML is used. If freight details do not exist in the XML, then the freight from the contract will be used.

   2. When Ignore Freight on XML is set to No and Use Freight from Contract is set to No, freight from XML is used. If freight details do not exist in the XML, then freight is not set.

   3. When Ignore Freight on XML is set to Yes and Use Freight from Contract setup is set to Yes, freight from Contract will be considered. If freight details are not on the contract, then freight is not set.

   4. When Ignore Freight on XML setup is Yes and Use Freight from Contract setup is No – Freight is not considered.

Chapter 2: New Report Writer Functions for Settlements

This chapter describes two new report writer functions created to return previously invoiced discount amounts for each and\or all assemblies on a settlement. (CIN-3552).

The two RW functions are:

1. RW_GetSettlementInvoicedDiscAmt function returns the previously invoiced discount amount for all the assemblies on a settlement.

2. RW_GetAssemblyInvoicedDiscAmt function returns the previously invoiced discount amount for each individual assembly on a settlement.

Calculated Field Definition:

1. Result Type = Currency

2. Expression Type = Calculated

3. Functions Tab

   1. User-Defined

   2. Core = Project

   3. Function = RW_GetAssemblyInvoicedDiscAmt or RW_GetSettlementInvoicedDiscAmt

   4. Select Add

4. Fields Tab

   1. Resources = IRGNSettlementHDRHIST, IRGNSettlementHDRWORK or IRGNAssemblyHDRWORK

   2. Field = IRAssemblyNumber or IRSettlmentNumber

   3. Select Add

5. Expressions

   1. Calculated

      1. Function_Script (RW_GetSettlementInvoicedDiscAmt IRGNSettlementHDRHIST.IRSettlementNumber) or

Function_Script (RW_GetAssemblyInvoicedDiscAmt IRGNAssemblyHDRWORK.IRAssemblyNumber)

1. True Case – NA

2. False Case - NA

Chapter 3: New to Branch Transfer Entry

This chapter describes an enhancement that allows the user to enter and/or require a Reason Code in Branch Transfer Entry. (CIN-7778)

This chapter contains the following section(s):

Changes to Branch Transfer Setup

Changes to Branch Transfer Entry

Changes to Branch Transfer Inquiry Zoom

Changes to Branch Transfer Setup

A new setting called Require Reason has been added to Branch Transfer Setup window.

Open Branch Transfer Setup

1. Require Reason

   1. Unmarked, default, a Reason Code is not required to save or process a branch transfer.

   2. Marked, the Reason Code field will act as a required field within Branch Transfer Entry.

Changes to Branch Transfer Entry

A new field called Reason Code has been added to Branch Transfer Entry window.

Open Branch Transfer Entry

1. Reason Code

   1. Required field when Require Reason checkbox is marked within Branch Transfer Setup.

   2. Enter or select a Reason Code for the transfer.

Changes to Branch Transfer Inquiry Zoom

A new field called Reason Code has been added to Branch Transfer Inquiry Zoom.

Open Branch Transfer Inquiry Zoom

1. Reason Code

   1. Default disabled.

   2. Displays the respective reason code entered in Branch Transfer Entry.

Appendix A: New Windows, Report & Tables

NEW Windows

NEW Reports

NEW Tables

Changes that may affect Reports or Data

¹

^I