Fixed data mapping is a component of the GDM structure that facilitates site-specific data mapping. Mappings can be dealer code specific, and one-to-many mappings are also supported.
Franchise:
Some dealers may have separate vehicle and commercial franchise codes, so the mapping type FRAN can be used in conjunction with the external values FORD and FORDC to define the franchise letters. If the franchise codes are the same then suffix the DMS value to ensure that the mapping remains unique.
Locations:
Locations on a stock record created by the acknowledgements package are initially set by the default record. The buying and physical locations are then overwritten if a location code exists in the dealer code map (the selling location is also overwritten for customer order integration packages). The buying, physical and selling stock locations are then run through the fixed data map. For example, if the buying location NEW is specified in the dealer code map, the physical and possibly selling locations would also be set to NEW. If, however, location NEW is head office and not an actual stocking location, and all vehicles ordered by NEW are to reside at location HUN, the physical location can be transformed from NEW to HUN using the fixed mapping option. The GDM identifier would always be GVA for this example. The mapping identifier could be one of < strong>BLOCN?, PLOCN? or SLOCN?, where the ? is replaced by an N for new stock, a U for used stock or Z for non-franchise stock. The DMS value is the replacement location and the external value is the location to be replaced.
Delivery/VHC:
Delivery and vehicle holding compound locations can be mapped to DMS locations using the mapping types DELLOCN and VHCLOCN. For many-to-one mappings, add the DMS value as a suffix.
Default locn:
Default physical location DEFLOCN, used if no map is specified for destination code.
Extra buy loc:
If there is more than one buying location for a given dealer, they must be mapped using the XBUYLOC mapping type.
Commercial:
Commercial dealer codes can be identified using the fixed data map. The mapping type COMMDEAL is used with an external value of blank and a DMS value of TRUE.
Call-off:
VISTA/OTD does not supply the exact adoption date, so we derive this date via a calculation that requires, amongst other things, the number of days following call-off on which a vehicle adopts. Thus we have the mapping types CALLOFF (vehicles) and COMCALLOFF (commercial), with blank external values and DMS values that represent the call-off period. Commercial vehicles can also have call-off periods defined at a model level using the model code as the external value and a DMS value of the model code and call-off period concatenated.
Order types:
VISTA/OTD order types can be mapped using the fixed mapping type ORDTYPE. For many-to-one mappings suffix the DMS value.
Safe progress:
List of progress codes that are to be protected from the update.
Showroom:
The Standard process assigns the Vista status code to the picture field on the vehicle stock record. This mapping allows for an alternative field to be set to assign to. The new assignment must be able to contain the status code (8 characters). This can be set with out a dealer code for all dealers or dealer codes can be assigned for different fields for each dealer.
Dealer transfer order:
This is a list of order types that are checked against if the dealer delivery date is not set to exclude vehicle records from being created.
Price protection:
Price protected progress code, for vehicles whose prices you do not want to be modified. All other details on the VSB record still need updating. Price protection ensures that you do not end up invoicing a new vehicle for more than the customer is expecting to pay.
You can define the name of the VSB field that holds the Vista status text for all or individual dealer codes. This enables vehicle-specific marketing material to be accessed in the Showroom module.
Note: If no mapping entry has been created or if the entry is found to be invalid, the VISTA status continues to populate the picture code.
To define a VSB field name:
From the Vehicle Order Acknowledgements Menu select the Fixed data map option.
The GVA Fixed Data Map form is displayed.
Select Edit > Insert row from the menu bar or right-click any grid row to obtain the context menu and select Insert row.
The Data Map Details form is displayed.
Complete the Data Map Details form fields as follows:
GVA type: VISTAOTD
Mapping type: SHOWROOM
Dealer code: To apply alternative VSB field to all dealer codes leave blank. Location-specific entry can be defined by specifying the dealer code.
DMS value: Name of the VSB field in the VS.newst data file to be updated (selecting the DMS value check box suffixes the DMS value with the external value, facilitating many-to-one Ext-to-DMS mappings).
External value: External value (selecting the External value check box suffixes the external value with the DMS value, facilitating many-to-one DMS-to-Ext mappings).
Note: The VISTA status text is stored in the Short description_1 (SHORTDES) field in the Vehicle acknowledgement status codes table, which may contain a maximum of eight characters. In order for the mapping to be valid, the VSB field should be a C (Character) type and have a length of eight characters or more.
Click Save.
The VSB field name is defined.
Mapping Entry Examples
1. Dealer code specific:
2. Global:
3. For when you want to define the additional progress codes that should not be overwritten with the mapped code from the Status codes table:
Note: The progress code that is updated to the Vehicle stockbook record is derived from the Status codes table in Ford Manufacturer Systems.
This form is displayed when you select the Fixed data map option from the Vehicle Order Acknowledgements menu. The fixed data map is used when a translation is required between data in the VISTA/OTD file and the equivalent data in the DMS. The suffixing functionality facilitates one-to-many mappings.
Menu Bar and Toolbar:
Menu bar Shortcut Toolbar Action File > View templates — — Shows or hides the templates File > Exit ESC Returns you to the Vehicle Order Acknowledgements menu Edit > Edit row — Enables you to edit the currently selected record Edit > Insert row — Inserts a new record after the currently selected record Edit > Delete row —
Enables you to delete the currently selected record Help > Help —
Displays this page in a web browser
Grid:
GVA type: Identifies the GVA type.
Map type: Identifies the mapping type.
Dealer code: Identifies the dealer code (required only if the mapping is dealer-specific).
Internal value: Identifies the DMS value.
External value: Identifies the external value.
S: Selecting this box when you are editing a row enables you to add a DMS value suffix to the external value. This facilitates many-to-one DMS-to-external mappings.
Grid right-click menu:
Edit row: Enables you to edit the currently selected record.
Insert row: Inserts a new record after the currently selected record.
Delete row: Enables you to delete the currently selected record.
