My sales manager and boss got together, because we have three sites and we want to structure and be able to help manage sales flows across all three sites.
We’ve decided to make one sales diary per site. Except for the Antwerp site, where there will be two diaries:
- One for sales in Flanders,
- One for international sales.
Astuce
As a reminder, in a module where you have a defined site, the data presented is only relative to that site.
Change site to view data for another site.
Document numbering, number prefixes #
In Silicon ioi, each document must be clearly recognizable. To achieve this, ioi imposes a prefix on each number. This prefix must be 3 to 5 characters long, in uppercase, and UNIQUE in all ioi documents.
Our boss prefers to work with 4 prefixes per document to allow for greater deployment in the future. With an English connotation to be neutral and “corporate”.
For our configuration, this means
| Site | Sales journal | Offer | Order | Delivery | Invoice |
|---|---|---|---|---|---|
| LIEGE | SALES LIG | QTSLSCONL (cont.) | ORDL | DELL | INVLCRNL (nc) |
| BXL | SALES BXL | QTSBSCONB (cont.) | ORDB | DELB | INVBCRNB (nc) |
| ANT | SALES ANT | QTSASCONTA (cont.) | ORDA | DELA | INVACRNA (nc) |
| INT | SALES INT | QTSISCONTI (cont) | ORDI | DELI | INVICRNI (nc) |
Astuce
You can deactivate a document in one of the logs and perform a routing to another log.
Example: Quotations/orders go into a separate log. For the rest (deliveries/invoices), the second journal diverts deliveries to the first journal.
Astuce
-
Document numbers are actually alphanumeric. That’s why the system asks for the number of digits. The system will add zeros to the left of the document number to arrive at the correct format or base length.
-
This alpha-numeric numbering allows you to create structured numbers.
Example: ORDL2022000456.01 with indices. This makes it easy to manage offer variants, for example.