Importing PageConnect/XPPS files

SECURITY  Security level with Admin permission to configure Other Extensions & Tools. Refer to Admin security settings.

NAVIGATION   > Admin > Extensions & Integrations > Other Extensions & Tools > Xerox PageConnect/XPPS™ Import

To import your file, do the following:

1. Download the PageConnect/XPPS Billing Details File each month from the Xerox Service Contract Order Tool (SCOT), selecting the File Export Format option of Autotask, and save it to your desktop.

1. Go to > Admin > Extensions & Integrations > Other Extensions & Tools > Xerox PageConnect/XPPS™ Import. The Xerox PageConnect/XPPS™ Import page opens, with the General tab displayed.

2. Click Choose File, and navigate to the file you downloaded. If you attempt to import a file of a different format, you will see an error message: "Files of type "'[file extension]" are not supported. Please select an .xml file."
3. Click Import.

Autotask will perform several validations on the import file. The file will only be imported if there are no validation failures. You will see a success message: "Your Xerox PageConnect/XPPS file has been successfully processed. Click OK to continue."

4. If the print output type Unit Cost for any of the products in the import is different than the Contract Unit Cost on the corresponding installed product's contract for the matching material code, you will be presented with a confirmation message: "# of the device(s) in your import file have a color or mono unit cost in your import file that differs from their contract unit cost in Autotask, or they do not have a contract unit cost in Autotask. These contract unit cost(s) have been updated in Autotask".

NOTE  Only the Unit Cost in the Contract is updated, not the Unit Cost of the Material Code in Admin.

This means that Xerox has changed the amount it charges YOU for the overage on the printer. We are updating the numbers in the contract, to make sure the Contract Profitability reports remain accurate. You may consider changing the price you charge your customer for the overage, to avoid losing money. Refer to Charge Defaults.

5. Click OK to continue.

If there are one or more validation failures, an error log table will appear. You can use the information reported in this error log table to correct your import file or add the missing printer as a device to a customer, then re-import the file. The log will display the serial number of the printer for which the error occurred.

NOTE  Use "Find" to locate the offending printer's block of data in the XML file.

• Click Print to print the error log
• Click Export to export the error log as a .csv file

An import could fail for the following reasons:

Failure Message	Fix
"Unable to find a device with this serial number and this service"	One of the printers for which you have downloaded billing data is not associated with an organization in Autotask. You need to install the Device to the organization, and associate it with the correct Contract and Service. • Open the Autotask Contract and click Devices on the Contract Menu. • Click New. • Select Xerox PageConnect/XPPS as the Device Type. • Select the correct printer model. • Select the Service that will be used to bill the Base Service Fee. • Save the Device. For detailed information on adding a Device to a Contract, refer to Adding and editing devices.
"Device with this serial number is inactive"	If the Autotask record is wrong, search Edit the Device in Autotask and set the status flag to Active. If the import file is wrong, delete the item from the XML file.
"Base Product is not mapped to PageConnect/XPPS [Print Output Type] Material Code" where the bracketed text is replaced by a print output type: "Mono", "Color" "MonoColor1", CLRLVL12, or CLRLVL3	You need to map the Material Codes that will be used to bill the specified print output type overage to the base product. This is done on the Options tab. Refer to Mapping Xerox-related products to material codes.
"ColorOver contains more than 4 decimal places"	Open the XML file and delete the additional decimal places.
"BaseSvc must be numeric"	All these errors must be fixed in the XML file. Open the file and change the data in the referenced fields to a number or an integer.
"BaseSppl must be numeric"
"[Print Output Type]Over must be an integer" where the bracketed text is replaced by one of the following print output types:Mono, Color, MonoColor1, CLRLVL12, or CLRLVL3 For example, "MonoOver must be an integer" or "ColorOver must be an integer"
"[Print Output Type]Begin must be an integer" where the bracketed text is replaced by one of the following print output types:Mono, Color, MonoColor1, CLRLVL12, or CLRLVL3 For example, "MonoBegin must be an integer" or "ColorBegin must be an integer"
"[Print Output Type]End must be an integer" where the bracketed text is replaced by one of the following print output types:Mono, Color, MonoColor1, CLRLVL12, or CLRLVL3 For example, "MonoEnd must be an integer" or "ColorEnd must be an integer"
"[Print Output Type]Adjust must be an integer" where the bracketed text is replaced by one of the following print output types:Mono, Color, MonoColor1, CLRLVL12, or CLRLVL3 For example, "MonoAdjust must be an integer" or "ColorAdjust must be an integer"
"[Print Output Type]Count must be an integer" where the bracketed text is replaced by one of the following print output types:Mono, Color, MonoColor1, CLRLVL12, or CLRLVL3 For example, "MonoCount must be an integer" or "ColorCount must be an integer"
"[Print Output Type]Include must be an integer" where the bracketed text is replaced by one of the following print output types:Mono, Color, MonoColor1, CLRLVL12, or CLRLVL3 For example, "MonoInclude must be an integer" or "ColorInclude must be an integer"
"PeriodBegin must be a valid date"	Open the XML file and correct the date format.

After you have addressed all errors, re-run your import process.