Record and Run Transaction File in Process Runner DB

This section contains the following topics:

• MM02 - Update Material
• MM01 - Create Material
• VA01 - Header Detail (Multi-Line Transaction)
• FB50 - Create Multi-Line GL Document
• FB01 - Inter Company Code Transaction
• FB60 - Change Company Code
• Transaction Extended

For best practices for Transaction Process files, see the FAQs.

MM02 - Update Material

This topic describes how to create a Transaction Process file and then use the file to update the material master data to SAP.

Scenario:

Let us consider an example of updating material master in SAP using the SAP transaction code MM02. We have a list of materials whose Gross Weight and Net Weight must be updated in the material master records using the SAP transaction code MM02.

We assume that you already know all the materials you want to update gross and net weight values for or download the sample data Excel file ready to be used from MM02 Change Material Excel File.

If the net weight is greater than the gross weight, an error occurs and MM02 transaction does not allow these values to be uploaded.

To record and run MM02 transaction,

1. To record the Process file, perform the following steps:
   1. Select File > New Process > New Transaction or select Transaction (TX) available on the left side of the New Process window.
   2. Enter the transaction code MM02 in the Transaction Code box.

      

   3. Select Start Recording. The Connector for SAP window appears. 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 progress bar to indicate that the recording is in progress.

MM01 - Create Material

This topic describes how to create a Transaction Process file and then use the file to create the material master data to SAP.

Scenario:

Let us consider an example of creating new material master in SAP using the SAP transaction code MM01. MM01 is a standard SAP transaction code available with an R/3 SAP systems depending on the version and release level. Sector, Type and Material Number are required to create a material; you can optionally add other details to the material using the Basic View and save the material data.

We assume that you already know what you want to change and you have all the required data in the Excel file. Alternatively, download the sample data Excel file from MM01 Create Material.xlsx.

To record and run MM01 transaction,

1. To record the Process file, perform the following steps:
   1. Select File > New Process > New Transaction or select Transaction (TX) available on the left side of the New Process window.
   2. Enter the transaction code MM01 in the Transaction Code box.
   3. Select Start Recording. The Connector for SAP window appears. 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 progress bar to indicate that the recording is in progress.
2. In SAP GUI, perform the following steps:
   1. Enter your data in the Create Material (Initial Screen) window.

      

   2. Press Enter. The Select View(s) window is displayed.
   3. Select the Basic Data 1 view and click .

      

   4. Enter the required information when you are in Basic data 1 view (or first view you selected). Select Purchasing view from the pull-down menu on the right side.

      

   5. Enter the Plant value in Organizational Levels window and select Enter.
   6. Enter the appropriate value in Purchasing Group and select Enter. The last screen is displayed.

      

   7. In the Last data screen reached window, select Yes. The changes are saved, the SAP GUI session is ended, and Process Runner DB opens the Process file as [MM01 | *NEW*].
3. Go to the Mapper tab, select Advanced View. A detailed view of the mapper, including the fields that are automatically mapped, is displayed.

   

4. To save the Process file, select File > Save > Save As Local, enter the name for the Process file, and select Save.
5. To run the Process file, select Run. After successful Run you can view the status in Log column of your Excel Data File as shown below.

Optionally, you can verify the records in SAP using the MM03 transaction code.

VA01 - Header Detail (Multi-Line Transaction)

This topic describes how to create a Transaction Process file for Header Detail (multi-line Transaction) transactions. Purchase and sales orders, Bills of Materials, periods in condition records and planning transactions contain multiple lines to be entered. Typically, these lines are maintained in Excel in more than one row. You can use the mapping types that are available in Process Runner DB to eliminate the need to separately identify your DS data; you do not need to modify DS data to mark Header and Details records.

Scenario:

Let us assume that we have three Customer Purchase Orders using the using the SAP transaction code VA01. For each of these, we would create a sales order in our system by entering a list of Material Number and their respective quantity.

We assume that you already know what you want to change and you have all the required data in the Excel file. Alternatively, download the sample data Excel file from VA01 Create Sales Order.xlsx.

To record and run VA01 transaction,

1. To record the Process file, perform the following steps:
   1. Select File > New Process > New Transaction or select Transaction (TX) available on the left side of the New Process window.
   2. Enter the transaction code VA01 in the Transaction Code box.
   3. Select Start Recording. The Connector for SAP window appears. 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 progress bar to indicate that the recording is in progress.
2. In SAP GUI, perform the following steps:
   1. Enter your data in the Order Type, Sales Organization, Distribution Channel and Division fields corresponding to the database file in the Create Sales Order: Initial Screen window, and select Enter. The Create Standard Order: Overview window appears.

      

   2. Enter the additional details for creating a Sales Order, such as Sold to Party, Ship to Party, PO Number and PO Date fields corresponding to the DS data file, and select Enter.

      

   3. Insert the first row of your DS data in the second row of the SAP Sales Order line item window. For loop recording, select a row where you enter the data and select Create a item button. You may have to scroll down if you cannot view the button toolbar for Create a Item.

      

      The data is moved to the first row and the second row is available; you can enter the new record in the second row.

      

   4. Select Save.The changes are saved, the SAP GUI session is ended, and Process Runner opens the Process file as [VA01 | *NEW*].
3. 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 DS columns by entering the map values or using the drag-and-drop functionality. Note that we are usingProcess Runner DBr Start – End Loop Mapping Mechanism to assign the advanced mapping types.
   1. Find the occurrence of Create Item in SAPMV45A – 4001 (4.0 Screen Container for Overview Screens) and select Start Loop from the dropdown list for SAPMV45A – 4001 in the Screen Name column.

      

      A new row with mapping type Start Loop & End Loop is added in the Mapper. On the Block Type for Start Loop, set Block Type to On Value - Ignore Blank' & 'Block Value to A.

      

   2. Select Header+Line Item in the Block Type column for Material Number, Sales Document Item, and Cumulative Order Quantity in Sales Units.
4. To save the Process file, select File > Save > Save As Local, enter the name for the Process file, and select Save.
5. To run the Process file, select Run. After successful Run you can view the status in Log column of your ITABLE as shown below.

   

FB50 - Create Multi-Line GL Document

This topic describes how to create a Transaction Process file to record FB50 transaction and then enter loops to handle multiple line items. Company is defined as the smallest unit for which the financial statements can be created commercially. An SAP system might be configured with or without company code.

Scenario:

We assume that you already know what you want to change and you have all the required data in the Excel file. Alternatively, download the sample data Excel file (with company code) from FB50 Multi Line with company code popup.xlsx. The sample data Excel file (without company code) that is ready to use is available at FB50 Multi Line without company code.xlsx.

To record and run FB50 transaction,

1. To create the Process file, perform the following steps:
   1. Select File > New Process > New Transaction or select Transaction (TX) available on the left side of the New Process window.
   2. Enter the transaction code FB50 in the Transaction Code box.
   3. Select Start Recording. The Connector for SAP window appears. 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 progress bar to indicate that the recording is in progress.
2. In SAP GUI, perform the following steps:
   1. Enter the company code 1000, and select Enter. Note that the Enter Company Code window is displayed only if it is configured in the SAP system. If the company code screen is not displayed, go to the next step.
   2. Enter Document Date, Currency, Posting Date, Reference, and Doc Header Text and select .

      

   3. In the items grid, enter G/L acct, D/C (H-Credit, S-Debit), Amount, Tax Code, Cost Center, and others starting from the second row in the grid corresponding to the database data file.

      Note: For loop recording, select a row where the data must be entered, and then click (Insert Row) to enter the next entry. The data is moved to the first row and the second row is available; you can enter the new record in the second row.

      

   4. Select Status column for the row where the data is entered. The validation check mark is displayed.

      

   5. To push the entered record downwards, select the record that was entered and click (Insert Row).

      

   6. Repeat the steps until the amount is balanced; SAP does not allow you to exit the screen without balancing the amount.

      

   7. Select Save. Not that during recording, a database update in SAP takes place and the SAP GUI session is ended.
3. Process Runner DB automatically maps the fields to Database that were specified in New Process Wizard during recording.
• To update the mapper settings for recording (with Company Code), perform the following steps:
  1. Select Advanced View.
  2. To deactivate the mapped screens that were inserted to balance the recording, which was performed to exit from SAP GUI, select the entire mapped screen for the second item that is not required and select Row(s) Action > Deactivate Row(s) in the Edit group.

     

  3. Exclude the header items, select SAPMF05A - 1001, and then Start Loop from the dropdown list. The End Loop for the line items are set automatically. By default, the Block Type column for Start Loop is set to On Value-Ignore Blank and Block Value to A. Process Runner DB identifies multi-line documents at table in iTable.

     

4. To run the Process file, select Run and perform the following:
   1. Select the SAP system, enter client, user name, password, and language. In case of SNC environment, user name and password are not required.
   2. If required, enter the company code on first call, because transactions such as FB50 might require this information.

      Note: If the Process file is recorded without company code and run using an SAP system that is configured with company code, an error message is displayed. You must allow Process Runner DB to auto-fix the company code error.

5. Optionally, to verify the data in SAP, perform the following steps:
   1. Log in to the same SAP system that you used to record the transaction, enter FB50 and select Enter.
   2. Enter the document number and company code that can retrieved from the status message in the log column, and also enter the fiscal year.

      

   3. Select Enter. The details are displayed.

      

You can also use the Hyperlink feature of Process Runner DB that can redirect to the created document of SAP in just one click for validation.

FB01 - Inter Company Code Transaction

This topic describes how to create a Transaction Process file for inter-company code transactions. Inter company code is used with finance transactions, where single vendor has more then one unit. This document shows how to record FB01 transaction and enter company code to handle multiple line items.

Scenario:

We assume that you already know what you want to change and you have all the required data in the Excel file. Alternatively, download the sample data Excel file from FB01 Post Document.xlsx.

To record and run FB01 transaction,

1. To record the Process file, perform the following steps:
   1. Select File > New Process > New Transaction or select Transaction (TX) available on the left side of the New Process window.
   2. Enter the Transaction code FB01 in the Transaction Code box.
   3. Select Start Recording. The Connector for SAP window appears. 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 progress bar to indicate that the recording is in progress.
2. In SAP GUI, perform the following steps:
   1. Enter Document Date, Type, Company code, and Currency/Rate.
   2. Select Fast Data Entry.

      

   3. Select Display Document Overview.

      

   4. Enter Posting key and Account number. Select Enter.

      

   5. Enter Amount and Tax Code. Select Enter.

      

   6. Enter the Business Area and Cost Center. Select Enter.

      

   7. Repeat the steps to enter details about another line item. Select Enter.

      

   8. Select Save. When the recording is completed in SAP, Process Runner DB opens the Process file as [FB01 | *NEW*].
3. To map the fields to SAP Fields, select the screens that are not required, which were used to balance the recording and select Deactivate Selected Row(s). Delete all the screens that were used to balance the recording; update the loops if required.

   

4. Select Advanced from the Settings section on the Home tab. The Advanced Settings window is displayed. Select the following options:
   • FI Company Code Settings > Automatically handle inter-company scenario
   • F1 Posting Key/Screen > Simplified Posting Keys to Screen mapping

     

5. To run the Process file, select Run.

FB60 - Change Company Code

This topic explains describes how to record FB60 transaction to post the documents with multi-company code values. Change company code is used with finance transactions, where a single vender has more then one unit.

Scenario:

We assume that you already know what you want to change and you have all the required data in Excel file. Alternatively, download the sample data Excel file that is ready to use from FB60 Change Company Code.xlsx.

To record and run FB60 transaction,

1. To record the Process file, perform the following steps:
   1. Select File > New Process > New Transaction or select Transaction (TX) available on the left side of the New Process window.
   2. Enter the Transaction code FB60 in the Transaction Code box.
   3. Select Start Recording. The Connector for SAP window appears. 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 progress bar to indicate that the recording is in progress.

Transaction Extended

This topic describes how to use the same transaction to read and write values simultaneously.

To create a transaction to work for both read-only and read/write modes,

1. Record a new transaction for MM02.
2. On the Mapper tab, right-click MARA-GREW(Gross Weight) and select Clone.

   

3. Map the newly copied row to SAP To DS and Field 4 to retrieve the Gross Weight value before update from Field 3; the value in this column is what we get before updates to that field.
4. Repeat the steps for Net weight.

   

5. Go to Home. An extra option on the Control Parameter tab is automatically suggested by Process Runner DB. Select the following options:
   • To read the SAP To DS fields, clear Stop transaction on Commit and run in BI mode.
   • To perform normal MM02 write function, select Suppress All "Copy from SAP To DS" mappings.

     

6. Run the Process file. Notice the below output which shows gross weight and net weight before change in FIELD4 and FIELD5. It also updated Gross weight and Net weight from FIELD2 and FIELD3.