This OP explains how to create a service contract. |
Who uses this document? | What is the nature of the need | ||||
|---|---|---|---|---|---|
User / PREQ creator | Approver | PSR | PS | Goods | Services |
X | X | ||||
End product ![]()
Before starting the contract creation, the vendor must be created for the concerned P.Org.
# | Main activities | Tips / Best practices | Key points |
1 | Enter transaction MK03 |

# | Main activities | Tips / Best practices | Key points |
2 | Flag the "Address" Field | This will allow to see if the vendor is created without going into further selections. | |
3 | Click in selections screen |

# | Main activities | Tips / Best practices | Key points |
4 | Chose the selection most suitable according to the data available on the contract |

# | Main activities | Tips / Best practices | Key points |
5 | Insert the data you have and click |

# | Main activities | Tips / Best practices | Key points |
6 | If there is only 1 entry, click | If there are doubts concerning the vendor, clarification must be requested with the buyer (requestor of contract creation) | If data is the same, the vendor is created in SAP. |

# | Main activities | Tips / Best practices | Key points |
7 | If there are several vendors with the data inserted, each must be entered in MK03 (step 2 onwards) and compare the details in each to see to which vendor number the contract concerns. | If there are doubts between several vendor, clarification must be requested with the buyer (requestor of contract creation) |

# | Main activities | Tips / Best practices | Key points |
9 | Enter transaction MKVZ. | This transaction allows to see for which P.Orgs the vendor is created for. |

# | Main activities | Tips / Best practices | Key points |
10 | Insert the vendor number found in Step 6. | ||
11 | Click |

# | Main activities | Tips / Best practices | Key points |
12 | In Column | If the vendor has the P.Org listed (and no X in columns in steps 13 and 14), it means the contract can be created. If not, request to Vendor Master Data Team this creation. | |
13 | In column | ||
14 | In Column |

# | Main activities | Tips / Best practices | Key points |
15 | Enter transaction ME31K. |

# | Main activities | Tips / Best practices | Key points |
16 | Enter the vendor number found in step 6. | ||
17 | Agreement type can be : | MK: used when the contract is based on quantities | Most usual is WK. |
18 | Enter the date of signature of contract. | If not available, enter the date the request was received. | |
19 | Enter the purchasing organization for which the contract must be setup. | For international agreements the P.Org is ZZ20. | |
20 | Enter the Purchasing group of the requester of contract creation. | If other P.Group requested clarify the discrepancy with the buyer. | |
21 | Hit Enter. |

# | Main activities | Tips / Best practices | Key points |
22 | On the appearing screen enter the company code of the requester. | The company code definition has no impact on contract creation. It is just a value to bypass the error. | |
23 | Click |

# | Main activities | Tips / Best practices | Key points |
24 | Enter the validity of the contract | It should never be more than 7 years, and it should never be 2999 or 9999, whatever asked by buyer | |
25 | Define the language of the contract. | For international agreements, EN must be used. | |
26 | Define the terms of payment of the contract. | The data shown are defined at P.Org level of the vendor and may not be the data contracted. | |
27 | Insert target value. | Mostly used is 999.999.999 . | This limit will allow to create POs/invoices up to this limit. |
28 | Insert the Incoterms. | The data shown are defined at P.Org level of the vendor and may not be the data contracted. | |
29 | Insert the ARIBA contract number. | Value: CW+7digits | |
30 | Insert the responsible for the contract on the vendor side. | ||
31 | Click in |

# | Main activities | Tips / Best practices | Key points |
32 | Define starting and end date of condition. | End date usually left 31.12.9999 unless the condition has a time limit. | |
33 | Select the condition to add. | Possible entries | |
34 | Is intervals must be defined, select the line and click |

# | Main activities | Tips / Best practices | Key points |
35 | Insert the start of the interval for which the condition must be applied. | This field can be the end of the interval depending on the condition selected. | |
36 | Chose the unit of measure from which the condition must applied. | ||
37 | Insert the condition to be applied. |

# | Main activities | Tips / Best practices | Key points |
38 | In the above example, the condition is defined as:
| ||
39 | Go back by clicking in | ||
40 | Click in |

# | Main activities | Tips / Best practices | Key points |
41 | To define the partners first select the P.Org for which the definition must be made. | In this screen, even though the contract is created only for 1 P.Org, all the ones for which the vendor is created will be shown. | |
42 | Clikc in |

# | Main activities | Tips / Best practices | Key points |
43 | Select the appropriate partner function. | Possible choices: | |
44 | Select the vendor. | If not known, please follow steps 2 to 8 of this OP. | |
45 | Click on | ||
46 | Click on |

The creation of the contract items can be manual or automatic.
The generic rule is that, in case the service contract has up to 5 lines, their creation can be done manually. Repeat the steps of chapter 2.3.1 up to 4 times.
If the contract has over 5 items there is only the need to create the first line and the ones afterwards can be created by file upload.
# | Main activities | Tips / Best practices | Key points |
47 | Enter Value D | It corresponds to a service | |
48 | Enter Value U (=unknown). This will enable for the account assignment to be defined upon the creation of the SES | ||
49 | Enter a brief description of the first item. | ||
50 | Enter the Material group of the item. Hit Enter or click |

# | Main activities | Tips / Best practices | Key points |
51 | Enter the Service number (previously created). | ||
52 | Enter the value contracted for this service. | Repeat these steps if contract item has only few services assigned. | |
53 | Go back with |

# | Main activities | Tips / Best practices | Key points |
54 | Repeat steps 47 to 53 for as many lines as need to be created. | Only 1 service is to be created per line. | |
55 | Save the contract. |

# | Main activities | Tips / Best practices | Key points |
56 | Enter transaction ZZMCCONTSERV. |

# | Main activities | Tips / Best practices | Key points |
57 | Enter the contract number | ||
58 | Enter the P.Org of the contract | ||
59 | Enter the vendor number | ||
60 | Chose "Test mode" or "Real mode" depending on the action. | Before running the transaction in "real mode" it is advisable to run it a first time in "test mode" to detect and correct errors. | |
61 | Click | ||
62 | Save the file before editing it. |

# | Main activities | Tips / Best practices | Key points |
63 | Add the services necessary per contract line. | ||
64 | Add the contracted price per each service. |

# | Main activities | Tips / Best practices | Key points |
65 | Finished file before uploading. |

# | Main activities | Tips / Best practices | Key points |
66 | Enter transaction ZZMCCONTSERV. |

# | Main activities | Tips / Best practices | Key points |
67 | Enter the contract number | ||
68 | Enter the P.Org of the contract | ||
69 | Enter the vendor number | ||
70 | Chose "Test mode" or "Real mode" depending on the action. | Before running the transaction in "real mode" it is advisable to run it a first time in "test mode" to detect and correct errors. | |
71 | Select the file previously worked on and upload it. | ||
72 | Click |

# | Main activities | Tips / Best practices | Key points |
73 | These warning messages do not block the creation of service lines they just alert that the same service is being used repeatedly. | ||
74 | Number of service lines to be created. | ||
75 | Click on |

# | Main activities | Tips / Best practices | Key points |
76 | Select the last line shown with your user. | ||
77 | Click |

# | Main activities | Tips / Best practices | Key points |
78 | Select "Display errors only" | If there are several lines to be created (over 100) it is preferable to run the session in background. | |
79 | Click |

# | Main activities | Tips / Best practices | Key points |
80 | Enter transaction ME33K. |

# | Main activities | Tips / Best practices | Key points |
81 | Enter the contract number and hit Enter. |

# | Main activities | Tips / Best practices | Key points |
82 | In the contract display the number of lines can be confirmed and click |

# | Main activities | Tips / Best practices | Key points |
83 | In the service list of each contract line you can confirm the services were created with the value defined on the Excel file. |

This procedure refers to the documents listed in the table below:
File name | Document type | Document title |
List of OPS related to PRO 20.1 | PRO | xxxx |