CINCH Customer Documentation

Chapter 2_Cinch Document Exchange 12.0

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

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


New CIDX 2.02 Purchase Order Export
CIDX 2.02 Purchase Order Export has been created to allow POs to be exported out of Cinch.

  1. CIDX 2.02 Purchase Order Export
    1. Supported Exchange Partner Filters
      1. Vendor ID is optional
        1. Blank or * will send all vendors.
        2. Enter a Vendor ID filters all documents on an exact Vendor Match. Only one Vendor ID can be entered per service partner.
    2. Service Line Settings
      1. Always Send Internal Item ID
        1. Yes. when selected the GP Item Number will be sent along with the item number type selected in the Item ID Source.
        2. No, only the item number type selected in the Item ID Source will be sent.
      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 and 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 setting.
      3. Export Quantities In Base UofM
        1. Yes, when selected the quantity values are exported in their equivalent Base UofM quantities.
        2. No, when selected quantity from the Purchase Order is exported. No is the default setting.
      4. 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, ISO, EAN, AssignedBySeller, AssignedByBuyer, ANSI, GBABA, EDIFACT, AssignedByManufacturer, Other
          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, ISO, EAN, AssignedBySeller, AssignedByBuyer, ANSI, GBABA, EDIFACT, and Other 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.
      5. Message Label Extension is used to decide what file extension written to the file system. (xml, txt, etc.)
      6. Sending Pricing
        1. Yes, when selected pricing from the line will be sent.
        2. No, when selected pricing will not be sent. Default = No
      7. 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.
          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.
      8. XML Namespace Prefix
        1. For specific XML naming requirements. Prefixes each tag with this value.
      9. XML Namespace URL
        1. Puts the XML namespace URL in the header of each document.

Processing Note:

  • Printing the PO in GP will trigger the system to export any new or updated PO's.
  • It is recommended on any changes to the PO that the user print the PO to reset the PO status and revision number to ensure all updates are sent.
  • The Order Create From Section of the schema identifies the entity that is sending the Order Document. The XML document will be filled with company name and address information.
  • The Order Create To Section of the schema identifies the entity that the document is being sent to. In this Purchase Order case it will be the Vendor, so the XML document will be filled with Vendor information from the purchase order.
  • The Partner section of the schema identifies partner:
    • Buyer will be the Name and Address from Company Master
    • Seller will be the Vendor ID from the Purchase Order
    • Ship To will be the Name and Address for the Site ID from the first line
    • Payer will be the Name and Address from Company Master
  • The product Identifier section of the schema identifies what item is being ordered. The XML document can contain multiple ways of identifying the product on order. As such, the export will create product identifiers per the following:
    • Item number. The Dynamics GP Item number on the purchase order line will create "ProductIdentifier" tag(s): ProductIdentification Agency = "AssignedByBuyer" and Product Identifier = Item ID.
    • Vendor Item Number. If the Dynamics GP Purchase Order Contains a Vendor Item Number, set the Item ID Source to AssignedByManufacturer then the export will create and additional product identifier tag(s). ProductIdentification Agency = "AssignedByManufacturer" and Product Identifier = Vendor Item ID.
  • PO Deletes – When Dynamics GP deletes a Purchase Order the record is removed and the data no longer exists to create the XML Document. So it is be recommended that Dynamics Purchase Orders are voided rather than deleted in Dynamics.
  • If a Ship Method is selected on the Purchasing Vendor Detail Entry window, and the Shipping Type for that Ship Method is a "Pickup" type, then the Ship Method will be translated and the value will be exported in the TransportMethodCode tag and the Ship From section will be populated with Vendor ship address info. Otherwise neither of those sections will be written.


New CIDX 4.0 Purchase Order Export
CIDX 4.0 Purchase Order Export has been created to allow POs to be exported out of Cinch.

  1. CIDX 4.0 Purchase Order Export
    1. Supported Exchange Partner Filters
      1. Vendor ID is optional
        1. Blank or * will send all vendors.
        2. Enter a Vendor ID filters all documents on an exact Vendor Match. Only one Vendor ID can be entered per service partner.
    2. Service Line Settings
      1. Always Send Internal Item ID
        1. Yes. when selected the GP Item Number will be sent along with the item number type selected in the Item ID Source.
        2. No, only the item number type selected in the Item ID Source will be sent.
      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. Export Quantities In Base UofM
        1. Yes, when selected the quantity values are exported in their equivalent Base UofM quantities.
        2. No, when selected quantity from the Purchase Order is exported. No is the default setting.
      4. 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 are a CinchX specific setting. When any of these are selected system will send the Cinch or translated value.
      5. Message Label Extension is used to decide what file extension written to the file system. (xml, txt, etc.)
      6. Sending Pricing
        1. Yes, when selected pricing from the line will be sent.
        2. No, when selected pricing will not be sent. Default = No
      7. 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.
          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.
      8. XML Namespace Prefix
        1. For specific XML naming requirements. Prefixes each tag with this value.
      9. XML Namespace URL
        1. Puts the XML namespace URL in the header of each document.

Processing Note:

  • Printing the PO in GP will trigger the system to export any new or updated PO's.
  • It is recommended on any changes to the PO that the user print the PO to reset the PO status and revision number to ensure all updates are sent.
  • The Order Create From Section of the schema identifies the entity that is sending the Order Document. The XML document will be filled with company name and address information.
  • The Order Create To Section of the schema identifies the entity that the document is being sent to. In this Purchase Order case it will be the Vendor, so the XML document will be filled with Vendor information from the purchase order.
  • The Partner section of the schema identifies partner:
    • Buyer will be the Name and Address from Company Master
    • Seller will be the Vendor ID from the Purchase Order
    • Ship To will be the Name and Address for the Site ID from the first line
    • Payer will be the Name and Address from Company Master
  • The product Identifier section of the schema identifies what item is being ordered. The XML document can contain multiple ways of identifying the product on order. As such, the export will create product identifiers per the following:
    • Item number. The Dynamics GP Item number on the purchase order line will create "ProductIdentifier" tag(s): ProductIdentification Agency = "AssignedByBuyer" and Product Identifier = Item ID.
    • Vendor Item Number. If the Dynamics GP Purchase Order Contains a Vendor Item Number, set the Item ID Source to AssignedByManufacturer then the export will create and additional product identifier tag(s). ProductIdentification Agency = "AssignedByManufacturer" and Product Identifier = Vendor Item ID.
  • PO Deletes – When Dynamics GP deletes a Purchase Order the record is removed and the data no longer exists to create the XML Document. So it is be recommended that Dynamics Purchase Orders are voided rather than deleted in Dynamics.
  • If a Ship Method is selected on the Purchasing Vendor Detail Entry window, and the Shipping Type for that Ship Method is a "Pickup" type, then the Ship Method will be translated and the value will be exported in the TransportMethodCode tag and the Ship From section will be populated with Vendor ship address info. Otherwise neither of those sections will be written.


New CIDX 5.0 Purchase Order Export
CIDX 5.0 Purchase Order Export has been created to allow POs to be exported out of Cinch.

  1. CIDX 5.0 Purchase Order Export
    1. Supported Exchange Partner Filters
      1. Vendor ID is optional
        1. Blank or * will send all vendors.
        2. Enter a Vendor ID filters all documents on an exact Vendor Match. Only one Vendor ID can be entered per service partner.
    2. Service Line Settings
      1. Always Send Internal Item ID
        1. Yes. when selected the GP Item Number will be sent along with the item number type selected in the Item ID Source.
        2. No, only the item number type selected in the Item ID Source will be sent.
      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, GLN, 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. When GLN is selected, the Entity ID will be pulled from the GLN identifier for the appropriate master record (vendor, location, company, etc.), and a translation will not be performed.
          3. 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. Export Quantities In Base UofM
        1. Yes, when selected the quantity values are exported in their equivalent Base UofM quantities.
        2. No, when selected quantity from the Purchase Order is exported. No is the default setting.
      4. 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.
      5. Message Label Extension is used to decide what file extension written to the file system. (xml, txt, etc.)
      6. Sending Pricing
        1. Yes, when selected pricing from the line will be sent.
        2. No, when selected pricing will not be sent. Default = No
      7. 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.
          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.
      8. XML Namespace Prefix
        1. For specific XML naming requirements. Prefixes each tag with this value.
      9. XML Namespace URL
        1. Puts the XML namespace URL in the header of each document.

Processing Note:

  • Printing the PO in GP will trigger the system to export any new or updated PO's.
  • It is recommended on any changes to the PO that the user print the PO to reset the PO status and revision number to ensure all updates are sent.
  • The Order Create From Section of the schema identifies the entity that is sending the Order Document. The XML document will be filled with company name and address information.
  • The Order Create To Section of the schema identifies the entity that the document is being sent to. In this Purchase Order case it will be the Vendor, so the XML document will be filled with Vendor information from the purchase order.
  • The Partner section of the schema identifies partner:
    • Buyer will be the Name and Address from Company Master
    • Seller will be the Vendor ID from the Purchase Order
    • Ship To will be the Name and Address for the Site ID from the first line
    • Payer will be the Name and Address from Company Master
  • The product Identifier section of the schema identifies what item is being ordered. The XML document can contain multiple ways of identifying the product on order. As such, the export will create product identifiers per the following:
    • Item number. The Dynamics GP Item number on the purchase order line will create "ProductIdentifier" tag(s): ProductIdentification Agency = "AssignedByBuyer" and Product Identifier = Item ID.
    • Vendor Item Number. If the Dynamics GP Purchase Order Contains a Vendor Item Number, set the Item ID Source to AssignedByManufacturer then the export will create and additional product identifier tag(s). ProductIdentification Agency = "AssignedByManufacturer" and Product Identifier = Vendor Item ID.
  • PO Deletes – When Dynamics GP deletes a Purchase Order the record is removed and the data no longer exists to create the XML Document. So it is be recommended that Dynamics Purchase Orders are voided rather than deleted in Dynamics.
  • If a Ship Method is selected on the Purchasing Vendor Detail Entry window, and the Shipping Type for that Ship Method is a "Pickup" type, then the Ship Method will be translated and the value will be exported in the TransportMethodCode tag and the Ship From section will be populated with Vendor ship address info. Otherwise neither of those sections will be written.


New CIDX 5.2 Purchase Order Export
CIDX 5.0 Purchase Order Export has been created to allow POs to be exported out of Cinch.

  1. CIDX 5.0 Purchase Order Export
    1. Supported Exchange Partner Filters
      1. Vendor ID is optional
        1. Blank or * will send all vendors.
        2. Enter a Vendor ID filters all documents on an exact Vendor Match. Only one Vendor ID can be entered per service partner.
    2. Service Line Settings
      1. Always Send Internal Item ID
        1. Yes. when selected the GP Item Number will be sent along with the item number type selected in the Item ID Source.
        2. No, only the item number type selected in the Item ID Source will be sent.
      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, GLN, 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. When GLN is selected, the Entity ID will be pulled from the GLN identifier for the appropriate master record (vendor, location, company, etc.), and a translation will not be performed.
          3. 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. Export Quantities In Base UofM
        1. Yes, when selected the quantity values are exported in their equivalent Base UofM quantities.
        2. No, when selected quantity from the Purchase Order is exported. No is the default setting.
      4. 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.
      5. Message Label Extension is used to decide what file extension written to the file system. (xml, txt, etc.)
      6. Sending Pricing
        1. Yes, when selected pricing from the line will be sent.
        2. No, when selected pricing will not be sent. Default = No
      7. 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.
          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.
      8. XML Namespace Prefix
        1. For specific XML naming requirements. Prefixes each tag with this value.
      9. XML Namespace URL
        1. Puts the XML namespace URL in the header of each document.

Processing Note:

  • Printing the PO in GP will trigger the system to export any new or updated PO's.
  • It is recommended on any changes to the PO that the user print the PO to reset the PO status and revision number to ensure all updates are sent.
  • The Order Create From Section of the schema identifies the entity that is sending the Order Document. The XML document will be filled with company name and address information.
  • The Order Create To Section of the schema identifies the entity that the document is being sent to. In this Purchase Order case it will be the Vendor, so the XML document will be filled with Vendor information from the purchase order.
  • The Partner section of the schema identifies partner:
    • Buyer will be the Name and Address from Company Master
    • Seller will be the Vendor ID from the Purchase Order
    • Ship To will be the Name and Address for the Site ID from the first line
    • Payer will be the Name and Address from Company Master
  • The product Identifier section of the schema identifies what item is being ordered. The XML document can contain multiple ways of identifying the product on order. As such, the export will create product identifiers per the following:
    • Item number. The Dynamics GP Item number on the purchase order line will create "ProductIdentifier" tag(s): ProductIdentification Agency = "AssignedByBuyer" and Product Identifier = Item ID.
    • Vendor Item Number. If the Dynamics GP Purchase Order Contains a Vendor Item Number, set the Item ID Source to AssignedByManufacturer then the export will create and additional product identifier tag(s). ProductIdentification Agency = "AssignedByManufacturer" and Product Identifier = Vendor Item ID.
  • PO Deletes – When Dynamics GP deletes a Purchase Order the record is removed and the data no longer exists to create the XML Document. So it is be recommended that Dynamics Purchase Orders are voided rather than deleted in Dynamics.
  • If a Ship Method is selected on the Purchasing Vendor Detail Entry window, and the Shipping Type for that Ship Method is a "Pickup" type, then the Ship Method will be translated and the value will be exported in the TransportMethodCode tag and the Ship From section will be populated with Vendor ship address info. Otherwise neither of those sections will be written.


New CIDX 2.02 PO Response Import
CIDX 2.02 Purchase Response Import has been created to import purchase order response which will update to the Dynamics GP Purchase Order, indicating if the Order has been accepted, or rejected by the Vendor.

  1. CIDX 2.02 Purchase Response Import
    1. Supported Exchange Partner Filters
      1. No filters apply
    2. Service Line Settings
      1. Default Branch
        1. A valid branch ID can be selected. If default branch is specified any unresolved buyer addresses will be forced to this specified branch.
        2. If blank, the buyer address in the AgXML must resolve to a location in the current company or the shipment will be rejected.
      2. 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:

  • Purchase Order Processing Setup, Allow Hold/Remove Hold of Purchase Orders checkbox is required to be marked to allow the purchase order to be placed on hold.
  • Regardless of status accept or reject, the Purchase Order Response Import will update the Dynamics Purchase Order Header Note with all special instructions form the Purchase Order Response XML Document. The reason for the rejection is contained in those "Special Instruction" XML tags. The Special Instructions can exist on the Header (Xpath-OrderResponseBody/OrderResponseProperties/SpecialInstructions) and/or on each line (Xpath-OrderResponseBody/OrderResponseDetails/OrderResponseProductLineItems/ SpecialInstructions). The import will append all the special instructions (header and Line) and place them in the Note field.
  • The Purchase Order Response will accept or reject the Purchase Order but will NOT update the PO with the new item, quantity or cost changes.
  • If the Order is accepted:
    • PO Status. The PO Status remains unchanged.
    • The Purchasing Vendor Detail, Confirm With field will be updated with the date accepted from the XML document and the word "accept".
  • If the Order is Rejected:
    • PO is placed On Hold, Hold checkbox is marked.
    • The Purchasing Date Inquiry, Placed On Hold by field will be set to the User ID defined on the Service Setting.
    • The Purchasing Date Inquiry, Placed On Hold Date will be set to the system date.
    • The Note is updated (appended) with the response.
    • If PO is rejected, we expect user to create a new PO that reflects any changes. User can then print that new Purchase Order so it gets exported.
    • If an additional response is received to Accept the PO after it has already been rejected, placed on hold, the Confirm With will be updated to Accepted but the PO will remain on hold. The user will need to determine what should be done based on the Notes.


New CIDX 4.0 PO Response Import
CIDX 4.0 Purchase Response Import has been created to import purchase order response which will update to the Dynamics GP Purchase Order, indicating if the Order has been accepted, or rejected by the Vendor.

  1. CIDX 4.0 Purchase Response Import
    1. Supported Exchange Partner Filters
      1. No filters apply
    2. Service Line Settings
      1. Default Branch
        1. A valid branch ID can be selected. If default branch is specified any unresolved buyer addresses will be forced to this specified branch.
        2. If blank, the buyer address in the AgXML must resolve to a location in the current company or the shipment will be rejected.
      2. 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:

  • Purchase Order Processing Setup, Allow Hold/Remove Hold of Purchase Orders checkbox is required to be marked to allow the purchase order to be placed on hold.
  • Regardless of status accept or reject, the Purchase Order Response Import will update the Dynamics Purchase Order Header Note with all special instructions form the Purchase Order Response XML Document. The reason for the rejection is contained in those "Special Instruction" XML tags. The Special Instructions can exist on the Header (Xpath-OrderResponseBody/OrderResponseProperties/SpecialInstructions) and/or on each line (Xpath-OrderResponseBody/OrderResponseDetails/OrderResponseProductLineItems/ SpecialInstructions). The import will append all the special instructions (header and Line) and place them in the Note field.
  • The Purchase Order Response will accept or reject the Purchase Order but will NOT update the PO with the new item, quantity or cost changes.
  • If the Order is accepted:
    • PO Status. The PO Status remains unchanged.
    • The Purchasing Vendor Detail, Confirm With field will be updated with the date accepted from the XML document and the word "accept".
  • If the Order is Rejected:
    • PO is placed On Hold, Hold checkbox is marked.
    • The Purchasing Date Inquiry, Placed On Hold by field will be set to the User ID defined on the Service Setting.
    • The Purchasing Date Inquiry, Placed On Hold Date will be set to the system date of the XML response document.
    • The Note is updated (appended) with the response.
    • If PO is rejected, we expect user to create a new PO that reflects any changes. User can then print that new Purchase Order so it gets exported.
    • If an additional response is received to Accept the PO after it has already been rejected, placed on hold, the Confirm With will be updated to Accepted but the PO will remain on hold. The user will need to determine what should be done based on the Notes.


New CIDX 5.0 PO Response Import
CIDX 5.0 Purchase Response Import has been created to import purchase order response which will update to the Dynamics GP Purchase Order, indicating if the Order has been accepted, or rejected by the Vendor.

  1. CIDX 5.0 Purchase Response Import
    1. Supported Exchange Partner Filters
      1. No filters apply
    2. Service Line Settings
      1. Default Branch
        1. A valid branch ID can be selected. If default branch is specified any unresolved buyer addresses will be forced to this specified branch.
        2. If blank, the buyer address in the AgXML must resolve to a location in the current company or the shipment will be rejected.
      2. 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:

  • Purchase Order Processing Setup, Allow Hold/Remove Hold of Purchase Orders checkbox is required to be marked to allow the purchase order to be placed on hold.
  • Regardless of status accept or reject, the Purchase Order Response Import will update the Dynamics Purchase Order Header Note with all special instructions form the Purchase Order Response XML Document. The reason for the rejection is contained in those "Special Instruction" XML tags. The Special Instructions can exist on the Header (Xpath-OrderResponseBody/OrderResponseProperties/SpecialInstructions) and/or on each line (Xpath-OrderResponseBody/OrderResponseDetails/OrderResponseProductLineItems/ SpecialInstructions). The import will append all the special instructions (header and Line) and place them in the Note field.
  • The Purchase Order Response will accept or reject the Purchase Order but will NOT update the PO with the new item, quantity or cost changes.
  • If the Order is accepted:
    • PO Status. The PO Status remains unchanged.
    • The Purchasing Vendor Detail, Confirm With field will be updated with the date accepted from the XML document and the word "accept".
  • If the Order is Rejected:
    • PO is placed On Hold, Hold checkbox is marked.
    • The Purchasing Date Inquiry, Placed On Hold by field will be set to the User ID defined on the Service Setting.
    • The Purchasing Date Inquiry, Placed On Hold Date will be set to the system date.
    • The Note is updated (appended) with the response.
    • If PO is rejected, we expect user to create a new PO that reflects any changes. User can then print that new Purchase Order so it gets exported.
    • If an additional response is received to Accept the PO after it has already been rejected, placed on hold, the Confirm With will be updated to Accepted but the PO will remain on hold. The user will need to determine what should be done based on the Notes.


New CIDX 5.2 PO Response Import
CIDX 5.2 Purchase Response Import has been created to import purchase order response which will update to the Dynamics GP Purchase Order, indicating if the Order has been accepted, or rejected by the Vendor.

  1. CIDX 5.2 Purchase Response Import
    1. Supported Exchange Partner Filters
      1. No filters apply
    2. Service Line Settings
      1. Default Branch
        1. A valid branch ID can be selected. If default branch is specified any unresolved buyer addresses will be forced to this specified branch.
        2. If blank, the buyer address in the AgXML must resolve to a location in the current company or the shipment will be rejected.
      2. 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:

  • Purchase Order Processing Setup, Allow Hold/Remove Hold of Purchase Orders checkbox is required to be marked to allow the purchase order to be placed on hold.
  • Regardless of status accept or reject, the Purchase Order Response Import will update the Dynamics Purchase Order Header Note with all special instructions form the Purchase Order Response XML Document. The reason for the rejection is contained in those "Special Instruction" XML tags. The Special Instructions can exist on the Header (Xpath-OrderResponseBody/OrderResponseProperties/SpecialInstructions) and/or on each line (Xpath-OrderResponseBody/OrderResponseDetails/OrderResponseProductLineItems/ SpecialInstructions). The import will append all the special instructions (header and Line) and place them in the Note field.
  • The Purchase Order Response will accept or reject the Purchase Order but will NOT update the PO with the new item, quantity or cost changes.
  • If the Order is accepted:
    • PO Status. The PO Status remains unchanged.
    • The Purchasing Vendor Detail, Confirm With field will be updated with the date accepted from the XML document and the word "accept".
  • If the Order is Rejected:
    • PO is placed On Hold, Hold checkbox is marked.
    • The Purchasing Date Inquiry, Placed On Hold by field will be set to the User ID defined on the Service Setting.
    • The Purchasing Date Inquiry, Placed On Hold Date will be set to the system date
    • The Note is updated (appended) with the response.
    • If PO is rejected, we expect user to create a new PO that reflects any changes. User can then print that new Purchase Order so it gets exported.
    • If an additional response is received to Accept the PO after it has already been rejected, placed on hold, the Confirm With will be updated to Accepted but the PO will remain on hold. The user will need to determine what should be done based on the Notes.


New CIDX 2.02 Ship Notice Import
CIDX 2.02 Ship Notice Import has been created to import data from ship notice xml documents which contain details as to the Purchase Order being shipped, including the items and quantities. The CIDX Ship Notice will be imported to a Cinch company database table for future reference.

  1. CIDX 2.02 Ship Notice Import
    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 the inbound tickets will be saved in that batch.
        2. Maximum number of characters 15.
        3. If the batch does not exist it will be added.
      3. Batch Prefix
        1. Default = CIDX
          1. If a batch prefix is entered the inbound tickets 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 15. This includes the branch prefix, the batch prefix and the date time suffix.
      4. Default Branch
        1. A valid branch ID can be selected. If default branch is specified any unresolved buyer addresses will be forced to this specified branch.
        2. If blank, the buyer address in the AgXML must resolve to a location in the current company or the shipment will be rejected.
      5. 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:

  • A multi-segment primary key has been added to each table. Starting with the header the combination of unique values is: 1. Document Number 2. IRShipFromID 3. Document Date 4. Date SEQ Number.
    • Since two suppliers could have the same document Identifier, the IRShipFromID solves that potential conflict. Also a supplier could send multiple updates, even within the same date. So Document Date and Date SEQ Number resolve that potential conflict.
  • Tables where data is placed for future reference are IRASShipNoticeHDR, IRASShipNoticeRef and IRASShipNoticeLine


New CIDX 3.0 Ship Notice Import
CIDX 3.0 Ship Notice Import has been created to import data from ship notice xml documents which contain details as to the Purchase Order being shipped, including the items and quantities. The CIDX Ship Notice will be imported to a Cinch company database table for future reference.

  1. CIDX 3.0 Ship Notice Import
    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 the inbound tickets will be saved in that batch.
        2. Maximum number of characters 15.
        3. If the batch does not exist it will be added.
      3. Batch Prefix
        1. Default = CIDX
          1. If a batch prefix is entered the inbound tickets 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 15. This includes the branch prefix, the batch prefix and the date time suffix.
      4. Default Branch
        1. A valid branch ID can be selected. If default branch is specified any unresolved buyer addresses will be forced to this specified branch.
        2. If blank, the buyer address in the AgXML must resolve to a location in the current company or the shipment will be rejected.
      5. 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:

  • A multi-segment primary key has been added to each table. Starting with the header the combination of unique values is: 1. Document Number 2. IRShipFromID 3. Document Date 4. Date SEQ Number.
    • Since two suppliers could have the same document Identifier, the IRShipFromID solves that potential conflict. Also a supplier could send multiple updates, even within the same date. So Document Date and Date SEQ Number resolve that potential conflict.
  • Tables where data is placed for future reference are IRASShipNoticeHDR, IRASShipNoticeRef and IRASShipNoticeLine


New CIDX 4.0 Ship Notice Import
CIDX 4.0 Ship Notice Import has been created to import data from ship notice xml documents which contain details as to the Purchase Order being shipped, including the items and quantities. The CIDX Ship Notice will be imported to a Cinch company database table for future reference.

  1. CIDX 4.0 Ship Notice Import
    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 the inbound tickets will be saved in that batch.
        2. Maximum number of characters 15.
        3. If the batch does not exist it will be added.
      3. Batch Prefix
        1. Default = CIDX
          1. If a batch prefix is entered the inbound tickets 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 15. This includes the branch prefix, the batch prefix and the date time suffix.
      4. Default Branch
        1. A valid branch ID can be selected. If default branch is specified any unresolved buyer addresses will be forced to this specified branch.
        2. If blank, the buyer address in the AgXML must resolve to a location in the current company or the shipment will be rejected.
      5. 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:

  • A multi-segment primary key has been added to each table. Starting with the header the combination of unique values is: 1. Document Number 2. IRShipFromID 3. Document Date 4. Date SEQ Number.
    • Since two suppliers could have the same document Identifier, the IRShipFromID solves that potential conflict. Also a supplier could send multiple updates, even within the same date. So Document Date and Date SEQ Number resolve that potential conflict.
  • Tables where data is placed for future reference are IRASShipNoticeHDR, IRASShipNoticeRef and IRASShipNoticeLine


New CIDX 5.0 Ship Notice Import
CIDX 5.0 Ship Notice Import has been created to import data from ship notice xml documents which contain details as to the Purchase Order being shipped, including the items and quantities. The CIDX Ship Notice will be imported to a Cinch company database table for future reference.

  1. CIDX 5.0 Ship Notice Import
    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 the inbound tickets will be saved in that batch.
        2. Maximum number of characters 15.
        3. If the batch does not exist it will be added.
      3. Batch Prefix
        1. Default = CIDX
          1. If a batch prefix is entered the inbound tickets 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 15. This includes the branch prefix, the batch prefix and the date time suffix.
      4. Default Branch
        1. A valid branch ID can be selected. If default branch is specified any unresolved buyer addresses will be forced to this specified branch.
        2. If blank, the buyer address in the AgXML must resolve to a location in the current company or the shipment will be rejected.
      5. 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:

  • A multi-segment primary key has been added to each table. Starting with the header the combination of unique values is: 1. Document Number 2. IRShipFromID 3. Document Date 4. Date SEQ Number.
    • Since two suppliers could have the same document Identifier, the IRShipFromID solves that potential conflict. Also a supplier could send multiple updates, even within the same date. So Document Date and Date SEQ Number resolve that potential conflict.
  • Tables where data is placed for future reference are IRASShipNoticeHDR, IRASShipNoticeRef and IRASShipNoticeLine


New CIDX 5.2 Ship Notice Import
CIDX 5.2 Ship Notice Import has been created to import data from ship notice xml documents which contain details as to the Purchase Order being shipped, including the items and quantities. The CIDX Ship Notice will be imported to a Cinch company database table for future reference.

  1. CIDX 5.2 Ship Notice Import
    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 the inbound tickets will be saved in that batch.
        2. Maximum number of characters 15.
        3. If the batch does not exist it will be added.
      3. Batch Prefix
        1. Default = CIDX
          1. If a batch prefix is entered the inbound tickets 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 15. This includes the branch prefix, the batch prefix and the date time suffix.
      4. Default Branch
        1. A valid branch ID can be selected. If default branch is specified any unresolved buyer addresses will be forced to this specified branch.
        2. If blank, the buyer address in the AgXML must resolve to a location in the current company or the shipment will be rejected.
      5. 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:

  • A multi-segment primary key has been added to each table. Starting with the header the combination of unique values is: 1. Document Number 2. IRShipFromID 3. Document Date 4. Date SEQ Number.
    • Since two suppliers could have the same document Identifier, the IRShipFromID solves that potential conflict. Also a supplier could send multiple updates, even within the same date. So Document Date and Date SEQ Number resolve that potential conflict.
  • Tables where data is placed for future reference are IRASShipNoticeHDR, IRASShipNoticeRef and IRASShipNoticeLine


Changes to CIDX 4.0 Product Movement Export
CIDX Product Movement Export has been renamed to CIDX 4.0 Product Movement Export and modified to create additional filters to further restrict transactions to a specific pipe.

  1. CIDX 4.0 Product Movement Export
    1. Service Line Settings
      1. Customer Class Filter
        1. Default = *
        2. Enter a single Customer Class or list of Customer 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. A customer class prefix mask can be used to filter by records that match the prefix.
          5. Documents must have a matching Customer Class in this list to be exported.
      2. Customer Filter
        1. Default = *
        2. Enter a single Customer or list of Customers.
          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 customer prefix mask can be used to filter by records that match the prefix.
          5. Documents must have a matching Customer in this list to be exported.
      3. 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.
            1. Default is the default value.
      4. Export Fertilizer Blends
        1. Cinch typically creates a Blended Item and each of the fertilizer component line items, reporting the sale of the Blend item and the components might be perceived as doubling up on the sales. This setting allows the option to NOT Export the Fertilizer Blend Line item.
          1. Yes, when selected the blended items as well as the individual component items will be exported.
          2. No, when selected only the component items to be exported. No is the default value.
      5. Export Matching Lines Only
        1. Yes, when selected only line items that match the filter criteria will be exported.
          1. If an order doesn't contain any line items that pass the filters, the entire order will be ignored.
          2. This setting only comes into play when part of the order passes the service filters, Manufacturing Filter, Item Filter, License Type Filter and Item User Category Filters.
          3. Yes is the default value.
        2. No, when selected all line items on the order will be exported if one line matches any filters.
      6. Export Primary Customer Only
        1. Yes, when selected and splits are present only one transaction will be exported, and it will be in the primary customer's name. The exported quantity will be a total of all split participants, and the price will be the total extended price divided by the total quantity of all particpants.
          1. Yes is the default value.
        2. No when select a transaction will be exported for each split partner.
      7. Export Quantities in
        1. Base UofM when selected the quantity values are exported in their equivalent Base UofM quantities.
        2. Selling UofM, when selected the unit of measure and quantities will come directly from document line item.
          1. Selling UofM is the default value.
        3. Purchase UofM, when selected the quantity values are exported to the Purchasing UOM from Item Purchasing Options Maint (Item Maint>Purchasing).
      8. Filter Items by Vendor Item #
        1. Yes when selected, only items that have a matching vendor for the vendor selected in the Send-To Vendor ID setting will be sent. If an item does not have a vendor item setup for the Send To Vendor the export will fail. (Export matching lines only setting can still overrride this).
        2. No when selected items will not be filtered by vendor.
      9. Include Invoices
        1. Yes, invoices will be exported for the selected filters. Default = Yes
        2. No, invoices will not be exported.
      10. Include Returns
        1. Yes, returns will be exported for the selected filters. Default = Yes
        2. No, returns will not be exported.
      11. 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. A 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.
        3. The setting for Export Matching Lines Only will also have an impact on how this filter work.
      12. Item Filter
        1. Default = *
        2. Enter a single Item or list of Items.
          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 item prefix mask can be used to filter by records that match the prefix.
          5. Line items must have a matching Item in this list to be exported.
        3. The setting for Export Matching Lines Only will also have an impact on how this filter work.
      13. 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.
      14. 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.
        3. The setting for Export Matching Lines Only will also have an impact on how this filter work.
      15. 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.
        3. The setting for Export Matching Lines Only will also have an impact on how this filter work.
      16. 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.
        3. The setting for Export Matching Lines Only will also have an impact on how this filter work.
      17. 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.
        3. The setting for Export Matching Lines Only will also have an impact on how this filter work.
      18. 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.
        3. The setting for Export Matching Lines Only will also have an impact on how this filter work.
      19. 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.
        3. The setting for Export Matching Lines Only will also have an impact on how this filter work.
      20. License Type Filter. License Types are the Required License defined on the Item.
        1. Default = *
        2. Enter a License Type or list of License Types.
          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 license type prefix mask can be used to filter by records that match the prefix.
          5. Line items must have a matching License Type in this list to be exported.
        3. The setting for Export Matching Lines Only will also have an impact on how this filter work.
      21. Manufacturer Filter. Manufacturer defined on the Item Extension Maintenance window.
        1. Default = *
        2. Enter a Manufacturer or list of Manufacturers.
          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 manufacturer prefix mask can be used to filter by records that match the prefix.
          5. Line items must have a matching Manufacturer in this list to be exported.
        3. The setting for Export Matching Lines Only will also have an impact on how this filter work.
      22. 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).
      23. Send Cust# on Translation Fail
        1. Yes, when selected and the PARTNERID translation for customer number fails, it will send the Cinch customer number with an agency type of AssignedBySeller.
        2. No, when selected the standard PARTNERID translation kicks in and if a translation is missing, processing will fail. Default = No
      24. Send Pricing
        1. Yes, when selected pricing from the line will be sent.
        2. No, when selected pricing will not be sent. Default = No
      25. Sent To Vendor ID
        1. A valid Vendor ID is required be entered to help populate the To section of the xml doc.
        2. This vendor will also be used to determine item numbers if Item ID Source is set to "AssignedByManufacturer".
      26. Swap Ship From/To on Return
        1. No when selected Ship From will contain the seller (company) info, and Ship To will contain the customer info. Default = No
        2. Yes when selected the entity information for the parties in the Ship From and Ship To sections will be swapped. That is, Ship From will contain the info from Ship To in a normal order document, and Ship To will contain the Ship From info. This reflects the direction of how the product is actually moving.
      27. Use Branch for Reporting Entity
        1. Yes, when selected the branch address information will be used to populate the ReportingEntity section of xml (current functionality).
        2. No, when selected ReportingEntity information will be populated the same as the From section of xml, which is populated from company info. (Company name, company id translated). Default = No
      28. Use UN/CEFact for UOM Values
        1. Yes, when selected the standard UN/CEFACT (UN-Rec-20) units of measure will be sent describing quantities in the xml document.
          1. If the UN/CEFACT is not found the export will fail.
          2. Default = Yes
        2. No, when selected the standard Cinch, or translated values will be sent.
      29. XML Namespace Prefix
        1. Recommended to leave this field blank.
          1. For specific XML naming requirements. Prefixes each tag with this value.
      30. XML Namespace URL
        1. Recommended to leave this field blank.
          1. Puts the XML namespace URL in the header of each document.


New to CIDX 5.0 Product Movement Export
CIDX 5.0 Product Movement Export has been created for exporting Invoice and Return documents. The export process will be initiated with the posting of an invoice or a return document. Resending a document is done through the Export Change Tracking window.

  1. CIDX 5.0 Product Movement Export
    1. Service Line Settings
      1. Customer Class Filter
        1. Default = *
        2. Enter a single Customer Class or list of Customer 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. A customer class prefix mask can be used to filter by records that match the prefix.
          5. Documents must have a matching Customer Class in this list to be exported.
      2. Customer Filter
        1. Default = *
        2. Enter a single Customer or list of Customers.
          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 customer prefix mask can be used to filter by records that match the prefix.
          5. Documents must have a matching Customer in this list to be exported.
      3. 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, GLN, 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. When GLN is selected, the Entity ID will be pulled from the GLN identifier for the appropriate master record (vendor, location, company, etc.), and a translation will not be performed.
          3. 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.
            1. Default is the default value.
      4. Export Fertilizer Blends
        1. Cinch typically creates a Blended Item and each of the fertilizer component line items, reporting the sale of the Blend item and the components might be perceived as doubling up on the sales. This setting allows the option to NOT Export the Fertilizer Blend Line item.
          1. Yes, when selected the blended items as well as the individual component items will be exported.
          2. No, when selected only the component items to be exported. No is the default value.
      5. Export Matching Lines Only
        1. Yes, when selected only line items that match the filter criteria will be exported.
          1. If an order doesn't contain any line items that pass the filters, the entire order will be ignored.
          2. This setting only comes into play when part of the order passes the service filters, Manufacturing Filter, Item Filter, License Type Filter and Item User Category Filters.
          3. Yes is the default value.
        2. No, when selected all line items on the order will be exported if one line matches any filters.
      6. Export Primary Customer Only
        1. Yes, when selected and splits are present only one transaction will be exported, and it will be in the primary customer's name. The exported quantity will be a total of all split participants, and the price will be the total extended price divided by the total quantity of all particpants.
          1. Yes is the default value.
        2. No when select a transaction will be exported for each split partner.
      7. Export Quantities in
        1. Base UofM when selected the quantity values are exported in their equivalent Base UofM quantities.
        2. Selling UofM, when selected the unit of measure and quantities will come directly from document line item.
          1. Selling UofM is the default value.
        3. Purchase UofM, when selected the quantity values are exported to the Purchasing UOM from Item Purchasing Options Maint (Item Maint>Purchasing).
      8. Filter Items by Vendor Item #
        1. Yes when selected, only items that have a matching vendor for the vendor selected in the Send-To Vendor ID setting will be sent. If an item does not have a vendor item setup for the Send To Vendor the export will fail. (Export matching lines only setting can still overrride this)
        2. No when selected items will not be filtered by vendor.
      9. Include Invoices
        1. Yes, invoices will be exported for the selected filters. Default = Yes
        2. No, invoices will not be exported.
      10. Include Returns
        1. Yes, returns will be exported for the selected filters. Default = Yes
        2. No, returns will not be exported.
      11. 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. A 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.
        3. The setting for Export Matching Lines Only will also have an impact on how this filter work.
      12. Item Filter
        1. Default = *
        2. Enter a single Item or list of Items.
          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 item prefix mask can be used to filter by records that match the prefix.
          5. Line items must have a matching Item in this list to be exported.
        3. The setting for Export Matching Lines Only will also have an impact on how this filter work.
      13. 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.
      14. 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.
        3. The setting for Export Matching Lines Only will also have an impact on how this filter work.
      15. 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.
        3. The setting for Export Matching Lines Only will also have an impact on how this filter work.
      16. 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.
        3. The setting for Export Matching Lines Only will also have an impact on how this filter work.
      17. 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.
        3. The setting for Export Matching Lines Only will also have an impact on how this filter work.
      18. 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.
        3. The setting for Export Matching Lines Only will also have an impact on how this filter work.
      19. 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.
        3. The setting for Export Matching Lines Only will also have an impact on how this filter work.
      20. License Type Filter. License Types are the Required License defined on the Item.
        1. Default = *
        2. Enter a License Type or list of License Types.
          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 license type prefix mask can be used to filter by records that match the prefix.
          5. Line items must have a matching License Type in this list to be exported.
        3. The setting for Export Matching Lines Only will also have an impact on how this filter work.
      21. Manufacturer Filter. Manufacturer defined on the Item Extension Maintenance window.
        1. Default = *
        2. Enter a Manufacturer or list of Manufacturers.
          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 manufacturer prefix mask can be used to filter by records that match the prefix.
          5. Line items must have a matching Manufacturer in this list to be exported.
        3. The setting for Export Matching Lines Only will also have an impact on how this filter work.
      22. 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).
      23. Send Cust# on Translation Fail
        1. Yes, when selected and the PARTNERID translation for customer number fails, it will send the Cinch customer number with an agency type of AssignedBySeller.
        2. No, when selected the standard PARTNERID translation kicks in and if a translation is missing, processing will fail. Default = No
      24. Send Pricing
        1. Yes, when selected pricing from the line will be sent.
        2. No, when selected pricing will not be sent. Default = No
      25. Sent To Vendor ID
        1. A valid Vendor ID is required be entered to help populate the To section of the xml doc.
        2. This vendor will also be used to determine item numbers if Item ID Source is set to "AssignedByManufacturer".
      26. Swap Ship From/To on Return
        1. No when selected Ship From will contain the seller (company) info, and Ship To will contain the customer info. Default = No
        2. Yes when selected the entity information for the parties in the Ship From and Ship To sections will be swapped. That is, Ship From will contain the info from Ship To in a normal order document, and Ship To will contain the Ship From info. This reflects the direction of how the product is actually moving.
      27. Use Branch for Reporting Entity
        1. Yes, when selected the branch address information will be used to populate the ReportingEntity section of xml (current functionality).
        2. No, when selected ReportingEntity information will be populated the same as the From section of xml, which is populated from company info. (Company name, company id translated). Default = No
      28. Use UN/CEFact for UOM Values
        1. Yes, when selected the standard UN/CEFACT (UN-Rec-20) units of measure will be sent describing quantities in the xml document.
          1. If the UN/CEFACT is not found the export will fail.
          2. Default = Yes
        2. No, when selected the standard Cinch, or translated values will be sent.
      29. XML Namespace Prefix
        1. Recommended to leave this field blank.
          1. For specific XML naming requirements. Prefixes each tag with this value.
      30. XML Namespace URL
        1. Recommended to leave this field blank.
          1. Puts the XML namespace URL in the header of each document.


New to CIDX 5.2 Product Movement Export
CIDX 5.2 Product Movement Export has been created for exporting Invoice and Return documents. The export process will be initiated with the posting of an invoice or a return document. Resending a document is done through the Export Change Tracking window.

  1. CIDX 5.2 Product Movement Export
    1. Service Line Settings
      1. Customer Class Filter
        1. Default = *
        2. Enter a single Customer Class or list of Customer 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. A customer class prefix mask can be used to filter by records that match the prefix.
          5. Documents must have a matching Customer Class in this list to be exported.
      2. Customer Filter
        1. Default = *
        2. Enter a single Customer or list of Customers.
          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 customer prefix mask can be used to filter by records that match the prefix.
          5. Documents must have a matching Customer in this list to be exported.
      3. 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, GLN, 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. When GLN is selected, the Entity ID will be pulled from the GLN identifier for the appropriate master record (vendor, location, company, etc.), and a translation will not be performed.
          3. 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.
            1. Default is the default value.
      4. Export Fertilizer Blends
        1. Cinch typically creates a Blended Item and each of the fertilizer component line items, reporting the sale of the Blend item and the components might be perceived as doubling up on the sales. This setting allows the option to NOT Export the Fertilizer Blend Line item.
          1. Yes, when selected the blended items as well as the individual component items will be exported.
          2. No, when selected only the component items to be exported. No is the default value.
      5. Export Matching Lines Only
        1. Yes, when selected only line items that match the filter criteria will be exported.
          1. If an order doesn't contain any line items that pass the filters, the entire order will be ignored.
          2. This setting only comes into play when part of the order passes the service filters, Manufacturing Filter, Item Filter, License Type Filter and Item User Category Filters.
          3. Yes is the default value.
        2. No, when selected all line items on the order will be exported if one line matches any filters.
      6. Export Primary Customer Only
        1. Yes, when selected and splits are present only one transaction will be exported, and it will be in the primary customer's name. The exported quantity will be a total of all split participants, and the price will be the total extended price divided by the total quantity of all particpants.
          1. Yes is the default value.
        2. No when select a transaction will be exported for each split partner.
      7. Export Quantities in
        1. Base UofM when selected the quantity values are exported in their equivalent Base UofM quantities.
        2. Selling UofM, when selected the unit of measure and quantities will come directly from document line item.
          1. Selling UofM is the default value.
        3. Purchase UofM, when selected the quantity values are exported to the Purchasing UOM from Item Purchasing Options Maint (Item Maint>Purchasing).
      8. Filter Items by Vendor Item #
        1. Yes when selected, only items that have a matching vendor for the vendor selected in the Send-To Vendor ID setting will be sent. If an item does not have a vendor item setup for the Send To Vendor the export will fail. (Export matching lines only setting can still overrride this)
        2. No when selected items will not be filtered by vendor.
      9. Include Invoices
        1. Yes, invoices will be exported for the selected filters. Default = Yes
        2. No, invoices will not be exported.
      10. Include Returns
        1. Yes, returns will be exported for the selected filters. Default = Yes
        2. No, returns will not be exported.
      11. 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. A 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.
        3. The setting for Export Matching Lines Only will also have an impact on how this filter work.
      12. Item Filter
        1. Default = *
        2. Enter a single Item or list of Items.
          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 item prefix mask can be used to filter by records that match the prefix.
          5. Line items must have a matching Item in this list to be exported.
        3. The setting for Export Matching Lines Only will also have an impact on how this filter work.
      13. 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.
      14. 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.
        3. The setting for Export Matching Lines Only will also have an impact on how this filter work.
      15. 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.
        3. The setting for Export Matching Lines Only will also have an impact on how this filter work.
      16. 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.
        3. The setting for Export Matching Lines Only will also have an impact on how this filter work.
      17. 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.
        3. The setting for Export Matching Lines Only will also have an impact on how this filter work.
      18. 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.
        3. The setting for Export Matching Lines Only will also have an impact on how this filter work.
      19. 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.
        3. The setting for Export Matching Lines Only will also have an impact on how this filter work.
      20. License Type Filter. License Types are the Required License defined on the Item.
        1. Default = *
        2. Enter a License Type or list of License Types.
          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 license type prefix mask can be used to filter by records that match the prefix.
          5. Line items must have a matching License Type in this list to be exported.
        3. The setting for Export Matching Lines Only will also have an impact on how this filter work.
      21. Manufacturer Filter. Manufacturer defined on the Item Extension Maintenance window.
        1. Default = *
        2. Enter a Manufacturer or list of Manufacturers.
          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 manufacturer prefix mask can be used to filter by records that match the prefix.
          5. Line items must have a matching Manufacturer in this list to be exported.
        3. The setting for Export Matching Lines Only will also have an impact on how this filter work.
      22. 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).
      23. Send Cust# on Translation Fail
        1. Yes, when selected and the PARTNERID translation for customer number fails, it will send the Cinch customer number with an agency type of AssignedBySeller.
        2. No, when selected the standard PARTNERID translation kicks in and if a translation is missing, processing will fail. Default = No
      24. Send Pricing
        1. Yes, when selected pricing from the line will be sent.
        2. No, when selected pricing will not be sent. Default = No
      25. Sent To Vendor ID
        1. A valid Vendor ID is required be entered to help populate the To section of the xml doc.
        2. This vendor will also be used to determine item numbers if Item ID Source is set to "AssignedByManufacturer".
      26. Swap Ship From/To on Return
        1. No when selected Ship From will contain the seller (company) info, and Ship To will contain the customer info. Default = No
        2. Yes when selected the entity information for the parties in the Ship From and Ship To sections will be swapped. That is, Ship From will contain the info from Ship To in a normal order document, and Ship To will contain the Ship From info. This reflects the direction of how the product is actually moving.
      27. Use Branch for Reporting Entity
        1. Yes, when selected the branch address information will be used to populate the ReportingEntity section of xml (current functionality).
        2. No, when selected ReportingEntity information will be populated the same as the From section of xml, which is populated from company info. (Company name, company id translated). Default = No
      28. Use UN/CEFact for UOM Values
        1. Yes, when selected the standard UN/CEFACT (UN-Rec-20) units of measure will be sent describing quantities in the xml document.
          1. If the UN/CEFACT is not found the export will fail.
          2. Default = Yes
        2. No, when selected the standard Cinch, or translated values will be sent.
      29. XML Namespace Prefix
        1. Recommended to leave this field blank.
          1. For specific XML naming requirements. Prefixes each tag with this value.
      30. XML Namespace URL
        1. Recommended to leave this field blank.
          1. Puts the XML namespace URL in the header of each document.


Changes to Service Partner Setup
Service Partner Setup has been modified with the addition of a new Port Type to support Nexus Web Services and an enhancement to FTP Port Type to support SSH file transfer protocol.

  1. Initialize
    1. When Service is CIDX Product Movement (4.0, 5.0 or 5.2), and when the Initialize button is selected the following drop down opens:


    1. All, when selected all transactions between the Filter by Start Date (if enabled) and now will be re-exported.
    2. Missing, when selected only transactions that have not been previously exported will be sent.
      1. This is also based on retained history transactions, if the history transactions have beeen purged but if they fall betweeen the Filter by Start Date and now they will be exported again.
    3. Filter by Start Date lets you choose a date to determine how far back to go when re-exporting transactions.
  2. Nexus WS FS
  3. Select Port Type Nexus WS FS
  4. URL, enter the URL of the Nexus web service handler.
  5. Request Path is ignored for the Nexus WS FS Port Type and therefore disabled.
  6. Response Path enter the CinchX file share path where responses from Nexus will be picked up.
  7. Service Settings, after the Service has been saved:
      1. Manually add a setting in the service scrolling window called Action ID.
        1. Enter the ID of a Nexus action that will be used to forward on the xml payload to the business partner noted above. (example SendFile)
      2. Manually add a setting in the service scrolling window called Choreography ID.
        1. Enter the ID of a Choreography that has been setup in Nexus to forward on the xml payload that will be passed in to the Nexus web service. (example GenericFile)
      3. Manually add a setting in the service scrolling window called Business Partner ID.
        1. Enter the ID of a collaboration partner in Nexus which is a participant in the choreography noted above to receive the xml payload. (Example SAXON)
  8. FTP Port Type to support SFTP (SSH File Transfer Protocol)
  9. Service Settings, after the Service has been saved:
  10. For a Secure FTP manually add a setting the service scrolling window called FTP Protocol. This FTP library supports four different ftp modes. To accommodate for this, a setting is required to choose the required protocol. The user would enter the same setting as is setup on the ftp server they are trying to connect to. The valid options are:
  11. FTPSE – FTP/SSL Explicit
  12. FTPSI – FTP/SSL Implicit
  13. SFTP – SSH FTP
  14. FTP – FTP (This is the default and will be used if the setting does not exist or is empty.)
  15. Manually add a setting in the service scrolling window called UserName.
  16. Enter the user name to access the remote SFTP host.
  17. Manually add a setting in the service scrolling window called Password.
  18. Enter a password if the remote SFTP host requires it.
  19. Leave the value for password blank for anonymous access.
  20. Manually add a setting in the service scrolling window called Port.
  21. Enter the port number that the remote SFTP host will be listening on.
  22. Manually add a setting in the service scrolling window called Private Client Key Path.
  23. Enter the local path of your private key if the remote host requires one. This path should be local to where ever the Cinch Document Exchange service is running.
  24. Manually add a setting in the service scrolling window called Public Server Key Path.
  25. Enter the local path of the remote SFTP host's public key if the remote host requires one. This path should be local to wherever the Cinch Document Exchange service is running.
  26. Manually add a setting in the service scrolling window called SFTP Auth Type.
  27. Choose the type of authentication method the remote SFTP host requires to communicate with them. Available values are:
          1. Public Key
          2. Password
          3. Public Key and Password
  28. Manually add a setting in the service scrolling window called Ignore Cert.
  29. Setting this to "Yes" allows a connection to be made to the remote server regardless if the server certificate is valid or not.
  30. Setting to "No" requires the server certificate to be valid and trusted by the local server.


Changes to Export Criteria Entry
Export Criteria Entry has been modified with the addition of Cross Reference drop down boxes to provide the ability to cross reference the Company and Site on GLN or DUNS numbers rather than a cross reference table. And to cross reference item on GTIN numbers rather than a cross reference table.

  1. Open Export Criteria Entry

(Cards>Cinch Sales>XML – Export XRef>Export Criteria Entry)

  1. When Export Type is Inventory Actual the Cross Reference drop down lists will be enabled.
    1. The Drop Down lists provide the ability to cross reference on GLN, DUNS or GTIN numbers rather than a cross reference table.
    2. When a selection is made from the drop down list, if anything other than None is selected the table XRef will be disabled.
    3. When a selection is made from the drop down list after table XRef if the selection is anything but None table XRef will get cleared.
  2. Cross reference drop down boxes:
    1. Company cross reference.
      1. None - is used if changes need to be made to go back to a table cross reference rather than a GLN or DUNS value.
      2. GLN when selected the GLN Number from the Company Locations Details will be sent in the PartnerIdentification Agency tag of the XML.
        1. The PartnerIdentification Agency tag within the XML will be Other since GLN is not a supported Agency tag in CIDX 4.0 schema.
      3. DUNS/EBID when selected the DUNS Number from the Company Locations Details will be sent in the PartnerIdentification Agency tag of the XML.
        1. The PartnerIdentification Agency tag within the XML will be D-U-N-S.
    2. Item cross reference.
      1. None - is used if changes need to be made to go back to a table cross reference rather than a GTIN, Selleer Internal value.
      2. GTIN when selected the AGIIS Product ID (GTIN) from the Item Extensions Maintenance will be sent in the ProductIdentifier Agency tag of the XML.
        1. The ProductIdentifier Agency tag within the XML will be AGIIS Product ID.
      3. Seller Internal when selected the Vendor Item for the specified Vendor will be included in the XML.
        1. The Primary Vendor from the Item Quantities Maintenance will be used to determine the Vendor to get the Vendor Item.
        2. The ProductIdentifier Agency tag within the XML will be Assigned by Manufacturer.
    3. Site cross reference.
      1. None - is used if changes need to be made to go back to a table cross reference rather than a GLN or DUNS value.
      2. GLN when selected the GLN Number from the Locations Code COMP Entry will be sent in the PartnerIdentification Agency tag of the XML.
        1. The PartnerIdentification Agency tag within the XML will be Other since GLN is not a supported Agency tag in CIDX 4.0 schema.
      3. DUNS/EBID when selected the DUNS Number from the Company Locations Details will be sent in the PartnerIdentification Agency tag of the XML.
        1. The PartnerIdentification Agency tag within the XML will be D-U-N-S.
  3. The following Cross Reference items are required to generate an Inventory Actual Export Type:
    1. Company X-Ref or a selected drop down other than None.
    2. Item X-Ref or a selected drop down other than None.
    3. Site X-Ref or a selected drop down other than None.
    4. Manufacturer X-Ref
  4. Suppress Zero Quantity checkbox, when marked will suppress exporting of zero quantity inventory.


Changes to XML Export Entry
XML Export Entry has been modified so that when the selected Export Name is setup for Inventory Actual, Start and End Dates will default to the user date and be locked as the system export inventory quantities as of the time the export is run. If the selected Export Name has the Suppress Zero Quantity checkbox marked items that have a zero quantity will not be included in the displayed Transaction list.

  1. Open XML Export Entry

(Microsoft Dynamics GP>Tools> Routines>Cinch Sales>Export Entry)

New Sales History Address Maint
Sales History Address Maintenance has been created to allow the user to change the Ship To information on posted Invoice and Returns which will allow the record to be evaluated and/or exported for Cinch Document Exchange CIDX Product Movement.

  1. Open Sales History Address Maintenance

(Microsoft Dynamics GP>Tools>Utilities>Cinch Sales>Sales History Maintenance)

  1. Select the Document Type
    1. Only Invoices and Returns are supported.
  2. Select the Sales Number to edit.
  3. Select the Sales Number Expansion button to access the Sales Details screen.
    1. User can manually edit the address information or select a different Bill To or Ship To Address ID which will update the screen and within the data tables.
    2. There will be no update to document Taxes made for an address change.
  4. Select Save to the changes.
  5. Select Clear to clear the window without saving changes.


New Touchpoint PO Import 01
Touchpoint PO Import 01 is an adapter created to convert lines in a CSV document to a CIDX Purchase Order XML document and places them in the designated path for Import by the CIDX Purchase Order Import service.

  1. Touchpoint PO Import 01
    1. Supported Exchange Partner Filters
      1. No filters apply
    2. Service Line Settings
      1. CIDX Version
        1. Specifies the version of the CIDX Purchase Order doc to create. Options are:
          1. CIDX 2.02
          2. CIDX 4.0
          3. CIDX 5.0
          4. CIDX 5.2
      2. Default Seller ID
        1. The entered value will be used to populate the xml Seller Identifier and Seller Name tags.
        2. If no value is entered, the system will default PIONEER.
      3. 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).
      4. Purchase Order Type, Purchase Order Port URL and Purchase Order Port Req Path.
        1. These settings need to match the CIDX Purchase Order Import header settings for the appropriate CIDX version.
        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.


Processing Note:

  • No translations will be utilized in this adapter.
  • DEL (delete) Transaction Types will create a void XML document.
    • CIDX 2.0. and CIDX 4.0 the Action Request will be Void
    • CIDX 5.0 and CIDX 5.2 the Action Request will be Delete
  • Certain pieces of data are required by the xml schema such as From and To, etc. To fill these, some hard coded values, and various Cinch info will be used. In those cases From will be set to Pioneer, and To will be set from the Cinch company name.


New CIDX 2.02 Purchase Order Import
CIDX 2.02 Purchase Order Import has been created to create or update purchase order records for selected customers.

  1. CIDX 2.02 Purchase Order Export
    1. Supported Exchange Partner Filters
      1. Vendor ID is required. Only one vendor can be entered per service partner.
        1. When a purchase order file for the selected vendor is received, it is imported to create/update the purchase order.
    2. Service Line Settings
      1. Allow Voids
        1. Yes, will allow the Purchase Order to be voided based on the incoming file.
        2. No, will not allow the Purchase Order to be voided based on the incoming file. Default = No
      2. Default Branch
        1. A valid branch ID can be selected. If default branch is specified any unresolved seller addresses will be forced to this specified branch.
        2. If blank, the seller address in the AgXML must resolve to a location in the current company or the record will be rejected.
      3. Use location id for Ship-To
        1. This setting allows the inventory site to be determined from a location id in the xml document.
        2. Yes, the Cinch address ID will be used if included in the message.
          1. The OrderCreatePartners ShipTo.PartnerInformation. PartnerIdentifier will be translated as a LOCATIONCODE type and will be validated.
        3. No, the address match will be run.
          1. The Address Information will be address matched against inventory sites.
          2. Default = no
      4. Use Partner Doc#
        1. Yes, the document identifier from the xml document will be used as the Purchase Order number. Default = Yes
        2. No, the next Purchase Order number will be used.
      5. 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:

  • The Vendor Item must be setup for the translated item/vendor combination.
  • When importing an XML created from Touchpoint PO Import 01 the Use Location ID for Ship TO service setting must be set to Yes.
  • When importing an XML created from Touchpoint PO Import 01 the Delete transaction types will be created as a void transaction. So it is recommended to set the Allow Void service setting for processing preference.
  • Void document imports will void the Purchase Order providing no items have been received against the Purchase Order, the cancelled quantity will be set on the Purchase Order line for the void amount.
  • When an import record tries to void or update an existing Purchase Order that was items received against it, and error will be thrown and the import will fail. The Purchase Order will need to be updated manually.


Updated CIDX 4.0 Purchase Order Import
CIDX 4.0 Purchase Order Import has been updated to create or update purchase order records for selected customers.

  1. CIDX 4.0 Purchase Order Import
    1. Supported Exchange Partner Filters
      1. Vendor ID is required. Only one vendor can be entered per service partner.
        1. When a purchase order file for the selected vendor is received, it is imported to create/update the purchase order.
    2. Service Line Settings
      1. Allow Voids
        1. Yes, will allow the Purchase Order to be voided based on the incoming file.
        2. No, will not allow the Purchase Order to be voided based on the incoming file. Default = No
      2. Default Branch
        1. A valid branch ID can be selected. If default branch is specified any unresolved seller addresses will be forced to this specified branch.
        2. If blank, the seller address in the AgXML must resolve to a location in the current company or the record will be rejected.
      3. Use location id for Ship-To
        1. This setting allows the inventory site to be determined from a location id in the xml document.
        2. Yes, the Cinch address ID will be used if included in the message.
          1. The OrderCreatePartners ShipTo.PartnerInformation. PartnerIdentifier will be translated as a LOCATIONCODE type and will be validated.
        3. No, the address match will be run.
          1. The Address Information will be address matched against inventory sites.
          2. Default = no
      4. Use Partner Doc#
        1. Yes, the document identifier from the xml document will be used as the Purchase Order number. Default = Yes
        2. No, the next Purchase Order number will be used.
      5. 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:

  • The Vendor Item must be setup for the translated item/vendor combination.
  • When importing an XML created from Touchpoint PO Import 01 the Use Location ID for Ship TO service setting must be set to Yes.
  • When importing an XML created from Touchpoint PO Import 01 the Delete transaction types will be created as a void transaction. So it is recommended to set the Allow Void service setting for processing preference.
  • Void document imports will void the Purchase Order providing no items have been received against the Purchase Order, the cancelled quantity will be set on the Purchase Order line for the void amount.
  • When an import record tries to void or update an existing Purchase Order that was items received against it, and error will be thrown and the import will fail. The Purchase Order will need to be updated manually.


New CIDX 5.0 Purchase Order Import
CIDX 5.0 Purchase Order Import has been created to create or update purchase order records for selected customers.

  1. CIDX 5.0 Purchase Order Export
    1. Supported Exchange Partner Filters
      1. Vendor ID is required. Only one vendor can be entered per service partner.
        1. When a purchase order file for the selected vendor is received, it is imported to create/update the purchase order.
    2. Service Line Settings
      1. Allow Voids
        1. Yes, will allow the Purchase Order to be voided based on the incoming file.
        2. No, will not allow the Purchase Order to be voided based on the incoming file. Default = No
      2. Default Branch
        1. A valid branch ID can be selected. If default branch is specified any unresolved seller addresses will be forced to this specified branch.
        2. If blank, the seller address in the AgXML must resolve to a location in the current company or the record will be rejected.
      3. Use location id for Ship-To
        1. This setting allows the inventory site to be determined from a location id in the xml document.
        2. Yes, the Cinch address ID will be used if included in the message.
          1. The OrderCreatePartners ShipTo.PartnerInformation. PartnerIdentifier will be translated as a LOCATIONCODE type and will be validated.
        3. No, the address match will be run.
          1. The Address Information will be address matched against inventory sites.
          2. Default = no
      4. Use Partner Doc#
        1. Yes, the document identifier from the xml document will be used as the Purchase Order number. Default = Yes
        2. No, the next Purchase Order number will be used.
      5. 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:

  • The Vendor Item must be setup for the translated item/vendor combination.
  • When importing an XML created from Touchpoint PO Import 01 the Use Location ID for Ship TO service setting must be set to Yes.
  • When importing an XML created from Touchpoint PO Import 01 the Delete transaction types will be created as a void transaction. So it is recommended to set the Allow Void service setting for processing preference.
  • Void document imports will void the Purchase Order providing no items have been received against the Purchase Order, the cancelled quantity will be set on the Purchase Order line for the void amount.
  • When an import record tries to void or update an existing Purchase Order that was items received against it, and error will be thrown and the import will fail. The Purchase Order will need to be updated manually.


New CIDX 5.2 Purchase Order Import
CIDX 5.2 Purchase Order Import has been created to create or update purchase order records for selected customers.

  1. CIDX 5.2 Purchase Order Export
    1. Supported Exchange Partner Filters
      1. Vendor ID is required. Only one vendor can be entered per service partner.
        1. When a purchase order file for the selected vendor is received, it is imported to create/update the purchase order.
    2. Service Line Settings
      1. Allow Voids
        1. Yes, will allow the Purchase Order to be voided based on the incoming file.
        2. No, will not allow the Purchase Order to be voided based on the incoming file. Default = No
      2. Default Branch
        1. A valid branch ID can be selected. If default branch is specified any unresolved seller addresses will be forced to this specified branch.
        2. If blank, the seller address in the AgXML must resolve to a location in the current company or the record will be rejected.
      3. Use location id for Ship-To
        1. This setting allows the inventory site to be determined from a location id in the xml document.
        2. Yes, the Cinch address ID will be used if included in the message.
          1. The OrderCreatePartners ShipTo.PartnerInformation. PartnerIdentifier will be translated as a LOCATIONCODE type and will be validated.
        3. No, the address match will be run.
          1. The Address Information will be address matched against inventory sites.
          2. Default = no
      4. Use Partner Doc#
        1. Yes, the document identifier from the xml document will be used as the Purchase Order number. Default = Yes
        2. No, the next Purchase Order number will be used.
      5. 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:

  • The Vendor Item must be setup for the translated item/vendor combination.
  • When importing an XML created from Touchpoint PO Import 01 the Use Location ID for Ship TO service setting must be set to Yes.
  • When importing an XML created from Touchpoint PO Import 01 the Delete transaction types will be created as a void transaction. So it is recommended to set the Allow Void service setting for processing preference.
  • Void document imports will void the Purchase Order providing no items have been received against the Purchase Order, the cancelled quantity will be set on the Purchase Order line for the void amount.
  • When an import record tries to void or update an existing Purchase Order that was items received against it, and error will be thrown and the import will fail. The Purchase Order will need to be updated manually.



✦✦✦

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.