See also:
The MDPLUS/VDF parameters define the settings for the import of several types of MDPLUS files containing franchise data.
You need to set up the MDPLUS parameters per franchise, when selecting the Franchise Data company, all franchises for which a MDPLUS parameter record is available are displayed.
What do you want to do?
This form is displayed when you click Manufacturer systems (Module) and MB. Mercedes-Benz (Company) > Menu - Utilities > Mercedes-Benz parameters and you browse to Sales > + MDPLUS/VDF parameters > [no. Company name] on the Project parameters browser. It defines the settings for the MDPLUS interfaces.
Fields:
Franchise code: Select the franchise that is available for the Franchise data company concerned.
Interface File Type: Select from the list the required MDPLUS interface file type.
1 VAF/VG Interface: Uses the VAF/VG file format, which is available since Autoline Revision 8.20.
2 NHS Interface National data: Uses MDPLUS data that is delivered in the NHS file format to the dealers.
3 NHS Interface Factory data: Uses MDPLUS data that is delivered in the NHS file format to the Autoline importer systems.
4 VDF Vehicle definition format: Uses the VDF file import for the selected franchise.
Note: Depending on what Interface File Type you select, some fields are added or removed from the parameter record.
Tabs:
Fields:
Import data for this franchise: Select to import the MDPLUS franchise data for the selected franchise of the chosen company. This will make this franchise available in the franchise list of the import program. This option is also used, to enable an automatically import of de MDPLUS data.
Default VAT code for variant: Enter the VAT code, this code is set on the variant in case a new record is created by the interface.
Use default variant: Select to use the entry of the Default variant parameter as default in case a new record is created by the interface.
Default variant: Enter the default record for the variant when the Use default variant parameter is selected.
Don't use models from MDPLUS: The models within MDPLUS are in most cases different than the models that are used within Autoline. In this case is it necessary to select this parameter.
The import program does not create the MDPLUS models but will use the models that are already available in Franchise Data. The MDPLUS Interface will first try to find the model with the first four digits of the national type. In case this model does not exist is the model code with the first three digits of the national type used. In case no matching model is found, a message is displayed.
Chassis validation: When this parameter is selected the chassis prefix field on the variant record is filled with the valid validation mask for this variant. The Chassis validation is used to make sure that the entered chassis number on the VSB record is valid for the vehicle.
Add option code in description: In some cases could it be useful to have the option code within the description. When this parameter is selected, the option code is added in the description field before the description.
Note: This option can also be used as a default setting for the Add option code in front of description field in the VSB Import from external systems form
Mail group for import information: It is possible to send an email to a user or a group of users after the new MDPLUS data has been uploaded. Enter the email address or the mail group address in the Mail group for import information parameter.
Use MDPLUS option validation: Options within MDPLUS can have the same Option class. It is not allowed to have more than one option from an option class on a vehicle specification. When this parameter is selected a validation done which excludes options with the same option class from the vehicle specification in the Showroom module.
Add option description at model level: Select if you want to add the option description at model level instead of the default variant level.
Note: The Add option description at model level field is available when Interface file type 2 or 3 is selected.
Auditing during import: Select to make the files dd.specs and dd.price available in Database auditing during the MDPLUS import.
Note: Please make sure you have the neccessary data fields of the dd.specs or dd.opprc files set up in the Database audit tool.
Warning: Be aware that the auditing of these files will have a huge impact on the required time for the import process to finish.
Use DD notes to store descriptions: Select to store the full option description in the field Arabic notes (ARABNOTE) of the dd.opnot file during the MDPLUS import.
Note: Please make sure that the reports and formats are changed accordingly.
Import information:
File type: Displays, if the last imported file was a complete file or an incremental file.
Last import done / time taken: Displays the date and duration time of the last import of the MDPLUS data is done for this franchise.
Franchise data time stamp: Displays the creation date and time of the MDPLUS file.
Note: The Franchise data time stamp field is available when Interface file type 2 or 3 is selected.
All parameters that exist and are set for previous versions of MDplus imports, which are also used in the import of VDF files, are copied when selecting the VDF interface.
Fields:
Import data for this franchise: Select to import the MDPLUS franchise data for the selected franchise of the chosen company. This will make this franchise available in the franchise list of the import program. This option is also used, to enable an automatically import of de MDPLUS data.
Skip import of obsolete data: Select to skip the import of data with a validation period ending in the past.
Default model: Enter the model code used as default.
Default variant: Enter the variant code used as default in case a new record is created by the interface.
Warning: Please make sure that the Default variant parameter is completed. The variant and its information is skipped from processing, when this field is blank or a none existing variant code is entered.
Default option: Enter the (Factory fitted) option code which is defined on franchise level in Build specifications and used as default in case a new record is created by the interface. It is possible to use this entered option code for all options types predefined. If the option code is not available for a certain option type, the values of the option code for the "Factory fitted options" option type are used as default.
Warning: Please make sure that the Default option parameter is completed. The option and its information is skipped from processing, when this field is blank or a none existing option code is entered.
Model creation from MDPLUS: By default models will be created automatically using MDplus models provided into the VDF import files.
1 Create models using 3-digits from baumuster: Will automatically create models (if they do not exist) using the 3 digits of the baumusters.
2 Create models using 4-digits from baumuster: Will automatically create models (if they do not exist) using the 4 digits of the baumusters.
3 Use existing models matching the first digits of baumuster: Will not create any models and will only import data for models found on the system. To determine if a model is existing on the system the first the first 5 digits of the baumuster are used to find it on the system. If model is not found the first 4 digits will be used next and when still not found the first 3 digits will be used last.
4 Use first part of MDplus model code: Will look at the first part of the MDplus model code provided (for example, use W164 out of: W164-OFF ROAD. When the model does not exist it will be created automatically otherwise the information will be updated for the model. When no partial model code can be derived out of the model code (missing: -, or no text before: -) provided in the VDF vehicle file (baumuster section, vehicleTypeGroupID) the model will be skipped for import.
Note: The parameter Model creation from MDPLUS is only available if Interface file type 4 - VDF Vehicle Definition Format is selected.
Chassis validation: When this parameter is selected the chassis prefix field on the variant record is filled with the valid validation mask for this variant. The Chassis validation is used to make sure that the entered chassis number on the VSB record is valid for the vehicle.
Add option code in description: In some cases could it be useful to have the option code within the description. When this parameter is selected, the option code is added in the description field before the description.
Note: This option can also be used as a default setting for the Add option code in front of description field in the VSB Import from external systems form
Use MDPLUS option validation: Options within MDPLUS can have the same Option class. It is not allowed to have more than one option from an option class on a vehicle specification. When this parameter is selected a validation done which excludes options with the same option class from the vehicle specification in the Showroom module.
Import only option description: Select to only import option descriptions and skip options prices, relations, and validations.
Add option description at model level: Select if you want to add the option description at model level instead of the default variant level.
Store full descriptions in notes: Select to store the full option description in the field Arabic notes (ARABNOTE) of the dd.opnot file during the MDPLUS import.
Note: Please make sure that the reports and formats are changed accordingly.
Retail price: Select the price use as the retail price in Autoline.
Taxable price: Select the price use as the taxable price in Autoline.
Cost price: Select the price use as the cost price in Autoline.
Mailgroup for import information: Enter the email address or the mail group address, it is possible to send an email to a user or a group of users that new franchise data is available.
This parameter record is a mapping table, which maps the Mercedes-Benz option type to the Autoline option type.
Note: This mapping of the Mercedes-Benz option type and the Autoline option type is also used for the Franchise data import.
Note: These parameters are used to find the options in franchise data and to set the correct VAT and Analyses codes in case an option cannot be found.
Fields:
Select for every Mercedes-Benz option type the Autoline option type from the list and complete the VAT code and Analysis code.
Type: Select the option type that you want to use in Autoline for this Mercedes-Benz option. This option type is needed to find the option in the Franchise data when it is created from MDPLUS.
VAT: Indicates the VAT code that is used when an option of this type is created, available for Interface file type 1, 2, and 3.
Analysis: Indicates the analysis code that is used when a new option is created, available for Interface file type 1, 2, and 3.
CTT code (Mohlsheim code): By default set to K (previously the fixed mohlsheim code) but it is possible to change the value and map it to an Autoline option type, available for Interface file type 4.
Note: The fields on the Files tab are changing, depending on the Interface file type, which can be selected on the General tab.
Fields with Interface file type 2 and 3:
Location of the files: Indicates the directory on the Autoline server where the import file can be found.
NHS Import filename: Indicates the name of the file that contains the MDPLUS data. This file should be located in the directory specified above.
Language translation: MDPLUS can deliver description in several languages within the MDPLUS files. With these parameters, it is possible to link the language code from MDPLUS to the corresponding language slot in Autoline.
Fields with Interface file type 1:
Location of the files: Indicates the directory on the Autoline server where the import file can be found.
Model information: Name of the file with the Model information.
National types: Name of the file with the National Types information.
Options: Name of the file with the Options information.
Sequence numbers: The sequence numbers can be used if you have more import files per file type. In that case, you can put an asterisk (*) in place of the sequence number.
Language translation: MDPLUS can deliver description in several languages within the MDPLUS files. With these parameters, it is possible to link the language code from MDPLUS to the corresponding language slot in Autoline.
Fields:
Location of the files: Indicates the primary location of the VDF import files and sub-directories.
VDF file mask: Indicates the mask which is used to identify compressed archives that should be processed by the VDF interface.
Note: You can use the standard wildcards as * and ?.
Import job alternative file: Allows to set an alternative file name (or mask) for locating the import job file(s) in the compressed archive. When this field is empty (default) import job file are located using the mask: VDF_IMPJOB*.xml.
Note: Either a full filename can be entered or one * can be used to find import job files (for example, ALT_IMPORT*.xml would find all import jobs starting with ALT_IMPORT with the extension .xml).
Language translation: MDPLUS can deliver description in several languages within the MDPLUS files. With these parameters, it is possible to link the language code from MDPLUS to the corresponding language slot in Autoline.
Auditing during import: Select to make the files dd.specs and dd.price available in Database auditing during the MDPLUS import.
Note: Please make sure you have the neccessary data fields of the dd.specs or dd.opprc files set up in the Database audit tool.
Warning: Be aware that the auditing of these files will have a huge impact on the required time for the import process to finish.
Log purge in days: Define the number of days after which the log is purged when running an import.
Note: Zero disables purging of log files.
Language of import files: Select the language which is used to generate the XML files.
Note: This will increase the chances to import the correct descriptions with special characters.
Note: This Tab is only available if Interface File type 4 - VDF - Vehicle definition format is selected and if users have priority 8 or are kcc users.
When an import or a mapping process is started a lock file is written in the VDF-root directory and a user-status-message is set to identify the process running. When a lock file is created the name, the date and the time are stored on the company franchise parameter record.
The Tab displays the stored name of a lock file set by the VDF import interface along with the date and time of the file.
Fields:
Lock: Displays the lock file name.
Date: Displays the lock file creation date.
Time: Displays the lock file creation time.
Lock Tab (Interface file type 4) Tab Buttons:
Fields:
View: Displays the MDplus, VDF - Lock information form with information about the running process from the lock file.
The Locked for data item in the MDplus, VDF - Lock information form can contain one of the values.
IMPORT: The lock file is generated by an import which was started.
MAPPING: The lock file is generated upon starting the processing of mappings.
Note: The View button is only enabled when a lock file is actually present on the system.
Unlock: Removes the lock file from the system and allows the import and/or mapping processes to run.
Note: The Unlock button is available if the system could not find an import or a mapping process running when entering the Lock (Interface file type 4) tab.
Note: The STCDS tab is visible when the STCDS is set up.
Fields:
External system ID: Select the external system ID from the StarConnect parameters.
Note: This creates a mapping between the STCDS external system ID and the selected franchise data company.
Note: The STCDS provides the VDF data. As the STCDS does provide a file name but only the data is the filename defined by Autoline. The VDF interface will store the received information in the VDF import directory for the applicable franchises. This is based on the VDF file mask as specified on the Files (Interface file type 4) tab.
Button Retailer mapping: Opens the SCTDS retailer mapping in which the user can change the External system ID.
Before you can setup the parameters for franchise, you need to add franchise codes per company.
To add a new franchise:
Click New or the 
icon.
The MDPLUS/VDF Parameters form is displayed.
Click Amend, enter Franchise code and complete the parameters fields concerning this dealer.
Click Save, to save your changes.
Your dealer number parameters are represented as a parameter element in the browser, with the Franchise code appended.
You amend a franchise if you need to change the parameters for some reason.
To amend a franchise:
Click the Franchise code element that represents the settings you want to change.
The MDPLUS/VDF Parameters form is displayed for the Franchise code you selected.
Click Amend and make the changes.
Click Save, to save your changes.
If it is necessary to delete an franchise, proceed as follows.
To delete a franchise:
Click the Franchise code element that represents the parameters you want to delete.
The MDPLUS/VDF Parameters form is displayed.
Click Amend.
The Delete button is available.
Click Delete.
You are prompted to confirm deletion.
Click OK to delete the settings.
The record is deleted and the parameter element is removed from the browser.