CINCH Customer Documentation
CINCH 18.61.1000 - What's New
CINCH Software
Version 18.61.1000
CINCH Document Exchange Software
Version 18.61.0.20
What’s New
May 2024
- 1 Introduction
- 2 Supported Version
- 3 Dynamics GP
- 4 AgWorks
- 5 Feed Mill Manager
- 6 Chapter 1: CINCH Document Exchange
- 7 Changes to AgXML 4.0 Load Export
- 8 Changes to AgXML 4.0 Purchase Load Import
- 9 Changes to AgXML 4.0 Purch Contract Export & Import
- 10 Changes to AgXML 4.0 Purch Contract Import
- 11 Changes to AgXML 4.0 Sales Contract Export & Import
- 12 Changes to AgXML 4.0 Shipment Import
- 13 Changes to Excel Ticket Import 01
- 14 NEW AGI Load Export (Adaptor)
- 15 NEW AGI Shipment Import (Adaptor)
- 16 NEW oneWeigh PurLoad2Tkt Exp AutoID (Adaptor)
- 17 Chapter 2: CINCH Grain Miscellaneous
- 18 Changes to Assembly Apply Entry
- 19 Changes to Bulk Transfer Entry
- 20 Changes to Contract Supplemental Inquiry
- 21 Changes to Direct Shipment – Single Ticket
- 22 Changes to Discount Detail Maintenance
- 23 Changes to General Setup
- 24 Changes to Inbound Scale Ticket Entry – Batch Edit List
- 25 Changes to Inbound Scale Ticket Inquiry
- 26 Changes to Load Invoice Inquiry
- 27 Changes to Mass Shipment Update
- 28 Changes to Purchase Contract Reports – Contract Supplementals
- 29 Changes to Reason Code Maintenance
- 30 Changes to Sales Contract Inquiry
- 31 Changes to Sales Contract Quantity Inquiry
- 32 Changes to Scale Ticket Apply Entry
- 33 Changes to Settlement Entry
- 34 Changes to Settlement Reports – Advances by Date & Customer
- 35 Changes to Settlement Void
- 36 Changes to Trade Roll
- 37 Changes to Void Open Payables Transactions
- 38 Chapter 3: CINCH Sales Miscellaneous
- 39 Changes to Sales Setup
- 40 Chapter 4: NEW Assembly Loads
- 41 Changes to Assembly Entry
- 42 Changes to Purchase Load Generator
- 43 Changes to Purchase Load Entry
- 44 Chapter 5: NEW Bulk Shipment Invoicing Options
- 45 Changes to Sales/Outbound User Setup
- 46 Changes to Bulk Shipment Invoicing
- 47 Chapter 6: NEW Grain Shipment Entry Options
- 48 Changes to Sales/Outbound User Setup
- 49 Changes to Grain Shipping Entry
- 50 Chapter 7: NEW Load Order Lookup Default
- 51 Changes to Freight Record Maintenance
- 52 Changes to Load Order Entry
- 53 Changes to Mass Load Order Delete Entry
- 54 Changes to Sales Load Order Reports
- 55 Chapter 8: NEW Process Manufacturing - Batch Retention
- 56 Changes to Manufacturing Entry
- 57 Chapter 9: NEW Sales Contract Entry - Multiple Freight Carriers
- 58 Changes to General Setup
- 59 Changes to Sales Contract Entry
- 60 Changes to Sales Contract Amendment Entry
- 61 NEW Sales Contract Freight Inquiry
- 62 Chapter 10: NEW Container ID field added to Sales Windows
- 63 Changes to Additional Line Information
- 64 Changes to Additional Line Information Inquiry
- 65 Chapter 11: NEW Load Reassignment – Options
- 66 Changes to Load Reassignment
- 67 Chapter 12: NEW Bulk Transfer Entry and Grain Shipment Entry – Multi Lot
- 68 Changes to Grain Shipment Entry
- 69 Changes to Bulk Transfer Entry
- 70 NEW Lot Inquiry Windows
- 71 Chapter 13: NEW Additional CINCH Reports added to GP’s Named Printers
- 72 Chapter 14: NEW Bulk/Grain Shipment Invoicing – Contract Filter
- 73 Changes to Bulk Shipment Invoicing
- 74 Changes to Grain Shipment Invoicing
- 75 Chapter 15: NEW Require Reason Code for Manual Weight Changes
- 76 Changes to User Extensions Setup
- 77 Changes to Ticket Entry Windows
- 78 Changes to Shipping Entry Windows
- 79 Changes to Bulk Transfer Entry
- 80 Changes to Inquiry Windows
- 81 Chapter 16: NEW Freight Rate UOM for Shipping Methods
- 82 Changes to Shipping Method Detail Maintenance
- 83 Changes to Transaction Windows (U of M Validation)
- 84 Changes to Freight Entry & Inquiry Windows
- 85 Appendix A: New Windows, Report & Tables
- 86 NEW Windows
- 87 NEW Reports
- 88 NEW Tables
- 89 Changes that may affect Reports or Data
Introduction
What’s New is your guide to enhancements in CINCH Software.
We add enhancements based on feedback we receive from customers, as well as on market research. Your willingness to help us build better products makes this a more complete solution, putting you in a better position to manage your organization successfully. We encourage you to share your thoughts and reactions with us at any time.
Some enhancements described in this documentation are optional. If you currently have a license for one of these modules and have an active enhancement program, you will automatically receive the enhancements contained in that module.
This document describes enhancements that were added to the CINCH Software since General Release 18.60.1000.
Descriptions of the enhancements are divided into the following chapters:
Chapter 1, “CINCH Document Exchange“ describes miscellaneous enhancements made to CINCHX.
Chapter 2, “CINCH Grain Miscellaneous“ describes miscellaneous enhancements made to CINCH Grain.
Chapter 3, “CINCH Sales Miscellaneous“ describes miscellaneous enhancements made to CINCH Sales.
Chapter 4, “NEW to Assembly Loads“ describes an enhancement made to create loads for assemblies with non-contracted items.
Chapter 5, “NEW Bulk Shipment Invoicing Options” describes an enhancement made to the Bulk Shipment Invoicing window to allow the automatic selection of the One Invoice per Customer and Combine Ship To’s checkboxes.
Chapter 6, “NEW Grain Shipment Entry Options” describes an enhancement made to the Grain Shipment Entry window to allow a user to save a grain shipment with zero weights.
Chapter 7, " NEW Load Order Lookup Default” describes an enhancement made to the Load Order Lookup window’s filter setting. The setting changes depending on where the window is opened. In the past the default was always set to Open Loads.
Chapter 8, “NEW Process Manufacturing – Batch Retention” describes an enhancement made to CINCH Process Manufacturing
Chapter 9, “NEW Sales Contract Entry – Multiple Freight Carries” describes the enhancement to allow multiple freight carriers to be selected on a sales contract.
Chapter 10, “NEW Container ID field added to Sales Windows.” describes an enhancement to the Additional Line Information window opened via multiple sales windows to display an items Container ID.
Chapter 11, “NEW Load Reassignment – Options” describes enhancements made to the Load Reassignment window to add additional filter options along with a new column for Car Number.
Chapter 12, “NEW Bulk Transfer Entry and Grain Shipment Entry – Multi Lot” describes the enhancement where multi lot functionality has been added to two additional windows.
Chapter 13, “NEW Additional CINCH Reports Added to GP’s Named Printers” describes the enhancement done to CINCH\Intellego, reports for use with GP’s Named Printers.
Chapter 14, “NEW Bulk/Grain Shipment Invoicing – Contract Filter” describes an enhancement made to the Bulk/Grain Shipment Invoicing windows to filter by sales contracts.
Chapter 15, “NEW Require Reason Code for Manual Weight Changes” describes an enhancement to require a reason for manually adjusting scale weights.
Chapter 16, “NEW Freight Rate UOM for Shipping Methods” describes an enhancement made to the way freight is calculated.
Supported Version
The following is a list of the Dynamics GP version we will be supporting for this release.
Dynamics GP
Software Version: 18.6.1695 (2023)
KB4602608
Dex Version: (18.00.0028)
AgWorks
Is currently not supported.
Feed Mill Manager
Is currently not supported.
This chapter describes miscellaneous enhancements made to CINCHX.
This chapter contains the following section(s):
Changes to AgXML 4.0 Load Export
Changes to AgXML 4.0 Purchase Load Import
Changes to AgXML 4.0 Purch Contract Export & Import
Changes to AgXML 4.0 Purch Contract Import
Changes to AgXML 4.0 Sales Contract Export & Import
Changes to AgXML 4.0 Shipment Import
Changes to Excel Ticket Import 01
NEW oneWeigh PurLoad2Tkt Exp AutoID
Changes to AgXML 4.0 Load Export
The AgXML 4.0 Load Export has been enhanced with a new service setting. This setting was created to work with the NEW AGI (Junge) integration. (CIN-7974)
Item Density From
None, default, when selected the Density tag will not be included within the User Area of the XML.
UDST1 or UDST2, when selected, CINCHX will add a tag called Density within the User Area of the XML. The tag will be populated with the value assigned to the Load Item’s User Defined Text String 1 or 2. (Cards>>Inventory>>Item>>Additional>>Item Extensions>>Additional>>User Defined)
Processing Notes:
When the exported load is used by AGI Load Export:
The Item Density From setting is required.
It is suggested to set the Item or Item Class Filter to limit the loads being sent to the AGI Load Export adapter.
Deleted loads must be handled manually within AGI and CINCH. Therefore, it is recommended that the Allow Deletes and Allow Voids both be set to No.
Updated loads will be passed to AGI Load Export, if the load has not been shipped within AGI it will be updated, if the load has been shipped, AGI will fail to import the file.
Changes to AgXML 4.0 Purchase Load Import
The AgXML 4.0 Purchase Load Import has been enhanced with a new service setting. (CIN-6665)
Allow Contract Overrun
Yes, if a load overruns a contract the import will not fail.
No, default, if a load overruns a contract the import will fail.
Changes to AgXML 4.0 Purch Contract Export & Import
The AgXML 4.0 Purch Contract Export & Import have been enhanced to export and import the user defined list information. Previously only the user defined sting information was exporting and importing. This information resides in the <ContractHeader> <UserArea> <IRContractUserArea> <IRUserDefL1-4> of the XML. If one of the user defined list vales does not exist within the system, the import will fail with a message that User_Defined_ListX does not exist. (CIN-6235)
Changes to AgXML 4.0 Purch Contract Import
The AgXML 4.0 Purch Contract Import has been enhanced to look to the contract header’s user area within the XML for the contract type. If the following tag is present, the system will use it to set the purchase contract’s contract type. If it is not present, the system will use the Price Type tag to set the purchase contract’s contract type.
<ContractHeader>
<UserArea>
<IRContractType>0-7</IRContractType>
Contract Types:
Spot = 1
Cash = 2
Price Later = 3
Basis = 4
Futures Fixed = 5
Minimum Price = 6
Other = 7
0 or no tag= System uses the Price Type Tag to set Contract Type
Changes to AgXML 4.0 Sales Contract Export & Import
The AgXML 4.0 Sales Contract Export & Import have been enhanced to export and import the user defined list information. Previously only the user defined sting information was exporting and importing. This information resides in the <ContractHeader> <UserArea> <IRContractUserArea> <IRUserDefL1-4> of the XML. If one of the user defined list vales does not exist within the system, the import will fail with a message that User_Defined_ListX does not exist. (CIN-6235)
Changes to AgXML 4.0 Shipment Import
The AgXML 4.0 Shipment Import has been updated when the service setting Auto Post is set to Yes. (CIN-5064)
Auto Post
Yes,
Shipments that are imported will automatically be posted.
If the shipment is associated with a Sales Load Order with a Shipment From equaling Purchase, a Purchase Invoice Receipt will be created and saved to a batch.
If the shipment being imported is applied to an open load, not associated to a contract, and there is a price and price UOM on the load it will be used.
No, shipments that are imported will be saved to a batch to be posted.
Changes to Excel Ticket Import 01
The Excel Ticket Import 01 has been enhanced to support load orders using the 20 grade Excel template. The system will look to the 113 column of the 20 grade Excel spreadsheet. The 50 grade Excel template has not been enhanced and will not support load orders. (CIN-8373)
NEW AGI Load Export (Adaptor)
The AGI Load Export is a new adaptor which converts an AgXML 4.0 Load Export into an AGI (Junge) XML format. (CIN-7974)
Service Header Settings
Partner ID, no exchange filters apply.
Supported Port Types: File Share and FTP
Service Line Settings:
AGI Load Path
The location CINCHX will place the AGI Load Export files it creates. (Require field)
Examples:
AGI Port Type = File Share, C:\CinchXFileShare\AGI\AGILoadExport
AGI Port Type = FTP, Cinch/CINCHXFTP/SalesLoad/Request/Sent
AGI Port Type – Indicates how the AGI Load Export XML file will be transferred. The supported Port Types are:
File Share – Default
FTP,
Note: Additional FTP settings will need to be manually added when either the AGI Port Type or the Header Server Setting Port type is FTP.
FTP Protocol
Ignore Cert
Password
Port
UserName
AGI Port URL – required only when the AGI Port Type equals FTP. This is the root FTP server address. (Example: ftp://ftp.culturatech.com)
Message Label Extension
The file extension of the exported file.
It is recommended to use XML.
Processing Note(s)
This integration requires an item’s density. The AgXML 4.0 Load Export must have the service setting Item Density From set to either UDST1 or UDST2 for this adaptor to work.
File Layout/Mapping is as follows:
AGI Load Export Tags (XML) | Notes |
<AgvanceData> | Line 01
|
<TicketStatus> | Line 02 All Action Types will be translated to ‘Ready’ |
<TicketNum> | Line 03 Set to CINCH Load Order Number |
<Location> | Line 04 Set to Load Order’s Site ID Description |
<Date> | Line 05 Set to the Load Order’s Scheduled Date |
<ShipFromLocation> | Line 06 Set to the Load Order’s Customer Name |
<Crop> | Line 07 Set to the Load Order’s Item Description |
<Placement /> | Line 08 Ignored |
<Quantity /> | Line 09 Ignored |
<QuantityUOM /> | Line 10 Ignored |
<GrowerID> | Line 11 Set to the Load Order’s Customer ID |
<GrowerAlternateID /> | Line 12 Ignored |
<FieldID /> | Line 13 Ignored |
<BlendType /> | Line 14 Liquid (Hard Coded) |
<LbsPerUnit /> | Line 15 Ignored |
<VolumePerUnit /> | Line 16 Ignored |
<Density> | Line 17 Value will be set to the AgXML 4.0 Load Export Service Setting of Item Density From. If no tag exists in the AgXML 4.0 Load Export the AGI Load Export will fail. |
<GuaranteedAnalysis /> | Line 18 Ignored |
<VRT> | Line 19 Set to False |
<ShipVia> | Line 20 Set to the Load Order’s Ship Company ID |
<Customer PO> | Line 21 Set to the Load Order’s Cust PO No |
<BillingNotes /> | Line 22 Ignored |
<AdditionalComments /> | Line 23 Ignored |
<MisComments /> | Line 24 Ignored |
<ApplicatorComments /> | Line 25 Ignored |
<Pests /> | Line 26 Ignored |
<CustomApplied /> | Line 27 Ignored |
<CustomerFedLicense /> | Line 28 Ignored |
<CustomerFedLicenseExp /> | Line 29 Ignored |
<Applicators /> | Line 30 |
<Fields /> | Line 31 |
<Addresses> | Line 32 |
<Address> | Line 33 |
<Type> | Line 34 Location (Hard Coded) |
<Name> | Line 35 Set to the Load Order’s Site ID Description |
<Address1> | Line 36 Set to the Load Order’s Site ID Address 1 |
<Address2> | Line 37 Set to the Load Order’s Site ID Address 2 |
<Address3> | Line 38 Set to the Load Order’s Site ID Address 3 |
<City> | Line 39 Set to the Load Order’s Site ID City |
<State> | Line 40 Set to the Load Order’s Site ID State |
<Zip> | Line 41 Set to the Load Order’s Site ID Zip |
<Phone1 /> | Line 42 Ignored |
<Phone2 /> | Line 43 Ignored |
</Address> | Line 44 |
<Address> | Line 45 |
<Type> | Line 46 BillTo (Hard Coded) |
<Name> | Line 47 Set to the Load Order’s Customer ID Name |
<Address1> | Line 48 Set to the Load Order’s Bill To ID’s Adress 1 |
<Address2> | Line 49 Set to the Load Order’s Bill To Adress 2 |
<Address3> | Line 50 Set to the Load Order’s Bill To Adress 3 |
<City> | Line 51 Set to the Load Order’s Bill To City |
<State> | Line 52 Set to the Load Order’s Bill To State |
<Zip> | Line 53 Set to the Load Order’s Bill To Zip |
<Phone1 /> | Line 54 Ignored |
<Phone2 /> | Line 55 Ignored |
</Address> | Line 56 |
<Address> | Line 57 |
<Type> | Line 58 ShipTo (Hard Coded) |
<Name> | Line 59 Set to the Load Order’s Customer ID Name |
<Address1> | Line 60 Set to the Load Order’s Ship To ID’s Adress 1 |
<Address2> | Line 31 Set to the Load Order’s Ship To Adress 2 |
<Address3> | Line 62 Set to the Load Order’s Ship To Adress 3 |
<City> | Line 63 Set to the Load Order’s Ship To City |
<State> | Line 64 Set to the Load Order’s Ship To State |
<Zip> | Line 65 Set to the Load Order’s Ship To Zip |
<Phone1 /> | Line 66 Ignored |
<Phone2 /> | Line 67 Ignored |
</Address> | Line 68 |
</Addresses> | Line 69 |
<Vehicles> | Line 70
|
<Vehicle> | Line 71 |
<ID> | Line 72 CINCH Load Order Vehicle/Car |
<Description /> | Line 73 Ignored |
<Type /> | Line 74 Ignored |
< JobAcres /> | Line 75 Ignored |
</Vehicle | Line 76 |
</Vehicles> | Line 77 |
<Products> | Line 78 Only one product/item is supported |
<Product> | Line 79 |
<Product ID> | Line 80 CINCH Load Order Item ID |
<Name> | Line 81 CINCH Load Order Item Description |
<DeptID> | Line 82 Blank |
<ProdID> | Line 83 CINCH Load Order Item ID |
<RatePerUnit /> | Line 84 Ignored |
<RatePerUnitUOM /> | Line 85 Ignored |
<MixAmount> | Line 86 CINCH Load Order Load Quantity |
<MixAmountUOM> | Line 87 CINCH Load Order Load Quantity UOM |
<ActiveIngredient /> | Line 88 Ignored |
<EPANumber /> | Line 89 Ignored |
<FederallyRestricted /> | Line 90 Ignored |
<ProductType /> | Line 91 Ignored |
<Density> | Line 92 AgXML 4.0 Load Export Service Setting of Item Density From. If no tag exists in the AgXML 4.0 Load Export the AGI Load Export will fail. If the tag is empty the export will fail during AGI processing. |
< /Product> | Line 93 |
</Products> | Line 94 |
</AgvanceData> | Line 95 |
NEW AGI Shipment Import (Adaptor)
The AGI Shipment Import is a new adaptor that converts an AGI (Junge) XML file to an AgXML 4.0 Shipment Import. (CIN-7974)
Service Header Settings
Partner ID, no exchange filters apply.
Supported Port Types: File Share and FTP
Service Line Settings:
AGI Port Type – Indicates how the AGI Shipment Import XML file will be transferred. The supported Port Types are:
File Share – Default
FTP
Note: Additional settings will need to be manually added when either the AGI Port Type or the Header Server Setting Port type is FTP.
FTP Protocol
Ignore Cert
Password
Port
UserName
AGI Port URL - is the location where CINCHX will place the created file. We suggest this matches the AgXML 4.0 Shipment Import header URL.
AGI Shipment Path – We suggest this matches the AgXML 4.0 Shipment Import header Request Path.
Message Label Extension
The file extension of the export file.
It is recommended to use XML.
Processing Note(s)
The adapter will generate an XML format that is supported by the AgXML 4.0 Shipment Import.
It is assumed this shipment will be imported as a Bulk Shipment; therefore, it is suggested that the AgXML 4.0 Shipment Import service setting Outbound Window be set to Bulk.
The file received from AGI will be in the same format as was previously created from the AGI Load Import adaptor. The only changes to it will be the values within the following tag(s):
<TicketStatus> will be set to Done.
<MixAmount> will be increased or decreased.
The AgXML 40 Shipment Import file will be built mostly with the information from the CINCH Load Order, which is indicated within the <TicketNum> tag of the AGI Shipment Import file. The only other information that will be used from the AGI Shipment Import file is the <MixAmount> tag which will be used to set the <IRNetMeter> and <IRGrossMeter> tags within the AgXML 4.0 Shipment Import.
File Layout/Mapping is as follows:
Notes | |
<CommodityMovement> | Line 02 |
<ActionType> | Line 03 Expecting that the TicketStatus will be set to Done. However, no matter what it is set to, we are setting it to Add |
<CommodityMovement CreateDateTime> | Line 04 Shipment’s created date/time determined by system’s processing date. |
<CommodityMovementLast UpdateDateTime> | Line 05 Shipment’s created date/time determined by system’s processing time. |
<CommodityMovementType> | Line 06 Defaults to Outbound |
<CommodityMovementStatus> | Line 07 Defaults to Weight and Quality Notification |
<CommodityMovementBuyer> | Line 08 |
<EntityInformation> | Line 09 |
<EntityIdentifier identifierSource="Seller Internal"> | Line 10 Customer ID Obtained from the Load Order’s Customer ID not the AGI Shipment Import. |
</EntityInformation> | Line 11 |
</CommodityMovementBuyer> | Line 12 |
<CommodityMovementSeller> | Line 13 |
<EntityInformation> | Line 14 |
<EntityType> | Line 15 Defaults to Organization |
<Address> | Line 16 |
<AddressLine> | Line 17 Site ID’s Address 1 Obtained from the Load Order’s Site ID not the AGI Shipment Import. |
AddressLine> | Line 18 Site ID’s Address 2 |
<AddressLine> | Line 19 Site ID’s Address 3 |
<City> | Line 20 Site ID’s City |
<CountryRegionCode> | Line 21 Site ID’s State |
<PostalCode> | Line 22 Site ID’s Zip |
<CountryCode> | Line 23 Site ID’s Country Code |
</Address> | Line 24 |
</EntityInformation> | Line 25 |
<CommodityMovementIdentifier identifierSource="Seller Internal"> | Line 26 Adaptor defaults AGI’s TicketNum which is CINCH’s Load Order Number (Required) This number is used to create the Shipment Number. The shipment number will depend on how the AgXML 4.0 Shipment Import service settings “Get Shipment# From Buyer/Seller Doc#” are set. |
</CommodityMovementSeller> | Line 27 |
<TransportationMode> | Line 28 This is defaulting to Truck no matter what the Ship Method’s Shipping Category is set to. |
<ShipmentInformation> | Line 29 |
<Shipper> | Line 30 |
<EntityInformation> | Line 31 |
<EntityIdentifier identifierSource ="Buyer Internal"> | Line 32 Obtained from the Load Order’s Ship Company not the AGI Shipment Import. |
</EntityInformation> | Line 33 |
</Shipper> | Line 34 |
<RailShipmentIdentifier> | Line 35 Obtained from the Load Order’s Unit Train field not the AGI Shipment Import |
<ShipmentSize> | Line 36 |
<Quantity unitOfMeasure="UOM"> | Line 37 Obtained from the Load Order’s Quantity field not the AGI Shipment Import |
</ShipmentSize> | Line 38 |
<VehicleIdentification> | Line 39 |
<VehicleIdentifierType> | Line 40 Defaulted to Load Order |
<VehicleIdentifier> | Line 41 Obtained from the AGI Shipment Import’s TicketNum, but is not displayed on the Bulk Shipment |
</VehicleIdentification> | Line 42 |
</ShipmentInformation> | Line 43 |
<CommodityInformation> | Line 44 |
<CommodityNameCode> | Line 45 Item ID Obtained from the Load Order’s Item ID not the AGI Shipment Import. |
<CommodityGroup> | Line 46 Obtained from the Load Order’s Item ID not the AGI Shipment Import. |
</CommodityInformation> | Line 47 |
<CommodityMovement WeightInformation> | Line 48 |
<CommodityMovementActual WeightInformation> | Line 49 |
<WeightCertificate> | Line 50 |
<WeightCertificateHeader> | Line 51 |
<TransportationMode> | Line 52 This is defaulting to Truck no matter what the Ship Method’s Shipping Category is set to. |
<IssueDateTime> | Line 53 |
<Date> | Line 54 Shipment’s created date/time determined by system’s processing date. |
</IssueDateTime> | Line 55 |
<WeightCertificateIdentifier> | Line 56 CINCH Load Order Number – doesn’t default into the shipment |
<ServiceEvent> | Line 57 Defaults to Outbound |
<EstimatedWeightIndicator> | Line 58 Defaults to false |
<BatchIndicator> | Line 59 Defaults to false |
<ServiceOfficialCategory> | Line 60 Defaults to Unofficial |
</WeightCertificateHeader> | Line 61 |
<WeightCertificateDetail> | Line 62 |
<WeightCertificateLine> | Line 63 |
<VehicleIdentification> | Line 64 |
<VehicleIdentifierType> | Line 65 Defaults to Load Order |
<VehicleIdentifier>SP713 </VehicleIdentifier> | Line 66 Defaulted to the AGI Shipment Export’s TicketNum and is required. This is the Load assigned to the Bulk Shipment. |
</VehicleIdentification> | Line 67 |
<VehicleIdentification> | Line 68 |
<VehicleIdentifierType> | Line 69 Defaults to Rail Car |
<RailOrBargeAlphaPrefix> | Line 70 Defaulted to the AGI Shipment Export’s TicketNum. This is the Car Number assigned to the Bulk Shipment. |
</VehicleIdentification> | Line 71 |
<VehicleIdentification> | Line 72 |
<VehicleIdentifierType> | Line 73 Defaults to Meter Ticket Number |
<VehicleIdentifier> | Line 74 Defaulted to the AGI Shipment Export’s TicketNum and is not assigned to the Bulk Shipment. |
</VehicleIdentification> | Line 75 |
<NetWeight> | Line 76 |
<Weight unitOfMeasure="UOM"> | Line 77 Defaulted to the AGI Shipment Export’s MixAmountUOM |
</NetWeight> | Line 78 |
<GrossMeterQuantity unitOfMeasure ="UOM"> | Line 79 Defaulted to the AGI Shipment Export’s MixAmountUOM” & MixAmount. This does not appear on the shipment. |
</WeightCertificateLine> | Line 80 |
</WeightCertificateDetail> | Line 81 |
</WeightCertificate> | Line 82 |
</CommodityMovementActual WeightInformation> | Line 83 |
</CommodityMovementWeight Information> | Line 84 |
<UserArea> | Line 85 |
<IRTicketUserArea> | Line 86 |
<IRMeterTicketNumber> | Line 87 Defaulted to the AGI Shipment Export’s TicketNum and is not assigned to the Bulk Shipment but it is required. |
<IRNetMeter> | Line 88 Defaulted to the AGI Shipment Import’s MixAmount. This is the shipment’s Meter Net. |
<IRShrinkMeter> | Line 89 Ignored |
<IRGrossMeter> | Line 90 Defaulted to the AGI Shipment Import’s MixAmount. This is the shipment’s Meter Gross. |
</IRTicketUserArea> | Line 91 |
</UserArea> | Line 92 |
</CommodityMovement> | Line 93 |
NEW oneWeigh PurLoad2Tkt Exp AutoID (Adaptor)
The oneWeigh PurLoad2Tkt Exp AutoID is a new adaptor that takes an AgXML 4.0 Purch Load Export file and translates it into an oneWeigh Auto ID flat file. (CIN-5394)
Service Header Settings.
Partner ID, No exchange filters apply.
Supported Port Types, File Share and FTP only.
See Service Partner Setup for more information on Port Types, URL, and Request/Response Paths.
Service Line Settings
Message Label Extension
The file extension of the export file.
It is recommended to use FIL.
oneWeigh Import Path
The location CINCHX will save the oneWeigh Auto ID files it creates. (Require field)
Examples:
oneWeigh Port Type = File Share, C:\CinchXFileShare\USAG\oneWeighImportPath
oneWeigh Port Type = FTP, CINCH/CINCHXFTP/Load/oneWeighFiles. (These are the subdirectories of the oneWeigh Port URL. Folders need to be manually setup on the FTP)
oneWeigh Port Type – Indicates how the oneWeigh Load2Tkt Exp AutoID flat file will be transferred. The supported Port Types are:
File Share – Default
FTP
oneWeigh Port URL – required only when the service line setting of “oneWeigh Port Type” equals FTP and is the root FTP server address. (Example: ftp://ftp.culturatech.com) It is especially useful when the pickup up of the Load Order is via File Share yet the drop off is via FTP.
Populate Variety/Class
Yes, when selected the first and second characters of the Commodity Name Code from the Load Order XML file will be used to populate the Commodity, positions 50-51 in the FIL file. The third through the eighth character of the Commodity Name Code from the Load Order XML file will be used to populate the Variety Class, positions 52-57 in the FIL file.
No, when selected, only the first and second characters of the Commodity Name Code from the Load Order file will be used to populate the Commodity, positions 50-51 in the FIL file. The Variety Class will not be populated, positions 53-58 in the FIL file will be blank.
Remark Position Address1
Select which position, 01-30 within the FIL file under the ONEA2 record type, to display the first Address Line from the XML file’s <Origin>, <LocationInformation>, <Address>, <AddressLINE>.
This is the Load’s Company ID Source’s first Address Line.
Remark Position Address2
Select which position, 01-30 within the FIL file under the ONEA2 record type, to display the second Address Line from the XML file’s <Origin>, <LocationInformation>, <Address>, <AddressLINE>.
This is the Load’s Company ID Source’s second Address Line.
Remark Position City
Select which position, 01-30 within the FIL file under the ONEA2 record type, to display the City from the XML file’s <Origin>, <LocationInformation>, <Address>, <City>.
This is the Load’s Company ID Source’s City.
Remark Position Load Number
This will default to 07, but user can select another position, 01-30 within the FIL file under the ONEA2 record type, to display the Load Number from the XML file’s <VehicleIdentification>, <VehicleIdentifier>.
The selected remark must have the Remark Description set to Load Order within One Weigh Ticket Information to ensure the Load Order is included in the export from One Weigh and handled correctly when shipment is imported.
Remark Position Order Reference
This will default to 15, but user can select another position, 01-30 within the FIL file under the ONEA2 record type, to display the Order Reference from the XML file’s <UserArea>, <REFERENCE>.
This is the Load’s Order Reference.
Remark Position Origin Location
Select which position, 01-30 within the FIL file under the ONEA2 record type, to display the Location Name from the XML file’s <Orign>, <LocationInformation>, <LocationName>.
This is the Load’s Company ID Source’s Location Name.
Remark Position State
Select which position, 01-30 within the FIL file under the ONEA2 record type, to display the State from the XML file’s <Origin>, <LocationInformation>, <Address>, <CountryRegionCode>.
This is the Load’s Company ID Source’s State.
Remark Position Zip Code
Select which position, 01-30 within the FIL file under the ONEA2 record type, to display the Zip Code from the XML file’s <Origin>, <LocationInformation>, <Address>, <PostalCode>.
This is the Load’s Company ID Source’s Zip.
Processing Notes:
Needs AgXML 4.0 Purch Load Export (Transaction Service) to feed it Purchase Load Orders from CINCH.
Converts an XML file into a flat file (FIL) that oneWeigh can import.
If the Port Type of FTP is selected in either the Service Header Settings or the Service Line Settings, additional Service Line Settings need to be added manually. See the Service Partner Setup section for more information on the FTP Port Type.
This adaptor has translations for record type ONEA0 and ONEA2 (Ticket Remarks).
The FIL file that is created can contain two record types: ONEA0 and ONEA2
File Translation for record type of “ONEA0”:
Record Type (Position 1-5) = ONEA0
Auto ID Number (Position 6-17) = Load Number
Ship From ID (Position 18-27) = Customer ID from Load
Shipper ID (Position 28-37) = Will be left blank.
Commodity (Position 50-51) = Item, translation (First two characters of the Standard Value)
Variety Class (Position 52-57) = Item, translation (third thru eighth character of the Standard Value)
Expected Apply Type (Position 58-59) = C (Contract)
Expected Contract Number (Position 60-66) = CINCH contract number, which will be truncated.
Ticket Type (Position 87-87) = R (Regular)
Ticket Location (Position 88-90) = Based on AgXML 4.0 Purchase Load Order Export service setting Company ID Source (Branch, Company or Location), translated
In Out Code (Position 93-93) = I, Purchase Load Orders are inbound
Delete When Expired (Position 94 – 94) = Y
Expire Date (Position 95-102) = YYYYMMDD
This will be set to a fixed date in the past, (20200101).
This will be set when the Order is marked On Hold, Voided or Deleted in CINCH.
Maximum Tickets (Position 103 – 106) = 1
ID Source (Position 241-241) = L (Load Order)
File Translation for record type of “ONEA2”:
Record Type (Position 1-5) = ONEA2
Number (Position 6-7) = Remark Number (01-30)
Value (Position 8-57) = Remark Position values.
On Hold Load Orders
It is assumed that the AgXML 4.0 Purch Load Export, Service setting CINCH Consumer is set to Yes. This will ensure the On Hold sending will be included in the Load Export file.
If a Load Order is exported and later marked on hold, the IROnHoldCB is true, the oneWeigh Expire Date will be set to 20200101, which will allow it to be removed from OneWeigh.
Void Load Orders
It is assumed that the AgXML 4.0 Purch Load Export, Service setting Allow Voids is set to Yes. This will ensure the Voided Orders will be exported.
If a Load Order is exported and later voided, the oneWeigh Expire Date will be set to 20200101, which will allow it to be removed from OneWeigh.
Delete Load Orders
It is assumed that the AgXML 4.0 Purch Load Export, Service setting Allow Deletes is set to Yes. This will ensure the Deleted Orders will be exported.
If a Load Order is exported and later deleted, the oneWeigh Expire Date will be set to 20200101, which will allow it to be removed from OneWeigh.
Remark Position service lines, there are no validation if the remark number has already been selected. User will need to ensure the selected One Weigh Remark number maps correctly.
This chapter describes miscellaneous enhancements made to CINCH Grain.
This chapter contains the following section(s):
Changes to Assembly Apply Entry
Changes to Bulk Transfer Entry
Changes to Contract Supplemental Inquiry
Changes to Direct Shipment–Single Ticket
Changes to Discount Detail Maintenance
Changes to Inbound Scale Ticket Entry – Batch Edit List
Changes to Inbound Scale Ticket Inquiry
Changes to Load Invoice Inquiry
Changes to Mass Shipment Update
Changes to Purchase Contract Report – Contract Supplementals
Changes to Reason Code Maintenance
Changes to Sales Contract Inquiry
Changes to Sales Contract Quantity Inquiry
Changes to Scale Ticket Apply Entry
Changes to Settlement Reports – Advances by Date & Customer
Changes to Void Open Payables Transactions
Changes to Assembly Apply Entry
A new field has been added to the header of Assembly Apply Entry (CIN-6115).
Open Assembly Apply Entry.
(Transactions>>CINCH Grain>>Purchases/Inbound>>Assembly Sheets >>Assembly Apply Entry)
Disc Schedule displays the discount schedule assigned to the selected assembly.
Changes to Bulk Transfer Entry
A warning has been added to the Reverse Posted Transaction lookup window to warn the user when selecting a transfer that has already been reversed. (CIN-7565)
Open Bulk Transfer Entry
(Transactions >> CINCH Grain >> Bulk Transfer Entry)
Reverse Posted Transaction
When a user selects a transaction which has already been reversed, a warning message will be displayed indicating that the transfer has already been reversed, are you sure you want to continue?
Yes, continue to reverse the transaction.
No, default, lookup window will close without selecting a transfer.
Changes to Contract Supplemental Inquiry
Added an additional line to each Voucher Number to indicate if the Voucher has been voided. (CIN-8375)
Open Contract Supplement Inquiry
(Transactions >> CINCH Grain >> Purchases/Inbound >> Purchase Contracts >> Purchase Contract Entry >> Additional >> Supplemental Entry)
Voided
Yes, indicates the user and date the voucher was voided.
No, voucher has not been voided.
Changes to Direct Shipment – Single Ticket
The Direct Shipment – Single Ticket window has been updated to allow the input of separate freight information for the inbound scale ticket verses the outbound grain shipment. (CIN-7581)
Open Direct Shipment-Single Ticket
(Transactions >> CINCH Grain >> Direct Shipment–Single Ticket)
Freight Entry, FOB, Ship Company, and Total Freight will be based on the drop-down selection of Inbound or Outbound.
Inbound
Freight Entry button and Expansion button next to the Total Freight will open the Ticket Freight Entry window.
FOB, Ship Company, and Total Freight represent freight information for the inbound scale ticket.
Outbound
Freight Entry button and Expansion button next to the Total Freight will open the Load Shipping Freight Entry.
FOB, Ship Company, and Total Freight represent freight information for the outbound grain shipment.
Changes to Discount Detail Maintenance
A new setting has been added to the Discount Detail Maintenance window. (CIN-7808)
Open Discount Detail Maintenance
(Cards>>CINCH Grain>>Contracts>>Discount Detail Maintenance)
Split Flat Amount
Unchecked, default, flat rate amounts will not be split between split tickets. Each ticket will be charged the full flat amount.
Checked, flat amounts will be split between split tickets based on the percentage of the Split ID assigned to the ticket.
Changes to General Setup
A new option has been added to the Outbound section of the General Setup window. (CIN-8312)
Open General Setup
(Microsoft Dynamics GP >> Tools >> Setup >> CINCH Grain >> General Setup)
Require Reason Code on Shipment Invoice Returns
Unchecked, default setting, a Reason Code will not be required on a shipment invoice return entered via the Shipment Invoice Return Entry window.
Checked, a Reason Code will be required to save a shipment invoice return via the Shipment Invoice Return Entry window.
Changes to Inbound Scale Ticket Entry – Batch Edit List
The Inbound Scale Ticket Entry’s batch edit list has been updated with a warning for tickets assigned to a disposition type of storage or grain bank, General Setup’s Ticket Cost is set to Market, and an Item Daily Price does not exist. The warning states “A Ticket Detail does not have a Market Price; it will post but inventory will not be updated.” (CIN-6053)
Changes to Inbound Scale Ticket Inquiry
The Inbound Scale Ticket Inquiry’s Export function has been enhanced to export more than 20 grades. (CIN-6375)
Open the Inbound Scale Ticket Inquiry window.
(Inquiry>>CINCH Grain>>Purchases/Inbound>>Inbound Scale Ticket Inquiry)
Choose the Export button to export the information to a Microsoft Excel spreadsheet.
Changes to Load Invoice Inquiry
The Load Invoice Inquiry has been enhanced with a Total Discount Amount field and two columns have been added to the Excel report. (CIN-5990)
Open Load Invoice Inquiry
(Inquiry>>CINCH Grain>>Sales/Outbound>>Load Invoice Inquiry)
Total Discount Amount displays the total discount amount for the shipment.
Export to Excel, added the following columns.
Discount Amount displays the total discount amount for the shipment.
Grade Factor displays each grade factor and it’s discount amount.
Changes to Mass Shipment Update
Mass Grain Shipment Update has been enhanced to not only split grain shipments but bulk shipments as well. A Shipment Type field has been added and the Redisplay and Process button function have been updated to reflect this change. (CIN-7931)
Open Mass Shipment Update
(Microsoft Dynamics GP >> Tools >> Routines >> CINCH Grain >> Mass Shipment Update)
Shipment Type
Redisplay, displays only unprocessed posted shipments not linked to a contract(s), Loads or have been created via Direct Shipment-Single Ticket.
Process
Splits the selected posted Bulk \Grain Shipment using the selected Split ID.
The split shipments will use the original shipment number followed by "S1", "S2"...etc.
All shipment details will be sourced from the original shipment. Gross, Tare, and Freight will be recalculated based on the split percentages.
The original shipment will be deleted, and the deleted “originating” shipment number cannot be reused.
Ship To & Bill To address details will be defaulted from the Split Customer details.
Note: Shipments can be split multiple times. However, the system will stop the splitting if the Shipment Number reaches the maximum field length.
Changes to Purchase Contract Reports – Contract Supplementals
Added an Exclude Voided checkbox enabled only for the Contract Supplemental Report Name . (CIN-8375)
Open Purchase Contract Reports
(Reports>>CINCH Grain>>Purchase Contract Reports)
Exclude Voided – enabled only for the Contract Supplements Report
Unchecked, default setting, includes voided vouchers within the report with an asterisk (*). Voided vouchers will be included in the report totals.
Checked, voided vouchers will not be included in the report or report totals.
Changes to Reason Code Maintenance
A filter has been added to the Reason Code Maintenance window to indicate the modules where the reason code can be used. (CIN-8297)
Open Reason Code Maintenance
(Cards>>CINCH Grain>>Reason Code Maintenance)
Reason Code Module allows the user to indicate which module a reason code will be available for selection.
All, default, this reason code will be available for selection in all modules.
Assembly, this reason code will only be available for selection within the following window(s).
Assembly Entry
Assembly Transfer Entry
Assembly Transfer Reverse
Discount Amount Maintenance
Ticket Assembly Move
Unapplied Tickets Select
Branch Transfer, this reason code will only be available for selection within the following window(s).
Branch Transfer Entry
Bulk Transfer, this reason code will only be available for selection within the following window(s).
Bulk Transfer Entry – Void Reason
Bulk Transfer Load Order Entry – Enter a Reason Code (Voided Load)
Document Utility, this reason code will only be available for selection within the following window(s).
Document Utility
Load Order (Sales), this reason code will only be available for selection within the following window(s).
Mass Load Order Delete
Load Order Entry – Enter a Reason Code (Void)
Prepay, this reason code will only be available for selection within the following window(s).
Prepay Effective Date Change
Program Detail, this reason code will only be available for selection within the following window(s).
Program Other Details Entry
Program Apply Entry
Purchase Load Order, this reason code will only be available for selection within the following window(s).
Purchase Load Order Entry
Sales, this reason code will only be available for selection within the following window(s).
AgWorks Setup Options
Booking Reports
Sales Reports
Sales Return Entry
Sales Shipment Invoicing
Split Details Entry
Shipment Inv Return, this reason code will only be available for selection within the following window(s).
Shipment Invoice Return Entry
Vendor Return, this reason code will only be available for selection within the following window(s).
Vendor Return Entry
Weight Override, this reason code will only be available for selection within the following window(s).
Bulk Shipment Entry
Bulk Ticket Entry
Bulk Transfer Entry
Grain Shipment Entry
Inbound Scale Ticket Entry
Notes:
The Reason Code Lookup, within the windows stated above, will show the reason codes set to All and reason codes assigned to the specific module.
Manually entering a reason code, within the windows stated above, that is not assigned to the module you are working in will display an error indicating that the reason code is not valid for the module.
Reason Code IDs must be unique. Example, you cannot have a Reason Code ID called “TEST” for the module Sales and one called “TEST” for the Vendor Return.
Changes to Sales Contract Inquiry
Changes have been made to the Del/Cancel/IT expansion button on the Sales Contract Inquiry. (CIN-5117)
Open the Scale Contract Inquiry
(Inquiry>>CINCH Grain>>Sales/Outbound>>Sales Contract Inquiry)
Del/Cancel/IT Expansion
Delivered Inquiry opens the Sales Contract Deliveries window and displays information based upon Shipment.
Wash Inquiry opens the Contract Wash Inquiry window.
In Transit Inquiry opens the Sales Contract Deliveries window and displays information based upon In Transit.
Underfill Inquiry displays the underfill quantity for the contract in a message box.
Changes to Sales Contract Quantity Inquiry
Changes have been made to the Del/Cancel/IT expansion button on the Sales Contract Quantity Inquiry. (CIN-5117)
Open the Scale Contract Quantity Inquiry
(Inquiry>>CINCH Grain>>Sales/Outbound>>Sales Contract Quantity Inquiry)
Del/Cancel/IT Expansion
Changes to Scale Ticket Apply Entry
A new column heading has been added to Scale Ticket Apply Entry (CIN-6115).
Open the Scale Ticket Apply Entry
(Transactions>>CINCH Grain>>Purchases/Inbound>>Scale Tickets>> Scale Ticket Apply Entry)
Ticket scrolling window, added column Disc Schedule which appears when the Rollup checkbox is selected and displays the discount schedule assigned to the tickets.
Note: Rolled tickets are now grouped together by Customer, Item, Disposition, Discount Schedule, along with the Splits – Total and Net Qty of unapplied tickets.
Assembly scrolling window, added column Disc Schedule which displays the discount schedule assigned to the assembly.
Changes to Settlement Entry
The Settlement Entry window has been updated to display a total field for net quantity. (CIN-8422)
(Transactions >> CINCH Grain >> Purchases/Inbound >> Settlements >> Settlement Entry)
A total field has been added to the To Settle scrolling window. It will display the total of the Net Qty column.
Changes to Settlement Reports – Advances by Date & Customer
The Settlement Reports of Advances by Customer and Advances by Date have been updated with a subtotal of settled amount by customer or date and a new column called Remaining Amount which displays each settlements remaining amount (original advance amount minus the settled amount) with a subtotal of all remaining amounts. (CIN-7847)
Changes to Settlement Void
A new warning message has been added to the Settlement Void process when contracts linked to a settlement have been underfilled. (CIN-8420)
Open Settlement Void
(Microsoft Dynamics GP >> Tools >> Routines >> CINCH Grain >> Settlement Void)
Void, when pressed will verify if a contract linked to the settlement has been underfilled. If so, a warning will be displayed indicating that the contract underfill void process should be completed prior to voiding the settlement especially if ticket application changes are needed.
Yes, settlement will be voided.
No, settlement will not be voided.
Changes to Trade Roll
The Trade Roll window allows the user to roll an individual or multiple trades into new trades. Some fields, which are disable when a trade number is selected had lookups that were active. These lookups have now been disabled. (CIN-4408)
Open Trade Roll
(Transactions>>CINCH Grain>>Commodity Trading>> Trade Roll)
The Broker ID Lookup, Hedge Lookup, and Ticker Symbol Lookup have been disabled if a Trade Number has been selected.
Changes to Void Open Payables Transactions
A new warning message has been added to GP Dynamics’ Void Open Payables Transactions process when contracts linked to vouchers have been underfilled. (CIN-8420)
Open Void Open Payables Transactions
(Purchasing >> Transactions >> Void Open Transactions)
Void, when pressed will verify if a contract linked to the voucher has been underfilled. If so, a warning will be displayed indicating that the contract underfill void process should be completed prior to voiding the voucher especially if ticket application changes are needed.
Continue, voucher will be voided.
Cancel, voucher will not be voided.
This chapter describes miscellaneous enhancements made to CINCH Sales.
This chapter contains the following section(s):
Changes to Sales Setup
A new option has been added to the Sales Returns section of the Sales Setup window. (CIN-8177)
Open Sales Setup
(Microsoft Dynamics GP>>Tools>>Setup>>CINCH Sales>>Sales Setup)
Require Reason
Unchecked, default setting, a Reason Code will not be required for a sales returns entered via the Sales Return Entry window.
Checked, a Reason Code will be required to save a sales return via the Sales Return Entry window. A warning message will be displayed upon saving a sales return without a reason code.
This chapter describes an enhancement made to create loads for assemblies with non-contracted items. (CIN-4401)
This chapter contains the following section(s):
Changes to Purchase Load Generator
Changes to Purchase Load Entry
Changes to Assembly Entry
A new Generate Loads button has been added to the Assembly Entry window.
Open Assembly Entry
(Transactions>>CINCH Grain>>Purchases/Inbound>>Assembly Sheets >>Assembly Entry)
Generate Loads
Validates if the assembly is for a non-contracted item.
Yes, continue.
No, stop and display a message indicating that the system cannot generate loads for an assembly linked to a contract.
Opens the Purchase Load Generator window to create loads based on the assembly.
Changes to Purchase Load Generator
A new Assembly field has been added to the Purchase Load Generator window to allow the creation of loads based on an assembly instead of a contract.
Open Purchase Load Generator
(Transaction>CINCH Grain>Purchase/Inbound>Purchase Load Generator)
Assembly, enter or lookup an assembly.
When accessing Purchase Load Generator from Assembly Entry, the assembly will be selected, and the field, along with the contract number field, will be disabled.
When accessing Purchase Load Generator from Purchase Contract Entry, the assembly field will be empty and disabled.
Selecting an Assembly will disable the Contract Number field and vice versa.
Changes to Purchase Load Entry
A new Assembly field has been added to the Purchase Load Entry window to allow the creation of loads based on an assembly instead of a contract.
Open Purchase Load Entry
(Transaction>CINCH Grain>Purchase/Inbound>Purchase Load Entry)
Assembly
Enter or lookup an assembly.
An assembly linked to a contract cannot be selected.
Selecting an assembly will disable the Contract Number field and vice versa.
This chapter describes an enhancement made to the Bulk Shipment Invoicing window to allow the automatic selection of the One Invoice per Customer and Combine Ship To’s checkboxes. (CIN-7846)
This chapter contains the following section(s):
Changes to Sales/Outbound User Setup
Changes to Bulk Shipment Invoicing
Changes to Sales/Outbound User Setup
Two new settings have been added to the Sales/Outbound User Setup window.
Open the Sales/Outbound User Setup window.
One Invoice Per Customer in Bulk Shipment Invoicing.
Unchecked, default setting, the One Invoice per Customer checkbox will be unmarked within the Bulk Shipping invoicing window.
Checked, the One Invoice per Customer checkbox will be marked within the Bulk Shipping Invoicing window.
Combine Ship To’s in Bulk Shipment Invoicing.
Disabled by default.
Enable only when One Invoice Per Customer is marked.
Unchecked, default setting, the Combine Ship To’s checkbox will be unmarked within the Bulk Shipping Invoicing window.
Checked, the Combine Ship To’s checkbox will be marked within the Bulk Shipping Invoicing window.
Changes to Bulk Shipment Invoicing
Two new default settings have been added to the Bulk Shipment Invoicing window.
Open the Bulk Shipment Invoicing window.
(Transactions >> CINCH Grain >> Sales/Outbound >> Bulk Shipment Invoicing)
One Invoice per Customer checkbox will default checked or unchecked depending on the One Invoice per Customer in Bulk Shipment Invoicing setting within the Sales/Outbound User Setup window.
Combine Ship To’s checkbox will default checked or unchecked depending on Combine Ship To’s in Bulk Shipment Invoicing setting within the Sales/Outbound User Setup window.
This chapter describes an enhancement made to the Grain Shipment Entry window to allow a user to save a grain shipment with zero weights. (CIN-6015)
This chapter contains the following section(s):
Changes to Sales/Outbound User Setup
Changes to Grain Shipping Entry
Changes to Sales/Outbound User Setup
An existing setting has been updated in the Sales/Outbound User Setup window.
Open the Sales/Outbound User Setup window.
(Microsoft Dynamics GP >> Tools >> Setup >> CINCH Grain >> Sales/Outbound User Setup)
Allow Save with Zero Weights previously only worked for Bulk Shipment Entry. Now it also works for Grain Shipping Entry.
Unchecked, bulk or grain shipments must have a weight to be saved.
Checked, bulk or grain shipments can be saved with zero weights. However, they cannot be posted without a gross weight.
Changes to Grain Shipping Entry
The Grain Shipment Entry window will now allow a shipment to be saved with zero weights.
Open the Grain Shipping Entry
(Transactions >> CINCH Grain >> Sales/Outbound >> Grain Shipping Entry)
Scale – Weights in lb
If Sales/Outbound User Setup, Allow Save with Zero Weights checkbox is selected the shipment can be saved with zero weights. However, posting a Grain Shipment is not allowed without a gross quantity.
If Sales/Outbound User Setup, Allow Save with Zero Weights checkbox is not selected the shipment cannot be saved with zero weights.
This chapter describes an enhancement made to the Load Order Lookup window’s filter setting. The setting changes depending on where the window is opened. In the past the default was always set to Open Loads. (CIN-6983)
This chapter contains the following section(s):
Changes to Freight Record Maintenance
Changes to Mass Load Order Delete Entry
Changes to Sales Load Order Reports
Changes to Freight Record Maintenance
The Load Order Lookup default filter will be set to All Loads when opened from Freight Record Maintenance.
Open the Freight Record Maintenance.
(Transactions >> CINCH Grain >> Freight Charge Matching Entry >> Add Missing)
If the Source Module equals Load Order, the Document Number lookup button will open the Load Order Lookup window with the default filter set to All Loads.
Changes to Load Order Entry
The Load Order Lookup default filter will be set to All Loads when opened from Load Order Entry.
Open the Load Order Entry window.
(Transactions>>CINCH Grain>>Sales\Outbound>>Load Order Entry)
Load Number lookup button will open the Load Order Lookup window with the default filter set to All Loads.
Changes to Mass Load Order Delete Entry
The Load Order Lookup default filter will be set to All Loads when opened from Mass Load Order Void.
Open the Mass Load Order Void/Delete window.
(Microsoft Dynamics GP>Tools>Routines>CINCH Grain>Mass Load Order Void/Delete)
If the Range is set to Load Number, the From/To lookup buttons will open the Load Order Lookup window with the default filter set to All Loads.
Changes to Sales Load Order Reports
The Load # Lookup default filter will be set to All Loads when opened from Sales Load Order Report.
Open the Sales Load Order Reports window.
(Reports>>CINCH Grain>>Sales Load Order Reports)
Selecting the Load # From/To lookup buttons will open the Load Order Lookup window with the default filter set to All Loads.
This chapter describes an enhancement made to CINCH Process Manufacturing. (CIN-8345)
This chapter contains the following section(s):
Changes to Manufacturing Entry
Changes to Manufacturing Entry
Batch Numbers are now retained upon saving, clearing, deleting, or posting a manufacturing transaction.
Open the Manufacturing Entry
(Transactions>>CINCH Manufacturing>>Manufacturing Entry)
Batch Number retains with Save, Clear, and Delete actions.
This chapter describes the enhancement to allow multiple freight carriers to be selected on a sales contract. (CIN-2477)
This chapter contains the following section(s):
Changes to Sales Contract Entry
Changes to Sales Contract Amendment Entry
NEW Sales Contract Freight Inquiry
Changes to General Setup
Open General Setup
(Microsoft Dynamics GP >> Tools>>Setup>>CINCH Grain>>General Setup)
Outbound Setup – Enable Sales contract Multiple Carrier
Unchecked, default, only one freight carrier can be selected within Sales Contract Entry.
Checked, allows multiple freight carriers to be selected within Sales Contract Entry.
Sales Contract Entry window has been modified to support multiple freight carriers.
Open Sales Contract Entry
(Transactions>>CINCH Grain>>Sales\Outbound>>Sales Contract Entry)
Ship Company, FOB, Payment Resp., Freight Rate and Freight U of M fields are available only if a single freight carrier is used for this contract delivery period. If multiple freight carriers have been entered, these fields will be blank and disabled. Use the Freight Entry button to enter/view freight information.
Note: If only one freight carrier is used, a freight record will not be written to the sales contract freight tables unless the Freight Entry button is selected. Sales contract freight records are only necessary when multiple freight carriers are used.
Freight Entry
Visible only when Enable Sales Contract Multiple Carrier is marked in General Setup.
Opens the Sales Contract Freight Entry window allowing users to enter multiple freight carriers.
If a Shipping Company was entered on the main window, it will automatically be inserted into the scrolling window.
The Contract Number is display only and will default from the Sales Contract Entry window.
Depending on what was selected in Freight Setup, either Shipping Company or Vendor will display in the drop-down list. Select the Shipping Company/Vendor to create freight records for.
Select an FOB if desired.
Select a Payment Liability of Customer Pays or Company Pays. This is required for the freight record to be saved. Freight matching records will not be created at this time.
The Freight U of M, Freight Rate, Freight Rate UofM, Freight Adjustment, Freight Misc Amt, and Fuel Surcharge % will default from the Shipping Method Detail Maintenance window but can be changed if necessary.
Net Quantities are not fully determined until transactions are saved.
The Fuel Surcharge will automatically be calculated based on the Surcharge % entered.
If freight information needs modifying, highlight the line in the scrolling window. The Shipping Company will display in the header and the user can enter the appropriate information.
Choose Insert to insert the record that was created.
Enter any additional freight lines as needed.
Choose OK to close the window. It is required to choose OK to close the window to verify that all freight information has been entered. If OK is selected without inserting a line and there is information in the header, it will ask if you want to insert the information.
If only one freight carrier is used, a freight record will not be written to the sales contract freight tables unless the Freight Entry button is selected. Sales contract freight records are only necessary when multiple freight carriers are used.
When a sales contract with multiple freight carriers is assigned to a transaction the freight will be rolled down to the transaction within the following windows:
Load Order Generator
Load Order Entry
Grain Shipping Entry
Bulk Shipping Entry
Grain Shipment Invoicing
Bulk Shipment Invoicing
Load Reassignment
Sales Contract Amendment Entry window has been modified to support multiple freight carriers.
Open Sales Contract Entry
(Transactions>CINCH Grain>>Sales/Outbound> Sales Contract Amendment Entry or Transactions>CINCH Grain>Sales/Outbound>Sales Contract Entry, Amendment button)
Ship Company, FOB, Payment Resp., Freight Rate and Freight U of M fields are available only if a single freight carrier is used for this contract delivery period. If multiple freight carriers have been entered, these fields will be blank and disabled. Use the Freight Entry button to enter/view freight information.
Freight Entry
Visible only when Enable Sales Contract Multiple Carrier is marked in General Setup.
If freight records are updated and transactions have already been created. Freight information for those transactions will need to be manually updated. Only new transactions will reflect the changes.
Opens the Sales Contract Freight Amend Entry window allowing users to enter multiple freight carriers.
Since Sales Contract Entry and Sales Contract Amendment Entry have been updated to support multiple freight carriers a new inquiry window has also been added.
Open Sale Contract Freight Inquiry
(Inquiry >> CINCH Grain >> Sales/Outbound >> Sales Contract Inquiry or Sales Contract Amendment Inquiry >> Contract Expansion >> Freight Entry)
Displays multiple freight information.
Note: If only one freight carrier is used, a freight record will not be written to the sales contract freight tables unless the Freight Entry button is selected within the entry windows. Sales contract freight records are only necessary when multiple freight carriers are used.
This chapter describes an enhancement to the Additional Line Information window opened via multiple sales windows to display an items Container ID. (CIN-5073)
This chapter contains the following section(s):
Changes to Additional Line Information
Changes to Additional Line Information Inquiry
Open Additional Line Information
(Transactions >> CINCH Sales >> Counter Sales Entry >> Scrolling Window >> Additional Info Expansion Button)
(Transactions >> CINCH Sales >> Sales Invoice Entry >> Scrolling Window >> Additional Info Expansion Button)
(Transactions >> CINCH Sales >> Sales Return Entry >> Scrolling Window >> Additional Info Expansion Button)
(Transactions >> CINCH Sales >> Sales Order Entry >> Scrolling Window >> Floating Expansion Button)
Enter or select a Container ID to be associated with the line item.
Open Additional Line Information Inquiry
(Inquiry>>CINCH Sales>> Sales Order Processing Document Inquiry >> Document Number Expansion Button >> Scrolling Window >> Additional Info Expansion Button)
(Inquiry >> CINCH Sales >> Sales Detail Inquiry >> Select Document No >> Sales Doc Button >> Scrolling Window >> Additional Info Expansion Button)
Container ID displays the container associated with the line item.
This Chapter describes enhancements made to the Load Reassignment window to add additional filter options along with a new column for Car Number. (CIN-8347, CIN-8348 & CIN-8349)
This chapter contains the following section(s):
Open Load Reassignment
(Transactions >>CINCH Grain>Sales/Outbound >> Uninvoiced Shipments; Load Reassignment) or (Transactions >> CINCH Grain >> Sales/Outbound >> Load Reassignment)
Sort by, works for the upper scrolling window and includes a drop-down and column header select. The sort is in ascending order only.
Car Number has been included in the upper scrolling window and will display based on assigned shipment.
This chapter describes the enhancement where multi lot functionality has been added to two additional windows. (CIN-7080)
This chapter contains the following section(s):
Changes to Grain Shipment Entry
Changes to Bulk Transfer Entry
Changes to Grain Shipment Entry
Multi lot functionality has been added to the Grain Shipment Entry window.
Open Grain Shipping Entry.
(Transactions >> CINCH Grain >> Outbound\Sales >> Grain Shipping Entry)
Lot Number
Displays a single lot number when only one lot number is selected, or it will display *Multi Lot* when multiple lot numbers have been selected.
Lookup offers two selection options:
Lot opens the Lot Analysis Advanced Lookup window.
Multi Lot opens the Shipment Multi Lot Entry window.
Item Number, Item Description, Extended Quantity and Site ID will default from the shipment.
Lot Selected displays the total lot quantity selected.
Quantity Type defaults to On Hand.
Available lots, for the selected Site ID, are displayed in the Available Lots scrolling window.
Enter a quantity in the Quantity Selected column for the appropriate lot and press the Insert button.
Only one lot can be entered/inserted at a time.
If a lot has expired, a warning will be displayed.
If Use Expired Lots is setup in Inventory Control, a password can be entered. If correct, the system will use the lot.
If Use Expired Lots is not setup in Inventory Control, the lot cannot be selected.
If a lot is about to expire and warning options have been setup in Item Maintenance Options, a warning will be displayed.
Select yes to use the lot.
Select no and the lot will not be selected.
Selected lots are displayed in the Selected Lots scrolling window.
Highlight a selected lot and press the Remove button to remove the selected lot.
Press the Remove All button to remove all the selected lots.
Ok closes the Shipment Multi Lot Entry window and returns the user to the Bulk Shipment Entry window.
Changes to Bulk Transfer Entry
Multi lot functionality has been added to the Bulk Transfer Entry window.
Open Bulk Transfer Entry
(Transactions >> CINCH Grain >> Bulk Transfer Entry)
Lot Number
Displays a single lot number when only one lot number is selected, or it will display *Multi Lot* when multiple lot numbers have been selected.
Lookup offers two selection options:
Lot opens the Lot Analysis Advanced Lookup window.
Multi Lot opens the Bulk Transfer Multi Lot Entry window.
Item Number, Item Description, Extended Quantity and Site ID will default from the shipment.
Lot Selected displays the total lot quantity selected.
Quantity Type defaults to On Hand.
Available lots, for the selected Site ID, are displayed in the Available Lots scrolling window.
Enter a quantity in the Quantity Selected column for the appropriate lot and press the Insert button.
Only one lot can be entered/inserted at a time.
If a lot has expired, a warning will be displayed.
If Use Expired Lots is setup in Inventory Control, a password can be entered. If correct, the system will use the lot.
If Use Expired Lots is not setup in Inventory Control, the lot cannot be selected.
If a lot is about to expire and warning options have been setup in Item Maintenance Options, a warning will be displayed.
Select yes to use the lot.
Select no and the lot will not be selected.
Selected lots are displayed in the Selected Lots scrolling window.
Highlight a selected lot and press the Remove button to remove the selected lot.
Press the Remove All button to remove all the selected lots.
Ok closes the Shipment Multi Lot Entry window and returns the user to the Bulk Shipment Entry window.
NEW Lot Inquiry Windows
Since multi lot functionality has been added to both Grain Shipment Entry and Bulk Transfer Entry window their inquiry windows have also been updated.
Open Load Shipping Inquiry Zoom & Bulk Transfer Inquiry Zoom
(Inquiry>>CINCH Grain>>Sales/Outbound>>Load Shipment Inquiry>>Shipment Expansion button)
Lot Number
Displays a single lot number when only one lot number is selected, or it will display *Multi Lot* when multiple lot numbers have been selected.
When *Multi Lot* is displayed the expansion button will open either Shipment Multi Lot Inquiry.
Or Transfer Multi Lot Inquiry
This chapter describes the enhancement done to CINCH\Intellego, reports for use with GP’s Named Printers. Previously only 62 CINCH/Intellego reports worked with GP’s Named Printers. Now, 522 CINCH/Intellego reports work with GP’s Named Printers. (CIN-5123)
If you would like to see a list of all reports, the following SQL script can be run against the Dynamics database:
select * from STN41200 where PRNSER = 6 /*ST_Printer_Assign_MSTR*/
If reports are missing from this table, go to Microsoft Dynamics GP >> Maintenance >> CINCH Maintenance >> Printer Initialize and select the Initialize Printers button.
This chapter describes an enhancement made to the Bulk/Grain Shipment Invoicing windows to filter by sales contracts. (CIN-8274)
This chapter contains the following section(s):
Changes to Bulk Shipment Invoicing
Changes to Grain Shipment Invoicing
Changes to Bulk Shipment Invoicing
Open Bulk Shipment Invoicing
(Transactions >> CINCH Grain >> Sales/Outbound >> Bulk Shipment Invoicing)
Range allows the user to filter the shipments in the scrolling window by Customer Number, Item Number, Ship Date, Currency, Customer Class, Payment Terms, Priority, Load Number and/or Contract.
Changes to Grain Shipment Invoicing
Open Grain Shipment Invoicing
(Transactions>>CINCH Grain>>Sales/Outbound>>Grain Shipment Invoicing)
Range allows the user to filter the shipments in the scrolling window by Item Number, Ship Date, Ship Number, Load Number, Currency ID and/or Contract.
This chapter describes an enhancement to require a reason for manually adjusting scale weights. (CIN-7861)
This chapter contains the following section(s):
Changes to User Extensions Setup
Changes to Ticket Entry Windows
Changes to Shipping Entry Windows
Changes to Bulk Transfer Entry
Changes to User Extensions Setup
Open User Extensions Setup
(Microsoft Dynamics GP >> Tools >> Setup >> System >> User >> Additional >> User Extensions)
Inbound Permissions
Allow Wt Change in Ticket Entry (Existing Setting)
Works with the Allow Wt Override with Reason in Ticket Entry. Only one or the other setting can be selected. If the other setting is selected, this setting will be disabled.
Unchecked, default setting, disables scale weight fields from manual adjustments within Inbound Scale Ticket Entry and Bulk Ticket Entry.
Checked, allows user to change scale weights within Inbound Scale Ticket Entry and Bulk Ticket Entry.
Allow Wt Override with Reason in Ticket Entry (New Setting)
Works with the Allow Wt Change in Ticket Entry. Only one or the other setting can be selected. If the other setting is selected, this setting will be disabled.
Unchecked, default setting, disables scale weight fields from manual adjustments within Inbound Scale Ticket Entry and Bulk Ticket Entry.
Checked, allows user to change scale weights within Inbound Scale Ticket Entry and Bulk Ticket Entry. Users must provide their name and a valid reason code to save the transaction.
Outbound Permissions
Allow Wt Change in Shipping Entry (Existing Setting)
Works with the Allow Wt Override with Reason in Shipping Entry. Only one or the other setting can be selected. If the other setting is selected, this setting will be disabled.
Unchecked, default setting, disables scale weight fields from manual adjustments within Bulk Shipping Entry and Grain Shipping Entry.
Checked, allows user to change scale weights within Bulk Shipping Entry and Grain Shipping Entry.
Allow Wt Override with Reason in Shipping Entry (New Setting)
Works with the Allow Wt Change in Shipping Entry. Only one or the other setting can be selected. If the other setting is selected, this setting will be disabled.
Unchecked, default setting, disables scale weight fields from manual adjustments within Bulk Shipping Entry and Grain Shipping Entry.
Checked, allows user to change scale weights within Bulk Shipping Entry and Grain Shipping Entry. Users must provide their name and a valid reason code to save the transaction.
Bulk Transfer Permissions
Allow Wt Change in Bulk Transfer Entry (Existing Setting)
Works with the Allow Wt Change in with Reason in Bulk Transfer Entry. Only one or the other setting can be selected. If the other setting is selected, this setting will be disabled.
Unchecked, default setting, disables scale weight fields from manual adjustments within Bulk Transfer Entry.
Checked, allows user to change scale weights within Bulk Transfer Entry.
Allow Wt Override with Reason in Bulk Transfer Entry (New Setting)
Works with the Allow Wt Change in Bulk Transfer Entry. Only one or the other setting can be selected. If the other setting is selected, this setting will be disabled.
Unchecked, default setting, disables scale weight fields from manual adjustments within Bulk Transfer Entry.
Checked, allows user to change scale weights within Bulk Transfer Entry. Users must provide their name and a valid reason code to save the transaction.
Changes to Ticket Entry Windows
Open Inbound Scale Ticket Entry or Bulk Ticket Entry
(Transactions>>CINCH Grain>>Purchases/Inbound>>Scale Tickets>>Inbound Scale Ticket Entry) or (Transactions>>CINCH Grain>>Purchases/Inbound>>Scale Tickets >>Bulk Ticket Entry)
Override & Reason
Enabled if User Extension Maintenance’s Allow Wt Override with Reason in Ticket Entry is selected.
Selecting Override
Opens the Weight Override Information window asking Who is overriding scale weights. This is a free form field. User ID validation will NOT be conducted.
Ok, if information has been entered in the Weight Override By field, the Gross & Tare fields will be enabled. If nothing is entered in the Weight Override By field, the system will NOT enable the Gross & Tare fields.
Cancel, closes the window without enabling the Gross and Tare fields.
Enables the Reason field, an existing reason code must be entered/selected prior to saving the transaction.
Changes to Shipping Entry Windows
Open Bulk Shipping Entry or Grain Shipping Entry
(Transactions >> CINCH Grain >> Outbound\Sales >> Bulk Shipping Entry) or (Transactions >> CINCH Grain >> Outbound\Sales >> Grain Shipping Entry)
Override & Reason
Enabled if User Extension Maintenance’s Allow Wt Override with Reason in Shipping Entry is selected.
Selecting Override
Opens the Weight Override Information window asking Who is overriding scale weights. This is a free form field. User ID validation will NOT be conducted.
Ok, if information has been entered in the Weight Override By field, the Gross & Tare fields will be enabled. If nothing is entered in the Weight Override By field, the system will NOT enable the Gross & Tare fields.
Cancel, closes the window without enabling the Gross and Tare fields.
Enables the Reason field, an existing reason code must be entered/selected prior to saving the transaction.
Changes to Bulk Transfer Entry
Open Bulk Transfer Entry
(Transactions >> CINCH Grain >> Bulk Transfer Entry)
Override & Reason
Enabled if User Extension Maintenance’s Allow Wt Override with Reason in Bulk Transfer Entry is selected.
Selecting Override
Opens the Weight Override Information window asking who is overriding scale weights. This is a free form field. User ID validation will NOT be conducted.
Ok, if information has been entered in the Weight Override By field, the Gross & Tare fields will be enabled. If nothing is entered in the Weight Override By field, the system will NOT enable the Gross & Tare fields.
Cancel, closes the window without enabling the Gross and Tare fields.
Enables the Reason field, an existing reason code must be entered/selected prior to saving the transaction.
The system will not distinguish which weight (origination or destination) has been overridden.
Changes to Inquiry Windows
Open Inbound Scale Ticket Inquiry Zoom, Bulk Ticket Inquiry Zoom, Load Shipping Inquiry Zoom, Bulk Shipping Inquiry Zoom, or Bulk Transfer Inquiry Zoom
(Inquiry >> CINCH Grain >> Purchases/Inbound >> Inbound Scale Ticket Inquiry >> Ticket Zoom)
(Inquiry >> CINCH Grain >> Sales/Outbound >> Load Shipment Inquiry >> Shipment Zoom)
((Inquiry >> CINCH Grain > >Bulk Transfer Inquiry >> Number Zoom)
Override button opens the Reason Log Inquiry
Visible if User Extension Maintenance’s Allow Wt Override with Reason in (Ticket Entry, Shipping Entry or Bulk Transfer Entry) is selected.
Type displays the transaction type were the window was open from; GrainShip, BulkShip, ScaleTicket, BulkTicket, or BulkTransfer.
Document displays the transaction number.
Scrolling window:
Document Number displays the transaction number.
Reason displays the Reason Code ID used to manually update the scale weights.
Update Information displays the “Who” manually updated the scale weights.
Date displays the date the scale weights were updated.
Time displays the time the scale weights were updated.
This chapter describes an enhancement made to the way freight is calculated. A new Freight Rate UOM has been added to calculate freight in a different UOM in which an item is sold/purchased. The Freight Rate U of M must be defined within the transactional item’s base UOM schedule. (CIN-1433)
This chapter contains the following section(s):
Changes to Shipping Method Detail Maintenance
Changes to Transaction Windows (U of M Validation)
Changes to Freight Entry & Inquiry Windows
Changes to Shipping Method Detail Maintenance
A new field has been added to the Shipping Method Detail Maintenance window to calculate freight in a different unit of measure than a transaction’s UOM.
Open Shipping Method Detail Maintenance
(Microsoft Dynamics GP >> Tools >> Setup >> Company >> Shipping Methods >> Additional >> Freight Extensions)
Enabled only when Freight UofM Type is set to Per Gross Unit or Per Net Unit.
Enter the unit of measure in which freight amounts will be calculated.
If a unit of measure is not entered, freight amounts will be calculated using the unit of measure assigned to the transaction. (Previous Functionality)
Warning: The system normally calculates freight once. If changes are made to a transaction or a Freight Rate U of M is added to a Ship Company after freight has been calculated. It is up to the user to validate and update freight accordingly.
Changes to Transaction Windows (U of M Validation)
Selection of an item or ship method within a transactional window will trigger a validation of each’s unit of measure. These unit of measures must exist within the item’s unit of measure schedule with a translation to the base unit of measure. (CIN-8676)
The outcome of the validation will be one of the following.
If both UOMs are the same or the Ship Company’s Freight Rate U of M is blank, the system will calculate freight by using the transaction’s unit of measure. (Previous Functionality)
If the UOMs are different and the Ship Method’s Freight Rate U of M exists in the Item’s Unit of Measure Schedule with a quantity equivalent to the base, the system will calculate the Freight in the Ship Method’s Freight Rate U of M.
Example: An item has a base unit of measure of LB (Pound) and conversions for BU (bushel) and CWT (100 weight). A transaction is created to sell/purchase the item in BU and the freight must be calculated in CWT. The system will convert the BU into LB and CWT into LB, divide the item’s UOM in LB by the Ship Company’s UOM in LB, and multiply it by the Freight Rate to come up with the Freight Amount for the freight unit of measure of CWT.
If the UOMs are different and the Ship Method’s Freight U of M DOES NOT exist in the Item’s UOM Schedule with a quantity equivalent to the base, the system will display a warning indicating that the Freight Rate U of M defined for this Ship Company is not defined to the Base UOM within this item's U of M Schedule and cannot be used.
The following transactional windows are where the validation will occur.
Sales Contract Entry
Sales Contract Amendment Entry
Load Order Entry
Grain Shipping Entry
Bulk Shipping Entry
Grain Shipment Invoicing
Bulk Shipment Invoicing
Unit Train Shipment Entry
Mass Load Order Update
Direct Shipment-Single Ticket
Purchase Contract Entry
Purchase Contract Delivery Entry
Purchase Contract Amendment Entry
Purchase Load Entry
Inbound Scale Ticket Entry
Bulk Ticket Entry
Bulk Transfer Load Generator Enty
Bulk Transfer Entry
Inbound In Transit Unit Train Entry
Inbound In Transit Ticket Entry
All Freight Entry Windows
Warning: The system normally calculates freight once. If changes are made to a transaction or a Freight Rate U of M is added to a Ship Company after freight has been calculated. It is up to the user to validate and update freight accordingly.
Changes to Freight Entry & Inquiry Windows
A new, display only, field called Freight Rate UoM has been added to the freight entry windows to reflect the unit of measure for the Freight Rate field when the Freight UoM (Type) is set to Per Gross Unit or Per Net Unit.
Unit of measure validations will take place when a Shipping Company is selected. The following freight entry windows have this new functionality.
Sales Contract Freight Entry (Multiple Carrier)
Sales Contract Freight Amend Entry (Multiple Carrier)
Sales Contract Freight Inquiry
Unit Train Freight Entry
Load Order Freight Entry
Load Generator Freight Entry
Load Order Freight Inquiry
Load Shipping Freight Entry
Load Shipping Feight Inquiry
Mass Load Order Freight Entry
Purchase Load Freight Entry
Purchase Load Freight Inquiry
Inbound In Transit Ticket Freight Entry
Inbound In Transit Unit Train Freight Entry
Inbound In Transit Unit Train Unload Freight Entry
Inbound Unit Train Freight Entry
Ticket Freight Entry
Ticket Freight Inquiry
Bulk Transfer Load Freight Entry
Bulk Transfer Load Freight Inquiry
Transfer Freight Entry
Transfer Freight Inquiry
Warning: The system normally calculates freight once. If changes are made to a transaction or a Freight Rate U of M is added to a Ship Company after freight has been calculated. It is up to the user to validate and update freight accordingly.
Appendix A: New Windows, Report & Tables
This section lists the new windows, reports and tables added to this release. Based on the Microsoft Dynamics GP security model, access will need to be determined per security task.
NEW Windows
Display Name | Form Name |
Reason Log Inquiry | IRCSReasonLogInquiry |
Bulk Transfer Multi Lot Entry | IRGNBulkTransMultiLotEntry |
Transfer Multi Lot Inquiry | IRGNBulkTransMultiLotInquiry |
Saels Contract Freight Amend Entry | IRGNSalesContractAmendFreightEntry |
Sales Contract Freight Entry | IRGNSalesContractFreightEntry |
Sales Contract Freight Inquiry | IRGNSalesContractFreightInquiry |
NEW Reports
Report Name |
NA |
|
NEW Tables
Table Name |
IRCSReasonLog |
IRGNBulkTransferLots |
IRGNSalesCtrFreightWH |
IRGNSalesCtrFreightWHTEMP |
IRGNSalesCtrFreightWHVER |
IRIVUOMTEMP |
Changes that may affect Reports or Data
Reports/Data |
NA |
1
I
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.