Skip to main content

supplyPushArrivalDates

Pushes arrival dates from Endless to the ERP records that hold them: a shipment's draft ASN or the transfer orders its posted ASN created, and a purchase order's open lines.

Authentication Requirements​

Requires the supply:push_to_accounting permission for the company.

Business Rules​

  • Between one and 50 shipments and purchase orders in total, each belonging to the company
  • Dates only. Quantities, locations, and the posting date are never written
  • An optional arrival date overrides the saved date for exactly one shipment without changing its expected arrival date in Endless; batches use each record's saved date
  • A draft ASN receives the actual ship date and expected arrival date. Posted transfers receive only the expected arrival date and keep their shipment dates
  • A purchase order writes its expected date to the header and to lines that are still open and not yet on the water; received lines are left alone
  • Records that cannot be updated are skipped with a reason rather than failed: no actual ship date, archived, not in the ERP yet, already received, or a post that has not finished
  • Only one shipment push, post, or arrival date update runs per integration at a time

Error Scenarios​

  • **VALIDATION**: the selection is empty or too large, a record belongs to another company, or the integration cannot push arrival dates for the selected record type

Behavior​

Returns a process ID immediately; the push runs in the background. The process metadata lists each record under outcomes as { identifier, outcome, reason }, where outcome is updated, skipped, or failed.

supplyPushArrivalDates(
  input: SupplyPushArrivalDatesInput!
): AsynchronousActionResponse!

Arguments​

supplyPushArrivalDates.input ● SupplyPushArrivalDatesInput! non-null input common​

Parameters for SupplyPushArrivalDates

Type​

AsynchronousActionResponse object common​

Asynchronous action response type