This is normally a Priority 8 option that enables you to maintain details of the type of communication between Dialogys and the DMS. The Listener listens in on the port and performs certain operations depending on the commands supplied by Dialogys. Operation codes must be set up to determine which operations are valid when communicating with Dialogys. There is a standard, initial set-up, and no changes are envisaged after that unless Renault introduces new operations.
To access the Renault Dialogys Operations Form:
From the RENAULT OPERATIONS Menu, select the Dialogys option.
The Dialogys Menu is displayed.
Select the Maintain operation codes option.
The Renault Dialogys Operations Form is displayed.
This form is displayed when you select the Dialogys option from the RENAULT OPERATIONS Menu, then select the Maintain operation codes option from the Dialogys Menu. It enables you to maintain details of types of communication between Dialogys and the DMS.
Operation code: Renault-defined operation code - for example: 01
Description: Renault description of operation code
Valid code: This is a Y/N value. If Y, the DMS supports this operation.
Message: This message is displayed on the Dialogys screen if the operation is not valid.
01 DMS status: 01 operation code is for Dialogys to enquire as to the state of the Dealer Management System (DMS) - for example, whether it is operational, down, busy, and so on. The DMS cannot return a Down status because the Listener must be operational to interpret requests from Dialogys in the first place. However, the DMS can return status information as to whether it is busy or available. Because Kerridge is not providing interfaces for raising estimates or invoices through Dialogys, only Status codes 0 or 1 are returned. The return message leaves the DMS release, OS release, and Dialogys interface program release fields blank by default.
90 Stop [Dialogys interface]: This operation code is not used. Instead, the DMS returns Status code Y with a message that this operation is not supported.
a1 Account number: This operation code is not used. Instead, the DMS returns Status code Y with a message that this operation is not supported.
e1 Estimate: This operation code is not used. Instead, the DMS returns Status code Y with a message that this operation is not supported.
f1 Continuation estimate: This operation code is not used. Instead, the DMS returns Status code Y with a message that this operation is not supported.
¡1 Init.of invoicing parameters: This operation code represents an initialisation query that is required when starting a communications session.
|1 List of parts: This operation supplies the DMS with a list of parts, up to a maximum of 100, to be included in a Point-of-Sale order (WIP). Dialogys allows for the automatic creation of orders within the DMS. However, to enable important functions and checks within the DMS, all orders should be manually created in the DMS to start with. The following data from Dialogys is ignored:
As well as sending the order list, Dialogys sends a Parts List ID. This is used to write to a new Dialogys orders file on the DMS. This file, (RE.MS.dgord), is used to validate that an order has not been previously received.
The DMS performs the following:
Order reference: Where the Customer order reference field on the DMS order is blank, the order reference supplied by Dialogys is written into the Customer order field. The Dialogys order reference does not overwrite an existing customer order reference and is not recorded anywhere else on the DMS order.
Text to be printed on form: Not currently used
Price to be used: Where the part exists in the Stock File, the price is the normal price for this customer, and the customer's normal discount terms apply. If the part does not exist in the Stock File but exists in the Price File, the prices from the Price File are used instead. This is standard, Point-of-Sale functionality. Where the part does not exist in either the Stock or the Price File, a temporary line is created and price information must be entered in the WIP as per normal operations.
Order Type (status): If the Dialogys type is set to - (minus) , the order line status is set to 2 if there is sufficient, free stock of this part to satisfy this demand, otherwise the line status is set to 1. Status 1 indicates a lost sale due to price, and Status 2 indicates a lost sale due to insufficient stock.
If the Dialogys type is 0 or 1, and there is insufficient, free stock to meet this demand, the status is set to V for Vehicle-off-Road (VOR) back-order. If the type is 2, and there is insufficient demand, the status is set to S for normal Stock back-orders.
For all other types, or where there is sufficient stock to supply demand, the status is set to M, and what course of action to take can then be determined.
Where the type is 0, 1, or 2, and there is some free stock but not sufficient to satisfy the entire demand, the DMS sets the status to M and enables decisions on what course of action to take manually. Satisfying part of a demand and back-ordering the balance is not automatic as, in some cases, a partial supply is of no use.
Split: Any split information received is ignored. The values for splits are blank.
Order reference for line: This information is ignored.
Return codes: Return codes of 3 and 4 are not used. Only the following codes are returned:
0 - OK
1 - Unknown order number
2 - Order exists but cannot be used
5 - Impossible to create this order
6 - Dialogys Parts list ID already received
Automatic printing of parts list: Not used
n1 Name of customer: This operation code is not used. Instead, the DMS returns status code Y with a message that this operation is not supported.
o1 Order: This operation asks the DMS for information about a specific order. Statuses are returned as follows:
Status 1 - Unknown order number - is returned if the order cannot be found within Autoline.
Status 2 - Order exists but cannot be used - is returned if the order is found, but is set for deletion or has been used already and no longer exists in Point-of Sale.
Otherwise, Status 0 - OK - is returned.
The following information relating to this order is returned:
Account number: If a vehicle was attached to this order, the account number associated with this vehicle is returned. This may not be the account number associated with this order, as it could be an internal repair order charged internally, or a warranty order, or an order being charged against a fleet maintenance company, and so on. If there is no vehicle attached to this order, the account number associated with the order is returned.
Customer in account flag: A value of 1 is always returned.
Customer data: If a vehicle is associated with this order, customer details relating to this vehicle's owner are returned, but need not be the same as those associated with this order.
Vehicle technical description: The vehicle details for the vehicle associated with this order are returned. Where no vehicle is associated, blank information is returned.
Team: Blank information is returned.
Splits: Not currently used. Blank values are returned where split data is expected.
r1 Reference: This operation asks the DMS for information about specific parts references, which are supplied by Dialogys. Up to 21 parts references can be included in each request. For each reference, the DMS performs as follows:
Status code: The DMS checks whether the reference exists in the Stock File and/or Price File, and returns the appropriate status code. These are:
0 in both
1 - in neither
2 - in price but not stock
3 - in stock but not price
Description: This is the description from the stock file, by default. However, if the reference only exists in the Stock File, this is the description from the Price File.
Location: These are the first seven characters of the bin location.
Price without taxes: This is the official, retail price from the Price File. If the Price File record does not exist, this represents the retail price from the Stock File.
Quantity in stock: This is the free stock reported on the stock record - that is, actual, physical stock less any reserved quantity.
CORT: This field is not populated.
Prices with taxes: This is the VAT-inclusive, retail price for this part if supplied over the counter. It does not take into account any local, or special, VAT schemes. That is, the VAT code supplied by Renault for this part is used. A VAT mapping table is required to link Renault's VAT codes to the equivalent codes used by the dealer within Autoline. This value is rounded to two, decimal places.
Price code: This information is available on the Renault-supplied Price File, and is taken from there. The field in question is the Discount code (DISCOUNT) in the Renault Price File.
Family code: This information is available on the Renault-supplied Price File, and is taken from there. The field in question is the family code (FAMCODE) in the Renault Price File.
Deposit reference: This field is not populated.
Supersede information: If there is a one-to-one supersession, the information relating to the supersede reference is returned. Where this is a supersession chain, the next reference in the chain that has free stock is returned - failing that, the last reference in the chain.
s1 Service: This operation code is not used. Instead, the DMS returns Status code Y with a message that this operation is not supported.
u1 Update DMS cust and vehicle: This operation code is not used. The operation supplies the DMS with vehicle and customer information. The DMS can then update its own tables with data manually verified on Dialogys and which the user deems to be correct.
Because Dialogys does not recognise a return code other than 0, the only means of notifying the Dialogys user of any problem encountered while updating the Autoline database files is to return Status 0 with a message about these problems - for example: Vehicle record not found, and so on. On the DMS, customer data is not updated, but a certain amount of vehicle data is. For security reasons, creation of new customer or vehicle data records in this manner is not permitted. Where a one-to-one match exists for a vehicle, update of the following information is allowed:
VIN: If the VIN on the Autoline database is blank, and there is only one match using the registration number, it can be updated from the data supplied by Dialogys.
Registration number: If the registration number on the Autoline database is blank and there is only one match using the VIN, it can be updated from the data supplied by Dialogys.
Additional table: Not currently in use. All the data contained in the additional vehicle table as described in Vehicle technical description can be updated. No validation of this data takes place within Autoline. It is assumed that either the Dialogys user or the Dialogys system has manually entered, or validated, this data correctly. However, if the data coming from Dialogys are blank, it does not over-ride existing values.
v1 Vehicle: This operation asks the DMS for information about a vehicle in the Autoline Marketing Vehicle database and the associated customer, after either a registration or vehicle identification number (VIN) is provided. If no vehicles matching the supplied data are found within the Autoline Marketing Vehicle database, return Status 1 - Unknown vehicle - is sent. Where two or more matches are found within the Autoline database, this status is sent, but a detail of the uniquely identifiable Autoline record number and vehicle description for each matching vehicle is also sent in the Message section of the response. This Message section is displayed in Dialogys and can warn the user that there is more than one vehicle match. As there is no direct user interaction between Dialogys and Autoline, a choice of vehicles from which to select is not offered.
Where a single match has been found, the following information is returned:
Account number: The Autoline account code from the vehicle record. It may not be the Sales Ledger account for this vehicle's owner, but could be a catch-all, vehicle, cash sales account assigned to this vehicle when the record was created.
Customer in account flag: A value of 1 is always returned. (Whether or not an account is a real customer account, is not validated.)
Customer data: The name, address, and contact details for this vehicle's owner.
Note: These are returned from the Marketing database, not from the Sales Ledger Account file. This ensures that the correct information is returned where the account for this vehicle is set to a catch-all, cash sales account.
Vehicle technical description: A significant amount of the vehicle technical information required by Dialogys is not currently stored on Autoline, and there are no fields dedicated to this data. An additional table, not currently in use, exists to record this information. Held within Renault Manufacturing Systems on Autoline, it has the same unique identifiers as the vehicle record within the Marketing database. This ensures a one-to-one relationship between this additional, vehicle information and the source vehicle itself.
Order List and split data: Split data are currently not used. Split flags and split lists are shown as blank. The Order List flag in the returned data contains the following indicators:
- 0 - only one, open order for this customer exists.
1 - no open orders for this customer
2 - multiple, open orders for this customer
3 - the DMS cannot return a list of open orders.
Order list detail is returned as documented by Renault in the Dialogys interface document. The search is limited to open orders for this vehicle.
w1 [Ask for] List of parts from an order: This operation code is not used. Instead, the DMS returns Status code Y with a message that this operation is not supported.
