# ESM-SaaS-Order-Fulfillment-Procedures_686069896
## Introduction

This document details how to fulfill SMAX/AMX/HCMX SaaS orders in Control Tower. It contains the licenses for generating customer orders through Control Tower.

## Receive ESM SaaS Orders

- When a new SaaS order comes in, PDL " [smax\_saas\_orders@](mailto:smax_saas_orders@microfocus.com) [microfocus.com](http://microfocus.com/) " receives an email notification that the new order has been generated in Control Tower and requires team to perform order provisioning actions

![](attachments/686069896/686069892.png)

- According to customer's purchase, the SaaS order may include different products and different number of license units. To understand the structure of ESM products, please refer to <ESM Product Structure & License>
- In the notification email, there is a specific Control Tower SaaS order ID, next we need to provision the order in Control Tower based on this ID

## Order Fulfillment Procedures

- Please refer to document to get detail order fulfillment procedures: [SMAX\_Provisioning\_Flow.docx](#)
- Please noticed the above document is using SMAX as example to describe the order fulfillment procedures, there are following products in ESM should be follow the same procedures if it included in customer's order
	- Asset Management X
		- Hybrid Cloud Management X
		- Hybrid Cloud Management X FinOps Express
		- Hybrid Cloud Management X Premium
		- Operations Orchestration
		- Service Management Automation X
		- Service Management Automation X Express
		- Universal Discovery

## Best Practices

### Customer Order License Management

- Once the licenses for the relevant products have been generated and downloaded via the UT ticket attachment, in order to facilitate the organization of these licenses， the best practice is to upload these source excel file to [SharePoint folder](https://opentextcorporation.sharepoint.com/sites/MFI-SMAXSaaSDevOps/Shared%20Documents/Forms/AllItems.aspx?id=%2Fsites%2FMFI%2DSMAXSaaSDevOps%2FShared%20Documents%2F2%2DESM%20SaaS%20Customer%2FLicense&viewid=250c668f%2D9c3b%2D4ad9%2Db164%2D3d6ac18e50c3) with specific naming rules like:  
	  
	**<customer>\_<product name>\_<license unit number>\_<prod or dev tenant>.xls**  
	  
	For example:  
	![](attachments/686069896/686069894.png)
- After then, the Cloud engineer can extract the license key from the source excel file and save as real product license file. The new product license file name can keep as same naming rules.
	- For SMAX its XML format
		- For CMS it's text format

For example:  

- With this practice, it will be easy for Cloud Ops engineer to apply correct license to customer's prod/dev tenants.
