Purchasing in SAP MM

 

2.1 Material Type

2.1.1 Define Attributes of Material Type

 

	Config-ID and Title:	Define attributes of material type
	Organization/Area:	MM
	ERP Responsible:	MM Team
		File Name:	Configuration Document – MM.doc
Responsibility:	MM Team	Status:	Open / Closed

 

Header Details

Description:	Define attributes of material type
Transaction Code:	SPRO
Menu Path:	IMG ->logistics-General-> Material Types -> Define attributes of material Type
Client dependent settings:	Yes / No

 

 

 

 

FIELDS	VALUES	COMMENTS
Material Type	ROH	In the step we create materiel type, it controls: 1.Number range 2.Views selection 3.Field selection 4.Procurement type 5.Number assignment (internal or external)
	FERT
	HALB

 

Use: Material type controls number range, views selection, field selection, procurement type, and number assignment (internal or external)

 

 

 

Description:	Define Field Selection of Material Master
Transaction Code:	SPRO
Menu Path:	IMG ->logistics-General->Material Master ->Field Selection ->Assign Fields to Field Selection
Client dependent settings:	Yes / No

 

 

Maintain Field Selection for Data Screens

 

 

2.1.2 Define Number Range For Each Material Type

 

Header Details

Description:	Define Number range for each material types
Transaction Code:	SPRO
Menu Path:	IMG ->logistics-General->Material Master ->Basic Setting ->Material Types -> Define Number Range For Each Material Type
Client dependent settings:	Yes / No

 

 

FIELDS	VALUES	COMMENTS
FERT,HALB,ROH,VERP   Other Material Types	A- ZZZZZZZZZZZZZZZZZ   Accordingly	In this step, you define the type of number assignment and the number range intervals for material master records. When creating a material master record, you must assign it a unique number

 

Use In this step, you define the type of number assignment and the number range intervals for material master records

 

Define Material Group

 

Description:	Define Number range for each material types
Transaction Code:	SPRO
Menu Path:	IMG ->logistics-General->Material Master ->Settings for Key Fields->Define Material Groups
Client dependent settings:	Yes / No

 

 

2.2  Vendor Master

2.2.1 Define Account Group For Vendor

 

	Config-ID and Title:	Define account group for vendor
	Organization/Area:	MM
	ERP Responsible:	MM Team
		File Name:	Configuration Document – MM.doc
Responsibility:	MM Team	Status:	Open / Closed

 

Header Details

Description:	Define Account Group
Transaction Code:	SPRO
Menu Path:	IMG ->Financial accounting basic setting->Account receivable and account payable -> Define Account group with screen layouts
Client dependent settings:	Yes / No

 

FIELDS	VALUES	COMMENTS
Account Group	0001	In the step you create account group.

 

 

For One time select check box

 

 

 

 

Use: Account group controls Number range, Number assignment (internal or external), Field selection, Vendor status (one time or regular vendor) and Partner function

 

In this step you determine the account groups for vendors.

You can also define reference account groups for one-time accounts. These enable you to control the fields in the one-time account screen. You can, for example, make certain fields required fields and suppress others.

When creating a vendor account, an account group must be specified. You can enter a reference account group in the "General data" section of the one-time account master record under "Control data". If you do not specify a reference account group, all fields in the one-time account screen for document entry are ready for input (as before).

Via the account group you determine

• The interval for the account numbers

• Whether the number is assigned internally by the system or externally by the user (type of number assignment)

• Whether it is a one-time account

• Which fields are ready for input or must be filled when creating and changing master records (field status)

Example:

In the one-time accounts you want to suppress the address, communication and bank detail fields. These fields are part of the general data and so you set the field status in the general data section. Define the reconciliation account as a required field since this is a required entry for one-time accounts as well. The field is company code-dependent so you define the status for this field in the company data section.

With the account groups, you group accounts together according to the criteria mentioned above, for example, one-time accounts. You determine the account number interval and the type of number assignment by using number ranges.

 

2.3  Purchase Group

 

2.3.1 Create Purchase group 

 

	Config-ID and Title:	Create Purchase Group
	Organization/Area:	MM
	ERP Responsible:	MM Team
		File Name:	Configuration Document – MM.doc
Responsibility:	MM Team	Status:	Open / Closed

 

Header Details

Description:	Create Purchase Group
Transaction Code:	SPRO
Menu Path:	IMG -> Material Management -> Purchasing  ->Create Purchasing Groups
Client dependent settings:	Yes / No

 

A key for a buyer or group of buyers responsible for certain purchasing activities.

The purchasing group is:

• Internally responsible for the procurement of a material or a class of materials

• The principal channel for a company's dealings with its vendors

 

 

 

 

 

FIELDS	VALUES	COMMENTS
- Purchase Group		In this step, you can create purchasing groups. A purchasing group can be an individual or a group of individuals

 

Use: A key for a buyer or group of buyers responsible for certain purchasing activities. The purchasing group is internally responsible for the procurement of a material or a class of materials and it is the principal channel for a company's dealings with its vendors

 

 

 

2.4  Purchase Info Record

 

2.4.1 Define Number Range For Purchase Info Record

 

 

	Config-ID and Title:	Define Number Range and Screen Layout for Purchase Info Record
	Organization/Area:	MM
	ERP Responsible:	MM Team
		File Name:	Configuration Document – MM.doc
Responsibility:	MM Team	Status:	Open / Closed

 

Header Details

Description:	Define Number Range for Purchase Info Record
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management->Purchasing-> Purchase Info Record ->Define Number Range
Client dependent settings:	Yes / No

 

 

FIELDS	VALUES	COMMENTS
		In this step, you assign each transaction to a number range group. You define the number range interval for each group. In addition, you specify whether the number range is assigned by the user at the time of entry (i.e. externally) or by the system (i.e. internally )

 

 

 

2.4.2 Define Screen Layout For Purchase Info Record

 

Description:	Define Screen Layout For Purchase Info Record
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management ->Purchasing ->Purchase Info Record ->Define Screen Layout
Client dependent settings:	Yes / No

 

 

 

FIELDS	VALUES	COMMENTS
Vendor	Display	In this step, you make the settings for the screen layout and field attributes.

 

Use: In the purchasing info record, you can control the attributes of input fields. You can specify which field

• Require an entry (required-, or mandatory-entry field),
• Permit an entry (optional-entry field) 
• Do not allow an entry (display-only, or hidden field)

 

 

2.5 Purchase Requisition

 

2.5.1 Define Document Types For Purchase Requisition

 

	Config-ID and Title:	Define Document Types
	Organization/Area:	MM
	ERP Responsible:	MM Team
		File Name:	Configuration Document – MM.doc
Responsibility:	MM Team	Status:	Open / Closed

 

Header Details

Description:	Define Document types
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management->Purchasing-> Purchase Requisition ->Define Document Types
Client dependent settings:	Yes / No

 

FIELDS	VALUES	COMMENTS
Document types NB          UB	Description Purch Req  Purch Req Stk Tra.	In this step we create document type for purchase requisition.

 

Use: Document type controls:

• Number range
• Number assignment (internal or external)
• Field Selection
• Allowed item category
• Allowed follow-on document types

 

 

 

 

2.5.2 Maintain Number Range For Purchase Requisition

 

	Config-ID and Title:	Maintain number range
	Organization/Area:	MM
	ERP Responsible:	MM Team
		File Name:	Configuration Document – MM.doc
Responsibility:	MM Team	Status:	Open / Closed

 

Description:	Maintain Number Range
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management ->Purchasing -> purchase requisition ->Maintain Number Range
Client dependent settings:	Yes / No

 

2.5.3 Define screen layout at document level

 

	Config-ID and Title:	Define screen layout
	Organization/Area:	MM
	ERP Responsible:	MM Team
		File Name:	Configuration Document – MM.doc
Responsibility:	MM Team	Status:	Open / Closed

 

Header Details

Description:	Define Screen Layout
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management ->Purchasing -> purchase requisition ->Define Screen Layout at Document level
Client dependent settings:	Yes / No

 

 

 

 

 

 

 

FIELDS	VALUES	COMMENTS
Plant	Required entry	In this step you mark fields as Requird, Optional, Display. Assign field selection reference key to Document type in the step IMG ->Material Management->Purchasing-> Purchase Requisition ->Define Document types

 

Use: In the Purchase Requisition, you can control the attributes of input fields. You can specify which field

• Require an entry (required-, or mandatory-entry field),
• Permit an entry (optional-entry field) 
• Do not allow an entry (display-only, or hidden field)

 

 

 

 

 

2.5.4 Define Release procedure For Purchase Requisition

 

Header Details

Description:	Define Release procedure
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management ->Purchasing ->Purchase Requisition -> Release Procedure->Procedure with Classification->Edit Characteristics
Client dependent settings:	Yes / No

 

FIELDS	VALUES	COMMENTS
Characteristics	CEBAN_BSART CEBAN_BEDNR CEBAN_MATKL CEBAN_WERKS	In this step, you create characteristics for a release procedure with classification.

 

Use: Classification characteristics constitute the criteria for a release condition. If the criteria of a release condition are satisfied, the associated release strategy is assigned to the purchase requisition

 

Header Details

 

Description:	Define Class
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management ->Purchasing ->Purchase Requisition -> Release Procedure->Procedure with Classification->Edit class
Client dependent settings:	Yes / No

 

 

 

 

 

FIELDS	VALUES	COMMENTS
Class	PR_PUR	In this step you create class and maintain characteristics in characteristics tab page.

 

Use: In a class, you group the characteristics that are to constitute a release condition for a release strategy. In the step " Set up Procedure with Classification", you assign this class to the release procedure.

 

 

 

 

 

Header Details

Description:	Set Up Procedure With Classification
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management ->Purchasing ->Purchase Requisition -> Release Procedure->Procedure with Classification-> Set Up Procedure With Classification->Define Release Group
Client dependent settings:	Yes / No

 

 

 

 

FIELDS	VALUES	COMMENTS
Release Group	Please refer the details in the sheet enclosed above.	In this step you maintain Release Group and Release Class.

 

Use: Specify for the release group either "overall release" or "item-wise release" using the OverReqRel (overall requisition release) indicator. You determine whether a purchase requisition can be released in total or item-by-item via the document type. If, for example, you have defined the former, that is, the overall release, for document type "NB - purchase requisition", a requisition of the document type "NB" cannot be released on an item-wise basis. For this reason, the release group for overall release, for example, only applies to the document types with overall release.

Header Details

Description:	Define Release Code
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management ->Purchasing ->Purchase Requisition -> Release Procedure->Procedure with Classification-> Set Up Procedure With Classification->Define Release Code
Client dependent settings:	Yes / No

 

 

 

 

 

 

 

FIELDS	VALUES	COMMENTS
Release codes		In this step maintain Release Group and Release Codes.

 

Use Here you create the release codes that you need for your release strategy and assign the codes to your release group. If a release code is to be used in workflow, indicate this accordingly in the Workflow field.

 

 

 

Header Details

Description:	Define Release Indicator
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management ->Purchasing ->Purchase Requisition -> Release Procedure->Procedure with Classification-> Set Up Procedure With Classification-> Release Indicator
Client dependent settings:	Yes / No

 

Screen Entry Details

 

 

FIELDS	VALUES	COMMENTS
Release Indicator 1 2 3 4 A B X	Description Request for quotation RFQ/purchase order RFQ/PO no change of date RFQ/PO no changes Fixed RFQ Fixed RFQ/purchase order Blocked for Purchase _	In this step maintain release indicator

Use: A release indicator shows the release status of a purchase requisition. Predefined release indicators, which you can use for your release strategy, are available in the standard system.

 

 

 

 

 

Header Details

Description:	Define Release Strategies
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management ->Purchasing ->Purchase Requisition -> Release Procedure->Procedure with Classification-> Set Up Procedure With Classification-> Release Strategies
Client dependent settings:	Yes / No

 

 

 

FIELDS	VALUES	COMMENTS
Release Strategy  Please refer the details below.	Description	In this step maintain Release Strategies, Release Prerequisite, Release Status and Release Classification. Using Release Simulation can check Release Procedure.

 

Use: Create a release strategy for your release group and assign your release codes accordingly

 

 

 

2.6             Request For Quotation

 

2.6.1 Define Document for Request For Quotation

 

	Config-ID and Title:	Define Document Types
	Organization/Area:	MM
	ERP Responsible:	MM Team
		File Name:	Configuration Document – MM.doc
Responsibility:	MM Team	Status:	Open / Closed

 

Header Details

Description:	Define Document types
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management->Purchasing->RFQ/Quotation -> Define Document types   IMG ->Material Management->Purchasing->RFQ/Quotation ->Define Document types  ->Allowed Item Category IMG ->Material Management->Purchasing->RFQ/Quotation ->Define Document types->Link Purchase Requisition –Document Type
Client dependent settings:	Yes / No

 

 

 

 

 

 

FIELDS	VALUES	COMMENTS
Document types	AN: RFQ- Domestic ANM:RFQ- Imports	In this step you create document type for Request for Quotation, it controls: 1Number Range 2.Number assignment (internal or external) 3.Field Selection 4.Allowed follow-on document types 5.Allowed item category

 

 

Use: Document type controls:

• Number range
• Number assignment (internal or external)
• Field Selection
• Allowed item category
• Allowed follow-on document types

 

2.6.2 Maintain Number Range 

 

Header Details

Description:	Maintain Number Range
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management ->Purchasing ->RFQ/Quotation  ->Define Number Ranges
Client dependent settings:	Yes / No

 

 

FIELDS	VALUES	COMMENTS
AN - 60	6000000000-6099999999	In this step you maintain number range interval for Number Range Number
ANM - 61	6100000000- 6199999999

 

 

 

2.6.3 Define Screen Layout at Document Level

 

Header Details

Description:	Maintain Screen Layout
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management ->Purchasing ->RFQ/Quotation ->Define Screen Layout at Document level
Client dependent settings:	Yes / No

 

 

 

 

 

 

FIELDS	VALUES	COMMENTS
Plant	Required entry Collective RFQ Deadline Submission of Quotation Start of Validity Period End of Validity period Target Qty Unit of Measure Tax Code	In this step you mark fields as Requird, Optional, Display Assign field selection reference key to Document type in the step IMG ->Material Management->Purchasing-> RFQ/Quotation ->Define Document types

 

Use: In the  Purchasing document , you can control the attributes of input fields. You can specify which field

• Require an entry (required-, or mandatory-entry field),
• Permit an entry (optional-entry field) 
• Do not allow an entry (display-only, or hidden field)

 

 

2.7            Purchase Order

 

2.7.1 Define Document Type For Purchase Order

 

	Config-ID and Title:	Define Document types
	Organization/Area:	MM
	ERP Responsible:	MM Team
		File Name:	Configuration Document – MM.doc
Responsibility:	MM Team	Status:	Open / Closed

 

Header Details

Description:	Define Document types
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management->Purchasing-> Purchase Order       ->Define Document types    IMG ->Material Management->Purchasing-> Purchase Order       ->Define Document types ->Allowed Item Categories   IMG ->Material Management->Purchasing-> Purchase Order       ->Define Document types  -> Link Purchase Requisition –Document Type
Client dependent settings:	Yes / No

Use: Document type controls:

• Number range
• Number assignment (internal or external)
• Field Selection
• Allowed item category
• Allowed follow-on document types

2.7.2 Maintain number range

 

Header Details

Description:	Maintain Number Range
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management ->Purchasing -> Purchase Order ->Define Number Ranges
Client dependent settings:	Yes / No

 

 

2.7.3 Define screen layout at document level

 

Header Details

Description:	Maintain Number Range
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management ->Purchasing -> purchase Order  ->Define Screen Layout at Document level
Client dependent settings:	Yes / No

 

 

 

 

 

FIELDS	VALUES	COMMENTS
Plant	Required entry Currency Delivery Date Tax Code Purchase Req No.	In this step you mark fields as Required, Optional, Display Assign field selection reference key to Document type in the step IMG ->Material Management->Purchasing-> Purchase Order ->Define Document types

 

Use: In the Purchasing document, you can control the attributes of input fields. You can specify which field

• Require an entry (required-, or mandatory-entry field),
• Permit an entry (optional-entry field) 
• Do not allow an entry (display-only, or hidden)

 

 

 

 

 

2.7.4 Define Release procedure For Purchase order

 

Header Details

Description:	Define Release procedure
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management ->Purchasing ->Purchase Order -> Release Procedure for purchase order ->Edit Characteristics
Client dependent settings:	Yes / No

 

 

 

 

 

 

 

 

FIELDS	VALUES	COMMENTS
Characteristics PO_PUR_DOCTYPE                PO_PUR_NETVALUE                PO_Pur_Group                 PO_PUR_PLANT	Order type (Purchasing)   Total net order value   Purchasing group   Plant	In this step, you create characteristics for a release procedure for purchase orders (POs).

 

Use: Classification characteristics constitute the criteria for a release condition. If the criteria of a release condition are satisfied, the associated release strategy is assigned to the purchase requisition

 

Use: Classification characteristics constitute the criteria for a release condition. If the criteria of a release condition are satisfied, the associated release strategy is assigned to the purchase requisition

 

 

 

Header Details

Description:	Define Class
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management ->Purchasing ->Purchase Order -> Release Procedure for Purchase Order ->Edit class
Client dependent settings:	Yes / No

 

 

 

 

FIELDS	VALUES	COMMENTS
Class PO_PUR	Class name Release Strategy for Purchase	In this step you create class and maintain characteristics in characteristics tab page.

 

 

Use: In a class, you group the characteristics that are to constitute a release condition for a release strategy. In the step " Set up Procedure with Classification", you assign this class to the release procedure.

 

Header Details

Description:	Set Up Procedure With Classification
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management ->Purchasing ->Purchase Order -> Release Procedure for Purchase Order-> Define Release Procedure for Purchase Order-> Release Groups
Client dependent settings:	Yes / No

 

 

 

FIELDS	VALUES	COMMENTS
Release Group	Please see the Release Group above.	In this step maintain release Group and Release Class.

 

 

Use: Create a release group for your release procedure and assign it to a class. In the process, you assign release conditions to the release procedure

 

Header Details

Description:	Define Release Codes
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management ->Purchasing ->Purchase Order -> Release Procedure for Purchase Order-> Define Release Procedure for Purchase Order-> Release Codes
Client dependent settings:	Yes / No

 

 

 

 

FIELDS	VALUES	COMMENTS
Release codes	Please refer the value of Codes above	In this step maintain Release Group and Release Codes.

 

Use Here you create the release codes that you need for your release strategy and assign the codes to your release group. If a release code is to be used in workflow, indicate this accordingly in the Workflow field.

 

 

 

Header Details

Description:	Define Release Indicator
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management ->Purchasing ->Purchase Order -> Release Procedure for Purchase Order-> Define Release Procedure for Purchase Order-> Release Indicator
Client dependent settings:	Yes / No

 

 

FIELDS	VALUES	COMMENTS
A B	Blocked for Processing Released	In this step maintain release indicator

Use: A release indicator shows the release status of a purchase requisition. Predefined release indicators, which you can use for your release strategy, are available in the standard system.

Header Details

Description:			Define Release Strategies
Transaction Code:			SPRO
Menu Path:			IMG ->Material Management ->Purchasing ->Purchase Order -> Release Procedure for Purchase Order-> Define Release Procedure for Purchase Order-> Release Strategies
Client dependent settings:			Yes / No
	FIELDS	VALUES		COMMENTS
		Please refer the details below		In this step maintain release strategies, release prerequisite, release status and, release classification. Using release simulation can check release procedure.

 

 

Use: Create a release strategy for your release group and assign your release codes accordingly

 

 

 

2.8            Contract

 

2.9.1 Define Document Type

 

	Config-ID and Title:	Define Document Type
	Organization/Area:	MM
	ERP Responsible:	MM Team
		File Name:	Configuration Document – MM.doc
Responsibility:	MM Team	Status:	Open / Closed

 

 

 

 

Header Details

Description:	Define Document types
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management->Purchasing-> Contract ->Define Document types      IMG ->Material Management->Purchasing-> Contract ->Define Document types ->Allowed Item Categories   IMG ->Material Management->Purchasing-> Contract ->Define Document types -> Link Purchase Requisition –Document Type
Client dependent settings:	Yes / No

 

 

FIELDS	VALUES	COMMENTS
MK WK	Quantity Cont Value Cont	In this step we create document type for purchase Order, it controls: 1.Number range 2.Number assignment (internal or external) 3.Field Selection 4.Allowed follow-on document types 5.Allowed item category

 

Use : Document type controls:

• Number range
• Number assignment (internal or external)
• Field Selection
• Allowed item category
• Allowed follow-on document types

 

 

2.9.2 Maintain Number Range  

 

Header Details

Description:	Maintain Number Range
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management ->Purchasing -> Contract ->Define Number Ranges
Client dependent settings:	Yes / No

 

 

 

 

 

FIELDS	VALUES	COMMENTS
46	460000000 – 469999999	In this step you maintain number range interval for Number Range Number and assign this number Range to Document type  in menu path :IMG->Material Management -> Purchasing-> Contract->Define Document Types

 

 

2.9.3 Define Screen Layout at Document Level

 

 

Header Details

Description:	Define screen layout at document level
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management ->Purchasing -> contract ->Define Screen Layout at Document level
Client dependent settings:	Yes / No

 

 

FIELDS	VALUES	COMMENTS
Plant	Optional entry	In this  step you mark fields as Requird,Optional ,Display Assign field selection reference key to Document type in the step IMG ->Material Management->Purchasing-> Purchase Order ->Define Document types

 

Use: In the Purchase Requisition, you can control the attributes of input fields. You can specify which field

• Require an entry (required-, or mandatory-entry field),
• Permit an entry (optional-entry field) 
• Do not allow an entry (display-only, or hidden field

 

 

 

 

 

 

2.9            Scheduling Agreement

 

2.10.1 Define Document Type

 

	Config-ID and Title:	Define Document Types
	Organization/Area:	MM
	ERP Responsible:	MM Team
		File Name:	Configuration Document – MM.doc
Responsibility:	MM Team	Status:	Open / Closed

 

Header Details

Description:	Define Document types
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management->Purchasing-> Scheduling Agreement ->Define Document types    IMG ->Material Management->Purchasing-> Scheduling Agreement ->Define Document types ->Allowed Item Categories   IMG ->Material Management->Purchasing-> Scheduling Agreement->Define Document types -> Link Purchase Requisition –Document Type
Client dependent settings:	Yes / No

 

 

FIELDS	VALUES	COMMENTS
LP LPA LU	Scheduling Agt Scheduling Agt Transp. sched. agmt.	In this step we create document type for purchase Order, it controls: 1.Number range 2.Number assignment (internal or external) 3.Field Selection 4.Allowed follow-on document types 5.Allowed item category 6.Time Dependent or Time Independent

 

Use: document type controls:

1.Number range

2.Number assignment (internal or external)

3.Field Selection

4.Allowed follow-on document types

5.Allowed item category

6.Time Dependent or Time Independent

 

 

2.10.2 Maintain Number Range 

 

Header Details

Description:	Maintain Number Range
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management ->Purchasing -> Scheduling Agreement ->Define Number Ranges
Client dependent settings:	Yes / No

 

 

 

FIELDS	VALUES	COMMENTS
55	5500000000 – 5599999999	In this step you maintain number range interval for number range number and this number range to document type in menu path: IMG ->Material Management->Purchasing->Scheduling Agreement ->Define Document types

 

2.10.3 Define Screen Layout at Document Level

 

Header Details

Description:	Define screen layout at document level
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management ->Purchasing ->Scheduling Agreement ->Define Screen Layout at Document level
Client dependent settings:	Yes / No

 

 

FIELDS	VALUES	COMMENTS
Plant	Optional entry	In this step you mark fields as Requird, Optional, Display Assign field selection reference key to Document type in the step IMG ->Material Management->Purchasing-> Scheduling Agreement ->Define Document types

 

Use: In the Scheduling Agreement , you can control the attributes of input fields. You can specify which field

• Require an entry (required-, or mandatory-entry field),
• Permit an entry (optional-entry field) 
• Do not allow an entry (display-only, or hidden field)

 

2.6            Scheduling Agreement

 

2.10.1 Define Document Type

 

	Config-ID and Title:	Define Document Types
	Organization/Area:	MM
	ERP Responsible:	MM Team
		File Name:	Configuration Document – MM.doc
Responsibility:	MM Team	Status:	Open / Closed

 

Header Details

Description:	Define Document types
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management->Purchasing-> Scheduling Agreement ->Define Document types    IMG ->Material Management->Purchasing-> Scheduling Agreement ->Define Document types ->Allowed Item Categories   IMG ->Material Management->Purchasing-> Scheduling Agreement->Define Document types -> Link Purchase Requisition –Document Type
Client dependent settings:	Yes / No

 

 

FIELDS	VALUES	COMMENTS
LP LPA LU	Scheduling Agt Scheduling Agt Transp. sched. agmt.	In this step we create document type for purchase Order, it controls: 1.Number range 2.Number assignment (internal or external) 3.Field Selection 4.Allowed follow-on document types 5.Allowed item category 6.Time Dependent or Time Independent

 

Use: document type controls:

1.Number range

2.Number assignment (internal or external)

3.Field Selection

4.Allowed follow-on document types

5.Allowed item category

6.Time Dependent or Time Independent

 

 

2.10.2 Maintain Number Range 

 

Header Details

Description:	Maintain Number Range
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management ->Purchasing -> Scheduling Agreement ->Define Number Ranges
Client dependent settings:	Yes / No

 

 

 

FIELDS	VALUES	COMMENTS
55	5500000000 – 5599999999	In this step you maintain number range interval for number range number and this number range to document type in menu path: IMG ->Material Management->Purchasing->Scheduling Agreement ->Define Document types

 

2.10.3 Define Screen Layout at Document Level

 

Header Details

Description:	Define screen layout at document level
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management ->Purchasing ->Scheduling Agreement ->Define Screen Layout at Document level
Client dependent settings:	Yes / No

 

 

FIELDS	VALUES	COMMENTS
Plant	Optional entry	In this step you mark fields as Requird, Optional, Display Assign field selection reference key to Document type in the step IMG ->Material Management->Purchasing-> Scheduling Agreement ->Define Document types

 

Use: In the Scheduling Agreement , you can control the attributes of input fields. You can specify which field

• Require an entry (required-, or mandatory-entry field),
• Permit an entry (optional-entry field) 
• Do not allow an entry (display-only, or hidden field)

 

 

 

 

2.11.Confirmation   

 

2.11.1 Define External Confirmation Categories

 

	Config-ID and Title:	Confirmation
	Organization/Area:	MM
	ERP Responsible:	MM Team
		File Name:	Configuration Document – MM.doc
Responsibility:	MM Team	Status:	Open / Closed

 

Header Details

Description:	Define External Confirmation Categories
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management ->Purchasing -> Confirmations ->Define External Confirmation Categories
Client dependent settings:	Yes / No

 

 

FIELDS	VALUES	COMMENTS
AB GW LA	Order acknowledgment Rough GR Inbound delivery	In this step, you define the external confirmation categories. If you have set up confirmation control in a production system, you should not make any changes to these settings. Changes to the Customizing settings can lead to data inconsistencies in your system - for example, incorrect MRP-relevant quantities.

 

Use: The term "confirmation" (short for "vendor confirmation") is an umbrella term for various types of information provided by a vendor to a customer, including order acknowledgments, loading or transport confirmations and shipping notifications.

If the customer's materials planning and inventory control system does not work with confirmations, it can only refer to the delivery dates and quantities set out in the purchase order. The use of confirmations, on the other hand, makes the materials planning and inventory control process more precise, since between the PO date and the planned delivery date the customer receives increasingly reliable information about the pending arrival of ordered goods.

 

2.11.2 Define Internal Confirmation Categories

 

Header Details

Description:	Define Internal Confirmation Categories
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management ->Purchasing -> Confirmations ->Define Internal Confirmation Categories
Client dependent settings:	Yes / No

 

FIELDS	VALUES	COMMENTS
Order acknowledgment Shipping notification Rough goods receipt	AB LA GW	In this step, you assign an external confirmation category to each internal confirmation category. On the basis of this assignment, the system is able to recognize which confirmation category represents order acknowledgments and which one represents shipping notifications

 

Use: In this step, you assign an external confirmation category to each internal confirmation category.

On the basis of this assignment, the system is able to recognize which confirmation category represents order acknowledgments and which one represents shipping notifications, for example.

 

2.11.3 Set Up Confirmation Control

 

Header Details

Description:	Set Up Confirmation Control
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management ->Purchasing -> Confirmations ->Set Up Confirmation Control
Client dependent settings:	Yes / No

 

FIELDS	VALUES	COMMENTS
0001   0002    0003    0004	Confirmations Rough GR Inb. deliv./rough GR Inbound delivery	Confirmation control key For PO items in respect of which confirmations are to be used, a confirmation key must be assigned. Example You can define a confirmation control key with just one confirmation category (e.g. shipping notification) and a confirmation control key covering several confirmation categories (order acknowledgment, loading confirmation, shipping notification).

 

Use:In this step, you define confirmation control keys and specify the confirmation sequence.

 

 

 

 

 

FIELDS	VALUES	COMMENTS
Sequence 1 2	Confirmation Category AB LA	With the confirmation sequence, you can specify the order in which the individual confirmations defined in a confirmation control key are expected and which confirmation categories are to be automatically monitored. In addition, you can specify for all confirmation categories whether they are for your information only or are also to be relevant to Materials Planning and Goods Receiving.

 

2.12       Pricing Procedure

 

2.12.1Condition Table

 

	Config-ID and Title:	Define Pricing Procedure
	Organization/Area:	MM
	ERP Responsible:	MM Team
		File Name:	Configuration Document – MM.doc
Responsibility:	MM Team	Status:	Open / Closed

 

Header Details

Description:	Define Condition Table
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management ->Purchasing -> Condition -> Define Price Determination Process -> Maintain Condition Table -> Change Condition Table
Client dependent settings:	Yes / No

 

 

 

 

 

 

FIELDS	VALUES	COMMENTS
	Purchasing Document Item	In this step maintain fields in selected field column from allowed field column..

 

Use : In a condition table, you specify the combination of fields for which you can create condition records

 

 

2.12.2 Define Access Sequences

 

Header Details

Description:	Define Access Sequences
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management ->Purchasing -> Condition -> Define Price Determination Process -> Define  Access Sequences
Client dependent settings:	Yes / No

 

 

 

 

FIELDS	VALUES	COMMENTS
Access Sequence	ZFRT     freight access sequence	An access sequence is a search strategy with the aid of which the SAP System searches for valid condition records of a certain condition type. For example, you can stipulate for a price that the SAP System first searches for a price for a specific plant, and then for a generally applicable price

 

 2.12.3 Define Condition Type

 

 Header Details

 

Description:	Define Condition Type
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management ->Purchasing -> Condition -> Define Price Determination Process -> Define Condition Type->Define Condition Type
Client dependent settings:	Yes / No

 

 

 

 

 

 

 

FIELDS		VALUES	COMMENTS
			1. In this step define condition type and maintain required field i.e. condition type, condition category, condition class. 2. For Automatic condition type maintains Access Sequence in access seq. field. 3. For main condition type maintain pricing procedure in pricing procedure field.

 

 

 

 

2.12.4 Define Schema Group

 

 Header Details

Description:	Define Schema Group   1.Schema Group: Vendor 2.Schema Groups For Purchase Organization 3. Assignment of Schema Group to Purchasing Organization
Transaction Code:	SPRO
Menu Path:	1.IMG ->Material Management ->Purchasing -> Condition -> Define Price Determination Process -> Define Schema Group->Schema Groups: Vendor   2. IMG ->Material Management ->Purchasing -> Condition -> Define Price Determination Process -> Define Schema Group->Schema Group For Purchase Organization   3. IMG ->Material Management ->Purchasing -> Condition -> Define Price Determination Process -> Define Schema Group->Assignment of Schema Group to Purchasing Organization
Client dependent settings:	Yes / No

 

 

 

FIELDS	VALUES	COMMENTS
		In this step define Vendor Schema, Purchase Org. Schema and Assign Purchase Org. Schema to Purchase Organization

 

2.12.5 Define Calculation Schema

 

Header Details

Description:	Define Calculation Schema
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management ->Purchasing -> Condition -> Define Price Determination Process -> Define calculation schema
Client dependent settings:	Yes / No

 

 

 

 

 

 

 

FIELDS		VALUES	COMMENTS
			In this step define Calculation Schema.

 

 

 

2.12.6 Determine Calculation Schema

 

 Header Details

Description:	Determine Calculation Schema
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management ->Purchasing -> Condition -> Define Price Determination Process -> Define schema Determination ->Determine Calculation Schema for Standard Purchase Orders
Client dependent settings:	Yes / No

 

 

 

 

 

                         

FIELDS	VALUES	COMMENTS
	Refer the details given above.	In this step assign vendor schema and purchase organization schema to pricing procedure.

 

Vendor Schema Group

 

Purchase organization Schema Group

 

Purchase Organization  assigned to Purchase org. Schema Group.

 

 

Schema Determination  for Std. Purchase Order.

 

 

 

2.14 Messages

 

	Config-ID and Title:	Messages
	Organization/Area:	MM
	ERP Responsible:	MM Team
		File Name:	Configuration Document – MM.doc
Responsibility:	MM Team	Status:	Open / Closed

 

 

 

 

2.14.1 Output Control

 

 Header Details

Description:	Output Control
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management ->Purchasing -> Output Control  ->Message Type->Define Message Type For Request For Quotation
Client dependent settings:	Yes / No

 

                        

FIELDS	VALUES	COMMENTS
Output Type	NEU	In this step, you define the message types for RFQs. In the SAP System, the message type denotes different kinds of message (in Purchasing, mainly communications sent to vendors, such as purchase orders, order acknowledgments, and expediters) Similarly you can define Message type for Purchase Order, Contract, and Scheduling Agreement.

 

 

 

 

2.15       Vendor Evaluation

 

	Config-ID and Title:	Vendor Evaluation
	Organization/Area:	MM
	ERP Responsible:	MM Team
		File Name:	Configuration Document – MM.doc
Responsibility:	MM Team	Status:	Open / Closed

 

2.15.1 Header Details

 

Description:	Define Weighting Key
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management ->Purchasing -> Vendor Evaluation ->Define Weighting Key
Client dependent settings:	Yes / No

 

 

 

 

                      

FIELDS		VALUES	COMMENTS
01 02	Equal weighting Unequal weighting		In this step define weighting key. In vendor evaluation the key by which evaluation criteria are weighted according to their importance. For example, the overall evaluation of a vendor is calculated from the scores awarded for the main evaluation criteria "price," "quality," and "delivery." The latter comprises "on-time delivery performance" and "quantity reliability

 

 

 

2.15.2 Define Criteria 

 

Header Details

Description:	1.Define Criteria 2.Define Sub criteria
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management ->Purchasing -> Vendor Evaluation ->Define Criteria
Client dependent settings:	Yes / No

 

                      

FIELDS		VALUES	COMMENTS
01 02 03 04 05	Price Quality Delivery Service Service		In this step, you define the criteria by which the system computes scores for vendors and specify whether the scores for the sub criteria are computed manually, semi-automatically, or automatically.

 

 

 

2.15.3 Define Scope Of List

 

 Header Details

Description:	Define Scope Of List
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management ->Purchasing -> Vendor Evaluation ->Define Scope of List
Client dependent settings:	Yes / No

 

 

 

 

 

 

                      

FIELDS	VALUES	COMMENTS
1 2 3 4 5 6 7	Overall evaluation Price Quality Delivery Service Service	In this step, you can define various types of list, each representing different main criteria or the same main criteria in a different order. The parameter Version 1 yields a ranking list of vendors sorted according to the score for the main criterion "Price". Then follow the overall evaluation and the main criteria "General service/support", "Quality", "Delivery", and "Externally performed service/work".

 

 

 

 

2.15.4  Define Purchase Organization Data For Vendor Evaluation

 

Header Details

 

Description:	Define Purchase Organization Data For Vendor Evaluation
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management ->Purchasing -> Vendor Evaluation -> Define Purchase Organization Data For Vendor Evaluation
Client dependent settings:	Yes / No

 

 

 

 

 

 

 

 

 

                      

FIELDS	VALUES	COMMENTS
Please refer the values given above		In this step, you define individual Vendor Evaluation System settings for each purchasing organization. In the process, please note that all parameters must be maintained in order for the system to be able to compute scores. If, for example, you do not maintain any smoothing factors for the criteria "on-time delivery performance", "quantity reliability", and "compliance with shipping instructions", the system will not be able to compute the scores.

 

 

 

 

 

 

 

 

2.16 Partner Determination 

 

	Config-ID and Title:	Partner Determination
	Organization/Area:	MM
	ERP Responsible:	MM TEAM
		File Name:	Configuration Document – MM.doc
Responsibility:	MM Team	Status:	Open / Closed

 

2.16.1 Header Details

Description:	Partner Determination
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management -> Purchasing->Partner Determination  ->Partner Roles->Define Partner Roles
Client dependent settings:	Yes / No

 

 

 

                      

FIELDS	VALUES	COMMENTS
		In this step, you define the partner roles. You specify the roles involved: vendor, customer, own employee etc

 

 

 

2.16.2 Define Permissible Partner Role Per Account Group

 

Header Details

Description:	Partner Determination
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management -> Purchasing->Partner Determination  ->Partner Roles->Define Permissible Partner Role Per Account Group
Client dependent settings:	Yes / No

 

 

 

FIELDS	VALUES	COMMENTS
		In this step you can specify for each account group of the vendor which role the vendor may assume. You can specify that certain vendor may only serve as an ordering address not as an invoicing party.

 

 

 

 

 

2.16.3 Define Partner Schema

Header Details

Description:	Define Partner Schema
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management -> Purchasing->Partner Determination  ->Partner Roles->Partner Setting in vendor Master Record ->Define Partner Schema
Client dependent settings:	Yes / No

 

 

 

FIELDS	VALUES	COMMENTS
		In this step, you define partner determination schemas. Partner schemas allow you to group various partner roles. You can specify that certain roles in a schema are mandatory, i.e. cannot be changed after entry. . In this step, you assign partner schemas to account groups. Example Account group 0001 has the partners "vendor", "goods supplier", and "invoicing party". Account group 0002 has the same roles plus the roll of "different payee

 

 

2.16.4  Partner Setting In Purchasing Document

 

Header Details

Description:	Partner Setting In Purchasing Document
Transaction Code:	SPRO
Menu Path:	IMG ->Material Management -> Purchasing->Partner Determination  ->Partner Roles->Partner Setting in Purchasing Document  ->Define Partner Schema
Client dependent settings:	Yes / No

 

 

FIELDS	VALUES	COMMENTS
		In this section, you make the partner settings for purchasing documents. Partner schemas enable you to group various partner roles. You can specify that certain roles in a schema are mandatory, i.e. may not be changed after entry. You can assign these partner schemas to different purchasing document types. This has the effect that only the roles of this schema can be maintained in documents belonging to this document type.

 

 

 

 

Part 3

3           External Service Management

 

External Service Management

	Config-ID and Title:	External Service Management
	Organization/Area:	MM
	ERP Responsible:	MM TEAM
		File Name:	Configuration Document – MM.doc
Responsibility:	MM Team	Status:	Open / Closed