This document explains the automated and manual status logic for Service order and Customer File:


Action

SO Status

Condition

Status Description

CF Status

SO created and saved

New


New

New

Auto status changed when Condition is met and SO is saved

OSRV

Tracking Status--> Origin Pack Out--->If Packing date actual not empty or Loading actual date not empty

Origin Services

OPS Active (If atleast 1 SO among related SO has this status)

Auto status changed when Condition is met and SO is saved

OSIT

Tracking Status--> SIT @ Origin--->Date In date not empty

SIT Origin

OPS Active (If atleast 1 SO among related SO has this status)

Auto status changed when Condition is met and SO is saved

TRNS

Service Order--> Forwarding--> Routing-->Actual Departure date not empty

In Transit

OPS Active (If atleast 1 SO among related SO has this status)

Auto status changed when Condition is met and SO is saved

DSRV

Service Order--> Forwarding--> Routing-->Actual arrival date not empty

Destination Services

OPS Active (If atleast 1 SO among related SO has this status)

Auto status changed when Condition is met and SO is saved

DSIT

Tracking Status--> SIT @ Destination--->Date In date not empty

SIT Destination

OPS Active (If atleast 1 SO among related SO has this status)

Auto status changed when Condition is met and SO is saved

DLVR

Tracking Status--> Destination--->Delivery actual date not empty

Delivered

OPS Active (If atleast 1 SO among related SO has this status)

Auto status changed when Condition is met and SO is saved

CLMS

Claim status for the so, if one claim has been filed i.e. claim's created on date is not empty

Claims

Claims (If all related SO has been delivered but atleast 1 SO has the status claims)

User Action

HOLD

User can select, status as HOLD when SO status is NEW

On Hold

User can select a CF on HOLD when CF status as NEW/ All related SO has status as HOLD

User Action

CNCL

User can select, status as Cancel when SO status not as Cancel or HOLD

Cancelled


User Action

REOP

User can select, status as Reopen when SO previous SO status as Cancel or HOLD

Reopened


User Action

NEW

User can select, status as Reopen when SO previous SO status set as "Ready to close"

New


Auto status changed when Condition is met

2CLS

If either [SO previous status is Cancel] OR [(SO previous status <> Claims) and (sys date() - delivery actual date > 90)]

Ready to close


User Action

CLSD

User can select SO status as closed. Shows warning for confirmation

Closed

[When all related jobs are closed, then status of CF is "Closed"] Or [Closed from Cancel/Lost Sale (Pending)/ Ops Finished

Auto status changed when Condition is met

Active storage

SO of STO job types has count from storage > 1 (add item to loaction in ticket is saved)

Active storage

All transit/STO type jobs have been closed and atleast 1 So with storage job is active