Sap Plm280 Sample

8/9/2019 Sap Plm280 Sample

http://slidepdf.com/reader/full/sap-plm280-sample 1/25

PLM280 Resource Related Billing

Date

Training Center

Instructors

Education Website

Participant HandbookCourse Version: 2006 Q2

Course Duration: 1 Day(s)

Material Number: 50078284

An SAP course - use it to learn, reference it for work



Copyright

Copyright © 2006 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or f or any purpose without

the express permission of SAP AG. Additionally this publication and its contents are provided solely

for your use, this publication and its contents may not be rented, transferred or sold without the express

permission of SAP AG. The information contained herein may be changed without prior no tice.

Some software products marketed by SAP AG and its distributors contain proprietary software

components of other software vendors.

Trademarks

• Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are

registered trademarks of Microsoft Corporation.

• IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®,

AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation.

• ORACLE® is a registered trademark of ORACLE Corporation.

• INFORMIX®-OnLine for SAP and INFORMIX® Dynamic ServerTM are registered trademarksof Informix Software Incorporated.

• UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.

• Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®,

VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of

Citrix Systems, Inc.

• HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide

Web Consortium, Massachusetts Institute of Technology.

• JAVA® is a registered trademark of Sun Microsystems, Inc.

• JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for

technology invented and implemented by Netscape.

• SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP

EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all

over the world. All other products mentioned are trademarks or registered trademarks of their

respective companies.

Disclaimer

THESE MATERIALS ARE PROVIDED BY SAP ON AN "AS IS" BASIS, AND SAP EXPRESSLY

DISCLAIMS ANY AND ALL WARRANTIES, EXPRESS OR APPLIED, INCLUDING WITHOUT

LIMITATION WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR

PURPOSE, WITH RESPECT TO THESE MATERIALS AND THE SERVICE, INFORMATION, TEXT,

GRAPHICS, LINKS, OR ANY OTHER MATERIALS AND PRODUCTS CONTAINED HEREIN. IN

NO EVENT SHALL SAP BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL,

CONSEQUENTIAL, OR PUNITIVE DAMAGES OF ANY KIND WHATSOEVER, INCLUDING

WITHOUT LIMITATION LOST REVENUES OR LOST PROFITS, WHICH MAY RESULT FROM

THE USE OF THESE MATERIALS OR INCLUDED SOFTWARE COMPONENTS.



About This Handbook

This handbook is intended to complement the instructor-led presentation of this

course, and serve as a source of reference. It is not suitable for self-study.

Typographic Conventions

American English is the standard used in this handbook. The following typographic

conventions are also used.

Type Style Description

Example text Words or characters that appear on the screen. Theseinclude field names, screen titles, pushbuttons as well as

menu names, paths, and options.

Also used for cross-references to other documentation

both internal (in this documentation) and external (in

other locations, such as SAPNet).

Example text Emphasized words or phrases in body text, titles of

graphics, and tables

EXAMPLE TEXT Names of elements in the system. These include report

names, program names, transaction codes, table names,

and individual key words of a programming language,when surrounded by body text, for example SELECT

and INCLUDE.

Example text Screen output. This includes file and directory names

and their paths, messages, names of variables and

parameters, and passages of the source text of a program.

Example text Exact user entry. These are words and characters that

you enter in the system exactly as they appear in the

documentation.

<Example text> Variable user entry. Pointed brackets indicate that youreplace these words and characters with appropriate

entries.

2006/Q2 © 2006 SAP AG. All rights reserved. iii



About This Handbook

Icons in Body Text

The following icons are used in this handbook.

Icon Meaning

For more information, tips, or background

Note or further explanation of previous point

Exception or caution

Procedures

Indicates that the item is displayed in the instructor’s

presentation.

iv © 2006 SAP AG. All rights reserved. 2006/Q2



Contents

Course Overview .... ...... ...... ...... ....... ...... ...... ...... ....... ...... ...... ....... ..... ix

Course Goals................................................................................. ix

Course Objectives ....... ....... ....... ....... ...... ....... ...... ....... ....... ...... ....... . ix

Unit 1: Introduction .. ...... ...... ...... ....... ...... ...... ....... ...... ...... ...... ....... ..... 1

Introduction.................................................................................... 2

Unit 2: Project Structures .................................................................. 21

Work Breakdown Structure................................................................ 22 Activities and Networks . . . . . . . . . .. . . . . . . .. . .. . . . . . . .. . .. . . . . . . .. . .. . . . . . . .. . .. . . . . . . .. . .. . . 38

Milestones, Documents, and Tools....................................................... 52

Unit 3: Reporting ...... ...... ...... ....... ...... ...... ...... ....... ...... ...... ....... ...... .. 67

Reporting .................................................................................... 68

Unit 4: Planning............................................................................... 93

Date Planning .......... ....... ...... ....... ...... ....... ...... ....... ...... ....... ...... .... 95

Resource Planning ....... ...... ....... ....... ...... ....... ...... ....... ....... ...... ...... 108

Material Planning ...... ....... ...... ....... ...... ....... ....... ...... ....... ...... ....... .. 120

Cost and Revenue Planning ... ... ... .... ... ... .... ... ... .... .... ... ... .... ... ... .... .... 130

Unit 5: Budget................................................................................159

Budget....................................................................................... 160

Unit 6: Execution ......... ...... ...... ....... ...... ...... ....... ...... ...... ...... ....... .... 175

Actual Dates and Confirmations . . . . . . . .. . . . . . . . . . .. . . . . . . . . . .. . . . . . . .. . .. . . . . . . .. . .. . . . . 177

Assigning Documents, Procurement Processes, and Claim Management . . . . . . . . 193

Milestone Billing and PS Cash Management ... .. .. .. .. ... .. .. .. ... .. .. .. .. ... .. .. ... . 211

Unit 7: Period-End Closing................................................................223

Period-End Closing and Settlement..................................................... 224

2006/Q2 © 2006 SAP AG. All rights reserved. v

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-



Contents

Appendix 1: cProjects ....... ...... ...... ...... ....... ...... ...... ...... ....... ...... .... 247

Appendix 2: SAP xApp Resource and Portfolio Management .. .. .. .. .. .. .. .. .251

Appendix 3: Versions ...... ...... ...... ...... ....... ...... ...... ...... ....... ...... ...... 255

Appendix 4: Subnetworks ...... ...... ...... ....... ...... ...... ....... ...... ...... ...... 257

Appendix 5: Network Configuration ... ... .... ... ... ... ... ... ... .... ... ... ... ... ... ... 259

Appendix 6: Using Milestones ... ... ... ... .... ... ... ... ... ... .... ... ... ... ... ... ... ... .261

Appendix 7: Documents@web ... ... .... .... ... ... ... ... ... .... ... ... ... ... ... ... ... ..263

Appendix 8: Project Portals ... ... .... ... .... ... ... ... ... ... .... ... ... ... ... ... ... ... ... 265

Appendix 9: Progress Analysis ... .... ... ... ... ... ... ... .... ... ... ... ... ... ... ... .... .269

Appendix 10: Cross-Project Evaluations .. .. .. .. ... .. ... .. .. .. .. .. .. .. .. .. .. ... .. .. 273

Appendix 11: Evaluations with SAP Business Information Warehouse ... . .279

Appendix 12: Scheduling Scenarios ... ... ... ... ... .... ... ... ... ... ... .... ... ... ... ..281

Appendix 13: Service ....... ...... ...... ...... ...... ....... ...... ...... ....... ...... ..... 283

Appendix 14: OCI Interface ... .... ... ... ... ... ... .... ... ... ... ... ... ... .... ... ... ... ... .285

Appendix 15: Integrating iPPE with Project System .. .. .. .. .. .. .. .. .. .. .. .. .. .. .287

Appendix 16: In-House Production Process .. ... .. .. .. .. .. .. .. .. .. ... .. .. .. .. .. .. .289

Appendix 17: Progress Tracking ... ... ... ... ... .... ... ... ... ... ... ... .... ... ... ... ... .291

Appendix 18: Delivery from Projects ... ... ... .... ... ... ... ... ... ... .... ... ... ... ... ..293

Appendix 19: Workflows and Mails in Project System .. .. .. .. .. .. .. .. .. .. .. .. .. .295

Appendix 20: Assembly Processing ... ... ... ... .... ... ... ... ... ... .... ... ... ... ... ..297

Appendix 21: Archiving ...... ...... ....... ...... ....... ...... ...... ....... ...... ...... ..299

Glossary .......................................................................................301

vi © 2006 SAP AG. All rights reserved. 2006/Q2

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-



Contents

Index............................................................................................305

2006/Q2 © 2006 SAP AG. All rights reserved. vii

http://-/?-

http://-/?-



Contents

viii © 2006 SAP AG. All rights reserved. 2006/Q2



Course Overview

SAP Project System supports comprehensive functions for planning, controlling,

and organizing all the activities carried out during the course of a project. It helps

you manage your project structures, dates, costs, and resources throughout the entire

project lifecycle. Course PLM200 provides you with an overview of the functions

in SAP Project System.

Target Audience

This course is intended for the following audiences:

• Project managers

• Project team members

• Consultants

Course Prerequisites

Required Knowledge

• Knowledge of navigating SAP systems

• Basic knowledge of project management

Recommended Knowledge

• Completion of another SAP course, such as AC040 on business processes inManagement Accounting, or SCM500 on external procurement processes

Course Goals

This course will prepare you to:

• Discuss the basic functions of SAP Project System for structuring, planning,

executing, and monitoring projects

Course Objectives

After completing this course, you will be able to:

• Use work breakdown structures, activities, and networks to structure projects

• Discuss aspects of planning dates, resources, materials, costs, and revenues

2006/Q2 © 2006 SAP AG. All rights reserved. ix



Course Overview

• Name the functions used for budgeting

• Explain aspects and processes used for executing projects

• Explain various period-end closing activities in Project Management• Use reporting options for monitoring project data

SAP Software Component Information

The information in this course pertains to the following SAP Software Components

and releases:

x © 2006 SAP AG. All rights reserved. 2006/Q2



Unit 1Introduction

Unit Overview

This unit describes the general characteristics and structures of projects. It introduces

two business examples that will be used throughout the course to explain and

demonstrate the functions of SAP Project System (SAP PS).

Unit Objectives

After completing this unit, you will be able to:

• Explain the characteristics of projects

• Differentiate between the main tasks of SAP PS, cProjects, and SAP xApp

Resource and Portfolio Management (SAP xRPM)

• Name the two structures used in SAP PS

• Describe the project examples used in this course

Unit ContentsLesson: Introduction................................................................... 2

Exercise 1: Preparations (to be carried out by instructor).. .. .. .. .. .. .. .. .. 11

2006/Q2 © 2006 SAP AG. All rights reserved. 1

http://-/?-

http://-/?-

http://-/?-

http://-/?-



Unit 1: Introduction

Lesson: Introduction

Lesson OverviewThis lesson gives you a brief overview of the characteristics and phases typical to a

project, and of the SAP tools that are available specially for program and project

management. It introduces networks and work breakdown structures, which are used

in SAP Project System (SAP PS) for mapping projects. Both of these structures, as

well as basic functions and processes of SAP PS, are described in this course using

two sample projects. The business examples for these two projects are introduced

in this lesson.

Lesson Objectives

After completing this lesson, you will be able to:

• Explain the characteristics of projects

• Differentiate between the main tasks of SAP PS, cProjects, and SAP xApp

Resource and Portfolio Management (SAP xRPM)

• Name the two structures used in SAP PS

• Describe the project examples used in this course

Business Example

Two typical projects are used in this course to illustrate the functions of SAP PS.

“Elevator E-99##” is a typical investment project and is an example of a project that is

mapped using only a work breakdown structure. “Turbine System T-200##” is a sales project and is used to explain activities and networks. More information on these two

example projects is provided in this lesson.

Introduction

Both large-scale projects, such as constructing a factory, and smaller projects, such

as organizing a trade fair, require the numerous activities involved to be planned,

controlled and monitored precisely, systematically, and efficiently. Professional

project management is becoming an increasingly important factor for boosting the

competitive strength of companies, and not just for those whose success is based on

project-oriented business processes. A “project” is an undertaking that a company

carries out, characterized by the uniqueness of its general conditions and constraints.These conditions include the objectives of the project, the time frame for executing

it, as well as financial and capacity-related restrictions. Projects usually involve

cross-departmental and highly complex business processes, the results of which must

2 © 2006 SAP AG. All rights reserved. 2006/Q2




often yield an extremely high level of quality. Projects are often cost-intensive,

time-consuming, and of strategic importance; as a result, they can also represent

a risk for the company.

Figure 1: Project Characteristics

The term “project” is not specific to a particular industry sector and can involve

various aspects such as research and development projects, investment measures,

make-to-order production, and more extensive maintenance tasks. Projects are

normally given an appropriate structure to allow dates, resources, costs, budgets

and payments to be planned, controlled, and monitored transparently. Hierarchies

are often used for evaluating aggregated data, allocating budgets, and defining

responsibilities. Project-specific organizational forms are usually created for projects

that are integrated in an enterprise's business processes. These organizational forms

are in a position central to the user departments involved so that all the tasks that occur

when the project is executed can be properly controlled.

SAP Project System

SAP PS is a project management tool that assists you throughout all the phases of

your project. Through the high level of integration between SAP PS and other SAP

functions, such as Logistics, Accounting, and Human Resources, SAP PS ensures that





the necessary business processes are handled quickly and efficiently. SAP PS provides

structures that allow you to map projects flexibly and with the appropriate structures.

Using suitable tools and reports in SAP PS, you can plan and monitor dates, costs,

revenues, budgets, resources, materials, and so on, for these structures.

SAP PS is a component of both mySAP Enterprise Resource Planning (mySAP ERP)

and mySAP Product Lifecycle Management (mySAP PLM).

In addition to SAP PS, additional SAP functions for achieving efficient program

and project management at a company are provided with Collaboration Projects

(cProjects) and SAP xApp Resource and Portfolio Management (SAP xRPM).

cProjectscan be used independently of SAP PS, but also in combination with SAP PS,

for efficient project management. cProjects is a web-based, flexible, and easy-to-learn

project management tool tailored to suit the requirements of development, consulting,

and IT projects. In addition to the functions offered by cProjects for structuring,

planning, and implementing projects, different integration scenarios such asCollaboration Folders (cFolders) or SAP systems can also be used.

SAP xRPMis used for the strategic management of entire project portfolios. To this

end, data from different project management tools, for example Microsoft Project

(Client and Server), cProjects, or SAP PS can be consolidated with controlling data

from mySAP ERP Financials and monitored uniformly with special dashboards and

SAP Business Information Warehouse analysis functions in an Enterprise Portal. The

merging of data from different project management tools in SAP xRPM facilitates

uniform, system-wide resource planning of all projects.





Figure 2: Program Management and Project Management

The two structures provided by SAP PS for mapping projects are work breakdown

structures and networks. You use a work breakdown structure to organize a project in

the form of a hierarchy, and so map the structure of the project. Networks, on the other

hand, are used to represent the individual project activities together with their temporal

and logical relationships, in other words, the flow of the project. You can map a

project using just one work breakdown structure or one network. However, you can

also illustrate a project using a work breakdown structure and one or more networks in

order to use the characteristics of both structures together. Work breakdown structures

consist of work breakdown structure elements (WBS elements) that are arranged at

various levels to produce a hierarchical model of the project activities to be carried

out. Each individual WBS element can act as a controlling object in which you can

plan and monitor costs, revenues, payments, budgets, and dates. A network represents

the flow of a project. The individual tasks in the project are mapped as activities in a

network. The temporal and logical dependencies between the various activities can

be represented as links, also known as relationships. Activities form the operative

basis for planning and controlling dates, costs, and resources (personnel, machinery,materials). When activities are assigned to WBS elements, the dates and costs defined

in the individual activities are totaled up (aggregated) at the WBS level, and can

be evaluated. Activity funds already assigned are checked against the budgets of

the WBS elements.





Figure 3: Structures

Two example projects explain how you can use the two structures, work breakdown

structure and network, when you are managing projects with SAP PS. The various

functions they support are also described.

Business Examples

The project with the ID E-99## (## stands for the number of the group a course

partici pant belongs to) is an example of an investment or cost project that can be

mapped with just a work breakdown structure, that is, without networks or activities.

You use the work breakdown structure in this business example to plan and monitor

the project for constructing an elevator in your company. Cost-related aspects are

particularly important while the project is being executed.





Figure 4: Investment Project E-99##

The following steps are carried out in this course for project E-99##:

1. Create a suitable work breakdown structure using the Project Builder

2. Plan basic dates manually for WBS elements using the project planning board

3. Plan costs manually for the WBS elements using Easy Cost Planning

4. Budget WBS elements

5. Enter actual dates during the project execution phase

6. Assign various documents for WBS elements using Execution Services for

updating commitment costs and actual costs

7. Calculate overhead costs and carry out settlement to assets under construction

in Asset Accounting using the Schedule Manager

Project Builder, project planning board, Easy Cost Planning, Execution Services, and

Schedule Manager are tools in the SAP system that are used here to perform the

various steps. In addition to these tools, this course introduces you to a range of

reports and information systems that you can use to evaluate the project data during

the various project phases.

Project T-200## is used in this course as an example of a sales project that is mapped

in the SAP system with a work breakdown structure and a network. The starting

point for creating and executing the project in this business example is a customer

inquiry and, later on, a sales order for constructing a turbine system. In addition toControlling-related aspects for developing and constructing the turbine system, it is

also important to consider a number of logistical requirements (on-time material

procur ement, availability of capacity). The network acts as a quantity structure for

planning dates, costs, resources, and material requirements automatically.





Figure 5: Sales Project T-200##





The following steps are carried out in this course for project T-200##:

1. Create a customer inquiry in Sales and Distribution

2. Create a project (work breakdown structure and network) using standard

structures

3. Plan dates using scheduling

4. Plan resources

• Plan capacity requirements

• Distribute work among the workforce

• Plan the external procurement of services

5. Plan materials by transferring bills of material

6. Plan costs using network costing

7. Create sales pricing data

• Create a quotation based on a project cost plan

• Plan revenues for the project

8. Create a sales order with a billing plan in Sales and Distribution

9. Enter confirmations (in particular, using the cross-application time sheet: CATS)

10. Purchase materials and services

11. Document var iances using claims

12. Post revenues using milestone billing

13. Calculate overhead costs, carry out a results analysis and settle the resultsanalysis values to the profitability segment

In this business example too, you will use suitable reports to track planned and actual

data (dates, resources, costs, revenues, and payments) that is written to the network

activities. By assigning the activities to WBS elements, you can aggregate activity

data at work breakdown structure level and evaluate it.

In simplified terms, a project can generally be divided into the following phases:





Figure 6: Phases in a Project

A high degree of precision is required when planning and coordinating large and

complex projects. When planning the flow of a project, you will schedule deadlines

and dates, make resources available, and assign funds. SAP PS gives you the support

you need throughout all phases of the project.





Exercise 1: Preparations (to be carried outby instructor)

Exercise Objectives

After completing this exercise, you will be able to:

• Make the system settings required for the course (instructor only)

Business Example

Original IDES data is used for structuring, planning and executing the example

projects. You also need to implement a number of additional individual settings in the

SAP system.

Task 1: Preparations (to be carried out by instructor)

Check the parameters in the user master data and the settings in the SAP system that

are required for performing the demonstrations and exercises.

1. Check the user master records for the course participants. They should contain

suitable parameters and fixed values.

2. In Customizing for Project System, set the Adjust Basic Dates indicator in the

130000000001 IDES Scheduling Forward profile for WBS scheduling.

3. PS Cash Management must be activated in company code 1000 to ensure that the

payment data is updated. Check this setting in Customizing for Project System.

4. To carry out period-end closing using the Schedule Manager, you have to

maintain a prefix number for the SAP system (transaction OOW4).

Check workflow Customizing using transaction SWU3, and if necessary perform

automatic workflow Customizing.

In the TVARV table, you have to enter suitable values for parameters PS_PERIOD

and PS_YEAR (transaction SM31). Make the appropriate settings in the system.

Continued on next page





Task 2: Language Settings (to be carried out byinstructor; only for courses not held in German)

German is set as the original language for master data in the IDES systems. For

courses held in other languages, the master data short texts need to be switched

to those languages.

Hint: The example shows the texts being converted to English (EN). No

changes need to be made for courses held in German.

1. Set the short texts for standard networks and standard projects to EN using

transaction YILA. Use text pools ZT-TRAIN-PS-01, ZT-TRAIN-PS-02

and ZT-TRAINING-PS-03.

2. Set the language for vendor 1000 to the required language (in our example,

English). Use transaction XK02 to change the vendor data.

3. Set the language for customer 1600 to the required language (in our example,

English). Use transaction XD02 to change the customer data.





Solution 1: Preparations (to be carried outby instructor)

Task 1: Preparations (to be carried out by instructor)

Check the parameters in the user master data and the settings in the SAP system that

are required for performing the demonstrations and exercises.

1. Check the user master records for the course participants. They should contain

suitable parameters and fixed values.

a) Check the parameters for the participants using transaction SU01. The

following parameters should be maintained:

Parameter Value Text

BUK 1000 Company Code

CAC 1000 Controlling Area

PDB 130000000000 Profile for logical

database PSJ

PFL YIDES_130000 Profile for project

information system

WRK 1300 Plant

b) Set suitable fixed values for:

• Decimal places

• Date format

• Time zone

2. In Customizing for Project System, set the Adjust Basic Dates indicator in the

130000000001 IDES Scheduling Forward profile for WBS scheduling.

a) In Customizing for Project System, choose SAP Customizing

Implementation Guide! Project System! Dates! Date Planning in

WBS ! Define Parameters for WBS Scheduling . Then display the details

of the 130000000001 IDES Scheduling Forward profile. Set the Adjust

Basic Dates indicator and save your changes.






3. PS Cash Management must be activated in company code 1000 to ensure that the

payment data is updated. Check this setting in Customizing for Project System.

a) In Customizing for Project System, choose SAP Customizing Implementation Guide! Project System! Payments! Activate Project

Cash Management in Company Code. The following setting is required:

CoCd FMA Actv.

1000 1000 x

4. To carry out period-end closing using the Schedule Manager, you have to

maintain a prefix number for the SAP system (transaction OOW4).

Check workflow Customizing using transaction SWU3, and if necessary perform

automatic workflow Customizing.

In the TVARV table, you have to enter suitable values for parameters PS_PERIOD

and PS_YEAR (transaction SM31). Make the appropriate settings in the system.

a) Call up transaction OOW4. Check whether the table contains the training

system and your client. If necessary, enter a new line with any number you

like (###, for example 865) and your system and client number. Save

the data as a local object.

b) Check the standard settings for the workflow. To do so, call up transaction

SWU3. You may need to perform automatic Customizing.

c) Call up transaction SM31 for maintaining tables. Enter table TVARV on

the selection screen. Call up the screen for maintaining the data. Change

the parameter values in accordance with the following table and save

your changes.

Name Value

PS_PERIOD Current month

PS_YEAR Current year






Task 2: Language Settings (to be carried out byinstructor; only for courses not held in German)

German is set as the original language for master data in the IDES systems. For courses held in other languages, the master data short texts need to be switched

to those languages.

Hint: The example shows the texts being converted to English (EN). No

changes need to be made for courses held in German.

1. Set the short texts for standard networks and standard projects to EN using

transaction YILA. Use text pools ZT-TRAIN-PS-01, ZT-TRAIN-PS-02

and ZT-TRAINING-PS-03.

a) Call up transaction YILA. If necessary, confirm the dialog box with the

message on the language switch. Enter the following data in the lower

section of the screen (Selection: Textpool ):

Field Value

Target Language EN

Text Pool ZT-TRAIN-PS-01

Select Update Short Texts.

Update the texts in text pools ZT-TRAIN-PS-02 and ZT-TRAINING-PS-03

in the same way.

2. Set the language for vendor 1000 to the required language (in our example,

English). Use transaction XK02 to change the vendor data.

a) Call up transaction XK02. Enter the following data on the initial screen:

Field Value

Vendor 1000

Company Code 1000

Purchasing Organization 1000

Address x

Confirm your entries with Enter . In the Language field, choose English

and save your changes.


2006/Q2 © 2006 SAP AG All rights reserved 15

Sap Plm280 Sample

Documents

Transcript of Sap Plm280 Sample