Chapter 2_CINCH 18.56 Grain Miscellaneous.

Changes to Minnesota Lienholder Import
Changes to Ticket Assembly Move
New to EMI Equipment
New to Treeno Interface

Changes to Minnesota Lienholder Import
The Minnesota Lienholder Import has been updated to support either the complete or summary report layout. (CIN-6374)

Open the Lien Holder Import window.

(Microsoft Dynamics GP >> Tools >> Routines >> CINCH Grain >> Lien Holder Import)

The state field now holds two selections for MN
1. MN – original functionality using the complete MN file layout. (C_COMPLETE_Job9.CSV)
2. MN-Sum – uses the summary MN file layout. (C_COMPLETE_SummaryJob9.CSV)
File to Import – select the file to import. If the file selected does not match the state selected, the system will ask the user to verify the file.
Item X-Ref Type for the (complete) summary report is located in Column Z – Product Name.
Vendor X-Ref Type for the (complete) summary report is located in Column Y - CNS Party ID.

Changes to Ticket Assembly Move
Ticket Assembly Move has been updated to support the movement of either priced or unpriced quantities when moving tickets between assemblies assigned to the same contract. (CIN-6168)

Open the Ticket Assembly Move window.

(Transactions>>CINCH Grain>>Purchases/Inbound>>Assembly Sheets>>Ticket Assembly Move)

New Header Fields:
1. Contract From displays the contract number that is associated with the selected Assembly From number.
2. Contract To displays the contract number that is associated with the selected Assembly To number.
3. Move Type is enabled and required when the Contract From and Contract To numbers are the same, meaning the move is between assemblies assigned to the same contract. When this happens…
  1. Users can either move the priced or the unpriced quantity, they cannot move both in the same move.
  2. The Move % value will be calculated based on the Move Type.
  3. A move cannot have a different Move Type at the header and line level. The header Move Type will rule.
  4. If Move Type is Priced or Unpriced and the select all checkbox is checked, the system will only choose tickets with priced or unpriced quantities, and a warning will be displayed indicating that not all tickets have been selected.
  5. If a user selects/enters an Assembly To without selecting the Move Type and then tries to mark a ticket, a message will be displayed asking the user to select a Move Type.
New Line Field and validations:
1. Move Type is enabled only if the To Assembly is attached to the same contract as the header's Assembly Form.
2. A selected ticket's Move Qty will be updated based on the selected Move Type.
3. Move Qty must be equal to or less than the priced/unpriced quantity or a message will be displayed to adjust the quantity.
4. If a user enters/selects a To Assembly at the line level, selects the Move Type as Priced for ticket 1 and unpriced for Ticket 2, which has the same To Assembly as Ticket 1, a message will be displayed indicating that one cannot select another move type for the same assembly.
5. If a ticket is selected for a Priced/Unpriced Move Type and the ticket has unpriced/priced quantity, the system will display a message indicating that a priced/unpriced ticket should be selected.

New to EMI Equipment
EMI Equipment/scale interface tables have been updated to better record whether an inbound/outbound ticket's gross, tare or both weights were manually entered or are true scale weights upon saving. (CIN-6639) Also, scale IDs have been added to a few tables. (CIN-6348)
A scale ID is attached to a weight if the scale button is pressed, and it is not removed if the scale weight is manually manipulated. Users have looked to the IRManualWeightCB field to see if weights were manually manipulated. However, this did not tell the user if it was the gross weight, tare weight or both weights that were manipulated. In order to fix this issue, the fields IRGrossManualWeightCB and IRTareManualWeighCB have been added to the following tables.

IRGNTicketScaleWORK
IRGNLoadShipmentWORK
IRGNLoadShipmentOPEN
IRGNLoadShipmentHIST
IRGNBulkTransferDTLWORK
IRGNBulkTransferDTLTEMP
IRGNBulkTransferDTLHIST

Zero (0) = Scale Weight and One (1) = Manual Weight. The values will reflect the status of the weight upon saving.
Note: The scale Weigh button is not tied to the gross or tare weight fields. Scale weights are entered based upon the window and the number of times the Weigh button has been clicked as to which field the weight will populate.
Example: Inbound Scale Ticket Entry with two scales will display two Weigh Buttons. The first click of either Weigh button, if no weights have been logged, will record the weight as the gross weight. The second click of either Weigh buttons will compare the received weight with the logged gross weight. If the logged gross weight is more than the second received weight, the second weight will be recorded as the tare weight. If the second received weight is greater than the recorded gross weight, the system will move the logged gross weight to the tare weight and use the second weight as the gross weight. Any additional presses of the Weigh buttons will act the same as the second press of the button. This process is reversed for outbound tickets.
The fields IRGrossWeightScaleID and IRTareWeightScaleID have been added to the following tables.

IRGNLoadShipmentOPEN
- IRGNLoadShipmentHIST

These fields already existed in the IRGNLoadShipmentWORK table.
NEW to Treeno Interface
Purchasing Invoice Inquiry Zoom has been added to the Treeno Interface. (CIN-6535)

Open Purchasing Invoice Inquiry Zoom.

( Purchasing >> Inquiry >> Purchase Order Documents >> select at least one Include option for a receipt >> Redisplay button >> select an invoice >> Receipt No. link)

The original window title displays followed by the below fields separated by a semi colon ( and inserted between curly brackets ({}). If any of the fields are blank nothing displays between semi colons.
1. Vendor ID
2. Vendor Name
3. Receipt No.
4. Vendor Document Number – added when available.
5. Invoice Date
6. Invoice Total