Sap MM-configuration-step-by-step-guide

159,640 views

Published on

SAP MM CONFIGURATION GUIDE

Published in: Education
134 Comments
170 Likes
Statistics
Notes
No Downloads
Views
Total views
159,640
On SlideShare
0
From Embeds
0
Number of Embeds
1,172
Actions
Shares
0
Downloads
17,940
Comments
134
Likes
170
Embeds 0
No embeds

No notes for slide

Sap MM-configuration-step-by-step-guide

  1. 1. MM – Configuration Documentation
  2. 2. Table of Contents1PURPOSE OF THE DOCUMENT................................................................................................................5ENTERPRISE STRUCTURE - DEFINITION...............................................................................................61.1 DEFINE VALUATION LEVEL ...........................................................................................................................61.2 DEFINE PLANT...............................................................................................................................................61.3 MAINTAIN STORAGE LOCATION....................................................................................................................71.4 MAINTAIN PURCHASING ORGANIZATION.......................................................................................................8ENTERPRISE STRUCTURE ASSIGNMENTS.............................................................................................91.5 ASSIGN PLANT TO COMPANY CODE..............................................................................................................91.6 ASSIGN PURCHASING ORGANIZATION TO COMPANY CODE............................................................................91.7 ASSIGN PURCHASING ORGANIZATION TO PLANT.........................................................................................101.8 ASSIGN STANDARD PURCHASING ORGANIZATION TO PLANT.......................................................................11GENERAL LOGISTICS ...............................................................................................................................121.9 ASSIGN FIELDS TO FIELDS SELECTION GROUPS..........................................................................................121.10 MAINTAIN FIELD SELECTION FOR DATA SCREENS...................................................................................121.11 MAINTAIN COMPANY CODES FOR MATERIALS MANAGEMENT................................................................131.12 DEFINE ATTRIBUTES OF MATERIAL TYPES...............................................................................................141.13 DEFINE NUMBER RANGES FOR EACH MATERIAL TYPES............................................................................161.14 DEFINE ATTRIBUTES OF SYSTEM MESSAGES.............................................................................................171.15 DEFINE MATERIAL GROUPS.......................................................................................................................171.16 DEFINE EXTERNAL MATERIAL GROUPS....................................................................................................181.17 INITIALIZE PERIOD.....................................................................................................................................18MATERIALS MANAGEMENT – CONSUMPTION BASED PLANNING.............................................201.18 ACTIVATE MRP FOR MRP AREAS............................................................................................................201.19 DEFINE MRP AREAS.................................................................................................................................20MATERIALS MANAGEMENT – PURCHASING......................................................................................211.20 DEFINE ATTRIBUTES OF SYSTEM MESSAGES............................................................................................211.21 DEFINE PURCHASING VALUE KEYS...........................................................................................................211.22 ENTRY AIDS FOR ITEMS WITHOUT A MATERIAL MASTER........................................................................221.23 CREATE PURCHASING GROUPS..................................................................................................................231.24 DEFINE DOCUMENT TYPES (RFQ/QUOTATION)........................................................................................231.25 DEFINE TEXT TYPES FOR HEADER TEXTS (RFQ/QUOTATIONS)...............................................................251.26 DEFINE COPYING RULES FOR HEADER TEXTS (RFQ/QUOTATIONS)..........................................................251.27 DEFINE DOCUMENT TYPES (PURCHASE REQUISITIONS).............................................................................261.28 RELEASE PROCEDURE WITH CLASSIFICATION (PURCHASE REQUISITIONS)...............................................271.29 DEFINE NUMBER RANGES (PURCHASE ORDERS)......................................................................................321.30 DEFINE DOCUMENT TYPES (PURCHASE ORDERS).....................................................................................331.31 SET TOLERANCE LIMITS FOR PRICE VARIANCE........................................................................................351.32 RELEASE PROCEDURE FOR PURCHASE ORDERS........................................................................................361.33 DEFINE SCREEN LAYOUT AT DOCUMENT LEVEL......................................................................................391.34 DEFINE TEXT TYPES FOR HEADER TEXTS (PURCHASE ORDERS)..............................................................401.35 DEFINE COPYING RULES FOR HEADER TEXTS (PURCHASE ORDER)..........................................................411.36 DEFINE TEXT TYPES FOR ITEM TEXTS (PURCHASE ORDERS)...................................................................411.37 DEFINE COPYING RULES FOR ITEM TEXTS (PURCHASE ORDER)................................................................421.38 DEFINE DOCUMENT TYPES (CONTRACTS).................................................................................................431.39 DEFINE SCREEN LAYOUT AT DOCUMENT LEVEL (CONTRACTS)...............................................................451.40 DEFINE TEXT TYPES FOR HEADER TEXTS (CONTRACTS)..........................................................................46
  3. 3. 1.41 DEFINE COPYING RULES FOR HEADER TEXTS (CONTRACTS)....................................................................471.42 DEFINE TEXT TYPES FOR ITEM TEXTS (CONTRACTS)...............................................................................471.43 DEFINE COPYING RULES FOR ITEM TEXTS (CONTRACT)...........................................................................471.44 DEFINE EXTERNAL CONFIRMATION CATEGORIES.....................................................................................491.45 DEFINE INTERNAL CONFIRMATION CATEGORIES......................................................................................491.46 SET UP CONFIRMATION CONTROL............................................................................................................501.47 DEFINE ACCESS SEQUENCE.......................................................................................................................511.48 DEFINE CONDITION TYPES........................................................................................................................521.49 DEFINE CALCULATION SCHEMA................................................................................................................541.50 DEFINE SCHEMA GROUP............................................................................................................................561.51 DEFINE SCHEMA DETERMINATION............................................................................................................571.52 DEFINE TRANSACTION EVENT KEYS..........................................................................................................591.53 MAINTAIN CONDITION TABLE...................................................................................................................601.54 DEFINE GRID FOR QUANTITY VARIANCES................................................................................................611.55 DEFINE GRID FOR DELIVERY DATE VARIANCE.........................................................................................611.56 DEFINE WEIGHING KEYS............................................................................................................................611.57 DEFINE CRITERION (VENDOR EVALUATION).............................................................................................621.58 DEFINE SCOPE OF LIST (VENDOR EVALUATION)......................................................................................631.59 MAINTAIN PURCHASING ORGANIZATION DATA........................................................................................631.60 DEFINE PERMISSIBLE PARTNER ROLES PER ACCOUNT GROUP.................................................................651.61 DEFINE PARTNER SCHEMAS (VENDOR MASTER)......................................................................................661.62 ASSIGN PARTNER SCHEMAS TO ACCOUNT GROUPS..................................................................................671.63 DEFINE PARTNER SCHEMAS (PURCHASING DOCUMENTS)........................................................................671.64 ASSIGN PARTNER SCHEMAS TO DOCUMENT TYPES..................................................................................68MATERIALS MANAGEMENT – EXTERNAL SERVICES MANAGEMENT......................................701.65 DEFINE SERVICE CATEGORY.....................................................................................................................701.66 DEFINE NUMBER RANGES.........................................................................................................................701.67 DEFINE NUMBER RANGE FOR SERVICE ENTRY SHEETS............................................................................711.68 DEFINE ATTRIBUTES OF SYSTEM MESSAGES.............................................................................................71MATERIALS MANAGEMENT – INVENTORY MGMT. & PHYSICAL INVENTORY.....................731.69 PLANT PARAMETERS..................................................................................................................................731.70 DEFINE NUMBER ASSIGNMENT FOR ACCOUNTING DOCUMENTS..............................................................731.71 DEFINE NUMBER ASSIGNMENT FOR MATERIAL AND PHYSICAL INVENTORY DOCUMENTS......................761.72 DEFINE NUMBER ASSIGNMENT FOR RESERVATIONS.................................................................................771.73 FIELD SELECTION FOR GOODS MOVEMENT/INITIAL HEADER SCREENS...................................................771.74 FIELD SELECTION FOR MIGO....................................................................................................................781.75 FIELD SELECTION PER MOVEMENT TYPE..................................................................................................791.76 SETTINGS FOR TRANSACTIONS AND REFERENCE DOCUMENTS.................................................................801.77 CREATE STORAGE LOCATION AUTOMATICALLY.......................................................................................811.78 SET MANUAL ACCOUNT ASSIGNMENT......................................................................................................821.79 DEFINE SCREEN LAYOUT...........................................................................................................................821.80 MAINTAIN COPY RULES FOR REFERENCE DOCUMENTS............................................................................831.81 SET UP DYNAMIC AVAILABILITY CHECK..................................................................................................841.82 GENERATE PHYSICAL INVENTORY DOCUMENTS FOR GOODS MOVEMENTS.............................................871.83 CHECK TOLERANCE LIMITS.......................................................................................................................871.84 CREATE STORAGE LOCATIONS AUTOMATICALLY.....................................................................................881.85 SET MANUAL ACCOUNT ASSIGNMENT......................................................................................................891.86 DEFINE SCREEN LAYOUT...........................................................................................................................901.87 MAINTAIN COPY RULES FOR REFERENCE DOCUMENTS............................................................................911.88 SET DYNAMIC AVAILABILITY CHECK.......................................................................................................921.89 SET “DELIVERY COMPLETED” INDICATOR................................................................................................931.90 SET EXPIRATION DATE CHECK..................................................................................................................94
  4. 4. 1.91 CREATE STORAGE LOCATION AUTOMATICALLY FOR AUTOMATIC MOVEMENTS.......................................941.92 SET MANUAL ACCOUNT ASSIGNMENT FOR AUTOMATIC MOVEMENTS.......................................................961.93 DEFINE SCREEN LAYOUT FOR AUTOMATIC MOVEMENTS..........................................................................971.94 GENERATE PHYSICAL INVENTORY DOCUMENTS FOR GOODS MOVEMENTS.............................................971.95 DEFINE DEFAULT VALUES FOR RESERVATIONS........................................................................................981.96 MAINTAIN COPY RULES FOR REFERENCE DOCUMENTS............................................................................991.97 SET DYNAMIC AVAILABILITY CHECK FOR RESERVATIONS......................................................................991.98 DEFAULT VALUES FOR PHYSICAL INVENTORY.......................................................................................1021.99 RECORD REASONS FOR GOODS MOVEMENTS..........................................................................................1031.100 COPY, CHANGE MOVEMENT TYPES.......................................................................................................103MATERIALS MANAGEMENT – VALUATION AND ACCOUNT ASSIGNMENT...........................1051.101 SPLIT VALUATION..................................................................................................................................1051.102 CONFIGURE SPLIT VALUATION..............................................................................................................105
  5. 5. 1 Purpose of the DocumentThis document captures in detail the steps required to configure the SAP system to meet thebusiness requirements as envisaged in the ITZ Process Definition Documents of Business Blueprintphase. The configuration steps have mappings to the corresponding menu path where theconfiguration has been done in the IMG (Implementation Guide). The descriptive procedure alongwith rationale of all configurations is also provided.The documentation provides visibility to all project teams members on the proposed systemsettings and changes. This is very important due to the highly integrated nature of SAP. All futurechanges or updates to the system should be done based on this document and the documentationupdated accordingly.This customisation manual outlines the way, how the Materials Management Module has beenconfigured for ITZ as per the requirement of their business scenarios and should be seen inconjunction with the KDS document.This document explains the settings done i.e. Configurations done for the present implementationonly and not all the nodes available.Other Nodes are kept as standard (as delivered by SAP)
  6. 6. Enterprise Structure - Definition1.1 Define Valuation LevelMenu path Implementation Guide for R/3 Customizing (IMG) → Enterprise Structure → Definition → Logistics general → Define Valuation LevelTransaction Code OX14Configuration Here we specify the level at which material stocks are valuated. WeDescription have used the Plant level since the application component Production Planning (PP) and Costing are being used. • Depending on the valuation level chosen, accounting data (in particular the valuation price) is maintained for each plant or for each company code in the material master record. • If material stocks are valuated at company code level, all plant stocks of a material are managed in a joint stock account for each company code. • If material stocks are valuated at plant level, the material stocks for each plant can be managed in different accounts. We can define a separate account determination for each plant.1.2 Define PlantMenu path Implementation Guide for R/3 Customizing (IMG) → Enterprise Structure → Definition → Logistics general → Define, copy, delete, check plantTransaction Code SPROConfiguration As a part of the Logistics Organizational Structure, Plants are defined inDescription SAP. The ‘Plant’ is an operating area or a branch or a location within a company. Each Plant is assigned to a single company code. A company code can have several Plants. In case of ITZ Pvt. Ltd., the various Plants are assigned to a each company code. Configuration of One Plant is depicted here, (for list of all please refer to MM KDS Document)
  7. 7. 1.3 Maintain Storage LocationMenu path Implementation Guide for R/3 Customizing (IMG) → Enterprise Structure → Definition → Materials Management → Maintain Storage LocationTransaction Code OX09Configuration A storage location is the place where stock is physically kept within a plant.Description There may be one or more storage locations within a plant. A storage location has the following attributes: • A storage location has a description and at least one address. • It is possible to store material data specific to a storage location. • Stocks are managed only on a quantity basis and not on a value basis at storage location level. • Physical inventories are carried out at storage location level. Configuration of Storage Locations under One Plant is depicted here, (for list of all please refer to MM KDS Document)
  8. 8. 1.4 Maintain purchasing organizationMenu path Implementation Guide for R/3 Customizing (IMG) → Enterprise Structure → Definition → Materials Management  Maintain Purchasing OrganizationTransaction Code SPROConfiguration At this node we configure the Purchasing Organization .The purchasingDescription organization is the highest level of aggregation (after the organizational unit "client") for purchasing statistics. In case of ITZ One single Purchase Organization is created as under :
  9. 9. Enterprise Structure Assignments1.5 Assign Plant to Company CodeMenu path Implementation Guide for R/3 Customizing (IMG) → Enterprise Structure → Assignment → Logistics general → Assign Plant to Company CodeTransaction Code SPROConfiguration A Plant needs to be assigned to one of the Company Codes, the relationDescription is always one to one i.e. One Plant can be assigned to only one company code All the plants can’t be shown here(for complete list refer MM KDS document)1.6 Assign purchasing organization to company codeMenu path Implementation Guide for R/3 Customizing (IMG) → Enterprise Structure → Assignment → Logistics general → Assign purchasing organization to company codeTransaction Code SPROConfiguration In this node we assign the Purchasing Organization to the companyDescription code under which it works. In case of ITZ the Purchasing Organization is Central, so it is not assigned to any Company Code
  10. 10. 1.7 Assign purchasing organization to PlantMenu path Implementation Guide for R/3 Customizing (IMG) → Enterprise Structure → Assignment → Logistics general → Assign purchasing organization to PlantTransaction Code SPROConfiguration In this step we assign purchasing organizations to the plants for whichDescription they are responsible. In case of ITZ since it operates with Centralized Purchasing Org. we have assigned the Purchasing Org. to all the plants defined as of now
  11. 11. 1.8 Assign standard purchasing organization to plantMenu path Implementation Guide for R/3 Customizing (IMG) → Enterprise Structure → Assignment → Logistics general → Assign standard purchasing organization to plantTransaction Code SPROConfiguration If several purchasing organisations procure for a certain plant, we canDescription define one of them as the standard purchasing organization for the transactions "pipeline procurement", "consigmnent" and "stock transfers". In source determination for stock transfers and consignent, the system automatically utilizes this standard purchasing organization. In the case of goods issues of pipeline materials, the purchasing info records of the standard purchasing organization are read. In ITZ, we have not defined this Setting as we are using single Purchasing Organisation
  12. 12. General Logistics1.9 Assign Fields to Fields Selection GroupsMenu path Implementation Guide for R/3 Customizing (IMG) → Logistics - General  Material Master  Field Selection Assign Fields to Fields Selection GroupsTransaction Code OMSRConfiguration Assignment of Material Master Fields is required to define whether aDescription field is hidden or displayed, or whether an entry is mandatory or optional in material master maintenance, it is always advisable to work with Standard SAP settings, but for few business requirement some assignments are changed to new field selection groups defined as per reserved name space. in case of ITZ, some of the list of changed entries is as given below: Field Name Description Changed Field Grp MVKE-MVGR1 Material group 1 211 MVKE-MVGR2 Material group 2 211 MVKE-MVGR3 Material group 3 2111.10 Maintain Field Selection for Data ScreensMenu path Implementation Guide for R/3 Customizing (IMG) → Logistics - General  Material Master  Field Selection Maintain Field Selection for Data ScreensTransaction Code OMS9Configuration In this step we define the nature of a Field belonging to a particular FieldDescription Selection Group wrt the Screen Reference of a Material Type. Steps involved are : • Selecting the field selection group. • Select the field selection option (hide, display, required entry, or Optional entry) for each field reference as required.
  13. 13. 1.11 Maintain Company Codes for Materials ManagementMenu path Implementation Guide for R/3 Customizing (IMG) → Logistics - General  Material Master  Basic Settings Maintain Company Codes for Materials ManagementTransaction Code OMSYConfiguration This activity is done for making a Company Code relevant for materialsDescription Management and to define the starting posting period This is a prerequisite for creating a Material Master
  14. 14. 1.12 Define Attributes of Material TypesMenu path Implementation Guide for R/3 Customizing (IMG) → Logistics - General  Material Master  Basic Settings Material Types Define Attributes of Material TypesTransaction OMS2CodeConfiguratio Material type is analogous to the family of a material master; all the importantn attributes of a material are governed by settings in the material type. To be preciseDescription it governs : 1. Number range pattern and nature (external/internal) 2. Hide/optional fields in the material master 3. Valuation Control at valuation area level (ultimately used to derive G/L) 4. Control on Production/Purchase
  15. 15. 1.13 Define Number Ranges for each material typesMenu path Implementation Guide for R/3 Customizing (IMG) → Logistics - General  Material Master  Basic Settings Material Types Define Number Ranges for each Material TypesTransaction Code MMNRConfiguration In this step, we have defined the type of number assignment and theDescription number range intervals for material master records. When creating a material master record, system must assign it a unique number. There are two ways of doing this: • internal number assignment In this case, a number within the number range interval allowed is assigned by the SAP system. • external number assignment Here, the user assigns a number within the number range interval allowed. We can define the intervals for external number assignment numerically and alphanumerically. We have defined the number range intervals for so-called groups. We assign one or more material types to each group. • If we assign just one material type to a group, we can define both an internal and an external number range interval for the material type. • If we group together more than one material type, we can define an internal and an external number range interval here too. This allows several material types to have the same number range intervals.
  16. 16. 1.14 Define Attributes of system messagesMenu path Implementation Guide for R/3 Customizing (IMG) → Logistics - General  Material Master  Basic Settings Define Attributes of system messagesTransaction Code OMT4Configuration When processing material master records, the system issues a number of systemDescription messages containing important user information. In this activity, we define how the SAP system handles these messages. We have the following options: • The message can be suppressed. • The message can be displayed as a warning. • The message can be displayed as an error message. (can’t be surpassed) For ITZ requirement Message Numbers MM189 & 312 are changed as Error message We are using Standard SAP Messages.1.15 Define Material GroupsMenu path Implementation Guide for R/3 Customizing (IMG) → Logistics - General  Material Master  Settings for Key Fields Define Material GroupsTransaction Code OMSFConfiguration Here we define the Groups for Materials & Services, This Grouping shallDescription be defined keeping in mind the reporting requirement of the company for analysing Purchases, Consumptions, Stocks etc, Setting is just a table entry, few records are shown in the screen shot, for complete list refer to the MM KDS document or the actual system node
  17. 17. 1.16 Define External Material GroupsMenu path Implementation Guide for R/3 Customizing (IMG) → Logistics - General  Material Master  Settings for Key Fields Define External Material GroupsTransaction Code SPROConfiguration Here we define the Groups for giving an extra key for filtering, sortingDescription the list of materials from a criterion other than Material grouping In case of ITZ we have not used External Material Groups1.17 Initialize PeriodMenu path Implementation Guide for R/3 Customizing (IMG) → Logistics - General  Material Master  Tools Initialize PeriodTransaction MMPICodeConfiguratio This Transaction can be used to initialize the period in materials management ,n Description i.e. it opens the already closed period (thru Txn : MMPV), but opening a period has serious implications on data consistency in SAP so as recommended by SAP Follow the instructions in Note 487381 before initialization
  18. 18. Materials Management – Consumption based Planning1.18 Activate MRP for MRP AreasMenu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Consumption-based Planning  Master Data  MRP Areas Activate MRP for MRP AreasTransaction Code SPROConfiguration This setting is required if we want to have planning at a level other than plants i.e.Description either of Storage location / at Subcontractor level. An MRP area represents an organizational unit for which we can perform material requirements planning separately. An MRP area can include one or several storage locations of a plant or a subcontractor. We can define MRP areas in a plant. For ITZ Ltd., we have not used MRP Areas.1.19 Define MRP AreasMenu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Consumption-based Planning  Master Data  MRP Areas Define MRP AreasTransaction Code SCALConfiguration Here we define the MRP areas for a plant for which we would like to carry outDescription material requirements planning separately. When creating an MRP area, we enter the number, which must have at least 5 digits to avoid any overlapping with the plant MRP area, the description and the MRP area type In case of ITZ we have not defined MRP area Important : If MRP area is activated Conversion of Planning file entries needs to be run in every new System Client through Report RMDBVM00 in Txn : SE38 The conversion report causes the system to create a new planning file. In addition, the system creates MRP area for the existing plants. These MRP areas do not, however, affect the way material requirements planning is carried out. The number for plant MRP areas is identical to the plant number and therefore consists of four digits. The conversion of the current planning file (table MDVM) to the new planning file (table DBVM) is a prerequisite for carrying out material requirements planning with MRP areas.
  19. 19. Materials Management – Purchasing1.20 Define Attributes of System MessagesMenu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Purchasing  Environment Data  Define Attributes of System MessagesTransaction Code SPROConfiguration In Purchasing, certain system messages containing importantDescription information for users may be issued from time to time In this step, we can specify whether the SAP System: • Suppresses the relevant information • Issues it as a warning message • Issues it as an error message In the case of an error message, processing cannot be continued until user input has been corrected For ITZ requirement, messages (as a change from standard) are configured as given below:1.21 Define Purchasing Value KeysMenu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Purchasing  Material Master  Define Purchasing Value KeysTransaction Code SPROConfiguration With Purchasing value key we can control following functions by using itDescription in the material master purchasing view, purchasing value key governs: • The issue of reminders and urging letters (expediters) with respect to nearly due and overdue deliveries • The admissibility of over- and under deliveries ("overages" and "under ages") • Order acknowledgment requirements for PO items • Shipping/packaging instructions This data appears as default data in purchasing documents and is taken from the material master record (unless a purchasing info record exists,
  20. 20. in which case it is taken from the info records).1.22 Entry Aids for Items without a Material MasterMenu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Purchasing  Material Master  Entry Aids for Items Without a Material MasterTransaction Code SPROConfiguration In this step we assign In this step, we can assign a purchasing value keyDescription and a valuation class to a material group. The assignment of a purchasing value key default values for reminder levels etc. in purchase order items without a material master record and without an info record. The assignment of a valuation class to a material group enables the system to determine different accounts for the individual
  21. 21. material groups. For ITZ we have maintained Valuation Classes in the accounting view of the materials.1.23 Create Purchasing GroupsMenu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Purchasing  Create Purchasing GroupsTransaction Code SPROConfiguration It’s a key for a buyer or group of buyers responsible for certain purchasingDescription activities. useful in accessing information, controlling authorizations, setting up release strategies etc. for ITZ ‘s Requirement following groups are configured, configuration is a simple table entry but purchasing group has a comprehensive use in all purchasing transactions/ documents1.24 Define Document Types (RFQ/Quotation)Menu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Purchasing  RFQ/Quotation  Define Document TypesTransaction SPROCodeConfiguration SAP manages RFQs and quotations as documents which are grouped intoDescription different document types., in this step we have : • Created new document types • Defined item interval • Defined admissible follow-on document types • Assigned document types to a number range group • Defined number range interval • Chosen type of number assignment - internal - external • Chosen update group The update group determines how the data from the document header is updated in the statistics file.
  22. 22. Linkage determines which PR document types can be referenced forcreating a particular RFQ document type
  23. 23. 1.25 Define Text Types for Header Texts (RFQ/Quotations)Menu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Purchasing RFQ /Quotations  Define Text Types for Header TextsTransaction Code SPROConfiguration In this step we define different Texts which appear in RFQ/QuotationDescription Headers, which are used to store information applicable for a particular RFQ document We have standard Header Text Types.1.26 Define copying rules for Header Texts (RFQ/Quotations)Menu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Purchasing RFQ /Quotations  Define copying rules for Line Texts (RFQ/Quotations)Transaction Code SPROConfiguration In this step we define copying rules for different header Texts whichDescription appear in RFQ/Quotation Line Items Copying rules are used to determine which texts can be adapted from other objects (for example, vendor master records, contracts) to the header text of the RFQ. We link text types in the RFQ with text types in other objects. System can adopt header texts from the following objects: • RFQ / Quotation • Contract • Scheduling agreement • Vendor master We can also specify whether the adopted text can be edited in the destination document or not. This type of setting is more useful in PO Header Texts
  24. 24. 1.27 Define document types (Purchase Requisitions)Menu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Purchasing  Purchase Requisitions  Define document types (Purchase Requisitions)Transaction Code SPROConfiguration SAP manages Purchase Requisitions as documents which are groupedDescription into various document types., in this step we have : • Created new document types • Defined item interval • Defined admissible follow-on document types • Assigned document types to a number range group • Defined number range interval • Chosen type of number assignment - internal - external • Chosen update group The update group determines how the data from the document header is updated in the statistics file.
  25. 25. Above linkage governs which type of PO can be created using PR of a particular type1.28 Release Procedure with Classification (Purchase Requisitions)Menu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Purchasing  Purchase Requisitions  Release Procedure Procedure with Classification  Set Up Procedure with ClassificationTransaction SPROCodeConfiguration In this step, we have set up the release procedure with classification.Description Purchase Requisition release is the process in which Purchase Requisition is approved and released by HOD of concern department for request of required material or services specified in Purchase Requisition. Once the Purchase Requisition is approved and released then Purchase Order or RFQ will be created for that material or services against same Purchase Requisition. Configuration involves following elements in sequence: Release Group: Specify for the release group either "overall release" or "item-wise release"
  26. 26. Release codes:The Release Code is a two-character ID allowing a person to release(approve) a requisition.(analogous to approver code)Release Indicators:A release indicator shows the release status of a purchase requisition
  27. 27. Release Indicators also involve:Field selection keyvia the field selection key, we can specify which fields in a purchaserequisition with this release indicator can be changed or must be populatedChanges after start of release process• With the Changeability indicator, we can specify the effects of changes to a requisition. For example, certain changes may require a new release strategy to be determined for the requisition.• Via the Value change field, we can cause the release strategy to be re- started if the value of a purchase requisition item is increased by more than a certain percentage (e.g. 10%). To do so, set the Changeability indicator to "4 - Changeable, new release in case of new strategy or value change" and enter a percentage in the Value change field.Release StrategyThe Release Strategy defines the approval process for Purchase Requisitions.The strategy specifies the release codes which are necessary and thesequence in which releases have to be affected. We can define a maximum ofeight release codes i.e. 8 Levels of approval.Release Prerequisites indicate the sequence in which a Purchase Requisitionmust be approved via the release codes. (In ITZ case release isparallel(either / or so indicators are kept blank)
  28. 28. Release Status indicates the affect after the release by a particular releasecodeRelease ValuesThese values need to be maintained in every client manually, this forms thebasis on which release strategy is triggered for a PR.An important prerequisite for this is to create Class & Characteristics inclass type 032Characteristics for Release StrategyCreate the Characteristics required for release strategy as master data thrutransaction CT04, here the most important setting is to attach thecharacteristics to corresponding field of structure CEBAN
  29. 29. attach it to the structureClass for Release StrategyCreate the class as master data thru transaction CL02
  30. 30. and attach the Characteristics created earlier to the class1.29 Define Number Ranges (Purchase Orders)Menu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Purchasing Purchase order  Define Number RangesTransaction Code OMH6Configuration In this step we define number ranges for Purchase order document types,Description (defined separately in customizing), this setting also includes number ranges for other external purchasing documents i.e. for
  31. 31. Contracts/Scheduling Agreements and RFQs. There are two ways of doing this: • internal number assignment In this case, a number within the number range interval allowed is assigned by the SAP system. • external number assignment Here, the user assigns a number within the number range interval allowed. We can define the intervals for external number assignment numerically and alphanumerically. In case of ITZ all the documents are assigned with internal number ranges with the exception for document type “Legacy Open P.O”, as it was required to retain the legacy P.O number for this case. go in change mode and define the intervals as shown:1.30 Define Document types (Purchase Orders)Menu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Purchasing Purchase Orders  Define document typesTransaction Code SPROConfiguration SAP manages Purchase Orders as documents which are grouped into
  32. 32. Description various document types., in this step we have : • Created new document types • Defined item interval • Define allowable item categories • Defined admissible follow-on document types • Assigned document types to a number range group • Defined number range interval • Chosen type of number assignment - internal - external • Chosen update group The update group determines how the data from the document header is updated in the statistics file.
  33. 33. Above linkage governs which type of PR can be referenced created while creating a particular Contract document type1.31 Set Tolerance Limits for Price VarianceMenu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Purchasing Purchase order  Set Tolerance Limits for Price VarianceTransaction Code SPROConfiguration When processing a purchase order, the system checks whether theDescription effective price of a PO item shows variances compared with the valuation price stored in the material master record. In addition, it checks whether the specified cash discount value is admissible. Variances are allowed within the tolerance limits. If a variance exceeds a tolerance limit, the system issues a warning or error message. In SAP, the types of variance are represented by the tolerance keys. For each tolerance key, we can define percentage and value-dependent upper and lower limits per company code. • PE Price variance, Purchasing o Tolerance limit for system message no. 207. This message appears if the specified effective price exceeds the predefined tolerances when compared with the material price. • SE Maximum cash discount deduction, Purchasing o Tolerance limit for system message no. 231. This is a warning message, which appears when the specified cash discount percentage exceeds the predefined tolerances.
  34. 34. 1.32 Release Procedure for Purchase OrdersMenu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Purchasing Purchase Order  Release Procedure for Purchase OrdersTransaction SPROCodeConfiguration In this step, we have set up the release procedure for Purchase Orders(thisDescription also covers the process for other external purchasing documents e.g. contracts/scheduling agreements) Purchase Order release is the process in which PO is approved and released by HOD of concern department for request of required material or services specified in PO. Once the Order is approved and released then GR can be created against the PO
  35. 35. In case of ITZ, Release strategy is used in case of all purchases.Configuration involves following elements in sequence:Release Group:Release groups are created for each type of purchasingRelease codes:The Release Code is a two-character ID allowing a person to release (approve)a requisition.(analogous to approver code)
  36. 36. Release Indicators:A release indicator shows the release status of a Purchase OrderRelease Indicators also involve:Changeability IndicatorWith the Changeability indicator, we can specify the effects of changes to aPO document. For example, certain changes may require a new releasestrategy to be determined for the requisition.• Via the Value change field, we can cause the release strategy to be re- started if the value of a purchase order is increased by more than a certain percentage (e.g. 10%). To do so, set the Changeability indicator to "6 - Changeable, new release in case of new strategy or value change" and enter a percentage in the Value change field.Release StrategyThe Release Strategy defines the approval process for PO. The strategyspecifies the release codes which are necessary and the sequence in whichreleases have to be affected. We can define a maximum of eight release codesi.e. 8 Levels of approval.Release Prerequisites indicate the sequence in which a Purchase Requisitionmust be approved via the release codes. (In ITZ case release is by a singleauthority so there are no prerequisite involved)Release Status indicates the affect after the release by a particular releasecodeRelease Values
  37. 37. These values need to be maintained in every client manually, this forms the basis on which release strategy is triggered for a PO. An important prerequisite for this is to create Class & Characteristics in class type 032 Characteristics for Release Strategy Create the Characteristics required for release strategy as master data thru transaction CT04, here the most important setting is to attach the characteristics to corresponding field of structure CEKKO And attach it to the structure Class for Release Strategy Create the class as master data thru transaction CL02 and attach the Characteristics created earlier to the class1.33 Define Screen Layout at Document LevelMenu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Purchasing Purchase Orders  Define Screen Layout at Document LevelTransaction Code SPROConfiguration In this step we define the attributes of various fields contained in a fieldDescription selection key (defined for a document type) inside which various fields are grouped into fields selection groups.Steps involved in the process are : • Selecting the field selection key (defined for a document type) • Select the field selection option (hide, display, required entry, or Optional entry) for each field inside a field selection group reference as required. Select a field selection key and set the attributes inside as shown:
  38. 38. get inside a field group and choose the attributes settings can be made similarly for other fields in various other groups as & when required1.34 Define Text Types for Header Texts (Purchase Orders)Menu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Purchasing Purchase Order  Define Text Types for Header TextsTransaction Code SPROConfiguration In this step we define different Texts which appear in Purchase orderDescription header, these are used to store information applicable for a particular PO document
  39. 39. 1.35 Define copying rules for Header Texts (Purchase Order)Menu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Purchasing Purchase Orders  Define copying rules for Header TextsTransaction Code SPROConfiguration In this step we define copying rules for different header Texts whichDescription appear in Purchase Order Headers Copying rules are used to determine which texts can be adapted from other objects (for example, vendor master records, contracts, RFQ) to the header text of the Purchase Order. We link text types in the PO with text types in other objects. System can adopt header texts from the following objects: • RFQ / Quotation • Contract • Scheduling agreement • Vendor master • Purchase Requisition We can also specify whether the adopted text can be edited in the destination document or not. Currently we are not maintaining any copying rule for header texts1.36 Define Text Types for Item Texts (Purchase Orders)Menu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Purchasing Purchase Order  Define Text Types for Item TextsTransaction SPROCodeConfiguration In this step we define different Texts which appear in Purchase order item level,Description these are used to store information applicable for a particular PO document line
  40. 40. item1.37 Define copying rules for Item Texts (Purchase Order)Menu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Purchasing Purchase Orders  Define copying rules for Item TextsTransaction Code SPROConfiguration In this step we define copying rules for different item Texts which appear inDescription Purchase Order ITEM Copying rules are used to determine which texts can be adapted from other objects (for example, vendor master records, contracts, RFQ) to the header text of the Purchase Order. We link text types in the PO with text types in other objects. System can adopt header texts from the following objects: • RFQ / Quotation • Purchase Requisition • Purchase Info record • Contract • Material master We can also specify here whether the adopted text can be edited in the destination document or not.
  41. 41. maintain the rules for a text as under1.38 Define Document Types (Contracts)Menu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Purchasing Contracts  Define Document TypesTransaction OMH6CodeConfiguratio SAP manages Contracts as documents which are grouped into variousn document types., in this step we have :Description • Created new document types • Defined item interval • Define allowable item categories • Defined admissible follow-on document types
  42. 42. • Assigned document types to a number range group • Defined number range interval • Chosen type of number assignment - internal - external • Chosen update group The update group determines how the data from the document header is updated in the statistics file.In case of ITZ, use of Contracts and Scheduling agreements is very minimal so wehave retained and used standard SAP document typesAbove linkage governs which type of PR can be referenced created whilecreating a particular Contract document type
  43. 43. 1.39 Define Screen Layout at Document Level (Contracts)Menu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Purchasing Contracts  Define Screen Layout at Document LevelTransaction SPROCodeConfiguratio In this step we define the attributes of various fields contained in a field selectionn key (defined for a document type) inside which various fields are grouped intoDescription fields selection groups.Steps involved in the process are : • Selecting the field selection key (defined for a document type) • Select the field selection option (hide, display, required entry, or Optional entry) for each field inside a field selection group reference as required. Select a field selection key and set the attributes inside as shown: get inside a field group and choose the attributes
  44. 44. settings can be made similarly for other fields in various other groups as & when required1.40 Define Text Types for Header Texts (Contracts)Menu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Purchasing Contracts  Define Text Types for Header TextsTransaction Code SPROConfiguration In this step we define different Texts which appear in Contract header,Description these are used to store information applicable for a particular Contract document
  45. 45. 1.41 Define copying rules for Header Texts (Contracts)Menu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Purchasing Contracts  Define copying rules for Header TextsTransaction Code SPROConfiguration In this step we define copying rules for different header Texts whichDescription appear in Contract Headers Copying rules are used to determine which texts can be adapted from other objects (for example, vendor master records, Contract, RFQ) to the header text of the Contract. We link text types in the PO with text types in other objects. System can adopt header texts from the following objects: • RFQ / Quotation • Contract • Vendor master We can also specify whether the adopted text can be edited in the destination document or not. We are maintaining Standard Text and copying Rules for Header Texts1.42 Define Text Types for Item Texts (Contracts)Menu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Purchasing Contracts  Define Text Types for Item TextsTransaction SPROCodeConfiguration In this step we define different Texts which appear in Contract item level, theseDescription are used to store information applicable for a particular Contract document line item1.43 Define copying rules for Item Texts (Contract)Menu path Implementation Guide for R/3 Customizing (IMG) → Materials
  46. 46. Management  Purchasing Contracts  Define copying rules for Item TextsTransaction Code SPROConfiguration In this step we define copying rules for different item Texts which appear inDescription Contract Headers Copying rules are used to determine which texts can be adapted from other objects (for example, vendor master records, contracts, RFQ) to the header text of the Contract. We link text types in the Contract with text types in other objects. System can adopt header texts from the following objects: • RFQ / Quotation • Purchase Requisition • Contract • Purchase Info record • Material master We can also specify here whether the adopted text can be edited in the destination document or not. maintain the rules for a text as under
  47. 47. 1.44 Define External Confirmation CategoriesMenu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Purchasing Confirmations  Define External Confirmation CategoriesTransaction SPROCodeConfiguration Notification from the vendor to the recipient regarding the status of a purchaseDescription order., In case of ITZ , CONFIRMATIONS are not being used Confirmation categories are defined to symbolize the key for a type of confirmation1.45 Define Internal Confirmation CategoriesMenu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Purchasing Confirmations  Define Internal Confirmation CategoriesTransaction SPROCodeConfiguration In this step, we assign an external confirmation category to each internal confirmationDescription category. Internal Categories are for system controls.
  48. 48. 1.46 Set Up Confirmation ControlMenu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Purchasing Confirmations  Set Up Confirmation ControlTransaction SPROCodeConfiguration In this step, we assign an external confirmation category to each internal confirmationDescription category. Internal Categories are for system controls. As shown all the conformation categories are relevant for MRP, but the last one is relevant to GR also, which means that when a GR is made against the P.O line
  49. 49. item it will get defaulted with qty of last conf. category1.47 Define Access SequenceMenu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Purchasing Conditions Define Price Determination Process  Define Access SequenceTransaction SPROCodeConfiguratio Access sequence is an important element of pricing determination. It is the Ordern Description in which the system searches through the condition tables when searching for particular condition records. The search order goes from specific condition records to general condition records. E.G. Access sequence is made up of condition table (the level at which data is stored) In the access sequence shown system will search for the record from first to last
  50. 50. table in sequence. (e.g. if Custom duty % for a material is maintained at all the three levels i.e. Incoterms-plant-maerial / Plant-Material / Plant-Material Type level , then system will take the record from 1 st available level only i.e. Incoterms- plant-maerial in this case) Each condition table is defined as an combination of fields for data access and is assigned to different condition types ( In case of ITZ , we are not maintaining any access sequence),1.48 Define Condition TypesMenu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Purchasing Conditions Define Price Determination Process  Define Condition TypesTransaction M/06CodesConfiguratio In this step we have defined condition types.n Description The condition types are used to represent pricing elements such as prices, discounts, surcharges, taxes, or delivery costs in the SAP. These are stored in the system in condition records. For condition types for which we want to maintain conditions with their own validity period we have specified an access sequence. (e.g. for all import duty conditions
  51. 51. Important Settings Condition type include: Condition Class: Defines nature of condition as Prices / surcharge / discounts etc. Calculation type: Defines nature of condition unit i.e. Amount type / Percentage / Qty etc Condition Category : e.g. Packaging, Cost , Tax, Delivery Costs(requiring extra vendor at condition level) Access Sequence : Allows condition records to be maintained Header Condition : Allows usage at Header level of Purchasing document Accruals : Makes a condition irrelevant to net price calculation i.e. excluded from tax base1.49 Define Calculation SchemaMenu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Purchasing Conditions Define Price Determination Process  Define Calculation SchemaTransaction M/08CodeConfiguratio In this step, we have defined the calculation schemas.nDescription In MM area, a calculation schema is a framework of steps used to calculate pricing in as purchasing document Analogous to this is referred to in the Sales and Distribution (SD) area as a pricing procedure. In the calculation schema (pricing procedure), we specify which condition types are to be taken into account in which sequence. In the price (or cost) determination process, the SAP System automatically determines which calculation schema is valid for a business transaction and takes into account, one after another, the condition types it contains . In case of ITZ we have defined schemas all starting with Z*, these will get derived in different types of purchasing documents as per the rule explained in Schema determination configuration
  52. 52. Select one of the schema and see the control data as shown below:Important keys in defining Schema are as under:Step No. & Counter: For determination the sequence of conditions and to act as abase for calculations with in conditionFrom- To : Base for calculation of condition value, this is only relevant for % type
  53. 53. of conditions Statistical: Makes a condition non-relevant to account postings Subtotal: Used to pass the condition value in to fields of P.O item tables and other pricing structure Requirement : Used for validating Condition value determination using small ABAP written formulae Base Type: Here a Formula for determining the condition basis as an alternative to the standard. Accrual key: for deriving a separate account during GR / Invoice postings1.50 Define Schema GroupMenu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Purchasing Conditions Define Price Determination Process  Define Schema GroupTransaction Code SPROConfiguration Every External Purchase document derives Calculation Schema from aDescription combination of Purchasing Organization and Vendor, to simplify data maintenance for this process SAP works with grouping concept. So all the purchasing org. are grouped in to a Schema group and Vendors requiring same pricing stricture are grouped into a Schema group , now for the combination of these , system derives the pricing schemas Click on a row to enter :
  54. 54. the other part i.e. vendors are assigned with schema group in vendor master1.51 Define Schema DeterminationMenu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Purchasing Conditions Define Price Determination Process  Define Schema determinationTransaction Code SPROConfiguration In this step we have defined the determination of Pricing schema forDescription different type of Purchasing documents and for Stock transport orders For standard purchase orders (depending on the schema group of the vendor and the purchasing organization) For stock transport orders (depending on the supplying plant, the document type and the schema group of the purchasing organization)
  55. 55. select first item ,and second item
  56. 56. 1.52 Define Transaction Event keysMenu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Purchasing Conditions Define Price Determination Process  Define Transaction Event keysTransaction SPROCodeConfiguration In this step, we have defined transaction/event keys for condition types involvingDescription provisions. This enables the system to find the relevant account for provisions (for accrued delivery costs or miscellaneous provisions, for example), We have assigned these transaction/event key to each condition type that is relevant to provisions in the step Define Calculation Schema. Select the 1st row Select second row, it displays the usage of key in schema
  57. 57. 1.53 Maintain Condition TableMenu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Purchasing Conditions Define Price Determination Process  Maintain Condition TableTransaction Code SPROConfiguration In this step, we create custom tables, these table are used to storeDescription condition records for different condition types , for this these tables should be a part of access sequence With help of this we can derive prices, discounts and surcharges dependent on almost all the fields in a purchasing document. In a condition table, we specify the combination of fields for which we can create condition records. As per SAP recommendation we should not change the condition tables that are included in the standard version of the SAP System. Check the extent to which we can use the condition tables that are supplied with the standard SAP System, for our tables we can only choose names between 501 and 999. If we make no entry, the system will automatically assign a consecutive number. For ITZ we have not defined any tables: Steps: For creating new condition tables. copy a similar condition table and proceed as follows: • Enter the name of the table we wish to create. • Note that we can only choose names between 501 and 999. If we make no entry, the system will automatically assign a consecutive number. • Specify whether we wish to create the table with or without a validity period.
  58. 58. • Enter the type of condition table (for example, transparent table). • Enter a description for the condition table. • From the list of allowed fields that are included in the field catalog and which can be extended there, choose the desired fields for the condition table. • Generate the new condition table. IMP: All the fields that shall be used to pick up any condition value must be part of Header/Key field in the condition table.1.54 Define Grid for Quantity VariancesMenu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Purchasing Statistics Define Grid for Quantity VariancesTransaction Code SPROConfiguration For Purchasing information system for vendor performance the statistics isDescription managed on the amount of quantity variances of vendors. The delivery quantity variance specifies in percent the variance between the purchase order quantity and the quantity actually delivered. This key figure is determined if an order item is completed and is updated for the entry date of the goods receipt or for the entry date of purchase order change. In this step we can determine four interval limits for every purchasing organization. Five intervals are then available to we for evaluation of vendors1.55 Define Grid for Delivery Date VarianceMenu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Purchasing Statistics Define Grid for Delivery dateTransaction Code SPROConfiguration Delivery date variance data is used in statistics for evaluating vendorDescription performance. The delivery date variance specifies the difference in days the difference between the statistically relevant delivery date and the date of the goods receipt. This key figure is updated during the goods receipt for the entry date. In this step we can determine four interval limits for every purchasing organization. Five intervals are then available to we for evaluation of vendors1.56 Define Weighing keysMenu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Purchasing Vendor Evaluation  Define Weighing keysTransaction SPROCodeConfiguration In vendor evaluation criteria are weighted according to their importance through
  59. 59. Description Weighing key. 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." If we consider a vendors price to be more important than quality, and quality to be more important than delivery, we can assign weights to the criteria in a ratio of three for price, two for quality, and one for delivery. This ratio is recorded in a weighting key.1.57 Define Criterion (Vendor Evaluation)Menu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Purchasing Vendor Evaluation  Define CriterionTransaction SPROCodeConfiguration Here we have defined the criteria by which the system computes scores forDescription vendors and specify whether the scores for the subcriteria are computed manually, semi-automatically, or automatically. Select One of the criterion and drilldown to sub criterion
  60. 60. 1.58 Define Scope of List (Vendor Evaluation)Menu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Purchasing Vendor Evaluation  Define Scope of ListTransaction SPROCodeConfiguration In this step we define various types of list, each representing different mainDescription criteria or the same main criteria in a different order. In the standard system, the scope-of-list parameters standard and version 1 are supplied as an example: • The parameter Standard provides the user with a ranking list of vendors by overall score. The main criteria are arranged in the order "Price", "Quality", "Delivery", "General service/support” and "Externally performed service/work". • 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". check the details of list inside1.59 Maintain Purchasing Organization dataMenu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Purchasing Vendor Evaluation  Maintain Purchasing Organization dataTransaction Code SPRO
  61. 61. ConfigurationDescription Select a row and displays criterion for Purchasing Organization Sub criterions for main criterion
  62. 62. Weighing for a Purchasing Org. We have provided Equal Weighting to the Criteria as we have different weighing parameters for ITZ Point scores for a Purchasing Org.1.60 Define Permissible Partner Roles per Account GroupMenu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Purchasing Partner Determination  Partner Roles Define Permissible Partner Roles per Account GroupTransaction Code SPROConfiguration Here we can specify for each account group of the vendor which rolesDescription the vendor may assume. Example we can specify that certain vendors may only serve as an ordering address, not as an invoicing party.
  63. 63. 1.61 Define Partner Schemas (Vendor Master)Menu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Purchasing Partner Determination  Partner settings in Vendor Master records Define Partner SchemasTransaction Code SPROConfiguration Partner schemas allow us to group various partner roles. We can specifyDescription that certain roles in a schema are mandatory, i.e. cannot be changed after entry. For ITZ, Schema groups Z1 is defined select a schema to detail the allowed partner functions
  64. 64. 1.62 Assign Partner Schemas to Account GroupsMenu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Purchasing Partner Determination  Partner settings in Vendor Master records Assign Partner Schemas to account groupsTransaction Code SPROConfiguration Here we assign the already defined schema groups to vendor accountDescription groups1.63 Define Partner Schemas (Purchasing Documents)Menu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Purchasing Partner Determination  Partner settings in Purchasing documents Define Partner SchemasTransaction Code SPRO
  65. 65. Configuration Partner schemas allow us to group various purchasing documents forDescription partner determination. We can specify that certain roles in a schema are mandatory, i.e. cannot be changed after entry. For ITZ, Schema group Z001 is defined Select a Schema to detail the partner function allowed1.64 Assign Partner Schemas to Document TypesMenu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  Purchasing Partner Determination  Partner settings in Purchasing documents Assign Partner Schemas to document typesTransaction Code SPROConfiguration In this step, we have assigned the partner schemas to the various types ofDescription purchasing document. As a result, only the roles of the schema in question can be maintained in documents of the relevant types.
  66. 66. Materials Management – External Services Management1.65 Define Service CategoryMenu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  External Services Management Service Master  Define Service CategoryTransaction Code SPROConfiguration In this step, we define the service category.Description The service category is the most important criterion for structuring Service master records. It provides a default value for the valuation Classes. Service master records can be assigned to number ranges on the basis of the service category.1.66 Define Number RangesMenu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  External Services Management Service Master  Define Number RangesTransaction Code SPROConfiguration In this step, we define Number Ranges for each service category.Description
  67. 67. 1.67 Define Number Range for Service Entry SheetsMenu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  External Services Management Service Master  Define Service CategoryTransaction Code SPROConfiguration In this step, we define the service category.Description The service category is the most important criterion for structuring Service master records. It provides a default value for the valuation Classes. Service master records can be assigned to number ranges on the basis of the service category.1.68 Define Attributes of System messagesMenu path Implementation Guide for R/3 Customizing (IMG) → Materials Management  External Services Management Service Master  Define Service CategoryTransaction Code SPROConfiguration In External Services Management, a number of system messagesDescription containing important information for users may be issued. Users can process this information further. In this step, we can define whether the SAP System • Suppresses this information • Issues it in the form of a warning • Issues it in the form of an error message For ITZ requirement, additional messages no. SE 346 / 347 / 361 is activated as Error along with other additional Standard SAP Messages
  68. 68. Materials Management – Inventory Mgmt. & Physical Inventory1.69 Plant ParametersMenu path Implementation Guide for R/3 Customizing (IMG) → Materials Management → Inventory Management and Physical Inventory → Plant ParametersTransaction SPROCodeConfiguratio In this step, we make the general plant settings for ‘Inventory Management’. Alln settings are also contained in the individual steps of the Implementation GuideDescription for Inventory Management. • If we have created a plant in the enterprise structure using the Copy plant function, we do not need to make any settings. • If we have created a plant manually, we have to create a new entry for the plant parameters.1.70 Define Number Assignment for Accounting DocumentsMenu path Implementation Guide for R/3 Customizing (IMG) → Materials Management → Inventory Management and Physical Inventory → Number Assignment → Define Number Assignment for Accounting DocumentsTransaction OMBACode
  69. 69. Configuratio In this step, we set the number ranges for the accounting documents which aren created when goods movements or inventory differences are posted.Description For accounting-relevant goods movements, the system creates two different documents: • material document • accounting document Both the material documents and the accounting documents have their own document numbers. When inventory differences are posted, the system also creates an accounting document for the physical inventory document. In this step, we only maintain the number assignment for accounting documents. Accounting documents are split into document types to allow differentiated document number assignment, which is the basis for distinguishing between the various accounting operations. A number range is assigned to each document type. In a company code, we have to define number intervals for each number range and fiscal year. In inventory management, the transaction determines which document type is used. Goods Issue Document Type TCode Transaction text Type Description Subseq. Adjustmt: Act.Ingredient Goods MB05 Mat WE receipt MB11 Goods Movement WA Goods
  70. 70. issue GoodsMB1A Goods Withdrawal WA issue GoodsMB1B Transfer Posting WA issue GoodsMB26 Picking list WA issue Place in Stor.for Mat.Doc:MBSU Init.Scrn GoodsMIGO_GI Goods Movement WA issueMIGO_T GoodsR Transfer Posting WA issue Goods Receipt Document Type TypTCode Transaction text e Description GoodsMB01 Post Goods Receipt for PO WE receipt Subsequ.Adj.of GoodsMB04 "Mat.Provided"Consmp. WE receipt GoodsMB0A Post Goods Receipt for PO WE receipt GoodsMB1C Other Goods Receipts WA issue Goods Receipt for Production GoodsMB31 Order WE receipt Subsequent Delivery f. MaterialMBNL Doc.MBRL Return Delivery for Matl Document Release Blocked Stock via Mat. GoodsMBSF Doc. WE receiptMBSL Copy Material DocumentMBST Cancel Material DocumentMIGO_G GoodsO Goods Movement WE receiptMIGO_G GoodsR Goods Movement WE receiptMIGO_G Subseq. Adjust. of Material GoodsS Provided WE receipt Automatic Movements Document TypeTCode Transaction text Type DescriptionBMBC Batch Information Cockpit WA Goods issue GoodsBORGR GR Automotive WE receipt GoodsBORGR_B GR Automotive: Posting WE receipt GoodsBORGR_C GR Automotive: Clearing WE receiptCAT5 Data Transfer CATS -> PS WA Goods issue Data Transfer CATS ->CAT9 PM/CS WA Goods issueCIP2 CC2: Update PDC messages WA Goods issueCIP3 CC3: Update PDC messages WA Goods issueCIP4 CC4: Update PDC messages WA Goods issue

×