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 6 Next »

TABLE OF CONTENTS:

CINCH 16.1

Unable to render {include} The included page could not be found.

CINCH 16.0






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.

CINCH 12.3

This chapter describes the miscellaneous changes made to Cinch Document Exchange.
This chapter contains the following sections:


Change to AgXML 4.0 Load Export
AgXML 4.0 Load Export has been modified to allow deleted load transactions to be exported.

  1. AgXML 4.0 Load Export
    1. Service Line Settings
      1. Send reused Load#s as Adds
        1. Yes, when selected the XML Action type will be forced to Add regardless if the load is new or an update to an existing load.
        2. Default = No


New CSV Sales Shipment Import 01
The New CSV Sales Shipment Import 01 takes a comma delimited file and converts it to an xml document conforming to the CIDX 4.0 Product Movement Report schema. The newly created xml document can be written to a location where a configured CIDX 4.0 Sales Shipment Import pipe can pick it up and import it into Cinch as a Sales Shipment.

  1. CSV Sales Shipment Import 01
  2. Support Exchange Partner Filters
    1. No filters apply
  3. Service Line Settings
  4. Message Label Extension
              1. The file extension of the export file. This extension can be anything but we recommended you use XML for easy viewing in IE.
            2. Sales Shipment Port Type, Sales Shipment Port URL and Sales Shipment Path:
              1. These settings need to match the CIDX 4.0 Sales Shipment Import header settings for this service.


Processing Note:

  • File Layout/mapping is as follows:
    • Fulfill Order #, column A – a valid GP Order Number being fulfilled.
    • Fulfill Order Line ID, column B – a valid GP Order Line ID used to specify the line being fulfilled.
      • If the fulfilled order row id is empty, the system will attempt to match the shipment based on Item ID.
    • Ship Date, column C
    • Location, column D, a valid GP inventory site.
    • Unit of Measure, column E, ship quantity U of M
    • Item ID, column F, a valid GP Inventory Item
    • Quantity Shipped, column G
    • Shipping Method, column H, a valid GP Ship Method.


Changes to CIDX 4.0 Sales Shipment Import
CIDX 4.0 Sales Shipment Import has been updated with additional service setting options to support using values provided from the CSV Sales Shipment Import 01 file.

  1. CIDX 4.0 Sales Shipment Import
  2. Service Line Settings
    1. Default Payment Terms From
      1. XML, payment term from the xml document will be used.
    2. Ship Method
      1. If a ship method exists in xml, it will be used. Otherwise it will use the default ship method value.

Processing Note:

  • Sales Shipments created from a file created from CSV Sales Shipment Import 01, the following will come from the specified Sales Order:
    • Branch
    • Customer ID
    • Customer Bill To
    • Customer Ship To
    • Payment Terms ID
  • After the Sales Shipment is imported user will navigate to Shipment Invoicing to create invoice(s).
  • Use location id for Ship To needs to be set to yes for the Order Ship To to be placed on the Shipment.
  • A shipment cannot be imported if associated to a closed Sales Order.


New CIDX 2.02 IAU Export
CIDX 2.02 IAU Export has been created to provide the ability to export Inventory Actual Usage documents for reporting inventory quantities back to vendors.

  1. CIDX 2.02 IAU Export Processor
    1. Supported Exchange Partner Filters
      1. Vendor filters apply
        1. Vendor ID is required. Only one vendor can be entered per service partner.
    2. Service Setting
      1. Always Translate Header IDs
        1. Yes, the From and To identifiers in the xml Header will use the value from the Entity ID Source setting as the Domain when performing the translations. (DUNS, AssignedBySeller, etc.)
        2. No, the default domain will be used for translations.
      2. Entity ID Sources is use to determine which "Agency" type for entities (buyer, seller, etc.) are selected during the export. The list of appropriate values are:
        1. Default, AssignedByBuyer, AssignedBySeller, DUNS,
          1. When DUNS is selected, the Entity ID will be pulled from the DUNS identifier for the appropriate master record (vendor, location, company, etc.), and a translation will not be performed.
          2. Default, AssignedByBuyer, AssignedBySeller, are not listed in the schema, but is a CinchX specific setting. When any of these are selected system will send the Cinch or translated value.
          3. Default is the default value.
      3. Hide Successful Item Trx Msgs
        1. Yes when selected only Item (and UofM) translations that fail will display in the document monitoring windows.
      4. Item Class Filter
        1. Default = *
        2. Enter a single Item Class or list of Item Classes.
          1. Each filter needs to be entered on a separate line.
          2. Multiple filters can be pasted at once into the drop down list box.
          3. An asterisk or empty string value will be treated as allow all, or, do not filter by this item.
          4. An item class prefix mask can be used to filter by records that match the prefix.
          5. Line items must have a matching Item Class in this list to be exported.
      5. Item ID Source is used to determine which "Agency" type for items are selected during the export. The list of appropriate values are:
        1. Default, ANSI, AssignedByBuyer, AssignedByManufacturer, AssignedBySeller, EAN, EDIFACT, GBABA, ISO, Other, UPC.
          1. When AssignedByManufacturer is selected a second Product Identifier with an Agency type of AssignedByManufacturer will be created in the XML for the Vendor Item Number from Item Vendor Maintenance.
          2. Default, ANSI, AssignedByBuyer, AssignedBySeller, EAN, EDIFACT, GBABA, ISO, Other, UPC are not listed in the schema, but is a CinchX specific setting. When any of these are selected system will send the Cinch or translated value.
          3. Default is the default value.
      6. Item User Category 1 Filter - Item User Categories are setup on Item Maintenance Options window.
        1. Default = *
        2. Enter an Item User Category 1 filter or list of Item User Category 1 filters.
          1. Each filter needs to be entered on a separate line.
          2. Multiple filters can be pasted at once into the drop down list box.
          3. An asterisk or empty string value will be treated as allow all, or, do not filter by this item.
          4. A user category prefix mask can be used to filter by records that match the prefix.
          5. Line items must have a matching Item User Category 1 in this list to be exported.
      7. Item User Category 2 Filter - Item User Categories are setup on Item Maintenance Options window.
        1. Default = *
        2. Enter an Item User Category 2 filter or list of Item User Category 2 filters.
          1. Each filter needs to be entered on a separate line.
          2. Multiple filters can be pasted at once into the drop down list box.
          3. An asterisk or empty string value will be treated as allow all, or, do not filter by this item.
          4. A user category prefix mask can be used to filter by records that match the prefix.
          5. Line items must have a matching Item User Category 2 in this list to be exported.
      8. Item User Category 3 Filter - Item User Categories are setup on Item Maintenance Options window.
        1. Default = *
        2. Enter an Item User Category 3 filter or list of Item User Category 3 filters.
          1. Each filter needs to be entered on a separate line.
          2. Multiple filters can be pasted at once into the drop down list box.
          3. An asterisk or empty string value will be treated as allow all, or, do not filter by this item.
          4. A user category prefix mask can be used to filter by records that match the prefix.
          5. Line items must have a matching Item User Category 3 in this list to be exported.
      9. Item User Category 4 Filter - Item User Categories are setup on Item Maintenance Options window.
        1. Default = *
        2. Enter an Item User Category 4 filter or list of Item User Category 4 filters.
          1. Each filter needs to be entered on a separate line.
          2. Multiple filters can be pasted at once into the drop down list box.
          3. An asterisk or empty string value will be treated as allow all, or, do not filter by this item.
          4. A user category prefix mask can be used to filter by records that match the prefix.
          5. Line items must have a matching Item User Category 4 in this list to be exported.
      10. Item User Category 5 Filter - Item User Categories are setup on Item Maintenance Options window.
        1. Default = *
        2. Enter an Item User Category 5 filter or list of Item User Category 5 filters.
          1. Each filter needs to be entered on a separate line.
          2. Multiple filters can be pasted at once into the drop down list box.
          3. An asterisk or empty string value will be treated as allow all, or, do not filter by this item.
          4. A user category prefix mask can be used to filter by records that match the prefix.
          5. Line items must have a matching Item User Category 5 in this list to be exported.
      11. Item User Category 6 Filter - Item User Categories are setup on Item Maintenance Options window.
        1. Default = *
        2. Enter an Item User Category 6 filter or list of Item User Category 6 filters.
          1. Each filter needs to be entered on a separate line.
          2. Multiple filters can be pasted at once into the drop down list box.
          3. An asterisk or empty string value will be treated as allow all, or, do not filter by this item.
          4. A user category prefix mask can be used to filter by records that match the prefix.
          5. Line items must have a matching Item User Category 6 in this list to be exported.
      12. 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 product 1234 will write a file called 1234.xml).
      13. Run Delay (# of days)
        1. This integer value field can be used to delay the export for a certain number of days after the interval occurs. This allows for things like exporting on the 3rd day of the month, or 180th day of the year.
        2. This setting is ignored when Run Interval is set to Daily
      14. Run Interval
        1. Select the interval at which the IAU documents will get exported.
          1. Available values in the dropdown list are Daily, Weekly, Monthly, Yearly.
          2. Default value is Monthly.
      15. Run Time
        1. Select the time of day that the export will occur after the interval has fired.
      16. Use UN/CEFACT for UofM Values
        1. Yes, when selected the standard UN/CEFACT (UN-Rec-20) units of measure will be sent describing quantities in the xml document. Default = Yes
          1. If the UN/CEFACT is not found the export will fail.
        2. No, when selected the standard Cinch, or translated values will be sent.
      17. XML Namespace Prefix
        1. Recommended to leave this field blank.
          1. For specific XML naming requirements. Prefixes each tag with this value.
      18. XML Namespace URL
        1. Recommended to leave this field blank.
          1. Puts the XML namespace URL in the header of each document.


New CIDX 4.0 IAU Export
CIDX 4.0 IAU Export has been created to provide the ability to export Inventory Actual Usage documents for reporting inventory quantities back to vendors.

  1. CIDX 4.0 IAU Export
    1. Supported Exchange Partner Filters
      1. Vendor filters apply
        1. Vendor ID is required. Only one vendor can be entered per service partner.
    2. Service Setting
      1. Always Translate Header IDs
        1. Yes, the From and To identifiers in the xml Header will use the value from the Entity ID Source setting as the Domain when performing the translations. (DUNS, AssignedBySeller, etc.)
        2. No, the default domain will be used for translations.
      2. Entity ID Sources is use to determine which "Agency" type for entities (buyer, seller, etc.) are selected during the export. The list of appropriate values are:
        1. Default, AGIIS-EBID, AGIIS-NAPD, AssignedByBuyer, AssignedByPapiNet, AssignedBySeller, AssignedByTestingLaboratory, DUNS, EAN, Other, SCAC
          1. When DUNS or AGIIS-EBID is selected, the Entity ID will be pulled from the DUNS identifier for the appropriate master record (vendor, location, company, etc.), and a translation will not be performed.
          2. Default, AGIIS-NAPD, AssignedByBuyer, AssignedByPapiNet, AssignedBySeller, AssignedByTestingLaboratory, EAN, Other or SCAC are not listed in the schema, but is a CinchX specific setting. When any of these are selected system will send the Cinch or translated value.
          3. Default is the default value.
      3. Hide Successful Item Trx Msgs
        1. Yes when selected only Item (and UofM) translations that fail will display in the document monitoring windows.
      4. Item Class Filter
        1. Default = *
        2. Enter a single Item Class or list of Item Classes.
          1. Each filter needs to be entered on a separate line.
          2. Multiple filters can be pasted at once into the drop down list box.
          3. An asterisk or empty string value will be treated as allow all, or, do not filter by this item.
          4. An item class prefix mask can be used to filter by records that match the prefix.
          5. Line items must have a matching Item Class in this list to be exported.
      5. Item ID Source is used to determine which "Agency" type for items are selected during the export. The list of appropriate values are:
        1. Default, AGIIS-ProductID, ANSI, AssignedByBuyer, AssignedByManufacturer, AssignedBySeller, EAN, EDIFACT, GBABA, ISO, Other, UPC.
          1. When AssignedByManufacturer is selected a second Product Identifier with an Agency type of AssignedByManufacturer will be created in the XML for the Vendor Item Number from Item Vendor Maintenance.
          2. When AGIIS-ProductID is selected, the Item ID will be pulled from the AGIIS Product ID (GTIN) from the Item Extensions Maintenance for the item, and a translation will not be performed.
          3. Default, ANSI, AssignedByBuyer, AssignedBySeller, EAN, EDIFACT, GBABA, ISO, Other, UPC are not listed in the schema, but is a CinchX specific setting. When any of these are selected system will send the Cinch or translated value.
          4. Default is the default value.
      6. Item User Category 1 Filter - Item User Categories are setup on Item Maintenance Options window.
        1. Default = *
        2. Enter an Item User Category 1 filter or list of Item User Category 1 filters.
          1. Each filter needs to be entered on a separate line.
          2. Multiple filters can be pasted at once into the drop down list box.
          3. An asterisk or empty string value will be treated as allow all, or, do not filter by this item.
          4. A user category prefix mask can be used to filter by records that match the prefix.
          5. Line items must have a matching Item User Category 1 in this list to be exported.
      7. Item User Category 2 Filter - Item User Categories are setup on Item Maintenance Options window.
        1. Default = *
        2. Enter an Item User Category 2 filter or list of Item User Category 2 filters.
          1. Each filter needs to be entered on a separate line.
          2. Multiple filters can be pasted at once into the drop down list box.
          3. An asterisk or empty string value will be treated as allow all, or, do not filter by this item.
          4. A user category prefix mask can be used to filter by records that match the prefix.
          5. Line items must have a matching Item User Category 2 in this list to be exported.
      8. Item User Category 3 Filter - Item User Categories are setup on Item Maintenance Options window.
        1. Default = *
        2. Enter an Item User Category 3 filter or list of Item User Category 3 filters.
          1. Each filter needs to be entered on a separate line.
          2. Multiple filters can be pasted at once into the drop down list box.
          3. An asterisk or empty string value will be treated as allow all, or, do not filter by this item.
          4. A user category prefix mask can be used to filter by records that match the prefix.
          5. Line items must have a matching Item User Category 3 in this list to be exported.
      9. Item User Category 4 Filter - Item User Categories are setup on Item Maintenance Options window.
        1. Default = *
        2. Enter an Item User Category 4 filter or list of Item User Category 4 filters.
          1. Each filter needs to be entered on a separate line.
          2. Multiple filters can be pasted at once into the drop down list box.
          3. An asterisk or empty string value will be treated as allow all, or, do not filter by this item.
          4. A user category prefix mask can be used to filter by records that match the prefix.
          5. Line items must have a matching Item User Category 4 in this list to be exported.
      10. Item User Category 5 Filter - Item User Categories are setup on Item Maintenance Options window.
        1. Default = *
        2. Enter an Item User Category 5 filter or list of Item User Category 5 filters.
          1. Each filter needs to be entered on a separate line.
          2. Multiple filters can be pasted at once into the drop down list box.
          3. An asterisk or empty string value will be treated as allow all, or, do not filter by this item.
          4. A user category prefix mask can be used to filter by records that match the prefix.
          5. Line items must have a matching Item User Category 5 in this list to be exported.
      11. Item User Category 6 Filter - Item User Categories are setup on Item Maintenance Options window.
        1. Default = *
        2. Enter an Item User Category 6 filter or list of Item User Category 6 filters.
          1. Each filter needs to be entered on a separate line.
          2. Multiple filters can be pasted at once into the drop down list box.
          3. An asterisk or empty string value will be treated as allow all, or, do not filter by this item.
          4. A user category prefix mask can be used to filter by records that match the prefix.
          5. Line items must have a matching Item User Category 6 in this list to be exported.
      12. 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 product 1234 will write a file called 1234.xml).
      13. Run Delay (# of days)
        1. This integer value field can be used to delay the export for a certain number of days after the interval occurs. This allows for things like exporting on the 3rd day of the month, or 180th day of the year.
        2. This setting is ignored when Run Interval is set to Daily
      14. Run Interval
        1. Select the interval at which the IAU documents will get exported.
          1. Available values in the dropdown list are Daily, Weekly, Monthly, Yearly
      15. Run Time
        1. Select the time of day that the export will occur after the interval has fired.
      16. Use UN/CEFACT for UofM Values
        1. Yes, when selected the standard UN/CEFACT (UN-Rec-20) units of measure will be sent describing quantities in the xml document. Default = Yes
          1. If the UN/CEFACT is not found the export will fail.
        2. No, when selected the standard Cinch, or translated values will be sent.
      17. XML Namespace Prefix
        1. Recommended to leave this field blank.
          1. For specific XML naming requirements. Prefixes each tag with this value.
      18. XML Namespace URL
        1. Recommended to leave this field blank.
          1. Puts the XML namespace URL in the header of each document.


Changes to CIDX 4.0 Sales Order Import
CIDX 4.0 Sales Order Import has been modified to watch for bulk items and when detected redirect them to CIDX 4.0 Load Import for further processing. In addition the Requested Delivery Date will be imported to the Sales User Defined Entry, User Date 01.

  1. CIDX 4.0 Sales Order Import
    1. Service Line Settings
      1. Fill UserDefDate1 w/sched date
        1. Yes, when selected the requested delivery date will be written to the User Date 01 field on the Sales User Defined Fields Entry window.
      2. Load Port URL, Load Port Type and LoadReq Path
        1. These settings need to match CIDX 4.0 Load Import header settings when the Watch for Load Orders setting is set to yes.
      3. Watch for Load Orders
        1. Yes, when selected the processor will look to the "Is Bulk" checkbox (located on the Hazmat Information screen off the item master) to determine if the translated item is bulk or not.
          1. If the item is a bulk item, further processing in this import will halt, and the xml document will be moved to the CIDX 4.0 Load Import setup in the Load Port/Path settings.
        2. If a bulk item is not detected, or this setting is set to No, this processor will continue to import the document as a normal sales order.


Changes to Excel Ticket Import 01
Excel Ticket Import 01 has been enhanced with the addition of the Send the On Track Number.

  1. Excel Ticket Import 01
    1. Service Line Settings
      1. Send On Track Number
        1. Yes, when selected the IROnTrack in the UserArea of the created XML will be populated.
          1. The On Track will be determined based on the order of the ticket in the excel document.
          2. AgXML 4.0 Ticket Import 4.0 and AgXML 4.0 In Transit-in Import looks for this data and will import it if the value exists.
        2. No when selected the IROnTrack will not be populated in the created XML.


Cinch Document Exchange with Multicurrency
The following describes the additional services that will work with Multicurrency.

Multicurrency supported services

  • AgXML 4.0 Purch Contract Export
  • AgXML 4.0 Purch Contract Import
  • AgXML 4.0 Purch Contr Price Export
  • AgXML 4.0 Purch Contr Price Import
  • Excel Purch Ctr Import 01
  • CIDX 2.02 Purchase Order Export
  • CIDX 2.02 Purchase Order Import
  • CIDX 4.0 Product Movement Export
  • CIDX 4.0 Purchase Order Export
  • CIDX 4.0 Purchase Order Import
  • CIDX 4.0 Sales Order Export
  • CIDX 4.0 Sales Order Import
  • CIDX 5.0 Product Movement Export
  • CIDX 5.0 Purchase Order Export
  • CIDX 5.0 Purchase Order Import
  • CIDX 5.2 Product Movement Export
  • CIDX 5.2 Purchase Order Export
  • CIDX 5.2 Purchase Order Import

CINCH 12.2

This chapter describes miscellaneous enhancements made to Cinch Document Exchange.
This chapter contains the following sections:


Changes to AgXML 4.0 In Transit-In Import
In Transit-In Import has been enhanced to allow cross branch application of Inbound In-Transit Scale Tickets.

  1. Process In Transit-In Import
  2. Service Line Settings
  3. One Assembly per Unit Train
              1. When set to Yes, a new assembly will be created for each unit train imported.
                1. Cross Branch application, Contract Number will be supplied within the import file, if the In Transit Ticket branch is different than the contract number, the system will duplicate the contract assembly and apply the in transit tickets to the newly created assembly.
              2. When set to No, system will import all tickets to the same assembly.
  4. Import as Barge
              1. Yes, when selected will create the In Transit Ticket and update the Barge with the information from the imported In Transit Ticket.
              2. No when selected will process the In Transit Ticket as normal.


Processing Notes:

  • If Import as Barge is set to yes, a Unit Number is required and will be the Barge Number that will be created.
  • A Purchase Contract is required when importing a barge.
  • The Barge Entry will be updated/created based on the imported In Transit Ticket. The Barge Entry Origination Weights, Grades and BOL Date will be populated with the information from the imported In Transit Ticket.
  • If the Barge does not exist one will be created.
  • Ship Company or Ship Method must be setup with Shipping Category of Barge.
  • (Compuweigh cannot handle a mode of "Barge" so the XML always says "Rail" as the mode even if it's actually a barge).


Changes to AgXML 4.0 Ticket Import
AgXML 4.0 Ticket Import has updated to support importing of Tickets with Barge.

  1. AgXML 4.0 Ticket Import
  2. Service Line Settings
  3. Import as Barge
              1. Yes, when selected will create the In Transit Unload Scale Ticket and update the Barge with the destination information from the imported Scale Ticket.
                1. The system will look to the Ticket for the Barge (in order to find the correct voyage) then to the Barge table, if more than one exists, the import will error. Or if none exist, the import will error.
                2. The Unload process will update the Barge Entry Unload Date, Destination Weights Grades.
              2. No when selected will process the Scale Ticket as normal.
            2. Use SampleID as Grade Cert – This setting will determine which xml value will be added to the Cinch Grade Cert field.
              1. When set to No, it will act as it currently does, and store the value from the xml QualityCertificateHeader.QualityCertificateIdentifier element.
              2. When set to Yes, it will store the value from the QualityCertificateHeader.SampleInformation.SampleIdentifier element.


Processing Notes:

  • To support the In Transit Change Branch
    • System will compare the Branch/Site in the Unload Ticket import file to the Branch/Site on the In Transit Ticket if they are not the same the import it will fail.
    • If the In Transit Ticket has an Outbound Shipment associated when the In Transit Ticket is unloaded the direct shipment status and shipment number will flow to the Inbound Ticket and the Outbound Shipment will be updated with the Inbound Scale Ticket number created during the unload process. The weights and grades will not update the shipment.


New PMR Reconciliation Matching
Product Movement Reconciliation has been created to provide the ability to reconcile sales history transactions (invoices and returns) to a partner's spreadsheet of transactions.

  1. Open PMR Reconcile.

(Transactions>Cinch Doc Exchange>PMR Reconcile)

    1. PMR Reconcile will only display on the menu if one of the Product Movement Exp processors (CIDX 4.0, CIDX 5.0 or CIDX 5.5) is registered.
  2. Select Records to display, is used to narrow down the data displayed. When changing selection, the grid is updated immediately.
    1. All
    2. Matched when selected records where the Cinch and partner records that are matched will be displayed.
    3. Partially Matched when selected records where document and item match but the quantity may be different.
    4. All Unmatched when selected all unmatched records will be displayed.
    5. Cinch Unmatched when selected only unmatched Cinch records will be displayed.
    6. Partner Unmatched when selected only unmatched partner records will be displayed.
  3. Restrictions:
    1. Primary Owner checkbox
      1. When selected Cinch sales data that is split, will display the total quantities of the transaction line for each split partner.
      2. When not selected the transaction line quantity displayed is based on the split partner portion.
    2. Start and End Dates
      1. Restricts records by transaction date.
    3. Partner
      1. When a service partner exchange partner is selected the system will only load transactions that were sent through pipes configured with the currently selected exchange partner.
      2. Select * to not filter by this criteria.
    4. Manufacturer
      1. Restricts transactions that contain items from the currently selected manufacturer.
      2. Select * to not filter by this criteria.
    5. Item Cat 1 – 6
      1. Restricts transactions based on each corresponding item category.
      2. Select * to not filter by this criteria.
  4. Grid
    1. Will display transaction lines that met the restriction criteria.
    2. Coloring - The grid is shaded with different colors to denote different sections of the grid.
      1. The first column is a status column.
        1. = unmatched
        2. = partially matched
        3. = matched
      2. The white/gray columns are Cinch values.
      3. The light blue/blue columns are partner values from the spreadsheet.
      4. The light orange/orange column denotes quantity differences.
    3. Sorting - The data can be sorted by any column.
      1. Click in the column header, and the data will immediately sort by the data in that column. Clicking the same header again will reverse the order.
    4. Filtering – Certain columns have a filter button in the header.
      1. Clicking the filter button will show a drop down list containing the following. Clicking any of those items will limit your view to only show rows that match that criteria.
        1. All
        2. Custom
        3. Blanks
        4. NonBlanks
      2. Selecting Custom filter opens the filter dialog window which allow you to filter multiple ways.


      1. To remove a filter, click the filter button again, and choose the "All" option.
    2. Status column – The first column helps identify which records have matches, which ones have partial matches and which ones have no match.
  2. Open button is selected to locate the customer's formatted Excel spreadsheet and import the data.
  3. Redisplay when selected refreshes the data in the data grid based on Cinch Sales History Restrictions.
  4. Resend button will reprocess selected records that has a through CinchX Product Movement Report export where the record has the Partner defined.
  5. Reset button reset the window to default restrictions and clear the customer's import data allow the user to start over.
  6. Supported file format of the Excel spreadsheet is as follows:


Col

Field Name

Cinch Field Name

Comments

A

InvoiceNumber

Invoice Number

Invoice/Return

B

InvoiceDate

Invoice Date


C

LineNumber

Line Number


D

ProductID

Item ID

X-Ref to Vendor Item Number.

E

Quantity

Quantity


F

UnitOfMeasure

Unit Of Measure




New OneWeigh Load to Ticket Export
OneWeigh Load to Ticket Export has been created to take AgXML 4.0 Load Order Export files and translate it into an Agris Scale Ticket ASCII file format as an Estimated Scale ticket.

  1. OneWeigh Load to Ticket Export
    1. Supported Exchange Partner Filters
      1. No filters apply
    2. Service Line Settings
      1. OneWeigh Import Path
        1. The location CinchX will save the OneWeigh Scale Ticket files it creates.
      2. Message Label Extension
        1. The file extension of the export file
          1. It is recommended to use FIL.


Processing Note:

  • File Translation for record type of "GRNT0":
    • Import Record Type (Positon 1-6) = GRNT0
    • Inbound/Outbound (Positon 7) = O, Load Orders are outbound
    • Ticket Location (Positon 8-10) = Branch, translated
    • Ticket Number (Positon 11-17) = Ticket Number
    • Ticket Type (Positon 18) = R = Regular
    • Shipment Date (Positon 19-24) = Blank
    • Ship To/From Name ID (Positon 31-40) = Customer ID, translated
    • Commodity (Positon 41-42) = Item, translated
    • Shipper Name ID (Positon 54-63) = Shipping Method/Ship Company
    • Total Net Units = (Positon 103-115) = Ordered Qty
    • Add/Update Option (Positon 233)
      • 1 = Add
      • 2 = Act Wts & Grds Update – Load Order updates will be set to 2.
    • Ticket Status (Positon 245) = E, Estimate


New OneWeigh Inv Tkt Import
OneWeigh Inv Ticket Import has been created to take incoming OneWeigh inventory tickets and convert them to AgXML 4.0 Commodity Movement documents.

  1. OneWeigh Inv Ticket Import
    1. Supported Exchange Partner Filters
      1. No filters apply
    2. Service Line Settings
      1. Shipment Port Type, Shipment Port URL and Shipment Port Req Path
        1. These settings need to match shipment import header settings for this service.
      2. 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.


Processing Note:

  • The adapter will read the OneWeigh and create a new xml file for each ticket it finds in the file that matches the criteria.
  • A record type of "INVT0" must exist in the AGRIS ASCII File in order to make a ticket. If the record does not contain that type, system will ignore that record. A record type of "INVT0" indicates an Inventory Management Delivery Ticket record.
  • After the adapter has finished parsing, translating, and converting the file(s), it will place the newly created xml files in a folder where the AgXML 4.0 Shipment Import process can import them.
  • AGRIS supports the ability to import multiple items on the same scale ticket. This is accomplished using a scale ticket and line number. However, CINCH does not support this functionality. Therefore, all AGRIS scale tickets with more than one line number will create an error in CINCHX Document Monitoring and will NOT be imported.
  • File Translation for record type of "INVT0":
    • Record Type (Position 1-5) = INVT0
    • Ticket Status (Position 6) = Only final tickets will be imported, tickets with a status of anything other than "F" will be discarded.
    • Ticket Location (Position 7-9) = Site ID
    • Ticket Number (Position 10-15) = Ticket Number
    • Shipment Date (Position 18-23) = Ticket Date
    • Inventory Location Code (Position 37-39) = Branch
    • Inventory Item Number (Position 40-54) = Item
    • Order Number (Position 93-98) = Load Number, must exist in Cinch or it will fail in Doc Monitor.
    • Ship To Name ID (Position 186-195) = Customer ID
    • Shipper Name ID (Position 196-205) = Shipping Method
    • Quantity (Position 216-228) = Gross Quantity
    • Gross Weight (Position 255-264) = Gross Weight
    • Tare Weight (Position 265-274) = Tare Weight
  • File Translation for record type of "INVT2":
    • Remark = Comment adapter will concatenate the remark lines and add them to the Shipment comment.


New OneWeigh Sales Order Export
OneWeigh Sales Order Export has been created to take AgXML 4.0 Load Order documents and convert them to Agris OneWeigh Sales Order format.

  1. OneWeigh Sales Order Export
    1. Supported Exchange Partner Filters
      1. No filters apply
    2. Service Line Settings
      1. OneWeigh Import Path
        1. The location CinchX will save the OneWeigh Sales Order files it creates.
      2. Message Label Extension
        1. The file extension of the export file
          1. This is required to be FIL.


Processing Note:

  • On Hold Load Orders
    • To handle On Hold Orders correctly the AgXML 4.0 Load Order Export, Cinch Consumer should be set to Yes.
    • If a load order is created with an on hold status, it will not be exported.
    • If a load is created and then subsequently marked as "on hold" the system will send an update with an 'ORDER STATUS' set to a numeric value to 1.
  • Only records with 'ORDER STATUS' = "A" are visible and available in OneWeigh.
  • When the delivery period of the load has expired. The load becomes unavailable in OneWeigh.
  • The filenames will be based on the file that's created by Load Export, which is based on the Load number in Cinch.
  • The length of the CINCH Load Order Number will not exceed 6 digits. To support the use of a numeric key pad in AGRIS OneWeigh, the Load Prefix and Load Suffix will not be used when entering loads within Cinch.
  • The length of the Cinch Sales Contract Number will not exceed 7 digits.
  • File Translation for record type of "INVT0":
    • Import Record Type (Positon 1-5) = INVP0
    • Order Type (Positon 6) = S - for Sales Order
    • Order Status (Positon 7)
      • A = Active
      • 1 = On Hold
      • X = Cancelled (deleted)
    • Order Location (Positon 8-10) = Blank will default to current on import
    • Order Number (Positon 11-16) = Load Order Number
    • Order Line Number (Positon 17-18) = 01, Cinch only supports one item per load
    • Oder Date (Positon 19-24) = Load Order Date
    • Shipment Date (Positon 25-30) = Blank
    • Bill To Name ID Number (Positon 31-40) = Customer ID
    • Inventory Location Code (Positon 41-43) = Site ID
      • Translated value for Company ID
    • Inventory Item Number (Positon 44-53) = Item ID
    • Contract Number (Positon 93-99) = Contract ID, Cinch limits to 7 digits
    • Quantity UOM Code (Positon 106-109) = Quantity UOM
    • Price UOM Code (Positon 110-113) = Price UofM
    • Their Order Number (Positon 154-168) = Load Order Number
    • Ship To/From Name ID (Positon 190-199) = Customer ID
    • Shipper Name ID (Positon 200-209) = Shipping Method
    • Order Quantity (Positon 220-232) = Quantity
    • Unit Price (Positon 233-245) = Price
    • Add/Update Option (Positon 274) = 3, the system will either add the record to OneWeigh if it's a new record, or update if the record already exists in OneWeigh.
  • Translations will occur on the following
    • Partner ID
    • Company ID
      • AgXML 4.0 Load Order Export service setting, Company ID Source
    • Shipper ID
    • UofM
    • Item


Change to AgXML 4.0 Load Export
AgXML 4.0 Load Export has been modified to allow deleted load transactions to be exported.

  1. AgXML 4.0 Load Export
    1. Service Line Settings
      1. Allow Deletes
        1. Yes when selected the system will will use previously filled stage table data to populate the XML document. The only difference in the exported XML document is that the ActionType flag will now be set to "Delete".
          1. This setting is only used when creating a transaction within OneWeigh Sales Order Export to delete an order. Load Import will import as an edit, void or delete will not occur.
        2. No when selected any Loads that have been deleted in Cinch will be ignored by CinchX.
      2. Send Loads that are On Hold
        1. The AgXML 4.0 Load Order Export, Cinch Consumer should be set to Yes for the On Hold setting to be present in export file.
        2. Yes when selected On Hold Load Orders will be exported.
        3. No when selected:
          1. If a load order is created with an on hold status, it will not be exported.
          2. If a load is created and then subsequently marked as "on hold" the system will send an update.


Changes to OneWeigh Ticket Import
OneWeigh Ticket Import has been enhanced with the new service setting to allow item number translations to use a different "Domain" when performing the translation.

  1. OneWeigh Ticket Import
    1. Item ID Source – the Domain the item number translations will to use when performing the translation. This setting allows multiple pipes to convert and export the same item number different ways.
      1. This defaults to ONEWEIGH but is editable.
    2. Map inbound Other Reference to – defines where the data from the OneWeigh Other Reference field will written. Need to verify that the Ticket Import, Put Partner Doc # In, is not using the same value, if so the Ticket Import setting will rule.
      1. Bill of Lading
      2. UserDef1
      3. UserDef2


Processing Note:

  • The adapter will take the Sample Number value from the OneWeigh ticket ASCII file and add that value to the CommodityMovement.CommodityMovementQualityInformation.CommodityMovementActualQualityInformation.QualityCertificate.QualityCertificateHeader.SampleInformation.SampleIdentifier section of the xml.
  • The adapter will take the WeightCertificateHeader.IssueDateTime from the OneWeigh ticket and:
    • For inbound tickets, this will be used to set the Tare Time value.
    • For outbound tickets, this will be used to set the Gross Time value.


Cinch Document Exchange with Multicurrency
The following describes how Cinch Document Exchange will work with Multicurrency.
Processing Note:

  • Currency ID on Imports:
    • If the Currency ID is included within the XML it will be used.
    • If the Currency ID is not included within the XML:
      • System will look to the Currency ID defined on Customer Maintenance Options or Vendor Maintenance Options.
      • If the Currency ID is not defined on the Customer Maintenance Options or Vendor Maintenance Options, system will use the Functional Currency ID.
    • Currency ID will be updated during contract application providing the transaction has not been posted.
    • If the Discount Schedule within the XML has a different Currency ID than Currency ID determined for the transaction, the transaction will fail on import.


Multicurrency supported services

  • AgXML 4.0 Load Export
  • AgXML 4.0 Load Import
  • AgXML 4.0 In Transit-In Import
  • AgXML 4.0 Shipment Export
  • AgXML 4.0 Shipment Import
  • AgXML 4.0 Ticket Export
  • AgXML 4.0 Ticket Import
  • CIDX 4.0 Load Export
  • CIDX 4.0 Load Import
  • Excel Shipment Import 02
  • Excel Ticket Import 01

CINCH 12.1

This chapter describes the additional and miscellaneous modifications made to Cinch Document Exchange.
This chapter contains the following sections:


New CSV ProcessMfg Import 01
CSV ProcessMfg Import is an adapter used to convert lines in a csv document to an AgXML document for use by the Process Manufacturing Import service and places them in the designated path.

  1. Process Manufacturing Import
  2. Service Line Settings
  3. Message Label Extension
        1. The file extension of the export file.
  4. ProcessMfg Port Type, ProcessMfg Port URL and ProcessMfg Req Path
        1. These settings need to match Process Manufacturing Import header settings for this service.

Processing Note:

  • A file was not provided with line details and therefore not tested.
  • File Layout:
    • Field 2 (Tank/Number/Scale#) = User Defined 2.
    • Field 4 (Product ID) from file = Recipe ID.
      • Adapter places a –P at the end of the Recipe ID in the created file requiring the Recipe to be translated.
    • Field 8 (Date/Time) = Date.
    • Field 11 = Recipe Qty
    • Field 12 (Site ID) in the file = Default Site
    • Field 7 (Rail Car/Truck Number) = User Defined 1
    • Field 13 (Scale Ticket#) – is used to by adapter to track if record is new or updated.


New Process Manufacturing Import
Process Manufacturing Import has been created to import manufacturing data and create Process Manufacturing transactions within Cinch. A process manufacturing transaction will be created based on the provided Recipe ID and Quantity. The system will go to the Recipe to determine the "Consumed" and "Produced" line item details.

  1. Process Manufacturing Import
  2. Service Line Settings
  3. Batch by Hour
              1. The Date/Time that will be used in the determination of the batch will come from the Process Manufacturing transaction itself. (Unlike other CinchX services where this is based on the system date and time).
              2. System will append a number at the end of the batch indicating which timeslot the batch is for.
                1. Example, if system is setup to create a new batch every 6 hours, Tickets that are imported with transaction time from 12:00 am to 6:00 am will have a "00" at the end of the batch number, transaction with times from 6:01 to 12:00 noon will have "06", tickets from 12:00 noon to 18:00 will have "12", transaction with times from 18:01 to 23:99 will have a "18".
              3. If no transactions are imported during a particular timeslot, the system will not create that batch.
              4. If setting is left blank, the hours will not be included in the batch number.
  4. Batch Prefix
              1. Default = PRCMF
              2. The transaction will be saved in a batch with a format of BBXXMMDD (BB is the Branch prefix, XX is the Batch prefix, and MMDD is the user date (MM= Month and DD= Day) of the transaction import.
              3. Maximum number of characters 15, this includes the branch prefix, the batch prefix and the date suffix.
              4. If the batch does not exist it will be added
  5. Default Activity Code
        1. If the Activity Code is included within in file line detail, it will be placed on each transaction line.
        2. The Activity Code to place on each transaction line in the event it is not provided with in file line detail.
        3. If Activity Code is not provided or the service setting is not set it will be left blank on the transaction.
  6. Default Apply Cost
        1. If the Apply Cost is included within in file line detail, it will be placed on each transaction line.
        2. If line detail is not provided the Apply Cost from the Recipe will be used.
        3. If the Recipe does not have the Apply Cost defined the Default Apply Cost will be used on each transaction line.
  7. Default Branch
        1. A valid branch ID is required. All transactions will be created within this branch.
  8. Default Cost Method
        1. If the Cost Method is included within in file line detail, it will be placed on each transaction line.
        2. If line detail is not provided the Cost Method from the Recipe will be used.
  9. Default Location
        1. If the Site is included within in file, it will be placed on each transaction line.
        2. If the Recipe does not have the Site defined the Default location will be used on each transaction line.
        3. A valid Site is a required to process the transaction.
  10. Default Work Center
        1. If the Work Center is included within in file line detail, it will be placed on each transaction line.
        2. The Work Center to place on each transaction line in the event it is not provided with in file line detail.
        3. If Work Center is not provided or the service setting is not set it will be left blank on the transaction.
  11. Use Partner Doc#
        1. Yes when selected the MfgNumber included within the import file will be used. Defaults to Yes. When set to Yes, if this is not present the message will fail within Doc Monitor for missing number.
        2. No when selected the next Mfg Number will be used. If line details are not present this must be set to No.
  12. Use Recipe Qty As Actual Qty
        1. Yes when selected will use the RecipeQty as the actual qty of the transaction. Defaults to Yes.
        2. No when selected will use the quantities of the line details as the total actual quantity.
        3. If there are no line details provided, the system will make the Actual Qty equal to the Recipe Qty.
  13. User ID
              1. This is used to set the Cinch transactional user.
              2. Document is created/updated on behalf of the specified user. This must be a valid Microsoft Dynamics GP user.
              3. If blank, User ID specified in CinchX Global Settings will be used.


Processing Note:

  • Given the Recipe ID and the Recipe qty the Import service will create an un-posted manufacturing transaction similar to the way the Fill Recipe Item button works in Manufacturing Entry.
    • When no line details are provided, the system will make the Actual Qty equal to the Recipe qty.
    • If the line level details are provided (that is, produced and consumed items) the system will update the Recipe created lines with the actual Quantities and add any lines that were not included in the recipe.
    • If the Service is provided a Recipe and line level details, the system will create a process manufacturing transaction based on the Recipe. Then the Actual Quantities will be updated with the line level details.
      • If line details contain items that are not on the recipe. System will create the lines with the actual qty and leave the Recipe Qty at zero.
      • If the recipe contains items that are not on the lines detail, the system will create the line from the recipe using the recipe qty then update the actual Qty to zero.


New Lot Analysis Import
Lot Analysis Import has been created to import Lot Analysis records from an XML file and create Lot Analysis transactions within Cinch.

  1. Lot Analysis Import
  2. Service Line Settings
  3. Default Branch
        1. A valid branch ID is required. All transactions will be created within this branch.
  4. User ID
              1. This is used to set the Cinch transactional user.
              2. Document is created/updated on behalf of the specified user. This must be a valid Microsoft Dynamics GP user.
              3. If blank, User ID specified in CinchX Global Settings will be used.
            2. Auto generate TestID
              1. Yes when selected the processor will create a new Test ID if one is not present in the xml document. If one is present in the xml document it will be used.
              2. No when selected an error will be thrown if a Test ID is not included in the xml doc.


Processing Note:

  • The system will look to Lot Analysis Setup, Disable Analysis By Location checkbox. If site is not included within the xml this checkbox must be marked or the record will fail on import.
    • XML documents tested did not have the Site included so this checkbox had to be marked to import records.
  • Translations can be setup on the Item, Lot Number and Analysis ID.
  • Create and Update records:
    • CinchX will look for existing Test ID's with the same Item, Site and Lot Number, if one is found, the system will update it with the results. And add any new result records.
      • Test files only contained one test result.
    • If no existing Test ID is found, the system will create new analysis records. The newly created Lot Analysis Record will be marked as "Active". System will update any other Lot Analysis Records for the Item, Site and Lot to "In-Active".
    • Auto Generate Test ID, if Test ID is missing, the system will use a Test ID of "01". Test ID will start out at "01" and increment from there for each new test that comes in with the same item number, site, and lot number.


Changes to TouchPoint PO Import 01
TouchPoint PO Import 01 has been modified with the option to allow records to be imported to a database or creating a Purchase Order.

  1. TouchPoint PO Import 01
    1. New Service Settings
      1. Create Purchase Order
        1. Yes, when selected the processor will export CIDX Order Create documents to be consumed by CIDX Purchase Order Import.
        2. No, when selected the TouchPoint data will be directly inserted into Cinch tables where custom reports will be able to access the data. Default = No


Processing Note:

  • Two translations will be utilized in this adapter.
    • Branch will be used to translate the value from the TouchPoint header SOLDTO_ID field to a Cinch Branch ID. The translation Standard Value is the Cinch Branch, Cinch Value is the value from the file.
    • UOFM will be used to translate the value from the TouchPoint line UNIT_OF_MEASURE to a numeric factor that will be used to calculate Quantity in the OrderDtl table. The translation Standard Value is the Cinch UOM Value (numeric value), Cinch Value is the value from the file.
  • Data fields within the Order table:
    • BranchID – From TouchPoint file, SOLDTO_ID translated to Cinch Branch
    • VendorID – Hardcoded to 110960
    • OrderNumber – From TouchPoint file, DOCUMENT_NBR
    • OrderDate = System Date
    • SourceId - Hardcoded to 2
    • LastModifiedUserKey – Hardcoded to BF9CAEA3-BA12-4204-86AE-F48F335111A2.
    • LastModifiedDate = System Date
    • Note = Leave Blank
  • Data fields within the OrderDtl table
    • OrderDtlId - System generated to make record unique.
    • OrderId - From Order table
    • ItemId = From TouchPoint file, ITEM_NUMBER. This is compared to the Vendor Item ID and will be populated with the corresponding Item Number. (IV100103 – ItemNMBR)
    • UOMId - From TouchPoint file, UNIT_OF_MEASURE translated to Cinch UofM
    • Quantity - From TouchPoint file, UNITS * (translated UOM value)
    • Price - hardcode to 0


New Excel Load Import 04
Excel Load Import 04 has been created to take in the Murex Excel file and parse each line into an AgXML 4.0 Load record.

  1. Excel Load Import 04
  2. Service Line Settings
  3. Load Port Type, Load Port URL and Load Port Req Path
        1. These settings need to match load import header settings for this service.
        2. E-Markets support will guide you through the process of setting up this service. Please DO NOT change these setting prior to contacting support.
  4. 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: load 1234 will write a file called 1234.xml).
            2. Excel Worksheet Name
              1. This is the name of the specific worksheet in the Excel spreadsheet where the import information can be found.


Processing Note:

  • File Layout is as follows.
    • Column B, bol_ref = Load Number and Cust Ref 1
    • Column E, schedule_date = Scheduled Date
    • Column F, order_qty = Quantity
    • Column H, item = Item
    • Column J, uom_code = Unit of Measure
    • Column L, ship_mode = Ship Method
    • Column P, consignee = Cust Ref Ship to Name
    • Column Q, business_unit = Customer
    • Column W, agreement_id = Cust Ref 2
    • Column AM, consignee_addr_city = Cust Ref City
    • Column AN, consignee_addr_St = Cust Ref State
  • Customer, since the file will be consumed by the ethanol plant, the customer will be the marketer. Inside the file, there is a column called "business_unit". The Adapter will place the "business_unit" in the "Buyer" section of the XML document.
  • Customer Ref Details, the file contains Customer Reference Details (consignee, agreement number, consignee addr city", and consignee addr st. The adapter will place that information within the User section of the XML Document so that it populates the Customer Ref Details.
  • Since the file does not contain a Sales Contract, the adapter will leave the Contract ID node empty in the XML. Per standard CinchX Load Order import functionality, the system will leave the Sales Contract blank or, based on setup of the service, default a sales contract and sales contract delivery period. User will be expected to call up the Load Order within Cinch and add (or verify) the sales contract if a sales contract is needed on the load order.
  • AgXML 4.0 Load Import created from Excel Load Import 04 must have the following service settings set as follows:
    • Direct Ship Scenario A = Yes
    • Use Agent as Customer = No
    • Use location id for Ship-To = No
    • Fail on Ship-To address Match = No
    • Use Partner Doc# = Yes


New CSV Trade import 01
CSV Trade Import 01 has been created to take in the Murex file and parse each line into an FIXML 5.0 Trade Import record.

  1. CSV Trade Import 01
  2. Service Line Settings
  3. Trade Port Type, Trade Port URL and Trade Req Path
        1. These settings need to match the trade import header settings for this service.
        2. E-Markets support will guide you through the process of setting up this service. Please DO NOT change these setting prior to contacting support.
  4. 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: trade 1234 will write a file called 1234.xml).


Processing Note:

  • File Layout/mapping is as follows.
    • Offer Number is next available number
    • Trader ID – from trade import service
    • Branch - from trade import service
    • Date = Offer Date and Fill Date
    • Account = Hedge Account (translated)
    • F or O = Type (Futures/Options)
    • Trade Type = User Defined 2
    • Trade Description = User Defined 1
    • 1 or 2 = Action (1 = Buy, 2 = Sell)
    • Buy Quantity = # contracts
    • Sell Quantity = # contracts
    • Alpha Month = Board Month
    • Year = Board Year
    • R&N Commodity Code = Commodity (translated)
    • Commodity Description = Board of Trade (translated)
    • Month = Board Month
    • Strike = Strike Price
    • Trade Price Decimal = Price/Premium
    • Contract Size, always Full
    • Market Zone – defaults from Branch
    • Hedge Factor, always 1
    • Hedge Month, same as Board Month
    • Hedge Year, same as Board Year
  • Since the file does not contain a ticker symbol, the adapter will query the ticker based on board of trade id, month code, board year, and commodity.
    • On the Trade import, if no match is found or if multiple matches are found, the ticker will fail within Doc Monitor.


Changes to FIXML 5.0 Trade import
FIXML 5.0 Trade Import has been modified with new translations to handle the CSV Trade Import 01.

  1. FIXML 5.0 Trade Import


Processing Note:

  • Hedge Account translation, a new translation type has been created to support the translation of hedge accounts that will be passed in with the CSV Trade Import 01 adapter.
    • The processor will look and see if a hedge account is passed in, and if so perform a translation on it to get the Cinch value. However, if the Hedge Account setting is setup with anything but a blank, it will override anything passed in.
  • Ticker translation, the processor currently allows translation of ticker symbols to those in Cinch.
    • Since the CSV Trade Import 01 adapter files do not contain a ticker symbol, process will allow the ticker to be queried based on board of trade id, month code, board year, and commodity. If no match is found based on those items, or if multiple matches are found, the ticker will not be included on the trade.


Changes to AgXML 4.0 Ticket Import
AgXML 4.0 Ticket Import has updated to support updating grades on a posted scale ticket.

  1. AgXML 4.0 Ticket Import
  2. Service Line Settings
  3. Update Destination Grades Only
        1. Yes, when selected the processor will only update records within the IRGNTicketGradeWORK table. After the grades are updated, discounts will be recalculated and DPR adjustment records will be created if needed. Also the response ticket that is normally exported (containing the new ticket number), will not be exported.
        2. No, when selected records are imported to create/update tickets normally.
      2. Get document identifier from
        1. The setting is used to select which section of xml to use when looking for the document identifier. This will not be used as the ticket number, it will be used to identify that the file has been imported and recorded in the number key status table. This gives the Grades Only import more flexibility when searching for the previously imported ticket.
        2. Available options are Buyer, Seller, and File Name
          1. File Name will not work if the Ticket Import and Grade Ticket Import files are not the same.
      3. Grades Only – Original Partner
        1. Since it is required that the Grades Only import uses a separate service partner than the normal ticket import, this will only be set on the grade import service partner to identify the original service partner.
        2. Enter the PartnerID (not the name) of the pipe used to import the original ticket.


Processing Note:

  • Importing grade updates will require two separate Service Partners setup.
    • The first Service Partner is used to import/create the ticket.
      • The Update Destination Grades Only set to No.
      • Get document identifier from:
        • The Commodity Movement Identifier (Buyer or Seller) within the XML.
        • File name is can only be used if the Ticket Import and Grade Ticket Import have the same file name.
        • This setting has nothing to do with how the ticket number is created, it just helps determine if the record has already been imported.
    • The second Service Partner is used to update an existing tickets grades.
      • The Update Destination Grades Only set to Yes.
      • Get document identifier from:
        • This must match the setting for the first Service Partner setting
      • Grades Only – Original Partner set to the first Service Partner ID.
  • The System will NOT allow the update if any of the following exist:
    • If the posted Inbound Scale Ticket is applied to a closed Assembly.
    • If the posted Inbound Scale Ticket is applied to a Purchase type Assembly.
  • If the updated grade value causes a quantity change on the Inbound Scale Ticket (detail), the system will create a DPR Adjustment for the date that the Import occurred. And the adjustment description will be Ticket Grade Change.


New CSV Shipment Import 02
CSV Shipment Import 02 has been created to take in the Kennedy scale file and parse each line into an AgXML 4.0 Shipment record.

  1. CSV Shipment Import 02
  2. Service Line Settings
  3. Shipment Port Type, Shipment Port URL and Shipment Port Req Path
        1. These settings need to match shipment import header settings for this service.
        2. E-Markets support will guide you through the process of setting up this service. Please DO NOT change this setting prior to contacting support.
  4. 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: shipment 1234 will write a file called 1234.xml).


Processing Note:

  • File Layout is as follows.
    • Ticket # = Shipment Ticket Number
    • Date = Shipment Date
    • Commodity = Item
    • TONS is the Unit of Measure
    • Truck # = Vehicle ID
    • Load # = Load Number
    • Description = User Defined 1
    • Account Name = Driver
  • Customer number will be pulled from the load. If a matching load is not found in the system for one of the load numbers in the file, an error will be thrown in doc monitoring for that particular line.
  • Each file will typically contain multiple tickets. One line per ticket.


Changes to CIDX PO Export 2.02
CIDX PO Export 2.02 has been modified to export the Customer and the Customer's Ship To Address for Drop-Ship PO's. All other PO types will continue to use the Location Address from the PO Line.
Changes to CIDX PO Export 4.0
CIDX PO Export 4.0 has been modified to export the Customer and the Customer's Ship To Address for Drop-Ship PO's. All other PO types will continue to use the Location Address from the PO Line.
Changes to CIDX PO Export 5.0
CIDX PO Export 5.0 has been modified to export the Customer and the Customer's Ship To Address for Drop-Ship PO's. All other PO types will continue to use the Location Address from the PO Line.
Changes to CIDX PO Export 5.2
CIDX PO Export 5.2 has been modified to export the Customer and the Customer's Ship To Address for Drop-Ship PO's. All other PO types will continue to use the Location Address from the PO Line.


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