Skip to content
Astera Technology

Correct a joiner’s site code across linked administration requests

Correct an identity-coded site and identify which already-issued requests reference the wrong site.

Use site code rather than display label

Synthetic J13 source specifies site ST-N. Index mistakenly says ST-S. Both display “Office”. Requests R1 desk delivery points ST-S, R2 general guide has no site dependency and R3 locker points ST-N. Local decision corrects J13 and amends only wrong-site requests.

Joiner site association
ReferenceSite bindingAction
J13 indexST-S; sourceST-NCorrect to ST-N
R1ST-SAmend destination
R2NonePreserve
R3ST-NPreserve
Download editable CSV ↓

Inspect linked request destinations

  1. Verify source site identity
  2. Correct J13 code
  3. Compare every linked destination code
  4. Track R1 amendment

Identical display names cannot prove that site codes are interchangeable.

How many linked requests need a site amendment?

Show the worked answer

One, R1. R2 is site-independent and R3 already matches ST-N.

Amend only affected requests

Filled administration checks
CaseAction or resultEvidence boundary
Change all three requestsAvoid unnecessary changeOnly R1 wrong-site
Compare “Office” labelsInsufficientCodes identify distinct sites
Download editable CSV ↓

Record old/new site codes with the amendment outcome. Correcting the source index does not prove R1’s destination was updated.

Related resources