Professional Documents
Culture Documents
Tamm41 1 PDF
Tamm41 1 PDF
TAMM41
Materials Management -
Appendices
SAP AG
AG 1999
SAP AG 1999
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.
Content: Appendices
Preface
SAP AG 1999
Overview Standard Courses
Contents:
l Standard Courses in MM
l Standard Courses in other areas
SAP AG 2000
Level 2 Level 3
LO510 3 days
Inventory Management
LO515 3 days
LO550 5 days
Invoice Verification
Cross-Functional
LO520 3 days Customizing in MM
Purchasing Details and LO521 2 days
Optimization
LO020 5 days Pricing in Purchasing
LO525 2 days
Processes in Consumption-Based
Procurement Planning and
LO955 3 days
Forecasting
Batch Management
LO540 2 days
Procurement of
External Services
LO925 2 days
Cross-Application
Business Processes in
SD and MM
LO640 3 days
Foreign Trade LO235 2 days
KANBAN
LO715 2 days
QM in Procurement
SAP AG 1999
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.
Level 2 Level 3
AC205 2 days
AC200 5 days
Financial Closing
General Ledger/
Accounts Payable/
Accounts Receivable AC260 2 days
Configuration Additional Financial
Functionality
AC660 5 days
AC290 5 days
Consolidation
AC010 5 days EC-CS:
Real Estate Consolidation Functions
Financial Accounting Management
and Reporting *AC240 5 days
AC305 4 days
FI-LC:
Asset Accounting Consolidation Functions
AC220 5 days **AC900 4 days
Special Purpose Ledger
R/3 For Auditors
AC700 5 days
Funds Management: CA550 3 days
Processes, Organization
and Configuration Inflation Accounting
HR050 5 days
AC270 3 days AC275 1 day
Human Resources Travel Management Travel Management
Travel Expenses Travel Planning
SAP AG 1999 ** from July 2000 on
Level 2 Level 3
AC412 2 days
Cost Center
Accounting:
Extended Functionality
AC410 3 days AC415 2 days
Cost Center
Accounting Overhead Orders
AC420 2 days
Activity Based Costing
AC040 5 days
Cost Management AC510 3 days
and Controlling Cost Object Controlling
for Products
AC505 3 days AC515 3 days
Product Cost Planning Cost Object Controlling
for Sales Orders
AC605 5 days AC530 2 days
Profitability Analysis Actual Costing /
Material Ledger
AC610 2 days AC650 2 days
Profit Center
Accounting Transfer Prices
Level 2 Level 3
HR305 3 days HR390 2 days
Configuration of Introduction
Master Data to Payroll
HR400 5 days
Payroll Configuration
HR050 5 days
Human Resources HR4xx 3 days
Country-Specific
Payroll
HR7xx 2 days
Payroll Reporting
(Country-Specific)
SAP AG 1999
Level 2 Level 3
LO611 3 days
Transportation
SAP AG 1999
LO640 3 days
Foreign Trade
LO645 2 days
Credit and Receivables
Risk Management
LO925 2 days
Cross-Application
Business Processes
in SD and MM
SAP AG 1999
Level 2 Level 3
LO980 3 days LO210 5 days
Engineering Production
Change Planning
Management
LO215 5 days LO230 5 days
LO235 2 days
Production
Capacity Planning
KANBAN Orders
LO050 5 days
LO205 3 days LO206 3 days LO225 3 days LO720 2 days
Manufacturing
Planning & Basic Data for Basic Data Repetitive CAP Calculation of
Execution for Discrete Part 2 Manufacturing Standard Values
Discrete & Repetitive Manufacturing
SAP AG 1999
E C - C S: Consolidation
Consolidation of
Investments
AC660 5 days
EC-CS: Consolidation
Functions
Contents:
l Procurement Processes
SAP AG 2000
SAP AG 1999
Procurement Processes
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.
Good Luck!
______________________________________________________
______________________________________________________
______________________________________________________
______________________________________________________
4 Warehouse
4-1 Make sure that Teil-## can be placed into storage. There are no particular
requirements.
______________________________________________________
______________________________________________________
______________________________________________________
______________________________________________________
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-6 Extend the material master record of Teil-## with the data that is required
for the purchase order and account management.
______________________________________________________
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.
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).
8-2 Which views and indicators do you maintain? Make a note of the
appropriate parameters.
______________________________________________________
______________________________________________________
______________________________________________________
______________________________________________________
______________________________________________________
______________________________________________________
______________________________________________________
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.
______________________________________________________
______________________________________________________
______________________________________________________
______________________________________________________
______________________________________________________
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:____________________________________________
Exercise complete!
Yes? Congratulations!
Contents:
l Menu Paths
SAP AG 1999
Documents:
Purchase requisition: Logistics → Materials Management → Purchasing →
Create / Change / Display Purchase Requisition → …
RFQ: Create Logistics → Materials Management → Purchasing →
RFQ/Quotation → Request for Quotation → Create
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
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
Customizing:
All menu paths begin with: Tools→AcceleratedSAP→Customizing→Edit
Project→SAP Reference IMG→Materials Management→Purchasing
Release Creation Profile for Scheduling Agreement→Maint. Rel. creation profile
Scheduling Agreements 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
Transfer posting
Goods movement
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)
Two-step proc. (step 1) Rem. fm. storage SLoc (movement type 313)
Transfer posting
Documents
Goods issue from pipeline Movement type è Consumptionè To cost centerè From
pipeline (movement type 201) (transaction MB1A )
Consignment
Subcontracting
Master data
Material documents for material List displaysè Mat. doc. for material (transaction
MB51)
MBGR)
Material documents for posting date List displays è Mat. doc. f. postg. date (transaction
MD59)
Contents:
l Material Master Tables and Details
l User Exits
SAP AG 2000
MARA
MARC MLGN
MLGT
SAP AG 1999
SAP AG 1999
SAP AG 1999
SAP AG 1999
Contents:
l The Full-Cycle SAP B2B Procurement Solution
l SAP B2B Procurement Architecture
l Date Transfer Programms
SAP AG 1999
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 1999
Function
module
Master data Direct input
(background
in the
the process
processing
old system
only)
SAP
Database
Screen
(in dialog
Formatting of the Batch input
or in the
master data
data process
background)
in SAP format
format
SAP AG 1999
R/3 application
Application object
Communication Message
structures default
Calls Proposes
Passes on data
Condition elements
Checks Has an
Condition Message
tables determination assignment
Processes
Writes
Message status
Is processed
Receives status
Message
processing
Starts
Processing program
...
Printout Fax Telex Mail EDI CPIC Workflow
event
Applikationsfilter
Applikation EF
Kommunikationsstruktur
RMBEV1
RMBEA1
Schema RMBEF1
AUFB
MAHN
Nachrichtenart NEU
Nachrichtensteuerung
Zugriffsfolge 0001
B026
B025
Zugriff auf B027
Konditionstabelle
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.
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.