MLS import
Microsoft License Statement (MLS) files can be imported. The files must be in .xlsx format, and in its original state (unaltered). The MLS import will import agreements and licenses, and map licenses to applications using the SKU (Stock-keeping Unit) repository. Moreover, the import will apply product use rights information where possible.
License information is imported from the License Agreement and the Transaction Data tabs of the MLS file. The following sections describe the information on these tabs that are used during import.
The MLS import is a powerful tool and will enable import of significant amount of data very quickly. Before undertaking an import, ensure that the report has been thoroughly validated, and that you understand what the MLS import does.
Definition of table columns
Table column | Definition |
---|---|
Field name in MLS file | The name of the column in the MLS file that contains the data to be imported. The MLS field name must not be altered. |
Field name in MLS import view | Each field in the MLS file must be mapped to a corresponding field in the user interface. This column shows the name of this field as it is displayed in the field mapping step of the import wizard. |
Location in the user interface | The location of the field in the user interface where the MLS data can be viewed after import. |
Field name in the user interface | The name of the field in the user interface where the MLS data can be viewed after import. |
License Agreement tab
The table below shows the columns on the License Agreement tab that are used for import, and the corresponding field names in the user interface where the values are imported.
Field name in MLS file | Comments | Example | Location in the user interface | Field name in the user interface |
---|---|---|---|---|
License Program, License Agreement Type, Agreement type, License/Enrollment/Customer number | Information in the fields License Program, License Agreement Type, Agreement Type, and License/ Enrollment/Customer number are put together and displayed as Agreement name. | Microsoft Open Value Corporate Agreement V0001222 | Agreement details header | Agreement name |
Agreement Status | Any agreement not already in the system will be imported. | Active | List all agreements view | |
Authorization / Agreement Number | Imported as master agreement for the enrolment. | 56U3434 | List all agreements view | |
License / Enrollment / Customer | V0001222 | Agreement details header | Agreement number | |
Agreement Start Date | 2009-03-18 | Agreement details | Agreement periods tab | Valid from | |
Agreement End Date | 2012-03-31 | Agreement details | Agreement periods tab | Valid to | |
Customer Name on Agreement | Organization based on Alias which is set prior to import. If Alias is not used, Organization will be set to ROOT. For Snow License Manager, use the Organization Name in Snow Management and Configuration Center and not the Friendly name. For SAM Core on Snow Atlas: If the import is unable to map to the organization, find the identities for each organization node and add the identities to the import file. To find the Organization ID, also called GUID do the following:
| ROOT 5d0ed580-e3e9-4377-a944-9845e8fd6e54 | List all agreements view | Organization |
Transaction Associated with Agreement | YES - agreement information will be imported NO - agreement information will be discarded Information on discarded agreements can be exported via the MLS import wizard. | YES | NO |
In addition, a number of fields in the user interface will be populated with default values during an MLS import. The table shows the column names used in the MLS import view, values to be set during import, the corresponding field names, and where these fields are visible in the user interface.
Field name in MLS import view | Value | Location in the user interface | Field name in the user interface |
---|---|---|---|
Agreement type | Software agreement | Agreement details | Sub-agreement tab | Agreement type |
Activate Automatic Upgrade | YES | Agreement details | Settings tab | License upgrade |
Alert on Expiration | NO | Agreement details | Settings tab | Alerts activated |
Restrict Organization | NO | Agreement details | Settings tab | Restricted organization access |
Subscription Agreement | YES | NO | Agreement details | Settings tab (value is set depending on License Program) | Subscription agreement |
Transaction Data tab
The table below shows the columns on the Transaction Data tab that are used for import, and the corresponding field names in the user interface where the values are imported.
Field name in MLS file | Comments | Example | Location in the user interface | Field name in the user interface |
---|---|---|---|---|
License / Enrollment / Customer | This value is used for mapping the information on the License Agreement tab with the information on the Transaction Data tab. | V0001222 | Agreement details header | Agreement number |
Agreement Status | Expired | |||
Coverage Start Date* | 2009-03-18 | Agreement details | Agreement periods tab | Valid from | |
Coverage End Date | If Coverage End Date is the same as the Agreement End Date, the license will use the SA period as the agreement period. Otherwise the period will based on information on Coverage Start Date and Coverage End Date. | 2010-03-31 | Agreement details | Agreement periods tab | Valid to |
Product Description | OfficeSB ALNG LicSAPk OLV NL 1Y Pltfrm | License details | Information tab | Product description | |
Transaction Quantity | 644 | License details | Quantity | |
Reseller Name | Reseller Ltd | Edit license | Information tab | Vendor | |
Date Reseller Submitted to Microsoft | 2010-08-31 | License details | Purchase tab | Date of purchase | |
Part Number | The Part Number is used for mapping the license to applications using the SKU repository and associated product use rights. | 076-03609 | License details | Information tab | Stock-keeping unit (SKU) |
Customer Name on Agreement | Organization based on Alias which is set prior to import. If Alias is not used, Organization will be set to ROOT. For Snow License Manager, use the Organization Name in Snow Management and Configuration Center and not the Friendly name. For SAM Core on Snow Atlas: If the import is unable to map to the organization, find the identities for each organization node and add the identities to the import file. To find the Organization ID, also called GUID do the following:
| ROOT 5d0ed580-e3e9-4377-a944-9845e8fd6e54 | Edit license | Assignment tab | Organization |
Included in License Summary | YES - license information will be imported. NO - license information will be discarded. Information on discarded licenses can be exported via the MLS import wizard. | YES | NO |
In addition, a number of fields in the user interface will be populated with default values during an MLS import. The table shows the column names used in the MLS import view, values to be set during import, the corresponding field names, and where these fields are visible in the user interface.
Field name in MLS import view | Value | Location in SLM Web | Field name in SLM Web |
---|---|---|---|
Invoice reference | Populated from the MLS field Customer Purchase Order Number. | Edit license | Purchase tab | Invoice Reference |
Metric | Populated with value from SKU. | Edit license | Purchase tab | Metric |
IsUpgrade | Populated with value from SKU. | Edit license | Purchase tab | Upgrade license |
Automatic Downgrade | Populated with value from SKU. | Edit license | Purchase tab | Downgrade rights |
Automatic Upgrade | Populated with value from SKU. | Edit license | Purchase tab | Upgrade license |
Processor / cores | Populated with value from SKU, if SKU is a Processor/ Core license, otherwise the field will not be used. | Edit license | Purchase tab | Processor cores |
Auto allocate (distribute) license | Auto allocation is enabled by default. | Edit license | Assignment tab | Auto allocate |
Is incomplete | Value is set depending on level of imported information. | List all licenses view (the Incomplete column). License details view (status Incomplete). | Incomplete |