CINCH Customer Documentation

Chapter 2_Cinch Document Exchange 12.3

Owned by Mike Terning
Last updated: Oct 25, 2018
13 min read

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.  

      1.  

        1.  

          1.  

            1.  

              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



✦✦✦

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.