{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":25807,"path":"it-asset-management/saas-license-management/integrate-with-successfactors.md","title":"Integrating with SAP SuccessFactors","bundle":null,"doc_type":null,"release":"australia","body":"\n# Integrating with SAP SuccessFactors\n\nIntegrating your Software Asset Management application with the SAP SuccessFactors application enables you to track your software subscriptions and to reclaim unused licenses.\n\n**Important:**\n\nYou must request and install the following applications from [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home):\n\n- SaaS License Management\n- SuccessFactors Spoke\n- Software Asset Management integration with SuccessFactors\n\n- If your installed SAP SuccessFactors spoke version is 3.1.5 or lower, follow these steps:\n 1. [Set up basic authentication for SAP SuccessFactors](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/saas-license-management/integrate-with-successfactors.md)\n 2. [Create an SAP SuccessFactors connection](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/saas-license-management/integrate-with-successfactors.md)\n 3. [Create an SAP SuccessFactors integration profile](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/saas-license-management/integrate-with-successfactors.md)\n- If your installed SAP SuccessFactors spoke version is 4.0.0 or higher, follow these steps:\n 1. [Register OAuth application in SuccessFactors](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/saas-license-management/integrate-with-successfactors.md)\n 2. [Upload the JKS certificate in your ServiceNow instance](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/saas-license-management/integrate-with-successfactors.md)\n 3. [Register SuccessFactors as an OAuth provider](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/saas-license-management/integrate-with-successfactors.md)\n 4. [Create the SAML2 assertion producer record](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/saas-license-management/integrate-with-successfactors.md)\n 5. [Create credential record for the OData API](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/saas-license-management/integrate-with-successfactors.md)\n 6. [Create connection record for the OData API](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/saas-license-management/integrate-with-successfactors.md)\n 7. [Create an SAP SuccessFactors integration profile](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/saas-license-management/integrate-with-successfactors.md)\n\n**Important:** Minimize security risks and protect information by granting access only to the necessary user or API permissions.\n\n|Process|Required user role in the SAP SuccessFactors application|Authentication scopes|\n|-------|--------------------------------------------------------|---------------------|\n|Download subscriptions|admin|None|\n|Pull user activity|admin|None|\n|Reclaim subscription|admin|None|\n\n## Set up basic authentication for SAP SuccessFactors\n\nSet up basic authentication to enable access to the SAP SuccessFactors API.\n\n### Before you begin\n\nSAP SuccessFactors Role required: admin\n\n### Procedure\n\n1. Log in to the SAP SuccessFactors instance using your admin credentials.\n\n2. On the page header of your instance, select **Home** > **Admin Center**.\n\n3. Create a group to assign API access permissions to.\n\n **Tip:** Include only non-admin users in this group, as admin users automatically have access to the SuccessFactors API.\n\n 1. In the **Tool Search** field of the Admin Center, search for and select **Manage Permission Groups**.\n\n 2. On the Permission Group dialog box, enter a name for the permission group in the **Group Name** field.\n\n 3. In the Choose Group Members section, specify the users or user groups that you want to include in this permission group by adding them to a People Pool.\n\n People Pools allow you to specify the sets of users or user groups that you want to include or exclude for a permission group. You can either include all users and user groups in a single People Pool or group them into different People Pools. For example, you can create different People Pools for each department or office location within your organization.\n\n To add users or user groups to a People Pool, select an identification category, such as **Username**, and then enter each user or user group in the corresponding text box. Each entry must be separated by a comma.\n\n You can apply multiple identification categories to a single People Pool by clicking **Add another category**. You can also add additional People Pools by clicking **Add another People Pool**.\n\n 4. In the Exclude these people from the group section, specify the users or user groups that you want to exclude from this permission group by adding them to a People Pool.\n\n To add users or user groups to a People Pool, select an identification category, such as **Username**, and then enter each user or user group in the corresponding text box. Each entry must be separated by a comma.\n\n You can apply multiple identification categories to a single People Pool by clicking **Add another category**. You can also add additional People Pools by clicking **Add another People Pool**.\n\n 5. Select **Done**.\n\n4. Configure API access permissions for your group.\n\n 1. In the **Tool Search** field of the Admin Center, search for and select **Manage Permission Roles**.\n\n 2. Select **Create New**.\n\n 3. On the Permission Role Detail form, enter a name for the permission role in the **Role Name** field.\n\n 4. Enter a description for the permission role in the **Description** field.\n\n 5. Under Permission settings, select **Permission...**.\n\n 6. In the Permission settings dialog box, select **Manage Integration Tools** from the left navigation pane.\n\n 7. Select the **Allow Admin to Access OData API through Basic Authentication** check box.\n\n 8. Select **Employee Central API** from the left navigation pane.\n\n 9. Select the **Employee Central HRIS OData API \\(editable\\)** check box.\n\n 10. Select **Done**.\n\n The dialog box closes and you return to the Permission Role Detail form.\n\n 11. Under the **Grant this role to...** tab, select **Add...** to search for and select the permission groups that you created in step [4](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/saas-license-management/integrate-with-successfactors.md).\n\n Adding this permission group allows the associated users and user groups to access the APIs that are enabled in this permission role.\n\n 12. Select **Save Changes**.\n\n\n## Create an SAP SuccessFactors connection\n\nCreate a connection between your SAP SuccessFactors OData API and your ServiceNow instance.\n\n### Before you begin\n\nServiceNow Role required: sam\\_integrator\n\n### Procedure\n\n1. From your ServiceNow instance, navigate to **Process Automation** > **Flow Designer**.\n\n The Flow Designer launches in a new tab.\n\n2. Select the **Connections** tab.\n\n3. Select **View Details** for your SuccessFactors\\_OData connection.\n\n4. From the list of available connections, search for and select SuccessFactors\\_OData.\n\n5. Select **Configure**.\n\n6. In the Configure Connection dialog box, fill in the fields.\n\n |Field|Description|\n |-----|-----------|\n |Connection Name|Name of the SuccessFactors\\_OData connection.|\n |Connection URL|OData API URL of your SAP SuccessFactors instance.|\n |User name|Username for your SAP SuccessFactors admin account. Enter the same username that you used to log in to your SAP SuccessFactors instance in [Set up basic authentication for SAP SuccessFactors](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/saas-license-management/integrate-with-successfactors.md).|\n |Password|Password for your SAP SuccessFactors admin account. Enter the same password that you used to log in to your SAP SuccessFactors instance in [Set up basic authentication for SAP SuccessFactors](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/saas-license-management/integrate-with-successfactors.md).|\n\n7. Select **Configure Connection**.\n\n\n## Register OAuth application in SuccessFactors\n\nEnable client certificate authentication for the outbound communication from SAP Master Data service by generating the `keystore.jks` and `keystore.cer` files.\n\n### Before you begin\n\nRole required: admin\n\n### Procedure\n\n1. Create a JKS certificate by using any one of the following methods:\n\n - Follow the steps in the [Creating Java Keystore\\(JKS\\) with Private Key and Certificate Chain](https://help.sap.com/docs/SAP_Cloud_Platform_Master_Data_for_Business_Partners/246fb358c1c7413289c03b8c72734209/18f5bae37a664396b2ebbc1b3c384c53.html) topic [SAP Help Portal](https://help.sap.com/docs/).\n - Install Java JDK 8 and Open SSL and execute the following commands in the Terminal:\n\n 1. `openssl genrsa -out private.key 2048`\n\n The `private.key` file is generated.\n\n 2. `openssl rsa -in private.key -pubout -out public.key`\n\n Extract the public key from key pair type.\n\n 3. `openssl req -new -x509 -key private.key -out publickey.cer -days 365`\n\n Enter details of the Distinguished Name \\(DN\\). The `publickey.cer` file is generated.\n\n 4. `openssl pkcs12 -export -in publickey.cer -inkey private.key -out successfactors.p12 -name \"successfactors\"`\n\n You’re prompted for a password. The `successfactors.p12` file is generated using the private and public key created in step a and step b.\n\n 5. `keytool -importkeystore -srckeystore successfactors.p12 -srcstoretype pkcs12 -destkeystore successfactors.jks`\n\n You’re prompted for the destination and source file password. The `successfactors.jks` file is created using the `successfactors.p12` file created in step c.\n\n **Note:** Confirm that you enter the same passwords in steps c and d. For example, if you enter the password as `123456` in step c, you must enter `123456` as password in step d too.\n\n2. Log in to the SuccessFactors account as an admin.\n\n3. Navigate to **Admin Centre** and select **Company Settings**.\n\n4. Select **Manage OAuth2 Client Applications**.\n\n5. Select **Register Client Application**.\n\n \\[Omitted image \"manage-oauth-client-sf.png\"\\] Alt text: Managing OAuth2 client applications\n\n6. In the **X.509 Certificate** field, provide the contents of the `publickey.cer` file \\(public key\\) without the headers.\n\n7. Select **Submit**.\n\n\n### Result\n\nThe API Key is generated and displayed.\n\n### What to do next\n\nCopy the API key generated and record the value for later use.\n\n## Upload the JKS certificate in your ServiceNow instance\n\nEnable client certificate authentication for the outbound communication by uploading the JKS certificate in your ServiceNow instance.\n\n### Before you begin\n\nRole required: admin\n\n### Procedure\n\n1. Log in to your ServiceNow instance as an admin.\n\n2. Upload the JKS certificate to your ServiceNow instance.\n\n For instructions to upload the JKS certificate, see [Upload a certificate to an instance](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/t_UploadACertificateToAnInstance.md).\\[Omitted image \"saml-oauth-sf.png\"\\] Alt text: Uploading certificate to an instance\n\n\n## Register SuccessFactors as an OAuth provider\n\nUse the API key generated during the client application configuration to register the application as an OAuth provider.\n\n### Before you begin\n\nChange the application scope to SuccessFactors spoke.\n\nRole required: admin\n\n### Procedure\n\n1. In your ServiceNow instance, navigate to **System OAuth** > **Application Registry**.\n\n2. Select **New**.\n\n3. In the form, fill in these fields.\n\n\n
\n\nField\n\n\n\nDescription\n\n
\n\nName\n\n\n\nUnique name to identify the certificate. For example, `SuccessFactors SAML`.\n\n
\n\nClient ID\n\n\n\nValue of the API key you had copied after registering the OAuth client application in SuccessFactors.\n\n
\n\nClient Secret\n\n\n\n**Note:** Client secret isn’t needed to register the application as an OAuth provider. You can provide any value for this field.\n\n
\n\nDefault Grant Type\n\n\n\nDefault grant type used to establish the token. Select **SAML2 Bearer**.\n\n
\n\nToken URL\n\n\n\nSuccessFactors OAuth server endpoint URL that includes the Company ID in this format: `https:///oauth/token?company_id=`. For example, `https://example.successfactors.eu/oauth/token?company_id=SFCPART123456`.\n\n
\\[Omitted image \"app-registry-sf.png\"\\] Alt text: Application Registries form\n\n4. Select **Submit**.\n\n\n## Create the SAML2 assertion producer record\n\nCreate a SAML2 assertion record to generate the SAML2 assertion and exchange the assertion for the access tokens with the provider.\n\n### Before you begin\n\nChange the application scope to SuccessFactors spoke.\n\nRole required: admin\n\n### Procedure\n\n1. Create a SAML2 assertion producer record in your instance.\n\n 1. Navigate to **All** > **System OAuth** > **SAML2 Assertion Producers**.\n\n 2. Select **New**.\n\n 3. On the form, fill these values.\n\n |Field|Description|\n |-----|-----------|\n |Name|Unique name to identify the SAML2 assertion producer record. For example, `Successfactor SAML OAuth`.|\n |Issuer|Unique identifier for the assertion issuing entity. Provide the ServiceNow instance URL.|\n |Subject NameID|User name to log in to the SuccessFactors instance. For example, `sfadmin`.|\n |Audience|Intended audience for the assertion. Enter the value, `www.successfactors.com`.|\n |Recipient|Intended recipient for the assertion. Enter URL in this format, `https:///oauth/token`.|\n\n \\[Omitted image \"saml-assert-prov.png\"\\] Alt text: SAML2 Assertion Producer\n\n 4. Select and hold \\(or right-click\\) the form header and select **Save**.\n\n 5. Under the **SAML2 Assertion Keystores** tab, select **New**.\n\n 6. On the form, fill these values.\n\n |Field|Description|\n |-----|-----------|\n |Name|Unique name to identify the SAML2 assertion keystore record. For example, `successfactors`.|\n |Signing Key Alias|Alias of key entry stored in the Keystore used to sign the assertion. For example, `successfactors`.|\n |Signing Key Password|Password of the key entry stored in the keystore used to sign the assertion.|\n |Signing Keystore|Required X.509 certificate record. Select the X.509 certificate record that you had earlier created. For more information, see[Upload the JKS certificate in your ServiceNow instance](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/saas-license-management/integrate-with-successfactors.md).|\n\n \\[Omitted image \"saml-assert-keystore.png\"\\] Alt text: SAML2 Assertion Keystore.\n\n 7. Select **Submit**.\n\n 8. Navigate to **All** > **System OAuth** > **SAML2 Assertion Producers**.\n\n 9. Open the SAML2 assertion producer record that you had created.\n\n For example, **Successfactor SAML OAuth**.\n\n 10. Under the **SAML2 Assertion Attributes** tab, select **New**.\n\n 11. On the form, fill these values.\n\n |Field|Description|\n |-----|-----------|\n |Name|Name to identify the SAML2 assertion attribute record. Enter `api_key`.|\n |Type|Type of the **Value** field. Select **String**.|\n |Value|API key generated after the OAuth client application is created in SuccessFactors.|\n\n \\[Omitted image \"saml2-assertion-att.png\"\\] Alt text: SAML2 Assertion Attribute.\n\n 12. Select **Submit**.\n\n2. Associate the SAML2 assertion producer with the application registry record.\n\n 1. Navigate to **System OAuth** > **Application Registry**.\n\n 2. Open the application registry record that you had created.\n\n For example, **SuccessFactors OAuth Reg**. For more information about creating the application registry, see [Register SuccessFactors as an OAuth provider](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/saas-license-management/integrate-with-successfactors.md).\n\n 3. Under the **OAuth Entity Profiles** tab, open the default OAuth entity profile record.\n\n For example, **Successfactor SAML default\\_profile**.\n\n 4. For the **Assertion Producer** field, select the SAML2 assertion producer record you had created.\n\n For example, **Successfactor SAML OAuth**.\\[Omitted image \"oauth-ent-profile-sf.png\"\\] Alt text: Defining OAuth scoped for this profile\n\n 5. Select **Update**.\n\n\n## Create credential record for the OData API\n\nCreate a connection record for the OData API in SuccessFactors. The SuccessFactors spoke connection and credential alias uses these connections to perform actions in SuccessFactors.\n\n### Before you begin\n\nRole required: admin\n\n### Procedure\n\n1. Navigate to **All** > **Connections & Credentials** > **Credentials**.\n\n2. Click **New**.\n\n The system displays the message **What type of Credentials would you like to create?**.\n\n3. Select **OAuth 2.0 Credentials**.\n\n An empty OAuth 2.0 Credentials form is displayed.\n\n4. On the form, fill these values.\n\n\n
\n\nField\n\n\n\nValue required\n\n
\n\nName\n\n\n\nName to uniquely identify the record. For example, enter `SAML_SuccessFactors_OData_Cred`.\n\n
\n\nOAuth Entity Profile\n\n\n\nOAuth entity profile record that is associated with the OAuth application registry you had created. For example, `Successfactor SAML default_profile`.For more information about creating the application registry, see [Register SuccessFactors as an OAuth provider](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/saas-license-management/integrate-with-successfactors.md).\n\n
\n\nActive\n\n\n\nOption to actively use the credential record.\n\n
\n\nOrder\n\n\n\nOrder to apply this credential. For example, enter `100`.\n\n
\\[Omitted image \"saml-sf-odata-cred.png\"\\] Alt text: OAuth 2.0 credentials\n\n5. Click **Submit**.\n\n\n### Result\n\nThe credential record to authorize actions using the OData API is created.\n\n## Create connection record for the OData API\n\nCreate a connection record for the OData API in SuccessFactors. The SuccessFactors spoke connection and credential alias uses these connections to perform actions in SuccessFactors.\n\n### Before you begin\n\nRole required: admin\n\n### Procedure\n\n1. Navigate to **All** > **Connections & Credentials** > **Connection & Credential Aliases**.\n\n2. Open for the record for **SuccessFactors OData**.\n\n For example, **SuccessFactors\\_OData**.\n\n3. From the **Connections** tab, click **New**.\n\n The system displays an empty HTTP\\(s\\) Connection form.\n\n4. On the form, fill these values.\n\n |Field|Description|\n |-----|-----------|\n |Name|Name to uniquely identify the record. For example, `SAML_SuccessFactors_OData_Conn`.|\n |Credential|Credential record you created for the OData API. For example, `SAML_SuccessFactors_OData_Cred`.|\n |Connection URL|SuccessFactors service root URL in this format: `https:///odata/v2`. For example, `https://apisalesdemo2.successfactors.eu/odata/v2`.|\n |Active|Option to actively use the connection record.|\n\n5. Click **Submit**.\n\n\n### Result\n\nThe connection record for the OData API in SuccessFactors is created.\n\n## Create an SAP SuccessFactors integration profile\n\nCreate an SAP SuccessFactors integration profile to track software subscriptions and optimize licensing for your SAP SuccessFactors applications.\n\n### Before you begin\n\nThe Software Asset Management - SaaS License Management plugin \\(sn\\_sam\\_saas\\_int\\) must be installed from the [ServiceNow Store](https://store.servicenow.com/).\n\nChange the application scope to **Global**.\n\nServiceNow Role required: sam\\_integrator\n\n**Important:** You must select the **Software Asset Management integration with SuccessFactors** check box for this integration while installing optional features on the [Application Manager](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/application-manager.md) page. For more information about choosing the required SaaS applications, see [Request SaaS License Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/saas-license-management/request-saas-license-management.md).\n\n### About this task\n\nIf you’re using Software Asset Workspace, the option to create the SuccessFactors integration profile in Core UI is inactive.\n\n### Procedure\n\n1. Navigate to the integration profile.\n\n\n
\n\nInterface\n\n\n\nAction\n\n
\n\n**Core UI**\n\n\n\n1. Navigate to **All** > **Software Asset** > **SaaS License** > **Direct Integration Profiles**.\n2. Select **New**.\n3. Select **SuccessFactors Integration Profile**.\n\n\n
\n\n**Software Asset Workspace**\n\n\n\n1. Navigate to **License operations** > **User Subscriptions** > **Direct integration profiles**.\n2. Select **New**.\n3. Select **SuccessFactors** from the drop-down list.\n4. Select **Continue**.\n\n\n
2. On the form, fill in the fields.\n\n\n
\n\nField\n\n\n\nValue\n\n
\n\nDisplay Name\n\n\n\nName of the integration profile. For example, `SuccessFactors Integration`.\n\n
\n\nStatus\n\n\n\nStatus of the integration profile. - If you have not published the integration profile, this field is automatically set to **Draft**.\n- If you have already published the integration profile, this field is automatically set to **Published**.\n\n\n
\n\nProfile Type\n\n\n\nType of integration profile. This field is automatically set to `SuccessFactors Subscription`.\n\n
3. Review the required user roles or API permissions specified in the **Vendor configuration** field for each process to minimize security risks and optimize SaaS licenses.\n\n **Note:** For more information, see [Minimal user permissions](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/saas-license-management/integrate-with-workfront.md) table.\n\n 1. In the Download Subscription Subflow section, verify that the **Subflow** field is set to **SuccessFactors Download Subscriptions**.\n\n **Note:** The **Download subscriptions** check box is selected by default and you can't clear it.\n\n 2. In the Calculate Activity Subflow section, verify that the **Subflow** field is set to **SuccessFactors Update User Activity**.\n\n **Note:** The **Download Activity** check box is selected by default. If you clear it, the activity scheduled job **SAM - Refresh <displayname> Activity** isn't created.\n\n 3. In the Reclaim Subscription Subflow section, verify that the **Subflow** field is set to **SuccessFactors Reclaim Subscription**.\n\n **Note:** The **Reclaim subscriptions** check box is selected by default. If you don't want to reclaim subscriptions, you can clear this check box. If you clear it, the removal candidates are created but the reclaim subscription subflow isn't triggered or the reclamation process isn't initiated.\n\n4. Select **Save**.\n\n Your ServiceNow instance creates a draft integration profile.\n\n The **Connection & Credential** field appears and is automatically set to **sn\\_successfactors.SuccessFactors\\_OData**.\n\n5. Generate and add the SAP SuccessFactors user login report to your integration profile.\n\n This report is required for retrieving the last activity date of your SAP SuccessFactors users. You must generate and add the latest version of this report every time you want to update the last activity date of your SAP SuccessFactors users in the Software Subscriptions \\[samp\\_sw\\_subscription\\] table.\n\n 1. Log in to your SAP SuccessFactors instance using the admin credentials.\n\n 2. On the page header of your instance, select **Home** > **Admin Center**.\n\n 3. On the page header of the Admin Center, select **Reporting**.\n\n 4. Select **New** to create a report.\n\n 5. When prompted to select the type of report that you want to create, select **Report - Table** > **Select**.\n\n 6. Under **How would you like your data to be structured?**, select **Single Domain**.\n\n 7. Under **What data would you like to start with?**, select **Login Data**.\n\n 8. Click **Select**.\n\n The Creating Login Data report page opens.\n\n 9. On the **General Info** tab, fill in the fields.\n\n |Field|Description|\n |-----|-----------|\n |Domain|Domain from which you’re retrieving data. This field is automatically set to **Login Data**.|\n |Report Name|Name of the report.|\n |Description|Description of the report.|\n |Report Priority|Priority of the report.|\n |Remove Styling|Deselect this check box.|\n\n 10. On the **People** tab, select **Refine criteria**.\n\n 11. In the Define Team dialog box, fill in the fields.\n\n |Field|Description|\n |-----|-----------|\n |Team Manager|Manager of the team for which you want to create this report. Select **Logged In User**.|\n |Team Reporting Type|Type of report that you want to create for the team. Select **Other Filters**. When you select this report type, you can define report scopes to filter the user groups that you want to include in the report. See [step 14](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/saas-license-management/integrate-with-successfactors.md) for more details.|\n |Include inactive users|Option to include all inactive team members in the report. Leave this option unselected.|\n\n 12. Select **OK**.\n\n The dialog box closes and you return to the **People** tab.\n\n 13. In the Define Report Scope section of the **People** tab, select the **Division**, **Department**, and **Location** report scopes to define filter criteria for the user groups that you want to include in the report.\n\n By default, all filter criteria for these report scopes are enabled.\n\n 14. On the **Columns** tab, select **+ Select Columns** to specify the data columns that you want to include in the report.\n\n You can sort, group, or rearrange the columns as needed.\n\n 15. Select the **Last Login** and **User Sys ID** check boxes so that the first column is Last Login and the second column is User Sys ID on the report.\n\n 16. On the **Configuration** tab, specify whether you want your data columns to display data in either the date only or the date and time format.\n\n For each applicable data column, select either **Date** \\(date only\\) or **Timestamp** \\(date and time\\). After you select the format for each data column, select **OK**.\n\n 17. On the **Filters** tab, select filters to refine the data that is displayed on the report.\n\n 18. Select **Refine Criteria** > **Employee Login Detail** > **Last Login**.\n\n A pop-up displays with the Define last login filter.\n\n 19. Select the **By Rule** > **Add rule** tab.\n\n 20. From the drop-down list, select the **Greater than** option.\n\n 21. Enter the date from when you want to generate the report.\n\n You must select a date not older than a couple of weeks to keep the file size within allowed limits.\n\n 22. Select **Done** after you select the filters.\n\n 23. Select **Generate**.\n\n 24. In the Download section of the generated report, select **Excel** to export the report as an Excel file.\n\n **Note:** The Excel file must not be greater than 5 MB.\n\n 25. Return to your SAP SuccessFactors integration profile form.\n\n 26. On the Integration Profile form header, select the Manage Attachments icon \\(\\[Omitted image \"manage-attachments-icon.png\"\\] Alt text: Manage attachments icon.\\).\n\n 27. In the Attachments dialog box, select **Choose file** to locate and select your user login report.\n\n 28. After the report uploads successfully, close the dialog box to return to the integration profile form.\n\n6. After the form reloads, select **Validate Connection** to verify the connection and credential details of this integration.\n\n Validating the connection verifies the Download Subscriptions and Calculate Activity APIs, but not the Reclaim Subscriptions APIs.\n\n7. After the connection is verified, select **Publish**.\n\n8. In the Publish Confirmation dialog box, select **OK**.\n\n **Note:** If you clear the **Download Activity** check box after the integration profile is published, you must revalidate the connections and then republish the integration profile because the following events occur:\n\n - The **Status** field on the integration profile form changes to **Draft**.\n - The **Validate connection** button shows up on the form.\n - The current **SAM - Refresh <displayname> Activity** job gets deleted.\n By default, the activity job runs every one hour and deletes the file attached to the integration profile as part of the clean-up. If the file isn't found, the activity job fails to indicate no new attachment. The job failure has no impact on the already updated last activity.\n\n If you plan to attach the file once everyday or once a week, you can update the run time of the **SAM - Refresh Success Factors Activity** scheduled job accordingly. You can also run this job on demand whenever you attach a file.\n\n You must attach a file every time for the job to run because SAP SuccessFactors doesn’t have an API for activity data pull.\n\n\n### What to do next\n\nAfter the integration connects, your ServiceNow instance automatically creates software models, reclamation rules, and software subscriptions that are refreshed daily.\n\nAfter creating an integration profile, view information about the profile in the Software Asset Workspace by navigating to **License operations** > **User subscription** > **Direct integration profiles**. You can select an integration profile to view the following related lists. If all of the following related lists aren't visible for an integration profile in the default view, you can select the custom integration view from the Details tab:\n\n- Software Models\n- Unrecognized Subscription Identifiers\n- Scheduled Jobs\n- Scheduled Job Results\n- Software Subscriptions\n- Subscription Identifier Exclusion Rule\n- Subscription User Exclusion Rule\n\nAfter creating an integration profile, you can define subscription exclusion rules to keep certain subscriptions from license cost calculations. For more information, see [Subscription exclusions for SaaS and SSO applications](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/saas-license-management/subscription-exclusions.md).\n\nIf you want to set up multiple integration profiles with unique connections, create child aliases to manage different configurations and settings for each integration profile. For more information, see [Create a child alias to set up multiple integration profiles](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/saas-license-management/create-child-alias-saas.md).\n\n**Important:** Child aliases and alias overrides aren't supported for the **SuccessFactors Update User Activity** subflow because this subflow doesn't use REST steps directly where aliases are required.\n\nReview all automatically generated reclamation rules to reclaim user subscriptions. For more information, see [Review a software reclamation rule](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/saas-license-management/add-reclamation-rule-sub.md).\n\nCreate software entitlements for the automatically generated software models to track used software against owned software.\n\n- For more information on creating software entitlements in the Software Asset Management Core UI, see [Create entitlements in Software Asset Management Core UI](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/software-asset-management/track-software-rights.md).\n- For more information on creating software entitlements in the Software Asset Workspace, see [Create entitlements in workspace](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/software-asset-management/create-entitlements-workspace.md).\n- For more information on creating software entitlements using the Software Asset Management Playbook, see [Create entitlements using the guided walk-through](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/software-asset-management/guidedwalk-workspace.md).\n\nReconciliation also runs on your subscriptions as a scheduled job or on-demand. You can view your reconciliation results in the [License Workbench](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/software-asset-management/sam-license-workbench.md) \\(Software Asset Management classic application\\) or the [License usage view](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/software-asset-management/sam-workspace-workbench.md) \\(Software Asset Workspace\\). Use these results to determine your license compliance position and to remediate any non-compliance.\n\n- For more information on running reconciliation in the Software Asset Management classic application, see [Run software reconciliation in Software Asset Management classic](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/software-asset-management/t_RunReconciliation.md).\n- For more information on running reconciliation in the Software Asset Workspace, see [Run software reconciliation in the workspace](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/software-asset-management/run-recon-workspace.md).\n\n"}}