Data Analytics: B2B License Import - Run Now With Exception Handling

Version 5

    Verified Product Versions

    Endpoint Manager 9.6Endpoint Manager 2016.xEndpoint Manager 2018.x


    LANDesk 9.6 SP2

    Data Analytics SP2 with latest content

    How to:

    This document will go over how to use "Run Now With Exception Handling" on the B2B rules to troubleshoot B2B import issues. An exception means that Data Analytics doesn't have that specific SKU attached to the software that you are trying to import the license for. While LANDesk tries to update SKU's with content releases, it is impossible to have every SKU a software vendor provides for a particular product. Which is why we have the ability to manually update and and resolve SKU exceptions.


    Step by Step:

    1. Right click the B2B rule that you want to work on and select "Run Now With Exception Handling".

    2. Once the rule starts running, it will open a window once the first exception has occurred:


    Section 1: This is where you select the software the license is attached to. This list is populated by the Licensed Software list in Data Analytics. You want to make sure you have the correct version selected. If the version you are needing to attach the license to is not in the list, you will need to create a content request for the product. If the license needs to be imported immediately you can manually add the software in Licensed Software. Add multiple products if the license is a multi-product license. Make sure the value matches up with the license that you are importing. In most instances the value will not need to be changed.


    Section 2: This is how the license will show in SLM. You can choose to have each license on a separate line, or have it only on one line.


    Section 3: This is where you select how many licenses to apply to the import. You will only need to change this number if it is a bulk license purchase. For example, if you purchased 55 Microsoft Office licenses, and there is no indication that it is a bulk license in the CSV, you will keep the number of license set to 1. The import is aware of number of licenses it is importing (from a different column in the CSV).  Take a look at the name of the product as well as the quantity listed in the CSV that opens when the exception occurs. In some instances the CSV will list a quantity of '1' but the Name/SKU will say it is for a 50 license bundle of the software. In that case you would want to change the "Number of Licenses For This Entry" to 50 so the correct number of licenses are applied in your environment..


    Section 4: This what the license type will show as in SLM.


    Section 5: Once all your information is correct, you have 3 options on how to proceed. The first option is to "Save SKU and Import License" this will save the SKU in the database (if you import the same SKU it will remember these settings so an exception will no longer occur on this SKU).


    Section 6: This will only import the license as you have entered it here. No SKU information will be saved. Use this option if you are not confident that the information that you entered is accurate. You can always delete the license in SLM that you imported and re-try it.


    Section 7: "Skip" will ignore this entry and moved on to the next exception. The license will not be imported.


    3: Once you have handled all of the exceptions, the B2B rule will finish processing and the licenses that were previously unable to be imported will now be in SLM.