MM-PUR - SapTopjobs Purchasing Configuration

8/9/2019 MM-PUR - SapTopjobs Purchasing Configuration

http://slidepdf.com/reader/full/mm-pur-saptopjobs-purchasing-configuration 1/88

SAP MM/WMConfiguration Pack

Purchasing

Published by Team of SAPConsultants at SAPTOPJOBS

Visit us at www.sap-topjobs.com

Copyright 2006-07@SAPTOPJOBS

All rights reserved. No part of this publication may be reproduced, stored in a

retrieval system, or transmitted in any form, or by any means electronic ormechanical including photocopying, recording or any information storage and

retrieval system without permission in writing from SAPTOPJOBS

http://www.sap-topjobs.com/




INDEX

1. Define Number Range ------------------------------------------------------------------ 3

2. Define Document Type ----------------------------------------------------------------- 5

3. Set Tolerance Limits for Price Variance ------------------------------------------ 9

4. Release procedure for purchase order------------------------------------------ 124.1 Edit Characteristic--------------------------------------------------------------- 13

4.2 Edit Class --------------------------------------------------------------------------- 194.3 Define Release Procedure for Purchase Orders ----------------------- 22

5. Define Screen layout at Document Level -------------------------------------- 30

6. Setup Stock Transport Order ------------------------------------------------------ 346.1 Define shipping data for plants --------------------------------------------- 35

6.2 Define checking rule ----------------------------------------------------------------- 38

6.3 Assign Delivery Type and Checking Rule ---------------------------------------- 406.4 Assign Document Type, One-step Procedure,…----------------------- 41

7. Contracts and Scheduling Agreement ------------------------------------------ 43

8. Price Determination in MM--------------------------------------------------------- 458.1 Define Access sequence-------------------------------------------------------- 47

8.2 Define condition type ----------------------------------------------------------- 51

8.3 Other condition types: --------------------------------------------------------- 58

8.4 Define Calculation Schema--------------------------------------------------- 70

8.5 Define Schema Group ---------------------------------------------------------- 75

8.6 Define Schema group for purchase organization --------------------- 77

8.7 Assign schema group to purchase organization ---------------------- 79

8.8 Define Schema Determination----------------------------------------------- 81

9. Maintain Account Determination ------------------------------------------------ 83



1. Define Number Range

BACKGROUND

This configuration setting enables us to define the numberranges for purchase orders. Number ranges are defineddirectly in the production system.

INSTRUCTIONS

Follow the Menu Path: IMG → Materials Management →

Purchasing → Purchase Order → Define Number Ranges

1. Click

2. Click



3. Click to add any new number range interval

4. Click

5. Click

Effect of this configuration

Number range maintained here will be referred in thedocument type of purchase Order.



2. Define Document Type

BACKGROUND

This configuration setting enables to define the documenttype.

Each purchasing document (RFQ, PR and PO) must have adocument type. Document type setting controls

• Create new document types

•

Define the item interval• Define allowed follow-on document types

• Assign document types to a number range group

• Define number range interval

• Choose type of number assignment (internal orexternal)

Standard document type defined by SAP is sufficient. We shalldiscuss the standard SAP document type.

INSTRUCTIONS


Purchasing → Purchase Order → Define Document Types

1. Click



2. Maintain the fields as explained below

Field Name Field description and valueKey identifying documenttype. E.g. NB

Description identifying thedocument type. E.g. StandardPurchase Order.

Steps between the line itemnumbers in the PO.

Internal Number rangeassignment. E.g. 45

External Number rangeassignment. E.g. 41

Field selection key definesattributes of the fields in thepurchase requisitiondocument. E.g. NBB

Control indicatordifferentiating between thedocument type.

Tick in this check boxindicates the details from thevendor master and info recordin to the PO. It will alsoupdate the LIS with vendordata.



Note: - This is applicable only for stock transport orders.

Leave the other fields as it is.

3. Select the document NB by pressing the grey box in theleft

4. Double click

Note: -Above screen shows the allowed item category for

purchase order with document type NB.

5. Select standard by clicking grey box in the left side.

6. Double click

7. Maintain the fields as explained below.



Field Name Field Description and Value

Document type of PR whichcan be converted to this typeof PO.

Description of the documenttype, automatically determined by the system.

Item category in the PRdocument type allowed to beconverted in to this PO type.

Tick in this check boxindicates that purchase orderitem must not contain

account assignment. This indicates the possibilitiesof using release order orreleases or delivery schedulefor a document.

Tick in this check box willindicate the user the usage of document type and itemcategory.

8. Click

9. Click till the main IMG screen is reached.


Document type configured here will be used while creating

the purchase requisition.



3. Set Tolerance Limits for Price Variance

BACKGROUND

This configuration setting enables to define the tolerance limitsfor price variance.

Tolerance limits check the price difference between thepurchase order and valuation price stored in the materialmaster.

INSTRUCTIONS


Purchasing → Purchase Requisitions → Set Tolerance Limitsfor Price Variance

1. Click

2. Click

3. Maintain the field as explained below

Field Name Field Description and value

Key identifying the tolerancekey. E.g. PE for price variance.

Lower Limit Checking of variance per unit.

Limit with 20% tolerancebetween PO and materialmaster moving average.

Upper Limit Checking of variance per unit.Limit with 10% toleranceetween PO and material



master moving average.

4. Click


Tolerance key will be assigned to the document type forpurchase Order.



When processing a Goods Receipt, the system checkswhether the unit price of a purchase order item differ fromthe moving average price of a material.



4. Release procedure for purchase order

BACKGROUND

This configuration setting enables to define the purchase orderrelease strategy with class and characteristics.

Steps involved in this are

• Create required characteristics on which release isto be performed.

• Create class of type 032 and attach thecharacteristics.

• Define release procedure

Let us try to understand each one of it in the followingsessions.



4.1 Edit Characteristic

BACKGROUND This configuration setting enables to define the characteristics. These characteristics are known as class characteristics. Todenote any property characteristics are used and it is assignedto the class.

Example 1:-Fat content, Protein, calcium can be the characteristics and itcan be assigned to the batch class 022.

Example 2:-Document type, Purchase organization can be thecharacteristics and it can be assigned to the Releaseprocedure class type 032.

Example 3:-Fuse type, fuse amp can be the characteristics for materialFUSE and it can be assigned to the material class type 001.

Let us try to create characteristic Net_Order_value relevant forpurchase order release.

INSTRUCTIONS


Purchasing → Purchase Order → Release Procedure for

Purchase Orders → Edit characteristics

1. Click

2. Enter characteristics. E.g. NET_ORDER_VALUE

3. Click to create new characteristic



4. Maintain the field as shown below

Field name Field description

Description of thecharacteristic. E.g. Total ordernet value

Status of the characteristic.E.g. Released



Data type to applicable to thischaracteristic. E.g. Currency format.

Indicate the number of characters.

Field indicating the currency.E.g. INR

Multiple value assignment ispossible if this radio button isselected.

Any interval range can beassigned as a value to thischaracteristic. E.g. 1 - 5000

Click

Language Enter the language in whichthe description is to bemaintained. E.g. EN toindicate English.

Description Description of the Language.E.g. Total Order value

5. Click

6. Maintain value as shown below

7. Click

8. Maintain the value as shown below.



Table name indicate the table from which the value is to betaken.

Field name indicates the field in the table from where thevalue is to be taken during processing.

9. Click

Note: - If the table name and field name are maintained,system will pick up the values from this table and fieldcombination.

10. Click

11. Click



Other details like decimal places, template are filledautomatically with the table and field reference.

12. Click

Note: - Similarly other characteristics can be created.Following are the SAP standard characteristics available.




This characteristic will be attached in the class of type 032(Release procedure)



4.2 Edit Class

BACKGROUND

This configuration setting enables to define the class.

Class is uniquely identified by the class type for differentpurposes.

Example:-

• 022 class type refers to batch class

• 032 class type refers to release procedure class

• 001 class type refers to material class

Each class will contain the relevant characteristics required.

INSTRUCTIONS



Purchase Orders → Edit class

1. Click

2. Enter class name. E.g. PO_RELEASE



Maintain the field values as explained below

Field Name Field Description and Value

Name of the class. E.g.PO_RELEASE

Type uniquely identifying theclass. E.g. 032 to indicateclass to be used for releaseprocedure.

Description of the class. E.g.PO Release strategy

Status of the class. E.g.Released.

3. Click

4. Enter all the characteristics to be used with this class.



5. Click


This class will be used to define the release strategy.

Note: - Let’s discuss with the SAP standard class. Howeverit is explained for clear understanding of creating class andcharacteristics.



4.3 Define Release Procedure for Purchase Orders

BACKGROUND

This configuration setting enables to define the releasestrategy.

Steps involved in release strategy are

Define release group

Define release code and attach with release group

Define release indicator

Define release strategy for release group and assignrelease codes

INSTRUCTIONS



Purchase Orders → Define Release Procedure for purchaseOrders

1. Click



2. Double click

3. Click to create new release group

4. Enter Release group. E.g. PO

5. Enter class. E.g. FRG_EKKO

6. Enter description. E.g. PO> 20000INR

7. Click

8. Click

9. Click two times.

10. Double click

11. Click

12. Enter Group. E.g. PO



13. Enter Release code. E.g. R1

14. Enter Description. E.g. Head procurement

15. Similarly create release codes. E.g. P1 to indicate

initial release which is changeable.

16. Click two times

17. double click

18. Click

19. Maintain the filed values as explained below

Field name Field description and value

Indicator to identify therelease indicator. E.g. N

Tick in this check boxindicates the PO is ready forfurther transmission.

Indicates whether the PO ischangeable after release. E.g.

1 to indicate it as nonchangeable.

Description for release code.E.g. PO Non changeable

20. Click

21. Click two times

22. Double click

23. Click

24. Maintain the fields as explained below



Field Name Field description and value

Key identifying the releasegroup. Enter the already created release group. E.g. PO

Key identifying the release

strategy. E.g. IN to indicaterelease strategy for plantIND6.Maintain description also.

Release codes. Enter the release codes. E.g.R1 which is the code createdfor release group PO.P1 for initial release which ischangeable.

25. Click

26. Click the check boxes as shown below



27. Above screen indicates that P1 must release itbefore R1 and R1 can release only after P1 release.

28. Click

29. Click

30. Maintain release indicators as shown below

31. Click



32. Click

33. Maintain the classification value on which therelease is to be performed.

34. Click

35. Click

36. Click

37. Click



38. Click on

39. Click

40. Click on

41. Click

42. Click



43. Click

44. Click

45. Click two times

46. Click to reach main IMG menu


This release strategy will be applicable to the document

type, purchase organization and value combination.



5. Define Screen layout at Document Level

BACKGROUND

This configuration setting enables to define the screenlayout. Screen layout enables to define fields as mandatory,optional or hide.

Under a four digit key the screen layout is defined and thiskey is attached to the relevant document type.

Let us try to understand the screen layout key NBF which isattached to the document type NB.

INSTRUCTIONS


Purchasing → Purchase Order → Define Screen Layout at

Document Level

1. Click

2. Click to create new keys.

Note: - Let us discuss the SAP standard key NBF.

3. Select NBF

4. Click



5. Double click on



6. Click the appropriate check box to make the field asrequired entry, optional entry or only display.

7. Click

8. Repeat the above steps till you complete all the fieldscontrol setting.

Note: - SAP Standard setting is sufficient. However it isexplained here for your understanding.

9. Click

10. Click




Screen layout defined here can be referred in the document

type. Screen layout key NBF is referred to the document typeNB.



6. Setup Stock Transport Order

Stock transport order is used to transfer materials between

plants.

Stock transport order does not contain any value.

Stock transports are performed between two companies whichare under the same company code.

Steps involved are

Defining shipping data Creating and defining checking rule Assigning delivery type and checking rule Assign document type

Let’s discuss the steps one by one.



6.1 Define shipping data for plants

BACKGROUND

This configuration setting enables to define the shipping data.

Shipping data contains

Customer name for the receiving plant

Sales organization data

INSTRUCTIONS


Purchasing → Purchase Order → Set up Stock Transport

Order → Define Shipping Data for Plants

1. Select Plant. E.g. IND6

2. Click



3. Maintain the following field data

Field name Field description

Code identifying thereceiving plant. Customermaster record must havebeen created for thisreceiving plant. Mainly used in inter company

stock transfer.Sales organization towhich the receiving plantis assigned.

Distribution channel of the receiving plant.



Division of the abovesales organization forbilling.

Language in which textsare to be printed and

displayed.

4. Click


This information will be used during STO process.



6.2 Define checking rule

BACKGROUND

Combination of checking rule and availability check willperform the availability of component at appropriatetransaction.

Creation of checking rule and defining checking rule isexplained in the MRP CD. Here only the screen shot for STOchecking rule is displayed.

INSTRUCTIONS



Order → Define checking rule

1. Click




When creating STO, system will perform the checkingaccording to the setting done here.



6.3 Assign Delivery Type and Checking Rule

BACKGROUND

This configuration setting enables to define checking rule fordelivery type.

When creating the document, checking rule assigned here willbe used to perform availability check to this order type.

INSTRUCTIONS



Order → Assign Delivery Type and Checking rule

1. Click

2. Click

3. Maintain the following fields

Field name Field description and Value

Key identifying the documenttype. E.g. UB to indicate stocktransport order.

Supplying plant. E.g. IND7

Delivery type to which the

checking rule is to beperformed. E.g. UL – delivery for stock transfer

Checking rule. E.g. A

4. Click



6.4 Assign Document Type, One-step Procedure,

BACKGROUND

This configuration setting enables to define checking rule fordelivery type.

When creating the document, checking rule assigned here willbe used to perform availability check to this order type.

INSTRUCTIONS

Follow the Menu Path: IMG → Materials Management →Purchasing → Purchase Order → Set up Stock Transport

Order → Assign Document type, One-step procedure, Underdelivery Tolerance.

1. Click

2. Click

3. Enter Supplying Plant. E.g. IND6

4. Enter receiving plant. E.g. IND7

5. Enter Order type. E.g. UB to indicate stock transportorder.

6. - Tick in this check box indicates the STO will beperformed in one step. E.g. GR is posted in receivingplant at the same time goods issue is posted insupplying plant. E.g. Leave this blank

7. Click

8. Click




When creating STO, system will perform as per the setting

here.



7. Contracts and Scheduling Agreement

Contract and scheduling agreements are similar to that of order.

Contract:- It is a long term purchasing agreement withvendor.

Scheduling Agreement :- it is a schedule released againstpurchase order.

IMG setting for the above are similar to that of PR and PO.

Setting involved are:

• Defining number range

• Defining document type

• Defining release procedure

• Defining screen layout at document level.

Since the settings are similar it is not explained here onceagain.

IMG menu path screen shot is shown here for your reference.





8. Price Determination in MM

BACKGROUND

This configuration setting enables to define pricing conditionsand pricing procedure.

In a purchasing document, it is essential to maintain thedetails of price brake up.

Example: -

Basic price 20.00 per unitLess discount 10% 2.00Price after discount 18.00Add Taxes on price after discount 4% 0.72Price after tax 18.72Add Freight 5% on price after discount 0.90

Net effective price 19.62

In SAP each line item is defined through the condition typeand it is arranged inside the pricing procedure (calculationschema) to perform the desired calculation.

Steps involved in calculation schema definitions are

• Define condition types

• Define calculation schema (pricing procedure)

• Define schema group for vendor / purchase organization.

• Assign schema groups with calculation schema



• Assign purchase organization schema group to therequired purchase organization in the IMG.

• (Note: - this way purchase organization specificcalculation schema can be assigned.)

• Assign the vendor schema group in the vendor masterpurchasing data screen.

• Note: - this way specific calculation schema for specificvendors can be assigned.

With the above settings, when PO is prepared for any vendor,the right pricing procedure will be determined.

Before we discuss in details, let us look at the PO with pricingprocedure.

Hope now you are ready to receive more on pricing procedure.Let us jump in to the details now.



8.1 Define Access sequence

BACKGROUND

This configuration setting enables to define Access sequence.

Access sequence is defining the sequence of priority to searchor pickup the data from the predefined tables. These tablesare known as condition table.

One can define own table according to the business

requirements.

INSTRUCTIONS


Purchasing → Conditions → Define Price Determination

Process → Define Access Sequences

1. Click

2. Click (it is a cross client setting)

3. Select any access sequence (e.g. 0002) to copy. Note:- It

can be created by clicking

4. Click

5. maintain the fields as explained below

Field Name Field description and value

Key identifying the accesssequence. E.g. ZIN6

Description of the access



sequence Key. E.g. Gross pricewithout plant.

Category for access sequence.E.g. Leave it blank

6. Click

7. Click

8. Click to add new table as the first search withaccess no.3

9. Maintain the fields as explained below.


Key defining the access

priority. E.g. 3 Table identification. E.g. 84

This is used to skip thecondition or to access furtherconditions. Leave it blank.

Tick in this check box will



stop further searching afterfetching the condition record.E.g. Tick this check box

10. Click

11. Select the access sequence with no.3 by clicking thegrey box in the left

12. Double click

13. Click

14. Click



15. Click



8.2 Define condition type

BACKGROUND

This configuration setting enables to define Condition type.

Conditions are two types.

• Time dependant

• Time Independent

Time dependant: -

Validity period and scale can be definedUpper limit and lower limit for price range can be definedAlways used in contracts and info record

Time Independent: -No validity period and scale are applicable

Condition type contains controls onPrice basis

Calculation typeRounding the valueChanges to the condition type in the POValidity

Note: - Let us try to understand the SAP standard conditiontype PB00. Then we shall discuss few more condition typesand try to understand the difference between them.

INSTRUCTIONS



Process → Define Condition type.



1. Click

2. Click



3. Maintain the following fields as explained below


Key identifying the conditiontype.

Key classifying the condition.E.g. enter B to identify as

price.Key identifying the calculationtype for the condition type.E.g. enter A to indicate % basecalculation.

Key categorizing the conditiontype. E.g. H to indicate thecondition category as basicprice type.

Used to round off thecondition value. Leave itblank.

Normally used in variantconfiguration with BOM.Leave it blank.

Tick in this check box



indicates that the systemcalculates the base price formore than one item in thedocument. But materials mustbelong to the same material

group. It cumulates thematerial belong to the samegroup and check with thescale quantity for furtheraction.

If this check box is ticked,system checks the conditionvalue at header level andcompares it with the total of

the condition value at itemlevel.

Routine used along with thegroup condition

Kind of changes allowed at POlevel for this condition type.Following are the allowedentries.

Tick in this check boxindicates that this is a headerlevel condition.

Tick in this check boxindicates that this is a item

level condition. Tick in this check box willallow the condition type to bedeleted from the PO

Tick in this check box will

enable the change of amountor % in the PO.



Tick in this check box willenable the change value in thePO.

Tick in this check box willenable the change conversion

factor in the PO. Tick in this check box willenable the change of calculation type in the PO.

Validity from date

Validity upto date

Pricing procedure in whichthis condition type will beused.

Control on how systemoperates when the conditiontype is deleted.

Indicates how the systemdetermines the basis for scale.E.g. Price or quantity or valuebasis.

Indicates how the scale valueis to be maintained.

Indicates maintenance of Scale value or % rate.

Formula to determine thescale base value.

UOM to be used along withgroup condition. Systemproposes the UOM whenmaintaining the conditionrecord for group conditions.

Tick in this check box willconvert the condition valueinto the document currency before it multiples thequantity and value fromcondition record.

Tick in this check box



indicates that the systemposts the amount derived fromthis condition into thefinancial accounting asaccruals.

Condition with this tickappears as a statisticalcondition in the document.

Relevant for internal costing.Leave it blank

Related to internal costingcondition. Leave it blank

Used in promotion. Leave itblank.

Used with variantconfiguration. Leave it blank

It is used when sales andcondition quantity UOM aredifferent to that of Base UOMof material.

Tick in this check box willautomatically exclude thediscounts that are proposed

during pricing.Controls on accountdetermination processing forthe condition type.

Related to sales pricecalculation. Leave it blank.

Related to sales pricecalculation. Leave it blank.

Text determination procedureused with sales. Leave itblank.

Text determination procedureused with sales. Leave itblank.

4. Click




Condition type defined here is used in the calculation schema

(pricing procedure).

Calculation Schema (Pricing procedure)



8.3 Other condition types: -

BACKGROUND

We are clear about the condition type. We have discussed only PB00 condition type. Let us have a look of other conditiontypes used in the pricing procedure ZIN006.

As explained above, required condition types are to be created.

INSTRUCTIONS



Process → Define Condition Types

1. Click

2. Double click



3. Click

4. Enter PBXX

5. Click

6. Double click on PBXX condition type



7. Click

8. Repeat steps 3 to 6 to view the next condition type

R000





YNST





FRA1





FRB1





FRC1





8.4 Define Calculation Schema

BACKGROUND

This configuration setting enables to define the calculationschema (pricing procedure).

Let us try to create the pricing procedure which we discussedin the beginning.

INSTRUCTIONS



Process → Define Calculation Schema

1. Click

2. Click


Field Name Field description and Value

Key identifying the pricingprocedure name. e.g. ZIN006

Description of the pricingprocedure. E.g. Price-dis+tax+Freight=netprice

4. Click

5. Select YIN006 line by clicking the grey box in the left



6. Double click

7. Click



Number identifying thesequence of the conditionwithin a procedure. E.g. 10

Access number or Counternumber inside that step.System will approachaccording to this sequence.

E.g. 1 if there are morecounter for a step, else leave itblank.

Condition type. E.g. PB00 toindicate the gross price.

From reference step.When it is required to apply discount or to add total, it ispossible to refer from and to

condition types which are tobe added.Normally used in the discountor surcharge or tax conditiontypes or to add the lines.

To reference step.When it is required to apply discount or to add total, it ispossible to refer from and to

condition types which are tobe added.Normally used in the discountor surcharge or tax conditiontypes or to add the lines.

Tick in this check boxindicates that this condition



types will be included in thepricing procedure manually.

Tick in this check box indicatethat this condition ismandatory.

Tick in this check boxindicates that this conditionvalue is only for statisticalpurpose.

Control on how to print thecondition.

Field indicator to store thesubtotal of this condition type.

It is possible to access the

condition type if certainpredefined requirements aremet. Through predefinedfunction module thoseconditions are built as“Requirement number”.

Alternative formula withcalculation type to determinecondition.

Alternate formula to find thecondition base value.

Key identifying the G/L account. E.g. Packing chargescan be posted in a differentGL account.Discuss with accounts beforemaintaining this field.

Key identifying the GL account to post the accrualsor provisions.Discuss with accounts beforemaintaining this field.



9. Maintain all other condition as explained above. Aftermaintaining the conditions, pricing procedure look likeas shown below.

10. Let us try to understand the above pricingprocedure.

PB00 / PBXX: -

a. PB00 / PBXX condition types are the mandatory condition must be associated with the pricingprocedure.

b. PB00 condition type is to determine the priceautomatically through info record.c. PBXX condition type is to enter the price manually if not

found through info record.d. Note: - Requirement field 5 controls the above function.

This is the use of requirement.e. R000 is for discount on gross price. Discount is to be

applied on gross price. i.e from step number 10 to Step20.

f. Step 40 is to total the price from line number 10 to 25.It will be displayed for statistical purpose.

g. YNST condition type is to add the tax to the value afterdiscount. I.e. to the line number 40.

h. Step 60 is to display the price including tax. I.e. priceafter discount plus taxes. I.e. from step number 40 to50



i. FRA1 / FRB1 / FRC1 condition in step number 70 withaccess number 1, 2 and 3 respectively are to indicatethe different types of freight charges. Note: - It isassumed that the different types of freight will beapplied at different times, hence all the three types are

maintained. j. Freight charges are paid not paid to the PO vendor,

hence these amounts are to be posted to the differentaccount. Through accruals key the right accounts aredetermined to this condition type.

k. Step 100 adds the price with tax and freight charges toarrive at the effective price. I.e. from line 60 to 70

11. Click


Pricing procedure created here will be used in the PO.



8.5 Define Schema Group

BACKGROUND

This configuration setting enables to define the schema groupfor vendor.

Schema group helps in determining the pricing procedure forvendor.

Schema group is the link between the pricing procedure andvendor master.

INSTRUCTIONS



Process → Define Schema Group

1. Click



2. Double Click

3. Click



Key identifying the schema

group. E.g. I6Description of the key. E.g.Simple pricing

5. Click


Schema group defined here will be used to assign with vendormaster and with pricing procedure.



8.6 Define Schema group for purchase organization

BACKGROUND

This configuration setting enables to define the schema groupfor purchase organization.

Schema group helps in determining the pricing procedure forpurchase organization.

Schema group is the link between the pricing procedure andpurchase organization.

INSTRUCTIONS




1. Click



2. Double Click

3. Click



Key identifying the schemagroup for purchaseorganization. Note: - any fourdigit key can be maintainedhere. E.g. IND6

Description of the key. E.g.Key for IND6

5. Click


Schema group defined here will be used to assign withpurchase organization and with pricing procedure.



8.7 Assign schema group to purchase organization

BACKGROUND

This configuration setting enables to establish the linkbetween the schema group and purchase organization.

Schema group helps in determining the pricing procedure forpurchase organization.

INSTRUCTIONS




1. Click

2. Double Click



3. Enter the schema group against the purchaseorganization.

4. Click .


Schema group defined here for the purchase organization willbe used when raising the PO in this purchase organization.



8.8 Define Schema Determination

BACKGROUND

This configuration setting enables to establish the linkbetween the schema groups and pricing procedure.

Pricing procedure determines the price basis during POcreation.

INSTRUCTIONS



Process → Define Schema Determination

1. Click

2. Double click

3. Click





Key identifying the purchase

organization schema group.E.g. IND6

Key identifying the vendorschema group. E.g. I6

Key identifying the pricingprocedure. E.g. ZIN006

5. Click


Relation between schema groups and pricing procedure is thebasis to determine the right pricing procedure duringpurchase order creation.



9. Maintain Account Determination

BACKGROUND

This configuration setting enables to define the accountdetermination.

Account determination is used to book the purchases againstany specific accounts.

It is defined by the Accounts team. Here the screen shots are

displayed for your reference.

INSTRUCTIONS


Purchasing → Account Assignment → Maintain AccountAssignment Categories

1. Click



2. Double click to view the details

Note: - To create new entries click




Tick in this check boxindicates account assignmentis changeable during GR orinvoice receipt.

Account assignmentchangeable only at Invoice



Receipt (IR).

Tick in this check boxindicates that the accountassignment is derived fromthe GL account

Tick in this check boxindicates that the delivery costassociated with the accountassigned PO will be posted toa separate GL account.

Goods receipt is linked to thepurchase order item. GR ispossible to this accountassigned PO

Tick in this check boxindicates that GR ismandatory.

Key indicating theconsumption posting.

Key used for accountdetermination. Prime key todetermine the GL account.

Indicates the multiple account

assignment.Indicates the stock typeassociated with this accountassignment category.

Indicates, GR for this items isnot to be valuated.

Indicates, GR is mandatory and it must be non valuated.

Indicates the distribution of

quantity and value formultiple account assignmentcategory.

Indicates how the partialinvoice is distributed in caseof multiple accountassignment.



Indicates, PO item is linked toinvoice.

Indicates invoice receipt ismandatory.

Below shown field groups are to be made required entry,optional entry, and display or hidden according to thebusiness requirements.

3. Click to view next page

4. Click to view next page



5. Click


Account assignment categories defined here will be used in thePO.

To learn about more of our best-selling SAP packs visit us atwww.sap-topjobs.com



MM-PUR - SapTopjobs Purchasing Configuration

Documents