# Getting Started The following sections introduce you to the first few actions as a new user of IT-Conductor FLUX™. ### Prerequisites * [Sign in to IT-Conductor](https://service.itconductor.com/lead?Product=7050657749437583\&License=true\&License.Expiration=30) and download the FLUX™ transport package. This package contains all the necessary components required to integrate FLUX™ with your SAP system. If you’re already registered with IT-Conductor,[ click here](https://service.itconductor.com/objectSavedSearch?OBJECT_Id=6254330032656119\&itconductor.context=7050657749437583) to download the package.

* Import the FLUX™ transport package into your SAP system using standard SAP transport management procedures. {% hint style="info" %} **Note for FLUX Customers** \ If you are currently using the ZFLUX transaction, you must import the [ZFLUX removal transports](https://service.itconductor.com/objectSavedSearch?OBJECT_Id=6254330032656119\&itconductor.context=7050657749437583) before importing the latest FLUX transport: 1. **ZO2K900147 – Deletes objects in package ZITCONDUCTOR\_SID** \ (This transport deletes all dependent objects and must be imported first) 2. **ZO2K900151 – Deletes package ZITCONDUCTOR\_SID** \ (This transport deletes the package itself and must be imported second) After importing both of these transports, proceed with importing the latest FLUX transport {% endhint %} {% hint style="info" %} **Note:** To be able to import exported data after a System Refresh, the FLUX™ transport must either be in the Production System or re-imported into the currently refreshed System. {% endhint %} * Use Tcode SE38 to run program **BTCTRNS1** to suspend all SAP background jobs before executing FLUX™ on your SAP environment. Once all post System Refresh tasks are completed, run **BTCTRNS2** to reschedule the background jobs. ### How to install the FLUX™ License Key Once you’ve imported the FLUX™ transport package into your SAP system, you’ll have to install the license key. The license key is an alphanumeric code that you should receive in your email upon signing up for IT-Conductor. If you need help finding your FLUX™ license key, please get in touch with [our support email](mailto:support@itconductor.com).

Figure 2: Mail Containing the FLUX™ Product Key

1. Go to your SAP system where FLUX™ will be executed and run tcode **/n/ITCON/FLUX**. If it’s your first time using FLUX™, you’ll get an information message.

1. Click on the checkmark to proceed.

3. Click the **Settings** icon to install the license.

4. Enter the path for **Export Data Directory**. FLUX™ automatically creates the default */usr/sap/trans/ITCONDUCTOR* directory. However, you may specify a different directory for data here. 5. Click on **Product Key.**

Figure 4b: IT-Conductor FLUX™ Settings - Product Key

6. Enter the key from the email attachment and click on the checkbox.

### Export Configuration 1. In your SAP landscape, type the Tcode **/n/ITCON/FLUX** to access the FLUX™ Configuration Cockpit.

Figure 7: IT-Conductor FLUX™ Configuration Cockpit

2. Click on **Create New Configuration.**

3. Add a description for the configuration. Then click on **Proceed** to continue.

Figure 9: Enter Configuration Description and Data Directory

{% hint style="info" %} **Note:** The export data directory defaults to **/usr/sap/trans/ITCONDUCTOR** and it is reserved exclusively for FLUX™. Only FLUX-generated files should be stored here. You may change the directory if needed, but its path must not exceed 130 characters {% endhint %} 4. Select the packages that you’d like to import.

Figure 10: Add Packages to a Configuration

{% hint style="info" %} **Note:** Importing the USER package functions similarly to using transaction codes SCC8/SCC7, exporting and importing all client-specific data under the SAP\_ALL profile (excluding change documents). If SCC8/SCC7 is already being used during the System Refresh, you may continue using them at your discretion, but it is strongly recommended to export the USER package beforehand as a backup of all user data. As part of the USER package import post-processing, the following programs are automatically executed via batch job: 1. **RSUSR405** – Resets all user buffers across all clients. 2. **RSADRCK2** – Cleans up and synchronizes company address data between systems. {% endhint %} 3. Click the **Save** button. This will create a new configuration item on the FLUX™ Configuration Cockpit. 4. Double-click to view the selected packages in the newly created item. You can still modify the packages in the configuration, name, and directory by clicking on '**Change Configuration Description and Directory'.** While they can be re-exported and re-imported, the packages within the Configuration cannot be changed once it has been exported.

Figure 11: Change Configuration Descriotion and Data Directory

7. Once you’re sure of the packages you want to export, double-click on the configuration and click on the **Export Selected Configuration** button.

8. Select the client you wish to export to, then click the check mark. Client-independent tables are always included. When importing a client-specific export, ensure the target client already exists on the refreshed system.

{% hint style="warning" %} **Note:** Please make sure that no other FLUX™ configuration packages or background jobs are running while these packages execute in dialog mode. See [‘Export/Import Jobs Still Running’ Error for more information](https://docs.itconductor.com/user-guide/flux/troubleshooting-guide/jobs-running-error). {% endhint %} The export has been requested. Back in the configuration cockpit, FLUX shows the export SAP system and the clients.

{% hint style="info" %} **Note:** For best practice, export all configuration packages before the System Refresh, even if you do not plan to import them all afterward. Be aware that importing all packages post refresh can be time-consuming. {% endhint %} 9. Check the status of the export by double-clicking on the configuration. The status of each package will turn green when it is done exporting. 10. Click on the green button to check the log of each package.

{% hint style="info" %} **Note:** Please make sure that all the packages in the configuration are exported before starting the import. {% endhint %} ### Export Condition Codes In FLUX Cockpit, R3trans return codes are displayed as status indicators. Codes 0 and 4 appear with a green status (successful or completed with warnings), while codes 8 and above are shown in red to indicate errors. **Condition Code 0**

Figure 17: Export Condition Code 0 - FLUX Cockpit View

Figure 18: Export Condition Code 0 - Log View

**Condition Code 4**

**Condition Code 8**

### Import Configuration 1. To import the packages, double-click on the same configuration and click on **Import Selected Configuration**

2. Click **Yes** on the pop-up window to continue. This will start the import.

{% hint style="warning" %} **Note:** If you’re importing the **VARIANTS** and **BATCHJOBS** configuration packages, they must be included in the same configuration and imported **first** after a System Refresh. This ensures their history is not overwritten during the FLUX™ import process. See [VARIANTS and BATCHJOBS Packages Import Errors](https://docs.itconductor.com/user-guide/flux/troubleshooting-guide/import-errors) for more information. {% endhint %} 3. Wait for a few minutes until the status of all the packages turns green. Click on the import green button to see the logs.

4. You may also check these logs against Tcode SM37.

Figure 27: IT-Conductor FLUX™ Background Jobs on SM37

4. To download the logs, go back to the FLUX™ Configuration Cockpit, select a configuration, and click on the **Zip and Download All Log Files** button.

Figure 28: Zip and Download Log Files on IT-Conductor FLUX™

6. Save the logs in your preferred location. FLUX™ unifies the export, import, and application logs in one zip file.

{% hint style="info" %} **Note:** The Application Log keeps records for a maximum of 2 days. {% endhint %} ### Import Condition Codes In FLUX Cockpit, R3trans return codes are displayed as status indicators. Codes 0 and 4 appear with a green status (successful or completed with warnings), while codes 8 and above are shown in red to indicate errors. **Condition Code 0**

Figure 29: Import Condition Code 0 - FLUX Cockpit View

Figure 30: Import Condition Code 0 - Log View

**Condition Code 4**

**Condition Code 8**

### Display and Navigation Features FLUX provides several options to help you organize and customize the information displayed on the configuration cockpit. These features allow you to sort, filter, and adjust the layout so you can quickly locate the data you need. * You can **sort** any column in ascending or descending order by clicking the sorting icons.

* Use the **filter** option to narrow down the list of configurations or jobs based on specific criteria

* The **Change Layout** option allows you to customize your display by choosing which columns appear on the configuration cockpit. You can show or hide fields, rearrange column order, and tailor the view to match your workflow.

### Video {% embed url="" %} Video 1: IT-Conductor FLUX Trailer {% endembed %} {% embed url="" %} Video 2: IT-Conductor FLUX V 1.0.1 Features Video {% endembed %} {% embed url="" %} Video 3: IT-Conductor FLUX SAP Post Copy Automation Webinar {% endembed %}