ME31K_ Create a contract, Studio v11 - Automate_Studio - Latest

Automate Studio with Evolve User Guide

Product type
Product family
Automate > Automate Studio
Product name
Automate Studio
Automate Studio with Evolve User Guide
Topic type
How Do I
First publish date

ME31K step by step: Creating a contract

This document describes how you can use Automate Transaction to create a contract in the SAP Business Suite from data in Microsoft Excel using the SAP transaction ME31K.



  1. Start Automate Studio from the desktop shortcut or from the Windows Start menu.
  2. Click New.

    file tab new

  3. Click Transaction, and then click Create from SAP recording.

    create from sap recording

  4. Choose the SAP system that you want to use, enter the appropriate user data, and then click Log On to SAP.

    s a p logon

    If you do not see the SAP system that you want, click Advanced SAP Logon, click Add System, provide the system information, and click OK.

  5. In the Transaction code box, type ME31K.

    transaction code box

  6. Leave the recording mode as Standard. If you do not see Standard, click Change and then click Batch Input Mode.

    Note: For most transactions, the default mode is Standard, and the Automate Function Module (WFM) selects the optimum mode for the t-code that is being recorded. If the WFM is not installed, Batch Mode will work for ME31K, and Non-Batch Input Mode Without Controls will work for most transactions. Non-Batch modes are necessary for downloading information from SAP transactions, or for Finance or HR transactions in which there are Dynamic Actions executing or user parameter values being used; otherwise, if you do not have access to Non-Batch modes, you can try recording in Batch Mode. The difference between Without SAP Controls and With SAP Controls is just a matter of what tools are on the transaction screens. For more information, see the Recording modes topic (Connect mode or Foundation mode).

  7. Click Start Recording

    start recording button

    The ME31K transaction starts.

    Note: The screens might appear slightly different in the recording mode because we are using a background mode. The screens might also vary according to the way that your SAP system has been configured.

  8. On the first screen, enter the following data:
    • Vendor
    • Agreement Type
    • Agreement Date
    • Purch. Org
    • Purchasing Group
    • Plant
    • Storage Location

    create contract initial screen

  9. Press Enter.
  10. Enter additional header details. In this example:
    • Validity End
    • Payt Terms
    • Targ. Val.

    create contract header data

  11. Press Enter to continue.

    Important: The next step might be different from the manual entry process.

  12. On the second row, enter the details for the first line item, including item number 10:
    • Item
    • Material Number
    • Quantity
    • Net Price

    enter line item on second row

  13. Click the Enter Lines button to create items.

    enter lines button

    This will move the first line item to row 1, so that row 2 is available again for data entry.

  14. Enter the details for the second row of line-item data, including item number 20.

    second line item on row 2

  15. Click the Enter Lines button again.
  16. Click Save to save the Contract. This also ends the recording.

    save button

After Studio finishes compiling the script, it will take you to the Map tab.


It is now time to create the mapping for this transaction. Mapping a script is just a matter of connecting SAP fields to fields in your data file. Transaction provides a Mapper to facilitate this process.

Auto Mapping will map the entire script to an Excel spreadsheet in the order that they appear in the Mapper. Because of the complexity of this transaction, we will map the fields manually instead.

The screenshot below shows the Basic View tab of the Mapper.

In each row of the Mapper, you will see:

  • Mapper row number: This is just a reference number.
  • Enable flag: only enabled Mapper rows will be executed by Transaction.
  • Field Description: The label associated with the SAP technical field name.
  • Field Name: The SAP technical field name.
  • Field Type & Length: For example, String or Decimal, and the padding options.
  • Mapping direction: Fixed Value, Excel to SAP, SAP to Excel (or, if mapping to Access: Access to SAP, SAP to Access).
  • Value: Values assigned to the SAP field; either fixed values or mapped locations in the associated data source.

Note: The Properties pane is also displayed, but it is not shown below.

basic tab in mapper

In the Data Set panel, you will see a preview screen of the selected data source type.

To change the data source type, click the drop-down menu under the Data Set tab and choose the data source type that you want.

change data source type drop down menu

The preview will change to reflect the choice. In this case, we will use Excel.

The first step is to add the loop.

A loop takes a section of the script and allows that section to repeat. In the case of a contract, the section where you enter line items needs to be repeatable. That way, whether you enter 1 line item or 100 into your Excel file, the script can upload all of the line items, using a single line item of scripting.

  1. Click the Expert View tab.

    Expert View displays the fields organized by screens, and you can see the screen name, number, and description.

    expert view

  2. Select the screen and fields for the second line item, right-click, and then click Disable to hide the screens and fields for the second line item.

    disable fields for second line item

  3. Select the Mapper rows for the remaining line item. In this example, select Mapper row 19, hold down the Shift key, and click row 25.