On this page
resolveTransfer
mutation · in the family Inventory operations
What it does
Resolve a transfer’s missing or damaged residuals — decide loss, damage, or found, in one step.
RESOLVE a short/lost/damaged Transfer: EVERY residual disposed in this ONE step via disposition-coded doc-referencing movements (loss / scrap = adjust in_transit- at the dest CURRENT WMA — scrap is the deliberate-disposal twin, damaged / found = value-neutral reclass to damaged / on_hand; returned = the pair: dest relief at the dest CURRENT WMA + the SOURCE book-in at the line's FROZEN at-ship unit cost, WMA recomputed exactly as a dest receive would — the value-conserving round trip; goods returned AFTER receipt ride an ordinary NEW reverse Transfer instead). An incomplete disposition set refuses CONFLICT/UNRESOLVED naming the residuals; over-disposal refuses NAMED; the composed call must fit the one-transaction action budget. Heals across LF status; destination IIs must be ACTIVE — and the returned lines' SOURCE IIs too (they receive the residual). Requires the doc CURRENT revision (OCC) + the unrestricted capability.
What happens
Every residual gets a disposition; the movements post document-referenced; the dispute closes.
Careful
The dispositions are the final word on the discrepancy — they post real stock adjustments.
Who may call it
Capability area: Inventory operations — Receiving, counting, transferring and moving stock.
- Owner
- Manager
- Associate Manager
- Warehouse Associate
- An API key whose scope allows
api:resolveTransfer
Arguments
| Name | Type | Required | Notes |
|---|---|---|---|
input | ResolveTransferInput ResolveTransferInput! | yes | No further notes. |
revision | ID ID! | yes | The revision id you read on the record; the change is refused if an edit landed in the meantime. |
reason | String | no | No further notes. |
Returns
Transfer Transfer! — A stock transfer: ONE shipment event moving stock between two LogicalFacilities of the SAME org group (the never-cross-group law IS the tenancy boundary; the source and destination ORGS may differ = intercompany, attribution stamped at birth). LIGHT weight (same physical location — birth-derived from the LF-PF-PFL spine) completes in the ONE submit step (no reserve, no in_transit). Cancel is pre-ship ONLY; cancelled is the ONE doomed terminal (lists filter it); completed/closed are IMMUTABLE non-doomed history — a write there refuses CONFLICT/IMMUTABLE.
Example request
mutation ExampleResolveTransfer($input: ResolveTransferInput!, $revision: ID!, $reason: String) {
resolveTransfer(input: $input, revision: $revision, reason: $reason) {
id
sysId
type
caption
status
parentId
rootId
createdAt
updatedAt
revisionNum
revision
destinationLogicalFacilityId
weight
sourceOrganizationId
destinationOrganizationId
expectedArrivalAt
carrierRefs
}
}
Variables:
{
"input": {
"transferId": "01900000-0000-7000-8000-1d47d93b0000",
"resolutions": [
{
"lineNo": 1,
"quantity": "2",
"disposition": "<disposition>",
"reason": "Correcting a miscount."
}
]
},
"revision": "01900000-0000-7000-8000-b7960e180000",
"reason": "Correcting a miscount."
}
Send it with the envelope naming the version: "extensions": {"at": {"version": {"name":"genesis","number":0}}}.
Example response
{
"data": {
"resolveTransfer": {
"id": "01900000-0000-7000-8000-37386ae00000",
"sysId": "TF-EXMP-0000-000F",
"type": "Transfer",
"caption": "Blue jeans",
"status": "draft",
"parentId": "01900000-0000-7000-8000-065235280000",
"rootId": "01900000-0000-7000-8000-a093dd800000",
"createdAt": "2027-01-31T00:00:00.000Z",
"updatedAt": "2027-01-31T00:00:00.000Z",
"revisionNum": 1,
"revision": "01900000-0000-7000-8000-b7960e180000",
"destinationLogicalFacilityId": "01900000-0000-7000-8000-3885245e0000",
"weight": "<weight>",
"sourceOrganizationId": "01900000-0000-7000-8000-b627156a0000",
"destinationOrganizationId": "01900000-0000-7000-8000-fcbbe67d0000",
"expectedArrivalAt": "2027-01-31T00:00:00.000Z",
"carrierRefs": [
"<carrier refs>"
]
}
},
"extensions": {
"at": {
"callId": "01EXAMPLE-CALL-ID",
"version": {
"requested": {
"name": "genesis",
"number": 0
},
"serviced": {
"name": "genesis",
"number": 0
}
}
}
}
}
Errors this call can answer
VALIDATION/INVALID— Something in the request is not valid. (VALIDATION)AUTHN/REQUIRED— Sign in to do this. (AUTHN)AUTHZ/FORBIDDEN— Your role does not allow this action. (AUTHZ)RATE_LIMIT/THROTTLED— Too many requests in a short time. (RATE_LIMIT)NOT_FOUND/*— That record could not be found. (NOT_FOUND)CONFLICT/*— The record’s state, or a change made in the meantime, does not allow this; the codes are on the CONFLICT page. (CONFLICT)VALIDATION/VERSION_REQUIRED— The request did not say which app version it came from. (VALIDATION)