#

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 seeing 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

#

Main activities

Tips / Best practices

Key points

6

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

8

If there aren't any hits for the search, means the vendor is not setup in SAP and needs to be created..

TBD. CREATE TICKET TO….

#

Main activities

Tips / Best practices

Key points

9

Enter transaction MKVZ.

This transaction allows seeing 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

#

Main activities

Tips / Best practices

Key points

12

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

13

To remove blocking flag use transaction MK05.

14

To remove the deletion flag use transaction MK06.

#

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

MK: used when the contract is based on quantities
WK: used when the contract is based on amounts

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

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

#

Main activities

Tips / Best practices

Key points

24

Enter the validity of the contract

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 creating 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

31

#

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.

34

#

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:

• If the PO is between 10K€ and 20K€, there will be a discount of 1% to the total of the PO.
• If the PO is between 20K€ and 50K€, there will be a discount of 2% to the total of the PO
• All Pos over 50K€ will have a discount of 5%

39

40

#

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

#

Main activities

Tips / Best practices

Key points

43

Select the appropriate partner function.

44

Select the vendor.

If not known, please follow steps 2 to 8 of this OP.

45

46

#

Main activities

Tips / Best practices

Key points

47

Enter the material number.

If not yet created, TBD

48

Enter the unit price contracted. Click Enter.

The reaming data is retrieved from the material master record.

#

Main activities

Tips / Best practices

Key points

49

#

Main activities

Tips / Best practices

Key points

50

Enter transaction ZZMCCONT.

#

Main activities

Tips / Best practices

Key points

51

Enter the contract number previously created.

52

Enter the P.Org of the contract.

53

Enter the vendor number of the contract.

Code VN in partners.

54

Flag 'Test mode' or 'Real Mode'.

First run must be always in test mode to check possible errors and avoid in real mode.

55

Save the file before editing it.

#

Main activities

Tips / Best practices

Key points

56

Add the material numbers necessary for this contract.

57

Insert the unit price contracted for each material number.

58

After all the materials have been entered, select the first line.

1. click on the format Painter and copy the formatting to the remaining lines.
2. Delete the first line

59

Save the file.

#

Main activities

Tips / Best practices

Key points

60

Enter transaction ZZMCCONT again.

#

Main activities

Tips / Best practices

Key points

61

Enter the contract number previously created.

62

Enter the P.Org of the contract.

63

Enter the vendor number of the contract.

Code VN in partners.

64

Flag 'Test mode' or 'Real Mode'.

First run must be always in test mode to check possible errors and avoid in real mode.

65

Select the file previously worked on and click upload.

66

#

Main activities

Tips / Best practices

Key points

67

#

Main activities

Tips / Best practices

Key points

68

The number of lines created is shown.

69

#

Main activities

Tips / Best practices

Key points

70

Select the last line shown with your user.

71

#

Main activities

Tips / Best practices

Key points

72

Select "Display errors only"

If there are several lines to be created (over 100) it is preferable to run the session in background.

73

#

Main activities

Tips / Best practices

Key points

74

Enter transaction ME33K.

#

Main activities

Tips / Best practices

Key points

75

Enter the contract number and hit Enter.

#

Main activities

Tips / Best practices

Key points

76

In the contract display the number of lines can be confirmed and checked if are according to the request.

#

Main activities

Tips / Best practices

Key points

77

Enter transaction ZZMSOURC.

#

Main activities

Tips / Best practices

Key points

78

Enter the contract number.

79

Enter the plant for which the source list must be assigned.

80

Flag "Fixed source"

81

MRP update must be "1"

82

#

Main activities

Tips / Best practices

Key points

83

Enter transaction ZZMSOURA.

#

Main activities

Tips / Best practices

Key points

84

Chose online Create in order to make the assignment in realtime.

85

Insert the contract number.

Multiple contracts can be processed at the same time.

86

Enter the P.Org

87

Enter the plants on which the source assignment must be done.

88

Flag the Fixed Source for MRP field

89

MRP update must be "1".

90

#

Main activities

Tips / Best practices

Key points

91

The list of plants for which the source was assigned is shown.