Skip to main content

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.

note

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 columnDefinition
Field name in MLS fileThe 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 viewEach 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 interfaceThe location of the field in the user interface where the MLS data can be viewed after import.
Field name in the user interfaceThe 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 fileCommentsExampleLocation in the user interfaceField name in the user interface
License Program, License Agreement Type, Agreement type, License/Enrollment/Customer numberInformation 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 V0001222Agreement details headerAgreement name
Agreement StatusAny agreement not already in the system will be imported.ActiveList all agreements view
Authorization / Agreement NumberImported as master agreement for the enrolment.56U3434List all agreements view
License / Enrollment / CustomerV0001222Agreement details headerAgreement number
Agreement Start Date2009-03-18Agreement details | Agreement periods tabValid from
Agreement End Date2012-03-31Agreement details | Agreement periods tabValid to
Customer Name on AgreementOrganization 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:
  • In the report Organizational overview, add the column Organization ID. For more information, see Add columns to lists.
ROOT
5d0ed580-e3e9-4377-a944-9845e8fd6e54
List all agreements viewOrganization
Transaction Associated with AgreementYES - 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 viewValueLocation in the user interfaceField name in the user interface
Agreement typeSoftware agreementAgreement details | Sub-agreement tabAgreement type
Activate Automatic UpgradeYESAgreement details | Settings tabLicense upgrade
Alert on ExpirationNOAgreement details | Settings tabAlerts activated
Restrict OrganizationNOAgreement details | Settings tabRestricted organization access
Subscription AgreementYES | NOAgreement 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 fileCommentsExampleLocation in the user interfaceField name in the user interface
License / Enrollment / CustomerThis value is used for mapping the information on the License Agreement tab with the information on the Transaction Data tab.V0001222Agreement details headerAgreement number
Agreement StatusExpired
Coverage Start Date*2009-03-18Agreement details | Agreement periods tabValid from
Coverage End DateIf 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-31Agreement details | Agreement periods tabValid to
Product DescriptionOfficeSB ALNG LicSAPk OLV NL 1Y PltfrmLicense details | Information tabProduct description
Transaction Quantity644License detailsQuantity
Reseller NameReseller LtdEdit license | Information tabVendor
Date Reseller Submitted to Microsoft2010-08-31License details | Purchase tabDate of purchase
Part NumberThe Part Number is used for mapping the license to applications using the SKU repository and associated product use rights.076-03609License details | Information tabStock-keeping unit (SKU)
Customer Name on AgreementOrganization 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:
  • In the report Organizational overview, add the column Organization ID. For more information, see Add columns to lists.
ROOT
5d0ed580-e3e9-4377-a944-9845e8fd6e54
Edit license | Assignment tabOrganization
Included in License SummaryYES - 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 viewValueLocation in SLM WebField name in SLM Web
Invoice referencePopulated from the MLS field Customer Purchase Order Number.Edit license | Purchase tabInvoice Reference
MetricPopulated with value from SKU.Edit license | Purchase tabMetric
IsUpgradePopulated with value from SKU.Edit license | Purchase tabUpgrade license
Automatic DowngradePopulated with value from SKU.Edit license | Purchase tabDowngrade rights
Automatic UpgradePopulated with value from SKU.Edit license | Purchase tabUpgrade license
Processor / coresPopulated with value from SKU, if SKU is a Processor/ Core license, otherwise the field will not be used.Edit license | Purchase tabProcessor cores
Auto allocate (distribute) licenseAuto allocation is enabled by default.Edit license | Assignment tabAuto allocate
Is incompleteValue is set depending on level of imported information.List all licenses view (the Incomplete column). License details view (status Incomplete).Incomplete