Distrinet import logic
Renault warehouse import leverages two slightly different import files, both in Excel format:
- SR import (vehicules) - file contains all other orders
- PK import (commandes) - file contains customer assigned orders
Both imports can be configured with different behaviour. However, by default all fields in them are handled the same way.
Field mapping table
Highlighted fields have different label in the files. Content is interpreted same though.
Status updates
Workflow state | On create | On update | Logic |
---|---|---|---|
harbour_arrived | + | + | State field value "SC" |
harbour_departed | + | + | State field value "TDK" |
sold | + | + | sold_status field value: "PK", "VD", "VR" |
jump_off | + | + | sold_status field value not equal: "PK", "VD", "VR" |
arrived_branch | + | + | State field value "DDK" or "DDK/>90" |
Delivered status
For new car:
- setting "create - states - delivered" should be enabled
- if "Actual Delivery Date" in file not empty, then delivered status will be set with date from file
- if "Actual Delivery Date" in file empty, do nothing
if car exist in database and file. Update process
- setting "update - states - delivered" should be enabled
- if "Actual Delivery Date" in file not empty, then delivered status will be set/update with date from file
- if "Actual Delivery Date" in file empty, then delivered status will be unset, delivery date will be set to null
Warehouse car creation
By default import logic should not create warehouse car when specification is flexible. List of flexible states could be defined in clients configuration files. Usually warehouse car should be created only once the vehicle Status value is one of these values:
DHPR, FAB, DP, EXPZ, CZ, EXPE, SC, TDK, DDK, DDK/>90, WYD
With all other Statuses vehicle is imported to Pipe but not to warehouse.
Also we can prevent warehouse car creation by defining rules for sold_status (Type de DR). Statuses PK, VC, VD could be used in configuration file.
we have setting to force create warehouse car :
- "create - always create warehouse car" - always create warehouse car for new car, other settings will be ignored
- "update - always create warehouse car" - always create warehouse car for existing car, other settings will be ignored
Distrinet statuses
Status | Description | Pipe | Cars in Stock |
---|---|---|---|
NAF | Unmatched customer orders | ordered | skip |
AVAF | Vehicle does not have “factory agreement” . It does not have any predictions of factory dates , delivery dates. | ||
M+2 | Vehicle production forecast month +2 | ordered | skip |
M+1 | Vehicle production forecast month +1 | ordered | skip |
M | Vehicle production forecast within month | ordered | skip |
DHPR | Vehicle is in production | ordered | create |
FAB | Vehicle is in production | ordered | create |
DP | Vehicle has exited the factory | ordered | create |
EXPZ | Vehicle set to zone centre | ordered | create |
CZ | Vehicle is at an zone centre | ordered | create |
EXPE | Vehicle is sent to import centre | ordered | create |
SC | Vehicle is at an import centre | harbour_arrived | create |
TDK | Vehicle is en route to dealer | harbour_arrived | create |
DDK | Vehicle has arrived at dealer < 90 days | arrived_branch | create |
DDK/>90 | Vehicle has arrived at dealer > 90 days | arrived_branch | create |
WYD |