ADP DMS Integration - Error Reporting

Transcription

1 DMS Integration - Error Reporting Please see below for a list of errors that may be encountered while using wiadvisor and how to resolve these DMS errors. If you require any further information, please contact the wiadvisor Support Team at wiTECH-1 Types of Errors and Description: Error Category OpCode Mismatch Service Advisor ID invalid Existing Appointment Make Model Abbreviation Connection Timeout Incorrect Data Input Description Data errors in the DMS that cannot be rectified via the wiadvisor user interface Dealer will need to directly correct the data error in OpCode in wiadvisor Pricing Wizard, Dealer Recommended or Customer Concerns (Repairs) is different than in DMS Ensure OpCode is valid in DMS. Ensure the OpCode entered in Pricing Wizard, Dealer Recommended or Customer Concerns (Repairs) interfaces in chrysler.advisor.dashboard.net are correct Re-push after OpCode is corrected Could be any one of the settings for - Reservationist, Dispatch, Password, Technician that was incorrectly provided or setup. Depending on the configuration of your dealerships DMS these settings are required to be configured in wiadvisor back-end in order for integration to work The wiadvisor DMS Integration Team will assist you troubleshoot the concern by correcting the set up based on the specific error message you have received Service Advisor DMS ID is not set up in wiadvisor back-end. Either select a different Service Advisor in Assign Repair Order screen in wiadvisor or contact wiadvisor Integration Team to update Service Advisor DMS ID in wiadvisor back-end and re-push the RO There is an existing appointment for this customer in the DMS Cancel the existing appointment in the DMS and re-push Every vehicle requires a correct Make/Model code in the DMS This error will require the correct Make/Model code to be assigned/added through the UDS function or contact to assist If Make/Model Code already exists contact wiadvisor for further assistance Occasionally DMS systems have connection timeouts Re-push the Appointment If the concern persists, contact the wiadvisor Support Team Most often the error will identify the incorrect data Correct the data and re-push or the contact wiadvisor Support Team Version 1.0 Page 1 of 9 Revision Date: 27-Jun-2013

2 Error Category Record in use or locked Sales Type Description Record is locked / in use by another user within your dealership Unlock record or wait a few seconds and re-push Error - Invalid Sale Type value: Every customer record requires a valid Sale Type o This error will require the updating the Sales Type or contact to assist o If the error persists or Sale Type values are unknown or contact the wiadvisor Support Team Sale Type is null: Depending on your dealership's DMS configuration, every customer record might require a valid Sale Type o If you getting this error, your DMS is configured for the Sales Type field within to be mandatory o has provided the steps to adjust configuration o Provide the dealer with the steps to make this field not mandatory in DMS o If the error persists or Sale Type values are unknown or contact the wiadvisor Support Team Specific Errors by Category and Action to Resolve: Error Category DMS Integration Distinct Errors Action to Resolve OpCode Mismatch Errors:[ "Opcode: 00chz01 - Rotate tires [TEST] is not a valid Opcode." ] 2: Line 1 Key 1: The technician must be a valid technician number. 2: Required parameter Reservationist is missing. 1: The In-service Date must be equal to or less than Delivery Date. 2: address is required for the customer. OpCode in wiadvisor Pricing Wizard, Dealer Recommended or Customer Concerns (Repairs) is different than in DMS Ensure OpCode is valid in DMS Ensure the OpCode entered in Pricing Wizard, Dealer Recommended or Repairs interfaces in chrysler.advisor.dashboard.net is correct Re-push after OpCode is corrected Contact the wiadvisor Support Team Reservationist provided may be invalid, contact the wiadvisor Support Team contact (wiadvisor does not update this Add information requested Version 1.0 Page 2 of 9 Revision Date: 27-Jun-2013

3 Birth Date cannot be a date in the future. NM1013 contact (wiadvisor does not update this L&R Percent Over Prime cannot contain periods. NM1137 Not a valid value for Gender. Must be M or F. NM1102 Outside Salesperson <Outside Salesperson DMS ID>is not in NAME-FILE. NM1312 Price Code may only contain numeric data. NM1002 Service delete code must be a number between NM1203 contact (wiadvisor does not update this contact (wiadvisor Support Team does not update this contact (wiadvisor). The steps to correct are as follows: Form the A logon Menu in -> ANM function -> Update customer record with a valid Outside Salesperson ID contact (wiadvisor does not update this contact (wiadvisor does not update this Typically a process called NND (Nightly Name Deletion) will remove customers on delete status from the system Make sure then you have process scheduled. o The customer records you are unable to update shouldn't have still been on the DMS This is not something that can be done while dealership personnel are actively using the system. After this has been completed, you should be able to successfully utilize the integration by inserting these customers as brand new The dealer does not need to take any action. The dealer can accomplish this on their own with the following steps: From the A Menu in, access function ANM > A for Add/update > S for Service > enter the customer number at the Control Version 1.0 Page 3 of 9 Revision Date: 27-Jun-2013

4 prompt > scroll down to Service Delete Code and re-enter the value there without the 'D' > F3 to save/exit Social Security # may not be the same as the control ID. NM1163 Tag Number 6692 is already in use for vehicle The In-service Date must be equal to or greater than 01/01/2010. Customer insert failed null: Required parameter County is missing Due to the automatic Vehicle ID length feature being turned off, the Vehicle ID cannot be determined from the supplied VIN. The Vehicle ID must be generated manually contact (wiadvisor does not update this Note: suggested that the dealer should not be using the Social Security # as the Customer Number contact (wiadvisor does not update this contact (wiadvisor does not update this contact (wiadvisor does not update this. Steps to correct: From the -A account Menu in, enter function NMS - > Properties -> 4 A/R Customer > General - > Scroll down to County and change DatReq to N (toggle by hitting the spacebar) This is a setup issue the dealer will have to address in the DMS. They need to access function UOP and change option 41, AUTOMATIC VEHICLE ID LENGTH Valid values are: o 6 = Use the last 6 characters of the VIN. o 7 = Use the last 7 characters of the VIN o 8 = Use the last 8 characters of the VIN. o 9 = Use the last 9 characters of the VIN. o 10 = Use the last 10 characters of the VIN. o 11 = Use the last 11 characters of the VIN. o NONE = Feature is turned off o The value is currently set to NONE. Instructions showing how to navigate once inside UOP: o Choose Option 2: CHANGE SETUP OF ONE OPTION Version 1.0 Page 4 of 9 Revision Date: 27-Jun-2013

5 Another RO Open Another RO Open Connection timeout Comp Line <Comp Line Name> is not set up. NM1304 Vehicle insert failed. 1:The Delete Code must be 1-3 positive digits. Vehicle update failed. 1: The registered owner is not a service customer. 1: Customer <Customer Number> has closed repair orders. Customer cannot be removed. THERE IS OPEN ROS FOR THIS VEHICLE Vehicle update failed because vehicle could not be read after it was found via search Choose Option 41: AUTOMATIC VEHICLE ID LENGTH (6/7/8/10/11/NONE) This is a case of older data on the DMS not being validated when originally populated Please have the dealer open the customer on the DMS and try to save it, the UI will then prompt to correct the issues The error is occurring because there is no default vehicle delete code specified in the service setups To remedy this, the dealer will need to follow the same process from case , except they will be changing option 64 in UOP this time The recommended value for this option is 36 In order to make a customer a service customer, the dealer would follow these steps: o From the -S account, enter function CUST > S for Service > enter the customer number at the Control: prompt > scroll down to Service Customer? line > toggle between Y and N with spacebar Close previous RO associated with the customer Close Open RO Attempt to push again. If persists, contact wiadvisor Version 1.0 Page 5 of 9 Revision Date: 27-Jun-2013

6 Connection timeout Connection timeout Existing Appointment DMS RO push failed. The request channel timed out while waiting for a reply after 00:01:00. Increase the timeout value passed to the call to request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout DMS RO push failed. An error occurred while receiving the HTTP response to pipcustomer/services/customerinse rtupdate. This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details 2:Vehicle,Vehicle Number> already has an appointment scheduled on 01/24/13 1:Vehicle ID cannot contain special characters. 2:Comments cannot contain control characters. 2:Remarks cannot contain control characters Customer insert failed null: Invalid zip code format. NM1110 Customer insert failed null: Name1 First name cannot exceed 20 characters. NM1133 Attempt to push again If persists, contact the wiadvisor Support Team Attempt to push again If persists, contact the wiadvisor Support Team Cancel existing appointment in the DMS (appointment was made after last appointment upload to wiadvisor) and repush Update vehicle ID in you DMS and re-push Correct the data entered. Invalid characters include hyphen (-), pound sign (#), forward slash (/), or ampersand (&) Correct the data entered requires zip code to match the City/State combination Correct the data entered. Ensure First Name does not exceed 20 characters Version 1.0 Page 6 of 9 Revision Date: 27-Jun-2013

7 Customer insert failed null: Name1 Last name cannot have punctuation, but hyphens, apostrophes and periods allowed. Strings can be separated by one space, (e.g. st james). NM1132 Address1 can only have alphanumeric, "-", "#", "'", or "/". Canadian addresses can have ",". NM1138 Address1 cannot exceed 45 characters. NM1133 Customer updated failed : null:name1 cannot be greater than 30 characters including spaces and punctuation.%fcnm1148 NAME1 is an Individual. Last name field is required. NM1140 Customer updated failed : null: Zip code must be between one of the following ranges. NM1112 Correct the data entered. The name fields cannot have punctuation, but hyphens, apostrophes and periods are allowed Correct the data entered. Invalid characters include hyphen (-), pound sign (#), forward slash (/) Correct the data entered. Combination of address fields cannot exceed 45 characters Correct the data entered. First Name 1+ Last Name + Middle Name cannot exceed 30 characters Correct the data entered. Ensure that you have selected Business customer type on wiadvisor when updating customer information Correct the data entered requires zip code to match the City/State combination. For example is a valid zip code for New York, NY, but are not. Labor Type Make Model Abbreviation Zip code must be in valid format 2:Line 1 Key 1: The labor type is invalid. 2:Labor Op 1 Key 0: The labor type is invalid 1:Invalid Make Abbreviation for Model Code Correct the data entered requires zip code to match the City/State combination. For example if US 10021; Cana da H0H H0H Confirm if Labor Type entered is active and if yes, contact the wiadvisor Support Team Contact to add Make Model to DMS list or ensure that the Make and Model Codes are valid in your DMS If not please add them through function UDS and add the appropriate code. If the issue Version 1.0 Page 7 of 9 Revision Date: 27-Jun-2013

8 persists, contact the wiadvisor Support Team Record in use or locked Record in use or locked Record in use or locked Record in use or locked Sales Type Sales Type Service Advisor ID invalid 1058:Stock number is currently locked by (genserve) on port :VehID 8L is currently locked by (genserve) on port 6026 Customer updated failed : null: Customer 4* has been changed, updates not allowed Customer updated failed : null: Customer 4* is currently locked by port 6291 adp (C133561,JEO-S) Customer updated failed : null is not a valid Sale Type. NM1308 Customer updated failed : null: Required parameter SaleType is missing 1:Warning, the service advisor number is not on file 2:Line 1 Key 1: The dispatch code must be a valid code Record is locked in the DMS by another user Record is locked in the DMS by another user Record is locked in the DMS by another user Record is locked in the DMS by another user Add Sales Type to DMS or change Sales Type for the customer to valid Sales Type As per follow these steps to correct: "There is a name maintenance setting on the DMS that controls whether or not a value is required for sale type This will not address the situation where an invalid sale type is populated, but it will allow for a null value going forward Toggling that setting is the quickest path to resolution in this case From their -A account (BNT-A in this case), the dealer can access function NMS > Properties > Control Type 4 A/R Customer > Parts, scroll down to Sale Type and change DatReq from Y to N" Change service advisor association for the vehicle or reinstate previous advisors with an inactive status This value can be corrected through VEH function in Dispatch code provided may be invalid Contact the wiadvisor Support Team Version 1.0 Page 8 of 9 Revision Date: 27-Jun-2013

9 2:Required parameter Dispatch code provided may be invalid DispatchMakeCode is missing Contact the wiadvisor Support Team Incorrect Password. Please try again 1:The customer is assigned more than once to the vehicle Contact the wiadvisor Support Team to provide correct password Contact the wiadvisor Support Team Exception of type 'Marketrend.BL.MM.DMSIntegrat ion.v0201.dmsintegrationexcepti on' was thrown Contact the wiadvisor Support Team If you have any questions or concerns, please contact wiadvisor Premium Support at 855-wiADVISOR ( ) or via at Version 1.0 Page 9 of 9 Revision Date: 27-Jun-2013