tamm41_material_management_extras.pdf
DESCRIPTION
TAMM41_Material_Management_Extras.pdfTRANSCRIPT
SAP AG 1999
TAMM41 Materials Management - Appendices
TAMM41TAMM41TAMM41
Materials Management -AppendicesMaterials Management -Materials Management -AppendicesAppendices SAP AG
n System R/3 TAMM41 Materials Management - Appendices
n Release 4.6B
n April, 2000
n Material Number: 50032315
SAP AG 1999
Copyright 2000 SAP AG. All rights reserved.
Neither this training manual nor any part thereof maybe copied or reproduced in any form or by any means,or translated into another language, without the priorconsent of SAP AG. The information contained in thisdocument is subject to change and supplement without priornotice.
All rights reserved.
Copyright
n Trademarks:
n Microsoft ®, Windows ®, NT ®, PowerPoint ®, WinWord ®, Excel ®, Project ®, SQL-Server ®, Multimedia Viewer ®, Video for Windows ®, Internet Explorer ®, NetShow ®, and HTML Help ® are registered trademarks of Microsoft Corporation.
n Lotus ScreenCam ® is a registered trademark of Lotus Development Corporation.
n Vivo ® and VivoActive ® are registered trademarks of RealNetworks, Inc.
n ARIS Toolset ® is a registered Trademark of IDS Prof. Scheer GmbH, Saarbrücken
n Adobe ® and Acrobat ® are registered trademarks of Adobe Systems Inc.
n TouchSend Index ® is a registered trademark of TouchSend Corporation.
n Visio ® is a registered trademark of Visio Corporation.
n IBM ®, OS/2 ®, DB2/6000 ® and AIX ® are a registered trademark of IBM Corporation.
n Indeo ® is a registered trademark of Intel Corporation.
n Netscape Navigator ®, and Netscape Communicator ® are registered trademarks of Netscape Communications, Inc.
n OSF/Motif ® is a registered trademark of Open Software Foundation.
n ORACLE ® is a registered trademark of ORACLE Corporation, California, USA.
n INFORMIX ®-OnLine for SAP is a registered trademark of Informix Software Incorporated.
n UNIX ® and X/Open ® are registered trademarks of SCO Santa Cruz Operation.
n ADABAS ® is a registered trademark of Software AG
n The following are trademarks or registered trademarks of SAP AG; ABAP™, InterSAP, RIVA, R/2, R/3, R/3 Retail, SAP (Word), SAPaccess, SAPfile, SAPfind, SAPmail, SAPoffice, SAPscript, SAPtime, SAPtronic, SAP-EDI, SAP EarlyWatch, SAP ArchiveLink, SAP Business Workflow, and ALE/WEB. The SAP logo and all other SAP products, services, logos, or brand names included herein are also trademarks or registered trademarks of SAP AG.
n Other products, services, logos, or brand names included herein are trademarks or registered trademarks of their respective owners.
SAP AG 1999
Unit Technical Details: Material Master
Unit Others
Unit Overview Standard Courses
Unit Additional Exercises
Unit Menu Paths
Content: Appendices
Preface
© SAP AG TAMM41 1-1
SAP AG 2000
Contents:
Overview Standard Courses
l Standard Courses in MM
l Standard Courses in other areas
© SAP AG TAMM41 1-2
SAP AG 1999
Materials Management
Processes inProcurement
LO020 5 days
Inventory ManagementLO510 3 days
Invoice Verification3 daysLO515
Consumption-BasedPlanning andForecasting
LO525 2 days
Procurement ofExternal Services
LO540 2 days
Foreign TradeLO640 3 days
QM in ProcurementLO715 2 days
KANBANLO235 2 days
Batch ManagementLO955 3 days
Pricing in Purchasing2 days LO521
Cross-FunctionalCustomizing in MM
5 days LO550
Purchasing Details andOptimization
LO520 3 days
Cross-ApplicationBusiness Processes inSD and MM
LO925 2 days
Level 2 Level 3
n With the help of this slide you may inform yourself about the standard courses in the MM module. Furthermore you are able to get an idea of how many topics are covered in standard courses in the TeamSAP Academy course TAMM40:
� LO020: all subjects
� LO510: all subjects
� LO511: Physical Inventory: Overview, Cycle Counting and Inventory Sampling
� LO515: nearly all subjects
� LO520: ca. 80 % (no vendor evaluation and no Material Part Numbers in the academy)
� LO521: overview & important details
� LO525: ca. 60 % (there is no forecast in the academy)
� LO540: Overview in week 1. For further details, please visit this course.
� LO550: all subjects
� LO955: overview & important details
n Not covered in the academy are the following courses: LO235, LO640, LO715, LO925. If you are interested in subjects contained in these courses, please visit the relevant courses or the related “Advanced Academy” courses.
© SAP AG TAMM41 1-3
SAP AG 1999
Financial Accounting
Financial Accountingand Reporting
AC010 5 days Real EstateManagement
AC290 5 days
Asset AccountingAC305 4 days
Special Purpose LedgerAC220 5 days
Human Resources
HR050 5 days
Funds Management:Processes, Organizationand Configuration
AC700 5 days
EC-CS:Consolidation Functions
AC660 5 days
FI-LC:Consolidation Functions
*AC240 5 days
R/3 For Auditors
**AC900 4 days
Inflation Accounting
CA550 3 days
Level 3Level 2C
on
solid
ation
Financial ClosingAC205 2 days
Additional FinancialFunctionality
AC260 2 days
General Ledger/Accounts Payable/Accounts ReceivableConfiguration
AC200 5 days
Travel ManagementTravel Expenses
AC270 3 days Travel ManagementTravel Planning
AC275 1 day
** from July 2000 on
© SAP AG TAMM41 1-4
SAP AG 1999
Controlling
Cost Managementand Controlling
AC040 5 days
Cost CenterAccounting
AC410 3 days
Product Cost Planning
AC505 3 days
Profitability Analysis
AC605 5 days
Profit CenterAccounting
AC610 2 days
Executive InformationSystem (EIS) 1 -Reporting
AC615 2 days
Level 2 Level 3
Cost CenterAccounting:Extended Functionality
AC412 2 days
Activity Based Costing
AC420 2 days
Cost Object Controllingfor Products
AC510 3 days
Transfer Prices
AC650 2 days
Executive InformationSystem (EIS) - Settingup the System
AC620 2 days
Overhead Orders
AC415 2 days
Cost Object Controllingfor Sales Orders
AC515 3 days
Actual Costing /Material Ledger
AC530 2 days
Executive InformationSystem (EIS) 3 -Business Planning
AC625 1 day
© SAP AG TAMM41 1-5
SAP AG 1999
Human Resources 4.6 (1)
Level 3Level 2
Human Resources
HR050 5 days
Employee Self ServiceHR250 3 days
OrganizationalManagement
HR505 3 days
Travel ManagementTravel Expenses
AC270 3 days
CompensationManagement
HR540 3 days
Reporting inHR
HR580 3 days
Training and EventManagement
HR515 3 days
Time EvaluationHR310/311 5 days
Configuration ofMaster Data
HR305 3 days
Configuration of TimeRecording
HR306 3 days
BenefitsAdministration
HR325 3 days
RecruitmentHR315 3 days
seeHR2
Configuration of HRSystem Controls
HR307 2 days
Programming in HR
HR350 5 days
Technical Topics inHuman Resources
HR530 3 days
CATS The CrossApplication Time Sheet
CA500 2 days
PersonnelDevelopment
HR510 3 days
© SAP AG TAMM41 1-6
SAP AG 1999
Human Resources 4.6 (2)
Human Resources
HR050 5 days
Payroll Reporting(Country-Specific)
HR7xx 2 days
Level 2 Level 3
Payroll Configuration
HR400 5 days
Country-SpecificPayroll
HR4xx 3 days
Configuration ofMaster Data
HR305 3 days
Introductionto Payroll
HR390 2 days
© SAP AG TAMM41 1-7
SAP AG 1999
Logistics Execution
Transportation
LO611 3 days
Processes inLogistics Execution
LO140 3 days
Level 2 Level 3
Additional Topics inWarehouseManagement
LO531 3 days
Shipping
LO610 2 days Cross-FunctionalCustomizing in SD
LO650 3 days
WarehouseManagement
LO530 3 days
© SAP AG TAMM41 1-8
SAP AG 1999
Sales and Distribution
Level 2 Level 3
Processes in Salesand Distribution
LO150 5 days
ShippingLO610 2 days
Pricing in SDLO620 3 days
TransportationLO611 2 days
Foreign TradeLO640 3 days
Credit and ReceivablesRisk Management
LO645 2 days
Cross-ApplicationBusiness Processesin SD and MM
LO925 2 days
SalesLO605 4 days
Sales SupportLO604 1 day
Sales WorkshopLO606 1 day
Cross-FunctionalCustomizing in SD
LO650 3 days
BillingLO615 2 days
© SAP AG TAMM41 1-9
SAP AG 1999
Production Planning
Level 2 Level 3
ManufacturingPlanning &Execution forDiscrete & Repetitive
LO050 5 days
EngineeringChangeManagement
LO980 3 days
BatchManagement
LO955 3 days
KANBAN
LO235 2 days
Classification
LO985 3 days Special Features ofLIS in Production
LO275 2 days
Logistics InfoPlanning
LO935 2 days
CAP Calculation ofStandard Values
LO720 2 days
RepetitiveManufacturing
LO225 3 days
Capacity Planning
LO230 5 days
LogisticsInformationSystem (LIS)Reporting
LO930 2 days
Basic DataPart 2
LO206 3 days Basic Data forDiscreteManufacturing
LO205 3 days
ProductionOrders
LO215 5 days
ProductionPlanning
LO210 5 days
VariantConfiguration Part 1
LO990 5 days
VariantConfiguration Part 2
LO991 3 days
© SAP AG TAMM41 1-10
SAP AG 1999
Enterprise Controlling
Cost Managementand Controlling
AC040 5 days
Financial Accountingand Reporting
AC010 5 days
Profit CenterAccounting
AC610 2 days
EC-CS: ConsolidationFunctions
AC660 5 days
Financial ClosingAC205 2 days
E C - E I S:Executive Information System
E C - B P:Business Planning
E C - P C A: Profit Center Accounting
Level 3
Special PurposeLedger
AC220 5 days
E C - C S: ConsolidationConsolidation ofInvestments
Executive InformationSystem (EIS) 3 -Business Planning
AC625 1 day Executive InformationSystem (EIS) 1 -Reporting
AC615 2 days
Level 2
Controlling Enterprise Controlling Financial Accounting
Executive InformationSystem (EIS) 2 -Setting up the System
AC620 2 days
EC-CS: IntegrationAC665 3 days
© SAP AG TAMM41 2-1
SAP AG 2000
Contents:
Additional Exercises
l Procurement Processes
© SAP AG TAMM41 2-2
SAP AG 1999
l This exercise is intended to test andconsolidate your knowledge.
l You should be able to practice this exercise byyourself.
l If necessary, use your course documents andthe R/3 Online Help Library.
Hints to the Exercises
© SAP AG TAMM41 2-3
Procurement Processes Exercises
Procurement Processes
At the conclusion of this exercise, you will be able to:
• Estimate how much you have understood of the previous subjects
You have various roles in the following business scenario. Map the required processes in the SAP System to meet your material management requirements.
1 Foreword
1-1 Aim of exercise
This exercise is intended to test and consolidate your knowledge. Work through the exercises yourself and, if necessary, use your course documents.
The instructor will answer any questions. No solutions are provided for these exercises.
1-2 General information
In this exercise (unlike the other ones) you are provided only with the most important information you need to do the exercises. It is therefore essential that you read the scenarios thoroughly and use them in the correct business processes. You will find that it is up to you to provide much of the information and data.
© SAP AG TAMM41 2-4
A functional business process is provided so that you can check whether you have completed the exercise successfully.
Please make a note of the data and documents you create on this exercise sheet.
1-3 Basic data
You are provided with information on all the required data and settings.
Unless you are told otherwise, work with: Company code: 1000 (IDES)
Purchasing organization: 1000 (IDES)
Plant: 1000 (Hamburg)
Purchasing group: LO020-## (T##)
MRP controller: 0##
Use only vendors T-K12A##, T-K12B##, and T-K12C## for your processes.
If the vendor master T-K12B-## does not exist, please create this vendor via the central maintenance transaction as a copy of vendor master record T-K12A-## using the following data (incl. Accounting view):
Company code: 1000 (IDES)
Purchasing organization: 1000 (IDES)
Account group: LIEF
Address data: (Your choice)
Recon. Account: 160000
Payment methods: Check and Bank Transfer
Order currency: UNI
Terms of payment: 0002
Incoterms: FOB Mannheim
Automatic Purch. Order: yes
Good Luck!
© SAP AG TAMM41 2-5
2 Engineering/Design department
2-1 You have just finished manufacturing a new product. To manufacture this product, you need a new component that has never been used before in your company.
This component is to be managed under the number Teil-## in your company.
Teil-## goes into full production and, in future, will be available as a spare part for internal customers.
2-2 In the Engineering/Design view, enter the data required.
Which material type do you choose? ___________________________
The description of the component is: ____________________
Which view(s) do you create? ___________________________
Which data do you enter?
______________________________________________________
______________________________________________________
© SAP AG TAMM41 2-6
3 Purchasing
3-1 The Engineering/Design department has informed you that a new material Teil-## has been created in the system. You are asked to find possible vendors for the component in the next few days.
3-2 In your company, the buyer usually maintains the data relevant to accounting. As you do not yet know what the material costs, do not enter the accounting data until you know the prices of possible suppliers.
Teil-## is relatively low in value and is not subject to short-term price fluctuations. You want to valuate it at a fixed price.
3-3 Which view(s) do you create? ____________________________
Make a note of the most important data:
______________________________________________________
______________________________________________________
______________________________________________________
4 Warehouse
4-1 Make sure that Teil-## can be placed into storage. There are no particular requirements.
4-2 Which view(s) do you create? ____________________________
Make a note of the most important data:
______________________________________________________
______________________________________________________
© SAP AG TAMM41 2-7
5 Purchasing
5-1 You check in the system if price data for Teil-## has already been entered in another department.
How do you do this (transaction)? Is there price data?
______________________________________________________
______________________________________________________
5-2 You send RFQs to three vendors (T-K12A##, T-K12B##, and T-K12C##). The amount in the RFQ is 10,000 in accordance with your expected annual requirements.
As QI wants to check the parts before the vendor is released, inform your potential vendors in your RFQ that you will order 100 parts on the condition that they are given the order.
RFQ numbers / vendor:
______________________________________________________
______________________________________________________
______________________________________________________
5-3 You have received the quotations.
T-K12A## offers Teil-## for 12 UNI / pc for quantities above 100 pcs with delivery free of charge. The delivery time is 5 days.
T-K12B## can deliver Teil-## for 10 UNI / pc, but requires a flat-rate low-quantity surcharge of 250 UNI for quantities below 200 pcs. There is also a flat-rate freight charge of 150 UNI per delivery. The delivery time is 1 week.
T-K12C## charges 14 UNI / pc, with no freight charge for quantities over 100 pieces and a 2% freight surcharge for quantities under 100 pieces. The delivery time is 10 days.
© SAP AG TAMM41 2-8
5-4 According to the information from Production, you will order the material about 20 times per year; that is, you expect deliveries of 500 pieces a time.
Analyze the quotations and reject those you do not want to include.
Most reasonable vendor:_____________ Effective price / pc ________
5-5 Create an info record based on the most reasonable quotation.
5-6 Extend the material master record of Teil-## with the data that is required for the purchase order and account management.
Which view(s) do you maintain? ____________________________
Make a note of the most important data:
______________________________________________________
______________________________________________________
5-7 Order 100 pieces of the material with reference to the most reasonable quotation. Also order an inspection gauge for your cost center 4100 from the same vendor (material without a master record). The vendor informed you by telephone that the price is 200 UNI.
Issue the purchase order as a message.
PO number:____________________________________________
5-8 Shortly after you have issued the purchase order, you notice that you require another piece of material M-01. You therefore change the purchase order and add the monitor as a third item. The price is 1000 UNI. You send the changed purchase order to the vendor.
© SAP AG TAMM41 2-9
5-9 The vendor calls you because he or she does not know anything about item 3, M-01. You discover that you have ordered the item from the wrong vendor and cancel it. To let the vendor know, you send him or her a message to this effect.
6 Warehouse
6-1 The vendor sends you 50 pieces of the ordered material plus the inspection gauge. Teil-## is inspected first.
6-2 The QM department makes a positive usage decision. You therefore transfer Teil-##.
6-3 The prototype production department requires 25 pieces to prepare the material for repetitive manufacturing. You issue the required quantity to the appropriate cost center (4110).
Goods issue, movement type: Consumption for cost center from warehouse
7 Engineering/design, manufacturing, materials planning and purchasing
It is decided that the material does not have any defects and should be procured regularly from this vendor. It is also decided that the procurement process with regard to materials planning, purchasing, and invoice verification should be as simple and cheap as possible.
© SAP AG TAMM41 2-10
8 Materials planning
8-1 As the MRP controller responsible, you work out an appropriate planning strategy.
After consulting the warehouse and production, you decide that it is not advisable to keep more than 800 pieces of the material Teil-## in stock (=maximum stock level). As soon as the stock drops below 300 pieces, the replenishment of the material is automatically initiated. In this case, the stock level should be completely replenished. To cover possible risks and fluctuations, you plan to hold a safety stock of 50 pieces. According to the Purchasing Department, the vendor requires a delivery time of 5 days. As you also want to take future requirements into account in materials planning, you decide on an approporiate MRP procedure (choose MRP type V1).
8-2 Which views and indicators do you maintain? Make a note of the appropriate parameters.
______________________________________________________
______________________________________________________
______________________________________________________
______________________________________________________
______________________________________________________
© SAP AG TAMM41 2-11
9 Invoice verification
9-1 The vendor charges you for the complete quantity of the sample purchase order (100 pc). You enter and post the invoice.
Can the Financial Accounting Department pay the invoice? Give a reason for your answer.
______________________________________________________
______________________________________________________
10 Purchasing
10-1 As you do not want to process every purchase requisition for the vendor and Teil-## manually, you configure the system so that the purchase requisitions are automatically assigned with sources of supply.
These purchase requisitions are to be converted to purchase orders automatically via a report.
10-2 Maintain all the data that is required to do this.
Hint: Material master, vendor master, info record, and source list.
Which entries are essential?
______________________________________________________
______________________________________________________
______________________________________________________
______________________________________________________
______________________________________________________
© SAP AG TAMM41 2-12
11 Start of production
11-1 As the person responsible in Production, you require 200 pieces of Teil-## in 2 weeks. You therefore create a reservation to ensure that this component is available for the required date.
...→ Inventory Management → Reservation → Create
Base date: Current date +2 weeks
Movement type: 201
Cost center: 4100
Teil-##: 200 pieces
Accept any messages and save
11-2 As the MRP controller, you are currently checking the stock/requirements list for Teil-##.
Are there any requirements and, if so, are these covered?
______________________________________________________
You carry out a planning run for Teil-## and save it. What is the result?
______________________________________________________
11-3 In Purchasing, you are processing all purchase requisitions which have already been assigned sources of supply. Assign a source of supply for Teil-## and display the purchase order that is created.
PO number:____________________________________________
11-4 A delivery from vendor T-K12B-## arrives in goods receipt. It is the remaining 50 pieces from the sample purchase order and the ordered quantity from the reservation.
© SAP AG TAMM41 2-13
11-5 The accounts payable clerk settles all the vendor’s invoices for Teil-##.
Invoiced amount: ____________________________
Exercise complete!
Did you complete the process?
No? Go through the exercises again step by step or speak to the instructor
Yes? Congratulations!
© SAP AG TAMM41 3-1
SAP AG 1999
Contents:
Menu Paths
l Menu Paths
© SAP AG TAMM41 3-2
Frequently-used Menu Paths
LO020 4.6 Processes in Procurement Activity Menu Path
Master Data:
Material master: Create material
Logistics → Materials Management → Material Master → Material → Create (Special)
Material master: Create material (alternative)
Logistics → Materials Management → Material Master → Material → Create (General) → Immediately
Material master: Display material
Logistics → Materials Management → Material Master → Material → Display → Display Current
Material master: Change material
Logistics → Materials Management → Material Master → Material → Change → Immediately
Material master: Extend material view
Logistics → Materials Management → Material Master → Other → Extend Material View(s)
Material master: Enter storage locations collectively:
Logistics → Materials Management → Material Master → Other → Enter Storage Locations
Material master: Materials list
Logistics → Materials Management → Material Master → Other → Materials List
Material master: Change documents
Logistics → Materials Management → Material Master → Material → Display Changes → Active Changes
Info record: Create / Change / Display
Logistics → Materials Management → Purchasing → Master Data → Info Record → …
Vendor (all data) Create / Change / Display
Logistics → Materials Management → Purchasing → Master Data → Vendor→ Central→ …
Vendor (purchasing data) Create / Change / Display
Logistics → Materials Management → Purchasing → Master Data → Vendor→ Purchasing → …
Conditions by vendor Logistics → Materials Management → Purchasing Master Data → Conditions → Discounts/Surcharges → By Vendor
Service master Logistics → Materials Management → Service Master → Service → Service Master
Service conditions for service Logistics → Materials Management → Service Master → Service → Service Conditions → For Service → Display
© SAP AG TAMM41 3-3
Activity Menu Path Service conditions for vendor without plant
Logistics → Materials Management → Service Master → Service → Service Conditions → For Vendor Without Plant → Display
Service conditions for vendor with plant
Logistics → Materials Management → Service Master → Service → Service Conditions → For Vendor with Plant → Display
Documents:
Purchase requisition: Create / Change / Display
Logistics → Materials Management → Purchasing → Purchase Requisition → …
RFQ: Create Logistics → Materials Management → Purchasing → RFQ/Quotation → Request for Quotation → Create
Quotation: Maintain Logistics → Materials Management → Purchasing → RFQ/Quotation → Quotation → Maintain
Price comparison Logistics → Materials Management → Purchasing → RFQ/Quotation → Quotation → Price Comparison
RFQ / Rejection: Issue message
Logistics → Materials Management → Purchasing RFQ/Quotation → Request for Quotation → Messages → Print/Transmit
Purchase order: Create / Change / Display
Logistics → Materials Management → Purchasing → Purchase Order → Create → Vendor/Supplying Plant Known
Purchase requisition / Purchase order: Assign and process
Logistics → Materials Management → Purchasing → Purchase Requisition → Follow-On Functions → Assign and Process
Create purchase order automatically
Logistics → Materials Management → Purchasing → Purchase Requistion → Follow-On Functions → Create Purchase Order → Automatically via Purchase Requisitions
Purchase order: Issue message
Logistics → Materials Management → Purchasing → Purchase Order → Messages → Print/Transmit
Contract: Create / Change / Display
Logistics → Materials Management → Purchasing → Outline Agreement → Contract → ...
Shipping notification: Create / Change / Display
Logistics → Materials Management → Purchasing → Purchase Order → Inbound Delivery → ...
Enter goods receipt Logistics → Materials Management → Inventory Management → Goods Movement → Goods Receipt → For Purchase Order
Enter transfer posting Logistics → Materials Management → Inventory
© SAP AG TAMM41 3-4
Activity Menu Path Management → Goods Movement → Transfer Posting
Enter service Logistics → Materials Management → Service Entry Sheet → Maintain
Enter invoice Logistics → Materials Management → Invoice Verification → Logistics Invoice Verification → Document Entry → Enter Invoice
Evaluated receipt settlement (ERS)
Logistics → Materials Management → Invoice Verification → Logistics Invoice Verification → Further Processing → Execute ERS
Single planning run Logistics → Materials Management → Materials Requirements Planning (MRP) → MRP → Planning → Single-Item, Single-Level
List Displays, Reporting and Information
List display: Purchase requisitions
Logistics → Materials Management → Purchasing → Purchase Requisition → List Displays
List display: Purchase orders Logistics → Materials Management → Purchasing → Purchase Order → List Displays
List display: RFQ / Quotation
Logistics → Materials Management → Purchasing → RFQ/Quotation → Request for Quotation → List Displays
List display: Info records Logistics → Materials Management → Purchasing→ Master Data → Info Record → List Displays → …
List display: Goods receipts Logistics → Materials Management → Inventory Management → Environment → List Displays → Material Documents
Stock overview Logistics → Materials Management → Inventory Management → Environment → Stock → Stock Overview
Stock/requirements list Logistics → Materials Management → Inventory Management → Environment → Stock → Stock/Requirements List
Purchasing group analysis Logistics → Materials Management → Purchasing → Purchase Order → Reporting → Purchasing Information System → Standard analyses → Purchasing group
Analysis of storage location Logistics → Materials Management → Inventory Management → Environment → Inventory
© SAP AG TAMM41 3-5
Activity Menu Path Controlling → Standard analyses → Storage location
© SAP AG TAMM41 3-6
Frequently-used Menu Paths
Activity Menu Path
Master Data: Material Master Record Logistics→Materials Management→Material
Master→Material→Create/Change/Display
Purchasing Info Record Logistics→Materials Management→Purchasing→Master data→Info record→Create/Change/Display
Vendor Master Record Logistics→Materials Management→Purchasing→Master data→Vendor→Purchasing/Central→Create/Change/ Display
Source List Logistics→Materials Management→Purchasing→Master data→Source list→Maintain
Quota Arrangement Logistics→Materials Management→Purchasing→Master data→Quota arrangement→Maintain
Classification Logistics→Central Functions→Classification→Master data
Mass Maintenance Logistics→Central Functions→Mass Maintenance→Mass maintenance→Dialog processing
Vendor Evaluation Maintain Logistics→Materials Management→Purchasing→Master data→Vendor evaluation→Maintain
Vendor Evaluation Automatic New Evaluation
Logistics→Materials Management→Purchasing→Master data→Vendor evaluation→Autom. new evaluation
Documents:
Purchase Order Logistics→Materials Management→Purchasing→Purchase order→Create→Vendor/supplying plant known
Contracts Logistics→Materials Management→Purchasing→Outline agreement→Contract→Create
Scheduling Agreement Logistics→Materials
© SAP AG TAMM41 3-7
Management→Purchasing→Outline agreement→Scheduling agreement→Create→Vendor known
Scheduling Agreement Delivery Schedule
Logistics→Materials Management→Purchasing→Outline agreement→Scheduling agreement→Delivery schedule→Maintain
Purchase Requisition Logistics→Materials Management→ Purchasing→Requisition→Create
Purchase Order with Source Determination
Logistics→Materials Management→Purchasing→Purchase order→Create→Vendor unknown
Process Assigned Purchase Requisitions
Logistics→Materials Management→Purchasing→Purchase order→Create→Via req. assgt. list
Assign and Process Purchase Requisitions
Logistics→Materials Management→Purchasing→ Requisition→Follow on functions→Assign and process
Invoicing Plan: Automatic Settlement
Logistics→Materials Management→Invoice Verification→Logistics Invoice Verification→Further processing→Invoicing plan
Release of Purchase Requisitions
Logistics→Materials Management→Purchasing→ Requisition→Release→Individual release/Collective release
Automatic Generation of Purchase Orders
Logistics→Materials Management→ Purchasing→ Requisition→Follow on functions→Create purchase order→Automat. via PReqs
Reports/Analyses Purchase Order Lists Logistics→Materials
Management→Purchasing→Purchase order→List displays→By vendor/By materials
Purchase Requisition Lists Logistics→Materials Management→Purchasing→ Requisition→List displays→General
Info Records Logistics→Materials Management→Purchasing→Master data→Info record→List displays→By vendor/By material
Vendor Evaluation Ranking List
Logistics→Materials Management→Purchasing→Master data→Vendor evaluation→List displays→Ranking lists
© SAP AG TAMM41 3-8
Vendor Evaluation: Evaluation per Material/Material Group
Logistics→Materials Management→Purchasing→Master data→Vendor evaluation→List displays→Evalns. per mat./gp.
Customizing:
All menu paths begin with: Tools→AcceleratedSAP→Customizing→Edit Project→SAP Reference IMG→Materials Management→Purchasing
Release Creation Profile for Scheduling Agreements
Scheduling Agreement→Maint. Rel. creation profile for Sched. Agmt w. Rel. Docu.
Regular Vendor Source Determination→Define Regular Vendor
User Parameter EVO Environment Data→Define Default Values for Buyers→Settings for Default Values
User Parameter EFB Authorization Management→Define Function Authorizations for Buyers→Function Authorizations: Purchase Order
Invoicing Plan Purchase Order→Invoicing Plan
Release Procedures for Requisitions
Purchase Requisition→Release Procedure
Release Procedures for Purchase Orders
Purchase Order→Define Release Procedure
Vendor Evaluation Vendor Evaluation
Manufacturer Parts Profile Material Master→Define Manufacturer Part Profile
© SAP AG TAMM41 3-9
Menu paths for LO510
Goods movement Goods receipt / Goods issue / Stock transfer /
Transfer posting
Documents Reservation / Purchase order / Invoice / Material document
Pipeline Goods issue from pipeline / Pipeline liabilities
Consignment Transfer posting consignment to own / Goods issue from consignment stores / Consignment liabilities / Display vendor consignment stock / Display vendor consignment liabilities
Subcontracting Transfer posting to stock with subcontractor / SC stocks per vendor / Subsequent adjustment
Master data Info record / Material master record / Bill of material
© SAP AG TAMM41 3-10
Reports Stock overview / Material documents for material / Current stock/requirements list / Material document for posting date / Consumption statistics / Warehouse material / Reservations for material / Reason for movement
Goods movement
Goods receipt Logistics è Materials management è Inventory management è Goods movementè Goods receipt
Purchase order For Purchase order è PO number known
(movement type 101) (transaction MB01)
For purchase order è PO number unknown
(movement type 101) (transaction MB0A)
GR blocked stock For Purchase Order è PO number known
(movement type 103)
Blocked stock For Purchase order è PO number known (movement type 101). To post the material to blocked stock, choose „S“ in the field marked T (stock type).
Quality insp. stock For Purchase order è PO number known (Movement type 101). To post the material to quality inspection stock, choose „X“ in the field marked T (stock type).
Init. entry of st. bals Choose Others. From the menu, choose movement type è Receiptè Init.stck entry (own) è To unrestricted (movement type 561) (transaction MB1C)
Choose Others. From the menu, choose movement type è Receiptè Init.stck entry (ext) è To unrestricted (movement type 561) (transaction MB1C)
© SAP AG TAMM41 3-11
Goods issue Logistics è Materials management è Inventory management è Goods movement è Goods issue (transaction MB1A)
Goods issue to a cost center Movement type è Consumption è To cost center è From warehouse (movement type 201)
Issue to sampling Movement type è Issue è To sampling è From unrestricted (movement type 333)
Movement type è Issue è To sampling è From qual. inspection (movement type 331)
Movement type è Issue è To sampling è From blocked (movement type 335)
Issue to scrap Movement type è Issue è To scrap è From unrestricted (movement type 551)
Movement type è Issue è To scrap è From qual. inspection (movement type 553)
Movement type è Issue è To scrap è From blocked (movement type 555)
Stock transfer Logistics è Materials management è Inventory management è Goods movement è Transfer posting (transaction MB1B)
Plant to plant Movement type è Transfer posting è Plant to plant
One-step procedure Rem. fm/pl. in storage (movement type 301)
Two-step proc. (step 1) Rem. fm stor. to plant (movement type 303)
Two-step proc. (step 2) Pl. in stor. in plant (movement type 305)
© SAP AG TAMM41 3-12
Stor. loc. to stor. loc. Movement type è Transfer posting è Stor. loc to stor. loc.
One-step procedure Unrestr. to unrestr. (movement type 311)
Two-step proc. (step 1) Rem. fm. storage SLoc (movement type 313)
Two-step proc. (step 2) Pl. in storage SLoc (movement type 315)
Transfer posting
Material to material Movement type è Transfer postingè Material to material (movement type 309)
Stock to stock Movement type è Transfer posting è Stock to stock è Blocked to unrestr. (movement type 343)
Movement type è Transfer posting è Stock to stock è QI to unrestricted (movement type 321)
Documents
Reservation Logistics è Materials management è Inventory management è Reservation
Create Reservation è Create (transaction MB21)
Change Reservation è Change (transaction MB22)
© SAP AG TAMM41 3-13
Display Reservation è Display (transaction MB23)
Manage Reservation è Manage (transaction MBVR)
For material Reservation è For material (transaction MB24)
Purchase order Logistics è Materials management è Purchasing è Purchase order
Create Purchase order è Create è Stock transfer (transaction ME27)
Change Purchase order è Change (transaction ME22)
Display Purchase order è Display (transaction ME23)
PO statistics Logistics è Materials management è Purchasing è Purchase
order è Display. Then choose Item è Statistics è General
PO history Logistics è Materials management è Purchasing è Purchase order è Display. Then choose Item è Statistics è PO history
Invoice Logistics è Materials management è Invoice verification è Invoice
verification
Create Document entry è Enter invoice (transaction MRHR)
Display Further processing è Display (transaction MR03)
Mat. doc. Logistics è Materials management è Inventory management è
Material document
Display Material document è Display (transaction MR03)
Change Material document è Change (transaction MR02)
Cancel Material document è Cancel/reverse (transaction MBST)
© SAP AG TAMM41 3-14
Pipeline
Goods issue from pipeline Movement type è Consumptionè To cost centerè From pipeline (movement type 201) (transaction MB1A )
Pipeline liabilities Logistics è Materials management è Invoice verification è Invoice verification è Further processing è Settle cons./pipe. liabs (transaction MRKO)
Consignment Transfer of consignment stock Logistics è Materials management è Inventory
management è Goods movement è Transfer posting. From the menu, choose movement type è Transfer postingè Vendor consignment è QI to unrestricted (movement type 321) (transaction MB1B)
Logistics è Materials management è Inventory management è Goods movement è Transfer posting. From the menu, choose movement type è Transfer posting è Vendor consignment è Consignment to own (movement type 403) (transaction MB1B)
Goods issue from consignment stock Logistics è Materials management è Inventory management è Goods movement è Goods issue. From the menu, choose movement type è Consumptionè To cost centerè From consgt. stores (movement type 201) (transaction MB1A)
Settle consignment liabilities Logistics è Materials management è Invoice verification è Invoice verification è Further processing è Settle cons./pipe. liabilities (transaction MRKO)
© SAP AG TAMM41 3-15
Display vendor consignment stock Inventory Management è Environment è Consignment è Consgnmt from vendor è Stock (transaction MB54)
Display consignment liabilities Inventory management è Environment è Consignment è Consgnmt from vendor è Liability (transaction MRKO)
Subcontracting
Transfer posting to subcontractor Logistics è Materials management è Inventory management è Goods movement è Transfer postingè Movement type è Transfer postingè Stck w. subcontract. è From unrestricted (movement type 541) (transaction MB1B)
SC stocks per vendor Logistics è Materials management è Purchasing è Purchase order è Reportingè SC stocks per vendor (transaction ME20)
Subsequent adjustment Logistics è Materials management è Inventory management è Goods movement è Subsequent adjustment è Subcontracting (transaction MB04)
Master data
Info records Logistics è Materials management è Purchasing è Master dataè Info record
Create Info record è Create (transaction ME11)
Display Info record è Create (transaction ME12)
Change Info record è Change (transaction ME13)
© SAP AG TAMM41 3-16
Material master Logistics è Materials management èMaterial master è Material
Create Create (general) è Immediately (transaction MMR1)
Change Change è Immediately (transaction MM02)
Display Display è Display current (transaction MM03)
Bill of material Logistics è Production è Master data è Bills of material è Bill of material è Material BOMè Display (transaction CS03)
Reports Logistics è Materials management è Inventory management è Environment
Stock overview Stock è Stock overview (transaction MMBE)
Material documents for material List displaysè Mat. doc. for material (transaction MB51)
Reason for movement List displays è Reason for movement (transaction
MBGR)
Stock/requirements list Stock è Stock/rqmts. list (transaction MD04)
Material documents for posting date List displays è Mat. doc. f. postg. date (transaction MD59)
© SAP AG TAMM41 3-17
Warehouse stock Environment è Stock è Warehouse stock (transaction MD52)
Consumption statistics from stock overview:
Create a stock overview and place the cursor on the plant line. Then choose Extras è Display material è Choose the Extras pushbutton, (then click on the right arrow to scroll along to the Consumption option) è Consumption (transaction MMBE)
Consumption statistics from plant stock availability:
Call up the plant stock availability for a material and a plant. Choose DD in the „scope of list“ box. Place the cursor on the plant line and choose the „ consumption values“ pushbutton (transaction CO09).
© SAP AG TAMM41 3-18
Menu Paths Frequently-used Menu Paths
Activity Menu Path
Maintenance of Time-dependent Conditions: Info Record Logistics→Materials
Management→Purchasing→Master data→Info record
Contract
Logistics→Materials Management→Purchasing→Outline agreement→Contract
Scheduling Agreement Logistics→Materials Management→Purchasing→Outline agreement→Scheduling agreement
General Conditions Logistics→Materials Management→Purchasing→Master data→Conditions→Discounts/surcharges→By vendor…
Other Conditions Logistics→Materials Management→Purchasing→Master data→Conditions→Other
Display Price Overview Logistics→Materials Management→Purchasing→Master data→Conditions→Prices→General overview→By contract/By info record…
Vendor Price change Logistics→Materials Management→Purchasing→Master data→Conditions→Vendor price changes→Involving info recs/Involving contracts…
Maintenance of Time-independent Conditions:
Purchase Order Logistics→Materials Management→Purchasing→Purchase order→Create→Vendor/supplying plant known
Automatic Document Adjustment
Logistics→Materials Management→Purchasing→Purchase order→Follow on functions→Auto. document adj.→Indiv. documents/Create worklist…
© SAP AG TAMM41 3-19
Subsequent (End-of Period Rebate) Settlement: Rebate Arrangement Logistics→Materials
Management→Purchasing→Master data→Subseq. settlement → Vendor rebate arrs. →Rebate arrangement→Create
Business Volume Logistics→Materials Management→Purchasing→Master data→Subseq. settlement → Vendor rebate arrs. →List displays→Bus. vol data
Settlement Document Logistics→Materials Management→Purchasing→Master data→Subseq. settlement → Vendor rebate arrs. →Rebate arrangement→Create settlement document→Via report
Extension of Rebate Logistics→Materials Management→Purchasing→Master data→Subseq. settlement → Vendor rebate arrs. →Rebate arrangement→Extend
Basic Materials Management Functions: Material Master Record Logistics→Materials Management→Material
Master→Material→Create/Change/Display
Vendor Master Record Logistics→Materials Management→Purchasing→Master data→Vendor→Purchasing/Central→Create/Change/ Display
Goods Receipt Logistics→Materials Management→Inventory Management→Goods Movement→Goods Receipt→For Purchase Order→PO Number Known
Enter Invoice Logistics→Materials Management→Invoice Verification→Logistics Invoice Verification →Document entry→Enter invoice
Release Invoice Logistics→Materials Management→Invoice Verification→Logistics Invoice Verification →Further processing→Release invoices
© SAP AG TAMM41 3-20
Customizing: All menu paths begin with: Tools→AcceleratedSAP→Customizing→Edit Project→SAP Reference IMG→Materials Management→Purchasing
Access Sequences Conditions→Define price determination process→Define access sequences
Condition Types Conditions→Define price determination process→Define condition types→Define condition types
Calculation Schemas Conditions→Define price determination process→Define calculation schema
Schema Groups Conditions→Define price determination process→Define schema group→Schema groups: vendor…
Schema Determination Conditions→Define price determination process→Define schema determination→Determine calculation schema…
Condition Exclusion Conditions→Define price determination process→Define condition exclusion→Condition exclusion groups
Condition Tables
Conditions→Define price determination process→Maintain condition table→Create/change/display condition table
Automatic Document Adjustment Control
Conditions → Automatic Document Adjustment → Control Document Adjustment → Control Purchasing Document Adjustment
Scope-of-List Parameters for Lists of Conditions
Conditions → Scope of L ist for conditions → Define scope of list parameters
© SAP AG TAMM41 4-1
SAP AG 2000
Contents:
Technical Details: Material Master
l Material Master Tables and Details
l User Exits
© SAP AG TAMM41 4-2
SAP AG 1999
MARA
MARC
MAKT MARM MVKE MLAN
MLGN
MARD
MLGT
MEAN MBEW
MAPRMVER
Material Master - Table Structure
n The individual tables contain the following data: MARA General data
MAKT Descriptions/short texts MARM Conversion factors MVKE Sales data per sales organization MLAN Sales data per country MEAN EAN (European Article Number) data MBEW Valuation data MARC Material data per plant MLGN Material data per WM warehouse
MLGT Material data per WM storage type MARD Material data per storage location
MVER Consumption data MAPR Forecast data (pointer)
© SAP AG TAMM41 4-3
SAP AG 1999
Development class(es)Function group(s)Module poolLogical database(s)
MG, MGA ..M....SAPLMGMM, SAPLMGD1None
Number range object(s)NR element
NR group tableNR group(s)NR transaction(s)Authorization classAuthorization object(s)
MATERIALNR01 internal02 externalNoneGroup 1MMNR Material Master M_AENR_BGRMaterial master authorization group
Lock object(s)Change document object
EMMAR* (several) EMVKE*None
Matchcode object(s)Message class(es)Archiving class(es)Archiving object
MAT1, MAT2, MCH1MM, M3, WE, MG
Profile(s) MRP-profile, forecast-profile
Technical Details for the Material Master
© SAP AG TAMM41 4-4
SAP AG 1999
Material Master User Exits: Number Assignment (I)
l Internal Number Assignment
Number assigned when you create material, not when you save it.
l Customer Enhancement MGA00001
(Exit: EXIT_SAPLMGMU_001, module MATERIAL_UPDATE_ALL)
Completes checks for customer-specific fields.
Extends checks for existing fields.
Can change material data (restricted).
Example: enter basic material, material group, and consecutive number asmaterial description.
© SAP AG TAMM41 4-5
SAP AG 1999
Material Master User Exits: Number Assignment (II)
l Customer Enhancement MGA00002
(Exit: EXIT_SAPLMG02_001 for internal number assignment, moduleMATERIAL_NUMBER_GET)
Influences internal material number assignment:
n Internal number changed by customer program. Example: program takesinternal material number from number range, attaches it to the materialtype, and saves the new number.
(Exit: EXIT_SAPLMG02_002 for external number assignment, moduleMATERIAL_NUMBER_GET)
Influences external material number assignment:
n External number changed by customer program. Example: program addscheck digit to external material number.
© SAP AG TAMM41 4-6
SAP AG 1999
Material Master User Exits: Number Assignment (III)
l Customer Enhancement MGA00003
(Exit: EXIT_SAPLOMCV_001 and EXIT_SAPLOMCV_002 ,EXIT_SAPLOMCV_901 and EXIT_SAPLOMCV _902 , module:MATERIAL_UPDATE_ALL) MATERIAL_UPDATE_ALL)
Influences material number display format:
n Example: Converts the material number from #### to MAT-####
Caution: Problem using the search help, for example, using the searchterm M*
Result 1: All materials starting with MAT-Result 2: All materials starting with MAT- M
© SAP AG TAMM41 5-1
SAP AG 1999
Contents:
Others
l The Full-Cycle SAP B2B Procurement Solution
l SAP B2B Procurement Architecture
l Date Transfer Programms
© SAP AG TAMM41 5-2
SAP AG 1999
• Creation and editing ofrequisitions, purchaseorders, and reservations
• Approval and rejection ofrequisitions and purchaseorders
• Status and tracking ofrequisitions, purchaseorders, and reservations
• Desktop receiving andservice entry support
• Invoicing
• Reporting
Steps of the SAP B2B Procurement Solution
The Full-Cycle SAP B2B Procurement Solution
n SAP BBP handles all the processes associated with the procurement of maintenance, repair and operations (MRO) of both goods and services. It effectively organizes and automates MRO purchasing by moving the buying process to the corporate employee’s desktop. This improves order accuracy, allows process transparency, cuts costs, and reduces cycle -time. Unlike current best-of-breed solutions that only handle certain isolated tasks, the SAP BBP solution manages all the steps within the requisition-to-payment process:
� Creation and maintenance of requisitions, purchase orders and reservations
� Approval and rejection of requisitions and purchase orders
� Status and tracking of requisitions, purchase orders and reservations
� Desktop receiving and service entry support
� Invoicing
Supplier based
ERS
� Procurement Card interface
� Reporting
n GUI as part of EnjoySAP Initiative, by FROG Design.
© SAP AG TAMM41 5-3
SAP AG 1999
l Built upon R/3 core Purchasingfunctionality
l Incorporates SAP BusinessWorkflow
l Communicates with one of thefollowing R/3
7 R/3 Release 3.1H
7 R/3 Release 4.0B
7 R/3 Release 4.5A
l Based on R/3 Release 4.5 nucleus
l Built using the SAP ITS technology
SAP B2B Proc.
R/3 Rel. 4.0B
R/3 Rel. 4.0B
R/3 Rel. 3.1H
R/3 Rel. 3.1H
Non
R/3
Non
R/3
R/3 Rel. 4.5A
R/3 Rel. 4.5A
SAP B2B Procurement Architecture
n Solution delivered as part of SAP SCM initiative.
n First Customer Shipment (FCS) in Q4/1998.
n Based on R/3 core purchasing functionality and SAP Business Workflow.
n Based on open scalable SAP Business Framework architecture for component design and interfaces
� BAPIs for realtime cross enterprise supplier integration based on XML technology.
© SAP AG TAMM41 5-4
SAP AG 1999
Data Transfer Programs
Direct input process
Function module
(background processing
only)
SAPDatabase
Batch inputprocess
Screen(in dialogor in the
background)
Formatting of theFormatting of themaster data master data
in SAP formatin SAP format
Master data Master data in the in the
old systemold system
n SAP provides the file layout for each master file.
n The user must create an SAP master file using the file layout provided and then write a conversion program to extract the legacy system data and transfer it into the SAP master file in the SAP format.
n Once in an SAP format the user can update the SAP database using the direct input or batch input process.
n Regardless of the input process used, the SAP System performs its normal data validation routines.
n The data transfer process is covered in course BC420.
© SAP AG TAMM41 5-5
Supplement for Message Control
For a comprehensive description of message determination, see the documentation CA – Message Control, which you can find in the SAP Library as follows:
SAP Library → Cross-Application Components → General Application Functions (CA-GTF) → CA – Message Control
General Information
Output and follow-on processing of partner-specific messages is automated using Message Control . The application calls the Message Control function using defined interfaces.
Message Control is a “service program” for other applications.
Message Control and the Link to the R/3 Application
...
Printout Fax Telex Mail EDI CPIC Workflow event
Condition elements
Condition tables
R/3 application Application object
Communication structures
Message default
Message determination
Message processing
Message status
Processing program
Is processed
CallsPasses on data
Receives status
Writes
Proposes
Has an assignment
Starts
Checks
Processes
© SAP AG TAMM41 5-6
Features The R/3 System condition technique is used to formulate the dependent data constellations for Message Control.
During message determination, the system checks whether one or more records in condition tables match the current application data. If this is the case, message determination was successful, one or more messages were found, and the corresponding message default is triggered. If the application supports it, you can change (edit) the default.
Consequently, the message is processed further immediately or at specific times. The processing status of the message is stored in a status record. If the application supports it, the system writes a processing log.
The Condition Elements: Hierarchy Example for Purchasing
EF
RMBEV1RMBEA1
RMBEF1
AUFBMAHN
NEU
0001
B026B025
B027
Zugriffsfolge
Zugriff auf Konditionstabelle
Nachrichtenart
Schema
Applikation
Feldkatalog für Konditionsschlüssel
Applikationsfilter
Kommunikationsstruktur
Nac
hric
hten
steu
erun
g A
nwen
dung
© SAP AG TAMM41 5-7
Terms Used
Application An application component is generally also described as an application. Each specific application that wants to use Message Control is assigned an application ID (such as EF for Purchasing – Purchase Order, V1 for Sales, MR for Invoice Verification).
Field catalog
The field catalog contains all fields that can be selected as keys for the condition tables for message control. An application filter is created for each application using this field. This filter determines which fields in the field catalog can be selected for the application in question. For example, the fields Purchasing organization and Purchasing group are defined for the application EF (Purchasing – Purchase Order) and the fields Plant and Storage location are defined for the application ME (Inventory Management).
Communication structure When the Message Control function is called, application data for transfer to Message Control is placed in communication structures. This application data is required for message determination.
Condition table A condition table is a table that consists of one or more condition keys and a data part:
• The condition keys can be selected according to the data constellation that the system is searching for the message for. The key fields originate in the field catalog .
• The data part depends on the use of the condition technique (message determination, price determination, or account determination) and consists of the fields that describe the message. In the case of message determination (that is, when the condition table is being used by Message Control), the data part consists of an index for the table of message attributes (NACH).
• The message attributes include, for example, the processing time point, the transmission medium, and the language. This data is specified when creating a message, that is, when creating the appropriate condition record in the applications.
Condition record Condition records are entries in a condition table. The condition records in an output condition table therefore describe the values or field contents that lead to a message, and the attributes for this message. Depending on the application, the message found is proposed in the business process or passed on for processing.
© SAP AG TAMM41 5-8
Message schema
A schema is the group of permitted messages for each message application (reprint, reminder, and so on). Each schema is searched separately for messages that are to be further processed in the data constellation specified (for example, send electronically or printed out).
You can specify conditions for the individual message type in a schema, under which the messages are to be created. For example, the system checks whether the message has already been reprinted when message type MAHN is used in Purchasing.
An application uses the current document type to determine exactly one schema that it passes on to message determination. The schema is thus a group of message types from the perspective of the application and is used for automatic default of messages for a business transaction.
Message type A message type is an ID for the message content and is used to manage parameters for message determination.
A message type (or condition type) groups together messages with the same meaning. It contains parameters that apply to all messages assigned to the group, such as partner roles defined.
Access sequence An access sequence is a message determination strategy that the system uses to determine valid values for the message default.
An access sequence:
• Determines the sequence in which the system works through the condition tables. The system searches for messages in the condition tables. You can agree that the system stops searching the condition tables of the access sequence once it has found a hit (Exclusive indicator).
• Assign fields from the communication structure to the keys for the condition tables (= table access). Using the content of the communication structure, the system tries to read the condition table and find a record (that is, a message). When this is successful, the record in the condition table is processed into a message status record for table NAST.
Partner determination During partner determination, the application passes on the communication structures and a table of partners for the application object to Message Control . This table contains partner roles and partner numbers.
In this case, you have to specify only the partner role in the condition record, since the partner for the corresponding partner role is passed on in the message status record during message determination. Therefore, the addressee for the message is known.
If you have agreed on a partner number in the condition record, this is passed on to the message default every time.