Those orders follow a specific workflow. Technical orders are created by the Portal upon receipt of order orders with either unavailable codes not included in the Portal catalogue or orange codes not included in a project/mission standard list.
Such codes will be labelled by the Portal as "NC" (non codified). Here below is an example of how such orders are created.
You inject into the Portal an order 17/BE/AF101/PO01560 :
The Portal performs code codes validation and detects SINSSYDL05- which is either not in the catalogue or orange not included in a standard list. The code is labelled as "NC":
Then the Portal requests a split of the order, to be perfomed performed by the user in charge of validation by clicking on split:
...
A /TEC reference will be created and that will need to be validated likewise the main reference, even if the two will follow a different and independent validation path.
For the first round of validations we will talk about a "request for information" to MSF Supply, whilst the second round will be the actual order:
| Info |
|---|
Splitting order into known and unknown codes allows MSF Supply - and therefore users - to speed up dealing with known codes and ultimately receiving goods in the fastest way. |
...