Page Comparison

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

• Changes to AgXML 4.0 In Transit-In Import
• Changes to AgXML 4.0 Ticket Import
• New PMR Reconciliation Matching
• New OneWeigh Load to Ticket Export
• New OneWeigh Inv Tkt Import
• New OneWeigh Sales Order Export
• Changes to AgXML 4.0 Load Export
• Changes to OneWeigh Ticket Import
• Cinch Document Exchange with Multicurrency

Anchor
ChangestoInTransitInImport ChangestoInTransitInImport

Anchor
_Toc419708847 _Toc419708847

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

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

...

Anchor
_Toc395183846 _Toc395183846

Anchor
_Toc419708848 _Toc419708848

Anchor
ChangesToAgXML40TicketImport ChangesToAgXML40TicketImport

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

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

...

Anchor
NewPMRReconciliationMatching NewPMRReconciliationMatching

Anchor
_Toc404087240 _Toc404087240

Anchor
_Toc419708849 _Toc419708849

Anchor
_Toc367879925 _Toc367879925

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

1. Open PMR Reconcile.

(Transactions>Cinch Doc Exchange>PMR Reconcile)

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

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

Anchor
OneWeighLoadtoTicketExport OneWeighLoadtoTicketExport

Anchor
_Toc419708850 _Toc419708850

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

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

...

Anchor
OneWeighInvTktImport OneWeighInvTktImport

Anchor
_Toc417919768 _Toc417919768

Anchor
_Toc419708851 _Toc419708851

Anchor
_Toc416973008 _Toc416973008

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

1. OneWeigh Inv Ticket Import
   1. Supported Exchange Partner Filters
      1. No filters apply
   2. Service Line Settings
      1. Shipment Port Type, Shipment Port URL and Shipment Port Req Path
         1. These settings need to match shipment import header settings for this service.
      2. Message Label Extension
         1. The file extension of the export file
            1. This extension can be anything but recommended to use XML for easy viewing in IE.

...

Anchor
OneWeighSalesOrderExport OneWeighSalesOrderExport

Anchor
_Toc416973009 _Toc416973009

Anchor
_Toc417919769 _Toc417919769

Anchor
_Toc419708852 _Toc419708852

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

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

...

Anchor
AGXML40LoadExport AGXML40LoadExport

Anchor
_Toc416973011 _Toc416973011

Anchor
_Toc417919770 _Toc417919770

Anchor
_Toc419708853 _Toc419708853

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

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

Anchor
ChangestoOneWeighTicketImport ChangestoOneWeighTicketImport

Anchor
_Toc418859416 _Toc418859416

Anchor
_Toc419708854 _Toc419708854

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

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

...