Skip to main content

Register an Oracle purchase

When an Oracle purchase has been made, the following needs to be done in Snow License Manager:

Add Oracle order manually

To add a new, single Oracle order field by field:

  1. On the Oracle overview and on the Entitlements tab, click the Orders view. The Oracle order list page appears.

  2. Select Add an Oracle order > Add order manually.

  3. On the Order information tab, enter the following information:

    1. Enter Order date.

    2. Select Status from the list:

      • When registering a new Oracle order, select Valid.

      • When upgrading or migrating an order, select status Terminated to highlight that this order is no longer valid.

        This is done to ensure traceability, since historical orders should still be available in the system.

    3. Type Order name and Oracle order number.

    4. Type the applicable Oracle Master Agreement (OMA) or Oracle License and Services Agreement (OLSA) reference.

    5. Optionally, type the Reseller order number.

    6. Optionally, type Internal reference number.

    7. Select the Currency for this order from the list.

    8. Type Area of use and Notes about the order.

    9. Enter information about the person responsible for the order in the Ordered by section.

    10. Enter information about the vendor or contractor for the order in the Vendor/contractor section.

    11. Click Add document to upload documents or add links related to the order.

  4. On the Products tab, click Add product and enter the following information to add the product licenses purchased on the Oracle order:

    1. Select Product categoryProduct type, and Product from the lists.

    2. In the Type list:

      • Select Normal for a new Oracle order.

      • Select Upgrade when upgrading from an earlier version or upgrading to another edition.

      • Select Migration when changing metrics.


        The currently used metrics are Named User Plus and Processor. For older products, there are other metrics. When upgrading a database with old metrics, you need to migrate the metrics to the currently used metrics.

    3. Select Period type, License type, and Metric from the lists.

    4. Type Quantity of licenses and License cost.

    5. Type CSI (Customer Support Identifier).

    6. In the Agreement list, select the agreement to attach the Oracle order to.

    7. In the box to the right of the Agreement list, type the support and upgrade cost for the agreement, normally 22% of the purchase price.

    8. Click Add product to save the changes.

    9. Repeat Step 4 for all products included in the order.

  5. Click Save.

Import Oracle orders

Instead of entering individual Oracle orders manually, you can import Microsoft Excel and comma-separated files containing one or more Oracle orders.


The Oracle order import functionality has no way to validate the uniqueness of licenses in an order, so you need to ensure that the entitlements that are imported are not yet in the system; otherwise, this could result in having duplicate licenses.

To start this process, navigate to the Upload your Oracle orders page using either of the following:

  • Home > Import data > Oracle order import

  • Enterprise > Oracle overview > Entitlements tab > Orders page > Add an Oracle order > Upload document



For more detailed information on the required data for Oracle order import and where the data can be found in Snow License Manager after the import, see the document Data Import Field Description.

Importing an Oracle order file is a four-step, wizard-like process:

  1. On the Upload your Oracle orders page (Upload order in the sidebar):

    1. Click Choose file. The Windows Open dialog appears.

    2. Browse to your Oracle order file (in .xls, .xlsx, or .csv format) and click Open. The file name now appears to the right of the Choose file button.


      If you are not sure that your Oracle order file is correct, click Download template (upper-right corner) to download a Microsoft Excel file that has the correct Oracle import file structure.

    3. Click Save and continue.

  2. On the Import settings page (Import settings in the sidebar):

    1. Select one of the following actions for organizations that appear in the source file, but do not exist in the database:

      • Do nothing: Do not create a new organization.

        • This means that Snow License Manager will not create a new organization, disregarding any data listed under the order import file column name Organization.

        • In this case, the order import status will become Discarded.


        Recommended practice for a SAM manager: Select Do nothing here if you don't know to which organization the Oracle order belongs.

      • Or Create: Create a new organization and attach the order to it.

        • The import file's Organization data indicates to which organization this Oracle order belongs.

    2. If you have not uploaded a .csv file, click Save and continue and continue with Step 3.

      If you have uploaded a .csv file select the delimiter character to use as a column separator:

      • Comma

      • Semicolon

      • Tab


      If you select a delimiter character that is not used in the uploaded Oracle order file, the file import status will become Discarded when you complete Step 4.

      In this case the order import will fail; therefore, you must make changes in the .csv import file so that the delimiter character selection matches the column-separator format of the file to be uploaded.

    3. Click Save and continue.

  3. On the Map fields page (Map fields in the sidebar):

    1. Review the mapping.

      • The Source column is a listing of the import file columns, and Destination is the name in Snow License Manager of each Oracle order field name. This information ends up under the Order information tab on the Oracle order detail view.

      • The minimum required input for the order import to be allowed is marked by an asterisk (*): Order date, Order name, Order number, Purchase currency, Organization, Agreement number, Agreement name, Agreement valid from, Agreement valid to.

    2. If you need to change this mapping, select a different field in the Source column.

    3. Once you are satisfied with the mapping, click Save and continue.

  4. On the Review import page (Review in the sidebar):

    1. Once you are satisfied with these import settings, click Finish report.

      If not, return to any of the previous steps by clicking Back.

    Order import statuses on the Review import page:

    • Complete: The order import will be successful. An order must have this status before you can Assign Oracle licenses to the products included in the order.

    • Incomplete: Required fields are present, but others are missing.

      • The advantage of importing incomplete Oracle orders is that you get them into the Snow License Manager system, where you can then edit them later when you have the rest of the order information.


      Snow Software expects that some customers may already have Oracle order Excel export files that closely match the Snow upload template, but not exactly. In this case, it can be helpful to import these Oracle orders.

      The disadvantage here is that you cannot Assign Oracle licenses as long as the order status is not Complete.

    • Discarded: Here are the reasons why an order can be given this status:

      • Structural error: As stated earlier, orders are given this status in a .csv file import where the delimiter character does not match the selected column separator setting.

      • Logical error: Another example of an imported Oracle order reaching the Discarded status: if any of the required fields have errors, such as the order file containing a currency that is not currently supported by Snow License Manager.

      • Lack of required field: If the order import file is missing any of the required fields, the order in question will be given Discarded status.

      To get any Discarded orders into the system, you must either fix the problem(s) in your import file and repeat the import process, or you can add the order manually, making sure to included valid order and product information.

Associate servers with the Oracle orders

The following needs to be done for all servers to be associated with the Oracle order.

  1. In the Computers category, navigate to the server.

  2. On the context menu, click Edit computer.

    The Edit computer view appears.

  3. On the Oracle tab, click Add.


    The Oracle tab is available only for Oracle servers.

  4. In the dialog box, type search criteria for the Oracle order item, and then click Search.

  5. Click the check boxes to select the correct Oracle order, and then click OK.

  6. Click Save.