Record and Run Transaction File

This section contains the following topics:

• MM02 - Update Material
• MM01 - Create Material
• Extend Material Master
• VA01 - Header Detail (Multi-Line Transaction)
• FB50 - Create Multi-Line GL Document
• FB01 - Inter Company Code Transaction
• FB60 - Change Company Code
• ME51N - Create Purchase Requisition with ENJOY transaction
• MM01 - Record Tax Classification
• MM02 - Record Updates for Various Views
• CS02 - Record BOM Item Changes
• 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.

For information about how to automate the mapping process, see Implement Dynamic Field Mapping from Excel 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 and the file is at C:\Process Runner Data Files\Material Master Weight update list.xls 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. The New Process window appears.
   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. The New Process window appears.
   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 opens the Process file as [MM01 | *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 Excel columns by entering the map values or using the drag-and-drop functionality. Optionally, clear the fields that you do not require.

      

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 and perform the following:
   1. Select the SAP system, enter client, user name, password, and language.
   2. Select OK. Process Runner runs the recorded Transaction and maps the data according to the mapper settings. Process Runner builds a data package by merging recorded transaction with mapped Excel and other values and send this package to SAP transaction for processing. When SAP completes running the transaction, Process Runner retrieves the transaction status and messages from SAP and places them in the next available empty columns in the Excel file as shown in the following screenshot.

      

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

Extend Material Master

This topic describes how after creating a material master in SAP using the default Basic Data 1 view, you can extend the same material master for other views.

To extend material master,

1. In SAP GUI, enter MM01 transaction code and select Enter or click . The Create Material (Initial Screen) window is displayed.
2. Enter the material number, select Industry Sector and Material Type, and select Enter or click . The Select View(s) window is displayed.
3. Select the views for which you want to extend the material master and select Enter or click .
4. Do not use scroll bar to scroll down if you do not see the required view in the existing list, instead, select page down button and then select the views. Process Runner does not record the scrolling action.
5. Select the dropdown and select those views again if more than one view is selected for extending the material.

   

6. Save the recording.
7. In Process Runner, select Run. The file is run and when SAP completes running the transaction, Process Runner retrieves the transaction status and messages from SAP and places them in the next available empty columns in the Excel file.

Optionally, you can verify the records in SAP.

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 to eliminate the need to separately identify your Excel data; you do not need to modify Excel 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. The New Process window appears.
   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 Excel data 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 Excel data file, and select Enter.

      

   3. Insert the first row of your Excel 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 Excel columns by entering the map values or using the drag-and-drop functionality. Note that we are using Process Runner 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 and perform the following:
   1. Select the SAP system, enter client, user name, password, and language.
   2. Select OK. Process Runner runs the recorded Transaction and maps the data according to the mapper settings. Process Runner builds a data package by merging recorded transaction with mapped Excel and other values and send this package to SAP transaction for processing. When SAP completes running the transaction, Process Runner retrieves the transaction status and messages from SAP and places them in the next available empty columns in the Excel file as shown in the following screenshot.

   

6. Optionally, to verify the data in SAP using VA03 transaction code, perform the following steps:
   1. Log in to the same SAP system that you used to record the transaction, enter VA03 and select Enter.
   2. Enter the sales order number created with Process Runner and select Search.

      

      The details are displayed.

      

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. The New Process window appears.
   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 Excel 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. To map Excel Columns and cells to SAP fields, perform the following steps:
   1. To update the mapper settings for recording (with Company Code), perform the following steps:
      1. Select Advanced View and remove the dynamic skip A-Execute only on the first call from the first screen SAPLACHD - 1000 (Company Code pop-up).

         

      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 section.

         

      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 identifies multi-line documents at A column in the Excel file.

         

   2. To update the mapper settings for recording (without 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 identifies multi-line documents at A column in the Excel file.

         

   3. Select Home > Generate Template from the Generate Template dropdown options.

      

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 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 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. The New Process window appears.
   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 opens the Process file as [FB01 | *NEW*].
3. To map the Excel columns and cells 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 and perform the following:
   1. Select the SAP system, enter client, user name, password, and language.
   2. Select OK. Process Runner runs the recorded Transaction and the transaction status are displayed in the log column of the Excel file.

      

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. The New Process window appears.
   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.

ME51N - Create Purchase Requisition with ENJOY transaction

This topic describes how to create a Transaction Process file for ME51N transaction. ME51N is used to create a Purchase Requisition and has superseded transaction ME51. ME51N is an ENJOY transaction. and information must be entered in a single screen; the ME51 transaction is split across several screens. This transaction requires the entry of a material or account assignment category.

ME52N is used to modify or maintain purchase requisitions and ME53N is used to view purchase requisitions created.

Scenario:

We assume that you already know what you want to change and you have all the required data in the Excel file.

To record and run ME51N 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. The New Process window appears.
   2. Enter the Transaction code ME51N 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 the SAP GUI, perform the following:
   1. In the Create Purchase Requisition window, select NB Purch.requis.Stand. option from the dropdown list.

      

   2. To close the Header window, select CTRL + F5, CTRL +F6 to close Item Overview window, and CTRL +F7 to close Item Detail window.
   3. To open the Header window, select CTL +F2, CTL + F3 to open Item Overview window and CTL + F4 to open Item Detail window.
   4. Select Personal Setting, clear Item overview as grid control, and select Save.

      

   5. Insert the first row of your Excel data in the second row of Item Overview section and enter the Requisition Item, Material, Quantity and Plant details according to the data in the Excel workbook, and select Enter.

      

   6. Select Configure Filter and define the filter criteria.

      

   7. Enter the value for Item of Requisition that is used as the filter criteria.

      

   8. Select Save. The changes are saved, the SAP GUI session is ended, and Process Runner opens the Process file as [MM51 | *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. Select Advanced View in Mapper. To update the mappings using the Start – End Loop Mapping mechanism, perform the following steps:
      1. Find the occurrence of Create Item in SAPLMEGUI – 0014 (View: Purchase Order Window)
      2. Set the Start Loop. A new row with mapping type Start Loop & End Loop is added in the Mapper.
      3. On the Block Type for Start Loop and set Block Type to On Value - Ignore Blank and Block Value to A.

         

      4. Set Block Type to Header+Line Item Value for Material Number, Item Number, Plant & Purchase Requisition Quantity.
4. Save the Process file and select Run.

   

Note: ME51N transaction code does not return a confirmation message of the Purchase Requisition creation while running the records in Batch or Non-Batch input mode. Refer the SAP OSS Note No: 217437 for this known issue. Therefore, we recommend that you use BAPI_PR_CREATE, which is equivalent to ME51N.

MM01 - Record Tax Classification

This topic describes how to record tax classification using MM01. When recording MM01 transaction in Process Runner that involves Tax classification, the screen progression of transaction recording looks different than that of normal SAP GUI.

Note: You can refer to the ready-to-run cloud sample 357 Cloud ID: MM01-Sales Master file.

To record the MM01 transaction for Tax Classification,

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. The New Process window appears.
   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 the required details in the Create Material (Initial Screen) window, select the view as Basic Data 1 and select Enter. Note that you must not select view(s) that you want to go to; select the first view and select Enter.

      

   2. Enter the basic data in Basic data 1, and select Sales:sales org1 from the pull-down menu on the right side.

      

   3. Enter the data in Organizational Levels and select Enter.

      

   4. On the Sales:sales org.1 tab, enter the required Tax Classification data as follows.
      1. Enter the tax classification data in the two fields and select Enter.

         

      2. If the tax classification data has more than two fields, then user can enter the data in rest of the fields at this phase. Enter the data in the fields and select Main Data.

         

      3. The user is redirected to Sales:sales org.1 where all the added fields (in step b) are listed in tax data. Click to add other views in the recording and select the save icon. The changes are saved, the SAP GUI session is ended, and Process Runner opens the Process file as [MM01 | *NEW*].

         

3. To save the Process file, select File > Save > Save As Local, enter the name for the Process file, and select Save.

MM02 - Record Updates for Various Views

This topic describes how, sometimes, due to the SAP behavior, it becomes difficult to use the same recording for different material types. You might have to record updates for various views in MM02. The view selection changes as per the configuration of the material type. For example, Purchasing view may not be in the same position for different materials. If you have recorded by selecting purchasing view based on material 100-100, it would not work for material 1500-520 because purchasing view is in the fourth position while in the original recording it was in the ninth position.

You must record the transaction as explained in the following steps:

1. Record by selecting Basic Data 1 or Basic Data 2 or the first view that you see. Do not select the view you want to go to yet.

   

2. In the Basic Data 1 view or the first view that you selected, select Purchasing from the dropdown list.

   

3. Make the required changes and complete the recording.
4. For multiple views, for example Accounting 1 and 2, after making the changes in one view, go to another view using this method and complete the recording.

In the New Process window, Process Runner provides a tip about recording in different views.

For further assistance, please create a support case on Salesforce.

CS02 - Record BOM Item Changes

This topic describes how to use the SAP transaction CS02 (Change Material BOM) for BOM management to change the BOM items of materials that are already created. Use Function field for selecting the item numbers to record the BOM item changes correctly (Add, Edit and Delete) in a CS02 transaction while recording to ensure that no existing components are overwritten.

To record BOM item changes,

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 CS02 in the Transaction Code box and select Start Recording.

      

   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 Material, Plant, and BOM Usage information in the Change material BOM: Initial Screen window and select Enter.

      

      We recommend that you use Function field displayed in the lower-left of the window. This ensures that the Process file being recorded works for Add, Edit, and Delete BOM items. If Position field is used while recording, it is possible that this may not work for addition of BOM items using the same Process file. Therefore, we recommend that you do not use Position field.

   2. Enter the values in the Change material BOM: Material Item Overview window according to your requirements and complete the recording.

      

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. You can refer the tutorial section of Process Runner for recording a new transaction.
2. On the Mapper tab, right-click MARA-GREW (Gross Weight) and select Clone.

   

3. Map the newly copied row to SAP To Excel and column D to retrieve the Gross Weight value before update from column B; 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. Select the following options:
   • To read the SAP To Excel fields, clear Stop transaction on Commit and run in BI mode.
   • To perform normal MM02 write function, select Suppress All "Copy from SAP To Excel" mappings.

     

6. Run the Process file. The Excel file shows gross weight and net weight before change in column D and E. It also updated gross weight and net weight from column B and C. The same transaction works for both the modes: read-only and read/write.