Why:
Dealer specific schedule related data, stored within the external system VOSP may be required by the GDS Fusion users. This function allows users to extract the data so that the Fusion schedule file can be updated.
Where:
From the Vehicle View, select Actions > VOSP extract.
How to Extract VOSP Data:
When the option is selected, Fusion initiates contact with VOSP and extracts any records that have been deposited under the current dealer number. Fusion then uses this data to update the Schedule File. A parameter applies a shift pattern to extracted data and a report or email with attachment will be produced advising the user if the extract has been successful or not.
Note! Only records where
there is a valid Chassis Series and Chassis Number will be extracted, providing
all TST operations also match.
Related Topics:
Setup:
Control File – Email Control
Set up VOSP report THR788/THP788 with required user list.
Parameters:
|
Parameter Name |
Purpose / Description |
|
VSP002 |
Create VOSP/GDS Interface report. |
|
VSP003 |
Current extract deletes any VOSP schedules that do not have an order number assigned. This new parameter will determine if both Local and VOSP records should be deleted. NEG = As today, only VOSP records (sxVOSP= 1) POS = VOSP and Local records. |
|
VSP004 |
Current extract attempts to 're-align' any manually created schedules with existing VOSP schedules (after the download has been run) based on parameters SEC001 (which checks nnn days before and after the existing non-VOSP schedule for an un-actioned VOSP order - the lowest applicable VOSP schedule date will be used to update the non-VOSP schedule) and SEC002 (which checks nnnnnnnn miles before and after the existing non-VOSP schedule for an un-actioned VOSP order - the lowest applicable VOSP schedule mileage will be used to update the non-VOSP schedule), this new parameter will determine if this processing should apply or not. POS = (Default) will attempt to align records. NEG = Will leave records at current date and mileage |