This page is under construction
Introduction
Onetrail, in close corporation with it’s customers, is currently developing two new features to increase the coverage for electronic ordering for the ICT industry.
A customer panel is currently active in developing the BTO/CTO (build- and configure to order) order process and we’ve developed the definitions for software license ordering in close corporation with Nolan Business Solutions.
Nolan Business Solution has experience in electronic software license ordering for years now and is an active partner of Onetrail for the UK market. For more info: https://www.nolanbusinesssolutions.co.uk/.
The software license order definition is published as draft here where you can put your vote if you’re interested in implementing software licensing.
You can also contribute to the software license definition by adding comments to the field definitions, you can propose new -, change or delete fields.
Software License in PIP3A4PurchaseOrderRequest
We decided to incorporate the software license fields into the existing order schema and thus not design a complete new schema. This because the software license fields are an addition to the current order. Like the current ProductLineItem element is still valid for licenses and only requires some additional fields for software licenses.
We’ve identified header and line level fields required for software licensing. We’re updating the current LicenseOrder element on header level and add an additional element to the line level ProductLineItem.
b132147e-6934-4407-98ce-c1c83ce128ccDECIDED0d33522c-699f-476e-aa74-f3fb4f14409dDraft for LicenseOrder element on header level- Draft for LicenseOrder element on header level
License Header Fields | Remark | Type | M/O |
Contract Number | Number of the license contract | String | M |
License Customer Number | ResellerID in case of VMWARE/ADOBE. Use the FromRole GLN and code conversion, this field is not required | String | O |
Vendor Name | The name of the software vendor. | String | M |
End User Purchase Order | Purchase Order Number from the end user. This field is not required, we're using the DocumentReference of type WorkOrder for this | String | M |
End User Business Name | End user company name | String | M |
End User Address Line1 | End user address line 1 | String | M |
End User Address Line2 | End user address line 2 | String | M |
End User City Name | End user city name | String | M |
End User Region Name | End user region name | String | O |
End User National Postal Code | End user national postal code | String | M |
End User GlobalCountryCode | End user country code (ISO_3166-1) | String(2) | M |
End User Contact Name | End user contact name | String | M |
End User Telephone Number | End user telephone number | String | M |
End User Email Address | End user email | String | M |
End User Type | Type of end user, also known as license type | String | O |
- Draft for LicensOrderLine element on line level
License Line Fields |
|
|
|
License Reference Number | Reference number to license. For Citrix, this is just comments. For VMware it's Token No. And for Symantec products it's SAN | String | O |
Price Level | Price level. Monthly or annual (AE or PE). MVLP and MFUL for Microsoft | String | O |
License Start Date | Start date of the license | Date | O |
License End Date | End data of the license | Date | O |
Reorder | Reorder flag, renewal | Yes/No | M |
