Purchasing In MM 2

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.