Collecting Data from Dependent SAP Systems

FlexNet Manager Suite 2022 R1 (On-Premises)

You can launch the data collection from the dependent SAP systems manually or by scheduling a job.

It is recommended that you schedule the Staging Database Monitor to run the data collection job a day before the SAP Inventory Agent reads the data from the SAP Admin module and loads it into the FlexNet Manager Suite database. For information on scheduling a background job, see Scheduling a Collection Job for the Staging Database Monitor. For information on data collection through the SAP Inventory Agent, see SAP Inventory Agent.

To specify the data that should be collected from dependent SAP systems:

  1. Open the SAP Admin module.
  2. In the system landscape, click Administration and then Staging Database Monitor.
    The Staging Database Monitor interface displays, allowing you to specify the data collection criteria.
  3. In the Systems section, select the dependent systems from which the data should be collected.
  4. Optionally select the Launch USMM remotely check box to start the USMM remotely on the dependent SAP systems that are specified in the Systems field above.
    Launching the USMM ensures that current package-measurement and activity-checks data are available in the dependent SAP systems; this data can then be collected by the Staging Database Monitor.

    The USMM is only used on dependent SAP systems to start the system measurement. No data is sent to SAP.

    For information on best practices when using the USMM, see Best Practice when Using USMM.

    Important: The Launch USMM remotely check box must be selected if you want to collect package data and activity checks data from system measurement results in dependent SAP systems.

    If you do not want to use the USMM to generate the data, use the Packages and Activity Checks features (both available from the Main menu of the SAP Admin module). Data collected by the Packages and Activity Checks features is added to the staging database.

    Note: This functionality cannot be launched remotely in FlexNet Manager Suite 2019 R1 or any earlier versions, if the remote system is based on the same or higher than these supported package versions:

    SAP_BASIS:

    • 7.02 (SP21)
    • 7.31 (SP23)
    • 7.40 (SP20)
    • 7.50 (SP11)
    • 7.51 (SP06)
    • 7.52 (SP02).
    As a workaround, you can use the Activity Checks and Package Measurement features after finishing your data collection in the Staging Database Monitor. Please refer to Activity Checks and SAP Package Measurement in the FlexNet Manager for SAP Applications User Guide PDF for more details.
  5. The Data to collect section lists all the data types you can collect. All data types are selected by default, so clear the check box for any data type you don't want to collect:
    1. User Details — Select this check box to collect user details from the dependent SAP systems. User details include user name, first and last name, license type, last logon date, user group, user type, email address, phone number, accounting number, validity dates, and cost center.
    2. System Users (Type B) — Select this check box to collect data for System users, along with data for other user types. Clear this check box to exclude the System user type from data collection.
      There are five different SAP user types, which are:
      • Dialog (A)
      • System (B)
      • Communications Data (C)
      • Reference (L)
      • Service (S).
    3. Role Data — Select this check box to collect role data from the dependent SAP systems.
    4. Objects — Select this check box to collect object data (name and type of consumed objects) from the dependent SAP systems. Object types are Report, Job, or Transaction.
    5. License Data — Select this check box to collect license data from the dependent SAP systems.
    6. Packages — Select this check box to collect package measurement data from the dependent SAP systems.
      If current package measurement data is not available, then we recommended that you clear this check box. Package measurement data can be generated by executing the USMM (using the Launch USMM remotely check box) or using the Packages feature (available from the Main menu of the SAP Admin module.
    7. Activity Checks — Choose whether you want to use Activity Checks by selecting one of the following options:
      • If current activity-checks data is not available, then we recommended that you clear this check box. Activity checks data can be generated by executing the USMM (using the Launch USMM remotely check box) or using the Activity Checks feature (available from the Main menu of the SAP Admin module).
      • Select this check box to collect data for activity checks from the dependent SAP systems. This applies the default parameters used by the USMM for activity checks. This option checks the activity of all end-users to ensure that sufficient pauses in activity are recorded in two subsequent days. The default break duration is 28,800 seconds (8 hours). Please refer to Activity Checks in the FlexNet Manager for SAP Applications User Guide PDF for more details.
        Important: The Satellite transport must be installed on the dependent system for activity checks data collection.
        Note: If you want to collect activity check data from a dependent system that runs SAP Basis release 4.6C, 6.2, or 6.4, you must start the data collection using the Activity Checks menu in the SAP Admin module. For systems running SAP Basis release 4.6C, 6.2, or 6.4, the Staging Database Monitor always returns a red status, even if the data collection using the Activity Checks menu was successful.
    1. Consumption Data — Select this check box to collect consumption data from the dependent SAP systems.
      By default, three months of consumption data will be collected. Use the following fields to refine the data collection period:
      1. Consumption end date — Enter the end date for the period of consumption data collection in the format dd/mm/yyyy or leave blank to use the current date.
      2. No. months of consumption —Enter the number of months that you want consumption data to be collected for. The default value is 3. Although you can technically enter any number of months, most SAP systems will typically only support three months of consumption data.
    2. Module Data — Select this check box if data on used SAP modules should be collected from the dependent SAP systems.
    3. RFC Data — Select this check box to collect RFC data from the dependent SAP systems.
      By default, three months of data will be collected. Use the following fields to refine the data collection period:
      1. RFC Data end date —Enter the end date for the period of RFC data collection in the format dd/mm/yyyy or leave blank to use the current date.
      2. No. months of RFC Data — Enter the number of months to indicate for how long RFC data should be collected. The default value is 3.
    4. Digital Access Data — Select this check box if digital access data should be collected from the dependent SAP systems.
      By default, three months of data will be collected. Use the following fields to refine the data collection period Use the following radio button to set a different time period:
      • No. months of Digital Access — Select to collect digital access data for a specific number of months and then enter the number of months. The default value is 3.
      • Last Full Calendar Year (monthly) — Select to collect digital access data that was generated in last full calendar year. The data will be monthly aggregated.
      • Start Date and End Date — Select to collect digital access data generated for a specific date rage and then enter then start and end date in the format dd/mm/yyyy. Leave the End Date blank to use the current date.
  6. In the Options section, select the way you want to collect data:
    1. Choose the run method for collection from these options:
      • Run Online — This is the default selection. Use this option if the functions that are called to facilitate the data collection should be executed online. It is recommended to select this option for the initial data collection, to ensure that data is successfully collected. If the data collection is working as expected, subsequent data collection can be run as a background task.
      • Run with "IN BACKGROUND TASK" — Select this option if the functions that are called to facilitate the data collection should be run as a background task. It is recommended to select this option only after you ran an initial data collection using the Run Online option, to ensure that the data collection runs as expected.
    2. Use BAPI_USER_GET_DETAIL — Choose the fastest way to collect the address, email address, and telephone number of users from these options:
      • Leave this check box selected to enable FlexNet Manager Suite to call this routine to gather the user data.
        Tip: Best practice is to test both options to determine the fastest method of data collection for your enterprise.
        • Calling BAPI_USER_GET_DETAIL for each user may be slow when there is a large number of users in this dependent SAP system, and the network communication between the Admin Module system and this dependent SAP system is less than ideal.
        • Calling BAPI_USER_GET_DETAIL may be the most efficient option if there is a large amount data in table ADR6 of this dependent SAP system, when it may reduce the memory usage and improve performance.
      • Clear this check box to enable FlexNet Manager Suite to gather the user data from table USR21, ADR6 and V_ADDR_USR through RFC_READ_TABLE.
  7. Click Execute or press F8 to launch the data collection.
You can verify the status of the data collection on the Staging Database Monitor - Data collection status screen. After the data collection has completed, the SAP Inventory Agent can connect to the staging database and collect the data. The data is then loaded into FlexNet Manager Suite via RFC connection.

>FlexNet Manager Suite (On-Premises)

2022 R1