Skip to main content
All CollectionsShipping
TrueAuto: Ship To Cumulatives
TrueAuto: Ship To Cumulatives

Learn all about the TrueAuto Ship To Cumulatives here and access the quick guide!

TrueAuto Support avatar
Written by TrueAuto Support
Updated over 2 months ago

Product: TrueAuto

Ship To Cumulatives in TrueAuto are used to track and maintain every cumulative quantity. When the Trading Partner tracks cumulative quantities, it is important to also maintain the Ship To Cumulative in TrueAuto. Cumulative quantities are used to calculate order balances, detect discrepancies, or report fiscal year totals on outbound transactions. Annual cumulative quantity resets will also occur here.

Ship To Cumulatives is the TrueAuto feature that is used to track all supplier, buyer, and Original Equipment Manufacturer (OEM) cumulative quantities as required. Each Ship To Cumulative allows users to set various defaults, such as pack quantity, packaging types, or engineering change level at the Trading Partner, Part Number, and Ship To address level which can be used on outbound shipments and/or invoices. Additionally, details from inbound Electronic Data Interchange (EDI) or integration that need to be retained and applied to outbound transactions may use Ship To Cumulative to store those details; for example, EDI daily shipping schedules may not have a Purchase Order (PO) or Engineering change level but can source them from Ship To Cumulative details stored when the EDI Planning Schedule is received.

A new Ship To Cumulative is created for the combination of trading partner, part number, and ship to location when TrueAuto receives a planned or firm request for the first time.

The following actions may also be accomplished on the Ship To Cumulative screens:

  • Review or adjust cumulative discrepancies

  • Review raw material discrepancies, and fabrication discrepancies, holding the Trading Partner to their highest authorized numbers.

  • Correct product activity discrepancies between TrueAuto and your trading partner.

rev. 11/9/24

Did this answer your question?