If there is no file to load, check whether other application data has been received from Ford via the BCM, and log a call with the Ford CDS help desk if necessary.
What do you want to look up?
ERROR: Check posting mnemonic setup in system parameters
Results from incorrect VSB parameter setup. Refer to VSB champion.
ERROR: Could not open ????? word search file, word searches will not function
The problem is in WS extract. Refer to Support.
ERROR: Load failed - Unable to read acknowledgement prime record type
The message archive group is not set up. Refer to Support.
ERROR: Log file is > 95% full
The log file is either not being nibbled or it needs extending. Refer to Support.
ERROR: Mandatory message type missing from group
Indicates corrupt raw data. Clear acknowledgements and ask supplier to resend, then load again. Possibly a GMA or GDM issue.
ERROR: Master posting tables not setup
Results from incorrect VSB setup. Refer to VSB champion.
ERROR: Message archive is > 95% full
The message archive index file is either not being nibbled or it needs extending. Refer to Support.
ERROR: More than maximum permitted number of messages per group
Indicates corrupt raw data. Clear the acknowledgements and ask supplier to resend, then load again. Possibly a GMA or GDM issue.
ERROR: New vehicle defaults not set up
Results from incorrect VSB setup. Refer to VSB champion.
ERROR: Newst default has no physical locn, dealer codes require location mappings
Results from incorrect dealer code map setup. Refer to VSB champion or Support.
ERROR: No dealer codes selected
You did not select a dealer code from the displayed list.
ERROR: No default account status specified in gvacp for ????????
Company parameters are not set up. Refer to Support.
ERROR: No default progress code specified in gvacp for ????????
Company parameters are not set up. Refer to Support.
ERROR: No entries in dealer code map
The dealer code map is not set up. Refer to Support.
ERROR: No franchise letters specified in gvacp for ????????
Company parameters are not set up. Refer to Support.
ERROR: No GVA type selected
You did not select a vehicle acknowledgement type from the displayed list.
ERROR: Posting dictionary ????? not set up for this company
Results from incorrect VSB parameter setup. Refer to VSB champion.
ERROR: Posting mnemonics in system parameters setup incorrectly
Results from incorrect VSB parameter setup. Refer to VSB champion.
ERROR: Priority user required to generate posting tables
Posting tables have been modified and MS needs a new copy. This requires either KCC or the user who modified the tables to enter the vehicle acknowledgements package.
ERROR: Reading acknowledgement parameters
Results from incorrect parameter setup. Refer to Support.
ERROR: Reading acknowledgement path
Results from a problem with the acknowledgement directory. Refer to Support.
ERROR: Reading GVA company parameter file
Company parameters are not set up. Refer to Support.
ERROR: System parameters not found for ??/??
Results from incorrect core product setup. Refer to module champion.
ERROR: Unable to access invoice buffer
Probably 95% full. Refer to NL champion.
ERROR: Unable to access record type
Indicates corrupt raw data. Clear acknowledgements and ask supplier to resend, then load again. Possibly a GMA or GDM issue.
ERROR: Unable to access VS log file
Probably 95% full. Refer to VSB champion.
ERROR: Unable to find message definition record
Entry in message archive group does not exist in GDM. Refer to Support.
ERROR: Unable to link VSB record to order
Caused by a fault when writing to the key map. Refer to Support.
ERROR: Unable to locate all column mapping records
GDM definition and column mapping mismatch. Refer to Support.
ERROR: Unable to lock gmaix record
Caused by GMA index record being locked, possibly resulting from another user accessing the application.
ERROR: Unable to lock import parameter file
Caused by GVA parameters being locked, possibly resulting from another user accessing the application.
ERROR: Unable to lock stock record
Probably caused by the stock record being edited. Refer to VSB champion.
ERROR: Unable to open acknowledgement file
Caused by a problem with the raw data feed. Refer to data supplier.
ERROR: Unable to open file, ??.??.?????
File missing or locked etc. Refer to Support.
ERROR: Unable to read account status file
Caused by a problem with the VSB account status file. Refer to VSB champion.
ERROR: Unable to read acknowledgement parameters
Caused by a problem with the GVA type. Refer to Support.
ERROR: Used vehicle defaults not set up
Caused by a problem with the VSB setup. Refer to VSB champion.
ERROR: Usdst default has no physical locn, dealer codes require location mappings
Caused by a problem with the dealer code map setup. Refer to VSB champion or Support.
ERROR: VSB record is already linked to an order
You are trying to attach order to stock record. Refer to VSB champion.
INFO: Acknowledgements cleared
No action required
INFO: Acknowledgements held
No action required
INFO: All selected records were successfully cleared
No action required
INFO: All selected records were successfully held
No action required
INFO: All selected records were successfully processed
No action required
INFO: Exceptions cleared
No action required
INFO: There are no acknowledgement files to view
Possibly results from a comms failure
INFO: There are no exceptions to report!!
No action required
INFO: There are no held acknowledgements!!
No action required
INFO: There are no matching files to view
Possibly results from a comms failure
INFO: There are no unprocessed acknowledgements!!
No action required
WARNING: exceptions failed to clear
Temporary lock. Try again.
WARNING: records failed to hold
Temporary lock. Try again.
WARNING: The Key Mapping file has fewer than 1000 free records and needs extending
Refer to Support.
WARNING: There were exceptions generated
Review the exceptions list.
WARNING: There were no matches
Adjust your search criteria.
MM Multiple MK vehicle records exist
Warning for the purpose of assisting database cleansing
MK Writing MK vehicle record
Error creating MK vehicle record. Check file size.
NF Unable to locate vehicle record
Warning that vehicle cannot be located or created in VSB automatically. Create the stock record manually, ensuring addition of COMM/ORDER number, before processing the acknowledgement.
MV Multiple VS vehicle records exist
Warning that there is more than one potential match for the acknowledgement. Use stock-link functionality.
ST Vehicle status too advanced
Warning that account postings have been generated for the vehicle and that the acknowledgement data will not be imported. If you want to update the vehicle you must first lower the account status.
LK Unable to lock vehicle record
A fault occurred in attempting to lock the matched vehicle record. The stock reference is in use.
SV Writing back vehicle record
A fault occurred in attempting to create or re-save the vehicle record. Check file size.
CH Writing back VS vehicle chassis
A fault occurred in attempting to update the VSB record with the MK reference. Create the link manually.
DD Vehicle primary build failed
Model or variant code missing from franchise data. Ensure incremental franchise data update set to run automatically.
CX Chassis mismatch
Linked stock record has different chassis number from that in the acknowledgement. Check and correct the VSB record.
C1 Creating stock template
Unable to lock VS controls. Seek assistance from VS champion.
SP Vehicle specification build failed
A fault occurred in attempting to build or amend the specification. Recover the vehicle record manually.
PT Posting table missing
Posting table needs to be created for MODEL/VARIANT.