|
| 1 | +--- |
| 2 | +title: Get SAP media for Bill of Materials |
| 3 | +description: How to download SAP media to use in your Bill of Materials (BOM) for the SAP deployment automation framework on Azure. |
| 4 | +author: kimforss |
| 5 | +ms.author: kimforss |
| 6 | +ms.reviewer: kimforss |
| 7 | +ms.date: 11/17/2021 |
| 8 | +ms.topic: how-to |
| 9 | +ms.service: virtual-machines-sap |
| 10 | +--- |
| 11 | + |
| 12 | +# Acquire media for BOM creation |
| 13 | + |
| 14 | +The [SAP deployment automation framework on Azure](automation-deployment-framework.md) uses a Bill of Materials (BOM). To create your BOM, you have to locate and download relevant SAP installation media. Then, you need to upload these media files to your Azure storage account. |
| 15 | + |
| 16 | +> [!NOTE] |
| 17 | +> This guide covers advanced deployment topics. For a basic explanation of how to deploy the automation framework, see the [get started guide](automation-get-started.md) instead. |
| 18 | +
|
| 19 | +This guide is for configurations that use either the SAP Application (DB) or HANA databases. |
| 20 | + |
| 21 | +## Prerequisites |
| 22 | + |
| 23 | +- An SAP account with permissions to download the SAP software and access the Maintenance Planner. |
| 24 | +- An installation of the [SAP download manager](https://support.sap.com/en/my-support/software-downloads.html) on your computer. |
| 25 | +- Information about your SAP system: |
| 26 | + - SAP account username and password |
| 27 | + - The SAP system product to deploy (such as **S/4HANA**) |
| 28 | + - The SAP System Identifier (SAP SID) |
| 29 | + - Any language pack requirements |
| 30 | + - The operating system (OS) to use in the application infrastructure |
| 31 | +- An Azure subscription. If you don't already have an Azure subscription, [create a free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F). |
| 32 | + |
| 33 | +## Acquire media |
| 34 | + |
| 35 | +To prepare for [downloading the SAP installation media](#download-media): |
| 36 | + |
| 37 | +1. On your computer, create a unique directory for your stack SAP downloads. For example, `~/Downloads/S4HANA_1909_SP2/`. |
| 38 | + |
| 39 | +1. Sign in to [SAP ONE Support Launchpad](https://launchpad.support.sap.com/). |
| 40 | + |
| 41 | +1. Clear your download basket. |
| 42 | + |
| 43 | + 1. Go to **Software Downloads**. |
| 44 | + |
| 45 | + 1. Select **Download Basket**. |
| 46 | + |
| 47 | + 1. Select all the items in the basket. |
| 48 | + |
| 49 | + 1. Select the **X** to remove all items from the basket. |
| 50 | + |
| 51 | +1. Add the utility SAPCAR to your download basket. |
| 52 | + |
| 53 | + 1. On the search bar, make sure the search type is set to **Downloads**. |
| 54 | + |
| 55 | + 1. Enter `SAPCAR` in the search bar and select **Search**. |
| 56 | + |
| 57 | + 1. In the table **Items Available to Download**, select the row for **SAPCAR** with **Maintenance Software Component**. This step filters available downloads for the latest version of the utility. |
| 58 | + |
| 59 | + 1. Make sure the drop-down menu for the table shows the correct OS type. For example, `LINUX ON X86_64 64BIT`. |
| 60 | + |
| 61 | + 1. Select the checkbox next to the filename of the SAPCAR executable. For example, `SAPCAR_1320-80000935.EXE`. |
| 62 | + |
| 63 | + 1. Select the shopping cart icon to add your selection to the download basket. |
| 64 | + |
| 65 | +1. Sign in to the [Maintenance Planner](https://support.sap.com/en/alm/solution-manager/processes-72/maintenance-planner.html). |
| 66 | + |
| 67 | +1. Design your SAP system. For example, if you're using **S/4HANA**: |
| 68 | + |
| 69 | + 1. Select the plan for **SAP S/4HANA**. |
| 70 | + |
| 71 | + 1. Optionally, change the Maintenance Plan name. |
| 72 | + |
| 73 | + 1. Select **Install New S4HANA System**. |
| 74 | + |
| 75 | + 1. Select **Next** |
| 76 | + |
| 77 | + 1. For **Install a New System**, enter the SAP SID you're using. |
| 78 | + |
| 79 | + 1. For **Target Version**, select your target SAP version. For example, **SAP S/4HANA 2020**. |
| 80 | + |
| 81 | + 1. For **Target Stack**, select your target stack. For example, **Initial Shipment Stack**. |
| 82 | + |
| 83 | + 1. If necessary, select your **Target Product Instances**. |
| 84 | + |
| 85 | + 1. Select **Next** |
| 86 | + |
| 87 | +1. Design your codeployment. |
| 88 | + |
| 89 | + 1. Select **Co-Deployed with Backend**. |
| 90 | + |
| 91 | + 1. For **Target Version**, select your target version for codeployment. For example, **SAP FIORI FOR SAP S/4HANA 2020**. |
| 92 | + |
| 93 | + 1. For **Target Stack**, select your target stack for codeployment. For example, **Initial Shipment Stack**. |
| 94 | + |
| 95 | + 1. Select **Next** |
| 96 | + |
| 97 | +1. Select **Continue Planning**. If you're using a *new system*, select **Next**. If you're using an *existing system*, make the following changes: |
| 98 | + |
| 99 | + 1. For **OS/DB dependent files**, select **Linux on x86_64 64bit**. |
| 100 | + |
| 101 | + 1. Select **Confirm Selection**. |
| 102 | + |
| 103 | + 1. Select **Next**. |
| 104 | + |
| 105 | +1. Optionally, under **Select Stack Independent Files**, configure settings for non-ABAP databases. You can choose to expand the database and deselect non-required language files. |
| 106 | + |
| 107 | +1. Select **Next**. |
| 108 | + |
| 109 | +1. Download stack XML files to the stack download directory you created earlier. |
| 110 | + |
| 111 | + 1. Select **Push to Download Basket**. |
| 112 | + |
| 113 | + 1. Select **Additional Downloads**. |
| 114 | + |
| 115 | + 1. Select **Download Stack Text File**. |
| 116 | + |
| 117 | + 1. Select **Download PDF**. |
| 118 | + |
| 119 | + 1. Select **Export to Excel**. |
| 120 | + |
| 121 | + 1. Go to your download basket again in the SAP Launchpad. You might need to refresh the page to see your new selections. |
| 122 | + |
| 123 | + 1. Select the **T** icon to download a file with the URLs for your download basket. |
| 124 | + |
| 125 | +## Get download basket manifest |
| 126 | + |
| 127 | +> [!IMPORTANT] |
| 128 | +> Only follow these steps if you want to run the scripted BOM generation. You must perform these actions before you run the SAP Download Manager. If you don't want to run the scripted BOM generation, [skip to the next section](#download-media). |
| 129 | +
|
| 130 | +To get your SAP Download Basket manifest JSON file (`DownloadBasket.json`): |
| 131 | + |
| 132 | +1. Open the **Postman** utility. |
| 133 | + |
| 134 | +1. Add a new request by selecting the plus sign (**+**) button in the workspace tab. A new page opens with your request. |
| 135 | + |
| 136 | +1. On the **Params** tab, set the request type to `GET`. |
| 137 | + |
| 138 | +1. For the request URL, enter `https://tech.support.sap.com:443/odata/svt/swdcuisrv/DownloadContentSet?_MODE=BASKET_CONTENT&_VERSION=3.1.2&$format=json`. |
| 139 | + |
| 140 | +1. Select the **Authorization** tab. |
| 141 | + |
| 142 | +1. For **Type**, select **Basic Auth**. |
| 143 | + |
| 144 | +1. For **Username**, enter your SAP username. |
| 145 | + |
| 146 | +1. For **Password**, enter your SAP password. |
| 147 | + |
| 148 | +1. Select the **Headers** tab. |
| 149 | + |
| 150 | +1. Uncheck the Accept-Encoding and User-Agent check boxes |
| 151 | + |
| 152 | +1. Select the **Send** button. |
| 153 | + |
| 154 | +1. On the **Body** tab, make sure to select the **Raw** view. |
| 155 | + |
| 156 | +1. Copy the raw JSON response body. Save the response in your stack download directory. |
| 157 | + |
| 158 | +## Download media |
| 159 | + |
| 160 | +To download the SAP installation media: |
| 161 | + |
| 162 | +1. On your computer, run the SAP Download Manager. |
| 163 | + |
| 164 | +1. Sign in to the SAP Download Manager. |
| 165 | + |
| 166 | +1. Access your SAP Download Basket. |
| 167 | + |
| 168 | +1. Set your download directory to the stack download directory that you created. For example, ``~/Downloads/S4HANA_1909_SP2/`. |
| 169 | + |
| 170 | +1. Download all files from your download basket into this directory. |
| 171 | + |
| 172 | +> [!NOTE] |
| 173 | +> The text file that contains your SAP download URLs is always `myDownloadBasketFiles.txt`. However, this file is specific to the application or database. You should keep this file with your other downloads for this particular section for use in later sections. |
| 174 | +
|
| 175 | +## Upload media |
| 176 | + |
| 177 | +To upload the SAP media and stack files to your Azure storage account: |
| 178 | + |
| 179 | +1. Sign in to the [Azure portal](https://portal.azure.com/). |
| 180 | + |
| 181 | +1. Under **Azure services**, select **Resource groups**. Or, enter `resource groups` in the search bar. |
| 182 | + |
| 183 | +1. Select the resource group for your SAP Library. |
| 184 | + |
| 185 | +1. On the resource group page, select the `saplib` storage account in the **Resources** table. |
| 186 | + |
| 187 | +1. On the storage account page's menu, select **Containers** under **Data storage**. |
| 188 | + |
| 189 | +1. Select the `sapbits` container. |
| 190 | + |
| 191 | +1. On the container page, upload your archives and tools. |
| 192 | + |
| 193 | + 1. Select the **Upload** button. |
| 194 | + |
| 195 | + 1. Select **Select a file**. |
| 196 | + |
| 197 | + 1. Navigate to the [directory where you downloaded the SAP media previously](#download-media). |
| 198 | + |
| 199 | + 1. Select all the archive files. These file names are similar to `*.SAR`, `*.RAR`, `*.ZIP`, and `SAPCAR*.EXE`. |
| 200 | + |
| 201 | + 1. Select **Advanced** to show advanced options. |
| 202 | + |
| 203 | + 1. For **Upload Directory**, enter `archives`. |
| 204 | + |
| 205 | +1. Upload your stack files. |
| 206 | + |
| 207 | + 1. Select the **Upload** button. |
| 208 | + |
| 209 | + 1. Select **Select a file**. |
| 210 | + |
| 211 | + 1. Navigate to the download directory that you [created in the previous section](#acquire-media). |
| 212 | + |
| 213 | + 1. Select all your stack files. These file names are similar to `MP_*.(xml|xls|pdf|txt)`. |
| 214 | + |
| 215 | + 1. Select **Advanced** to show advanced options. |
| 216 | + |
| 217 | + 1. For **Upload Directory**, enter `boms/<Stack_Version>/stackfiles` where `<Stack_Version>` is a combination of your product information. For example, `S4HANA_2020_ISS_v001` indicates the product type is `S4HANA`, the product release is `2020`, the service pack is `ISS` for the initial software shipment, and the stack is `v001`. |
| 218 | + |
| 219 | +## Next steps |
| 220 | + |
| 221 | +> [!div class="nextstepaction"] |
| 222 | +> [Prepare BOM](automation-bom-prepare.md) |
0 commit comments