materials management materials management

SAP AG 1999

TAMM40 Materials Management - Part IV

TAMM40TAMM40

Materials ManagementPart IV

Materials ManagementPart IV

SAP AG

n R/3 System TAMM40 Materials Management

n Release 4.6B

n April 2000

n Material number: 50032313

Contact for Buying Any SAP Materials: [email protected] Visit: ww.sapcertification.co.nr

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/4, 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 TAMM40 1-1

SAP AG 1999

Section: ASAP



SAP AG 1999

Unit ASAP Overview

Unit Implementation Roadmap

Content: ASAP



SAP AG 1999

ASAP Overview: Topics

ASAP Overview

UnitUnitUnit

TopicTopicTopic

Legend:Legend:Legend:

ASAP Defined

Tools Availablein ASAP



SAP AG 1999

ASAP Defined: Objectives

Upon completion of this topic, you will be able to:

l Identify ASAP’s purpose, and its role in TeamSAP

l Describe the 3 integrated components of ASAP

l Distinguish between the Implementation Assistant& ASAP in R/3

l Explain the need for flexibility in presenting thecontent of the ASAP Roadmap

l State the preconditions critical for an effectiveASAP project implementation

l Identify the major content and key deliverables ofeach of an ASAP implementation project’s phases



SAP AG 1999

TeamSAP Components

Peop

le

Processes

Products

People:People:Solutions expertiseQualityn SAPn Consulting partnersn Complementary

software partnersn Technology &

hardware partners

Processes:Processes:AcceleratedSAPConsistencyn AcceleratedSAP Roadmaps or

powered by methodologiesn SAP Review Programn Support, services

& education

Products:Products:The Business FrameworkStrengthn R/3 product familyn Complementary software productsn Technology partner productsn Industry solutions

TeamSAP

n TeamSAP represents a total organizational commitment by SAP and partners to the overall success of customers by helping them define the right business solution, by providing assistance during implementation and by guiding them as their business changes.

n TeamSAP projects have the following standards to assist in the success of customers:

� TeamSAP Coach - single point of contact for customer, providing fast answers to any questions.

� ASAP or ”powered-by”* implementation methodologies - ASAP is a clearly defined implementation strategy that ensures customers a quick and predictable implementation, regardless of size or complexity of environment. * Powered-by implementation methodologies are SAP Partner methodologies incorporated into the ASAP methodology.

� Managed by SAP or TeamSAP Partner - the TeamSAP Partner certification program represents the commitment between SAP and its partners to work together for the overall benefit of the customer.

� Quality Assurance Check - this program allows SAP to proactively measure how the project is progressing, how well the implementation methodology is being followed, to verify performance and to make sure customers are getting the solution presented in the software selection process.

� Steering Committee Representation - SAP representation on the customer's project steering committee will help provide strategic direction to the customer's implementation and for future business changes.



SAP AG 1999

Training, Licensing Training Material(Knowledge Warehouse), Support, Project Reviews

Training, Licensing Training Material(Knowledge Warehouse), Support, Project Reviews

l ImplementationAssistant

l Q&Adb

l ImplementationGuide

l Profile Generator

l Transport System

AcceleratedSAP - SAP´s Full Life-Cycle Solution

l ProjectManagement

l OrganizationalChangeManagement

l Risk Analysis

l Review

Methodology

Services

Project-Related

KnowledgeTools

ASAP RoadmapProject

PreparationBusiness Blueprint

RealizationFinal Preparation

Go Live &Support

Continuous

Improvement

ASAPASAP

n AcceleratedSAP (ASAP) is the implementation solution provided by SAP. ASAP integrates several components that work in conjunction to support the rapid and efficient implementation of the SAP’s R/3 System, Industry Solutions and New Dimension products. The components that make up ASAP are :

� Methodology - The ASAP Roadmap defines the phases of the implementation process and supports these with a comprehensive project plan. The project plan comprises MS Project templates providing complete work breakdown structures and resource assignments.

� Tools - The ASAP process is supported by a comprehensive set of both PC-based and R/3-resident tools.

� Service - Hotline, Consulting, Training, Project Reviews, SAPNet

� Project related Knowledge like Project Management, Change Management, Risk Analysis and Review Programs.



SAP AG 1999

Defining the Points on the ASAP Roadmap

ProjectPreparation

Business Blueprint

Realization

FinalPreparation Go Live &

Support

Continuous

Improvement

•Initial Project Planning•Project Procedures•Training•Project Kickoff•Technical Requirements•Quality Check

•Project Management•Organizational Change Management•Training•Develop System Environment•Organizational Structure Definition•Business Process Analysis•Business Process Defintion•Quality Check

•Project Management•Organizational Change Management•Training•Baseline Configuration and Confirmation•System Management•Final Configuration and Confirmation•Develop Programs, Interfaces etc.•Final Integration Test•Quality Check

•Project Management•Training•System Management•Detailed Project Planning•Cutover•Quality Check

•Production Support•Project End

n Phase 1: Project Preparation - Provides initial planning and preparation for your R/3 project.

n Phase 2: Business Blueprint - In this phase, you create the Business Blueprint, which is detailed documentation of the results gathered during requirements workshops. Furthermore, the Business Blueprint serves to document the business process requirements of the company. On this basis, you will achieve a common understanding of how the company intends to run their business within the R/3 System.

n Phase 3: Realization - In this phase, you implement all the business and process requirements based on the Business Blueprint. You configure the system step by step in two work packages, Baseline and Final configuration.

n Phase 4: Final Preparation - In this phase, you complete testing, end user training, system management and cutover activities to finalize your readiness to go live. Furthermore, the Final Preparation phase serves to resolve all critical open issues. Upon successful completion of this phase, you will be ready to run your business in your live R/3 System.

n Phase 5: Go Live and Support - Transition from a project-oriented, pre-production environment to successful and live production operation.

n Continuous Improvement - Provide on-going support and assistance for post go-live. It covers solutions for those activities which are standard in a productive environment: Business changes; technology changes; or changes in the user community.



SAP AG 1999

4 Master ListsExcel Spreadsheets forDevelopment, Organization,Business Processes andAuthorizations

ProjectCharter

BPP

Key ASAP Deliverables

Q&AdbStructures:

Business StrategyOrganizationGeneral SettingsMaster DataBusiness ProcessCross ApplicationDevelopment

BusinessBlueprint

ProjectPlan

Scope

Config.Plan

TestingPlan

Unit TestingTest ScenarioIntegration

4321 5

StressTest

VolumeTest

Cut OverPlan

DeliverEnd UserTraining

SystemPerformance

Review

ProjectTeamOrg.

Std. &Proced

TechnicalOperations

Manual

Develp.Programs

EUTrainingMaterial

Word Documents

Phase 1 - Project Preparation - Change Charter - Goals, objectives of org change management

n Project Plan - This is a first cut focusing on milestones and Work Packages. Details to come.

n Scope - Sets the initial definition of the project; input from sales cycle.

n Project Team Organization - Sets the who of the project. Standards & Procedures - Sets the why and how of the project.

Phase 2 - Business Blueprint - Reqs reviewed for each SAP Reference Structure & defined using CI Templates (use Q&Adb). Business Blueprint - This is the output of the Q&Adb and is the key document in Phase 3.

Phase 3 - Realization - Master Lists - Define business scenarios and R/3 transactions to be realized in the system. BPP - Bus Process Procedures representing R/3 transactions; used for unit testing & documentation. Planning - Defines how the configuration will be done and how it will be tested. Development Programs - Provides details of the external programming requirements. EU Training Material - End User training material and process documentation.

Phase 4 - Final Preparation Stress & Volume Tests - Plans for confirming the production hardware’s capabilities. Cut Over Plan - The details of how to move to the production environment and go live. EU Training - Delivery of the necessary levels of R/3 training prior to going live

Phase 5 - Go Live & Support: Ensuring system performance through SAP monitoring and feedback.



SAP AG 1999

ASAP Overview: Topics

ASAP Overview

UnitUnitUnit

TopicTopicTopic


ASAP Defined

Tools Availablein ASAP

ASAP Overview



SAP AG 1999

Overview

Define, organize, manage SAPimplementation project (ASAPmethodology)

Requirement analysis

Configuration (Customizing)

Transport

Document SAP implementationproject

•Administration•Roadmap•Question & Answer Database•Knowledge Corner•Accelerators to compliment tools

Business Blueprint (Q&Adb)Implementation Guide (IMG):•can be configured•reference to release•reference to organizationCopy function for organization unitsCustomizing Transport System

Implementation Assistant, Q&Adb, R/3,external modeling tools

Implementation Assistant, ASAP in R/3Implementation Assistant, ASAP in R/3

Implementation Assistant, ASAP in R/3Implementation Assistant, ASAP in R/3

ActionsActions ToolsTools

n Another important action not covered in this unit, is the creation of interfaces and enhancements. Here, the major tool is the ABAP Workbench.



SAP AG 1999

IA Project Area: Roadmap Add and Scoping

AcceleratedSAP Implementation Assistant

Roadmap

Activities

Tasks

Work Packages

Phase

Edit View

ADD...

Roadmap...

...By Scope

InScope

n Edit Roadmap Structure Items: It is possible to „scope“ and add new items to the Roadmap structure, so that the Roadmap can be tailored to project-specific requirements. Only the project manager can add or hide elements of the Roadmap.

n Setting Roadmap structure items in scope: SAP-delivered and user-defined items can be set out of scope.

n Adding new Roadmap structure items: For new user-defined Roadmap structure items, it is possible to assign the attributes Roadmap flavors (such as R/3, APO), Role (such as Business Process Team Lead), Subject area (such as Testing) and Scope.



SAP AG 1999

Activity - 2.5.1 Define Business Organization Structure

Tasks

Work Package - 2.5 Organizational Structure Definition

Phase - 2 Business Blueprint

l 2.5.1.1 Schedule Organization StructureWorkshop

l 2.5.1.2 Distribute Organization StructureGuidelines

l 2.5.1.3 Conduct Organization StructureWorkshop

l 2.5.1.4 Recommend and Approve Organization Structure

IA Project Area: Roadmap - Example

n In this example, the project has proceeded to Phase 2, Business Blueprint. Within this phase, the project team is about to begin definition of the organizational structure. As such, the project team would navigate within the Implementation Assistant to the point shown above.

n The activity level information generally consists of the purpose of the activity, general instructions on how to complete it, the trigger for starting this activity, the input that is used to complete the activity, the expected results in the form of outcome and output, and any templates or accelerators that can be used to complete the activity. The templates and accelerators, if available, will be linked and accessible from this page.

n The task level information generally consists of the purpose of the task, the suggested procedure, including steps, for completing the task, the expected results upon completion, the personnel responsible for performing the task, and any templates, accelerators or How Tos that can be used to complete the activity. The templates, accelerators and How Tos, if available, will be linked and accessible from the task page.



SAP AG 1999

Example: Tools/Accelerators

Task

l .....

l Conduct Organization Structure Workshop

l ....

Tools

n Q&Adb

w Organizational Questions

w Customer Input (CI) Templates

w Business Process Questions

w Issues Database

w Documentation

Accelerators

n Organization StructurePresentation

n Enterprise Modeling

n You can access ASAP accelerators from the tasks or from the alphabetical list of accelerators.



SAP AG 1999

IA: View

ViewViewSubjectAreas...

Roles...

Application ConsultantBusiness Process OwnerBusiness Process Team LeadBus. Process Team MemberChange Team LeaderChange Team MemberCross-Application ConsultantCustomer Project Manager….

Project SponsorSAP Consulting ManagerTeamSAP Project ManagerSAP ReviewerSAP Tech. ConsultantManagerSteering Committee MemberSystem AdministratorTechnical ConsultantTraining Coordinator

Project MngtConversion, Interfaces,EnhancementsBusiness Organization andProcessesConfigurationEnd User Training andDocumentationOrganizational Change MngtProject StandardsProject Team TrainingQualityReporting , FormsServicesSystem ManagementTestingDevelopmentAuthorization

View by Roles: View by Subject Areas:

Note: Not all roles are shown

n The View button allows you to specify role or subject area criteria, which tailors the content to be displayed.



SAP AG 1999

+

SAP Reference IMG

+

+

+

+

+

+

+

+

Implementation Guide for R/3 Customizing

+

Basis Components

...

Quality Management

Materials Management

Logistic-General

...

Financial Accounting

Cross-Application Components

Enterprise Structure

Global Setting

Customizing

Activities

n The R/3 Reference IMG contains all the Customizing Activities defined in the R/3 System.



SAP AG 1999

Customer Specific Configuration of the IMG

ProjectIMGs

ProjectIMG

Views

CustomizingTransactions

ProjectDocumentation

ProjectManagement

SAPReference

IMG

GenerateProject IMG

Views

CustomizingProjects

Manually

Generate

IMG-Link

Save

n For the realization, you can divide the scope of the Reference-IMG into different projects, which are assigned in turn to project IMGs.

n Once created, the project IMG is populated to produce one or more views. You can create views to improve the structure of the project IMGs. Use the project IMG to work on Customizing transactions, project and cross-project documentation, as well as project management information. Do this for each view and/or all views combined.

n With Release 4.6, the opportunity exists to create Project-Views via the IMG-Link. This functionality transports the Project Scope which is defined in the Question and Answer Data Base (Q&Adb) to the R/3 System. The Views generated by the IMG-Link contain those Customizing Activities assigned to the Processes that have been put in Scope in the Q&Adb.

n The IMG link does not create a Project IMG. The IMG link is used to generate and view process assigned, process non-assigned, or whole project IMG views of existing IMG projects.



SAP AG 1999

You are now able to:

l Identify ASAP’s role, main components, majorcontent, key deliverables, and pre conditionsfor effective utilization.

l Outline the purpose and functions for themajor tools used in ASAP

ASAP Overview: Unit Summary



SAP AG 1999

UnitUnitUnit

TopicTopicTopic


Phase 1Project Preparation

Phase 2Business Blueprint

Phase 3Realization

ImplementationRoadmap

Phase 4Final Preparation

Phase 5Go Live & Support

Implementation Roadmap: Topics



SAP AG 1999

l Explain the activities and tasks that areimportant in the Project Preparation phase ofyour implementation project

l Explain the activities and tasks that areimportant in the Business Blueprint Phase ofyour implementation project

l Explain the Realization Phase of the activitiesof the ASAP implementation

l Outline the Work Packages of Phase 4: FinalPreparation

l Outline the Work Packages of Phase 5: GoLive and Support

At the conclusion of this unit, you will be able to:

Implementation Roadmap: Unit Objectives



SAP AG 1999

UnitUnitUnit

TopicTopicTopic




Phase 3Realization




Overview Diagram: Implementation Roadmap (1)



SAP AG 1999

ProjectProject Procedures Procedures

QCQC

Technical ReqTechnical Req..PlanningPlanning

Initial ProjectInitial Project PlanningPlanning ProjectProject Kickoff Kickoff

Training ProjectTraining Project Planning Planning Phase Phase

Phase 1: Project Preparation - Work Packages (4)

n The purpose of this Workpackage is to formally announce to the company the initiation of the R/3 project, which includes the overall goals, detailed task plans, and processes. Consultants, steering committee, senior management, project managers from the company and SAP, and any other implementation partners must be involved. The kickoff meeting is focused on the company as a whole, while the project team standards meeting is focused on the project team.

n Activities

� Kickoff meeting

� Project team standards meeting.



SAP AG 1999

Define Project Mission Statement

Define Business Drivers

Identify Business Measurements

Identify Project Measurements

Develop the Change Charter

Assemble Project Charter Components

Approve Project Charter

Tasks

SAP Project

SAP Project Manager

Customermanagement

Project Charter

Accelerators:n Project Chartern Sample Project Charter

Create and Issue Project Charter

What?How?When?

Initial Project Planning

Initial Project Planning

n Define project mission statements: define the overall company goals and vision for the R/3 implementation.

n Define business drivers: identify specific company objectives and business drivers for initiating the R/3 implementation. Typical business drivers include: Improved inventory turnover, reduced shipping costs, improved customer service.

n Identify business measurements: document the implementation goals, and how they are used to measure the success of the project, specifically the business-related goals. Examples of business related goals are: Integration of business processes, reduction of on-hand inventories.

n Identify project measurements: document implementation goals, and how they are measured, specifically the project-related goals. Examples of project-related goals are: Target dates for completion of specific implementation phases or milestones, measurement of actual expense performance versus budgeted costs, completion of a specific deliverable(s).

n Develop the Change Charter: develop a comprehensive charter for the change project within the organization.

n Assemble project charter components: prepare a document that consolidates the mission statement, business drivers, business measurements, and project measurements.

n Approve project charter: reach agreement between company executive management, the project sponsor, and members of the project team on the project charter. It is important to have all members in agreement so that total commitment can be achieved.



SAP AG 1999

Define System Configuration Standards

Define Testing Strategies

Define Post Implementation Serviceand Support Strategy

Define System Authorization Standardsfor Project Team

Determine System Problems Standardsand Error Handling

Define Change Request Management

Define System Enhancement andModifications Approval Process

Define Upgrade Strategy

Define Implementation Standards & Procedures

ProjectProcedures

ProjectProcedures

n The purpose of this activity is to establish the overall implementation standards and procedures for the project. Some of these elements should be established by the technical members of the project team, and others by the business or functional members. All team members should have input to this process, and understand the basic procedures, once they have been defined. As with project management standards and procedures, it is important to address the implementation standards during Phase 1 and to establish clear guidelines. Some of the key issues to be defined are: Overall configuration standards for the project; initial system authorization standards; how system enhancements are handled; and how and when testing occurs.

n Prerequisites:

� Input: Project organization; R/3 implementation strategy.

n Result:

� Output: Configuration standards; end user training and documentation strategy; testing strategy; post-implementation support strategy; system authorization standards for the project team; system problems and error handling procedures; system enhancement and modification approval process.

� Outcome: Implementation standards and procedures are clearly defined and documented. They are input for the activity project team standards meeting.



SAP AG 1999

Motivate the individuals involved and bring them together as a team

Explain the implementation strategy, timeline, and project goals and objectives.

Clarify team member roles, responsibilities, and common objectives

Kickoff Meeting

Project KickoffProject Kickoff

n This milestone activity is a critical checkpoint that officially launches the R/3 implementation project to the entire company. Be sure to allow adequate time for questions and answers, as some issues could require clarification.

n Prerequisites:

� Trigger: Professional services agreement.

� Input: Project charter, implementation strategy, project organization, project plan.

n Result:

� Output: Kickoff meeting report; copies of presentation documentation; project charter; project team; organizational chart; project logistics and standards; project work plan; communication directory and standards.

� Outcome: Official start of the project; presentation of the input mentioned above; explanation for any issues or questions about the project from the kickoff meeting participants.

n This meeting should be conducted with high energy and should be attended by company senior management. A strong first impression is important to momentum.



SAP AG 1999

UnitUnitUnit

TopicTopicTopic




Phase 3Realization







SAP AG 1999

Project ManagementProject Management

Develop System Develop System Environment Environment

Organizational Change Management Organizational Change Management

BusinessBusinessOrg. StructureOrg. Structure

QCQC

BusinessBusinessProcess Definition Process Definition

Training Business Blueprint Phase Training Business Blueprint Phase

Phase 2: Business Blueprint - Work Packages (3)

n The purpose of this Work Package is to define the enterprise organizational structure using SAP organizational units, such as company codes and sales organizations.

n In conducting the organization structure workshop, several topics are discussed, including:

� What enterprise process areas and business processes will be used in the system

� What organizational units within the company will be affected by the implementation



SAP AG 1999

Schedule OrganizationStructure Workshop

Distribute OrganizationStructure Guidelines

Conduct OrganizationStructure Workshop

Recommend and ApproveOrganization Structure

Accelerators:n Organization Structure Presentation

n Structure Modeling with Structure Modeler

n Sample Scope Document

Tasks

1

1

SAP Reference Structure

Organization

Business Strategy

Define Business Organization Structure

Business Org. Structure


n The purpose of this activity is to prepare for business organization structure workshops to define the organizational structure of the company within the system. The organizational structure is established to give structure to the Logistic and Financial Enterprise Process Areas.

n Prerequisites:

� Input: Enterprise process area scope document (Sample Scope Document).

n Result:

� Output: Documented organization structure for the company.

� Outcome: The organization structure is signed off and is ready to be implemented.



SAP AG 1999

Associated Items 1

User Profiles

Unplaned Situations

1

1

1

1

1

1

1

1

1


QAdb

QAdb

QAdb

User

IssuesReport

Development

Basis

Training and Documentation

Cross - Application / User Roles

Business Processes

Master Data

General Settings

Organization

Business Strategy Business Analysis

Question

CI Template

BP Transaction

User Roles

Project Documentation

SAP Documentation

IDES Documentation

Associated Items

n The questions enable you to gather requirements on specific business scenarios and their processes. A Question may appear within several structures. The answer to a question on a specific occurrence within any structure is visible on all other occurrences using that question. While answers given to a question are visible at all occurrences, questions can only be answered and answers can only be changed at the current structure level. These questions are open-ended and promote the flow of information between you and the consultants who will configure your system. Using your answers as a guide, consultants define your company’s requirements in detail and adapt process models to reflect your company’s needs.

n The user roles enables consultants in the Blueprint phase to identify, adapt and describe SAP-delivered user roles based on project-specific requirements.

n The CI template sections form the heart of the business blueprint document. It is important to provide as much information as possible when entering your answers in these sections. In some cases the information may not be known at the Blueprint stage, if this occurs, it should be noted in the CI template answers. For example, when you enter the Authorization Considerations question during the Business Blueprint phase only high level information is available. As this changes, the Q&Adb should be updated with detailed authorization requirements.

n During the initial Q&Adb setup, you specified the path to SAP and IDES documentation. This documentation is available for view only and cannot be changed. If a SAP or IDES document is available for a selected function, the name of the document displays in the Associated Items box. Click the document to view it.

n You may add, view, or delete documentation to the Project Documentation folder in the Associated Items box. It is recommended to put all documents to the Project Documentation directory so that the document can be found in the Q&Adb directory.



SAP AG 1999

Scoping

Edit View Reports

...In Scope...

...Set In Scope...

3 Structure Item D

2 Structure Item B

2 Structure Item C


1 Structure Item A

3 Structure Item E


1 Structure Item A

2 Structure Item C

3 Structure Item E

n Before you begin answering questions, decide which structure items are valid and appropriate for your business. Setting these items In Scope, delimits the information gathering of the Q&Adb to your specific business. It is recommended to “scoping” top down along the Q&Adb structure.

n Any one or all hierarchy items can be set In scope by right-clicking on that item in the tree view and choosing Set In Scope.

n In Scope areas appear in yellow for easy identification.

n In Scope status can be removed from individual hierarchy items as necessary by clicking the checked Item Set In Scope menu item which removes the In scope status.

n If you would like to only see the items in scope, go to main toolbar and select View->In Scope. Only those areas that are In Scope will display in your tree structure.



SAP AG 1999

Organizational Structure


1 Organization

2 Procurement....

3 Controlling Area

2 Cross-application....

3 Company Code....

Business Analysis

Question

CI Template


SAP Documentation

IDES Documentation

Status

Information



n The Organization structure level contains items that describe the system organization structure in which framework the SAP system is configured. In the Q&Adb, questionnaires facilitate gathering requirements on the company’s structure and processes that allow an initial mapping of the company’s business to a proposed SAP organizational structure. The answers to the questions form part of the Business Blueprint.

n The second level contains the available enterprise areas (e.g. Sales and Distribution). It is not recommended that you change or enhance this level of the organizational structure.

n A third level further defines the organization (e.g., Sales area data).

n For each level you may set items in and out of scope.



SAP AG 1999


Develop System Develop System Environment Environment

Organizational Change Management Organizational Change Management

BusinessBusinessOrg. StructureOrg. Structure

QCQC

BusinessBusinessProcess Definition Process Definition

Training Business Blueprint Phase Training Business Blueprint Phase

Phase 2: Business Blueprint - Work Packages (4)

n The purpose of this Work Package is to define the company requirements based on SAP business processes, to provide the required functions. You must first define your organizational structure. The business process definitions create your Business Blueprint.



SAP AG 1999

BusinessBlueprint

Business ProcessQuestions

R/3 ReferenceStructure

INPUT OUTPUTBusiness Process

Definition

Technical AnalysisFunctionalSpecifications

OrganizationalStructure

MasterLists

Business AnalysisQuestionsCI TemplateBP Transactions

Business Process Definition

Business Process

Definition

Business Process

Definition

n After the definition of the organization structure, you define the business processes of the company in terms of the R/3 System.

n The Q&Adb is the tool supporting the definition of the business processes. You can use the CI (Customer Input) template and the business process questions within the Q&Adb to support the preparation and completion of the business process definition. For detailed analysis, you can access external tools for modeling the business processes via the Q&Adb.

n Generating the Business Blueprint gives you the company´s business process requirements in one document.

n Generating Business Process Master List gives you the business processes which are in scope for Customizing in the Realization Phase.



SAP AG 1999

General Settings and Master Data


2 Set Countries

2 Set Currencies....

1 General Settings

2 General Master Data

1 Master Data

3 Material Master....

2 General Master Data....

3 Serial Numbers....

Technical Analysis

Business Analysis

Question

CI Template

BP Transaction


SAP Documentation

IDES Documentation

Information

Status

Business Process

Definition

Business Process

Definition

n Result:

� Output: Completed general settings and master data questions in the Q&Adb and documented enterprise standards



SAP AG 1999

Edit View Reports

StatusStatus

MasterMaster Lists Lists

BPMLBPMLOSLOSLDLDLALAL

Business BlueprintBusiness Blueprint

BusinessBusiness Strategy Strategy

Scope DocumentScope Document

ReportsReports

--

Scope DocumentBusiness StrategyBusiness Blueprint All Organizational Structure General Settings Master Data Business Processes Cross-aplication User roles Training and Docu. DevelopmentMaster Lists Organizational Structure BPML Development List Authorization ListStatusIssuesUsers

-

-

-

-

Reports (Business Process Definition)

Business Process

Definition

Business Process

Definition

n Reports allows you to display project documentation in different forms, and creates a report structure in the Q&Adb.



SAP AG 1999

Tasks

SAPReference

IMG

Generate Project IMG

Accelerators:

n Sample Scope Document

n Working with Project IMGs

n ASAP IMG-Link

Data Scope Views Member Status

Country

Define Project Name

Cross ReferenceDoc Types TransportKeywords

Don‘t Generate Project IMG

IMG - Link

Manually

IMG-Link

Initialize IMG

Develop System Environment

Develop System Environment

n The purpose of this activity is to create the Implementation Guide (IMG ). It is important to create an IMG so that the Customizing process and documentation tasks are easier. The IMG is used as a reference at the last stages of business process definition, therefore you want to have this in place before beginning that Work Package.

n Use Project IMGs to do your project planning and control customizing work. When you set up your Project IMGs or Release projects, be sure to keep to the standards you defined in the Project procedures work package under the project documentation task for using status indicators, for scheduling, and for documentation.

n There are two methods of generating the Project IMG:

� The Manual creation of the Project IMG. This is the more common method, whereby consultants manually identify the components of the IMG that must be configured according to the project scope.

� The Automatic generation of the Project IMG from the ASAP Question & Answer database (Q&Adb). This is a new function that uses the scope settings within the ASAP Q&Adb and transfers them automatically into the R/3 project IMG. Please refer to the accelerator below for more information.



SAP AG 1999

IMG - Link


1 Structure Item A

2 Structure Item C

3 Structure Item E

Adminstration

Transfer Scope to R/3 System...

UserUser Maint Maint..

R3 Info

R/3R/3

Project

IMG


ProjectManagement

TransferScope

n 1. Set the scope in the Q&Adb During the Business Blueprint phase of the project, the project team undertakes a number of detailed workshops to define both the high-level scope and detailed scope. This scope is entered within the Q&Adb.

n 2. Create Project IMG in R/3 In order to transfer the Q&Adb scope to the R/3 System, it is first necessary to create a Project IMG through Project Administration in R/3. Specify a project name and description, select the countries and save the Project IMG.

n 3. Verify R/3 Login information in the Q&Adb Before initiating the transfer to R/3 it is important to make sure that the user’s parameters are set correctly to log on to the corresponding R/3 System.

n 4. Generate Project IMG based on the scope set in the Q&Adb The generation of the Project IMG will be derived from ASAP, based on the agreed scope. In order to transfer the Q&Adb scope to the R/3 System, select: Administration Transfer Scope to R/3 System Only the project manager is authorized to transfer the Q&Adb scope.



SAP AG 1999

UnitUnitUnit

TopicTopicTopic




Phase 3Realization







SAP AG 1999


QCQC

System ManagementSystem Management

Organizational ChangeOrganizational Change Management Management

Training Realization Phase Training Realization Phase

A-R-I-C-E,A-R-I-C-E, Forms Forms,, Archiving Archiving, ABAP, ABAP

BaselineBaseline Final Config.Final Config.

IntegrationIntegration

Phase 3: Realization - Work Packages (2)

n Baseline Configuration and Confirmation: During the Business Blueprint phase, the Identify Baseline Scope task divides relevant business and process requirements into two main blocks. The Baseline block comprises the priority requirements of the enterprise, ensuring that they can be implemented quickly.

� During Baseline configuration, work on processes that can be configured without programming or enhancements. Requirements that need programming or enhancements to the SAP system are addressed in separate work packages in the Realization Phase.

n Final Configuration and Confirmation: The purpose of this work package is to finalize the scope and configure your R/3 System.

� The Final configuration is an iterative process in which you set up your business requirements. You confirm that all your business requirements are met in the R/3 System. To make configuration easier, create two or more cycles. Each cycle, based on the value chains in the enterprise, includes the functions and processes you need. Depending on the scope of implementation, create an appropriate number of cycles (cycle 1, cycle 2, cycle 3 to through to cycle n). Configure these cycles sequentially.

� The Final configuration is a transformation process that expands the Baseline solution, defined during the Business Blueprint and Baseline configuration, through cycles (1 to n) until a solution is found to deliver.resulting in a solution that satisfies all stated business requirements.



SAP AG 1999

Tools for the R/3 Project Documentation

Business Navigator

SAPscript

IMG

Fiscal year

...

...

Financial accounting

Diagram Explorer (Intellicorp)

Aris for R/3 (IDS)

ERP Modeler (CASE wise)

Live Model ( Intellicorp)

ASAP Roadmap

n With the documentation for the ASAP Roadmap, SAP provides information about which documentation tools can be used for which project activities.

n The following tools are provided for the R/3 implementation:

� Implementation Assistant (e.g. Q&Adb, IssueDB) for request analysis, problem documentation and end-user and Project documentation

� External modeling tools for graphic process modeling (e.g. Micrografx, Visio, Intellicorp, IDS/ARIS)

� IMG -Documentation for customizing settings:

MS Word or SAPScript editors are used for documenting the customizing settings

Forms are available for MS Word documentation

It is possible to create multiple documents for each setting

The documentation is:

Cross-client

Transportable



SAP AG 1999

Baseline ScopeLevel 1 Level 2 Level 3

Linking the Blueprint to the Realization Phase

BusinessBlueprint

Cycle Scope

Level 1 Level 2 Level 3

The Business Blueprint is Always the Source Document

Reference

Reference

Development Master List

Level 1 Level 2 Level 3Authorization Master List

Level 1 Level 2 Level 3Organization Master List

Level 1 Level 2 Level 3Business Process Master List

Level 1 Level 2 Level 3

Integration TestLevel 1 Level 2 Level 3

GenerateWorksheets

n In Phase 2, the business requirements were defined in the Q&Adb along with the project scope. The Master Lists reflect the definitions defined in the Business Blueprint Document. The various worksheets used to control and drive the configuration and confirmation process are derived from those Master Lists.

n In all cases where there is disagreement about business process definition, the resolution is found in the Business Blueprint Document. The Blueprint is the reference source for answering all questions about requirements definition in Phase 3, Realization. As such, if there are changes, the Blueprint Document must be updated.



SAP AG 1999

Business Process Master List

IntegrationCyclesBaseline

Business Process Master List Check columns

7

7

7

Bas

elin

e

Cyc

les

Inte

grat

ion

7

7

Level 2 - Enterprise Process Area A

Level 3 - Scenario Process AA

Level 4 - Process Group AA00

Level 5 - Business Process AA10

Level 6 - BPP AA11

Level 5 - Business Process BB10

Level 1 - Business Process 7 7 7

… to createassociatedworksheet

… to createassociatedworksheet

Selectprocess, 7...Selectprocess, 7...

n The BPML, which is generated in the Q&Adb, is the central data repository. It contains all R/3 business processes and transactions that represent the scope of the project. Project scope was determined in the Business Blueprint Phase, the BPML is also generated then, prior to commencement of Realization Phase.

n As the central data repository, the BPML is used to feed required business process information to the working documents (worksheets) used to specify, manage, monitor and control the work packages of:

� Baseline Configuration and Confirmation

� Final Configuration and Confirmation (cycles)

� Final Integration Testing.

n During project scope definition in the Business Blueprint Phase, adjustments (Process variants) to R/3 business processes may have been made to meet customer needs e.g. a distinction between a goods receipt with and without bar code recognition might be required in which case a process variant would have been created. In addition, business process owners will probably have been identified. Applications consulting will also have defined, with the customer, the order of realization. All these events of the Business Blueprint Phase will have been reflected in the Master List illustrated in this slide. They will now be reflected in subsequent BPML worksheets derived from this Master List in Realization Phase.



SAP AG 1999

Baseline & Cycle Worksheets

CyclesBaseline

Baseline/Cycle Scope

Documentation Links

R/3 Links

Responsibilities

Configuration Dates

Testing Dates

Level 1, Level 2, Level 3, Level 4, Level 5, Level 6

CI, BPP, Case Proced, Test Scenario, Related Files

Transaction Code, IMG

Config, Writer, Tester

Plan, Actual

Plan, Actual

Status Doc’d, Config’d, Tested, Retest, Approved, Hold

n Baseline / Cycle Scope Level 1 - Structure item from Q&Adb Level 2 - Corresponds to Enterprise area level for business process Level 3 - Corresponds to Scenario level for business process Level 4 - Corresponds to Process Group level for business process Level 5 - Corresponds to Business Process level for business process Level 6 - Corresponds to Business Process Procedure level for business process

n Status - The current status of the particular level in the scope

n Responsibilities Config - Person responsible for configuring the system Writer - Person responsible for writing the documentation Tester - Person responsible for testing

n Configuration Dates Plan - Planned completion dates for the configuration of the defined level Actual - Actual completion dates of the configuration

n Testing Dates Plan - Planned completion date for testing the defined level Actual - Actual completion date of the testing

n Comments column included for notes and additional information documentation



SAP AG 1999

The ASAP Processes in the Work Packages

ConductScenarios

PrepareScenariosRefine

Configure

Test

CreateTest Plan

CreateConfig.

Plan

Define Test Cases

For Baseline / Final Configuration & Confirmation

n This process for configuration and confirmation is used in both of the Work Packages of Baseline Configuration & Confirmation and Final Configuration & Confirmation.

n While the process defines the flow of work through the Work Packages, the Implementation Assistant defines all the Tasks necessary to complete the configuration and confirmation work.



SAP AG 1999

Final Config. Workflow: Cycle 1- n

CONFIGURATION

TOOLSTOOLS

TOOLS

PROCESS

CreateConfig. Plan

PROCESS

ConfigureFinal Scope

PROCESS

CreateTest Plan

PROCESSDefine Test

Cases

PROCESS

Test FinalConfig.

TOOLS

Cycle PlansUnit TestTest ScenarioCase Proced.

TOOLSCycle Plans Status Actual DateUnit TestTest ScenarioCase Proced.

PROCESSPrepare

Scenarios

PROCESS

TestScenarios

TOOLS TOOLS

TOOLS

Cycle Plans Tester Plan Date

Test ScenarioEnd-To-EndLevel 3

Cycle Plans Configurator Plan DateConfig. Cases Level 4

Cycle Plans Status Actual DateBPP - Complete

CONFIRMATIONCONFIRMATIONCONFIGURATIONCONFIGURATION

OK?NO YES

Kickoff MtngDocumentation

n Process:

� Create Configuration Plan for Final Scope - Generate Cycle Plans (C1 to Cn); define cycle “n” plan based on level 4 process groups.

� Configure Processes and Functions (cycle 1-n) - Configure and document; verify configuration. Maintain cycle plan with results. Update BPPs as needed.

� Define Final Scope Test Cases - Create and/or change test cases as required. Test cases used to determine if the final configuration supports the business requirements.

� Create Test Plan for Final Scope - Plan resources and times for testing.

� Test Final Configuration (Cycle 1-n) - Conduct workshops to prepare, enter setup data and execute tests to verify. Update cycle plan with results. If configuration confirmed, move to next cycle. If configuration not confirmed, review configuration and retest.

� Prepare Final Confirmation Scenarios - Review existing test scenarios, confirm important business processes, write new scenarios as needed and update Cycle Plan.

� Perform Final Confirmation Scenarios - Business process owners exercise the required scenarios and document the results.



SAP AG 1999

Customer Specific Configuration of the IMG

ProjectIMGs

ProjectIMG

Views

CustomizingTransactions


ProjectManagement

SAPReference

IMG

GenerateProject IMG

Views

CustomizingProjects

Manually

Generate

IMG-Link

Save

n For the realization, you can divide the scope of the Reference-IMG into different projects, which are assigned in turn to project IMGs.

n Once created, the project IMG is populated to produce one or more views. You can create views to improve the structure of the project IMGs. Use the project IMG to work on Customizing transactions, project and cross-project documentation, as well as project management information. Do this for each view and/or all views combined.

n With Release 4.6, the opportunity exists to create Project-Views via the IMG-Link. This functionality transports the Project Scope which is defined in the Question and Answer Data Base (Q&Adb) to the R/3 System. The Views generated by the IMG-Link contain those Customizing Activities assigned to the Processes that have been put in Scope in the Q&Adb.

n The IMG link does not create a Project IMG. The IMG link is used to generate and view process assigned, process non-assigned, or whole project IMG views of existing IMG projects.



SAP AG 1999

+

SAP Reference IMG

+

+

+

+

+

+

+

+

Implementation Guide for R/3 Customizing

+

Basis Components

...

Quality Management

Materials Management

Logistic-General

...


Cross-Application Components

Enterprise Structure

Global Setting

Customizing

Activities

n The R/3 Reference IMG contains all the Customizing Activities defined in the R/3 System.



SAP AG 1999

Working with the Project IMG

R/3

IMG for R/3 Customizing

Keywords

Note Types

General

Memo

Employee

Status

Activity

Project Name

Customizing: Edit Project

My Customizing Worklist

Manage Worklist

OrganizationalStructure List

BusinessProcessMaster List

Project IMG Procurement

Project IMG Sales

n During Baseline and Final configuration you make the necessary Customizing settings using ASAP in R/3, Customizing, using either the BPML, the IMG link, or a manually generated project.

n The system displays the data for the relevant view (if you use IMG links) or project (if manually generated), so that you can edit them

n On the left of the screen area, you can see the IMG and Customizing activities.

n On the right of the screen area, you can see the text of the Customizing activity you have selected. Underneath it, you can see the general project data (start date, due date, and so on) and the employees and keywords assigned to the project. At the bottom, the system displays the IMG project document types for the Customizing activity documentation.



SAP AG 1999

Global settings

Countries

Currencies

Calendars

l Conceptl Recommendationsl Requirementsl Activityl WinHelp

l Status/activity datal Schedulingl Resourcesl Microsoft Project interface

ProjectManagement

l Open Customizing transactions

Activities

l Efficiently organized using notesl Use Microsoft Word

ProjectDocumentationSAP Documentation

•The IMG contains documentation for each activity. •The activities can be carried out directly.•Functions for project management and project documentation are available.

IMG

IMG: Tasks

n The IMG contains all Customizing activities you need to implement application components.

n You can create Customizing projects in an SAP System, to help structure and manage an implementation project. You can also record cross-project documentation.

n You can create an IMG for each project.

n From a Project IMG you can work on Customizing transactions, project documentation, cross-project documentation, and information on project management.



SAP AG 1999

Project Management

Basic DataBasic Data

Person responsible: __________Project language: __________

Planned datesStart: 10.01.99End: 04.30.00

Actual datesStart: ______End: ______

Project ScopeProject Scope

Application components

— 9 Financial Accounting— 9 Controlling— 9 Logistics – General— 9 Sales and Distribution— 9 Materials Management— W Quality Management— W Plant Maintenance— W . . .

Project Team MembersProject Team Members

ABC Mrs. Andrea AlbertXYZ Mr. Mike Miller

Project ViewsProject Views

l All mandatory activitiesl All critical activitiesl Activities for Release 4.6l Manual selection 1

Project StatusProject Status

01 Standard unchanged02 In process03 Test phase04 Completed05 Productive



SAP AG 1999

Integration Test 1 (IT1)

Sales

Production

Purchasing

Salesorder

SOP MPS MRPPlannedorder

Produc-tionorder

Delivery CustomerBilling

Shopfloorcontrol

Requi-sition

Vendorselection

Purchase order

Goodsreceipt

Invoice verifi-cation

Resource controlling

Logistics controlling Sales, Production, Purchasing, Warehouse

CustomerOrder Customer

Payment

VendorPayment

InventorySourcing

PresalesActivity


IT1 focuses on the internal integration testing

Final Integration

Testing

Final Integration

Testing

n The purpose of the first cycle of integration testing is to check all cross functional integration points (limited or Focused Drill-down Scenarios) for high frequency and impact business processes, and to finalize the entire system configuration. The focus is testing that data crosses from one function (SAP module) to another. ‘Focused Drill-down scenarios' was also the method used during Final Configuration where many iterations of different cases were processed quickly.

n Examples of integration points are:

� Creation of a delivery note to be passed to MM (Materials Management) for warehouse processing

� Running of MRP (Materials Resource Planning) in MM to automatically generate production orders in PP (Production Planning)

� Creation of customer billing documents in SD (Sales & Distribution) to be passed to FI (Financial Accounting).



SAP AG 1999

Goal

•• Simulate theSimulate the live live operation of the business operation of the businessincluding remote locationsincluding remote locations

•• VerifyVerify R/3 R/3 solution seamlessly meets the solution seamlessly meets thebusiness needbusiness need

Test is process oriented and conducted by Business Process owner

Trigger: Successful Final Configuration testApplication Development complete

Inputs: Business Process Master List Test Scenarios Development List

Overview of Final Integration Test

n Like Final Configuration and Confirmation of which it is the extension, Final Integration Test involves Test Case playback. The goal is to examine the cross functional and key integration points across the business processes followed by periodic processing and development. It is a simulation of live operations.



Exercises

Unit: Implementation Road

Topic: Customizing Projects

At the end of this exercise, you will be able to:

• Assign a project or a view as your standard project

• Obtain an overview of the definition of a project

• Work with a project implementation guide

Your company has decided that your group is to use a separate project for implementing Logistics. Therefore, Project 200 has been created for Logistics and an additional view for Materials Management. You will use this project to perform configuration work from now on.

1-1 Project Management

1-1-1 You can define the details of individual projects in Project Management. Find out the validity period of Project 200.

______________________________________________________

1-1-2 Before starting work on the project, find out about the status values that you can use to document the progress of work on your project.

______________________________________________________

______________________________________________________

______________________________________________________

1-1-3 Which employees are assigned to this project?

______________________________________________________

______________________________________________________



1-2 Standard Projects and Project Work

1-2-1 Maintain your worklist. Copy Project 200 and the view “LO550_Materials Management” to your worklist.

1-2-2 Define view “LO550_Materials Management” as the standard project for your Customizing activities so that you can access the Implementation Guide more quickly. Test this assignment by calling up the Edit Project function again.

______________________________________________________

______________________________________________________

1-2-3 In the Implementation Guide for your project, find out what the individual icons mean. To do this, you expand the General Settings node.

1-2-4 Define for your view that the system is to display the online documentation in SAPscript and that you want to be made aware of release notes immediately.

1-2-5 Use the cursor to choose the Materials Management node and search for the character string Purchasing groups. Choose Create Purchasing Group. Read the online documentation and any release notes there.

1-2-6 Define a new purchasing group, L##, that you will work with during this course. In a second session, enter this purchasing group in your user parameters (Parameter ID EKG) as the default value for future work.

1-2-7 What status does the activity Create purchasing groups have?

______________________________________________________

1-2-8 Complete the Standard customer note to inform all project team members of the changes that you have made.



SAP AG 1999

UnitUnitUnit

TopicTopicTopic




Phase 3Realization







SAP AG 1999


TrainingTraining

Detailed Detailed Project Project PlanningPlanning

System ManagementSystem Management QCQCCutoverCutover

Phase 4: Final Preparation - Work Packages (5)

n Activities:

� Perform Cutover to Production System

� Final Approval for Going Live



SAP AG 1999

ConductConductPrePre-Go-Live-Go-Live

End End UserUserTrainingTraining

Training: Goal and Content

Ensure thatEnsure that all end all end users are adequately users are adequatelytrained priortrained prior to to the Go the Go Live date Live date

Phase 3Training Realization Phase Phase 4

Define, Developand FinalizeTraining &

DocumentationConent

• Finalize logistics for training and the end user training schedule

Develop Templates,Standards and Review

Process

• Conduct end user training• Obtain end user training evaluation data• Track attendance

Define and ImplementEvaluation and

Improvement Process • Analyze end user training evaluation data& implement improvements

• Identify post go-live trainingrequirements

Conduct End User Training

Evaluate Training Effectiveness& Implement Improvements

Implement Training Logistics Plan

n End user documentation and training was developed in Phase 3. This included:

� setting the standards and review process for training content and documentation development, in addition to defining an evaluation and improvement process

� denoting power and other users in order to define, with the help of the training and development plan, the necessary training for production.

n The purpose of the Work Package here in Phase 4, is to finalize these preparations from Phase 3, verifying and adjusting the user training materials, and to ensure appropriate consideration of all logistic issues.

n Considerations in the logistics area include planning of training facilities, and producing copies of the end user documentation and other training material.

n Important: End user training and the preparation of training material are often the most time consuming and costly aspect of the system implementation. Changes in the procedure can influence considerably the time and costs of an R/3 implementation.



SAP AG 1999

Cutover Activities

FinalApproval Outcome

All SAP System aspects and supportorganization is approved and theproduction system is released

Inputs

n Production support &cutover plan

n End user training plan

n Test plan(s)

n Conversion check list

n Data transfer list

n Interface check list

n System administration

n End user documentation

Tasks

n Approve the ProductionSystem

n Secure ProductionEnvironment

n Verify Users are Ready



SAP AG 1999

Transport

SAP System

DevelopmentCustomizing

SAP (Targ.)System

Production

SAP System

Client zxxzxx

Client yxxyxx

Client xxxxxx

XXX

DevelopmentCustomizing

Training

automaticsystem settingrecording

automaticsystem settingrecording

automatic

system setting

recording

automatic

system setting

recording

Tool

CustomizingTransportSystem

ClientCopy

Function

n The Customizing Management System (CMS) manages the transport requests in the R/3-System in relation to an assigned Customizing Project.

n In the CMS, you can use the transport requests to copy SAP objects from one system, such as the development system, to a target system, such as the production system.

n You can also use the client copy function to copy SAP objects from one client (development client) to another client (training client) of the system as defined by a transport request.

n The system settings of the Customizing transactions are automatically recorded in transport requests. It is assumed that the client has been set correctly.



SAP AG 1999

UnitUnitUnit

TopicTopicTopic




Phase 3Realization







SAP AG 1999

Workflow in Work Package Go Live and Support

Provide supportto SAP Users and

to optimizesystem

performance

ProductionSupport

ProjectEnd

Post Go-LiveActivities

SystemTuning

Continuous ImprovementGo Live and Support

Officially closethe project

Support R/3System users

after the project isin productiveoperation and

develop long termsupport strategy

Improve systemperformance

End of ProjectEnd of Project



SAP AG 1999

Help Desk

Customer First Line SupportPower Users

IT StaffConfigurators

ABAP Programmers

HardwareVendor

DatabaseVendor

RemoteConsulting

EarlyWatch

End Users

Hardware Problem

Software Problem

Security Problem

Knowledge ProblemSystem

PerformanceProblem

Providing Production Support

SAPNet - Web FrontendSAPNet - R/3 Frontend

n It is important that whenever a problem arises, end users know who to contact, and how. The Help Desk is particularly important in the first weeks after Go Live, but you require Help Desk support throughout the production life of your SAP system.

n The Help Desk is a single point of contact with access to internal first level support for hardware, network, operating system, database, training, and application system problems.

n First level support personnel must not only possess special knowledge of these areas, but must also have company-specific knowledge concerning organization and processes.

n SAP services including ‘SAPNet’, Remote Consulting, and Early Watch are available resources to assist the internal production support team with problem resolution and avoidance.

n Coordination and co-operation with SAP and SAP Partners further expands the network of support for problems that cannot be solved internally by the Help Desk and First Level Support.

n Additional support is available to value contract customers who participate in the Customer Competence Center (CCC) program.

n Note that SAP has renamed its Online Service Systems (OSS) to: SAPNet – R/3 Frontend (formerly: Online Service System (OSS); and SAPNet – Web Frontend (formerly: SAPNet). This renaming reflects the ongoing integration of all SAPNet – R/3 Frontend functions into SAPNet – Web Frontend.



SAP AG 1999

l Problem requests

l Notes

l Hot News

l Online corrections

l Service requirements

l SAP software change registration

l Training details

l Project milestones for service

l Maintenance of Customer Master Data

Service

FunctionsFunctions

SAPNet - R/3Frontend

Partner

CCC = Customer CompetenceCenter

SAP /Branch

Customer/ CCC

or

SAPNet - WebFrontend

n CCC - a Customer's own, R/3 focused, internal support linked to SASupport Services. Refer to the Implementation Assistant under Implementation Accelerators for the accelerator - Customer Competence Center (CCC) Program.

n SAPNet - R/3 Frontend (formerly Online Service System (OSS)) provides the infrastructure for SAP's R/3 Service & Support and is the primary medium for problem management. It is the technological link between customers, SAP partners and SAP. Beyond this, SAPNet - R/3 Frontend provides access to valuable information about known problems and helps you resolve them on your own or with the help of the SAP Support Team. You have free access to SAPNet - R/3 Frontend wherever you are 24 hours a day.

n SAPNet – Web Frontend is SAP’s Internet/extranet solution. The features of the SAPNet – R/3 Frontend are being migrated consecutively into SAPNet – Web Frontend. The following are examples of tasks that can now be performed via SAPNet:

� Searching for SAP information

� Searching for R/3 notes

� Downloading SAP patches

� Requesting new SAPNet users

� Requesting SSCR keys.



SAP AG 1999


Implementation Roadmap: Unit Summary

l Explain the activities and tasks that areimportant in the Project Preparation phase ofyour implementation project

l Explain the activities and tasks that areimportant in the Business Blueprint Phase ofyour implementation project

l Explain the Realization Phase of the activitiesof the ASAP implementation

l Outline the Work Packages of Phase 4: FinalPreparation

l Outline the Work Packages of Phase 5: GoLive and Support



Solutions

Unit: Implementation Road

Topic: Customizing Projects

1-1 Project Management

1-1-1 Go to the Project Management function. Choose Tools → AcceleratedSAP → Customizing → Project Management. Display the general data on Project 200.

Start: 01.01.1999 End: 12.31.2009

1-1-2 Display the status values for Project 200.

LO-ERLEDIG Processing completed LO-FRAGEN Open issues LO-NACHARB Activity incomplete LO-PRÜFEN Check settings LO-TRANSP Transport settings LO-UNBENUT Function not used LO-UNVERÄN Setting transferred from SAP

1-1-3 Display the project team members.

GRUNEWALDK Karin Grunewald KUNITZ Roger Kunitz

1-2 Standard Projects and Project Work

1-2-1 Go to the Edit Project function. Choose Tools → AcceleratedSAP → Customizing → Edit Project. Choose Add to worklist and copy Project 200 and the view “LO550_Materials Management” to your worklist.

1-2-2 Select the view “LO550_Materials Management”. Choose Edit → Default project or project view → Define. Leave the Edit Project function and call it up again. The view “LO550_Materials Management” appears immediately in the Implementation Guide.



1-2-3 In the structure, the system displays icons for the following functions: IMG documentation Execute activity Status maintenance

1-2-4 On the menu bar, choose: View → Text display → SAPscript and View → Release notes → Show icons.

1-2-5 A hit list appears and you can choose the activity required.

1-2-6 Choose Create Purchasing Group. Add a new entry.

1-2-7 LO-TRANSP – Transport settings

1-2-8 Choose Standard customer note and maintain the note.



SAP AG 1999

Section: Cross-Functional Customizing in MM



SAP AG 1999

Unit Purchasing

Unit Pricing

Unit Inventory Management

Unit Global Settings

Unit MM OrganizationalLevels: BusinessScenario

Unit Master Data in MaterialsManagement

Content: Cross-Functional Customizing in MM

Preface



SAP AG 1999

Global Settings

l Countries

l Currenciesl Units of Measurement

l Factory Calendar

Contents:



SAP AG 1999

Global Settings: Unit Objectives


l List the settings for countries and currencies thatare relevant for Materials Managementtransactions

l Configure a new unit of measurement using theIMG

l List the steps that are necessary to create afactory calendar



SAP AG 1999

l As part of a global implementation, you havebeen asked to review some of the cross-application tables to verify that they arecompletely maintained from the MM perspective.

Global Settings: Business Scenario

n The MM project team has already identified additional units of measurement that are required for some Purchasing transactions. You have been asked to add these additional units of measurement to the necessary tables.



SAP AG 1999

Date: MM/DD/YYYY DD.MM.YYYY DD.MM.YYYY

Decimal: 100.00 100,00 100.00

Tax schema: TAXUSJ TAXD TAXGB

Address layout: 004 015 006

Postal code: 10 digit 5 digit 9 digit

Check: Optional entry Mandatory entry Optional entry

Country Settings

n Check that all the countries in which you have business partners are defined in the R/3 System. The information that you need to enter for each country includes:

� General data

� Foreign trade attributes

� Further check data (postal code, bank information, tax information and so on)

The R/3 System checks this data when you maintain the master data for vendors.

n These country settings are valid for all application components.



SAP AG 1999

Currencies

ISO codes USD GBP EUR ITL CHF

Decimal 2 2 2 0 2places

Rounding - - - 10 0.05

n The R/3 System usually uses the exchange rates stored in exchange rate type M for converting the currency when posting and clearing documents. There must be an entry in the system for this exchange rate type. The exchange rates are valid for all company codes.

n If you do not manually enter an exchange rate in a purchase order, the R/3 System uses the current exchange rate for exchange rate type M from the currency exchange rate table.

n In Customizing for FI, you can specify which exchange rate type should be used for each document type.



SAP AG 1999

Currency Conversions

Exchange rate typesExchange rate types

ER type Description Base currency Inv. EMU FixedM average rate - - - -EURO EMU EUR - X -

Conversion factorsConversion factors

ER type From To Valid from Factor Factor Diff. ER typeM ITL DEM 01.01.1999 1,000 : 1 EUROM USD GBP 01.01.1800 1 : 1

Exchange ratesExchange rates

ER typeValid from Quantity Factor From Factor Price ToEURO 01.01.1999 1.95583 x 1 DEM = 1 x EUREURO 01.01.1999 x 1 EUR = 1 x 1.95583 DEM

n You use the exchange rate type to store currency conversion rates for different purposes, but relating to the same date, in the R/3 System. You must not delete the entries that are already there.

n If the R/3 System is to perform exchange rate conversions between a large number of different currencies, you can simplify exchange rate maintenance by specifying a base currency per particular exchange rate type. Then you only need to specify the exchange rates of all currencies in relation to the base currency for the exchange rate type concerned. The R/3 System then converts all currencies in two steps, using the base currency.

n In accordance with legal requirements, the base currency (EUR) must be defined as the From currency for currency conversions within the EMU (European Monetary Union). To do this, you set the indicator in the field BCurr = From.



SAP AG 1999

Unit of measurement 2ounce

Unit of measurement 1ton

SI unitKG = kilogram

Conversion toSI unit

1.000 : 1

Conversion toSI unit

567 : 20.000

Dimension Ae.g. mass

Units of Measurement – Conversion Using SI Units

n You can use dimensions to facilitate conversions between different units of measurement.

n A unique SI unit is defined for each dimension.

n SI = Système International des Unités (international system of units).

n This is a system of internationally standardized units. These can be reduced to seven base units by grouping units together.

n In addition to the internal key for a unit of measurement, there are two language-dependent external keys (with corresponding descriptions). You must not change the internal key for the units of measurement supplied in the standard system.

n The maintenance of factors for conversion into the SI unit of the relevant dimension for units of measurement with the same dimension allows the R/3 System to carry out all conversions between these units of measurement.

n In the standard system, the entry AAAADL is predefined in the field Dimension for non-dimensional units of measurement.

n Before you can use a unit of measurement (for example, in purchasing transactions) you must set the indicator allowing it to be used as a commercial unit.



SAP AG 1999

Plant 1000:

Factory calendar 01

DefinitionFactory calendar ID: 01Public holiday calendar ID: 08Definition of working days in the weekSpecial rules

Definitionpublic holiday 1

Definitionpublic holiday 2

Definitionpublic holiday n

. . .

DefinitionPublic holiday calendar ID: 08Public holiday 1. . .Public holiday n

2.2.

1.1.

3.3.

4.4.

Maintaining and Assigning Factory Calendars

Maintainpublic holidays

Maintain publicholiday calendar

Maintainfactory calendar

Assignfactory calendar

n Factory calendars are used in several functional areas (for example, for lead-time scheduling, capacity planning, MRP, sales and distribution).

n The factory calendar specifies whether or not each calendar day counts as a working day.

n Factory calendars are generated in various steps and can be assigned to the plant or to individual work centers.

n You can use special rules to make allowance for company holidays and such in a factory calendar.

n The calendars are stored in a main memory buffer for the entire validity period (R/3 System parameter for buffer size: ‘zcsa/calendar_area’).

n You do not need to activate the calendar.

n Caution! Calendars are defined on a client-independent basis.

n The R/3 System generates change documents when you change the calendar.

n The R/3 System synchronizes the calendars if your company is using more than one application server.



SAP AG 1999

Global Settings: Summary


l List the settings for countries and currenciesthat are relevant for Materials Managementtransactions

l Configure a new unit of measurement using theIMG

l List the steps that are necessary to create afactory calendar



Exercise Data Sheet

Key to Icons in Exercises and Solutions

Exercises

Solutions

Objectives

Business scenario

Hints and Tips

Warning or Caution

There may not be sufficient time to work through all the exercises during the course. The exercises are intended to be additional examples that can be used, as required and time permitting, during the course. Attendees can also use these exercises after the course to consolidate what they have learned.

Data Used in Exercises

Type of Data Data in Training System

Material T-T1## Raw material

Material T-T2## Material to be provided

Material T-B1## Subcontracting material

Material T-RB9## Split valuation

Own material 1

Own material 2

Own material 3

Vendor T-L05A##, T-L05C##, T-L05D##

Cost center 1000

New account assignment category



G/L account 400550

Customizing project 200



Exercises

Unit: Global Settings

Topic: Global Settings


• Check the global settings in the SAP Implementation Guide

• Make settings for currencies and calendars

• Define a new unit of measurement

As subproject leader for the Logistics applications, you are also responsible for global settings. You have to represent the interests of Logistics in a general round of discussions. One issue is that analysis of your supply chain has revealed that you require a new unit of measurement.

1-1 Global Settings

1-1-1 Is the following statement true or false? Give reasons for your answer.

“You can make the country settings for Financial Accounting independent of the country settings for Logistics.”

______________________________________________________

______________________________________________________

1-1-2 Is the following statement true or false? Give reasons for your answer.

“When determining the exchange rate for foreign currencies in purchase orders, the system always uses exchange rate type EURX.”

______________________________________________________

______________________________________________________



what Exchange rate types are used for the following currency codes when determining exchanges rates?

– ITL converted to DEM – DEM converted to USD – USD converted to CAD

1-1-3 Specify whether the following definitions are client-specific or cross-client. Give reasons for your answer.

The definitions for public holidays and calendars are:

______________________________________________________

Assignment of a factory calendar to a plant or a work center in PP is:

______________________________________________________

1-1-4 Your company is planning to use the factory calendar with the ID “01” for the procurement process and to determine delivery dates.

Find out about this calendar:

– Which public holiday calendar has been assigned?

– Are there any special rules for this year?

– Which public holidays are defined for May this year?

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

1-2 Units of Measurement

1-2-1 Define a new ISO code, Z##, with the description “##-Bundle” for your new unit of measurement. Translate the language-specific description into German as “##-Packung”.

1-2-2 Define a new unit of measurement without dimension. Use the internal key P## , and use P## as both the commercial and technical display format. Enter the unit of measurement long text GR##-Bundle and the unit of measurement short text GR##-BU. This unit of measure should be available for commercial transactions. Assign the ISO code Z## to it. Specify that no decimal places are used.

______________________________________________________

______________________________________________________

______________________________________________________



1-2-3 Can you specify the following conversion between the units of measurement Piece and Bundle so that it applies globally?

12 pieces = 1 P##

______________________________________________________

______________________________________________________

______________________________________________________

1-2-4 Test the new unit of measurement and the translation that you maintained as well, by creating a purchase order.

Place an order with vendor T-L20A## using the new unit of measurement P##. Use purchasing organization IDES Deutschland, plant 1000 (Hamburg) and material group 001 (metal processing).Order 100 pieces of a consumption material (that is, a material without a master record) for cost center 1000. The order price is 50 UNI per P##.

Select the print preview and check that the short text GR##-BU is visible on your purchase order.



Solutions

Unit: Global Settings

Topic: Global Settings

1-1 Global Settings

1-1-1 This statement is incorrect, the global settings apply for all applications.

1-1-2 This statement is incorrect. Exchange rate type M is used in Purchasing. Depending on the two currencies concerned (“from” currency and “to” currency) and whether they belong to the EU or not, exchange rate type M is replaced with a different exchange rate type (EURO or EURX).

- ITL and DEM: Exchange rate type EURO - DEM and USD: Exchange rate type EURX - USD and CAD: Exchange rate type M

1-1-3 The definitions for public holidays and calendars are not client-specific. Changes to public holidays, public holiday calendars, and factory calendars are visible in all clients.

Assignment of a factory calendar to a plant or a work center in PP is client-specific. Plants and work centers are defined at client level and therefore the characteristics of the plants and work centers can only be specified on a client-specific basis.

1-1-4 Choose General Settings → Maintain Calendar. Factory calendar “01” uses public holiday calendar “08”.

The validity period for the factory calendar is always within the validity period for the public holiday calendar.

You can display the public holiday in May by calling the function Public holiday calendar → Display year. Factory calendar “01” does not contain any special rules.

1-2 Units of Measurement

1-2-1 Choose General Settings → Check Units of Measurement and ISO codes. Add a new entry, Z##.

(*) On the initial screen for maintaining units of measurement, choose Edit → Translation and language DE.

1-2-2 Choose Units of measurement (no dimensions) and add a new entry, P##. Assign ISO code Z##. Select the indicator Commercial unit.



1-2-3 The language-specific texts (abbreviations and unit of measurement descriptions) must be translated for the internal key (P##) for the new unit of measurement.

You can maintain the translation by logging on to the system in German and calling the Customizing activity Allgemeine Einstellungen → Maßeinheiten überprüfen, or by choosing Check Units of Measurement → Goto → Translation.

1-2-4 The units of measurement Piece and Bundle both have no dimensions. The conversion between these two units of measurement can only be specified in the application (such as material master, info record, purchase order).



SAP AG 1999

MM Organizational Levels

l Purchasing Organizationsl Plant and Storage Locations

l Relationships Between Organizational Units

Contents:



SAP AG 1999

MM Organizational Levels: Unit Objectives


l List the most important functions of the MMorganization structures

l Identify the relationships between the MMorganization levels and their environment

l Configure the Logistics (MM) organizational levelsin the Implementation Guide

l Use the plant copying and checking functions



SAP AG 1999

MM Organizational Levels: Business Scenario

l The implementation team has determined thatadditional plants need to be created for theimplementation.

l They have also decided that it would be beneficial ifthe new plants can utilize the existing contracts andconditions negotiated by the central purchasingorganization. It intends to use the organizationalassignments for the new plants to accomplish thisgoal.



SAP AG 1999

Company Code

Controlling Controlling areaarea

Business area0001

Business area0002

Chart of accounts

Currency

n The information determined at company code level includes:

� Company address

� Chart of accounts

� Balance sheet currency

� Fiscal year variant

� Controlling area

� Business area balance sheet active

n You define the company code in the IMG, in the node Enterprise Structure → Definition Financial Accounting. You also define the company address, country, language, and currency for the company code here.

n In the IMG node Enterprise Structure → Allocation → Controlling, you assign the company code to a controlling area.

n In the IMG node Financial Accounting → Financial Accounting Global Settings → Company Code → Enter Global Parameters, you assign the chart of accounts.

n In the IMG node Enterprise Structure → Definition → Financial Accounting → Maintain Business Area, you define the business areas.



SAP AG 1999

Purchasing Organization

Company codes

Purchasing group 2

Plant 1100

Purchasing group 1

Plant 1000

Purchasing group 3

Plant 1200

PurchasingPurchasingorganizationorganization

Info record

Contract

n The purchasing organization is legally responsible for transactions made in Purchasing and for negotiating purchasing conditions.

n The R/3 System derives the company code for a purchasing transaction from the purchasing organization, if the purchasing organization is assigned to a company code.

n In the standard system, you store all conditions available in the system with reference to a purchasing organization.

n A purchasing organization can access the info records and contract conditions negotiated by one of the other purchasing organizations.

n You can model a central, cross-company code purchasing structure. In this case, you do not assign the central purchasing organization to a company code.



SAP AG 1999

CentralCentralpurchasingpurchasing

(Reference POrg)(Reference POrg)

Plant1100

Plant1000

Plant1200

Company codeCompany code10001000


Reference Purchasing Organization


12001200


11001100


10001000

n Using a reference purchasing organization, you can allow contract release orders and use conditions across purchasing organization boundaries. This allows:

� You to use conditions from a reference purchasing organization for price determination in other purchasing organizations as well

� Several purchasing organizations to access the contracts of a particular reference purchasing organization



SAP AG 1999

Valuation Area

Valuation area

Material - Valuation Levels

Company code Plant

0001

n You define the valuation area by deciding at which level you want to valuate your stocks of materials. Your decision applies for all clients.

n Valuation area = Company code: The R/3 System creates the valuation data for a material for each company code. The price control used and the price of a material apply for each company code. This means that the material is valuated uniformly across all plants belonging to a particular company code.

n Valuation area = Plant: The R/3 System creates the valuation data for a material for each plant. The price control used and the price of a material apply for each plant. This allows you to valuate the same material in different ways in different plants.

n In a production system, you cannot change the valuation level to company code level or to plant level, because you would have to convert the data that already exists.

n For the PP component and for product costing, it is essentia l that you use the valuation level “Plant”.



SAP AG 1999

Functions and data stored at plant level:

Material requirements planning

PP master data administration

PP order management

Capacity planning

Product costing

Forecast

Plant maintenance planning

Material inventory management

Purchasing views

Accounting views(if valuation area = plant)

Plant

n Production planning and actual production generally take place on a plant-specific basis.

n However, certain applications can operate on a cross-plant basis.

n You can also define pooled capacities for capacity planning.

n You can carry out product costing across plants.

n You can carry out certain functions in requirements planning with reference to the storage location. You can also carry out requirements planning for several plants at the same time.

n You can define a plant as a maintenance planning plant.



SAP AG 1999

l The storage location is the level atwhich a plant’s actual stocks ofmaterials are kept.

l The physical inventory takes placeat storage location level.(Exception: physical inventorywithin the WarehouseManagement System)

l Stocks are managed at storagelocation level on a quantity basisonly – not on a value basis.

l A storage location is alwaysdefined as belonging to a certainplant.

Storage Location

n The storage location key is unique only within a plant or with reference to a plant.



SAP AG 1999

PlantPlant11001100


10001000


12001200

PlantPlant10001000

PlantPlant12001200

StorageStoragelocationlocation

00010001


00010001


00100010


00050005


MM Organizational Levels

n A plant is assigned to only one company code. A company code can contain more than one plant.

n A plant can contain more than one storage location, in which you manage material stocks.



SAP AG 1999

DivisionDivision

Valuation level

DivisionDivision

DivisionDivision

DistributionDistributionchannelchannel

Purchasing organizationPurchasing organization 00100100010001 00020002 Sales organizationSales organization

Plant 1000Plant 1000 Plant 1100Plant 1100

Company code

Organizational Structure of Logistics

Shipping point0002

Shipping point0001

Storage location 0002

Storage location0001

Stor. location 0003(WMS warehouse)

n The valuation level can be the plant (slide = SAP’s recommendation) or the company code.

n Purchasing organizations can be active for one or more plants.

n Sales organizations can be active for one or more plants. Sales organization, distribution channel, and product division are grouped to form a sales area.

n You can assign a plant to more than one sales organization/distribution channel combination.

n You assign each plant and division to one business area only.

n A plant can contain more than one shipping point. You can assign a shipping point to more than one plant.



SAP AG 1999

Controlling area1000

ClientClient

Controlling area2000

Companycode 1000

Plant 1000Plant 1000

ValuationValuationarea 1000area 1000









Companycode 2000

Companycode 3000

Chart ofaccounts

INT

R/3 Organizational Levels: MM and FI

n The R/3 System differentiates between various organizational units, which have a specific significance within each application.

n For the purposes of product costing ann PP, it is absolutely essential that there is a separate valuation area for each plant.

n You always perform value-based inventory management at the level of the valuation area.

n Partial stocks of the same material can be subject to split valuation (for example, stocks of a material produced in-house can be valuated at a different price to stocks of the same material that were procured externally). Split valuation is controlled using the valuation category and valuation type.



SAP AG 1999

Creating a Creating a “single plant”“single plant”

Maintain general plant dataLocation (city)/streetCountry/postal codeAddress

Make assignmentse.g.: Plant è Purchasing organization

Plant è Company codeCheck assignments

Check functional parameters for plantCheck/maintain all plant-dependent tables in the application areas.

Copying a Copying a “complex plant“complex plant””

Copy the general plant data and check è Location (city)/street

Country/postal codeAddress and so on

Copy all assignmentse.g.: Plant è Purchasing organization

Plant è Company codeè Check assignments

Copy the functional parametersThe system copies all plant-dependenttables in the application areas.Check if necessary.

Plant 2000

Plant 1000

Creating a New Plant

n You use the following extended functions to process organizational units:

� Copy

� Delete

� Check

� Create and process Project IMG view

These functions allow you to maintain not only the general plant data (key, description, address, country, language, factory calendar, and so on), but also additional plant-dependent table entries.

n Project IMG:

You use this function to create a new view for a Customizing project. The view that you create contains all the activities required to process the organizational unit within the scope of the Customizing project. The prerequisite for using this function is that you have already created a Customizing project.



SAP AG 1999

Plantdependenttables





Checking a Plant

n Checking a plant is a two-step procedure:

� In the first step, the R/3 System checks if there is an entry in all tables in which the organizational unit specified in the table key exists.

� In the second step, the R/3 System checks if the entry specified also exists in the dependent tables, which it checks against the table key.



SAP AG 1999

l List the most important functions of the MMorganization structures

l Identify the relationships between the MMorganization levels and their environment

l Configure the Logistics (MM) organizationallevels in the Implementation Guide

l Use the plant copying and checking functions


MM Organizational Levels: Summary



Exercises

Unit: MM Organizational Levels

Topic: Settings for the Enterprise Structure from the Materials Management Perspective

• At the end of this exercise, you will be able to:Indentify the organizational structures relevant to Materials Management

• Explain the reference purchasing organization and how it is used to support purchasing

• Configure a new plant with storage locations, and maintain the assignment to the company code and relevant purchasing organizations

• Use the plant copy functions

• Explain the financial organizational units of company code and controlling area and how they relate to a plant

Part of your job on the implementation team includes modeling the organizational structure of your company for the Logistics applications in the R/3 System. It has been determined that additional plants need to be created for the implementation. It has also been identified that the new plants will benefit if they can utilize the existing contracts and pricing negotiated by the global purchasing organization. It will be necessary to define the organizational assignments for the new plant so that this goal can be accomplished.

1-1 General Relationships

During consultation on the modeling of the organizational structure, the following statements were made. Decide whether they are true or false and give reasons for your answers.

1-1-1 “One plant can be assigned to several company codes.”

______________________________________________________

______________________________________________________

1-1-2 “A purchasing organization must always be assigned to a company code.”

______________________________________________________

______________________________________________________

1-1-3 “You can use the storage location key 0001 more than once.”



______________________________________________________

______________________________________________________

1-2 Studying the MM Organizational Units

You are helping to define the organizational units based on the current organizational structure of your company. In your view, what are the main criteria for defining the following?

1-2-1 ... A new company code

______________________________________________________

______________________________________________________

1-2-2 ... A new plant

______________________________________________________

______________________________________________________

1-2-3 ... A new storage location

______________________________________________________

______________________________________________________

1-2-4 ... A new purchasing organization

______________________________________________________

______________________________________________________

1-2-5 ... A new purchasing group

______________________________________________________

______________________________________________________

1-3 Defining Organizational Units

Once the project committee has approved the organizational structure, you are asked to set up a new plant site with the key TR##.

In this exercise, do not use the copy function at first, although this is advisable in practice.

1-3-1 Define a new plant, TR##. Define DE as the country for this plant.

______________________________________________________

1-3-2 Assign your plant TR## to the factory calendar Germany (standard).

______________________________________________________



1-3-3 Create storage locations 0001, 0002, and 0003 for this plant. Maintain at least one address for each of these storage locations.

______________________________________________________

1-3-4 Assign this plant to company code 1000.

______________________________________________________

______________________________________________________

1-3-5 Purchasing organization 1000 is responsible for this plant. Contract negotiations by Central purchasing for Europe should also be allowed. Configure these responsibilities.

______________________________________________________

______________________________________________________

1-3-6 Can you assign this plant to purchasing organization 0001 as well? Why/why not?

______________________________________________________

______________________________________________________

1-3-7 In the Implementation Guide, find out the significance of the standard purchasing organization. Which transactions is it used for? Assign for your plant purchasing organization 1000 as the standard purchasing organization.

______________________________________________________

______________________________________________________

1-3-8 In the Implementation Guide, find out the significance of the reference purchasing organization. Has a reference purchasing organization been defined for purchasing organization 1000?

______________________________________________________

______________________________________________________

1-3-9 Explain why purchasing groups must or must not be assigned to purchasing organizations.

______________________________________________________



______________________________________________________

1-3-10 Review the assignment of company code 1000 to controlling area 1000. Is this controlling area responsible for plant TR##?

______________________________________________________

______________________________________________________

1-3-11 Complete the data for plant TR## by using the copy function to add the other settings. Use plant 1200, which is set up completely, as the template to copy.

Choose IMG Filter and enter project number 0000000200. Look at the structure displayed.

As an example, choose Materials Management → Inventory Management and Physical Inventory→ Plant Parameters. Verify that the plant parameters have been maintained for your new plant.



Solutions

Unit: MM Organizational Levels

Topic: Settings for the Enterprise Structure from the Materials Management Perspective

1-1 General Relationships

1-1-1 False, each plant can only be assigned to one company code.

1-1-2 False, you do not have to assign a purchasing organization to a company code if this purchasing organization functions as a central purchasing organization. If a company code assignment for a purchasing organization is not made, plants from different company codes can be assigned to the same purchasing organization.

1-1-3 True,you can use the storage location key 0001 more than once because you define storage locations with reference to a plant.

1-2 Studying the MM Organizational Units

1-2-1 The company code embodies an independent organizational unit for Financial Accounting.

1-2-2 The plant represents an organizational unit for Logistics, which structures a company from the perspective of production, procurement, plant maintenance and requirements planning.

1-2-3 The storage location represents an organizational unit/area for distinguishing between material stocks within a plant.

1-2-4 The purchasing organization represents an organizational unit within Logistics that structures the company according to its purchasing requirements.

1-2-5 The purchasing group represents a person or a group of people responsible for certain purchasing activities.

1-3 Defining Organizational Units

1-3-1 Choose Enterprise Structure → Definition → Logistics – General → Define, copy, delete, check Plant

Choose Define plant

Choose New Entries

Enter Plant TR## and a description for Name 1.



Enter country code DE

Maintain the second address (Edit → Address)

1-3-2 Choose Define Plant → Details.

Enter Factory calendar 01

Save

1-3-3 Choose Enterprise Structure → Definition → Materials Management → Maintain Storage Location and add the new entries.

Maintain the addresses for storage locations 0001, 0002, and 0003 by selecting the storage location and selecting the folder Address.

Enter the first address number, such as 01, then select Address from the toolbar. Enter an address.

Save.

1-3-4 Choose Enterprise Structure → Allocation → Logistics – General → Assign Plant to Company Code.

Assign your plant to company code 1000.

1-3-5 Choose Enterprise Structure → Allocation → Materials Management → Assign Purchasing Organization to Plant.

Assign your plant to purchasing organization 1000 and purchasing organization C100.

1-3-6 If your plant is assigned to company code 1000, you cannot assign this plant to purchasing organization 0001, because purchasing organization 0001 is assigned to company code 0001.

1-3-7 Choose Enterprise Structure → Allocation → Materials Management → Assign Standard Purchasing Organization to Plant.

The standard purchasing organization is required for consumption postings for consignment and pipeline materials.

Assign purchasing organization 1000 as the standard purchasing organization for your plant.

1-3-8 Choose Enterprise Structure → Allocation → Materials Management → Assign Purchasing Organization to Reference Purchase Organization.

Purchasing organization C100 is defined as the reference purchasing organization for purchasing organization 1000.

The significance of having a reference purchasing organization is to be able to utilized the contracts and pricing cond itions established by the reference



organization.

1-3-9 Both settings are independent of one another. Purchasing groups are created for the individual employees to enable definition of user-specific activities settings (such as the printer for the purchase order printout, and contact person details, telephone number, and fax number on purchasing documents).

Purchasing organizations are set up as a level for defining conditions (price determination) and negotiating outline agreements.

1-3-10 Choose Enterprise Structure → Allocation → Controlling → Assign Company Code to Controlling Area.

Controlling area 1000 is responsible for plant TR##. This results from the assignments: Plant → Company code and Company code → Controlling area.Company code 1000 is assigned to controlling area 1000. Therefore, controlling area 1000 is responsible for your plant.

1-3-11 Choose Enterprise Structure → Definition → Logistics – General → Define, copy, delete, check Plant.

Choose Copy, delete, check plant

Select Copy

Enter from plant 1200 to plant TR##.

Select yes to copy the complete object.



SAP AG 1999

l Settings for Material Typesl Field Selection Control for Material Master Records

l Vendor Master Records

Contents:

Master Data in Materials Management



SAP AG 1999

Master Data in Materials Management: Objectives


l Configure the material types and set the controlattributes for them

l Define the material number assignment

l Determine and configure the field selection controlusing the influencing factors

l Define the necessary settings for the vendormaster



SAP AG 1999

l Many of the products that are both produced andconsumed across the organizational structures ofyour company belong to an internal supply chain.

l For this reason, your implementation team hasdecided to create a new material type that reflectsthis internal supply chain scenario.

Master Data in MM: Business Scenario

n Your company produces many materials at one plant and then ships them to another plant where they are used to produce a different product. You want to use a separate material type when creating these materials.

n This new material type should combine the attributes of the standard material types ROH and HALB.

n Your project team has decided that the new material type should have its own number intervals.

n After analyzing all material master fields, the project team decided to create a new field selection and sequence for individual view maintenance for materials of the new material type, instead of using those for the ROH and HALB material types.

n As part of the R/3 System implementation, you have been asked to give an overview of the vendor master record and the control options.



SAP AG 1999

Settings for Material Master Records

Configuring the Material Master

Field Selection

Basic Settings

Settings for Key Fields

Tools

n In the IMG node Configuring the Material Master, you modify the material master maintenance (screen layout, screen sequence, and so on) to meet the specific requirements of your company.

n In the IMG node Field Selection, you define which material master fields are ready for input as either mandatory entry or optional entry, displayed only, or suppressed.

n In the IMG node Basic Settings, you can define the material types, the number assignment for material master records, and so on.

n In the IMG node Settings for Key Fields, you specify the following:

� Which material groups and divisions you use in your company

� Which material statuses you require

� Which storage and temperature conditions must be met for particular materials

n In the IMG node Tools, you can:

� Define authorizations and authorization profiles for material master record maintenance

� Organize the data transfer for material master records

� Define the start time for background jobs

� Maintain search helps



SAP AG 1999

Basic Settings

Make Global Settings

Maintain Company Codes for MM

Define Attributes of Material Types

Define Number Ranges

Define Output Format of Material Numbers

n In the IMG node Make Global Settings, you define the following:

� How the administration data is updated for technical data (table MSTA) when processing material master records: The R/3 System updates the material administration data when you create and change material master records. You can select if:

The update should take place only at table level (for example, client level, plant level)

Or also when individual material statuses are created or changed (for example, purchasing data, MRP data, and so on).

� The standard document type for engineering/design drawings, if your company is implementing the document management system

n The period closing program terminates if the permitted number of incorrect material records is exceeded.

n You can use an indicator to activate special indiv idual processes for reference materials.

n To maintain company codes for Materials Management: You define the current posting period and the fiscal year for the material master records (accounting data) during initialization. You can also initialize the company code in Tools.



SAP AG 1999

Material type

Material

Field selection and screen sequence

General indicators for price control, special processesand for Retail

Costing control

Item category group SD

Views for material maintenance

Procurement type (internal/external)

Type of inventory management (quantity/value)

External alphanumeric number assignment without check

Assignment to an account category reference

Authorization group

MaterialMaterialA

Material typeMaterial type

A

Control of the Material Type: Material Master

n A material type is specified for each material. The material type is part of the general data on a material.

n The user departments defined for a material determine which views they can maintain for a material of this particular material type. This controls which applications can use the material.

n You can determine the type of inventory management (quantity-based and/or value-based) for a material type on a valuation area-specific basis.

n The material type controls essential processes in individual applications. For example, in Customizing for PP, you define the specific material types that are included in or excluded from the creation of BOMs and routings in your company, depending on their usage.

n You can configure the type of price control as an optional value or mandatory default value.

n The R/3 System assigns the stock accounts and consumption accounts using the valuation classes. It assigns the permitted valuation classes to the material type using the account category references.

n In Customizing for the material type, you can identify inconsistencies regarding the quantity and valued based inventory management for the valuation areas.

n You can define which material types are assigned to the special creation transactions.

n Individual indicators such as Material type ID and Time until deletion are only used in SAP Retail.



SAP AG 1999

Materialsplanning

Stocks at plant/storage location

Purchasing

Accounting

Storage

Costing

Forecast

Sales and distribution

Classification

Warehousemanagement

The material master isThe material master isthe central data objectthe central data object

in the R/3 System.in the R/3 System. It is usedIt is usedto represent raw materials,to represent raw materials,

auxiliary materials,auxiliary materials,operating supplies,operating supplies,

semi-finished products,semi-finished products,finished products, PRTsfinished products, PRTs

......

Definition

MaterialMaterialmaster recordmaster record

Basic data

Workscheduling

t

AB B C

B

A BXX XX

Material Master Record Maintenance: Views

n Each user department has its own view of a material master record.

n For the management of BOMs and routings, you must create at least one view at plant level.



SAP AG 1999

Group 01

Internal interval NA

External interval NA

Group nn

Internal interval NA

External interval NA

...

MaterialMaterial

Material typeMaterial type

Check externally assigned numberCheck externally assigned number ??

Number Assignment for Materials

n You define the material number groups independently of the company code or fiscal year.

n First, you must maintain the groups. Then, you assign the material types to the groups.

n You can assign an interval to one group only.

n You can change the number level of an interval manually.

n The standard system uses a buffer when assigning numbers to material master records. The amount of numbers for the buffer is 10. Using this buffer and having the material number assigned before saving a new material master can lead to gaps in the number assignment. However, if you reset the number level of an interval back to the initial value, the R/3 System fills these gaps when you create new materials.



SAP AG 1999

Material number:18 characters

Material number:18 characters

Database

Material

Conversion

Input/output length

Leading zeros

Template

Form of storage

How the Material Number is Displayed

n The input/output length, leading zeros, and template settings for the material number conversion apply only to online activities and printouts.



SAP AG 1999

Material types: Quantity and Value updating

Procurementfor stockpossible?

Stockvaluated?(Inventoryacct.)

Raw material

Non-stock mat.

Nonvaluated m.

Quantityupdate

Valueupdate

Materialtype

Blank: Storage / Invent. Acct.Acct. assigned: Consumption/cons.acct.

Acct. assigned: Consumption/Cons.acct.

Account Quantity/Valueassignment cat. Update

Acct. assigned: Storage (Value: 0 UNI) and consumption acct.

Stock ValuatedStock

No stock or not valuated

Otherwise:Consumpt.account

{

{

n Quantity Update:

� If stock is possible, you may choose if you order materials for stock (storage) or for consumption.

� Otherwise only procurement for consumption is possible.

n Value Update:

� If the stock is valuated, the value is posted to inventory/stock account.

� Without value update you have to use a non-blank account assignment type. In this case the value is posted to consumption account (and an Accounting object).



SAP AG 1999

Material Master Field Selection

Overview of the Influencing Factors

Field Selection Groups

Field Reference - Control String

Field Reference Assignment

Linking the Control Strings



SAP AG 1999

Material Field Selection: Influencing Factors

Transaction

Procurementindicator

Material type

Plant

Industry sector

SAP delivery

........

........

........ ?

Field selection

n There is a separate control string for each of these influencing factors.

n Each item in a control string of this type applies to a group of material master fields.



SAP AG 1999

Material type

Plant

Industry sector

Transaction

Procurement indicator

SAP delivery

Field reference Control string

In-house/external Control string





Material Field Selection: Field Reference

n As a rule, a reference key defines which control string applies to the relevant influencing factor.

n You can maintain the reference key for the material type, the plant, and the industry sector in the configuration menu.

n Each item in a control string of this type determines the field selection for a group of material master record fields. You can use the configuration menu to establish the group to which the individual fields are assigned.



SAP AG 1999

Field Namee.g.: MARA-FERTH

Field Namee.g.: MARA-FORMT

Field Namee.g.: MARA-KZUMW

Hide

Display

Required

Optional

Field optionField option

1:nField selectiongroup

e.g.: 015

Applies to all fields in the field selection group

Field Selection: Field Selection Group

n One or more material master fields are assigned to a field group.

n The field option applies to all the fields in the field group (for example, all the fields are required fields).



SAP AG 1999

Determine the field selection group, towhich the field to be changed belongs

Determine the influencing factor forchanging the field selection

Determine the control stringto be changed

Change the field selection for thisgroup in the relevant string

Check the link

11

12

13

14

15

Link rulesLink rules

For example, material type ROH

Tran

saction

MM

01

Material Field Selection: Procedure

++

+

+

+-

-

-

-

-

- - --

*

** **

*

*

.

..

n The field selection in a material master record transaction is determined by several control strings. The entries in all the control strings that are valid for the relevant transaction are linked (item for item) at certain points.

n Each of the link rules listed above determines the result of the field selection for a group of material master fields. The link rules are defined by SAP and cannot be changed.

n The symbols have the following meanings:

� - = suppress

� * = display

� + = mandatory entry

� . = optional entry



SAP AG 1999

User Material Masters

SubscreensSubscreensScreensScreens

Basic Data

ScreensequenceScreensequence

Basic DataSales

Purchasing

l You can set up the material master according to yourcompany`s requirements:

l You can remove screens that you do not need from thescreen sequence.

l You can create your own screens by deleting standardsubscreens or by inserting your own subscreens.

l You can change individual fields in subscreens.

n When you configure your system, you can customize the functions for material master records to suit your company's requirements. You can use either standard subscreens or subscreens that you create yourself to set up your own screens.



SAP AG 1999

Application No dialog Warning Error

ApplicationApplication ControlControl

PurchasingBOM headerBOM itemRoutingIndependent requirementsForecastMaterials planningProduction order headerProduction order itemQuality inspectionProduction resources/toolsPlant maintenanceInventory management

xxxx

x xxxxx x

xx

MaterialMaterialA

Material Status

Material status fieldMaterial status field

n The material status enables you to control the usability of a material for business applications.

n The material status is defined in the material master record and depends on the material concerned. The material status can be assigned to the material master at either the client level via the Basic data screen, or at the individual plant level.



SAP AG 1999

Container requirements

Laboratories andoffices

Materialmaster record

Material groups

Temperatureconditions

Divisions(Areas of responsibility

in SD)

Storage conditions

Material

Other Check Tables for the Material Master

n The material master contains a series of fields that are checked against other tables. These tables must be set up before you create material master records.



SAP AG 1999

Settings for Vendor Master Records

Vendor Account Groups

Field Selection

Number Assignment

Levels for Vendor Data

Partner Roles



SAP AG 1999

... the field selection

... which partner rolesare allowed, based on

partner schemas

... if vendor sub-rangesor plant-specific data

are allowed

... the number range

... the type ofnumber assignment(internal/external)

... how the master recordis used

(vendor or one-time vendor)

Account Group Control: Vendor Master

The account groupThe account groupcontrols ...controls ...

n You must specify an account group when you create a vendor master record. You use the account groups to group vendors according to certain criteria. You use the account group to define the following:

� Which fields are ready for input or must be filled when you create and change master records

� If the account in question is a one-time account (collective account for one-time vendors)

� If the data retention levels “Sub-Range” and/or “Plant” are allowed for a vendor master record.

� The account number interval and the type of number assignment, with the help of number ranges

� The partner roles that are allowed for the account group



SAP AG 1999

Field selection for:Field selection for: Basic dataBasic data

AccountingAccounting data data Purchasing dataPurchasing data

Purchasing data:Purchasing organization

Accounting data:Company code

Account group Transaction

Vendor Field Selection: Influencing Factors

n The link rules for the individual field status definitions for vendors correspond to those that apply to material master records.

n Depending on the transaction or activity, you can maintain the field status definitions for vendor master record maintenance:

� Centrally

� For Purchasing

� For Accounting (in Customizing for FI → Master data for Accounts Receivable and Accounts Payable).

n You can define the field selection for the purchasing, vendor sub-range and plant data screens based on the purchasing organization. The entry “*” in the purchasing organization field represents all purchasing organizations that are not specifically listed in the table.

n You can also maintain the field status definitions for the accounting data for each company code (account management, payment transactions, and so on) in Customizing for FI → Master data for Accounts Receivable and Accounts Payable.



SAP AG 1999

Partner Roles

VendorVendorGoods recipient

Goods supplier

Invoicing party

Paymentrecipient

n In the standard system, the following partner roles are defined as examples:

� Vendor

� Ordering address

� Goods supplier

� Invoicing party

� Different payee

n In Customizing, you define the partner roles that are optional and those that are mandatory. In the standard configuration, all partner roles are optional, except that of “vendor”. If no other roles are maintained, the data for the vendor role applies.

n You can use the partner schema to define your own partner role assignments.



SAP AG 1999

0001 Vendor MandatoryVD xOAAZ

0002 Purchase ordersVD xOAPI

VD VendorOA Order addressPI Invoicing partyGS Goods supplierAZ Diff. payt recipient

Partner Roles – Partner Schemas

Partner rolePartner role Partner schemaPartner schema

(1) Permittedpartner roles for

vendor inaccount group?

(2) Partner schemawith permitted

partner roles for vendors

Assignpartner schema

to account group

(2) Partner schemawith permitted

partner roles for purchase orders

Assignpartner schema

to order type

n You can define partner roles in any way you want.

n (1) You define for each partner role the account groups that the R/3 System can use when creating vendor master records. For example, the entry “OA LIEF” means that you can create an ordering address using account group LIEF.

n You maintain the partner roles allowed for vendor master records, purchasing documents, and rebate arrangements in partner schemas. You define for each schema if a partner role is mandatory (required) and if it can be changed.

n (2) You can assign a partner schema to each account group and possibly to allowed data retention levels (purchasing organization, vendor sub-range, and plant) of this account group. This allows you to define the partner roles that are allowed for vendor master records. For example, if partner schema L1 is assigned to account group LIEF (at purchasing organization level) and it contains partner role OA, you can maintain an ordering address in every vendor master record in account group LIEF (at purchasing organization level).

n In the case of purchasing documents and rebate arrangements, you assign the partner schemas depending on the document type or arrangement type.

n You can find all the Customizing activities for partner roles in the Purchasing IMG in the node Partner Determination.



SAP AG 1999

Master Data in Materials Management: Summary


l Configure the material types and set the controlattributes for them

l Define the material number assignment

l Determine and configure the field selection controlusing the influencing factors

l Define the necessary settings for the vendormaster



SAP AG 1999

Material Type (Hints to the exercise)

l 1-2-2/1-2-3 Determine approach/Make settings

n Regard the two sub-tasks as an integrated unit. You mayprocess them in a single step.

l 1-2-4 Testing the settings

n Not all 6 points can be checked by creating a material masterrecord.

n Which one(s) is/are omitted and how can this check be carriedout?

?



SAP AG 1999

Vendor Master Record (Hints to the exercise)

Permiss. PR/AGr•BA - LIEF•BA - BADR•BA - KRED

Assignment AGr/schema•LIEF - S1

Schema S1•BA•LF•AZ

Customizing

Vendor 1001BADR

Vendor 2000KRED

Vendor 1002BADR

Vendor 1000Partner roles:•BA 1000•BA 1001•BA 1002•BA 2000•AZ

LIEF

l Codes:

n Account group Z##, partner role ##, partner schema S##

l Note:

n The function Define permissible partner roles per accountgroup does not describe the partner roles that are allowed(this is done via the partner schema). It specifies that onlyvendors of certain account groups may be used for a partnerrole.



Exercises

Unit: Master Data in Materials Management

Topic: Material Type


• Check the attributes for a material type

• Define a new material type

• Configure the number assignment for material master records

Your project team has made the following arrangements for raw materials that you adopt from the legacy system:

• You will only procure these materials using external purchase orders.

• You are to allow only the following views for these raw materials: Basic data, Accounting, MRP, Purchasing, Storage, and Forecasting.

• The system is to update both the quantities and the values for all plants.

• The system always valuates these raw materials using the standard price procedure.

• Account assignment is made in the same way as for other raw materials.

• The numbers for these materials must be assigned internally from the interval 100000000 - 199999999.

On the basis of the process analysis, you have decided to use a separate material type for the raw materials from the legacy system. Make the settings necessary for this.

1-1 Define a New Material Type

1-1-1 Make a few notes on the controls that you can influence using the material type:

______________________________________________________

______________________________________________________

______________________________________________________



1-1-2 Give possible reasons or several examples that justify the need to create a separate material type.

______________________________________________________

______________________________________________________

1-1-3 Define a new material type, GR##. To do this, select the SAP reference material type for raw materials as your template to copy.

Define the attributes of the new material type and note how you do this:

- Only External procurement is allowed

___________________________________________________

- Permitted views: Basic data, Accounting, MRP, Purchasing, Storage, and Forecasting.

___________________________________________________

- Quantity and value update in all plants

___________________________________________________

- Only price control S is permitted and is binding

___________________________________________________

- Same account assignment (“account category reference”) as for raw materials

___________________________________________________

1-2 Number Assignment

1-2-1 What groups are there for assigning numbers to material master records? Check if the specified interval (100 000 000 - 199 999 999) already exists.

______________________________________________________

1-2-2 Write down the sequence in which you must proceed. Note that not all of the activities are relevant for your task.

_____ Select material type

_____ Change current number level

_____ Search for group with this range

_____ Obtain an overview of existing groups and their assigned intervals

_____ Assign material type to a group

_____ Select group

_____ Maintain groups

_____ Change intervals

1-2-3 In Customizing, use your sequence to configure the number assignment that the project team defined for your material type.



1-2-4 Test your settings by creating a new material master with material type GR## for plant 1000. Check all six points in the business scenario.

- Number assignment: is external number assignment possible for your material type? Which internal numbers are assigned?

___________________________________________________

- Permitted views:

___________________________________________________

- Procurement type:

___________________________________________________

- Quantity/value update:

___________________________________________________

- Valuation class(es):

___________________________________________________

- Price control:

___________________________________________________



Exercises


Topic: Field Selection


• Configure the field selection for material master records

To make the transition from the legacy system to the new system easier for the users, you have decided to define the field Old material number as a required field for your new material type.

On the other hand, this field should remain an optional field for material type ROH.

2-1 Settings Specific to the Material Type

2-1-1 Before you make the necessary Customizing settings for field selection, write down the steps and entries that are required to do this and the influencing variables that you need to consider:

Step 1: ______________________________________________

______________________________________________

Step 2: ______________________________________________

______________________________________________

Step 3: ______________________________________________

______________________________________________

Step 4: ______________________________________________

______________________________________________

Step 5: ______________________________________________

______________________________________________



2-1-2 Now use your notes to configure the appropriate required field in Customizing. If you require a new field reference, use the key ZM##.

Note that your Customizing changes are only to apply to the new material type, GR##.

Do not change any settings that could affect the other groups.

2-1-3 Test your field selection settings for material GR## by creating the basic data for a material with this material type and for a material with material type ROH.

Is the field Old material number ready for input (required or optional field), is it only displayed, or is it suppressed for the following material types?

GR## ______________________________________

ROH ______________________________________

2-2 Plant-Specific Settings

2-2-1 How do you make sure that the field Availability check (check group for the availability check) must be maintained for all of the material master records for your new plant?

Are other fields affected if you change the field selection? ______________________________________________________

Make these settings. If you require a new field reference, use the key ZW##.

______________________________________________________

2-2-2 Test your settings: Extend the material master from question 1-2-4 by the MRP view for your new plant TR##.

2-2-3 How could you prevent storage and sales data being created unnecessarily for the materials in plant 1400?

Is it possible to make this setting dependent on the procurement type or the material type?

Do NOT make this change.

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________



Exercises


Topic: Vendor Master Record


• Set up a new account group for vendor master records

• Define partner roles and make the necessary settings

Some of your large suppliers (Central Purchasing) have more than one sales plant. In your company, you want to use separate vendor master records for each one. All purchasing transactions are to be assigned to Central Purchasing. On the other hand, you want to transmit your purchasing documents (such as purchase orders) directly to the nearest sales plants.

You now have the task of further analyzing and modeling this process.

4-1 Vendor Master Settings

4-1-1 What further information do you need on this process?

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

4-1-2 Which activities must the solution include? Which activities are necessary

and how would you make these settings?

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

4-1-3 Which other activities might you also need to check?

______________________________________________________

______________________________________________________



Solutions


Topic: Material Type

1-1 Define a New Material Type

1-1-1 You can influence the following with the material type:

- The procurement type

- The permitted views

- The value and quantity updates

- The account assignment

- The number assignment

- The field selection

1-1-2 For certain materials, you want to allow maintenance of fewer views, make postings to different accounts via automatic account determination, or use a different field selection.

1-1-3 Choose Logistics – General → Material Master→ Basic Settings → Material Types → Define Attributes of Material Types.

Copy material type ROH and define the attributes of the new material type:

- Ext. purchase orders 2, Int. purchase orders 0

- Select: Basic data, Accounting, MRP, Purchasing, Storage, and Forecasting.

- Select: Quantity updating in all valuation areas Value updating in all valuation areas

- Price control Standard price Select Price ctrl mandatory

- Account category reference 0001



1-2 Number Assignment

1-2-1 Choose Logistics – General → Material Master→ Basic Settings → Material Types → Define Number Ranges for Each Material Type.

Group 1 – Interval 1 99 999 999 Group 2 – Interval 100 000 000 199 999 999

1-2-2 Proceed in the following sequence:

5. Select material type

- Change current number level not required

3. Search for group with this range

1. Obtain an overview of existing groups and their assigned ranges

6. Assign material type to a group

4. Select group

2. Maintain groups

- Change ranges not required

1-2-3 Select group 2. Select your material type GR##. Assign your material type to group 2.

1-2-4 External number assignment for your material type may not be allowed (indicator for material type External number assignment without check ).

Internal number assignment: as specified

Permitted views: as specified

Procurement type: F

Quantity/value update: not directly visible

Valuation classes: 3000, 3001, 3002, 3003

Price control: “S”, cannot be changed



Solutions


Topic: Field Selection

2-1 Settings Specific to the Material Type

2-1-1 You must note the following steps for the Customizing settings for field selection:

- Which field is the change to be made for? Which field selection group does this field belong to?

- Do other fields belong to this field selection group? Should the change to the field selection also apply to these fields (case a) or not (case b)? In case b, you have to assign a new (free) field selection group for the field to be changed.

- Which influencing factors is the field selection to be changed for?

- Which field reference is used to control the field selection for the influencing factor determined? You may have to define a new field reference.

- Field selection change and check of all influencing factors

2-1-2 Choose Logistics – General → Material Master→ Field Selection → Assign Fields to Field Selection Groups.

Position the cursor on MARA-BISMT. You are informed that field selection group 011 is assigned to this field. (You can see the field description in material master maintenance using F1 help on the selected field → Technical info.) No additional fields are assigned to field selection group 011.

Choose Logistics – General → Material Master→ Field Selection → Maintain Field Selection for Data Screens.

Copy field references ROH. Change item 011 in the new field reference ZM## from Optional entry to Required entry.



Change the attributes of your material type GR##. Assign field reference ZM## to your material type.

You do not need to take into account the other influencing factors, because the field is configured as optional entry in the standard system, that is, neither Hidden nor Display only.

2-1-3 Material type GR## Field is required Material type ROH Field is optional

2-2 Plant-Specific Settings

2-2-1 For the new plant, TR##, you can control the field selection using a specific field reference.

The field Availability check is called MARC-MTVFP and is assigned to field selection group 092. Only the description belongs to this group (you can ignore this).

Copy field reference 0001 (for plant 1000) or define a new field reference, ZW##. Change item 092 in the new field reference ZW## from optional entry to required entry.

Assign field reference ZW## to your plant. Choose Logistics – General → Material Master→ Field Selection → Define Plant-Specific Field Selection and Plant-Specific Screen Selection.

2-2-2 The field Availability check is a required entry for plant TR##.

2-2-3 You could prevent maintenance of storage data and sales data for the materials in plant 1400 by deleting these views or statuses for plant 1400. This setting does not depend on the procurement type or the material type.



Solutions


Topic: Vendor Master Record

4-1 Vendor Master Settings

4-1-1 Are there any specific considerations that you need to take into account (field selection, number assignment, the purchasing organization that the record is for, separate reconciliation account, special condition types, for example, for delivery costs)?

4-1-2 You can define a separate account group for a specific grouping with its own number range.

Depending on the business process, you may need to change the field selection – generally or depending on the purchasing organization.

4-1-3 You can use a partner role in the vendor master and possibly allow a separate partner schema for sending purchasing documents directly to the vendor’s sales plants. This partner role can be permitted at various levels:

- Purchasing organization

- Vendor sub-range

- Plant

To check the settings for the account group, field selection, and number assignment, choose Logistics – General → Business Partner → Vendors → Control.

To check the settings for partner roles and partner determination, choose Materials Management → Purchasing → Partner Determination → Partner Roles and Partner Settings in Vendor Master Record.



SAP AG 1999

l Document Types in Purchasing

l Screen Layout for Purchasing Documentsl Account Assignment Categories

l Long Texts in Purchasingl Messages

Contents:

Purchasing



SAP AG 1999

Purchasing: Unit Objectives


l Create new document types for purchasingtransactions

l Describe the influencing factors for purchasingdocument screen layouts and modify the fieldselection for purchasing transactions

l Define new long texts for Purchasing, set theappropriate links, and output the texts in messageform

l Describe the message determination process forpurchasing transactions



SAP AG 1999

Purchasing: Business Scenario

l In your company, some of your buyers managesubcontracting purchasing documents only.Since the item category field is not anauthorization object, but the purchasingdocument is an authorization object, you havebeen asked to create a new document type thatonly allows the use of the subcontracting itemcategory.

l The system should output specific long texts andother standard texts when using this newdocument type.

l You have been asked to provide an overview ofthe current purchasing document outputconfiguration and to create the necessarycondition records for the new document type.



SAP AG 1999

Transaction

Purchase requisition

RFQ

Purchase order

Contract

Contract

Scheduling agreementSch. agmt

RFQ

??

4.1.2000

6.1.2000

Number range internal no. assgt

Number range external no. assgt

Number Assignment in Purchasing Transactions

Document type

n The document category is used to characterize the attributes of purchasing documents – purchase requisition, request for quotation, purchase order, and so on.

n You can define separate document types for each purchasing transaction document category. You can assign one number range for internal number assignment and another number range for external number assignment to each document type.

n For contract types that are distributed in decentralized systems, you must define a number range for internal number assignment. The numbers of release orders in the local systems are not unique in the central system and therefore have to be assigned new keys.

n For each number range, you configure the following:

� The interval from which the number is assigned

� Whether number assignment is internal or external



SAP AG 1999

Purchasing document

Doc. type

AllowedAlloweditem categoriesitem categories

Description

Item interval

Field selection reference key

Number ranges

Contract:Standard rel. order quantity

Control

Document Types for Purchasing Transactions

Reference to Reference to requisitionrequisition

IntervalIntervalmaintenancemaintenance

n You configure separate document types for each category of purchasing document. In the document type assignment, you can store follow-on relationships between the document types of different purchasing document categories.

n If several item categories are possible for a document category, you can eliminate individual item categories for a document type in this document category.

n You can assign a number range for internal number assignment and a number range for external number assignment for each document type. You must assign at least one number range.

n You can create new document types.

n You can assign authorizations for individual document types in a document category (objects M_ANFR_BSA, M_BANF_BSA, and so on).

n The control indicator allows you to specify that a certain document type is used for stock transfer processing. In the case of purchase requisitions, you can use this indicator to specify that this document type requires the setting up of an outline agreement.

n Further settings are necessary in the case of document types for stock transport orders.



SAP AG 1999

Screen Layout for Purchasing Transactions

........

........

........ ?

Document type

Item category

Acct assignment category

Authorization todisplay prices

Release status

Transaction

Field selection

n The R/3 System stores separate control strings for each influencing factor.

n In the case of field selection for a purchasing transaction, the relevant control strings are linked at item level. The same linkage rules apply as for the material master record.

n If you select F2, you can view information on the meaning of the individual reference keys and the fields that are assigned to a position in the control string.



SAP AG 1999

Purchasingtransaction item

Account assignmentcategory

Account Assignment Categories

Screen sequence

IR for item

Account grouping

Consumption posting

Non-valuated GR

GR for item

Acct assgt can be changed at IR

Acct assgt can be changed after GR/IR

Description

n The account assignment category is used for each item of a purchasing document.

n You can specify the account assignment categories that are allowed for the individual item categories.

n The account grouping code for the account assignment category allows you to have the R/3 System suggest a consumption account number when you enter a purchasing document item subject to account assignment. You specify this account number when you make the settings for the automatic postings for the transaction Offsetting entry for inventory posting (GBB).



SAP AG 1999

Texts in Purchasing

Text Types in Purchasing Documents and Master Records

Copying Texts

Output of Texts in Messages



SAP AG 1999

Define text type meanings

Adopt from reference document

Link between text types


Link between text types


Text type relevant?

RFQ/QuotationRFQ/QuotationContractContract Purchase requisitionPurchase requisition

Purchase orderPurchase order Scheduling agreementScheduling agreement

Info recordInfo record

Vendor master recordVendor master record

Doc. header

Doc. item

...

pieceConditions

DM

%Info record

Text Types in Purchasing

n For the individual purchasing transaction types, you can define which, and how many, text types can be maintained for the document header and the document items.

n These settings are not client-specific.

n You can indicate if the R/3 System copies the existing text type (if there is one) from a reference document (for example, when copying an outline agreement). In addition, you can set a link to the text types of a master record or to a reference document in a different category. This enables you, for example, to specify the material master record texts that are copied to purchase orders.

n You can change text type descriptions for vendor master records and purchasing info records, and define new text types for vendor master records.

n You can select the text types in the vendor master record that are relevant on a client-by-client basis. You can configure text types for vendor master records centrally at company code level (in Customizing for FI) and at purchasing level (for each purchasing organization).



SAP AG 1999

Example of Copying Texts

BEST PO textGRUNPRUEIVER

Material master Info record

Purchase requisition Purchase order item

AT Note

BT Info recordorder text

o No MText

B01 Item textB02 Item noteB03 Delivery textB04 Material PO text...

F01 Item textF02 Info record PO textF03 Material PO textF04 Delivery text...

n For the texts in purchasing documents, you can specify if the R/3 System can copy a text (and which text or texts) from a master record or another document to the purchasing document and process it further there.

n You can specify a copy sequence. This number defines the sequence in which the R/3 System searches in the source text objects for the appropriate text. It copies the first object in which it finds the text to the target object.

n You can also define a Fixed indicator. This indicator controls if the R/3 System can copy a text from a master record or another document to your document and process it further there. You can choose from the following variants:

� The R/3 System copies the text to the target object (Status ‘_’) and it is fixed immediately.

� The user can copy the text to the target object, if required (Status ‘*’).

� The R/3 System cannot copy the text to the target object (Status ‘N’). The text cannot be changed, but it can be displayed.

n The R/3 System displays a text with status ‘*’ in the document and the text can be copied to the document (that is, it can be fixed), if:

� You change the text and save the document

� You select the text and copy it



SAP AG 1999

Standard textStandard textME_PO_TEXT_01ME_PO_TEXT_01

HeadingHeadingHeader

Header text 1Header text 2Header text 3Header text 4

Item 10Item text 1Item text 2

Item 20Item text 1Item text 2

(Header)

(Item)

10

20

(Supplement)

Text Types in Purchasing Messages

n You can choose the purchasing document text types that are output when the R/3 System transmits a message.

n Document header texts can be output in the form header (before the items) or in the form supplement (after all items). You specify for each document type and each (necessary) print operation (such as new printout and printout of changes) which texts are output in what sequence.

n In addition to the sequence, you can also specify the priority for item texts. This determines the item texts from the purchasing document, the material master record, and the info record that the R/3 System is to output (assuming that there is a reference and the actual text). Text output for a document item depends on the document type, the print operation, and the item category.

n You can define the texts that the R/3 System putputs when a field has been changed, as well as the heading for the individual print operations and documents.

n The form defines the message layout. You can use SAPscript functions to customize the form.

n You should not change the standard form, but create your own forms and assign them in Customizing.

n You can assign the form and the print program in the Customizing menu.



SAP AG 1999

Text key: addressText key: address Text key: letterheadText key: letterhead

Text key: salutationText key: salutationText key: footer linesText key: footer lines

Standard Standard texttext

Purchasing Organization Texts in Messages

n You can specify keys for standard texts. This allows you to define the sender’s address and the footer content on a purchase order output by the purchasing organization concerned.

n The standard text on the SAP standard form must be created with the text ID ADRS.



SAP AG 1999

Message Determination in Purchasing

Message Determination Process

Message Types

Access Sequences and Condition Records

Examples of Messages in Purchasing

Printer Determination



SAP AG 1999

PricingPricing

Condition type Message type Strategy type

Calculation schema/ MessagePricing procedure determination schema

Conditions

Message DeterminationMessage Determination

Terminology used in conditions

Batch DeterminationBatch Determination

Searchprocedure

A

Batch

n The condition technique is used not only in pricing in the MM purchasing application, it is also used in message determination and batch determination.

n The terminology in the applications in which the condition technique is used can vary from application, for instance in purchasing we talk of a calculation schema or pricing procedure. In the area of message determination it is known as a message schema. The condition type in pricing is known in message determination as the message type. The terminology in batch determination is strategy type and search procedure.



SAP AG 1999

Outputting Messages

Newprintout

Deliveryschedule

Orderacknowl.expediter

Expediter/reminder

Rejection

Purchasing document

Printer FaxTelex

Teletex

EDIE-mail

Output

n Each time you save a new purchasing document or one that has been changed (such as an RFQ, a purchase order, or an outline agreement), the R/3 System checks if it should generate an output format for this document. This output format represents a message.

n A message is information that is output using various media, such as a printer, e-mail, EDI, or fax.

n The information that the R/3 System outputs and the format used depends on the message concerned.

n The R/3 System can output messages via various media – this is defined in the document or automatically via message determination.

n The R/3 System places the document to be output in a message queue and it is released from here as required for printing, for output via EDI, and so on. You can either release messages manually or have the system release them.



SAP AG 1999

Message Output Without Message Determination

No message schema is assigned.

The system can only output the message types defined in the standard system (such as NEU).

The system only generates messages using the standardparameters (output medium PRINT, time 1, and IMMEDIATEOUTPUT). You can change the proposed values.

The system determines the printer in the following sequence:• Printer defined for the purchasing group• Printer defined in USER parameter PRI• Printer defined in USER defaults

n You can define separately for each purchasing transaction whether the R/3 System is to use message determination.

n For message output without message determination, you can change the proposed standard parameters in the individual documents.



SAP AG 1999

Message Output with Message Determination

Message determination is controlled using a schema.

Any message type can be output.

The system can suggest the output medium and time depending on the specific values of the influencing factors (such as document type, vendor).

The system only determines the printer in the following sequence:• Printer defined for the message record• Printer defined for the purchasing group

n The aim of message determination is to manage messages according to predefined criteria.

n During message determination, the R/3 System checks if there are “condition records” for the application data that was, for example, defined in Customizing. If this is the case, the system can process one or more messages (for example, send electronically).

n During message determination, the R/3 System searches for condition records according to a predefined hierarchy (access sequence).

n Message determination enables you, for example, to control document output for each vendor individually.

n You can define the schema that controls message determination separately for each purchasing transaction.

n For each message type, you can specify that the R/3 System is to optically archive the document when it is output.

n If you use message determination to output purchasing documents via a printer, the R/3 System determines the printer name from neither the USER parameter PRI nor from the USER defaults.



SAP AG 1999

222

333

444

555

Message Determination Process

Purchase order

Vendor 1001Purchasing organization 1000

Message header

Message Type PartnerNEU 1 DRUCKLF 123

Print parameters:

111

Printer:Output immediately:

Number:

LT60X2

1. New printout NEU2. Reminder MAHN3. Reminder re. AUFB order acknowl.

Message type: NEU

Access sequence: 0001

Access sequence: 0001

1. Doc. type/purchasing organization/vendor2. Document type

Message determ. schemaPurchase order RMBEF0

Records for message types

No valid record existsValid record exists

n The message determination function in Purchasing enables the R/3 System to determine the messages allowed for a purchasing transaction and suggest suitable messages. For example, you can configure the output medium and the output device, if necessary, together with the time and number of copies depending on certain criteria.

n Message determination is activated automatically in the SAP R/3 standard client (000) when you install the client.

n You define the combination of fields for which you want to create message records in a condition table.

n The access sequence is a search strategy that the R/3 System uses to search for valid message records.

n The message type represents different messages in the system – for example, purchase order printouts, order acknowledgements, reminders, and so on.

n You define the message types allowed for each message application (such as reminder, new printout, and so on) in a message schema. You can assign separate message schemas to the individual purchasing document categories (purchase order, contract, RFQ, and so on).



SAP AG 1999

Maintain message types• Indicator for condition access and possibly access

sequence for automatic message generation• Partner roles for different recipient

(such as vendor, ordering address, delivering plant)• Processing program and form (depending on output

medium)• MAIL title and MAIL text for internal use, if required

Fine-tuned control• Define which print operation this message type is defined for

(such as new printout, printout of changes)

NXYZNXYZ

Maintain message schema• Enter message type in schema:

This defines for which purchasing document and underwhich conditions the system generates the message.

Message Types

n Standard message types are supplied for each purchasing document (for example, NEU – Message type for new printout of a purchase order, and printout of changes).

n You can define further message types for each purchasing document type separately.

n You must create message records (condition records) for the individual message types that you want to use. These are data records in which key fields represent the requirement (= condition), under which the R/3 System finds a message. The other fields contain the actual message. Therefore, if one of the data records transferred from the application fits these key fields, the R/3 System finds the message and can process it (for example, output it as a print form or send it as an electronic message).



SAP AG 1999

Influencing Factors for Message Determination

Document 1

Doc. type NBPOrg. 1000

Vendor A

Document 2


Vendor B

Document 3


Vendor C

Document 4


Vendor D

Messagerecord

POrg. 1000Vendor A

Output EDI

Messagerecord


Vendor BOutput FAX

Messagerecord

Doc. type NB

Output Printout

Number 2

n You can configure message determination depending on the type of purchasing document, the purchasing organization, or the vendor.

n You can also define other criteria for message determination in Customizing. When creating condition tables, you select these influencing factors from a field catalog.



SAP AG 1999

Doc. type

NB

UB

Message record

Time: ImmediatelyMedium: PrinterNumber: 1...

POrg. Vendor

1000 1000

2000 ...

Message record

Time: 4pmMedium: FaxNumber: 1...

Seq. no.

1020...

Condition table

POrg./VendorDoc. type...

Condition Tables and Access Sequences

n Condition tables contain the actual message records in which you define the output details, such as time and number of copies. These tables contain the data patterns in which the R/3 System finds the messages (and proposes them for processing) as key fields. Each data pattern of this type corresponds to a condition record in the table. The actual message is described in the data part.

n You can use various key combinations to create condition tables. In the access sequence, you define the condition tables that the R/3 System is to read, and in what order.



SAP AG 1999

Document 1


Vendor A

Document 2


Vendor B

Document 3


Vendor C

Document 4


Vendor D

Condition table 1 for EDI vendors:

POrg. Vendor Message record

1000 ACondition table 2 for telex/fax vendors:

Doc. type POrg. Vendor Message record

NB 1000 BCond. table 3 for remaining vendors:

Doc. type Message record

NB Message details

Example: Message Determination Process

n Depending on the purchasing document type, the R/3 System determines if message determination is active and, if so, the schema that controls the message determination.

n It checks all message types entered for the schema determined and the requirements assigned to those message types.

n If the assigned requirement is met for an (automatically generated) message type, the program determines the access sequence with which it should search through the condition tables for message records.

n You can check the message determination facility using the determination analysis. An overview of all messages defined for your purchasing document appears. The search sequence and the results display the details of the message types for which the requirement is met, as well as the values for the key fields in the condition table.



SAP AG 1999

Enter a purchasingtransaction(such as Create PO)

Predefined messagetype (such as: NEU)

Record exists forthis message type

Print parametercorresponds topurchasing groupcriterion

Rec. contains no output device

Rec. contains an output device

Determination of form dependingon application/messagetype/transmission medium

Message containingoutput device ofpurchasing group

Printer Determination in Purchasing



SAP AG 1999

New Printout and Printout of Changes

Message schema:New message determination if changes are made

Message type NEUMedium: PrintoutTime: 2pmNumber: 1

CreateCreatedocumentdocument

Message type AENMedium: FaxTime: 10pm

ChangeChangedocumentdocument

Message schema:

No newmessage determination


CreateCreatedocumentdocument


ChangeChangedocumentdocument

(1)

2 2

1 1

(1)

n If you change fields that are relevant for printout of changes (see next slide) in a purchasing document that the R/3 System has already output messages for, it creates a new message to inform the business partner about the changes.

n In the activity Assign Message Schema, you can specify separately for each purchasing transaction that the R/3 System is to trigger a new message determination for change messages. This allows you to ensure that it always prints out new documents because a signature is required, but transmits changes via fax.

n Case 1 – No new message determination: You cannot use different message types for print operations “New” and “Changes”. You must define message type NEU in the activity Maintain Message Types→ Fine-Tuned Control for print operations 1 and 2 (“New” and “Changes”). If you have manually changed the output parameters determined by message de termination for the “New printout”, the system uses the changed values when printing out changes.

n Case 2 – New message determination if changes are made: You can use different message type for the print operations “New” and “Changes” (You must have set the indicator for multiple printouts for this message type). In the activity Maintain Message Types → Fine-Tuned Control, you can, for example, specify that the system is to use message type NEU for print operation “New” and message type AEN for the print operation “Change”.



SAP AG 1999

Settings for Printout of Changes

PurchasingPurchasingdocumentdocument

Item data

Header data

Address data(vendor address)

EKKO-ANGDT oþoo K4EKKO-INCO1 þþþþ K5EKKO-KTWRT oþþþ K6EKKO-ZTERM þþþþ K1...EKPO-KTMNG ooþþ P3 2EKPO-LOEKZ þþþþ _ 3EKPO-MENGE þo oo P4EKPO-NETPR þoþþ P7...SADR-NAME1 þþoo P10SADR-NAME2 þþoo P10 SADR-ORT01 þþoo P10SADR-PSTLZ þþoo P10...

Rel. fields B A K L Text no. Routine

n For each individual purchasing transaction, you can define the fields that are relevant for printing. This means that changing one of these fields leads to the R/3 System outputting a purchasing document that has already been output again. The following key is used:

� B = Purchase order

� A = Request for quotation

� K = Contract

� L = Scheduling agreement

n You can also specify the change texts that the R/3 System outputs when printing out changes. You can control the output using a text number (direct assignment) or a routine (indirect assignment).

n You maintain the texts for the text numbers in the Texts for Messages → Change Texts activity. These texts are independent of the purchasing transactions.

n If you use a routine, you can take into account more controls. For example, routine 3 checks if the item has been deleted or blocked. The R/3 System outputs different texts depending on the results of this check.



SAP AG 1999

Purchasing: Summary


l Create new document types for purchasingtransactions

l Describe the influencing factors for purchasingdocument screen layouts and modify the fieldselection for purchasing transactions

l Define new long texts for Purchasing, set theappropriate links, and output the texts inmessage form

l Describe the message determination process forpurchasing transactions



SAP AG 1999

l Naming of account grouping code: K##

l The exercise uses Z as the variable for your accountassignment category. Instead of Z, use the symbol for yourgroup (cf. 2-2-1):

l 2-1-2/3 Account grouping code/general ledger (G/L) account

n Company code 1000 uses the chart of accounts INT.

n Consumption accounts are specified in the trans./event key GBB.

n Which line in the accounting determination table is the right one?

Account Assignment Categories and FieldSelection (1) - Hints to the exercise

## AACat. ## AACat.01 0 12 J02 2 13 L03 3 14 R

: : 15 S09 9 16 V10 H 17 W11 i 18 Y

?



SAP AG 1999

Account Assignment Categories and FieldSelection (2) - Hints to the exercise

l 2-2-2 Field selection for account assignment category

n Setting for production/PP/internal/CO orders

l 2-2-3 Default account assignment

n Account determination for materials without a material masterrecord: Use an entry with valuation class blank.

n Account determination for materials with material masterrecord: Use Material T-T1## (see 2-1-3)

n For the purpose of the exercise, it is sufficient to adjust theaccount determination process just for this example. Inpractice, all transactions/events involved in the accountdetermination process must be checked and extended wherenecessary!



Purchasing Exercises

Unit: Purchasing

Topic: Purchasing Document Types and Number Assignment


• Check and modify the settings for purchasing document types

• Define a new purchasing document type and configure the number assignment for this document type

You have established that a special document type is to be used for procurement via subcontracting in your company.

This enables you to use a different field selection and a separate number range for subcontracting orders. In addition, you can assign different headings and texts for message output.

As a member of the project team, you are responsible for implementing this.

1-1 Number Assignment for Purchasing Documents

1-1-1 In the standard system, which of the keys listed below does the number assignment for purchasing documents depend on?

– Purchasing organization YES / NO?

– Purchasing group YES / NO?

– Document type YES / NO?

– Company code YES / NO?

1-1-2 Which number ranges are assigned for number assignment for purchase orders and purchase requisitions of document type NB?

Internal

External

Purchase requisitions

Purchase orders



1-2 New Document Types for Purchase Requisitions and Purchase Orders

Use the following information to define a new document type for purchase requisitions and a new document type for purchase orders. Recommendation: Copy Without dependent entries and maintain these entries manually. (You require only individual entries and would have to delete a lot of entries otherwise. In addition, you avoid conflicting with the other groups.)

1-2-1 Create a new document type, X##, for purchase requisitions. Do this by copying the document type NB. When executing the copy, select Only copy entry when prompted. Name your document type X##-Preq.

1-2-2 Configure the system so that only internal number assignment is defined for purchase requisitions with the document type X##. Use the number range group that is assigned to the interval 010000000 ... 019999999.

Which number range do you assign your document type?

______________________________________________________

1-2-3 Only subcontracting items are allowed for your document type X##. Make the necessary restriction for this. What do you have to do?

______________________________________________________

1-2-4 Configure the system so that items in a purchase requisition with document type X## can only be converted to RFQ items (document type AN) or purchase order items with your new purchase order type Y##. Note that you have not yet created document type Y##, so it will not be possible to establish this link until after the new purchasing document type Y## has been created.

______________________________________________________

1-2-5 What are the effects of the decision to copy with or without dependent entries?

______________________________________________________

______________________________________________________

1-2-6 Create a new document type, Y##, for purchase orders. Name this document type Y##-PO.

1-2-7 Configure the system so that it assigns the numbers for purchase orders with document type Y## internally from the interval 4700000000 ... 4799999999.



1-2-8 Only subcontracting items and text items are allowed for your document type Y##. Make the necessary setting for this. What do you have to do?

______________________________________________________

1-2-9 Configure the system so that items with purchase order type Y## can be created with reference to items with purchase requisition document types NB and X##. Note the permitted item categories for the purchase requisition document types. Which entries do you need to maintain?

______________________________________________________

______________________________________________________

______________________________________________________

1-3 Characteristics of Item Categories

1-3-1 Find out which indicators are defined for the item category Subcontracting.

Internal display: _____________________________________

External display: _____________________________________

1-3-2 Which characteristics are defined for the item category Subcontracting?

For items belonging to this item category, can you or must you:

a) Use material master records? __________________

b) Enter goods receipts? ______________________

c) Enter invoice receipts? ___________________

d) Are additional account assignments allowed? ____________________

Give reasons for your answer to question b):

______________________________________________________

______________________________________________________

1-4 Check whether your settings are correct for the document types X## and Y## by doing a test in purchasing.

1-4-1 Create a purchase requisition with document type NB and two items for purchasing group L##. In each item, request 100 pieces of material T-B1## for plant 1000, once as a standard item and once using subcontracting.

First purchase requisition: _________________________________

1-4-2 Create a purchase requisition with document type X## for purchasing group L##. Request 100 pieces of material T-B1## for plant 1000 again.

Which item categories are allowed?

______________________________________________________



Second purchase requisition: _______________________________

1-4-3 Check if it is possible to convert your second purchase requisition to a purchase order with document type NB, vendor T-L20C##, purchasing organization IDES Deutschland (1000), purchasing group L##.

Give a reason for the result.

______________________________________________________

1-4-4 Create a purchase order of type Y## using vendor T-L20C##, purchasing organization IDES Deutschland (1000), and purchasing group L## for plant 1000. Refer to both of your purchase requisitions. The unit price is 150.00 UNI. It will be necessary to manually change the standard item category to subcontracting for the item on the requisition that was ordered using document type NB.

Purchase order: _____________________________________

1-4-5 Can you extend this purchase order by a standard item (item category “_”)?

______________________________________________________

______________________________________________________



Exercises

Unit: Purchasing

Topic: Account Assignment Categories and Field Selection


• Check and modify settings for account assignment categories

• Check and modify the field selection depending on the account assignment category

• Assign the consumption account to be proposed, depending on the account assignment category and the material group

Your company requires more account assignment categories for Purchasing to support different account assignments and changes to the field selection. A different field selection is required for subcontracting orders as well. In the project team, you are responsible for these settings.

2-1 Settings for the Account Assignment Category

2-1-1 Display the settings for account assignment category K. Which standard or proposed values for the goods receipt and invoice receipt indicators does this account assignment category contain?

Goods receipt: __________________________________________

Invoice receipt: ________________________________________

2-1-2 Which account grouping (modification) is assigned to account assignment category K?

______________________________________________________

______________________________________________________

2-1-3 As a result of this, which G/L account number does the system propose if you order material T-T1## in plant 1000 for a cost center?

Check the proposal with the automatic account determination settings. Note that the financial transaction is GBB.

______________________________________________________

______________________________________________________



2-1-4 Can you use account assignment type K in purchasing documents for the following items?

- Standard items: ___________________________________

- Subcontracting items: ______________________________

2-1-5 Test these settings by ordering material T-T1## from vendor T-L20D## with purchase order type NB using purchasing organization IDES Deutschland (1000), purchasing group L## for plant 1000 with account assignment to cost center 1000.

Second purchase order: ___________________________________

2-2 New Account Assignment Category

2-2-1 Define a new account assignment category. For your account assignment category, your instructor will assign one of the following to each group: 0, 2, 3, 4, 5, 6, 7, 8, 9, H, I, J, L,R, S, V, W, Y.

TO do this, copy account assignment category K.

2-2-2 When you work with your new account assignment category, you should be able to assign the costs to a cost center or a production order. Also, you should always have to specify the goods recipient. Configure the field selection appropriately. Make these changes to your account assignment category.

2-2-3 In the case of your account assignment category, the system is to propose the following GL accounts for purchasing items for plant 1000:

For materials assigned to valuation class 3000: G/L account 400080

For items without a material number or valuation class: G/L account 400*** (as a template)

Write down the steps required to do this.

______________________________________________________

______________________________________________________

______________________________________________________

Make the necessary settings to accomplish this. Use account modification K##.

Ignore the warning messags that state that G/L account 400*** has not been created. As a template, the user will need to enter the remaining account information when ordering the item.

2-2-4 You should use your account assignment category solely for standard items. How do you make sure of this?

______________________________________________________



2-2-5 Test the settings for your new account assignment category by extending your second purchase order by two new items. For each item, use your new account assignment category. Order one item of 100 pieces of your material T-T1## and one piece of an item without a material number (order by description), both assigned to cost center 1000.

2-3 Field Selection Depending on Item Category

2-3-1 Which field status definition can you use to change the field selection for all subcontracting items without affecting the other item categories?

______________________________________________________

______________________________________________________

2-3-2 What do you have to do if the fields Confirmation control key and Warranty date are to be required fields for purchase orders with your new document type Y## (and only for purchase orders of this type)? Outline the procedure and make the settings.

Add a new entry, Y##F, by copying the entry NBF that was set up for document type NB. ______________________________________________________

______________________________________________________

______________________________________________________

2-3-3 Test Your Settings by creating a purchase order for material T-B1## using your document type Y##. The confirmation control key and warranty date should be required fields. Use Vendor T- :L20C##, purchasing organization IDES Deutschland (1000), plant 1000 and purchasing group L##. You will need to use item category L, subcontracting.



Exercises

Unit: Purchasing

Topic: Text Types and Text Copying


• Make the settings for text types and copying texts from previous documents

After deciding to use a special document type for subcontracting in your company, you now need to make the other settings for texts. As a member of the project team, you have been given the task of performing the configuration.

3-1 Text Types for Purchase Requisitions

3-1-1 Which consecutive numbers do the following text types for purchase requisitions have:

Item text: _________ Delivery text: ___________

Item note: _________ Material PO text: ___________

3-1-2 Which material master texts are the purchase requisition text types linked to? Which indicator is set for copying texts from the material master record to a purchase requisition?

______________________________________________________

______________________________________________________

3-1-3 Check these settings in the application. In the material master, enter a purchase order text for material T-B1##, plant 1000.

Create a purchase requisition with document type X## and request 100 pieces of this material for plant 1000.

Which text types can you maintain?

______________________________________________________

Which text can you not change in the purchase requisition item? What status does this text have?



______________________________________________________

Enter an item text and a delivery text.

Third purchase requisition: ________________________________

3-2 Text Types for Purchase Orders

3-2-1 Which consecutive numbers do the following purchase order header text types have:

Header text: _________ Terms of delivery: _________

Header note: _________ Terms of payment: _________

3-2-2 Which consecutive numbers do the following purchase order item text types have:

Item text: _________ Delivery text: _________

Info rec. note: _________ Material PO text: _________

3-2-3 Which purchase requisition texts are these purchase order item texts linked to? Which indicators are set for copying texts from the purchase requisition?

Item text: _____________________________________

Delivery text: _____________________________________

Info record note: _____________________________________

Material PO text: _____________________________________

3-2-4 Which material master texts are the purchase order item texts linked to? Which indicators are set for copying texts from the material master to the purchase order item?

______________________________________________________

______________________________________________________

3-2-5 Check these settings in the application. Create a purchase order with purchase order type Y## for plant 1000 using vendor T-L20C##, purchasing organization 1000, and purchasing group L##. Refer to your third purchase requisition.

Choose the texts for the header and item in the purchase order. Consider where the system finds the proposed texts, if necessary.

Which status is set for the material PO text in the purchase order item?

Status of the material PO text: ____________________________

Adopt the material PO text to the purchase order item. What status does the text have now?

Status of the material PO text: ____________________________



Which texts in the purchase requisition were copied? Are there differences between copying texts from the material master and copying texts from the purchase requisition?

______________________________________________________

______________________________________________________

3-2-6 Maintain the following texts in the purchase order header:

- Header text - Terms of delivery - Terms of payment

Third purchase order: ____________________________________



Exercises

Unit: Purchasing

Topic: Output of Texts in Messages


• Modify the settings for output of texts

Once you have created a special document type for subcontracting in your company and have also modified the text types and the copying of texts, the next task is to make the settings for output of texts in messages. As a member of the project team, you have been given the task of performing the conversion.

4-1 Text Output

4-4-1 As a heading, the system should print the title Subcontracting when outputting new printouts of purchase orders with your document type Y##.

4-4-2 The system is to output the following texts for purchase orders with document type Y## when printing out a new document.

Standard text name(text object TEXT, Text ID ST):

- Z_LB_EINK → in the form header before all other texts

Purchase order header texts (each with description):

- Header text → in the form header

- Terms of payment → in the form supplement

- Terms of delivery → in the supplement after output of the text ‘Terms of payment’

Purchase order item texts (each without description):

- Material PO text → as the first text for the item

- Item text → as the second text for the item

- Delivery text → as the last text for the item

4-4-3 Display your third purchase order. Select Print Preview, and display the output on the screen and check the result against the settings for your document type.



Exercises

Unit: Purchasing

Topic: Message Determination and Output Control


• Check the settings for message determination in Purchasing

• Define a new message type and make the other necessary settings

For the output of purchase orders, your company has specified that the system is to either output two copies via the printer (a copy each for the vendor and the buyer) or transmit the purchase order by fax for “certain” vendors and, (only) in this case, output a copy via the printer for the buyer.

In your project team, you have been given the task of testing message determination and configuring change requests.

5-1 Message Schema

5-1-1 Which message schema is assigned to the purchasing document type Purchase order?

______________________________________________________

5-1-2 Is message determination triggered again when you print out a change message?

______________________________________________________

5-1-3 Which message types does this schema contain? Which conditions does the system check for these message types?

______________________________________________________

______________________________________________________

______________________________________________________



5-2 Message Types

5-2-1 Display message type NEU. Which access sequence does the system use for this message type?

______________________________________________________

Do you have conditions access for this message type? ___________

Which indicator controls printer determination? __________

5-2-2 Which output operations does the system use this message type for?

______________________________________________________

5-3 Access Sequences

5-3-1 Display the access sequence detail screen for message type NEU. Which sequence does the system access message records in with this access sequence (= sequence of condition tables)?

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

5-3-2 In the Purchasing (application) menu, under Master data, call up the transaction for changing message records for purchase orders.

Which key combination can you maintain message records for message type NEU for? Compare the key combinations with the access sequence.

______________________________________________________

______________________________________________________

5-3-3 Choose the third condition table (Purchasing Output Determination: Document Type) and display the message record (condition record) for message type NEU and document type NB. Write down the following information on this message record:

Transmission medium: ___________________________________

Time: _____________________________________________

Output device: __________________________________________

Indicator for immediate output: ___________________________



5-3-4 Display the message output for your second purchase order (document type NB). To do this, choose the transaction for changing the purchase order. What information appears on the communication data detail screen for this message?


Time: _____________________________________________

Output device: __________________________________________

Why did the system generate a message for this purchase order? Which message record (condition record) does this information come from? You can check this information using the determination analysis.

______________________________________________________

______________________________________________________

5-3-5 Display the message output for your first purchase order (document type Y##). To do this, choose the transaction for changing the purchase order. What information appears on the communication data detail screen for this message?


Time: _____________________________________________

Output device: __________________________________________

Why did the system generate a message for this purchase order? Which message record (condition record) does this information come from?

______________________________________________________

______________________________________________________

5-3-6 Is there a message record for document type Y## for message type NEU in the third condition table (Purchase Output Determination: Document Type)?

______________________________________________________

5-3-7 For document type Y##, specify that the system should output two copies to the “buyer's printer” when the user specifically requests this.

Create a condition record for your document type Y##, however, do not maintain the printer. To assign the printer, use the IMG to assign the printer to the purchasing group.

______________________________________________________

______________________________________________________



5-3-8 Display the message output for your first purchase order again. Choose the transaction for changing the purchase order again. What information appears on the communication data detail screen for this message now?


Time: _____________________________________________

Output device: __________________________________________

Which message record (condition record) does this information come from? ______________________________________________________

5-4 New Message Type

5-4-1 For your own records, you require a printed copy of purchase orders that are transmitted by fax to your vendors. To accomplish this, you will use message type NEU to generate the fax transmission to the vendor, and a new message type to print a copy of the PO. You will need to enter two condition records, one for the fax transmission, and one for the printed copy.

Outline the procedure to add this new message type for purchase orders.

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

Complete the steps necessary to add this new message type for purchase orders.

Step 1. In order to obtain this printed copy, define a new message type, ZP##. Create this message type by copying NEU. When copying this new message type, select ‘Copy All’ when prompted.

Which transmission medium do you have to define for message type ZP##?

Step 2. Add an entry for this message type within the fine-tuned control table. Add an entry for print operation 1 and your message type ZP##.

Step 3. Maintain the message schema RMBEF1 to include your message type. Use step 55 and counter ##. Use requirement 101.



Step 4. Verfiy the permitted partner roles for message type ZP##. The permitted partner roles should have been copied while creating your new message type. If necessary, add at least on new entry for partner role VD and medium 1.

Step 5. Assign an existing output program and form for the output ZP## by copying the entry for message type NEU and transmission medium 1.

5-4-2 Message type ZP## should only result in print output when the original purchase order is transmitted by fax. This is accomplished by creating two condition records for each vendor that will receive a fax transmission; one for the fax transmission to the vendor using output type NEU, and one for the printed copy using output type ZP##.

Can you use the same access sequence to locate this condition record as for message type NEU? Which key combination must you or can you use to maintain the individual message records (condition records)?

Maintain the necessary condition records for Vendor T-L20A##. Use the condition table that includes the vendor, purchasing organization and document type for both output types NEU and ZP##.

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

5-4-3 Test your settings by creating a new purchase order for vendor T-L20A## with document type Y##. Verify the correct message types are display.



Purchasing Solutions

Unit: Purchasing

Topic: Purchasing Document Types and Number Assignment

1-1 Number Assignment for Purchasing Documents

1-1-1 In the standard system, the number assignment for a purchasing document depends only on the document type. The following are not relevant for the determination of the document number:

- The purchasing organization - The purchasing group - The company code

1-1-2 The number ranges that are assigned to document type NB for both purchase requisitions and purchase orders are:

Materials Management → Purchasing → Purchase Requisition or Purchase Order→ Define Document Type

The internal and external number ranges are displayed for each document type.

Internal

External

Purchase requisitions 01 02

Purchase orders 45 41

1-2 Create new document types for purchase requisitions and purchase orders

1-2-1 Choose Materials Management → Purchasing → Purchase Requisition → Define Document Types

Select document type NB

Select copy as

Replace the document type NB with X##.

Select enter

Select only copy entry

1-2-2 Assign the number range 01 for internal number assignment. Remove the assignment of an external number range.

1-2-3 Select document type X##.



Choose Allowed item categories

Select New entries

Enter item category L.

Save.

1-2-4 Select document type X##.

Choose Link purchase requisition – document type

Select New entries

Enter the RFQ document type AN, and item category L for both the purchasing document and the purchase requisition

Save.

Note: since you have not yet created the document type Y## for purchase orders, it is not possible to establish this link at this time.

1-2-5 If you copy a document type with all dependent entries, the system copies all entries necessary. You can use the new document type immediately. You have to delete any entries that are not required in this case.If you copy a document type without dependent entries, you must also add all other entries required. You may not be able to use the new document type immediately.

1-2-6 Choose Materials Management → Purchasing → Purchase Order → Define Document Types

Select document type NB

Select copy as

Replace the document type NB with Y##.

Select enter

Select only copy entry

1-2-7 Assign the number range 47 for internal number assignment. Remove the assignment of an external number range.

1-2-8 Select document type Y##.

Choose Allowed item categories

Select New entries

Enter item category L

Enter item category T

Save.



1-2-9 Select document type Y##.

Choose Link purchase requisition – document type

Select New entries

Enter the purchase requisition document type NB, and item category standard(blank) for the purchasing requisition and item category L for the purchasing document.

Enter the purchase requisition document type NB, and item category L for both the purchasing requisition and the purchasing document.

Enter the purchase requisition document type X##, and item category L for both the purchasing requisition and the purchasing document.

Save.

1-3 Characteristics of Item Categories

1-3-1 Choose Materials Management → Purchasing → Define External Representation of Item Categories.

Select item category L

Select Details

Internal display: 3 External display: L

1-3-2 Display the characterisitcs for the item category subcontracting.

Materials Management → Purchasing → Define External Representation of Item Categories.

Select item category L

Select Details

a) You can use material masters, but they are not absolutely necessary.

b) Goods receipts must be entered for subcontracting items, since that is the only way that the materials provided are posted out of the SAP System as “consumed”.

c) Invoice receipts can be entered but are not absolutely necessary, since you can change the indicator RE in the purchase order item.

d) Additional account assignments are allowed, but are not absolutely necessary.

1-4 Verify the settings for the new document types.

1-4-1 Create a purchase requisition using document type NB.

Logistics → Materials management → Purchasing → Requisition → Create

Before continuing, select Add to Favorites



1-4-2 Create a purchase requisition using document type X##.

Only item category L is allowed.

1-4-3 Attempt to convert the purchase requisition of document type X## to purchase order type NB.

Favorites → Purchasing → Purchase order → Create → Vendor/supplying plant known

To reference the requisition, enter the requisition and line item on the item screen. After selecting Enter, the requisition will be copied into the PO.

However, the second purchase requisition cannot be converted to a purchase order with document type NB because we have not allowed this link.

1-4-4 Create a PO using document type Y## referencing both purchase requisitions.

Both purchase requisitions can be copied to a Y## purchase order. Before being copied, however, you must manually change the item category to subcontracting (L) for the standard item in the first purchase requisition.

1-4-5 No, because the system should only allow you to use the item category L for this document type Y##.



Solutions

Unit: Purchasing

Topic: Account Assignment Categories and Field Selection

2-1 Settings for the Account Assignment Category

2-1-1 Choose Materials Management → Purchasing → Account Assignment → Maintain Account Assignment Categories.

Select account asssignment category K

Select Details

Goods receipt: A goods receipt is linked to the purchase order item, but you can change the indicator. The indicator for a non-valuated goods receipt is not set, but you can set it.

Invoice receipt: An invoice receipt is linked to the purchase order item, but you can change the indicator.

2-1-2 The account grouping (modification) for account assignment category K is VBR.

2-1-3 The G/L account number 400000 is assigned in account determination.

The program determines this G/L account with the keys:

- Chart of accounts INT - Valuation grouping code 0001 - Account grouping VBR - Valuation class 3000

The company code 1000 is assigned to the Chart of accounts INT. The plant 1000 is assigned to valuation grouping code 0001. The account assignment category K is assigned to account grouping VBR. The material T-T1## is assigned to valuation class 3000.

Knowing this information, the G/L account can be determined in the automatic postings table.

Materials Management → Valuation and Account Assignment → Account Determination → Account Determination Without Wizard → Create Automatic Postings

Cancel the pop up window

Select Account Assignment

Select transaction GBB



Select Choose

Enter INT

Locate the correct row for 0001 VBR 3000.

2-1-4 Choose Materials Management → Purchasing → Account Assignment → Define Combinat ion of Item Categories/Account Assignment Categories.

In the training system, you can use account assignment category K for standard items, but not for subcontracting items.

2-1-5 Create a purchase order to test the account determination settings.

Favorites → Purchasing → Purchase order → Create → Vendor/supplying plant known

The system proposes G/L account 400000 for the purchase order item (T-T1##) subject to account assignment with account assignment category K.

2-2 New Account Assignment Category

2-2-1 Define a new account assignment category

Materials Management → Purchasing → Account Assignment → Maintain Account Assignment Categories.

Select account assignment category K.

Choose Copy as

Enter the new account assignment category and description

Save

2-2-2 Configure the field selection.


Select your new account assignment category

Choose Details

Change the field selection for the fields named:

Select Optional for CO/PP order and cost center.

Select Required for goods recipient/ship-to party.

Save

2-2-3 To accomplish this, you need to assign a new account modification for the new account assignment category, such as K##.




Select your new account assignment category

Choose details

Assign K## to your new account assignment category.

Save your changes.

Next, in account determination, you need to add the following entries for the transaction/event key GBB.





Select Choose

Enter INT

Select New Entries

Record the following entries for chart of accounts INT, valuation grouping code 0001 and account grouping K##:

- For valuation class 3000, enter G/L account 400080 - For valuation class "____" (blank), enter G/L account 400***

Ignore both warning messages that state that G/L account 400*** has not been created.

2-2-4 Restrict your new account assignment category for use only with standard items.

Materials Management → Purchasing → Account Assignment → Define Combination of Item Categories/Account Assignment Categories.

Add a new entry for item category Standard and your new account assignment category.

2-2-5 Add additional line items to your existing PO to test the configuration of your new account assignment category.

Logistics → Materials management → Purchasing →Purchase order → Change

The system proposes G/L account 400080 for plant 1000 and material T-T1## for a purchase order item subject to account assignment with the new account assignment category.

The system proposes G/L account 400*** for plant 1000 without a material number for a purchase order item subject to account assignment with the new account assignment category. The buyer must complete the account number.



2-3 Field Selection Depending on Item Category

2-3-1 Choose Materials Management → Purchasing → Purchase Order or Purchase requisition → Define Screen Layout at Document Level.

PT3F for purchase orders

PT3B for purchase requisitions

2-3-2 Choose Materials Management → Purchasing → Purchase Order → Define Screen Layout at Document Level.

Add a new entry, Y##F, by copying the entry NBF that was set up for document type NB.

Select field selection NBF

Select Copy as

Enter Y##F as the new field selection key

Select Enter

Select your new field selection reference key, Y##F

Select Details

Select field selection group deadline monitoring

Select Enter

Change Confirmation Control Key to a required entry

Return to the list of field selection group

Select Administrative Data, Header

Change Warranty date to a required field

Save

Choose Materials Management → Purchasing → Purchase Order → Define Document Types.

Assign field reference key Y##F to your purchase order document type Y##.

2-3-3 Create a new purchase order with document type Y##. You are asked to enter a confirmation control key and the warranty date.

Favorites → Purchasing→ Purchase order → Create → Vendor/supplying plant known



Solutions

Unit: Purchasing

Topic: Text Types and Text Copying

3-1 Choose Materials Management → Purchasing → Purchase Requisition → Define Text Types and Copying Rules.

3-1-1 Item text: 01 Delivery text: 03

Item note: 02 Material PO text: 04

3-1-2 Select the individual text type.

Choose Text linkages. The material PO text in the purchase requisition is linked to the purchase order text from the material master.

Indicator N

3-1-3 First, maintain the purchase order text view of the material master record.

Logistics → Materials management → Material master→ Material → Change → Immediately

Enter a text and save.

Next, create a purchase requisition and determine which text were defaulted to the document, and which can be manually maintained.

Favorites → Logistics → Materials Management→ Purchasing → Requisition → Create

You can maintain text types Item text, Item note, and Delivery text.

The purchase order text from the material master is only displayed – it has status N.

Enter an item text and a delivery text.

3-2 Choose Materials Management → Purchasing → Purchase Order → Texts for Purchase Orders → ...

3-2-1 ... Define Text Types and Copying Rules for Header Texts.

Header text: 01 Terms of delivery: 05 Header note: 02 Terms of payment: 07



3-2-2 ... Define Text Types and Copying Rules for Item Texts.

Item text: 01 Delivery text: 04 Info record note: 05 Material PO text: 03

3-2-3 Which purchase requisition texts are these texts linked to?

Item text: → Purchase order item text, ind. “_” Delivery text: → Purchase order delivery text, ind. “_” Info record note: → no link to purchase req.— Material PO text: → no link to purchase req.

3-2-4 The purchase order item is linked to the purchase order text from the material master. It has the Fix indicator “*”, which allows the material PO text to be adopted to the PO, and then edited from the PO.

3-2-5 Create a purchase order.


The item text and delivery text in the purchase requisition are copied to the purchase order item text (status “_”).

The status “*” is set in the purchase order item for the material PO text. If you adopt the text or change the text, the status is changed to “_”.

3-2-6 Maintain the following texts in the purchase order header:

Enter Header text

Terms of delivery

Terms of payment



Solutions

Unit: Purchasing

Topic: Output of Texts in Messages

4-1 Text Output

4-4-1 Choose Materials Management → Purchasing → Messages → Texts for Messages → Define Texts for Purchase Order

Choose Document Printout: Purchase Order.

Choose Headings and add a new entry for Print operation 1 and your document type Y##.

Enter the title Subcontracting

Save

4-4-2 Choose Texts for document header and add a new entry for Print Operation 1 and your document type Y##. For example, you can specify that the system is to output standard text name Z_LB_EINK (file TEXT, text ID “ST”) with print sequence 5.

Add another new entry for Print operation 1 and your document type Y##. This time you specify that the system is to output the header text (text object EKKO, text ID F01) with print sequence 10, for example. Select Print title.

Save.

Choose Texts for document supplement and add two new entries for Operation 1 and your document type Y##. Specify that the system is to output the texts Terms of payment (text object EKKO, text ID F07) print sequence 12 and Terms of delivery (text object EKKO, text ID F05) print sequence 13. Select Print title.

Save.

Choose Texts for document item and add three entries. Specify that the system is to output the three texts for the item in the specified sequence:

Add a new entry for Print operation 1 and your document type Y##, item category L. This time you specify that the system is to output the Material PO text (text object EKPO, text ID F03) with print sequence 1.

Add a new entry for Print operation 1 and your document type Y##, item category L. This time you specify that the system is to output the Item text (text object EKPO, text ID F01) with print sequence 2.

Add a new entry for Print operation 1 and your document type Y##, item category L. This time you specify that the system is to output the Delivery text (text object EKPO, text ID F04) with print sequence 3.



4-4-3 Display the print preview.

Logistics → Materials Management → Purchasing →Purchase order → Display

Before continuing, select Add to favorites

Select Print Preview

The system displays the maintained and configured texts for your purchase order.



Solutions

Unit: Purchasing

Topic: Message Determination and Output Control

5-1 Message Schema

5-1-1 Choose Materials Management → Purchasing → Messages → Output Control → Message Determination Schemas → Define Message Schemas for Purchase Order → ...

Choose Assign Schema to Purchase Order RMBEF1

5-1-2 Display the assignment of the schema to the purchase order.

No, the M indicator for change message determination is not set for procedure RMBEF1.

5-1-3 Choose Maintain Message Determination Schema: Purchase Order

Select procedure RMBEF1

Select Control NEU Requirement 101 MAHN Requirement 103 AUFB Requirement 107

There maybe additional message types assigned, beyond these three.



5-2 Message Types

5-2-1 Choose Materials Management → Purchasing → Messages → Output Control → Message Types → Define Message Types for Purchase Order → ...

Choose Maintain Message Types for PO

Select output type NEU

Select DetailsAccess sequence Z987

Access to conditions: Yes

Printer determination is carried out using indicator 6.

5-2-2 Choose Fine-Tuned Control: Purchase Order The system uses message type NEU during the print operations 1 (New) and 2 (Change) .

5-3 Access Sequences

5-3-1 Choose Materials Management → Purchasing → Messages → Output Control → Access Sequences → Define Access Sequence for Purchase Order → ...

Select access sequence Z987

Select Accesses

Purchasing Output Determination: Purch. Org./Vendor for EDI Purchasing Output Determination: Doc. Type/Purch. Org./Vendor Purchasing Output Determination: Document Type Purchasing Output Determination (Training): Purch. Org.

5-3-2 You can maintain message condition records for message type NEU in the four condition tables for access sequence Z987, depending on:

- Purchasing organization/vendor for EDI - Document type/purchasing organization/vendor - Document type - Purchasing organization

Logistics → Materials management → Purchasing → Master data → Messages → Purchase order → Change



5-3-3 Transmission medium: 1 Time: 3 Output device: printer device may vary Indicator for immediate output: no

Logistics → Materials management → Purchasing → Master data → Messages → Purchase order → Display

Enter output type NEU, press Enter, and select the key combination Purchasing Output Determination: Document type

Enter document type NB, then execute

Record the medium, and time. To determine the output device and immediate output indicator, select communication

5-3-4 Transmission medium: 1 Time: 3 Output device: printer device may vary

Message record (condition record) for document type NB

Logistics → Materials management → Purchasing → Purchase order → Change

Enter the purchase order

Select Messages

The message output is displayed.

To display the determination analysis:

Select the entry for NEU, then

GOTO → Determin. Analysis

Select NEU, then details

This message record was determined based on the conditon record for document type NB.

5-3-5 Transmission medium: 1 Time: 3 Output device: printer device may vary

Message record (condition record) for purchasing organization 1000.

Logistics → Materials management → Purchasing → Purchase order → Change

Enter the purchase order

Select Messages

The message output is displayed.

To display the determination analysis:

Select the entry for NEU, then

GOTO → Determin. Analysis



Select NEU, then details

This message record was determined based on the condition record for purchasing organization 1000.

5-3-6 No, there is not a record for this document type.

Logistics → Materials management → Purchasing → Master data → Messages → Purchase order → Display

Enter output type NEU, press enter, and select the key combination Purchasing Output Determination: Document type

Enter document type Y##, then execute

“NO conditions records exist for this selection”

5-3-7 First, enter a condition record for the document type Y##.

Logistics → Materials management → Purchasing → Master data → Messages → Purchase order → Create

Enter output type NEU, press enter, and select the key combination Purchasing Output Determination: Document type

Enter document type Y##

Transmission medium: 1 Time: 3

Select Y##

Choose Communication Output device: leave blank Number: 2

The printer must be assigned to the purchasing group. To do this, enter the printer in the IMG:

Materials Management → Purchasing → Messages → Output Control → Assign Output Devices to Purchasing Groups. Assign a printer (request a printer number from your instructor) to your purchasing group.

5-3-8 Transmission medium: 1 Time: 3 Output device: dependent on the printer device assigned to the purchasing group defaults. Number: 2

Message record (condition record) for document type Y##

The printer was assigned from the purchasing group defaults. (This is not visible from the determination anlaysis)



5-4 New Message Type

5-4-1 Create a new message type.

Step 1: Choose Materials Management → Purchasing → Messages → Output Control → Message Types → Define Message Types for Purchase Order → ...

Choose Maintain Message Types for PO

Select the Change mode

Select NEU

Select Copy as

Copy message type NEU and specify transmission medium printer as the default value.. Select “Copy All” when prompted.

Save

Step 2: Choose Fined-Tuned Control: Purchase Order Create a new entry for print operation 1 and your message type ZP##.

Save.

Step 3: Maintain message schema RMBEF1. Choose Materials Management → Purchasing → Messages → Output Control → Message Determination Schemas → Define Message Schemas for Purchase Order

Choose Maintain Message Determination Schema: Purchase Order

Select RMBEF1

Select Control

Add a new entry, with step 55 and counter ## for your message type ZP##. Enter requirement 101.

Save.

Step 4: Maintain the permitted partner roles for message type ZP##. To do this, choose Materials Management → Purchasing → Messages → Output Control → Partner Roles per Message Type → Define Partner Roles for Purchase Order. Verify at least one entry for partner role VD and medium 1are provided. If necessary, add this entry.

Save.

Step 5: Assign an output program and a form for the output. To do this, choose Materials Management → Purchasing → Messages → Forms for Messages → Assign Form and Output Program for Purchase Order. Copy the entry for message type NEU and transmission medium 1.

Save.



5-4-2 Yes, since the determination is based on vendor, purchasing organization and document type, you can use the same access sequence Z987. You must maintain condition records in the second condition table (depending on the vendor, purchasing organization and document type):

Logistics → Materials management → Purchasing → Master data → Messages → Purchase order → Create

Enter output type NEU, press enter, and select the key combination Purchasing Output Determination: Doc Type/Purch. Org/VendorCreate two new entries:

Message type NEU: Vendor T-L20A##, Document type Y## → Medium 2 (Fax)

Message type ZP##: Vendor T-L20A##, Document type Y## → Medium 1 (Print output)

5-4-3 Test your settings


Create a new purchase order with document type Y##. Choose Messages. The system displays message type NEU with transmission medium 2 (if there is a fax number in the vendor master) and message type ZP## with transmission medium 1.



SAP AG 1999

l Elements of the Condition Technique

l Price Determination

l Header, Group and Item Conditions

l Maintaining Conditions

l Customizing Settings for Conditions

Pricing

Contents:



SAP AG 1999

l be familiar with the various elements of thecondition technique and understand how theyinteract

l be able to maintain conditions at variouslevels

l understand how the process of pricedetermination works in the system

l be able to create your own condition types andadjust the price determination process to suityour particular requirements

At the conclusion of this unit, you will:

Pricing: Unit Objectives



SAP AG 1999

l Prices, discounts and surcharges, freight costs,etc. are represented in the system in the form ofconditions. These conditions are used in thedetermination of net and effective prices inpurchase orders. Settings made in Customizingdetermine the details of these pricing elements andhow the price is computed.

Pricing: Business Scenario



SAP AG 1999

PricingPricing

Condition type Message type Strategy type

Calculation schema/ MessagePricing procedure determination schema

Conditions

Message DeterminationMessage Determination

Terminology used in conditions

Batch DeterminationBatch Determination

Searchprocedure

A

Batch

n The condition technique is used not only in pricing in the MM purchasing application, it is also used in message determination and batch determination.

n The terminology in the applications in which the condition technique is used can vary from application, for instance in purchasing we talk of a calculation schema or pricing procedure. In the area of message determination it is known as a message schema. The condition type in pricing is known in message determination as the message type. The terminology in batch determination is strategy type and search procedure.



SAP AG 1999

Surcharge 5%

From 100 pc 3%

Time-Dependent Conditions

Outl. purchaseagreement

General conditionsVendorCondition groupMaterial typeIncotermsInvoicing partyOther

DMDMFFFF

$$

Upper limit 5%

Lower limit 1%

pc % Conditions

$

Info record

Price 1 Price 2

01.01. 12.31.07.01.

Purch. organizationPlant Ref. purch. organization

n Conditions in info records and contracts are always time-dependent. You can specify in Customizing (via the document type) whether time-dependent or time-independent conditions can be maintained in quotations and scheduling agreements. As of Release 4.0A, the standard settings are time-dependent conditions for both scheduling agreements and quotations.

n Conditions in purchase orders are always time-independent conditions.

n Time-dependent conditions can be stored on either a plant-specific or a cross-plant basis (in the latter case, for all plants belonging to a purchasing organization). You can also use conditions negotiated by another purchasing organization (reference purchasing organization).

n In addition to time-dependent conditions that apply to individual info records, or quotation or outline agreement items, you can also define time-dependent conditions reflecting more general pricing arrangements (general conditions).

n Time-dependent conditions can be limited to a certain validity period.

n If a vendor's pricing varies according to the quantity purchased, you can enter it in the form of a price/quantity scale.

n You can specify upper and lower limits for time-dependent conditions in order to prevent agreed maximum or minimum figures from being exceeded in the event that condition values are changed manually in the purchase order.

n Valid time-dependent conditions from info records or outline purchase agreements are adopted as default values in purchase orders.



SAP AG 1999

Maintaining Time-Dependent Conditions

. . .

. . .Per contractPer info record. . .

. . .

. . .Per vendorPer condition groupPer material typePer invoicing party. . .

. . .

Condition typeRL01RGR0MAR1REST

Vendor discountGroup discountMisc. provisionAccount discount

Other. . .

CreateCreate by referencingChangeDisplay

. . .

1) Condition types GAU2, NAVS

2) Own condition types

Prices

Discounts/surch.

Master data. . .

. . .Conditions

Master data. . .

Conditions. . .

Master data. . .

. . .Conditions

n Time-dependent conditions can be maintained using the Master data menu in Purchasing (Master data → Conditions → Prices or Discounts/surcharges). SAP recommends that you do not maintain info record, outline agreement and quotation conditions using the Master data menu but maintain them in the relevant documents or in the info record.

n You can maintain general conditions using the Master data menu that apply, for example:

� To all the materials supplied by a vendor (vendor discount, condition type RL01)

� To all the materials belonging to a vendor condition group (condition group discount, condition type RGR0)

n There are special condition maintenance functions for the general standard condition types supplied by SAP (for example, RL01 and RGR0) (Master data → Conditions → Discounts/surcharges → By vendor/By condition group).

n For your own condition types, which cannot be maintained using the info record or outline agreement, you must use the general condition maintenance function (Master data → Conditions → Other → Create/Change).

n You must also use the general condition maintenance function for the standard condition types GAU2 and NAVS. You should only use the general maintenance function for other standard condition types if expressly advised to do so by SAP.



SAP AG 1999

Price Determination Process: Overview

Calculation schemaStep1...

. . .Cond. type ...PB00

Condition type: PB00Access sequence: 0002

Access sequence: 0002Condition tables:1. Contract item (excl.)2. Plant info record (excl.)3. Info record (excl.)...

Purch. order

Pur. org. 1000Vendor A

For plant 1000Material 1

10 pc

Condition tableContract itemNo record exists

Condition tablePlant info recordMaterial 1 50.00From 500 pc 48.00

50.00

n When you create a purchase order, a contract release order, or a delivery schedule (under a scheduling agreement), the R/3 System searches existing info records and documents for valid conditions and adopts any it finds as default values in the new document.

n The price determination process is carried out in a number of steps:

� First, the relevant calculation schema is determined.

� The R/3 System then searches for condition records for all condition types listed in the calculation schema that have an access sequence assigned to them.

� The search for condition records is carried out in the order specified in the access sequence.

� The search is concluded when a valid condition record is found.

n Material-specific discounts and surcharges are supplementary conditions linked to the gross price (condition type PB00). No access sequence is assigned to a supplementary condition in Customizing for the condition type. No separate price determination is carried out for supplementary conditions. They are found using the condition record for the gross price.



SAP AG 1999

Condition Types

Key Description Control

PB00

FRB1

SKTO

Gross price

Freight, absolute

Cash discount

Condition class: PricesCalculation type: Quantity-dependentCondition cat.: Base priceAccess sequence: Gross price

Condition class: Discount/surchargeCalculation type: Fixed amountCondition cat.: Delivery costs

Condition class: Discount/surchargeCalculation type: PercentageCondition cat.: Cash discount

n The individual conditions are described by means of condition types. There are condition types for the gross price, various discounts and surcharges, freight charges, fixed costs and so on.

n Condition types are defined together with their control parameters in Customizing.

n Condition types are differentiated broadly using the condition class and more finely using the condition category.

n The calculation type (or rule) stipulates how the R/3 System calculates the condition value. For example, a discount or surcharge can be a percentage of the gross price, a fixed amount or a quantity-dependent amount.

n The plus/minus sign determines whether a condition is treated as a negative or positive amount. Negative amounts are discounts (deductions), positive amounts are surcharges (additions).

n The scale basis (or reference magnitude) for scales also depends on the condition type. A scale can be based on quantity or dollar value, for example.

n An access sequence may be assigned to a condition type. The access sequence is a search strategy that enables you to specify the order in which condition tables are to be searched for relevant entries for a condition type. In the standard R/3 System, no access sequences are assigned to the condition types for discounts and surcharges (RA00, RA01 and so on.) because they do not have separate validity periods. They are always maintained at the same time as the gross price (PB00) and their validity period is always the same as the validity period of the gross price.

n You can define your own condition types.



SAP AG 1999

Customizing: Condition Type

Cond. class

Calculation type

Condition category

Control data 1

Header condition

Group condition

Item condition

+/- sign

Access sequence

Group condition

Manual entry

Condition type ZXYZ

Change options

Master dataPricing procedure

Scale basisScales

Scale type

AccrualControl data 2

...

...

...

...

...

...

n A condition type defines the properties and characteristics of a pricing element. Condition types are defined in Customizing. You should not change the standard condition types.

n If conditions with their own validity period are to be maintained for a certain condition type, this condition type must have an Access sequence assigned to it.

n A Condition class (for example, A = discounts or surcharges) and a Calculation type must be assigned to a condition type. The calculation type specifies whether the condition amount is defined as an absolute amount, an amount per unit of quantity, weight, or volume or as a percentage. Furthermore, a Condition category may have to be assigned to the condition type.

n A condition type can be defined as a Header condition and/or an Item condition, as well as a Group condition.

n The Plus/minus sign determines whether the condition type is treated as a discount (deduction) or surcharge (addition).

n Whether condition amounts or values can be changed or deleted is determined by the change options, particularly by the Manual entry field.

n A Calculation schema (”pricing procedure”) for supplementary conditions must be assigned to the condition type for the gross price.

n The scale basis for a scale defines how the R/3 System interprets a condition price scale. For example, the scale can be based on a value, a quantity or a weight.

n Using the Scale type, you specify whether the scale values of the condition represent the upper or lower limit for the price, discount or surcharge.



SAP AG 1999

Access Sequence

Cond. ty.

PB00

Control

Access sequence 0002

Access sequence

0002

No.

10

20

Condition table

. . .

A017 (Info record w. plant)

A018 (Info rec. w/o plant)

30

Exclusive

n An access sequence can be assigned to a condition type.

n An access sequence is a search strategy that enables you to specify the order in which condition tables are to be searched for relevant entries for a condition type. In the case of a price, for example, you can specify that the R/3 System is first to search for a plant-specific price – it is to search for a general, cross-plant price only if it cannot find a plant-specific one.

n The order of the accesses is determined by the order of the condition tables in the access sequence.

n The Exclusive indicator determines that the search for further valid entries in (other) condition tables is interrupted if an access was successful and a relevant entry was found.

n You define the prerequisites according to which the R/3 System searches certain condition tables for relevant entries using requirement routines. Certain condition tables are accessed only if the document item satisfies certain criteria.

n A condition type must have an access sequence assigned to it if you want to maintain conditions with their own validity periods (for example, condition type PB00).

n In the standard R/3 System, no access sequence is assigned to the condition types for discounts and surcharges (RA00, RA01and so on) because they do not have a separate validity period. They are always maintained at the same time as the gross price (PB00) and have the same validity period as the latter.

n You cannot assign an access sequence to a header condition.



SAP AG 1999

Customizing: Access Sequences

Access sequence0002 Gross price

Accesses

SNo.

10152025. . .

Tab.

68166717

Description

Agreement item, plant-dependentContract itemPlant info record per order unitMaterial info rec., plant-dependent

Requirement

3635

Excl.

Fields

Condition

LIFNRMATNREKORGWERKSESOKZ

Doc. structure

KOMKKOMPKOMKKOMPKOMP

Doc. field

LIFNRMATNREKORGWERKSESOKZ

Direct value source

n The access sequence is a search strategy through which you specify the order in which condition tables are to be searched for relevant entries for a condition type.

n The order of access is determined by the order of the condit ion tables in the access sequence.

n Using requirement routines, you specify the prerequisites according to which the R/3 System searches through certain condition tables for relevant entries. Requirement routines can be created in Customizing for Sales and Distribution as ABAP form routines.

n You use the Exclusive indicator to specify that the search for further valid conditions in (other) condition tables is stopped if an access was successful and a relevant entry found.

n The field contents with which a condition table is to be accessed are also defined in the access sequence, through the assignment of source fields from the document to the key fields of the condition table. Typically, accessing of the condition tables is carried out with the content of a field from the document header and/or the document item. However, you can specify a Direct value for the access. To define your own access sequences, the key should begin with the letter Z. When creating your own access sequences, pay special attention to the order of the fields. It is detrimental to system performance if a header field follows an item field in the field sequence.

n You should not change the standard access sequences.



SAP AG 1999

4321

Condition Records and Condition Tables

Condition table A017 (info record with plant)

Cond. ty. Vendor Material Pur. org. Plant . . . Cond. rec. no.

PB00 A 1 1000 1000 1234

Condition table A018 (info record without plant)

Cond. ty. Vendor Material Pur. org. . . .

PB00 A 1 1000

Cond. rec. no.

4321. . .

Table KONP (item conditions)

Cond. rec. no.

1234

PB00 . . .

Cond. ty. . . .

PB00 . . .

11.00

Cond. amount

10.00

. . .

. . .

. . .

. . .

n Conditions are stored in the system as condition records.

n Condition tables reference condition records. Condition tables enable you to vary the key structure of condition records.

n There are condition tables with the following key fields

� Vendor, material, purchasing organization, info record category

� Vendor, material, purchasing organization, plant, info record category

� Vendor, material, purchasing organization, info record category, order unit

� Purchasing document, item, plant

n Entries in condition tables consist of a key part and a data part. The data part contains the number of a condition record.

n Condition records are stored in the following transparent tables

� KONP (time-dependent conditions)

� KONH (header conditions)

� KONM (quantity scales)

� KONW (value scales)



SAP AG 1999

Customizing: Condition Tables

Table 999

Technical view

Selected fields

Purch. organization

Purchasing doc.

With validity period

ChooseLineTextField name EVRTN. . .

Activate

Table A999 activatedReports and screen flagged forgeneration

Field catalog

Order unitCompany codePurch. organization

Purchasing doc.. . .

n Condition tables refer to condition records. Condition tables enable you to vary the key structure of condition records. You should not change a standard condition table.

n You can create your own condition tables. The name of the table must be a number between 501 and 999. If you make no specification, the R/3 System assigns a sequential number.

n To create a new condition table, you must first check whether the existing fields in the field catalog are sufficient for your requirements. You may first have to extend the field catalog. You can include all the fields of the communication structures KOMK, KOMP and KOMG in the field catalog.

n To maintain time-dependent conditions, your new condition table must be defined as a condition table with a validity period.

n Choose the key fields for your condition table from among the allowed fields (fields in the field catalog).

n Finally, you must generate your condition table. Through the generation process, your new condition table is activated and the reports and screens for condition maintenance flagged for generation.

n You can maintain conditions for a new condition table only if the condition table is used in an access sequence.



SAP AG 1999

Calculation Schema

Step

1

Counter

1

Cond. ty.

PB00

10 1 RB00

. . . . . . . . .

10 9 ZA01

. . . . . . . . .

20 0

. . . . . . . . .

31 1

. . . . . . . . .

FRA1

35 1

40 0

SKTO

Fr. . . .

1

20

20

Description

Gross price

Absolute discount

Freight %

Cash discount

Effective price

% Surcharge on gross X

StatManu.

X

X

Net value incl. discount

X

X

n In MM, the framework for determining the purchase or valuation price is “price calculation schema”, which groups together all the condition types that are relevant to this process. (Note that in the SD area such calculation schemas may be referred to as “pricing procedures”.)

n Among other things, the calculation schema defines the:

� Permissible condition types

� Condition types for which conditions are adopted automatically (Manu. indicator)

� Condition types for which the net price calculation is applied (Stat. indicator)

� Order in which the condition types are taken into account in the calculation of the net or effective price

� Condition types for which subtotals are calculated

� Requirements that must be satisfied before a certain condition type is taken into account

n In addition, the From reference step for percentage conditions is defined in the calculation schema. The From reference step can be combined with a To reference step.



SAP AG 1999

Sequence of Conditions


Cnt.

1234

C.ty.

RB00RC00RA00RA01

Description

Abs. discountDiscount/qty.% disc. on net% disc. /gross

Conditions for item 10C.ty.

PB00RA00RB00

Description

Gross price% disc. on netAbs. discountNet value

Amount

100.00 2%

10.00 88.00

Pur. order


Cnt.

0000

C.ty.

RB00RC00RA00RA01

Description

Abs. discountDiscount/qty.% disc. on net% disc./gross.

Conditions for item 10C.ty.

PB00RB00RA00

Description

Gross priceAbs. discount% disc. on net Net value

Amount

100.00 10.00

2% 88.20

Pur. order

n The step numbers of the condition types in the calculation schema determine the sequence (order) in which the condition types are taken into account in the calculation of the net or effective price. This sequence cannot be changed in the document even if the condition types are entered manually.

n Condition types assigned to the same step in the calculation schema are sorted by means of a counter. With these condition types, the order of manual entry decides the point at which the condition type is taken into account in the calculation of the net or effective price.



SAP AG 1999

Price Determination Process: Overview


. . .Cond. type ...PB00

Condition type: PB00Access sequence: 0002

Access sequence: 0002Condition tables:1. Contract item (excl.)2. Plant info record (excl.)3. Info record (excl.)...

Purch. order

Pur. org. 1000Vendor A

For plant 1000Material 1

10 pc

Condition tableContract itemNo record exists

Condition tablePlant info recordMaterial 1 50.00From 500 pc 48.00

50.00

n When you create a purchase order, a contract release order, or a delivery schedule (under a scheduling agreement), the R/3 System searches existing info records and documents for valid conditions and adopts any it finds as default values in the new document.

n The price determination process is carried out in a number of steps:

� First, the relevant calculation schema is determined.

� The R/3 System then searches for condition records for all condition types listed in the calculation schema that have an access sequence assigned to them.

� The search for condition records is carried out in the order specified in the access sequence.

� The search is concluded when a valid condition record is found.

n Material-specific discounts and surcharges are supplementary conditions linked to the gross price (condition type PB00). No access sequence is assigned to a supplementary condition in Customizing for the condition type. No separate price determination is carried out for supplementary conditions. They are found using the condition record for the gross price.



SAP AG 1999

Customizing

Schema Determination

Schema gr.purch. org.

0001

0001

Schema gr.vendor

01

02

Calculationschema

RM0000

YM0000

ZM0000

XM0000

Purch. org.

2000

3000

Schema gr.

0001

0001

Purch. order

Pur. org. 1000

Vendor A

Vendor ASchema group 02

n You can predefine how the calculation schema is determined for standard POs and stock transport orders, the calculation of the market price in vendor evaluation and for external services management (as of Release 4.0A).

n You have the following options with regard to schema assignment for standard POs:

� You can assign a generally valid calculation schema (in the standard R/3 System, RM0000)

� You can make the assignment of a calculation schema dependent on a schema group for one or more purchasing organizations and/or a schema group for one or more vendors.

n The schema group comprises those purchasing organizations or vendors to which the same calculation schema is to be assigned. Schema groups are defined in Customizing. The assignment of purchasing organizations to schema groups is also made in Customizing, whereas the assignment of a vendor to a schema group must be made in the relevant vendor master record.

n Schema assignment for stock transport orders depends on the schema group of the purchasing organization, the document type and/or the supplying plant. Schema assignment for the calculation of the market price in vendor evaluation depends on the purchasing organization. The calculation schema for external services management depends on the document type. In this case, you should note that a uniform calculation schema per document type must be chosen for the documents RFQ/quotation (AN), purchase requisition (NB), and purchase order (NB).



SAP AG 1999

Calculation schemaStep1

Condition typePB00

Purch. order

Pur. org.Vendor

For plantMaterial

Access Sequence for Gross Price

1000A

10001

Condition type PB00Access sequence: 0002

Access sequence 0002No.

101520

253545...

Tab.

681667

171828

Contract item, plant-dependentContract itemPlant info record per order unit

Material info record, plant-specificMaterial info recordInfo record for non-stock material

Requirement

Plant info record exists,variable order unit activePlant info record exists

Item without material

Condition tableNo. of condition record

n The access sequence is a search strategy defining the order in which condition tables are searched for relevant entries for a condition type. The order of accesses is determined by the order of the condition tables in the access sequence.

n A vendor’s gross price for a material can depend on a variety of factors. There are different condition tables with different combinations of key fields for the various price-influencing factors, for example:

� Table A068 – for gross prices in plant-specific outline agreement items

� Table A016 – for gross prices in the items of centrally agreed contracts

� Table A067 – for order-unit-dependent gross prices in plant-specific material info records

� Table A017 – for gross prices in plant-specific material info records

� Table A018 – for gross prices in material info records

� Table A025 – for gross prices in plant-specific non-stock-material info records (info records without a material number).

n You can differentiate between gross prices, discounts and surcharges for different variants of a configurable material.

n Requirement routines are used to determine the prerequisites by which the system searches certain condition tables for relevant entries. Some condition tables are accessed only if the document item fulfills certain criteria.



SAP AG 1999

Info Record and Order Price History

Info record

Condition:

Valid:

10.00

01.01. - 06.30. Purch. order 123

Item Mat. Price

10.50

Purchase order

Pricing date: 07.01.

Item Mat. Price

10.50

Purchase order

Pricing date: 06.01.

Item Mat. Price

10.00

Quotation inresponse to RFQ

Item Mat. Price

10.00

Order price historyPO no. 123: 10.50

Order price historyPO no. 123: 10.50

n An info record can be created either manually or automatically (using the info update indicator). If an info record is created manually, the gross price and supplementary conditions can be maintained for a certain validity period. You can enter scales and upper and lower limits.

n If an info record is generated from a contract, the gross price and all supplementary conditions are adopted in the info record.

n If an info record is created from a PO or scheduling agreement, the conditions are adopted in the order price history not in the info record.

n If info record conditions exist and are valid, they are suggested (that is, they appear as default values) when a new PO is created. The conditions from the order price history (that is, the price and conditions of the last PO) are used as default values only if the R/3 System was unable to find any valid info record conditions.

n In info record list displays, a distinction is made between info record conditions (headword “condition”) and the conditions of the last PO (headword “purchase order”).



SAP AG 1999

Scales

Price Surcharge

From 1 pc500 pc

1000 pc

100.00 UNI99.00 UNI96.00 UNI

To 500.00 UNI1000.00 UNI

50.00 UNI30.00 UNI

Scale typeScale basis

(= From scale) (= Qty. scale)

Customizing condition type

Condition record (KONP)

Scale lines (KONM/KONW)

AC

Scale typeScale basis

BB

(= To scale) (= Value scale)

n A vendor’s gross price for a material (or a discount or surcharge) can vary – for example, according to the quantity ordered. In this case, you must enter the conditions in the form of a scale. Scaled conditions consist of one or more scale levels. Each scale level consists of a scale value and a scale amount depending on the latter. For example: ⌧Above 1000pc 96.00 UNI | Scale value | Scale basis | Scale amount |

n The first scale level should always start with 1 or 0, for example.:

� Gross price from 1 pc upwards 100.00 UNI; from 100 pc 99 UNI, � Discount from 0 pc upwards 0 %; from 500 pc 2.5 %.

n The scale type and the scale basis for a scale are defined for the condition type in Customizing. Using the scale type, you specify whether the scale values of the condition represent the upper or lower limits for the price, discount or surcharge. There are ”From” scales (scale type A) and ”To” scales (scale type B). If no scale type has been assigned to a condition type in Customizing, you can specify whether the scale is to be maintained as a From or To scale before entering the lines of the scale. You specify how the R/3 System is to interpret the price scale for a condition by means of the scale basis. For example, the scale can relate to a money value (scale basis B), a quantity, (scale basis C) or a weight (scale basis D or E).

n Scaled conditions are stored in the tables KONM and KONW.



SAP AG 1999

Header, Group, and Item Conditions

Purchase order

Mat.

1

4

5

Item

10

20

40

Mat. gr.

001

009

009

Qty.

1

1

10

Price

81.00

72.00

63.00

Per purchase order: 20.00 freight surcharge

Mat. group discount:

5% from 100.00

Special discount for material 5

1% from 10 pc upwards

n Item conditions are conditions relating to a single item of a document.

n Header conditions are entered in the header of a document and relate to all the items of that document.

n Some standard condition types can be used only as item conditions, some only as header conditions and others as both header and item conditions. Usage options are determined by the Header condition/Item condition switch in Customizing for the condition type.

n No automatic price determination process is carried out for header conditions. For this reason, you cannot assign an access sequence to a header condition (except if it is also defined as an item condition) or create condition records for such a condition.

n A condition type can be defined as a group condition in Customizing. A group condition is a condition relating to several items of a document. In the case of a group condition, the condition values (price, order quantities, weight or volume) of the relevant items are added and the total used as the condition basis. This allows more favorable values to be taken as a basis for the scale computation than would be the case if individual items were considered. The grouping of items is carried out using the key of the condition record for the group condition or by means of a group condition routine assigned to the condition type in Customizing.



SAP AG 1999

Header Conditions

Purchase order

Mat.

1+ surcharge

2+ surcharge

3+ surcharge

Pos.

10

20

30

Qty.

1

1

1

Price

300.00 10.00

100.00 10.00

50.00 10.00

Header conditionZB00 Abs. surcharge 10.00

ZB00 Group condition =ZB00 Abs. surcharge 10.00

Purchase order

Mat.

1+ surcharge

2+ surcharge

3+ surcharge

Item

10

20

30

Qty.

1

1

1

Price

300.00120.00

100.00 40.00

50.00 20.00

Header conditionHB00 Header surch. 180.00

HB00 group condition =180.00 Total

n Header conditions apply to all the items of a document and are apportioned among the items automatically.

n A header condition may involve a percentage or a fixed amount. If you have specified a header condition in the form of a percentage discount or surcharge, this percentage applies to all the items of the document automatically. If the header condition involves a fixed amount, the value of the condition can be assigned to each item or spread proportionately among the items.

n The condition value is spread proportionately among the document items if the condition type has been defined as a group condition in Customizing. If the condition type has not been defined as a group condition, the value of the header condition is assigned to each item, in which case the header condition constitutes an entry aid.

n In the standard R/3 System, the apportionment of an absolute header condition is carried out on a value basis. However, you can specify in Customizing that apportionment is to be according to the weight or volume of the individual items. The basis for apportionment is specified in the Base formula field of the calculation schema.



SAP AG 1999

Material 1

PB00 Gross price

Group Conditions and Scales

Info record conditions

From

From

From

1 pc

100 pc

900 pc

100.00

99.00

90.00

Purchase order

Mat.

1

1

Item

10

20

Qty.

80

40

Cost center

A1

A2

Condition type PB00

Group cond. =

Customizing Purchase order

Mat.

1

1

Item

10

20

Qty.

80

40

Price

99.00

99.00

Cost center

A1

A2

Price

100.00

100.00

n A condition type can be defined as a group condition in Customizing. A group condition is a condition that relates to several items of a document. In the case of a group condition, the values (price, order quantities, weight or volume) of the relevant items are added and the total used as the condition basis. This allows more favorable values to be taken as the basis for the scale computation than would be the case if individual items were considered. The grouping of items is carried out using the key of the condition record for the group condition or using a group condition routine assigned to the condition type in Customizing.

n Solong as the document has not yet been saved, a price determination process is carried out for each document item in isolation, and the condition basis determined. Only after the document is saved are the item values cumulated. Then, the scale amount is determined on the basis of the cumulated item values.

n You can explicitly initiate the determination of the scale amount on the basis of the cumulated item values on the header condition screen by activating the conditions. Both the activation of the conditions and saving the document constitute opportunities to verify the determination of the lower scale amount.



SAP AG 1999

l be familiar with the various elements of thecondition technique and understand how theyinteract

l be able to maintain conditions at various levels

l understand how the process of pricedetermination works in the system

l be able to create your own condition types andadjust the price determination process to suityour particular requirements

You should now:

Pricing: Unit Summary



Exercises

Unit: Elements of the Condition Technique

At the conclusion of this exercise, you will be able to:

• Describe the elements of the condition technique and their interaction

• Examine differences between, and maintenance of, time-dependent and time- independent conditions

• Define important control parameters for condition types and calculation schemas

Your purchasing department needs a method for storing and determining purchase prices for materials. In the R/3 System, the condition technique is used to determine purchase and valuation prices. This technique is based on conditions that are described by condition types, stored in condition records and condition tables, found by means of access sequences, and arranged in calculation schemas.

1-1 In your role in the procurement area, there are certain tasks that you perform on a regular basis. To facilitate the completion of your tasks, activate the menu for the activity group for SAP_MM_Buyer and assign it to your user.

1-2 Select Documentation and read the description of this activity group.

1-3 Create an info record with the following data: Vendor: T-L21A## Material: T-REK## Purchasing organization: IDES (1000) Planned delivery time: 10 days Purchasing group: Z21 (LO521 Buyer) Standard quantity: 100 Gross price: 9.90 UNI (from 1 pc)

9.50 UNI (from 100 pc) 9.00 UNI (from 500 pc)

Discount % on net: 1% (from 1 pc) 2% (from 500 pc)

Freight (value): 50.00 UNI

The conditions are valid until the end of next year.



1-3-1 What condition types do you use?

Condition Condition type

Gross price

Discount % on net

Freight (value)

1-3-2 Add the task from the above exercise to your Favorites.

1-4 Vendor T-L21A## also grants a scaled discount on all materials for a limited period of time:

• 3% from a condition value of 1000 UNI upwards



The discount is valid for a period of four weeks, starting today.

Maintain the vendor discount for purchasing organization 1000.

If a discount or surcharge is to apply only from a certain value upwards, you should insert a zero line in the scale, for example: From 0.00 UNI: 0% From 1000.00 UNI: 3%

1-4-1 Add this task to your Favorites.

1-5 Now create a purchase order:

Vendor: T-L21A##

Purchasing organization: IDES (1000)

Purchasing group: LO521 Buyer (Z21)

Delivery date: In 2 weeks (applies to both items)

Item 1: Order 120 pc of material T-REK## for plant 1000.

Item 2: Order 560 pc of material T-REK## for plant 1100.

1-5-1 Must you enter an order price? ______________________________________________________

1-5-2 Before saving, check the conditions for both items and determine the amounts/percentages for each:



Item 10 Item 20

Gross price (per 1 pc)

Discount % on net

Vendor discount

Net price (per 1 pc)

Freight surcharge

Cash discount

Actual price (per 1 pc)

Save your purchase order. Purchase order: ___________________


1-6 Display the Customizing settings and determine the specified control parameters for the following condition types:

Condition type

Access sequence

Condition class

Calculation type

Condition category

Plus/ minus

PB00

RA00

RB00

RC00

RL01

FRB1

SKTO



1-7 Create an additional info record:

Vendor: T-L21A##

Material: T-REL##


Planned delivery time: 10 days


Standard quantity: 100

For this material, you have negotiated the following conditions with your vendor, which are valid indefinitely:

Gross price: 120.00 UNI

Discount % on gross: 1%

Discount/quantity: 2.00 UNI (from 1 carton) 5.00 UNI (from 10 cartons) 10.00 UNI (from 50 cartons)

Be sure to scale the discount/quantity by carton, not pc.

Discount (value): 20.00 UNI (from 1 pc)

120.00 UNI (from 500 pc)

Discount % on net: 1.5%

1-7-1 What condition types did you use for the above conditions?

• Gross price _________________________________

• Discount % on gross _________________________________

• Discount/quantity _________________________________

• Discount (value) _________________________________

• Discount % on net _________________________________

Save your info record.



*1-8 Display the control data for calculation schema RM0000 and ascertain the sequence of the following discount condition types:

Condition type Step Counter

RB00

RC00

RA00

RA01

HB01

RL01

RGR0

*1-9 Create a purchase order.

Vendor: T-L21A##



Delivery date: In 8 weeks

Order 500 pc of material T-REL## for plant 1000.

Check the conditions of your purchase order item and compare the sequence of the discount conditions with the sequence in your info record and in the calculation schema.

1-9-1 In which sequence are the discount conditions adopted in the purchase order?

______________________________________________________



Exercises

Unit: Price Determination

Topic: Customizing Settings

At the conclusion of this exercise, you will be able to:

• Examine how the R/3 System finds the appropriate calculation schema

• Create condition types and calculation schemas by copying existing data

Your purchasing policy dictates that prices should automatically default into purchase orders whenever possible. Since you negotiate with vendors and agree on prices ahead of time, you often create info records to facilitate this process. When a purchase order is created, the R/3 System finds the appropriate calculation schema and carries out the price determination process.

2-1 Create a new condition type Z##A by copying the standard condition type PB00. Name your condition type TAMM Gross price ##.

Save your condition type.

2-2 Read the IMG documentation for the node Define calculation schema.

2-3 Create a new calculation schema ZM00## with the title Document Schema TAMM-##, by copying the standard calculation schema RM0000 with all dependent entries.

During the copying process, the R/3 System will repeatedly issue the warning message You should use the counter only for manual item conditions. Acknowledge this and any other warnings by choosing Enter each time.

2-4 Create a second new calculation schema YM00## with the title Supplementary Conditions TAMM-## by copying the standard calculation schema RM0000 with all dependent entries. Acknowledge the repeated warnings by choosing Enter each time.

2-4-1 In both new calculation schemas YM00## and ZM00##, replace the standard condition type PB00 with your condition type Z##A.

Save your calculation schemas.



2-5 Now change your condition type Z##A by assigning your new calculation schema YM00## to it as the supplementary schema instead of the standard calculation schema.

Save your change.

2-6 Create a new vendor schema group ## with the title Schema group TAMM-##.

For course participants belonging to group 01:

Schema group 01 already exists in the standard system and need not be created. Simply change the title.

Save your schema group.

2-7 Now define the schema determination process by assigning your calculation schema ZM00## to your vendor schema group ##. The assignment should be independent of the purchasing organization.

Save your assignment.

2-8 Assign your schema group ## to vendor T-L21B## on the purchasing data screen of the vendor master record for purchasing organization 1000.

Save your assignment.




Solutions

Unit: Elements of the Condition Technique

1-1 Select Other Menu.

Select Activity group SAP_MM_Buyer.

Select Assign users.

Enter your user name and select Add users.

Select Yes to Generate profile and compare user masters.

The next time you log on, you can select User menu to call up this menu.

1-2 Select Documentation.

1-3 User menu → Master data → Info record → Create.

Enter the vendor, material and purchasing organization on the initial screen. Be sure to leave the plant field blank.

From the Purch. Org data 1 screen, choose Conditions and enter the pricing conditions. Choose scales on the conditions screen to enter the scales.

1-3-1

Condition Condition type

Gross price PB00

Discount % on net RA00

Freight (value) FRB1 or 2

1-3-2 Select Favorites → Add.



1-4 User menu → Conditions → Discounts/surcharges → By vendor.

Enter the vendor and purchasing organization, then choose Execute.

On the next screen, select the purchasing organization and choose Create.

Choose Scales and enter the scale.

1-4-1 Choose Favorites → Add.

1-5 Menu → SAP Standard menu → Logistics → Materials Management → Purchasing → Purchase order → Create → Vendor/supplying plant known.

1-5-1 No, the order price is adopted from your cross-plant info record.

1-5-2 Select the appropriate line item in the Item overview screen area and then select the Conditions tab in the Item details screen area.

Item 10 Item 20

Gross price (per 1 pc) 9.50 UNI 9.00 UNI

Discount % on net 1% 2%

Vendor discount 3% 4%

Net price (per 1 pc) 9.12 UNI 8.46 UNI

Freight surcharge 50.00 UNI 50.00 UNI

Cash discount 3% 3%

Actual price (per 1 pc) 9.26 UNI 8.30 UNI

1-5-3 Favorites → Add



1-6 →SAP standard menu → Tools → AcceleratedSAP → Customizing → Edit project → SAP reference IMG.

Materials Management → Purchasing → Conditions → Define price determination process → Define condition types → Define condition types.

Look at the detail screen for each of the condition types.

Condition type

Access sequence

Condition class

Calculation type

Condition category

Plus/ sign

PB00 0002 B C H _

RA00 _ A A _ X

RB00 _ A B _ X

RC00 _ A C _ X

RL01 0006 A A _ X

FRB1 _ A B B

SKTO _ A A E _

Condition class: A = Discount or surcharge B = Prices Calculation type: A = Percentage B = Fixed amount C = Quantity-dependent Condition category: B = Delivery costs E = Cash discount H = Base price Plus/Minus: X = Negative, A = Positive, Blank(_) = positive and negative

1-7 Favorites → Master data → Info record → Create.

1-7-1

• Gross price PB00

• Discount % on gross RA01

• Discount/quantity RC00

• Discount (value) RB00

• Discount % on net RA00

*1-8 SAP Standard menu → Tools → AcceleratedSAP → Customizing → Edit project → SAP reference IMG.



Materials Management → Purchasing → Conditions → Define price determination process → Define calculation schema.

Select RM0000, then choose Control.

Condition type Step Counter

RB00 10 1

RC00 10 2

RA00 10 3

RA01 10 4

HB01 10 10

RL01 10 11

RGR0 10 13

*1-9 Favorites → Purchasing → Purchase order → Create → Vendor/supplying plant known.

1-9-1 Since all discount condition types in the calculation schema are assigned to the same step, their sequence in the purchase order is determined by the manual entry in the info record.



Solutions

Unit: Price Determination

Topic: Customizing Settings

2-1 SAP standard menu → Tools → AcceleratedSAP → Customizing → Edit project. → SAP Reference IMG → Materials management → Purchasing → Conditions → Define price determination process → Define condition types → Define condition types.

2-2 SAP standard menu → Tools → AcceleratedSAP → Customizing → Edit project → SAP Reference IMG → Materials management → Purchasing → Conditions → Define price determination process.

Select IMG activity documentation on the left-hand side of the Define calculation schema node.

2-3 SAP standard menu → Tools → AcceleratedSAP → Customizing → Edit project → SAP Reference IMG → Materials management → Purchasing → Conditions → Define price determination process → Define calculation schema.

Choose Copy all when asked.

2-4 SAP standard menu → Tools → AcceleratedSAP → Customizing → Edit project → SAP Reference IMG → Materials management → Purchasing → Conditions → Define price determination process → Define calculation schema.

Choose Copy all when asked.

2-4-1 Select the calculation schema, then choose Control.

2-5 SAP standard menu → Tools → AcceleratedSAP → Customizing → Edit project. → SAP Reference IMG → Materials management → Purchasing → Conditions → Define price determination process → Define condition types → Define condition types.

Go into the detail screen and change the entry in the PricingProc field.

2-6 SAP standard menu → Tools → AcceleratedSAP → Customizing → Edit project. → SAP Reference IMG → Materials management → Purchasing → Conditions → Define price determination process → Define schema group→ Schema Groups: Vendor.



2-7 SAP standard menu → Tools → AcceleratedSAP → Customizing → Edit project. → SAP Reference IMG → Materials management → Purchasing → Conditions → Define price determination process → Define schema determination → Determine Calculation Schema.

Leave Schema gp. POrg blank. Enter only your vendor schema group and your calculation schema.

2-8 User menu → Vendor → Purchasing → Change (current).

Select purchasing data.

2-8-1 Favorites → Add.



SAP AG 1999

Inventory Management

l Settings for Goods Movements

l Definition of New Movement Typesl Dynamic Availability Check

l Messages in Inventory Management

Contents:



SAP AG 1999

Inventory Management: Unit Objectives

At the conclusion of this course, you will be able to:

l Create number ranges for material documentsand assign transactions

l Modify the field selection and screen layout forgoods movements

l List the most important characteristics ofmovement types

l Define a new movement type and configureaccount determination for movement types thatuse account grouping

l Configure the dynamic availability check forreservations

l Specify the message determination details



SAP AG 1999

Inventory Management: Business Scenario

l You have been asked to create a new movementtype for goods issues to cost centers.

l Your company’s aim is to use this movement typeto separate expenses between different G/Laccounts according to certain criteria.

l You want to configure the dynamic availabilitycheck for these new movement types to informusers of possible unavailability.

l You have been asked to provide an overview ofthe configuration of output determination inInventory Management.



SAP AG 1999

Accounting documentsAccounting documents

Document type

Number range

Number interval(Dependent on year and company code)

Group 2(Other goods movements,

physical inventory differences)

To year: number interval 22000: 49 000 000 ---

49 999 999

Transaction type 3(WI)

Transaction type 2(WA)

111

222

Number Assignment for Goods Movements

Transaction

Transaction type 1(WE)

Material documentsMaterial documents

To year: number interval 12000: 50 000 000 ---

50 999 999

Group 1(Goods receipt for purchase order,

goods receipt for order, ...)

n You must not change the transaction type assigned to a goods movement.

n Internal number assignment is defined for material documents.

n For Italy, you have the option of defining external or internal number assignment for GR/GI slips.



SAP AG 1999

Field selection for movement type

Field selection rules for G/L account

Field selection for:Field selection for:

ggoods issues, transfer postings, other receiptsoods issues, transfer postings, other receipts

Screen Layout for Movement Types

n The settings made in the Define Screen Layout activity, concerning the field selection for the movement type, apply for goods movements and reservations.

n You configure the field selection for the fields G/L account and Reason for movement using separate activit ies.

n The field selection for the movement type must not conflict with the settings for field selection for the G/L account to be posted to (offsetting entry for inventory posting).

n You define the field selection dependent on the G/L account using the field status group in the G/L account master. You assign the G/L account-dependent field selection to the company code using the field status variant.

n In addition, the R/3 System checks if the field selection for the G/L accounts matches the field selection for the relevant posting key for the transaction.

n In Customizing for Financial Accounting, you can define the field selection for posting keys and for the various field status groups.

n In particular, you should note that you must define a mandatory entry in the G/L account as a mandatory entry for the movement type as well.



SAP AG 1999

Field Sel. for Goods Movements: Special Aspects

Customizing Enter goods movement

Reason for movement:

- Define key

- Define field selection for each movement type

222 On the Details screen, the field “Reason for movement” is:- Mandatory entry- Optional entry- Suppressed

222

Configure manual account assignment for each movement type

111 Account for offsetting entryfor inventory posting is: - Mandatory entry- Optional entry- Suppressed

111

n In the standard system, you can enter the account for the offsetting posting for the inventory posting manually when you enter goods movements. In doing this, you change the account number assignment predefined in account determination. In the Set Manual Account Assignment activity, you define the movement types for which the G/L account is to be available for manual input of the offsetting account for the inventory posting.

n When entering goods movements (such as in the case of a return delivery of material to the vendor), you can specify the reason for performing this movement (such as due to unacceptable quality). The R/3 System saves the reason for the movement in the material document. In Inventory Management, you can use a report to analyze the material documents for which a reason for the movement was specified.

n In Customizing, you can do the following for each movement type:

⌧Define whether the field Reason is mandatory, optional, or suppressed for entry

⌧Store a key for explaining the movement (such as reason for return in the case of a return delivery) and a relevant text. When entering a goods movement, you can only enter reasons that are defined for this movement type.



SAP AG 1999

Field Selection for Initial Screen/Header Screen

The settings apply to all initial screens/header screens (1):

You can have settings applyunder certain conditions,for example: transaction code

Document date

Document header text

Posting date

Bill of lading

Reason for movement

Delivery note number

Material slip

Modifiable fieldsModifiable fields

ü

ü

ü

Input Reqd Disp. Supp. HiLi.

n In the case of modifiable fields, you use indicators to define how the individual fields are displayed on the screen. You have the following options:

� The field is ready for input (standard setting).

� The field requires an entry (mandatory entry).

� The field is displayed only.

� The field is suppressed.

� The field is highlighted.

n These settings can apply to the entire client or you can narrow them down using the influencing fields. This enables you to define the field as a mandatory entry depending on the transaction or the document type.

n (1) When you call this activity, the list of all fields that you can modify appears. The settings made in this list apply to the entire client if there are no restrictions or if the requirements for the conditions are not met.

n (2) You make the settings for influencing fields on a separate screen.



SAP AG 1999

Field Selection for Transaction MIGO

Header and detail fieldsHeader and detail fieldsTable columnsTable columns

The settings apply to all header screen/detail screens, for example:

Date of production

MPN material

Vendor material no.

Reason for movement: key

Reason for movement: text

Returns item

Account assignment ü

ü

ü

Input Reqd Disp. Supp. HiLi.



SAP AG 1999

Movement Types (1)

Level ... dependent on ... ... settings for ...

Movement type

Short texts

Permitted R/3transactions

Help texts

Field selectionbatch search

Movement type

Movement typeSpecial stock indicatorMovement indicatorInward movement indicatorConsumption indicator

Movement type

Movement typeSpecial stock indicatorTransaction

Movement typeSpecial stock indicator

Entry control (print indicator, batch indicator, check expiration date)Update control (automatic LORT, consumption, statistics, physical inventory)

Movement type text(description of the movement)

When may you use the movement type?(Propose movement type despite different movement type indicator?)

Extended text(Text describing the individual movement)

Field selection control, batch search procedure(schema for batch determination)

n The movement type is a central control parameter for goods movements. When you create a new movement type, you reference one of the model movement types. The latter’s control indicator appears as the default value for the new movement type.

n You maintain various views for a movement type on the relevant screens. You define the parameters for the individual views depending on various key terms.

n You choose a value string and a quantity string for the movement type. The value string controls the G/L account determination for transactions covered by the movement type (see also the unit on valuation and account assignment), whereas the quantity string controls the updating of the material master fields.

n You can also maintain the parameters for existing movement types using the function for configuring new movement types. The work area that you specify when you enter this transaction must include all movement types that you want to access during configuration.



SAP AG 1999

... dependent on ... ... settings for ...Level

Update control,WMS movementtypes

Accountgrouping

Revers./follow-onmovement types

Reason formovement

Deactivate QMinspection processing

LIS statisticsgroup

Movement type and indicators forvalue/quantity updates, special stocks, movements,receipts, and consumption

Movement type and indicators forspecial stocks, value/quantity updates,movements, and consumption

Movement type, function code

Movement type,key for reason

Movement type and indicators forspecial stocks, movements,receipts, and consumption

Movement type and indicators forspecial stocks and movements

Entry control(availability check, missing parts processing)Update control(LIFO/FIFO, LVS, QM, value/quantity string)

Account grouping code,Indicator for "Check account assignment"

Reversal movement type,Indicator for "Type of posting"

Description of reason

Movement type for QM inspectionprocessing not active

Statistical update control (LIS)

Movement Types (2)



SAP AG 1999

MaterialindicatorAvailability check

Goods movementChecking rule

Movement type

Message onscreen

Customizing- Definition of checking rules

- Assignment of checking rule to R/3 transaction

CustomizingMessage type(error, warning,information)

Customizing- Stock types

- Inward/outward elements- Take account of replenishment lead time?

Checkavailability

Dynamic Availability Check

n You can activate the dynamic availability check in Customizing for entering reservations and goods movements. The R/3 System then carries out the dynamic check in addition to the routine static availability check.



SAP AG 1999

Message schema ME0001Message schema ME0001

Message types Condition

Message type WE01Message type WE01

Print parameterAccess sequence

Message record exists

yes no

Printerdetermination

Continue with nextmessage type

EnterEntergoods movementgoods movement

- Print indicator

- Movement type- Version

(Loop)

1) Manual input2) Specification in message record

3) Flexible printer determination MessageMessagegeneratedgenerated

Generating Messages in Inventory Management

n Message determination in Inventory Management is similar to the process used in Purchasing.

n You define the printers (logical printer name) that the R/3 System can use to print out documents for goods movements.

n You can choose between three variants for flexible printer determination, which you can define separately for each message type:

� Printer assignment by message type/plant/storage location

� Printer assignment by message type/plant/storage location/user group

� Printer assignment by message type/user

n You can define a separate item print indicator for a return delivery to a vendor and assign it to the movement type for return deliveries.

n For printing out documents relating to goods movements, you can either use the form supplied in the standard system or design one of your own using SAPscript functions.

n There are separate settings for printing labels.



SAP AG 1999

Plant Parameters (1)

l Create storage location data for materials automaticallyl Propose final delivery indicator

l Missing parts check active at GR

l Batch where-used list active/not activel Check for expiration date

l ...

Settings for Goods MovementsSettings for Goods Movements

Allow negative stocks for individual special stocks (vendor consignment, customer consignment, ...)(Condition: negative stocks are allowed at plant level and storage location level)

Settings for negative stocksSettings for negative stocks



SAP AG 1999

Plant Parameters (2)

l Stock typesl Propose alternative units of measure

l Determine batches in the backgroundl Create change documents when changing the count results

l Modifying the book inventory balance

l Reason for physical inventory difference

Settings for the physical inventorySettings for the physical inventory

l Propose “Movement allowed” indicatorl Date specification for setting the “Movement allowed” indicator

l Retention period for reservation items

Settings for reservationsSettings for reservations



SAP AG 1999

Inventory Management: Summary


l List the important settings for InventoryManagement transactions and implement themwith the help of the IMG

l Activate the dynamic availability check forInventory Management transactions

l Create a new movement type



SAP AG 1999

Movement Types (Hints to the exercise)

n 1-2-2 Which field should be used to enter the confirmationnumber is specified in the exercise (in the introductorydescription of the business process).

n 1-2-3 R/3 is an integrated system. Field selection is influenced bya further factor in addition to the settings in InventoryManagement. Which one? What must you do to avoid conflicts?

n 1-2-4 In task 1-2-2, you have set up the Item text field for thepurpose of entering the confirmation number. Now an alternativeis sought here.(The stock of confirmation numbers is constant. New ones arenot continually needed.)

n 1-3 Account grouping code: V##



SAP AG 1999

Message Determination (1) - Hints to the exercise

l To have an internal message sent to a buyer only in thecase of a return delivery (movement type 122), a field mustbe found to which movement type 122 (and only this one)is assigned and which is used as a key field of a conditiontable of the message determination process:

n The item print indicator fulfills this requirement: It is assignedto the movement types and there are condition tables that usethis field as a key.

n Is there an access sequence that uses one of these conditiontables? We should use such an access sequence.

n Assigning the item print indicator to movement type 122 is tobe done once only, just as the definition of the item printindicator (e.g. M) is a once-only process. Both the assignmentand definition of the print indicator are carried out by theinstructor (or the fastest group). This part of task 3-1-3 is thenalready completed.

n To make it possible to send a mail, you must assign programSAPOFFICE_AUFRUF to your new message type.



SAP AG 1999


Item print ind.1 Material doc.2 Return delivery:M Return del. 122

Print version1 individual slip2 indiv.sl.w.insp.t.3 Collective slip

Mvt. type/IPInd.122 - M

Versionper transactionMIGO - 1MBRL - 2

The version assigned to the transaction is used by MIGO transaction. In oldtransactions it is only a suggestion. The user has the option of choosing versions 1 or 3.

-> We must create the following messagerecords for our new message type:•WE / 1 / M•WE / 2 / M•WE / 3 / M

(In practice, corresponding message recordsshould also be created for printing (existing message type).)

l What must be done if our access sequence uses acondition table with the following keys?

n Transaction/event type (e.g. WE)

n Print version (1 individual slip / 2 indiv.slip with inspect.text /3 collective slip)

n Item print indicator (our defined M)



SAP AG 1999


l Attention: The Print indicator must be selected on theinitial or header screen for return deliveries. Otherwise theprint version field is empty. That is to say, the systemwould search for a message record of the key combinationWE/_/M.

11 2

Version:Individual slip with inspection text (version2) was suggested in the old transactionaccordance with Customizing settings butcan be changed by the user.

Version:The enjoy transaction MIGO uses theversion, which is defined with Customizingsettings. There is no way for the user tochange it.

n (1) The Print indicator must be selected on the initial or header screen for return deliveries. Otherwise the print version field is empty. That is to say, the system would search for a message record of the key combination WE/_/M.

n (2) Version: In old transactions the version is suggested in accordance with Customizing settings but can be changed by the user. However the enjoy transaction MIGO uses the version, which is defined with Customizing settings. There is no way for the user to change it.



Exercises

Unit: Inventory Management

Topic: Movement Types


• Check and modify the settings for movement types

• Define a new movement type

Your company requires a new movement type for goods issues, because certain consumption postings are to be registered to different cost elements. In contrast to goods issues to a cost center using movement type 201, a different field selection is also required for the new movement type because manual entry of a consumption account is to be blocked and an explanation for the movement is to be entered in the field Item text. As a member of the project team, you are responsible for implementing this.

1-1 New Movement Type for Goods Issues

1-1-1 Give possible reasons or various examples from your company that could call for a new movement type.

______________________________________________________

______________________________________________________

1-1-2 What options do you have if your company is to use two different accounts (cost elements) for consumption of goods issues to a cost center?

______________________________________________________

______________________________________________________

1-1-3 Define a new movement type, Z##, as a copy of movement type 201. Save your movement type and make the following settings for it.



1-2 Screen Layout/Field Selection

1-2-1 The consumption account number should always be determined through automatic account determination and no manual account assignment may occur. Define a suitable control for manual account assignment for this movement type to block manual entry of a consumption account. How do you proceed?

______________________________________________________

______________________________________________________

1-2-2 Define a suitable field selection for this new movement type for goods issues from your company's own stock so that no one can post goods movements using movement type Z## without providing a reason or explanation for the goods issue. How would you proceed?

When you do this, take into account goods issues from the company’s own stock only.

______________________________________________________

______________________________________________________

______________________________________________________

1-2-3 What other influencing factors for field selection must you use to verify your movement type field selection settings?

______________________________________________________

______________________________________________________

1-3 Account Determination

1-3-1 Use the update control view from the movement type table to determine the value string and the (posting) transactions that this value string defines that is assigned to movement type Z## for withdrawals from the company’s own stock when value and quantity updating are active.

Value string: ___________________________________________

Transaction key: ________________________________________

1-3-2 Consider which influencing factor you can use to assign different consumption accounts for movement types 201 and Z##, although both movement types use the same value string.

______________________________________________________

______________________________________________________



1-3-3 Make all the necessary settings for automatic posting so that the system posts goods issues in plant 1000 with movement type Z## for valuation classes 3000, 7900, and BK## to consumption account 400080. This will require a new account grouping code to be assigned to movement type Z##. Use V## as this account grouping code. It will also be necessary to enter this new entry into the account determination table for GBB. Create this entry for plant 1000 (valuation grouping code 0001) and valuation classes 3000, 7900 and BK##.

______________________________________________________

______________________________________________________

1-3-4 Make all the necessary settings for automatic postings so that the system posts goods issues in plant TR## with movement type Z## for valuation classes 3000, 7900, and BK## to consumption account 400080. It will also be necessary to enter this new entry into the account determination table for GBB. Create this entry for plant TR## (valuation grouping code BM##) and valuation classes 3000, 7900 and BK##.

1-4 Test the New Movement Type

Check that all your settings are correct and complete by doing a test in Inventory Management:

1-4-1 Check the current stock for your material T-T1## in plant 1000.

If no inventory is available, post a goods receipt for one of your purchase orders for material T-T1## in plant 1000, storage location 0001.

1-4-2 Enter a goods issue to cost center 1000 for 10 pieces of your material T-T1## from plant 1000, storage location 0001, with your new movement type Z##. Check the three changes that you made in Customizing:

Is the GL account changeable? _____________________________

Must you enter either item text and/or a reason code? ____________

What GL account (offsetting entry) was debited?________________

1-4-3 For the purposes of comparison, enter another goods issue for 10 pieces of the same material from plant 1000, storage location 0001 with movement type 201.

Is the GL account changeable? _____________________________

Must you enter either item text and/or a reason code? ____________

What GL account (offsetting entry) was debited?________________



Exercises


Topic: Availability Check


• Check the settings for the dynamic availability check

Your company uses manual reservations to record material requirements at an early stage – sometimes with considerable delivery times. You should modify the dynamic availability check for these manual reservations in such a way that the user always receives a message about the availability or non-availability of the materials.

2-1 Activate the Dynamic Availability Check

2-1-1 Is the dynamic availability check active when you create a reservation? If so, which checking rule is assigned to this transaction if required?

______________________________________________________

2-1-2 Which goods issues and receipts does this checking rule take into account for the materials that contain the key for individual requirements as a control indicator for the availability check?

Receipts: _____________________________________________

_____________________________________________

Issues: _____________________________________________

_____________________________________________

2-1-3 Which setting has been made for the replenishment lead-time for this combination of individual requirements and checking rule for reservations? What effect would changing this indicator have?

______________________________________________________

______________________________________________________



2-2 Settings for the Movement Type

2-2-1 When you enter a reservation with movement type 201, the system only sends a warning message in the event of non-availability when reserving material that is not special stock, with value and quantity updating active. Which key is used to control this?

______________________________________________________

______________________________________________________

2-2-2 When you enter a reservation with movement type Z##, the system should always output a message about the availability whether or not it is available. In the event of non-availability, the system is to send a warning message. Which key do you use to control this?

Make this setting for movement type Z##, without special stock, and with quantity and value updating active.

______________________________________________________

______________________________________________________

2-3 Check These Settings:

2-3-1 Create the MRP data for the material master record for T-T1## for plant TR##. To do this, copy the MRP data from plant 1000 to plant TR## (delete the MRP group while copying the MRP 1 view). All other fields can remain unchanged. Is requirements planning defined for this material?

MRP type: ____________________________________

Which indicator is set for the availability check? Write down the replenishment lead time as well.

Availability indicatory: ___________________________________

Total repl lead time: ___________________________________

2-3-2 Display the stock overview and the current stock/requirements list for material T-T1## in plant TR##. Write down the following stock levels (each at plant level).

If there is no warehouse stock, post an initial stock balance of 100 pieces in plant TR##, storage location 0001.

Unrestricted use: _______________________________________

Reserved: _______________________________________



Ordered: _______________________________________

2-3-3 Add reservations for material T-T1## in plant TR## for cost center 1000 using the following information (without saving them).

When you do this, check if a warning message about non-availability or an information message about availability is issued.

If the stock on order for this material in plant TR## is not zero, you must take into account the purchase order quantity and the receipt date.

a) Movement type Z##: Reserve a small quantity that is currently available in unrestricted use stock Use a withdrawal date one week from today.

Does the system issue a message that the material is available?

________________________________________________

b) Movement type Z##: Reserve a large quantity that is not available in unrestricted use stock Use a withdrawal date one week from today.

Does the system issue a warning message that the material is not available in a week’s time?

________________________________________________

c) Movement type Z##: Reserve a large quantity that is not available in unrestricted use stock Use a withdrawal date two months from today.

What message does the system issue?

________________________________________________



Exercises


Topic: Output Determination


• Check and modify message determination in Inventory Management

• Make further settings for message output in Inventory Management

Your company plans to print out accompanying documents for various goods movements. As well as printing the accompanying documents using output determination, the system is to send an internal message to the buyer responsible in the event of a return delivery. As a member of the project team, you are responsible for configuring the output determination function in Inventory Management.

3-1 Message Schema – Output Types

3-1-1 Which schema is assigned for output determination in Inventory Management?

______________________________________________________

3-1-2 Which output types are defined for sending internal employee mail messages?

Are there any restrictions on or requirements for sending these messages?

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

3-1-3 What do you have to do to send an internal message to inform a buyer about a return delivery of goods to a vendor?

______________________________________________________

______________________________________________________



3-1-4 Do you need a separate, new requirement that the system is to check in the event of a return delivery?

______________________________________________________

3-2 Access Sequences and Condition Records

3-2-1 Display the access sequences fo r output determination in Inventory Management. Is there a suitable access sequence that you can assign to the new output type? Give reasons for your answer.

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

3-2-2 How can you make sure that the system only generates a message using the new output type with the movement type for return deliveries?

______________________________________________________

______________________________________________________

______________________________________________________

______________________________________________________

3-2-3 What other data do you need to create before testing this?

______________________________________________________

______________________________________________________



Solutions


Topic: Movement Types

1-1 New Movement Type for Goods Issues

1-1-1 Examples could include the need for different automatic account determination, field selection or analyses of the movement type.

1-1-2 One solution would be to create two different movement types so that a separate account could be determined in automatic account determination. This would require a different account grouping (modifier) for each movement type.

Another approach would be to allow the storeperson to enter the consumption account manually. This can be permitted by allowing changes to the account control.

For control reason, we would recommend copying movement type 201 and configuring the account determination separately for the new movement type using a separate account grouping.

1-1-3 Choose Materials Management → Inventory Management and Physical Inventory → Movement Types → Copy, Change Movement Types, and copy movement type 201 (copy all dependent entries as well).

Select Client

Enter the client number that your class is assigned for this course.

Select movement type 201

Select copy as

Replace 201 with Z##

Select Enter

When prompted, select “Copy All”

Save



1-2 Screen Layout/Field Selection

1-2-1 Choose either: Materials Management → Inventory Management and Physical Inventory → Movement Types → Copy, Change Movement Types

Select Client


Select movement type Z##

Select Details

Set the suppress indicator for Account control

or: Materials Management → Inventory Management and Physical Inventory → Goods Issue / Transfer Postings → Set Manual Account Assignment

Select Z##, and suppress the manual account entry.

1-2-2 You can use the Item text field or Reason for movement field to enter a text explanation or reason code for the movement.

In the first case, you could configure the Item text field as a mandatory field; an explanation could be recorded in this field.

Materials Management → Inventory Management and Physical Inventory → Goods Issue / Transfer Postings → Define screen layout

or

Materials Management → Inventory Management and Physical Inventory → Movement Types → Copy, Change Movement Types

Select Client

Enter the client number that your class is assigned for this course

Select Z##, with blank special stock and select Field Selection

Select Z##, with a blank special stock indicatory

Select Details

Select General data

Change the line item text indicator to req. entry

Save

In the second case you, you could require a Reason for Movement code, and predefine the possible “reasons” (acknowledgement numbers) through configuration.

Materials Management → Inventory Management and Physical Inventory → Movement Types → Record Reason for goods movements

Select control reason



Set this as a required entry for movement type Z##

Select reason for movement and create reason codes and text for movement type Z##.

1-2-3 You must check the field selection settings for the movement type against the field selection settings that depend on the G/L account (offsetting entry = consumption account). This could be done either during the actual movement transaction, or when using the simulation mode during account assignment configuration.In addition, report RM07CUFA can be executed to compare the field selection for a GL account with a movement type.

1-3 Account Determination

1-3-1 Choose Materials Management → Inventory Management and Physical Inventory → Movement Types → Copy, Change Movement Types → Update Control/WM Movement Types

Select Client


Select movement type Z##

Select the Update control/WM movement types view.

Select the entry with a blank special stock indicator, qty and value update active.

Select details

To display the transaction/event keys, select the detail icon next to the value string.

Value string: WA01

Transaction key: BSX, GBB, PRD, (BSX, UMB)

1-3-2 You can use different account groupings to differentiate account determination for consumption accounts (offsetting entry to inventory posting) based on the movement type.

The account grouping for transaction GBB is defined for this purpose.

Movement type: 201 Account grouping: VBR Movement type: Z## Account grouping: V##

1-3-3 First, change the account grouping for movement type Z##.

Materials Management → Valuation and Account Assignment → Account Determination → Account Determination Without Wizard → Define account groupings for movement types

Change the account grouping for your movement type Z## to V##, for the entry with the blank special stock indicator, value and quantity updating, and transaction GBB.



Next, configure automatic postings and add the following entries for transaction GBB:

0001 V## 3000 → 400080 400080 0001 V## 7900 → 400080 400080 0001 V## BK## → 400080 400080





Enter INT

Create the new entries for chart of accounts INT, valuation grouping code 0001 and account group ing V##:

1-3-4 Next, configure the automatic postings for plant TR## and add the following entries for transaction GBB:

BM## V## 3000 → 400080 400080 BM## V## 7900 → 400080 400080 BM## V## BK## → 400080 400080





Enter INT

Create the new entries for chart of accounts INT, valuation grouping code BM## and account grouping V##:

1-4 Test the New Movement Type

1-4-1 Check the current stock of T-T1## in plant 1000.

Logistics → Materials management → Inventory management → Environment → Stock → Stock overview

1-4-2 Enter a goods issue and verify the customizing settings for movement type Z##.

Logistics → Materials management → Inventory management → Goods movement → Goods Issues

You cannot manually enter the account for the offsetting posting.



The fields Item text and/or Reason require an entry.

From the accounting document, the account 400080 is displayed as the offsetting entry.

1-4-3 Enter a goods issue and verify the customizing settings for movement type 201.

Logistics → Materials management → Inventory management → Goods movement → Goods Issues

You can manually change the account for the offsetting entry

The fields Item text and/or Reason do not require an entry.

From the accounting document, the account 400000 is displayed as the offsetting entry.



Solutions


Topic: Availability Check

2-1 Activate the Dynamic Availability Check

2-1-1 Choose Materials Management → Inventory Management and Physical Inventory → Reservation → Set Dynamic Availability Check

Select Transaction code

MB21 is assigned to Checking rule 03

2-1-2 Which receipts and issue transactions are taken into account?

Select Define Checking rule

Select Availability control 02(individual), checking rule 03

Select Details

Receipts: Purchase orders

Issues: Reservations, sales requirements, deliveries

2-1-3 The replenishment lead time is not taken into account. When taking the replenishment lead-time into account, the system assumes that the material can be procured within the RLT that is defined in the material master.

2-2 Settings for the Movement Type

2-2-1 Materials Management → Inventory Management and Physical Inventory → Reservation → Set Dynamic Availability Check

Select Movement type

Select movement type 201

Indicator A for the dynamic availability check has the effect of issuing a warning message only in the case of non-availablity.

2-2-2 Select movement type Z##, without special stock, and with quantity and value updating active.

Assign indicator E to movement type Z##.



2-3 Check These Settings:

2-3-1 Favorites → Material Master → Material → Create (general) → Immediately

Create the MRP 1,2,3 and 4 views for material T-T1##, plant TR##. Copy this data from material T-T1##, plant 1000. Remove the MRP group while copying.

MRP type (MRP 1): PD (Plant 1000)Indicator for availability check (MRP 3): 02

Total repl lead time (MRP 3): 0 days (calendar days)

2-3-2 Stock Overview

Logistics → Materials management → Inventory management → Environment → Stock → Stock overview

Unrestricted use: depending on previous exercises

Reserved: 0

Ordered: 0 (depending on previous exercises)

Stock requirements List:

Logistics → Materials management → Inventory management → Environment → Stock → Stock requirement list

2-3-3 Test the settings for the availability check.

Logistics → Materials management → Inventory management → Reservation → Create

a) Yes, an information message is issued stating that the material will be available.

b) Yes, a warning message is issued since the material is not available.

c) A warning message is issued since the material is not available.



Solutions


Topic: Output Determination

3-1 Message Schema – Output Types

3-1-1 Choose Materials Management → Inventory Management and Physical Inventory → Output Determination → Maintain Output Determination Procedures

Choose Conditions: Procedures

The message schema is ME0001.

3-1-2 Choose Materials Management → Inventory Management and Physical Inventory → Output Determination → Maintain Output Types

The output types that are configured for mail processing are:

MLFH, MLGR (requirement 171), MLMD (requirement 172)

The assignment to a requirement can be displayed from the control folder for the message schema. (see 3-1-1 for menupath)

3-1-3 You require a new message type, for example, RULI, that you need to assign partner role MP (Mail partner) with transmission medium 7 and a processing routine (SAPOFFICE_AUFRUF) to.

The output type must be stored in the schema and you must create at least one condition record. The condition record would include the item print indicator for movement type 122.

You use a separate print item indicator for movement type 122 to control the dependencies for sending this message.

3-1-4 No, because no further query is required, apart from a new print item indicator that is assigned to movement type 122. The movement type alone can be the dependency.



3-2 Access Sequences and Condition Records

3-2-1 Choose Materials Management → Inventory Management and Physical Inventory → Output Determination → Maintain Access Sequences

You can use an existing access sequence (such as 0003) since it contains the print item indicator as one of the keys.

3-2-2 Choose Materials Management → Inventory Management and Physical Inventory → Print Control → Maintain Print Indicator for Goods Receipt Documents

You must use a separate print item indicator for movement type 122 that is not assigned to any other movement type.

3-2-3 Choose Materials Management → Inventory Management and Physical Inventory → Output Determination → Maintain Conditions

You need to create condition records for the new message type.
