Skip to main content

Record and Run Data Extractor File

This section contains the following topics:

Extract Data from MARA

This topic describes how to extract data from MARA. Data Extractor is the process of extracting data from SAP table to Excel. You can filter data before extraction using the Data Filter feature. For information about how to extract data using the data filter feature, see Data Filter.

To record and run Data Extractor Process file for MARA,

  1. The steps to create, map, and run a Data Extractor Process file are as follows.
    1. Select File > New Process > New Data Extractor or Data Extractor available on the left side of the New Process window. The New Process window appears.
    2. In the Table/View Name box, enter the SAP table or view name. For this example, enter MARA.
    3. Optionally, select More and clear Automap all fields. You can select the required fields manually.
    4. If you do not know table name or if you want to find out table joins, select DD Explorer. The SAP Data Dictionary Explorer window is displayed with a list of all the tables and views as found in standard ECC6 system.

    5. Select OK. The SAP Data Dictionary Explorer window is closed.
    6. Select OK. Process Runner displays a progress bar to indicate that the recording is in progress. Process Runner opens the Process file as [MARA| *NEW*] with the Mapper tab opened.

  2. To map the Excel columns and cells to SAP Fields, perform the following steps:

    1. Go to the Mapper tab, select Advanced View. A detailed view of the mapper, including the fields that are automatically mapped, is displayed.
    2. Update the mappings; map the fields to the Excel columns by entering the map values or using the drag-and-drop functionality. Optionally, clear the fields that you do not require.

  3. T o save the Process file, select File > Save > Save As Local, enter the name for the Process file, and select Save.
  4. To run the Process file, select Run and perform the following:
    1. Select the SAP system, enter client, user name, password, and language.
    2. Select OK. The data is downloaded from the SAP system to the Excel file.

Create Pseudo Table Join Between Two SAP Tables

This topic describes how to create a dynamic table join from two SAP tables in Process Runner using the Process Connection and data filter builder functionality.

Scenario:

Let us consider an example of table join between two SAP Tables, MARA and MAKT and the requirement is to extract the data from the following columns, and also other information:

  • Material Number
  • Material Description

Columns A to G contains data from MARA (header) table, such as Material Number, Created On, Material Type, Material Group, Gross Weight, Net Weight, and Base Unit of Measure.

Column H contains data from MAKT (Material Description) table. But, we extract data only related to MARA and a pseudo join is created between MARA and MAKT.

This is not a SQL-type join; you must first extract data from the first or parent SAP table, and then extract data from the second or child table filtering from the parent SAP table data and use the data from parent table as the filtering condition. In this case, we are using Material Number that is extracted from MARA table as a filter for extracting data from MAKT table.

Concept:

  1. Create the two Process files individually and add the filter to provide the source value as Excel columns from the first Process file for the second Process file. This creates a pseudo table join.
  2. Connect the two Process files by Process Connection feature.
  3. Run the connected Process file.

To create pseudo table join from two SAP tables

  1. Open Process Runner and select New Process. The New Process window is displayed.
  2. Select Data Extractor module and in the Table/View Name box, enter MARA.
  3. Select More and clear Automap all fields. You can select the required fields manually.

  4. Select OK. The Connector for SAP window is displayed. Perform the following steps:
    1. Select the SAP system, select Logon, and enter the information for Client, User, Password, and Language.
    2. Select OK. Process Runner displays a message to indicate that the tables are validated and that you must update the required mappings.
  5. Go to the Mapper tab, select the required fields from the tables, and map the fields to the Excel columns by entering the map values or using the drag-and-drop functionality.

  6. Save the Process file and select Run.
  7. To create a Process file using the MATK table, repeat the steps 2-6.

  8. On the Mapper tab, select the required fields from this table and map those fields to the Excel columns.
  9. Perform the following steps:
    1. To create a pseudo join, enter the filter to get the description of material extracted from the first Process file; optionally, enter the second filter to ensure that you extract only the description in English language.

    2. Save the Process file and select Run.
  10. Select Save > Run.
  11. Connect the individual Process files as follows:
    1. Open the MARA Process file, select Process Connection, and browse to find the MAKT Process file.
    2. Ensure that the status and log columns from your first Process file is not overwritten by the data extraction of the second Process file. Also, update the End Row value to get the complete extraction from the second table.

  12. Save the connected Process file and select Run. The Excel file is displayed with the data from the two tables, MARA and MAKT.

If you are extracting a table join between Header Level table and Detail / Line Item level table, there is a possibility of one-to-many relationship that could cause mismatch in lines.

In this case, we suggest you extract the Detail / Line item level table first and then extract the Header level using filters.

For information about how to extract data from three tables using Process Connection functionality, see Create Pseudo Table Join Between Three SAP Tables.

Create Pseudo Table Join Between Three SAP Tables

This topic describes how to create a dynamic table join from three SAP tables in Process Runner using the Process Connection and data filter builder functionality.

Scenario:

Let us consider an example of table join between three SAP Tables, LTAP, LTAK and LTBK and the requirement is to extract the data from the following columns, and also other information:

  • Warehouse Number/ Warehouse Complex from LTAP
  • Transfer Order Number from LTAK
  • Transfer Requirement Number from LTBP

Columns A and B contains data from LTAP (header) table, such as Warehouse Number/Warehouse Complex and Transfer Order Number. Columns C, D and E contains data from LTAK table. Columns F and G contains data from LTBK table. But, we extract data only related LTAP and a pseudo join is created between LTAP, LTAK, and LTBK tables.

This is not a SQL-type join. You must first extract data from the first or parent SAP table, and then extract data from the second or child table filtering from the parent SAP table data and use the data from parent table as the filtering condition. In this case, we are using Warehouse Number/Warehouse Complex and Transfer Order Number, which is extracted from LTAP, as a filter for extracting data from LTAK and Warehouse Number/Warehouse Complex and Transfer Requirement Number, which is extracted from LTAK, as a filter for extracting data from LTBK.

Concept:

  1. Create the three Process files individually and add the filter to provide the source value as Excel columns from the first Process file for the second Process file, and from the second Process file for the third Process file. This creates a pseudo table join.
  2. Connect the three Process files by Process Connection feature.
  3. Run the connected Process file.

To create pseudo table join from three SAP tables

  1. Open Process Runner and select New Process. The New Process window is displayed.
  2. Select Data Extractor module and in the Table/View Name box, enter LTAP.
  3. Select More and clear Automap all fields. You can select the required fields manually.

  4. Select OK. The Connector for SAP window is displayed. Perform the following steps:
    1. Select the SAP system, select Logon, and enter the information for Client, User, Password, and Language.
    2. Select OK. Process Runner displays a message to indicate that the tables are validated and that you must update the required mappings.
  5. Go to the Mapper tab, select the required fields from the table, and map the fields to the Excel columns by entering the map values or using the drag-and-drop functionality.

  6. Save the Process file and select Run.
  7. To create a Process file using the LTAK table, repeat the steps 2-6.

  8. Perform the following steps:
    1. To create a pseudo join, enter the filter to get Warehouse Number/Warehouse Complex and Transfer Order Number extracted from the first Process file.

    2. Save the Process file and select Run.
  9. To create a Process file using the LTBK table, repeat the steps 2-6.

  10. Perform the following steps:
    1. To create a pseudo join, enter the filter to get Warehouse Number/Warehouse Complex and Transfer Order Number extracted from the second Process file that was created based on LTAK, in columns C and E.

    2. Save the Process file and select Run.
  11. Connect the individual Process files as follows:
    1. Open the LTAP Process file, select Process Connection, and browse to find the LTAK Process file.

    2. Open the LTAK Process file, select Process Connection, and browse to find the LTBK Process file.

      3. The following screenshot illustrates the three connected Process files.

    3. Ensure that status and log columns from your first Process file is not overwritten by the data extraction of the second and third Process files. Also, update the End Row value to get the complete extraction from the second and third tables.

      For example, the following screenshot illustrates how to update the End Row for the first Process file.

      The following screenshot illustrates how to update the End Row for the second Process file.

      The following screenshot illustrates how to update the End Row for the third Process file.

  12. Save the connected Process file and select Run. The Excel file is displayed with the data from the three tables, LTAP, LTAK and LTBK.

For information about how to extract data from three tables using the dynamic table join condition functionality, see Extract Data From Three SAP Tables Using Dynamic Table Join Feature.

For information about how to extract data from two tables using Process Connection functionality, see Create Pseudo Table Join Between Two SAP Tables .

Extract Data From Three SAP Tables Using Dynamic Table Join Feature

This topic describes how to create a table join from more than one SAP table in Process Runner using the dynamic table join condition functionality.

The Data Extractor (DE) module of Process Runner extracts data from tables or views using standard remote function module (RFM) that is provided by SAP. Process Runner also provides a custom data extraction remote function module for other business requirements and optimization. To create a join between tables for custom data extraction, configure the Data Extractor settings in the Tools > Options > Data Extractor tab and select Use Extended RFM. For more information, see Data Extractor.

Scenario:

Let us consider an example of table join between three SAP Tables, LTAP, LTAK and LTBK and the requirement is to extract the data from the following columns, and also other information:

  • Warehouse Number/ Warehouse Complex from LTAP
  • Transfer Order Number from LTAK
  • Transfer Requirement Number from LTBP

    • hmfile_hash_be11f525

To extract data from three data tables using join condition:

  1. Open Process Runner and select New Process. The New Process window is displayed.
  2. Select Data Extractor module and in the Table/View Name box, enter LTAP, LTAK and LTBK separated by commas.
  3. Select More and clear Automap all fields. You can select the required fields manually.

  4. Select OK. The Connector for SAP window is displayed. Perform the following steps:
    1. Select the SAP system, select Logon, and enter the information for Client, User, Password, and Language.
    2. Select OK. Process Runner displays a message to indicate that the tables are validated and that you must update the required mappings.
  5. Go to the Mapper tab, select the required fields from the three tables, and map the fields to the Excel columns by entering the map values or using the drag-and-drop functionality.

  6. Select Join Condition from the Edit section. The JoinCondtion(<NameOfTables>) window is displayed with the default table join condition on the Join Condition tab and the table names that are included in the join condition on the Tables tab. In this case, the default join condition joins the primary keys of the three tables; the Transfer Requirement Number (TBNUM) from the LTAK table is not a primary key and is not included in the default join condition.
    LTAP INNER JOIN LTAK ON ( LTAP~LGNUM = LTAK~LGNUM AND LTAP~TANUM = LTAK~TANUM )
    INNER JOIN LTBK ON ( LTAP~LGNUM = LTBK~LGNUM )
  7. To edit the default condition, perform the following steps:
    1. Add the Transfer Requirement Number (TBNUM) to the inner join with the LTBK table tab.
      LTAP INNER JOIN LTAK ON ( LTAP~LGNUM = LTAK~LGNUM AND LTAP~TANUM = LTAK~TANUM )
      INNER JOIN LTBK ON ( LTAP~LGNUM = LTBK~LGNUM AND LTAK~TBNUM = LTBK~TBNUM )

      HT-PTJTETSAP (20)

    2. To check the join condition for any errors, select Syntax Check.
    3. To display a warning message about the join condition, select Always Display Join Condition Run warning message.
    4. Optionally, to reset the join condition, select Default.
    5. Select OK. The changes to the join condition are saved.
  8. Save the Process file and select Run. The Excel file is displayed with the data extracted from the three tables.

    HT-PTJTETSAP (20)

For information about how to extract data from three tables using Process Connection functionality, see Create Pseudo Table Join Between Three SAP Tables.

Was this article helpful?

We're sorry to hear that.