TSCM34

SAP System

Course Version:

SAP R/3 EnterpriseSAP APO 3.1

Author:

See section SAP contacts

May 2003

TCASE1 Case Study for Solution Consultants Basic Training

TFIN14 Managerial & Financial Acc.THR14 Management / AdministrationTSCM24 PlanningTSCM34 ManufacturingTSCM54 ProcurementTSCM64 Order Fulfillment

Instructor Guide

Key to icons in the Guide:

Timing

Next Slide (s)

Instructor

Demonstration

Exercises

Activity

Summary

Objectives

Business Scenario

Hints and Tips

Warning or Caution

Internal Note

SAP AG TCASE1 - Case Study Bike International

Course Schedule

SAP Contacts.................................................................................................51 EPFs............................................................................................................................. 5

2 Subsidiaries.................................................................................................................. 5

Revisions to Previous Instructor Guide.......................................................6

Course Details................................................................................................71 Duration........................................................................................................................ 7

2 Course Materials and other Materials...........................................................................7

3 Country-Specific Units..................................................................................................8

4 Organizational Preparation..........................................................................................8

4.1 Organizational Aspects...........................................................................................8

4.2 Creating the Case Study Groups.............................................................................8

Course Instructor Profiles...........................................................................101 Level of Knowledge Required.....................................................................................10

2 Courses Recommended as Preparation.....................................................................10

3 Online Help Recommended as Preparation................................................................10

4 Hints on Preparing This Course..................................................................................10

Training System...........................................................................................111 Data Required.............................................................................................................11

1.1 Project clients 1## for participants......................................................................11

1.2 Mail client 400 for participants (getting help)......................................................11

1.3 Solution client 100 – only for instructors.............................................................112 User ID and Passwords for Course Participants.........................................................14

2.1 Logging onto a client for the first time – only trainers.........................................14

2.2 Existing Users in Case Study Project Clients 1##................................................15

2.3 Creating Users in Mail Client 400........................................................................15

2.4 Users in solution client 100 – only for trainers.....................................................173 Preparation in the System...........................................................................................17

4 Example ABAPs.........................................................................................................17

5 CATTs......................................................................................................................... 17

6 Technical Hints...........................................................................................................17

Goals and Objectives...................................................................................18

Course Structure and Flow.........................................................................181 General information....................................................................................................18

2 Case Study Structure..................................................................................................19

3 Case Study Overview (Introduction session: Preface and Unit 1)...............................19

4 Phase 1 – Team organization and Organizational Structure (Unit 2)..........................20

5 Phase 2 – System(s) set up / Implement Business Processes (Units 3, 4, 5).............21

6 Presentation of some prototype processes (Unit 5)....................................................22

Course Schedule..........................................................................................23

Unit: Organizational Structures..................................................................25

May 2003 Page 2/127


Course Schedule1 Contents of Unit..........................................................................................................25

2 Putting the Unit in Context..........................................................................................25

3 Settings in SAP systems.............................................................................................25

3.1 Financials (Financial Accounting and Controlling)..............................................26

3.2 Logistics – General...............................................................................................27

3.3 Sales and Distribution...........................................................................................27

3.4 Materials Management.........................................................................................28

3.5 Logistics Execution...............................................................................................29

3.6 Human Resources Management...........................................................................30

Unit: TFIN14 Managerial & Financial Accounting.....................................321 Contents of Unit..........................................................................................................32


2.1 Prototype process 1: Integration FIN- and PR-, PL-/MF-team (maybe OF)........34

2.2 Prototype process 2: Integration FIN- and MF-team............................................34

2.3 Prototype process 3: Integration HR- and FIN-team............................................34

2.4 Prototype process 4: Planning and Reporting in CO............................................34

2.5 Prototype process 5: Integration PR- and FIN-team.............................................34

2.6 Prototype process 6: Integration OF-- and FIN-team...........................................34

2.7 Prototype process 7: Integration PR-- and FIN-team (maybe OF)......................34


2.9 Prototype process 9: Integration PR-- and FIN-team...........................................35

2.10 Prototype process 10: Closing in FI/CO (FIN).....................................................35

2.11 Prototype process 12: Integration OF-, PR-, FIN-team........................................353 R/3 settings................................................................................................................. 36

3.1 FI:..........................................................................................................................36

3.2 CO:........................................................................................................................42

Unit: TSCM64 Order Fulfillment..................................................................491 Contents of Unit..........................................................................................................49


2.1 Prototype process 1: Integration OF - and PR-, FIN-, PL-/MF-teams...............50


2.3 Prototype process 7: Integration OF – and PR-, FIN-teams.................................50


2.5 Prototype process 12: Integration OF – and PR-, FIN-teams...............................513 Settings in R/3 System (SCM-OF General Customizing)............................................52

4 Problem log.................................................................................................................54

Unit: TSCM54 Procurement.........................................................................561 Contents of Unit..........................................................................................................56


2.1 Prototype process 1: Integration with FIN- and PL-/MF-team.............................57

2.2 Prototype process 5: Integration with FIN-team...................................................57

2.3 Prototype process 7: Integration with FIN-team (maybe OF)..............................58

2.4 Prototype process 9: Integration with FIN-team...................................................58

May 2003 Page 3/127


Course Schedule2.5 Prototype process 12: Integration with SD- and FIN-team..................................59

3 Settings in R/3 System................................................................................................60

4 Comments..................................................................................................................69

5 Problem Log...............................................................................................................70

Unit: Setting up the Core Interface.............................................................721 Contents of Unit..........................................................................................................72


3 Settings in R/3 and APO.............................................................................................74

Unit: TSCM24 Planning................................................................................841 Contents of Unit..........................................................................................................84


2.1 Prototype process 1: Integration with PR and FIN...............................................853 Settings in APO..........................................................................................................85

Unit: TSCM34 Manufacturing......................................................................891 Contents of Unit..........................................................................................................89


2.1 Prototype process 1: Integration with PR and FIN...............................................92

2.2 Prototype process 2: Integration with FIN............................................................933 Settings in R/3 and APO.............................................................................................94

3.1 Manufacturing in R/3............................................................................................94

3.2 Conversion of planned orders in APO and manufacturing in R/3.....................101

Unit: THR14 Management / Administration.............................................1111 Contents of Unit........................................................................................................111

2 Putting the Unit in Context........................................................................................111

2.1 Business Process 3: Payroll Accounting for Employees in Administration with Transfer to FI and CO (HR, FI/CO)...............................................................................111

2.2 Business Process 11: Legacy data transfer and Create SAP Query to show Organizational Assignment, Salary and Work Schedule of all employees....................112

3 Settings in R/3 System..............................................................................................112

4 HR - Case Study: common problems.......................................................................125

May 2003 Page 4/127


Course Schedule

SAP Contacts

1 EPFs

Generals: Gehlfuss, Joerg (author)

TFIN14 - Financials (FIN): Walter, Florian /Wittler, Andreas (Germany/authors),Wayne Skitt (US)

TSCM64 - Order Fulfillment (OF): Boulay, Nathalie (Germany/author)Kristine Butkus (US)

TSCM54 - Procurement (PR): Gehlfuss, Joerg (Germany/author),Mary Bazemore (US)

TSCM24 - Planning (PL): Wiedemann, Marc-Oliver (Germany/author),Hilmer Hintz (US)

TSCM34 - Manufacturing (MF): Wiedemann, Marc-Oliver (Germany/author),Hilmer Hintz (US)

THR14 - Human Resources (HR): Koenig, Karin (Germany/author),Donna Shrout (US)

2 Subsidiaries

Revisions to Previous Instructor Guide

The Case Study now is offered as separate 1-week courses. However, again it is the continuation and the end of the basic training for consultants. It runs from Monday to Thursday. As before, at Friday they have the possibility to take the certification test.

One of the big changes between 4.6B and 4.6C is, that in addition to the R/3 system we now have a related APO system, which is used by the SCM-Planning teams (PL) and the SCM-Manufacturing teams (MF). But not every Case Study needs to have PL and MF. Without both teams we just have the R/3 system as before.

However, the R/3 knowledge from the previous courses (Basics Part I and Part II) is smaller now (in comparison with 4.6B), because the content of the courses is reduced now (in 4.6B we had a hard time pressure). And no more we have two different courses/teams for FI on one hand and CO on the other one. There is a FI/CO-course now (Managerial & Financial Accounting). Therefore the FIN-Teams, which are concerning FI and CO, have a very smaller FI-knowledge and a very smaller CO-knowledge comparing with the 4.6B-FI-teams and 4.6B-CO-teams.

For that reasons nearly all prototype processes are changed and of course the related detailed descriptions in the ASAP Business Blueprints are changed.

There is just one version of materials, which is the former “ASAP version”, that means: Master data and business process are described within ASAP Business Blueprint documents. However, normally there is no real use of ASAP tools (except of using the existing ASAP Blueprints). There is not enough time and not enough detail knowledge for a real usage of ASAP. And maybe you have not installed the ASAP tool at participants’ PCs. Anyway, in any case we use the ASAP Business Blueprints.

May 2003 Page 5/127


Course ScheduleBy the way: The participants’ materials can be found in Knowledge Warehouse. There is a participant’s manual with nearly all materials. And there is - separately - the Bike Inter-national Organizational structure decision document (solution). It is to deliver separately and – as before - the instructors will handout this decision after the organizational structures meetings.

In addition, one of the units from the participant’s handbook (unit 1 – course overview) can be found as a template in SAPNet. You may use it, to enter your own specific data… Furthermore, use it for the introduction session.

And there is the FIN-organizational structure decision (solution) separately in SAPNet. This enables you to agree with the FIN-team earlier. Doing so, the FIN teams may start earlier to create company codes, etc.

The participants user data in the case study clients 1## are existing (see details below). However, (as before) in the mail client (for getting help) you have to create the users for the participants as well as the user HELP (for the instructors). This mail client is moved to client 400 now!

Last but not least the instructors guide itself got another structures than before.

Course Details

1 Duration

5 days (incl. Certification)

2 Course Materials and other Materials

Participants’ manual (KW structure TCASE1 – Part 1) with the following documents/units:

Preface

1. Course overview*

2. Introduction – The Bike International Company (used for phase 1)

3. ASAP Business Blueprint Master Data (used for phase 2)

4. ASAP Business Blueprint Business Processes (used for phase 2)

5. Prototype Business processes (used for phase 2)

The participants’ document

Bike International – Decision to Organizational structure (solution)This document is delivered separately. At the end of the Kick-off/Organizational structure meeting the instructors will give it to the students. It’s KW structure TCASE1 – Part 2.**

Note: The course materials - especially ASAP Blueprints - fallow the ASAP structure. They leave some freedom to the participants and therefore they are not formulated in a straight style as in the exercises of the regular courses.

May 2003 Page 6/127


Course Schedule

*Note: In addition you should download from SAPNet the template containing the unit 1 (Course overview) to enter your individual (specific) data of your course run, such as

the names of the managers / instructors,

the mySAP solutions that are not part of the case study (the module(s) or solution(s), you have no team for)

Country 1 (country of your case study run) and maybe a suggestion for country 2.

the beginning time of the Kick-off/Organizational structure meetings

the time table

maybe additional information (for example special things for your training center)

For details: See Course structure and flow.

We suggest, to use this individual Powerpoint version for the introduction session. Furthermore you should handout at least one printed document per team (maybe print 2 slides per page).

**Note: To enable the FIN team to start creating company codes before the organizational structure meeting, you may agree with them about the FIN structure before this meeting. Use the separate FIN decision (solution), which you may download from SAPNet.

Please inform your participants about a necessary CORRECTION in UNIT 5 of participants manual (page 5-7):

In process 7, part b) it must be read: "Carry out delivery accordingly from STAR CITY to MOON VILLAGE. Make sure during preparation that sufficient stock is available for delivery."

(in German documents: "Liefern Sie dementsprechend von GROSSSTADT nach KLEINDORF. Stellen Sie bei der Vorbereitung sicher, dass die Lagerbestände ausreichen.")

When the tax code V4 doesn`t work for SuperBike- so look at Note 29401 /FS215.

3 Country-Specific Units

None, but use the template for unit 1 (course overview) to enter your individual data. Use it for the introduction session (see course materials and other materials).

Check for HR, if there is a MOLGA for your country (where the case study runs) or if you should use the international MOLGA.

4 Organizational Preparation

4.1 Organizational AspectsCase study groups will need to be defined. The number of groups to be defined will be dependent on the total number of participants per track. At least 2 members from each track should be included in the group.

Ideally one training room per case study group must be reserved. Every case study group needs a sufficient number of workstations. Besides the R/3 system – and in case of SCM-

May 2003 Page 7/127


Course SchedulePlanning or SCM-Manufacturing the APO system - ensure access to the online documentation. They also need software to do their project work, for example MS office.

The participants materials consist of: Participants Manual (KW structure TCASE1 – Part 1) and The document Bike International – Decision to Organizational structure (solution) –

which is to be distributed by the trainers during the phase 1 meetings (KW structure TCASE1 – Part 2).

In addition, there is a course overview template and a separate FIN organization structure decision (solution) in SAPNet. You may download both files and use

the course overview template to enter your specific data and to use it for the introduction session (instead of unit 1 – course overview). Furthermore you should print it (maybe 2 slides per page) and deliver it at least once per team

the FIN structure to have an accelerated start for the FIN teams, which have to do some pre-work (especially to create company codes).

See Course Materials and other materials.

Manage the Online-Evaluation earlier then usually. It should be at the morning of day 4 latest (Thursday morning)! Afterwards, nobody will there to do it!

4.2 Creating the Case Study Groups

During the previous courses of the academy the trainer from each track should select the strongest students, which will continue this running course sequence, and assign these students to different case study groups. The other participants can then be assigned to the groups. This will ensure that each group contains a mix of stronger and weaker participants. Furthermore the trainer should have attention to different types of personal behavior. It is recommended to split students who worked together at one pc during the Academy.

Ensure, that every team includes at least some students from the running course sequence.

May 2003 Page 8/127


Course Schedule

Course Instructor Profiles

1 Level of Knowledge Required

The instructors should have an intensive knowledge of their area (related R/3 module and in the case of SCM-Planning/Manufacturing also related APO knowledge). Furthermore they should have some project experience. Knowledge of the integration aspects of the case study processes is helpful. For details see “Content of unit” sections.

We strongly recommend, that not all of the instructors of your instructors’ team are doing this job the first time. Some of them should have done it before.

The instructors should know the content/subjects of the previous SAP solution academy courses (Basic courses for consultants Part I and Part II) for the relevant area.

A quite nice talent as actor is useful to play the role of a manager at customer side.

For the FIN instructor basic FI/CO knowledge (enterprise structure and master data) should be sufficient for days 1-2. Beginning from day 2 more detailed knowledge in both application modules is essential.

2 Courses Recommended as Preparation

Practical consultant experience!

If exist in your area: Customizing course(s)

3 Online Help Recommended as Preparation

Topics, which are relevant for the organizational structure as well as for the prototype processes and other processes, which are described in the ASAP documents.

4 Hints on Preparing This Course

Read the Participants’ materials (the manual and the separate Bike International Organ-izational structure decision (solution) document). Be familiar with the prototype processes and the related details, given in the other units of the participants’ manual.

Use this guide and the client 100 of SAP training systems to see a possible solution. To enter client 100, use the special user TRAINING and the password of the month (the password of the month is given by your training administration). Maybe create your own user in client 100.

Client 100 is only used by the instructors. It should never used by participants!

Maybe (especially, if you are a case study trainer for the first time) ask your training administrator for the names of colleagues, who have conducted a case study before (for your area of course). Ask your colleagues for problems that arrived in previous case studies.

It is useful to wear comfortably shoes. You have to walk through different rooms to support your participants.

May 2003 Page 9/127


Course Schedule

Training System

1 Data Required

1.1 Project clients 1## for participants

The participants are working in case study “project” clients 1## (clients 101, 102, …up to 110 in maximum) – one client for every “consultant team”, consisting of members of all needed areas. For example, if you have 6 teams you need 6 clients: 101, …, 106.

These clients are copies from client 000. They are (nearly) “empty”, but as in every “new system” there is some starting data (for example company codes for various countries and plant 0001 – as sources to copy to own company codes, plants etc.).

Except of these “original delivered” data and except of the user records (see next section), no other data is needed. The system is to be set up and “filled” by the participants.

Just client-independent settings exist. Participants must not change client-independent setting!

1.2 Mail client 400 for participants (getting help)

There is a special client 400, which can be set up to simulate an On-line Service Support environment via SAP office mail. If used in this way, the participants can send a mail to a „Hotline“. This „Hotline“ is your team of teachers. The client plays the role of the on-line service support system, but only by using SAP office mail system.

Users have to be created (see below) and the „hotline“ inbox has to be checked regularly during the case study.

You explain this opportunity and how to send and read mails in the course overview unit.

The participants may use this client also to see and check a “working” client.

1.3 Solution client 100 – only for instructors

The client 100 has to be used only by the trainers. It contains the settings and a represent selection of master data for the prototype processes (maintained just in English).

For organizational structure see Organizational structure unit. For settings see the unit for your specific course (for example TSCM54 Procurement).

The following data exist in client 100 and may used by the instructors to test the processes:

What Description (Key) Comments

Customer (DEBI) Bargain Bike Ltd. (1) Sales: 1000/02/00 CC 1000Sales: 2000/02/00 CC 2000

Customer (CPD) One-time customers (100000 or 100002)

Sales: 1000/02/00 Comp.code: 1000

Vendor (KRED) Bumasoft CC 1000 / Porg 1000 (raw materials, …)

Vendor (KRED) Mr. Clean Co. CC 1000 / Porg 1000 (cleaning)

May 2003 Page 10/127


Course Schedule


Vendor (KRED) Top Design Corp. Cc 1000 / Porg 1000 (subcontracting and external services for fairy trade)Cc 2000 / Porg 2000 (ext. services for fairy trade)

Porg 1 (maybe for a central contract for services for fairy trade)

Vendor (CPD) CPD Germany (EUR) (CPD-DE-EUR)

CC 1000 / Porg 1000 (sort key 022, ref. CPDL)

Vendor (CPD) CPD Britain GBP(CPD-GB-GBP)

CC 2000 / Porg 2000 (sort key 022, ref. CPDL)

Material (FERT)

[R/3]

Men's 26" Mountain Bike – Black (100001)

Basic Data1100/1101/100: Storage/WM/Accounting1200/1201/100: Storage/WM/Acc./Purch.

1100/1101: MRP1200/1201: MRP (PD, weekly lot size, 100x, special procurement key for transfer from plant 1100)

1000/02/00: Sales

Material (FERT)

[R/3]

Lady’s 24" Street Bike – Green (100030)

Basic Data1100/1101/100: Storage/WM/Accounting1200/1201/100: Storage/WM/Acc./Purch.

1100/1101: MRP (X0)1100: Work Scheduling: ProdScheduling Profile CS0001

1200/1201: MRP (PD, weekly lot size, 100x, special procurement key for transfer from plant 1100)

Material (HAWA)

[R/3]

Cycle Shorts (500021) Basic Data1100/1101/100: Storage/WM/Acc./Purch.1200/1201/100: Storage/WM/Acc./Purch.

1100/1101: MRP (VB 200, FX 500)1200/1201: MRP (PD, weekly lot-size, 100x, min. 200, spec.proc.key transfer from plant 1100)

Material (HAWA)

[R/3]

Saddle Bag (500020) Basic Data1100/1101/100: Storage/WM/Acc./Purch.1200/1201/100: Storage/WM/Acc./Purch.

1200/1201: MRP (PD, weekly lot-size, 100x, min. 200, spec.proc.key transfer from plant 1100)

Material (HALB)[R/3]

Shift Assemby (300300) Basic Data1100/1102: Storage/Accounting

May 2003 Page 11/127


Course Schedule


Material (HALB)[R/3]

Break System (300200) Basic Data

1100/1101: MRP (X0) 1100: Storage/Accounting

BOM Material 100030 Plant: 1100

BOM: 1

Usage: 3

Routing Material 100030 Group: 50000000 / 1

Plant 1100

Workcenter MTB-ASSM Plant : 1100

Category: 0001

Usage 009

Production Version Material 100030

Plant 1100

Version: 0001

“Bikes Assembly”

Plant: 1100

Routing : 50000000 / 1

BOM : 1

Material (ROH)

[R/3]

Gear Shift XTR RDM900 (200310)

Basic Data1100/1102: Storage/Accounting/Purch.1100/1102: MRP (PD/EX/100x/min.200)

Material (HALB)

[R/3]

Frame Painted Black (300100)

Basic Data1100/1102: Storage/Acc./Purch.1100/1102: MRP (PD/EX/100x and special procurement key 30 = subcontr.)

(Material for Subcontracting)

Material (ROH)

[R/3]

Frame Aluminium MTB (200105)

Basic Data1100/1102: Stor./Acc./Purch/MRP

(Component for Subcontracting material)

Material (DIEN)

[R/3]

Cleaning services for buildings (600001)

Basis Data1100: Purchasing/Accounting (with cleaning services valuation class)

Scheduling agreement (LU)

Material 100001 Delivery plant 1100Receiving plant 1200Purchase Organization 1000

Source list Material 100001 / Plant 1200

With assigned LU-scheduling agreement (relevant for MRP)

Ext. Service (GRND)

Building a booth for fairy trade (1000000)

Valuation class 3200 (services)

Service Conditions 100 EUR / h Purch. Org. 2000

Vendor Top Design / Plant 2100

Service 1000000

May 2003 Page 12/127


Course Schedule


Employee (HR) Marsha Bridges (Personnel Number 1245)

Active employeePers.area 1000Salaried employee

Primary cost elements

417002 Purchased services (clean)

477050 Purchased ext. training

477055 Purchased training mat.

Default cost centre assignment 1160

Secondary cost elements

640010 Set-up hours

640020 Production hours

640040 Repair hours

All: Cost element type 43

Activity Types 1440 Set-up hours

1450 Production hours

1480 Repair hours

All: Activity Type Category 1, Price Indicator 3

Cost Centres See ASAP Documents

(1110 to 2230)

Assigned to profit centres

Statistical Key Figures

EMPL Employees

ENER Energy consumpt.

FLOOR Floor space

Fixed values

Total values

Fixed values

Internal Orders 400000 Trade Fair Bike

400001 Trade Fair Superbike

9ACS1000 Bike Accrual calculation

9ACS2000 Superbike Accrual calculation

Company code 1000

Company code 2000

Company code 1000

Company code 2000

Profit Centres See ASAP Documents

(10 to 99)

99 is Dummy Profit Centre

G/L accounts and further FIN data due to ASAP business blueprint documents.

2 User ID and Passwords for Course Participants

2.1 Logging onto a client for the first time – only trainers

Like in teaching clients, trainers can access the case study clients for the first time using:

User: TRAINING

Password: Password of the month (your training administrator is telling it)

May 2003 Page 13/127


Course ScheduleThis user and password should only be used for creating users. You need to create users for the participants only in client 400 (see the following sections). Furthermore you need to create the user HELP in client 400 and you should create your own user in all other relevant clients (100, 101, etc.).

2.2 Existing Users in Case Study Project Clients 1##

The following users exist in every project client 1## (101 up to 110):

User Initial PW Password Note

T-FIN-## STUDY (Will be entered by everyone itself.)

For FI/CO-students (## = 01 up to 10).

T-OF-## STUDY (Will be entered by everyone itself.)

For SCM-Order Fulfillment students(## = 01 up to 10).

T-PR-## STUDY (Will be entered by everyone itself.)

For SCM-Procurement students (## = 01 up to 10).

T-PL-## STUDY (Will be entered by everyone itself.)

For SCM-Planning students (## = 01 up to 10).

T-MF-## STUDY (Will be entered by everyone itself.)

For SCM-Manufacturing students (## = 01 up to 10).

T-HR-## STUDY (Will be entered by everyone itself.)

For HR-students (## = 01 up to 10).

CASE STUDY (Will be entered by everyone itself.)

Reserve / Master user

These users are copied from the user TRAINING and they have very powerful authorizations (SAP_ALL, SAP_NEW). The trainers may use the users T-xx-00 (xx = area/track).

You inform the students about these users in unit 1 (course overview). It is described in unit 2, too.

Note: The users got the following properties:

Date format: DD.MM.YYYY

Decimal format: 123.456,789

The participants may change it via System User Data Own Data.

2.3 Creating Users in Mail Client 400

Enter the Mail client (in SAP training systems, the client 400) and create the user HELP , using the transaction SU01. This is the address for the participants who need help and want to send a mail to the „Hotline“.

Furthermore create for each track included in the case study the users HELP-xx-## , where xx is the area/track (FIN, OF, PR, PL, MF, HR) and ## is the team number. For example, if you have 6 teams with FIN-, OF- and PR-people, the highest team number is 6, and you need the following HELP-users:

T-FIN-01, …, T-FIN-06,

T-OF-01, ..., T-OF-06 and

T-PR-01, …, T-PR-06.

To do this, use transaction ZUSR with following data:

May 2003 Page 14/127


Course Schedule

ZUSR-field Enter NoteCopy from TRAININGName of course HELP-xx Where xx = FIN, OF, PR, PL, MF, HR

(tracks/areas) No of exercise groups (Highest team no.) For example, if you have 6 teams, the

highest team number is 6.Initial password STUDY

You get the following popup:

Answer “No”.

The next popup gives you the full user names, for example HELP-HR-00 to HELP-HR-06, and it is asking, “Create these user?” Answer “Create”.

If you see the list of created users, you should go back and create the users for the next area/track.

All these result in the following HELP users in client 400:


HELP-FIN-## STUDY (Will be entered by the FIN-team)

For students, only to send a mail to user HELP. Only needed if FIN (FI/CO) is included.

HELP-OF-## STUDY (Will be entered by the OF-team)

For students, only to send a mail to user HELP. Only needed if OF (SD) is included.

HELP-PR-## STUDY (Will be entered by the PR-team)

For students, only to send a mail to user HELP. Only needed if PR (MM) is included.

HELP-PL-## STUDY (Will be entered by the PL-team)

For students, only to send a mail to user HELP. Only needed if PL (SCM-Planning) is included.

HELP-MF-## STUDY (Will be entered by the MF-team)

For students, only to send a mail to user HELP. Only needed if MF (SCM-Manufacturing) is included.

HELP-HR-## STUDY (Will be entered by the HR-team)

For students, only to send a mail to user HELP. Only needed if HR is included.

May 2003 Page 15/127


Course Schedule


HELP (your choice) (Agree with your trainer team)

For trainer team

You should create these users Monday morning, latest at the end of the introduction session.

You inform about these users during the course overview unit. Furthermore at this time, you explain how to send and read mails.

Note: The participants may use this client also to see and check a “working” client.

2.4 Users in solution client 100 – only for trainersEvery trainer may create his/her own user in this client. Enter the first time with user TRAINING and password of the month.

Client 100 is only allowed for instructors. It should never used by participants!

3 Preparation in the System

Just create the help users in client 400 as described above. Maybe create your own user in clients 100, 101, .etc.

Check transaction scc4 whether the roles of the clients are set to “Customizing”.

4 Example ABAPs

Normally, no ABAP needed.

However, to prevent the error message GA627 (CO) start the report RK811XST in all relevant clients (TC SE38) before the students start processing allocations. Alternatively, the participants may do it when they receive the error message and follow the link in the message. The report creates transaction basic sets for the allocation processor. This is in some cases necessary after a client copy (also see: note 101206).

5 CATTs

No CATT is needed.

Note: The CATT ZT_CASE_STUDY_NOPP - used in some 4.6B academies - is not needed anymore. The relevant situation will not appear in 4.6C academies, because the relevant CO process / demand is erased (the necessary CO knowledge is not available).

6 Technical Hints

The projects clients 1## (101 up to 110) are nearly “empty” clients (copies from client 000). There are just settings, which are delivered in every “new” customer R/3 system. However, there are the user records and client-independent settings

It is important that the normal enqueing mechanism is working in the project clients 1## during the case study. In standard it should be active.

May 2003 Page 16/127


Course Schedule

If not, run the report ZSENQON in related clients to switch it on.

May 2003 Page 17/127


Course Schedule

Goals and Objectives

The Case Study is the final part of the SAP Solution Academy basic courses for consultants, where the participants have the opportunity to complete a short project on their own. The participants work as a team of consultants to prepare a system according to customer requirements. For example they have:

To build their team (who is project leader, etc.) and to work in a project team

To discuss organizational structures, to present this to the customer and to set up this structure in the system(s)

To manage their project (project plan, team meetings)

To make customizing settings and to maintain the necessary data for prototype business processes

To report daily to the customer To demonstrate their solutions to the customer during the presentation of the prototype.

Course Structure and Flow

1 General information

During the case study, the SAP Solution Academy participants are regrouped so that at least two members from each track, which you have running, are included in the team (if possible, not more then 4 per area/track in a team).

In every team the following areas/tracks are mandatory:

Managerial & Financial Accounting (FIN),

SCM-Order Fulfillment (OF) and

SCM-Procurement (PR).

All other areas are optional in a team:

(SCM-Planning (PL),

SC-Manufacturing (MF) and

Management/Administration (HR).

Each team then acts as one project team customizing a system for the customer. Areas, which are not included in a team (see optional areas above), are not part of the prototype processes. However, the Customer Bike International is planning to have a later implementation and a later project start for these areas. You should inform the participants about this fact, and which of the areas have to be considered in that way (see unit 1 – course overview).

The trainers play the role of the customer management. Furthermore, if necessary, the trainers help as a hotline.

Detailed information with regards to the content of the case study is included in the case study materials, which need to be distributed to the students (see Course Materials and other Materials). These materials are also the main source of information!

May 2003 Page 18/127


Course Schedule2 Case Study Structure

The case study starts with an introduction session, where you present the preface slides as well as unit 1 – course overview. (Every participant got the manual, but not the document, containing the organizational structure decision (solution).)

Following, the participants break into the teams, to be consultants and to work on the tasks of phase 1 (Organize the project team, define the organizational structure, prepare a presentation of the results).

At the afternoon of the first day, the teams present their results of phase 1. The Bike International Management (that means, the instructors) handout the organizational structure decision. Furthermore the instructors give feedback and maybe some additional hints for phase 2.

At the end of day 1 or in the morning of day 2 the participants start with phase 2, that means to customize the system, to maintain data, to test the prototype business processes, prepare the final presentation of prototype processes, etc. Furthermore there are daily meetings with the management, to discuss the status, problems etc.

At the afternoon of day 4, every team presents some of its results to the management of Bike International. Again, the instructors give feedback.

For details, see next sections.

3 Case Study Overview (Introduction session: Preface and Unit 1)

Approximate 30 Minutes

In this session, you explain the structure of the case study, the objectives and tasks they have to do during the case study, the timetable for that tasks, etc. Furthermore you give some organizational information and hints, such as the system, the clients, the users, etc.

To do it use

Preface slides

Slides of unit 1 – course overview (Suggestion: Instead of the course slides, please use the template from SAPNet to create your own Powerpoint file with specific data)

The objectives of the first case study introduction session are to:

Outline the objectives and tasks

Outline the roles of the students, customer and management

Provide some direction. For example, the trainers should outline the modules/solutions, which the customer would like to have presented during the prototype presentation (the modules which are included in the Academy). If certain modules are not running in the Academy, the trainers must indicate that the management would like to implement the other modules in a later phase of the project. This information is important when participants are defining the organizational structure and when customizing the business processes.

Provide organizational information, for example, when and where the meetings will be (definition of organizational structure, daily report), etc.

Demonstrate the use of SAP Office in client 400

May 2003 Page 19/127


Course Schedule

Enable the students to work themselves by giving all necessary information.

Following, we mention the slides, where you should enter your own data using the template from SAPNet for unit 1 (course overview), feel free to enter more details as given here:

Bike International Management introduces themselves

Enter the names of the instructors (e.g. the managers of Bike Intern.).

Delete all lines with areas, which will not be part of this case study.

Outline all areas/solutions, which are not part of this case study run.

The Bike International Enterprises

Enter the country, where your academy runs as country 1 and enter a suggestion for country 2. Have attention that the currency of both countries differs from each other.

Phase 1: Definition of the Organizational Structures

Enter the time, when the meetings will start (for one team, which will be the first).

During your presentation please mention the duration of organizational structure meetings. Furthermore mention, that there will be a sequence of meetings (only one team will start at the given time).

Outline, that only the unit 2 document “Introduction – The Bike International Company” is to be read/used for the tasks of phase 1.

Maybe you like to have an earlier start for the FIN teams (to create company codes). In this case, you agree with them about the FIN organizational structure earlier. If not, on this slide just delete the note about the Financials director.

Time Schedule

Enter the times valid for your case study run, especially the time, when the final presentations will start (for one team, which will be the first).

During your presentation you should mention your expectations for the daily status report, for example that you want to know the status of the prototype processes (and not the status of the sub-teams).

After this introduction the students break into the project rooms to work on tasks of phase 1.

4 Phase 1 – Team organization and Organizational Structure (Unit 2)

Each team has at least 1-2 hours to organize the team and to discuss an organizational structure. Unit 2 (Introduction – The Bike International Company) contains the necessary information – to read by the participants (self study). It describes:

the case study

the tasks to be completed during the case study

the organizational structure and main targets of Bike International

May 2003 Page 20/127


Course ScheduleThereafter, a meeting is held where each team is given the opportunity to introduce their team and to present their organizational structure proposal. The trainers play the role of the customer management team. As a trainer, you should check the thinking behind the organizational structure presented by the groups and ask additional questions if necessary.

Once the presentation(s) has/have been held, the decided organizational structure (former called “solution”) should be delivered (the document) and presented by the trainers. The groups should use this solution for the business process customizing.

Furthermore the instructors give feedback and maybe they give some tips for the following tasks.

If there are no questions or proposals from the groups with regards to a business reengineering (potential for optimization) are made, encourage the participants to do this. Ensure however that the decision about the desired organizational structure is made by the customer: the given decision document. This ensures that the students use the structure and the given codes. In this way, it is easier for the trainer team to quickly give support via the hotline when problems arise.

Especially, if you have a large number of teams, the teams have to wait a very long time for their presentation and for the start in the systems. To accelerate the start, you should discuss and agree with the FIN teams about the FIN organizational structure earlier (during their project work at day one). That’s why there is a note in unit 1, that the financials director expects the FIN structure proposal earlier. To agree with them and to have a decision about the FIN structure, just download from SAPNet the relevant document with the separate FIN structure and hand it out to the participants during your discussion. With that document, the FIN teams may start to implement the FIN organizational structure and to be ready with company codes, when logistics wants to create their structure. However, the FIN teams should take part at the normal organizational structures meeting!

5 Phase 2 – System(s) set up / Implement Business Processes (Units 3, 4, 5)

Again, the participants break-out into case study teams to start with customizing of the organizational structure and the business processes. They maintain the necessary data and test the relevant processes. If necessary the trainers give support.

The relevant information can be found in the following units:

Unit 3 (ASAP Business Blueprint Master Data) - Details

Unit 4 (ASAP Business Blueprint Business Processes) - Details

Unit 5 (Prototype Business Processes for the Presentation)

Note, that unit 5 is giving the processes for the prototype presentation. These are the management expectations, i.e. what the management would like to see during the prototype presentation. The students should focus on these subjects. If not trigger them in that direction.

The ASAP documents (units 3 and 4) containing detailed information, needed for the prototype processes. However, these units contain much more information, also such which are not relevant for the prototype. If the teams are ready with the prototype processes they may set up further processes (optional).

These ASAP documents (units 3 and 4) are based on ASAP QADB (“delivered by colleagues”). Anyway, there will be probably not enough time and not the knowledge at participants’ side, really to use the ASAP tool. However, they should document their status by the help of a simple project plan. Furthermore they should document, which customizing steps, they have done (IMG status facility).

May 2003 Page 21/127


Course ScheduleAt days 2 and 3 the teams should present to the management (trainers) a status report. The management should be informed about the status of the project, about problems that arisen, if they are in time etc. If they have made some basic settings (as organizational structures, number ranges etc.), they should focus at the status of the prototype processes (instead of status of the sub-teams).

You may have one meeting per day with the project leaders and substitutes of every team at the same time. However, the instructors should go through all teams to “hear” all participants (their feeling, maybe additional problems, to support them).

Alternately, you may have the status report for each single team (with the whole team).

Use the last status report (the one on day 3), to get information, which processes could be presented by the teams and which not. Furthermore due to the prototype presentation you should agree with the teams about the sequence of the teams (plan about one hour per team + a little bit reserve/break for you). Ask for their wishes. And maybe use the number of running processes, to decide if the team could present early or later.

The teams have to prepare the prototype presentation.

Relevant settings are described in the next “unit” sections of this guide: First the enterprise structure settings, followed by “units” containing further settings of a track/area.

6 Presentation of some prototype processes (Unit 5)

At the previous status report the teams should have presented, which prototype processes are running so far (and maybe in which quality). Furthermore you should have decided, in which sequence the teams will present and at which time. You should plan about 1 hour per team (depending from the number of tracks, that are included).

During the team presentations at day 4 (afternoon), the trainers are playing the role of Bikes managers. You are interested in the prototype processes.

At the beginning you should ask, if further processes are running now (comparing with the last status report). Decide with your trainer colleagues (“managers”), which prototype processes you like to see from this team. Note: You can see only some processes (maybe just 2 or 3). Ensure to include all tracks/areas.

The team is presenting their results. From time to time you may ask for some more details, explanations, etc. Be just an interested customer… However, be fair and remember, that a certification is following at the next day. Don’t confuse them to much. If necessary, feel free to help with a tip etc.

If the team spent to much time for a single process/a single solution, and you are running out of time to see all tracks/areas, stop the presentation and jump to the next step or process.

At the end of the presentation you should give feedback (about their success, about the style of the presentation, maybe add some tips). Focus on positive things, but don’t spare the negatives.

Last but not least, ask for feedback from the participants. How’s the feeling? Did they enjoy? How useful do they consider the case study? And so one…

By the way: The online-evaluation should take place at Thursday - in the morning! (or even at Wednesday evening). Later on, nobody will be there to do it! However, a personal participants feedback should take place at the end of the presentation.

May 2003 Page 22/127


Course Schedule

Course Schedule

Day / Appr. Duration

Content: Units and Topics Activities: Instructor and Participant

Day 1

30 min.

Preface and Course overview (Unit 1)

Goals and Objectives

Content

Business Scenario

Information about the case study flow

The instructors explain the case study objectives, the business scenario, the structure, the tasks, etc. and they give various information (included areas, countries, system, clients, user, tips & hints, etc.).

Nearly the rest of day 1

Phase 1 (Team organization & Organizational structure)

Unit 2 – Introduction – The Bike International Company (self-study)

Kick-off Meeting / Organizational structure team presentation und managements’ decision

The participants break-out into case study teams to form the project teams and to discuss the organi-zational structures.

Every team introduces themselves and presents its team-agreed organizational structure.

The instructors are playing the role of the customer Management.

Finally, the instructors handout the decision for Bike’s organizational structure. Furthermore they give feedback and hints.

Day 1 after the meeting

Begin Phase 2 (Organizational structure setup, Implementation and Test of Prototype scenarios)

Bike International – organizational structure (decision)

Unit 3 – ASAP Business Blueprint Master Data (self-study)

Unit 4 – ASAP Business Blueprint Processes (self-study)

Unit 5 – Prototype processes for the presentation (self-study)

The participants break-out into case study teams to start with customizing of the organizational structure and the business processes. They maintain the necessary data and test the relevant processes.

Days 2, 3 and Day 4 AM

Continuation of Phase 2 At days 2 and 3 - in addition to the activities of phase 2 at day 1 – the teams (leader and substitute) present to the management a daily status report.

Day 4 PM Team presentations of prototype Every team is presenting some

May 2003 Page 23/127


Course Schedule

(about 1 h per team)

processes

Unit 5 – Prototype processes for the presentation

selected prototype processes. Ensure that all tracks will be included. Have attention to their status (which processes are running/which not).

Give feedback and ask for feedback due to the whole case study.

Additional notes:

Online evaluation should take place latest at Thursday morning! Later on, nobody will be there to do it…

The following time table (or an adopted one) is presented by you during the introduction session (Unit 1 – course overview):

Monday10:00 am - 10:30 am Introduction

10:45 am - 05:00 pm Project work & presentation

Tuesday 09:00 am - 05:00 pm Project work

02:00 pm - 02:30 pm Status report*

Wednesday 09:00 am - 05:00 pm Project work

02:00 pm - 02:30 pm Status report*

Thursday 09:00 am - 05:00 pm Project work

starting from _____ pm Presentation

*Project Manager and Substitute

May 2003 Page 24/127


Unit: Organizational Structures


1 Contents of Unit

Define and setup various organizational elements such as Company Codes, Plants, storage locations, Purchase organizations, Sales areas, etc.

2 Putting the Unit in Context

The team has to discuss, how the structure of Bike International should be build up in the SAP system(s). They present their results to the Bike Int. management (the instructors). The instructors (as managers of Bike Int.) asking for details or reasons.

After all the instructors are handing out to the participants the decided organizational structure (material “Bike International – Organizational structure (decision)”). The instructor s are giving feedback to the suggested solutions and they should give some hints due to the presentation and due to the next steps (for example, not to erase org. structures like plant 0001 after copying them).

Work within a project team

Discuss and define the organizational structure of Bike International

Present the results to the customer (presentation)

Set up the system with the decided organizational structure

Get practical experience

Recover the knowledge from previous courses

3 Settings in SAP systems

Use IMG menu pathes

Enterprise Structure Definition <Area> and

Enterprise Structure Assignment <Area>

Make in your area the following settings according to the Bike International Organizational structure decision:

May 2003 Page 25/127



3.1 Financials (Financial Accounting and Controlling)

As the enterprise structure in Financial Accounting is vital for the entire team, make sure that the participants don’t lose too much time with it and guide them accordingly.

Step 1:Check that country 1 is installed (for controlling area 0001 and company code 0001).< Financial Accounting\Financial Accounting Global Settings\Company Code\Enter Global Parameters>Use country-installer to modify if necessary.<General Settings\Set countries\Define countries>

Step 2:Define controlling area 1000 and company code 1000 by using the copy function for controlling areas. Copy company code segments of chart of accounts only if chart of accounts INT is defined for company code 0001.<Enterprise Structure\Definition\Controlling\Maintain Controlling Area>

Step 3:This step is only relevant if you did not copy the company segments of the chart of accounts.Change the chart of accounts for company code 1000 in the global parameters of company code 1000 to INT.< Financial Accounting\Financial Accounting Global Settings\Company Code\Enter Global Parameters> Copy the company code segments of G/L accounts from company code COPY.<Financial Accounting\General Ledger Accounting\G/L Accounts\Master Records\G/L Account Creation and Processing\Alternative Methods\Copy G/L Accounts\Copy Company Code>

Step 4:Set country version to country 2<General Settings\Set countries\Define countries>

Step 5:Copy company code 0001 to 2000. For the company code segments of the chart of accounts use the same proceeding as described in Step 2 and 3.<Enterprise Structure\Definition\Financial Accounting\Define, copy, delete, check company code>

Special note:The chart of accounts can only be modified, if no single company code segment exists. Company code segments though, can be deleted.<General Ledger Accounting \G/L Accounts\Master Records\Preparations\Deletion\Delete G/L Account>

May 2003 Page 26/127



3.2 Logistics – General

3.2.1 Valuation Level

Define valuation level as “Valuation level is a plant”.

3.2.2 Plants

Define plants 1100, 1200, 2100 by using the copy function to copy all entries from plant 0001. Enter the right names, addresses and calendars.Note: They should keep plant 0001 within the system!Plant 1100: Star City (German: Großstadt)Plant 1200: Moon Village (German: Kleindorf)Plant 2100: Mercury City (German: Mittelstadt)

Assign plants to company codesCompany code 1000 Bike Plants 1100, 1200Company code 2000 Super Bike Plant 2100

3.2.3 Division

Define division 00 – spreading, 02 – Mtn. Bikes, 03 – Street Bikes, 04 – Accessories

3.3 Sales and Distribution

3.3.1 Sales Org.

Define S.Org. 1000 BIKE, 2000 SUPERBIKE

Assign S.Org. – Co.Code

S.Org. 1000 Co.Code 1000

S.Org. 2000 Co.Code 2000

3.3.2 Distr. Channel

Define distr. Channel 02 wholesale, 03 Retail

May 2003 Page 27/127



Assign S.Org. Distr. Channel

S.Org. 1000 Distr. Channel 02




Assign Division S.Org.

00, 02, 03, 04 1000, 2000

create sales area

assign S.Org. distr.channel plant

3.3.3 Sales office

Define sales office 1000 star city, 1001 moon vill, 2000 mercury city

assign sales area sales office

3.4 Materials Management

3.4.1 Storage locations

Plant 1100: 1101 (sales mat. Star C.), 1102 (other mat. Star C.), 1103 (ProBike-Shop)

Plant 1200: 1201 (Moon Vil. mat.)

Plant 2100: 2101 (Merc.C. mat.)

The descriptions are just suggestions.

3.4.2 Purchase organizations

Define purchase organizations 1 (central PUR org), 1000 (Bike PUR org.), 2000 (Super Bike PUR org)

May 2003 Page 28/127



The descriptions are just suggestions.

Assign purchase organizations to company codesCompany code 1000 Bike 1000 Bike PUR orgCompany code 2000 Super Bike Superbike PUR org.

Assign purchase organizations to plantsPORG 1000 plants 1100 and 1200PORG 2000 plant 2100PORG 1 plants 1100, 1200 and 2100

Assign standard purchasing organization to plantsPlant 1100 PORG 1000Plant 1200 PORG 1000Plant 2100 PORG 2000

Assign PORG to reference PORGPORG 1000 PORG 1PORG 2000 PORG 1

3.5 Logistics Execution

3.5.1 Warehouse number

The warehouse number 100 Lean WM (without stocks) should exist (otherwise define it).

Assign warehouse number to plants/storage locations:

1100/1101 warehouse number 100



3.5.2 Shipping points

May 2003 Page 29/127



Define 1100 – normally, 110E – Pro Bike Shop, 1200 – normally, 2100 – normally

Assign shipping points plants

1100 1100

110E 1100

1200 1200

2100 2100

3.6 Human Resources Management

Define personnel areas Star City and Mercury City1000 Star City2000 Mercury City

Define personnel subareas Star City, Moon Village, Call Center and Mercury CitySC01 - Star CityMC01 – Moon VillageCC01 – Call CenterMC01 – Mercury City

Assign personnel subareas to personnel areasPersonnel area 1000 – MV01Personnel area 1000 – CC01Personnel area 1000 – SC01Personnel area 2000 – MC01

Assign personnel areas to company codesCompany code 1000 Bike 1000 Star CityCompany code 2000 Super Bike 2000 Mercury City

Define employee groupsActive employee 1

May 2003 Page 30/127



Define employee subgroupsZS - Salaried employees ZN - Non pay scale employee

Assign employee subgroups to employee groupsSalaried employees and non pay scale employee to active employees (user molga or country 1)1 – ZS1 - ZN

May 2003 Page 31/127



Unit: TFIN14 Managerial & Financial Accounting

1 Contents of Unit

Note:

For FIN instructors basic FI/CO knowledge (enterprise structure and master data) should be sufficient for days 1-2. From day 2 on more detailed knowledge in both application modules is essential.

FI:

Account groups AP, AR

chart of accounts

bank accounts

cross-company code transactions

line items, balances

closing activities

dunning

manual incoming payments

cash journal

correspondence

open item clearing

automatic outgoing payments

CO:

Cost elements (primary/secondary, default acct. assignment)

Cost centers

May 2003 Page 32/127



Activity types (only for manual entry, allocation and price)

Statistical key figures (fixed value / total value)

Internal Orders (for accrual calculation and for trade fairs; customizing of order type, budget profile and settlement profile / settlement rule, order groups)

Profit center (standard hierarchy, dummy profit center, assignment to master data in other application modules)

Substitution of profit centers in sales orders

Commitment management, budgeting and availability control for internal orders

Planning of activity output/prices, activity independent planning of primary costs and activity input, planning of statistical key figures

Accrual calculation (plan/actual)

Plan and actual: distribution, assessment, settlement

Generating opening balance for material stocks and payables/receivables in profit center accounting

Creating report painter reports




Recover the knowledge of previous courses in a practical-oriented way

Set up business processes (customizing and data maintenance)

Test the scenarios and prepare presentations


2.1 Prototype process 1: Integration FIN- and PR-, PL-/MF-team (maybe OF)

FI obtains an open item on an account payable with a payment block from PR. A payment run has to be executed. The outgoing payment on the bank

May 2003 Page 33/127



statement of the following day has to be posted in FI with clearing the open item on the bank sub-account.

2.2 Prototype process 2: Integration FIN- and MF-team

In CO the cost centre must show a credit for activity allocation after the new material is produced. In profit centre accounting the debits and credits from production orders and cost centres have to be shown. Optional the participants might also show the change in material stocks in profit centre accounting.

2.3 Prototype process 3: Integration HR- and FIN-team

The transfer of the payroll into FI, CO is demonstrated. The outgoing payment for salaries, income tax and social insurance on the bank statement of the following day has to be posted in FI with clearing the open item on the bank sub-account. On the employee’s cost centre a debit for personnel cost is shown.

2.4 Prototype process 4: Planning and Reporting in CO

A report painter report with cost elements in general selections (with variation), cost centres in rows and 10 columns with plan/actual costs restricted to quarters and full year has to be created. In 3 different (standard-) report painter reports the planned values on cost centres and profit centres and the budgeted values on internal orders are shown. Additional plan values have to be created and the plan allocations (distribution, assessment, accrual calculation, settlement) have to be executed. The results are shown in the standard reports.

2.5 Prototype process 5: Integration PR- and FIN-team

An open item in foreign currency is created by PR. FI has to run a foreign currency valuation. The costs are shown in the standard internal order and profit centre reports and a drilldown to the FI-document is shown. An order group with the two trade fair orders has to be created.

2.6 Prototype process 6: Integration OF-- and FIN-team

An open item is created by OF. First a partial payment has to be posted. A dunning run has to be executed. An invalid value adjustment has to be fulfilled and afterwards reversed due to the payment of the balance. In profit centre accounting the costs are shown. For the opening balance of AP/AR in profit centre accounting refer to process 10.

2.7 Prototype process 7: Integration PR-- and FIN-team (maybe OF)

The process has focus on Logistics. FI, CO only needs to show some posting documents.


An ingoing payment has to be posted with the cash journal. The offsetting account is a clearing account to which OF will post its billing document. The offsetting account has to be cleared automatically afterwards.

2.9 Prototype process 9: Integration PR-- and FIN-team

The actual costs are shown in a standard cost centre report. A distribution of cleaning service costs based on statistical key figure FLOOR is processed.

May 2003 Page 34/127



2.10 Prototype process 10: Closing in FI/CO (FIN)

Several closing business transactions have to be executed using the schedule manager. For the opening balance of AP/AR in profit centre accounting (as a prerequisite) the balance sheet adjustment has to be calculated (transaction F.5D).

2.11 Prototype process 12: Integration OF-, PR-, FIN-team

The FI-part in this process is very small. A billing document has to be posted. The account for inventory differences has to be reduced. This can be done in one or two accounting documents.

May 2003 Page 35/127



3 R/3 settings

Note: Setting due to Organizational structures are described in Organizational structures unit (see above).

3.1 FI:

Settings Solution - IMG - Menu Path Comments

Master data FI

Account group settings

IMG:

Financial Accounting Accounts Receivable and Accounts Payable Customer Accounts Master Records Preparations for Creating Customer Master Records Define Account Groups with Screen Layout (Customers)

Financial Accounting Accounts Receivable and Accounts Payable Vendor Accounts Master Records Preparations for Creating Vendor Master Records Define Account Groups with Screen Layout (Vendors)

Define field status for account groups DEBI and CPD (AR), KRED CPD (AP) accordingly to the blueprint.

Customer, vendor master data

Transaction XD01, FD01; XK01, FK01 Create customer and vendor master data

House bank IMG:

Financial Accounting Bank Accounting Bank Accounts Define House Banks

Participants should invent their house bank and bank account key

G/L accounts Transaction FS00 Define additional G/L accounts accordingly to the blueprint

Business transactions

May 2003 Page 36/127




Cross-company transactions

IMG:

Financial Accounting General Ledger Accounting Business Transactions Prepare Cross-Company Code Transactions

Optional! (not required in prototype processes)

Posting period Transaction OB52

Line item control: tolerance groups for employees

IMG:

Financial Accounting Financial Accounting Global Settings Document Line Item Controls Define Tolerance Groups for Employees

Define tolerance group blank for all employees, tolerance group BIG for financial accounting manager

Document reversal: negative posting

1. company code settings

IMG: Financial Accounting Financial Accounting Global Settings Company Code Enter Global Parameters

Activate field “Negative posting allowed”

2. Document type settings

IMG: Financial Accounting Financial Accounting Global Settings Document Document Header Define Document Types

Activate field “Negative posting allowed” (exemplary for one document type invalid value adjustment)

3. Reason for reversal

IMG: Financial Accounting General Ledger Accounting Business Transactions Adjustment Posting/Reversal Define Reasons for Reversal

Optional!

document reversal is only needed in prototype process 6 for the reversal of the invalid value adjustment.

Document change rule

IMG:

Financial Accounting Financial Accounting Global Settings

May 2003 Page 37/127




Document Document Header Document Change Rules, Document Header

Add field BKPF-BKTXT and field BKPF-XBLNR

Line item display: layouts

Transaction FBL1N, FBL3N, FBL5N

define layouts

Document posting: fast entry

IMG:

Financial Accounting General Ledger Accounting Business Transactions G/L Account Posting Carry Out and Check Document Settings Maintain Fast Entry Screens for G/L Account Items

Optional! (not required in prototype processes)

Define accordingly to client 100 variant bike.

Note: this is the variant for the old FB01 transaction.

For enjoy transactions have a look at SAP Note 186961

Define worklists Transaction OB55 Optional! (not required in prototype processes)

A G/L account worklist for bank and bank subaccounts can be defined

Define financial statement version

IMG:

Financial Accounting General Ledger Accounting Business Transactions Closing Documenting Define Financial Statement Versions

Define version BIKE accordingly to client 100 (additional accounts to be inserted)

Foreign currency valuation

IMG:

Financial Accounting General Ledger Accounting Business Transactions Closing Valuating Foreign Currency Valuation

Define method BIKE accordingly to client 100.

Note: to get a result in the foreign currency

May 2003 Page 38/127




Define Valuation Methods valuation exchange rates have to be modified appropriately

Regrouping of AR, AP

IMG:

Financial Accounting Accounts Receivable and Accounts Payable Business Transactions Closing Regroup Define Sort Method and Adjustment Accts for Regrouping Receivables/Payables

Check sort method SAP or define a sort method according to legislation in your country.

Note: The adjustment accounts can be defined form within this transaction

Regrouping of GR/IR clearing account

IMG:

Financial Accounting General Ledger Accounting Business Transactions Closing Regrouping Define Adjustment Accounts for GR/IR Clearing

Check the standard settings

Reserve for bad debit, down payment (manual incoming payment)

IMG:

Financial Accounting Accounts Receivable and Accounts Payable Business Transactions Postings with Alternative Reconciliation Account Other Special G/L Transactions Define Alternative Reconciliation Account for Customers

Check the standard settings for special G/L indicator E, A (manual incoming payment)

Scheduling of closing activities

Transaction SCMA Use task list CLOSING in client 100 as an example

Line item display Transaction FBL5N

Define layout, output subtotal for field invoice reference to keep together the invoice with partial payments

Dunning Transaction F150, <Environment\Change Configuration>

1. Dunning proceduresDefine dunning procedures accordingly to procedure 1000, 1001

May 2003 Page 39/127




in client 100

2. <Environment\Sort fields\Dunning notice item>Define accordingly sort variant P1 in client 100

3. <Environment\Company Code Data>Define Sort MHND as P1

Manual incoming payments

1. Define line layout variant for clearing transaction accordingly to variant BIK in client 100IMG: Financial Accounting Accounts Receivable and Accounts Payable Business Transactions Open Item Clearing Make Settings for Processing Open Items Define Line Layout for Document Change/Display

2. Down payment (see above)

Cross-company incoming payments

No extra customizing required, see above for cross-company transactions in general

Cash journal 1. General settingsIMG: Financial Accounting Bank Accounting Business Transactions Cash Journal Set Up Cash JournalCash journal 0001 is used in client 100

2. Business transactionsIMG: Financial Accounting Bank Accounting Business Transactions Cash Journal Create, Change, Delete Business Transactions

For prototype process 8, only business transaction PROBIKESHOP as defined in client 100 is needed.

Correspondence 1. Check general settings for correspondenceIMG: Financial Accounting Accounts Receivable and Accounts Payable Business Transactions Incoming

Take reason code for overpayment, underpayment 057 as an example.

May 2003 Page 40/127




Payments Manual Incoming Payments Outgoing Payment Notices Carry Out and Check Settings for Correspondence …

2. Define automatically generated payment notices for partial payments (accordingly to client 100)IMG: Financial Accounting Accounts Receivable and Accounts Payable Business Transactions Incoming Payments Manual Incoming Payments Outgoing Payment Notices Control the Automatically Generated Payment Notices

Automatic clearing 1. Rules for automatic clearingIMG: Financial Accounting Accounts Receivable and Accounts Payable Business Transactions Open Item Clearing Prepare Automatic Clearingfield XBLNR should be used as criterion for accounts receivablefield ZUONR should be used as criterion for G/L accounts

2. Tolerances for Customers/VendorsIMG: Financial Accounting Accounts Receivable and Accounts Payable Business Transactions Open Item Clearing Clearing Differences Define Tolerances for Customers/VendorsUse entry blank

3. Tolerances for G/L accountsIMG: Financial Accounting General Ledger Accounting Business Transactions Open Item Clearing Clearing Differences Define Tolerance Groups for G/L Accounts

Note:

For prototype 8 it is vital that SD and FI-team get into communication. Open item on account 100010 from invoice document (SD: copy control) and cash journal (FI: manual entry) must get the same entry in XBLNR (or ZUONR). The rule for automatic clearing has to be defined accordingly

May 2003 Page 41/127




Use entry blank

Automatic payments Most of the customizing is copied with the company code copy. Participants have to modify the following entries

Transaction F110, <Environment\Maintain Config>

1. All company codes: Tolerance days = 3, max. cash discount

2. Pmnt methods comp. code:S (C): min amount: 100.000,00, max amount 999.999,00U: min amount: 0,00, max amount 100.000,00

3. Bank determinationentries as in client 100:payment method U, S (C), house bank: GB, account ID: GIRO, FCA

Payment blocks Define Payment block R as changeable in payment proposal

IMG: Financial Accounting Accounts Receivable and Accounts Payable Business Transactions Release for Payment Define Payment Block Reasons for Payment Release

Note:

If payment block R is not changeable in payment proposal, payment block has to be deactivated in posting document or with MM-transaction

3.2 CO:

Settings R/3 - Menu Path Comments

Enter exchange rate for exchange rate type P and M

SPRO General Settings Currencies Enter exchange rates Make sure that the relevant exchange rates are maintained

Maintain controlling area SPRO General Controlling Organization Maintain Controlling Area

May 2003 Page 42/127




settings Controlling Area 1000

Basic Data

Name: Bike International

Cross-company-code cost accounting

Currency type: 30

Fisc. Year variant / Chart of Accounts: Same as in all company codes (K4 /INT)

Cost Center Standard Hierarchy: C0

Active components/control indicators

Active: Cost Centers, Order Man., Commitments Man., Profit Center, Sales Orders

Assignment of company codes

1000 and 2000

SPRO Controlling Profit Center Accounting Basic Settings Controlling Area Settings Maintain Controlling Area Settings Controlling Area 1000

Standard Hierarchy: P0

PCtr local currency type: 30

Legal valuation

Selected: Active indicator

May 2003 Page 43/127




Maintain versions and parameters for actual data

SPRO General Controlling Organization Maintain Versions Version 0

Controlling Area Settings

Selected: Plan, Actual

Settings by fiscal year

New Entries for relevant years

SPRO Controlling Profit Center Accounting Basic Settings Controlling Area Settings Activate Direct Postings Set Control Parameters for Actual Data Controlling Area 1000

Selected: Line Items, Online transfer

SPRO Controlling Profit Center Accounting Basic Settings Controlling Area Settings Activate Direct Postings Plan Versions Maintain Plan Versions Version 0 Settings for Profit Center Accounting

Selected: (Online transfer), (Line items)

Exchange rate type: M or P

Value date: Date for which an exchange rate is maintained

Define Profit Center / Profit Center Standard Hierarchy

Accounting Controlling Profit Center Accounting Master Data Standard Hierarchy Create / Change

Create and activate Profit Centers in the hierarchy according to ASAP-blueprint

Define Cost Center / Cost Center Standard Hierarchy

Accounting Controlling Cost Center Accounting Master Data Standard Hierarchy Change

Create Cost Centers and hierarchy nodes according to ASAP-blueprint

Profit Center Assignment is necessary

Create additional primary cost elements

Accounting Controlling Cost Element Accounting Master Data Cost Element Individual Processing Create Primary

G/L accounts must exist,

May 2003 Page 44/127




Create additional Cost elements according to ASAP-blueprint CCtr. 1160 as default assignment in account 417002

Create additional secondary cost elements

Accounting Controlling Cost Element Accounting Master Data Cost Element Individual Processing Create Secondary

Create additional Cost elements according to ASAP-blueprint

640010 – 640040: Cost element type 43

600500: Cost element type 21

630300: Cost element type 42

Create activity types Accounting Controlling Cost Center Accounting Master Data Activity Type Individual Processing Create

Activity type category 1 and price indicator 3 for all activity types according to ASAP-blueprint

Plan Activity Output/Prices Accounting Controlling Cost Center Accounting Planning Activity Output/Prices Change

Maintain activity output/prices as described in ASAP-blueprint

Create Statistical Key Figures Accounting Controlling Cost Center Accounting Master Data Statistical Key Figures Individual Processing Create

EMPL and FLOOR as type Fixed Value

ENER as Total Value

Maintain Budget Profile SPRO Controlling Internal Orders Budgeting and Availability Control Maintain Budget Profile Budget Profile for CO Orders

New Entry: Exchange Rate Type M or P, Activation Type 1, Controlling area currency,

May 2003 Page 45/127




selected: Overall

Define Tolerance Limits for Availability Control

SPRO Controlling Internal Orders Budgeting and Availability Control Define Tolerance Limits for Availability Control

New Entry for controlling area 1000 and the new budget profile: Act.Gr. 1, Action 2, Usage 100%

Define Order Types SPRO Controlling Internal Orders Order master Data Define Order Types

Copy: Order type 9A00 into own order type for Accrual calculation

Copy: Order type 0400 into own order type for trade fair orders

Change: necessary entries: own or standard settlement profile, own budget profile, commitment management, release immediately

For revenue postings out of SD an additional order type might be necessary

Maintain Budget Manager SPRO Controlling Internal Orders Budgeting and Availability Control Maintain Budget Manager

New Entry for trade fair order type and object class OCOST

Create Internal Orders Accounting Controlling Internal Orders Master Data Special Functions Order Create

Create Internal Orders according to ASAP-blueprint

Fill “settlement to one receiver” if no settlement profile is maintained in the order type

Assignment to company code and profit center is necessary

Assign Profit Center to Material Master

SPRO Controlling Profit Center Accounting Assignments to Profit Centers Material Perform Fast Assignment (or alternatively assign each material master separately)

Table name MARC, Execute (2x), Select Field: Profit Center

Fill with values according to ASAP-blueprint

Define Profit Center SPRO Controlling Profit Center Accounting Assignments to Profit Centers Important: Use the field

May 2003 Page 46/127




Substitution for Sales Orders Sales Orders Sales Order Substitutions

Define Substitution Rules

Define a new substitution with two steps according to the descriptions in the ASAP-blueprint

Assign Substitution Rules

Assign the new substitution to Controlling area 1000 with Active status 3

PCASUB-VKORG for the prerequisite

Change Original Order Budget

Accounting Controlling Internal Orders Budgeting Original Budget Change

Change the budget for the trade fair orders according to the ASAP-blueprint

Plan Statistical Key figures Accounting Controlling Cost Center Accounting Planning Statistical Key Figures Change

Change the planned key figures according to the ASAP-blueprint

Plan Activity Input (activity independent)

Accounting Controlling Cost Center Accounting Planning Cost And Activity Inputs Change

Layout 1-102

Maintain activity inputs as described in ASAP-blueprint

Switch to layout 1-102;

only select cost center, sender cost center and sender activity type on selection screen

Plan Primary Costs Accounting Controlling Cost Center Accounting Planning Cost and Activity Inputs Change

Change the planned primary costs according to the ASAP-blueprint

Layout 1-101

Create Plan (and Actual) Distribution

SPRO Controlling Cost Center Accounting Planning Allocations Distribution Define distribution Create

(SPRO Controlling Cost Center Accounting Actual Postings Period-End

May 2003 Page 47/127




Closing Distribution Define distribution Create)

Two segments:

100% of the booked cleaning service costs based on (planned or actual) statistical key figure FLOOR

100% of the booked energy costs based on (planned or actual) statistical key figure ENER

Create Plan (and Actual) Assessment

SPRO Controlling Cost Center Accounting Planning Allocations Assessment Define Assessment Create

(SPRO Controlling Cost Center Accounting Actual Postings Period-End Closing Assessment Assessment Create)

One segments:

100% of the booked training costs based on (planned or actual) statistical key figure EMPL

Maintain Overhead Structure for Accrual calculation Plan (and Actual)

SPRO Controlling Cost Center Accounting Planning Planning Aids Accrual Calculation Percentage method Maintain Overhead structure

(SPRO Controlling Cost Center Accounting Actual Postings Period-End Closing Accrual Calculation Percentage method Maintain Overhead structure)

First create Bases, Overhead rates and credits (via menu-path: Environment…) according to the ASAP-blueprint

Then create a new overhead structure

Finally assign this overhead structure for plan and actual accrual calculation in controlling area 1000

May 2003 Page 48/127



Unit: TSCM64 Order Fulfillment

1 Contents of Unit

account group customer

one-time customer

terms of payment

order type

order entry

item category

copying control

output determination

pricing

free goods

partner determination

incompleteness

number range

availability check

billing schedule

Lean-WM

shipping point determination

billing

consignment

May 2003 Page 49/127










2.1 Prototype process 1: Integration OF - and PR-, FIN-, PL-/MF-teams

PR is presenting, that a SD order in plant 2100 has generated transfer scheduling lines, which leads to demands in production plant 1100 (bikes). In that way the transfer to plant 1200 and the production in plant 1100 is triggered. OF just prepares the sales order in plant 1200. See process # 7.


OF sold, supplies and invoices in sales Org. 1000. The FIN-teams continues and explains the financial aspects.

2.3 Prototype process 7: Integration OF – and PR-, FIN-teams

OF puts on an order in sales org. 1000 to deliver from Moon village (plant 1200). MM has to organize, that missing stocks in plant 1200 will be delivered from production plant 1100 to plant 1200 (transfer). The team has to explain the financial aspects of these transfer postings. OF just prepares the sales order in plant 1200.

Note: If a team likes to implement the plant-to-plant-transfer using SD deliveries instead of the MM-GI-postings, they probably need support by OF/PR instructors.

May 2003 Page 50/127




OF puts on an order and produces a message for the Billing Document. Customer pays. Shipping and billing can be put on. Attention: IMG: Maintain Copying Control For Billing Documents Copying control: Sales document to billing document header allocation number = B (sales order).

Thus a better allocation is possible in FIN.

2.5 Prototype process 12: Integration OF – and PR-, FIN-teams

OF puts on a consignment fill-up and OF supplies and posts a goods issue. The customer announces a withdrawal and OF puts on a consignment issue. OF creates supply and posts goods issue and invoices.

PR checks customer consignment stocks and related movements. Furthermore they are doing a physical inventory (based on counting results of the customer), where FIN demonstrates the follow-on activities to debit/credit the customer due to differences.

OF fetches the remaining commodity and puts on a consignment pick-up. A supply with arrival is posted.

May 2003 Page 51/127



3 Settings in R/3 System (SCM-OF General Customizing)



Change account group DEBI IMG FIN Accounts Receivable and Accounts Payable Customer Accounts Master Records Preparations for Creating Customer Master Records Define Account Groups with Screen Layout (Customers) DEBI Detail –> Sales data Sales Customer district = opt. entry

pricing groups for customers IMG SD Basic Functions Pricing Maintain Price-Relevant Master Data Fields pricing groups for customers = 03 Wholesale; 04 Retail

Define goods receiving hours IMG SD Master Data Business Partners Customers Shipping Define goods receiving hours WE1 and WE2

Business partners create general data unloading points goods receiving hours

Create new order type IMG copy the standard OR order type/choose an new number interval, be careful that it is not being used for another purpose;

Check devision = no dialog

Create new item category IMG copy the standard TAN and change the field business data item (remove the checkmark) so that item payment terms cannot differ from the header

Assign item category Do not forget to assign the new

May 2003 Page 52/127




item category to the new order type

Free goods and new order type Remember to maintain the item category assignment

Zxxx NORM FREE ZTAN TANN

Incompletion procedure The volume field is not in the standard incompletion procedure

Get the field and table name from the technical help

Create Pricing procedure IMG copy the standard pricing procedure assignment ZVAA01 sales org. 1000

ZVAA02 sales org. 2000

Create Condition record pricing K020

PR00

MWST

NA00

Create Condition record output determination

RD03 cash sales

Create Checking group availability check

IMG SD basic function availability check and … availability check

Z1 plant 1000 / sales order and delivery

Z2 plant 2000 / sales order and delivery

May 2003 Page 53/127




billing schedule ZZ = 2. and 4. Friday/month

Process consignment IMG SD Picking LeanWM Define Movement Types = movement type 255 / warehouse number 100

Process consignment

account determination IMG SD basic function account assignment/costing assign G/L accounts Tbl. 001

MWS = 175000

ERL = 80000

ERS = 881001

Activate Lean-WM 1. IMG enterprise structure assignment logistics execution assign warehouse number to plant … =

1100-1101-100

1200-1201-100

2100-2101-100

2. IMG logistics execution shipping picking lean wm control plant/storage location/warehouse no. assignment

1100-1101-100-1-001

1200-1201-100-1-001

2100-2101-100-1-001

3. material create warehouse number 100

4 Problem log

Determined printer LP02 does not exist: Create printer LP02 with transaction SPAT (as copy from LP01).

Missing the assignment of a logical system to the client: We assigned the logical system ID3CLNT1## to every client in the master. Problem should be solved. However, if this problem should appear again, use transactions BD54 and SCC4 to create logical system ID3CLNT1## and assign it to

May 2003 Page 54/127



client 1##. (SCM-PL/MF should be able to do this or to help you.)

May 2003 Page 55/127



Unit: TSCM54 Procurement

1 Contents of Unit

Account groups

Material Types

Number ranges

Initialize period

Material groups

Account assignment (valuation control, valuation area, valuation classes, automatic postings etc.)

Terms of payment

Purchasing groups / MRP controller

Account assignment category / Field selection

Maybe movement type / Field selection

MRP

Procurement processes (Source determination, Purchase requisition, scheduling agreements, PO’s, GR, IV)

Transfer via Scheduling agreement (LU) without SD

Services

Optional: Sub-contracting

May 2003 Page 56/127










2.1 Prototype process 1: Integration with FIN- and PL-/MF-team

A multi-level MRP run for a finished product (bike) in production plant 1100 should create a purchase requisition for a raw material (Note: Without a planning team and without a manufacturing team, one raw material should be planned via reorder-point procedure). The PR-team is converting the purchase requisition to a PO, followed by GR and IV, where the invoice contains differences. FI continues.

To ensure this, MRP should be active. Furthermore they need a material master and a vendor master with necessary data (using relevant IMG settings). Account determination for bikes must fulfil the customer’s requirements.

Furthermore the PR-team is presenting, that a sales order in plant 1200 has generated transfer scheduling lines, which leads to demands in production plant 1100 (bikes or accessories). In that way the transfer to plant 1200 and the production of bikes in plant 1100 is triggered (for necessary preparations see process # 7). OF is just creating a sales order (probably during the preparation, not during the presentation).

2.2 Prototype process 5: Integration with FIN-team

Super Bike is ordering an external service (item category “services”) from a vendor in country 1, where the costs have to be posted to a special fairy trade CO-order (in company code 2000) and a consumption account for external services (maybe defaulted by the help of account assignment). The service has to be entered in a service-entry-sheet, which has to be released. The Invoice is in currency of country 1 (foreign currency) and has to be entered. The team is explaining to PO history. The FIN team continues.

To ensure this process, the vendor has to be maintained with the currency of country 1. They have to use a account assignment category for (PP/CO-) orders (maybe with field selection settings). A service master is useful. To have defaulted the right account (optional) they need to maintain automatic postings (account determination).

2.3 Prototype process 7: Integration with FIN-team (maybe OF)

By the help of a scheduling agreement (type LU), source determination and MRP (special procurement type for plant-to-plant transfer), the PR team has to

May 2003 Page 57/127



ensure the transfer from production plant 1100 to distribution plant 1200. Beginning with a demand in plant 1200 (customer order) and a MRP run, the system generates scheduling lines in plant 1200, which appears in plant 1100 as a demand to post a transfer from plant 1100 to plant 1200. The PR-team is posting a GI in plant 1100 (movement type 351) and a GR in plant 1200 (movement type 101).

Optional: Instead of a pure MM transfer process, they may have a SD delivery (without billing). In this case probably they need strong support by the instructors. You should refer to Online documentation for transfer postings (as tip for participants) and you should help them during customizing (the previous courses just mention the application shortly, but not the relevant customizing). Otherwise OF is just creating the sales order in plant 1200 (probably prepared before, not during the presentation.)

They have to present the results in FI and CO, especially that mountain bikes and street bikes uses different stock accounts. They compare the value of street bikes with the stock account value for street bike (it should be equal). In the same way they compare these values for mountain bikes.

Note: For the INT chart of accounts – in standard - the finished products and trading goods using the same stock account. If they don’t realize this, it may happen, that the two stock accounts for bikes got not only values for bikes but also values for accessories (in sum). In that case there is a difference between the stock account value and the stock values of the materials (the relevant bikes). The Bike managers may ask for the reason.

2.4 Prototype process 9: Integration with FIN-team

During the realization/preparation, MM has to ensure the account determination of the cleaning services account. The cleaning services valuation class should be determined by the help of the cleaning services material group (without material master). If using a material master for cleaning services the cleaning services valuation class must be assigned to the material master. Furthermore they have to create a new account assignment category and to set up the field selection for G/L account and cost centre (For both fields the Display option). Furthermore, they should ensure, that GR is not allowed for cleaning (via account assignment category settings). The cost centre is determined by a CO setting (assignment of cost centre to the G/L account). Maybe the field selection for PO transactions should declare the material group as mandatory.

During the presentation they create a PO item with the new account assignment category. It could be a PO item

Which is using a invoice plan or

Which is using a blanket item (category) or

Which is using just a normal item (category) – GR should not be possible!

They enter a material master for this cleaning service (or just a text and the right material group). The G/L account as well as the cost centre should be assigned automatically and should be displayed at the accounting detail screen of the PO item. (Note: If they use a blanket item, maybe the cost centre will not appear. Just leave the detail screen and open it again. Now you see the cost centre.) The team should be able to explain, how G/L account and cost centre are determined. MM is posting or showing the invoice.

May 2003 Page 58/127



The FIN-team compares the cost centre value before and after this process. Furthermore they distribute these costs per square area to real cost centres.

2.5 Prototype process 12: Integration with SD- and FIN-team

The PR team checks customer consignment stocks and related movements. Furthermore they are doing a physical inventory (based on counting results of the customer). Due to Business Blueprint Documents, movements should be blocked during the physical inventory. Probably during their preparation they have to check the field selection for the physically inventory movement type (to post the differences), where maybe FI has to correct the setting.

OF is posting deliveries, withdrawals and returns. FIN has to clear the physical-inventory differences account(s) against the customer (which has to pay for the loss of a bike).

May 2003 Page 59/127



3 Settings in R/3 System


May 2003 Page 60/127




Initialize Periods IMG: Logistics - General Material Master Basic Settings Maintain Company Codes for MM

Or

IMG: Logistics - General Material Master Tools Initialize Period

Set the period to the actual one.

This should be done at the very beginning before you create material masters! When a material masters is created once you cannot initialize the period via Maintain CC for MM. In this case you may use transaction MMPV (Close period) month for month.

As alternative, you may use Tools Initialize Period. But in case of existing material masters and especially with existing stocks you will erase these stocks!!!

Material types IMG: Logistics - General Material Master Basic Settings Material Types Define Attributes of Material Types

Set up the material types FERT, HIBE, HAWA, DIEN, ROH, HALB (or define your own as a copy from these).

Remind that Trading goods are called Accessories.

The flag External no. assignment w/o check must not be set. All material types should be checked against external intervals.

You need the purchasing view for finished products (FERT) to have transfer procurement to plant 1200 (and 2100). You have to allow external procurement.

You should keep the purchasing view for semi-finished products. You will need it for subcontracting (painted frames).

Suggestion: Start the descriptions for used material types with a special sign, for example an # (#Raw Material, #Finished Products, #Accessories/Trad.goods, etc.). This will collect all used material types at the beginning of the F4-List. So you can ease the life of your users.

May 2003 Page 61/127




Set up price control according to ASAP Blueprint Master Data. For material types, where the price control is given clearly, you may fix these settings.

Check quantity/value update flags for all used material types and plants.

Number ranges for materials

IMG: Logistics - General Material Master Basic Settings Material Types Define Number ranges for each material type

Set up a group for every of the used material types FERT, HIBE, HAWA, DIEN, ROH, HALB (or your own material types). Assign the given number ranges (see Master Data document) to the external intervals of the relevant groups. Assign the relevant material types to the groups (1:1).

Maybe use again the # sign as beginning of the group description.

Plant-specific screen selection

IMG: Logistics - General Material Master Field selection Define Plant-specific field selection and Plant-specific Screen selection

Maybe erase the work scheduling view (A) from plants 1200 and 2100.

It’s an optional setting, not really necessary.

Material Groups IMG: Logistics - General Material Master Settings for Key Fields Define Material Groups

Set up the given material groups (ASAP Blueprint Master data).

The material group for cleaning services is also used and needed for account determination (special account), where the valuation class should be determined by material groups.

May 2003 Page 62/127




Define Valuation Control

IMG: Materials management Valuation and Account Assignment Account determination Account Determination w/o wizard Define Valuation Control:

Activate Valuation grouping code

This is set by default, no activity needed.(Because we have the same accounting in all plants, it also works without Valuation grouping code. But using it, you are open for maybe later on new plants with a different account determination.)

Grouping valuation areas

IMG: Materials management Valuation and Account Assignment Account determination Account Determination w/o wizard Group together val. areas:

The plants 1100, 1200, 2100 must be assigned the same valuation grouping code, for example 0001.

If the plants are copied from plant 0001, this setting is copied from plant 0001 and all our plants are using val.grpg.code 0001. In this case here is no activity needed.

Define valuation classes

IMG: Materials management Valuation and Account Assignment Account determination Account Determination w/o wizard Define valuation classes:

Button [Valuation Class]

Val.class 3202 Cleaning services with acct.cat.ref. for services (0006)a new one (maybe copied from 3200)

Val.class 7920: change name to Mountain bikes and stay with acct.cat.ref. for finished products (0009)

Val.class 7921 Street bikes with acct.cat.ref. for fin.products (0009)a new one (maybe copied from 7920

Optional: maybe delete for some not used valuation classes the assignment of the Acct.cat.ref. (for example for val. 3001 etc.)

The new valuation class 3202 is needed for the special account determination for cleaning services (see prototype process #9).

For different stock accounts for mountain bike at one hand and street bikes at the other hand you need two different valuation classes for finished products. For example, use 7920 for mountain bikes (rename it) and create a new one 7921 for street bikes.

Additional, you may delete the assignment of account category reference for those valuation classes, which are not needed. In this way you avoid, that wrong valuation

May 2003 Page 63/127




classes are used.

Configure Automatic postings

IMG: Materials management Valuation and Account Assignment Account determination Account Determination w/o wizard Configure automatic posting:

Button [Account assignment]. Use chart of accounts INT.

BSX: 0001 – 3100 (Trading goods): Change stock account to another one (a new one or maybe 790000)

BSX: 0001 – 7920 (Mountain bikes): Check if the stock account for mountain bikes is used. If not, assign it.

BSX: 0001 – 7921 (Street bikes): Assign the stock account for street bikes.

GBB: 0001 – VBR – <empty val.class>: Assign 4*****

GBB: 0001 – VBR – 3200: Assign 417000 Purchased services

GBB: 0001 – VBR – 3202: Assign 417002 Purch. Serv. (Cleaning)

Check all transactions keys, which using valuation classes and create a new entry for the new valuation class 7921 and assign the same accounts as assigned to val.class 7920 (you should copy 7920 lines to 7921).

The default setting for account determination is using the same stock accounts for finished products and trading goods. That means, that probably stock values of accessories are mixed with stock values of mountain bikes or street bikes. So for accessories (trading goods) you need another stock account, but not the mountain bikes or street bikes accounts. Note: maybe the students will not change it. In that case they should realize that problem using the list of stock values, transaction MB5L (prototype process #7) . At least they should explain it, during their presentation.

For the bikes the customer Bike likes to have different stock accounts for mountain bikes and street bikes. That’s why, we have two different valuation classes. For the new one (probably 7921) you have to create new entries in all transaction event keys, which uses val.classes: different stock accounts, all other settings identical for both valuation classes (see prototype process #7).

May 2003 Page 64/127




For cleaning services we need a special account (CO assigning the right cost center to it) – prototype process #9.

Maybe, additional, you like to arrange a defaulted account for other services (except cleaning). You should use the purchased services account.

Note: Account 417000 works fine, however in standard settings the account 417001 got a special field selection, which may differ from account assignment category. That means additional settings for 417001. Suggestion: use 417000.

It could be a good idea to arrange the default 4***** as “account” for all procurement without a valuation class. Fine F4-use then.

Assign material group to valuation class (cleaning services)

IMG: Materials management Purchasing Material Master Entry Aids for Items w/o Material master

Assign the new valuation class for cleaning services (3202) to material group Cleaning Services.

This is needed for cleaning services account determination (and following CO assignment of cost center 1160 to account 417002). See prototype process #9.

Terms of payment (MM or SD)

IMG: Materials management Purchasing Vendor Master Define terms of Payment

Maintain the terms of payment ZT01, ZT02, ZT03 due to the rules given in ASAP Blueprint Master data. You should also use a default for baseline

This settings can also be done via a SD transaction and by SD people.

May 2003 Page 65/127




date, for example the posting date.

Purchasing groups IMG: Materials management Purchasing Create Purchasing Groups

Maintain the groups given in Organizational Structure Documents (especially the decision and maybe Introduction – The Bike International Company)

Descriptions could be:

Acc./Bikes 1000/1 (110)

Serv./Cons.1000/1 (120)

Raw mat. 1000/1 (130)

Acc./Bikes 2000 (210)

Serv./Cons.2000 (220)

Account Assignment Categories

IMG: Materials management Purchasing Account assignment Maintain Account Assignment Categories

Create or maintain the following categories:

Cleaning Services (a new one, use a free key – for example R)Create as copy from acct.assgnmt.cat. cost center (K) and set up the following:No GR (GR indicator is binding), Default IR flag (not binding), Field-selection option Display for Cost center and G/L account fields,Field-selection option for Unloading point and Goods recipients/ship to party fields may stay as Opt.entry or change it to Display.

Cost center (K)Change field-selection for Unloading point and Goods recipients/ship to party fields to Reqd.entry

Order (F)Field selection for CO/PP order field should be Reqd.entry,

The demand for cleaning services is: G/L account and cost center have to be determined automatically and must not changed by the user within the PO. To restrict the users in changing possibilities you need a new acct.assgnmt.cat. for cleaning services with the relevant field-selection (Display). To get the account 417002: see account determination. To get the cost center 1160 a CO setting is necessary (assignment of cost center to the G/L account).See prototype process #9 and relevant information in ASAP Blueprint Business scenarios.

Unloading point and Goods recipient is a required entry, except for cleaning services.

May 2003 Page 66/127




field selection for cost center field should be Hidden or Display.

Combination of Item Categories & Acct. Assignment categories

IMG: Materials management Purchasing Account assignment Define Combination of Item Categories/Account Assignment Categories

Create a new entry for standard procurement (blank item cat.) and your new acct.assgnmt.cat. for Cleaning services (maybe R).

The usage of the new acct.assgnmt.cat. for relevant item category/ies have to be defined.

Field selection for Purchase orders (ME21N)

IMG: Materials management Purchasing Purchase Order Define Screen Layout at Document Level

Check the settings for field selection key ME21N (transaction). Use field selections group Basic data, item, to setup the material group field to required.

Useful. But not really necessary.

Setup special procurement type

IMG: Materials management Consumption-Based Planning Plant Parameters Carry Out Overall Maintenance of Plant Parameters

Maintain the settings for plant 1200 (or create plant parameters, if they were not copied from plant 0001). Use [special procurement] button to setup the key 40 (or to define a new one):

Special procurement type description: Stock transfer (proc.from plant 1100)

Proc. Type F (External procurement)Special procurement U (stock transfer)Plant 1100 (delivery plant)

You may use type 40; enter the delivery plant and change the description.

You need such key to trigger the use of item category U and delivery plant 1100. MRP will create Purchase requisitions or schedule lines with item category U and delivery plant 1100 for materials with this special procurement type. That means, that you need a transfer scheduling agreement (LU) or you convert the purchase requisitions to transfer orders (UB).

Activate MRP in plants (MM or PP)

IMG: Materials management Consumption-Based Planning Planning Activate Material Requirements Planning

Material requirements planning: Set activate ... flag for the plants 1100, 1200 and 2100

Necessary for a multi-level or batch run. Not really necessary for a online single-item/single-level planning run.

Can be done alternately by PP (Planning

May 2003 Page 67/127




Set up planning file: Create a variant for every plant. Start job via Immediate or via Schedule job.

team or maybe manufacturing team).

Field selection for movement type, for example 70x W

IMG: Materials management Inventory Management and Physical Inventory Movement Types Copy, Change Movement Types

Select client (and maybe movement type) for the selection of the work area and enter your client (and maybe the movement type(s)) as work area.

In the dialog structure you are at the level movement type (see left). At the right navigate to movement type 70x and select this line.

Now navigate to the Field selection (from 201)/Batch search procedure level.Select the line for movement type 70x with special stock indicator W (consignment (cust.)). Go to the details for this line and again go to details of Materials management selection group. Set up the Customer to Required. (standard setting in MM).

Probably FI has to setup the field selection for customer field to optional entry.

For the physically inventory difference movement of customer consignment you need the customer field (Required entry in MM). However, the field selections of G/L accounts for the customer field should be set as optional entry (probably you use the same account for normal stocks).

If MM and FI got very different settings (for example required and suppressed) this causes an error message, when trying to post the difference. This error message gives you the possibility to run a report, which compares MM- and FI-settings and to access the relevant MM- and FI-customizing.

Note: There may occur similar problems for other movement types. Work in the same way.

Field selection for movement type, for example 643

(Example. However, movement type 643 is only relevant for

IMG: Materials management Inventory Management and Physical Inventory Movement Types Copy, Change Movement Types

Select client (and maybe movement type) for the selection of the work area and enter your client (and maybe movement type 643) as work area.

In the dialog structure you are at the level movement type (see left). At the

Bike is working w/o business areas. That’s why the field selections of G/L accounts will not allow entries for business units. However, movement type 643 allows a business area entry. This causes an error message, when trying to post a goods issue (will be done by

May 2003 Page 68/127




transf. postings from plant 1100 to plant 2100 via SD functionality incl. Billing)

right navigate to movement type 643 and select this line.

Now navigate to the Field selection (from 201)/Batch search procedure level.Select the line for movement type 643 w/o a special stock indicator. Go to the details for this line and again go to details of Additional Account assignments selection group. Set up the Business area to Suppress.

To have unique settings, you should also suppress the business area field for enjoy transaction(s): Navigate to the Field selection (Enjoy) level. Delete the line 643 - GSBER (this is the technical name of business area).

SD transactions).

Bike is not working with orders on hand (spec. stock indicator E). No need to change the field selection for orders on hand.

Note: There may occur similar problems for other movement types. Work in the same way.

4 Comments

Condition technique/Message Determination and import data are not covered during the basic courses. The participants probably will not be able to eliminate messages due message determination and import data.

When you post a GR for scheduling lines, normally only the quantity that is relevant for the current date is offered. Use the MIGO opportunity for personal settings (Settings Default values) to activate the Suggest all items flag. Now you get zero lines referring schedule lines with later dates. (Note: If the delivery is done by SD instead of MM your GR should refer to the outbound delivery instead of the scheduling agreement.)

Ordering a cleaning service with a normal PO item, the account assignment category for cleaning should deactivate the GR flag. Otherwise the IV will use the GR/IR clearing account instead the consumption account from PO item (however, posting a GR you get the consumption account).

May 2003 Page 69/127



5 Problem Log

This log results from Release 4.0, but it may also be helpful for Release 4.6.

Recognized Problem/Error What to Do

GOODS RECEIPT

Define tolerance limits for GR before this can be executed. IMG: Materials management Inventory management and Physical Inventory Goods Receipt Set Tolerance Limits

Define the tolerance key for each plant for which GR is to be performed.

Not able to search for the delivery number when creating GR for the delivery.

You have to know the delivery number and enter it manually in the field delivery when creating the GR for the cross-company stock transfer. The only way you can now enter a GR for delivery is by doing it from the Create GR for PO/PO number unknown screen. The possibility in earlier R/3 versions of creating a GR directly against the delivery number is no longer available.

Not able to make postings for movement type 561 while entering initial stock in the plants for finished goods. This is because, according to the exercise text, we need valuation classes for finished goods.

Enter the account assignments for movement type 561 and the new valuation class you have created.

IMG: MM Customizing Valuation and Account Assignment Account Determination Account Determination Without Wizard Define Account Grouping for Movement Types

SUBCONTRACTING/GOODS RECEIPT

Description for material not maintained in correct language for the subcontracting materials. This error message occurs when creating a purchase order.

Maintain the material master (material description) for the language for the country where your production plant is located.

May 2003 Page 70/127



Recognized Problem/Error What to DoINVOICE VERIFICATION

Posting keys missing for performing invoice verification. Must be maintained in table T169V.

Performed completely by the FI people.

Tax defaults not maintained for entering invoices to CC2000 and CC1000.

These defaults have to be maintained by FI/MM. This involves deciding which tax codes are to be used and entering them for CC2000 (and CC1000). In this case, tax code I1 was agreed upon with FI and entered.

IMG: Materials Management Invoice Verification......Logistics Invoice Verification Incoming Invoice Maintain Default Values for Tax Codes

The german tax indicator V1 uses 15%, however the text is saying 16%.

FI has to setup this tax indicator to 16%.

May 2003 Page 71/127



Unit: Setting up the Core Interface

1 Contents of Unit

This unit is only relevant if APO is part of the case-study.

The Unit Setting up the Core Interface contains the following topics:

Setting up the logical systems

Creation of ALE-Users

Creation of RFC-Destinations

Definiton of target-system and APO release

Creation of Business System Groups

Assigning Logical Systems and Queue types

Definition of publication

Creation of selection variants for integration models






May 2003 Page 72/127





If APO is part of the Case-Study the following 2 processes need these settings as a prerequisite:

Prototype process 1: Integration with PR and FIN

Prototype process 2: Integration with FIN

May 2003 Page 73/127



3 Settings in R/3 and APO


Settings R/3

Menu - Path

APO

Menu - Path

Comments

R/3 Setting up the Logical Systems

SPRO

Basis Components ALE Sending and Receiving Systems Logical Systems Define Logical System

Log.System:

ID3CLNT100

Name: ID3 client 100

SPRO

R/3 Basis Customizing ALE Sending and Receiving Systems Logical Systems Define Logical System

Log.System:

APOCLNT100

Name: APO client 100

R/3 Assign Client to Logical Systems

SPRO

Basis Components ALE Sending and Receiving Systems Logical Systems Assign Client to Logical Systems

Client 100

Logical System: ID3CLNT100

SPRO

R/3 Basis Customizing ALE Sending and Receiving Systems Logical Systems Assign Client to Logical Systems

Client 100

Logical System APOCLNT100

May 2003 Page 74/127



Settings R/3

Menu - Path

APO

Menu - Path

Comments

Create ALE-User Tools -> Administration -> - User maintenance -> Users

Username: USERADMIN

User-Type: Dialog

Profiles: SAP_ALL,

SAP_NEW

Initial password: INIT

Tools -> Administration -> - User maintenance -> Users Username: USERADMIN

User-Type: Dialog

Profiles: SAP_ALL,

SAP_NEW

Initial password: INIT

Maintain RFC-Destinations Logistics Central Functions SCP Interface Core Interface APO Settings RFC Destinations

Create an new R/3 connection:

APOCLNT100

Connection type: “3”

Target host : Name of the Server

System number :

R/3 Basis Customizing -> ALE -> Sending and Receiving Systems Systems in Network -> Define Target Systems for RFC-Calls

Create an new R/3 connection:

ID3CLNT100

Connection type: “3”

Target host : Name of the Server

Name of the target host and the system number will be provided by the system

May 2003 Page 75/127



Settings R/3

Menu - Path

APO

Menu - Path

Comments

Description:

R/3 Client 100 -> APO Client 100

Logon:

Language “ “

Client 100

User: USERADMIN

Password: “INIT”

System number :

Description:

APO Client 100 -> R/3 Client 100

Logon:

Language “ “

Client 100

User: USERADMIN

Password: “INIT”

administration and the trainer should maintain it in the solution-client.

The target host and the system is also shown in the SAPLogon

Define Target System Logistics Central Functions SCP Interface

Core Interface APO Settings Target Systems

Logical System: APOCLNT100

Queue Type:

Outbound Queue

May 2003 Page 76/127



Settings R/3

Menu - Path

APO

Menu - Path

Comments

Define APO Releases Logistics Central Functions SCP Interface

Core Interface APO Settings APO Releases

Logical System: APOCLNT100

Syst.type:

SAP_APO:

Release 30A

The current APO-Release of the IDES Master-System has to be checked by the trainer.

Maintain Business System Group

SPRO

APO Basis Settings Integration Business System Group -> Maintain Business System Group

BusSystGrp:

BSG I

Description:Business system group I

May 2003 Page 77/127



Settings R/3

Menu - Path

APO

Menu - Path

Comments

BSG II Business system group II

Assign Logical System and Queue Type

APO Basis Settings Integration Business System Group Assign Logical System And Queue Type

BusSystgrp:

BSG I

LogSystem: APOCLNT100

R/3 Flag : “ “

SAP Rel.: (current APO-Release)

Queue Type:

Outbound Queue

BusSystgrp:

BSG I

LogSystem: ID3CLNT100

R/3 Flag : “X“

SAP Rel.: (current R/3

May 2003 Page 78/127



Settings R/3

Menu - Path

APO

Menu - Path

Comments

Release)

Queue Type:

Outbound Queue

Define Publication APO Basis Settings Integration Publication Generate and Delete Distribution Definition

Publication type:

21 External procurement

31 In-house production

51 Planned independent requirements

53 Sales order

340 Delivery

360 Reservation

Location number: 1100

Location Type: 1001

Has to be done after transferring plants

May 2003 Page 79/127



Settings R/3

Menu - Path

APO

Menu - Path

Comments

Logical system: ID3CLNT100

Create Modell and Version 000

Master Data Planning Version Management Model and Version Management

Create a modell 000

For modell 000 create a version 000 containing the following settings:

PP/DS : Change planning active

PP/DS: Automatic planning active

PP/DS: Standard Production Horizon 100 days

The modell 000 and version 000 have to be created befor transfering data from R/3.

R/3 Create selection variants for the generation of

Logistics Central Functions SCP Interface Core

The integration models have to be activated one after the

May 2003 Page 80/127



Settings R/3

Menu - Path

APO

Menu - Path

Comments

integration models Interface APO Intergration Integration Model Generate Create

Model Name : T_BIKE

Logical System : APOCLNT100

APO Application : MD I

√ Materials

√ Plants

√ Customers

√ Vendors

√ Workcenters

Save as Variant:

Variant Name : T_BIKEMDI:

Short descripton: Bike International MDI

Model Name : T_BIKE

other i.e. first MDI, second MDII and at last TD. Not all of them at a time.

In order to restrict CIF from creating multi-mixed ressources the Project “APORES01” has to be deactivated in the transaction CMOD in APO.

May 2003 Page 81/127



Settings R/3

Menu - Path

APO

Menu - Path

Comments


APO Application : MD II

√ PPM

Variant Name : T_BIKEMDII:

Short descripton: Bike International MDII

Model Name : T_BIKE


APO Application : TD

√ Materials

√ Plants

√ Storage Loc.Stk

√ Sales Ord Stock

May 2003 Page 82/127



Settings R/3

Menu - Path

APO

Menu - Path

Comments

√ Cust.Spec.Stk

√ Transit Stock

√ Vend.Spec.Stk

√ Sales Orders

√ Planned orders

√ Pos and Preqs

√ Plan Ind. Reqs

√ Prod.Order

√ Manual Reserv.

Variant Name : T_BIKETD:

Short descripton: Bike International TD

May 2003 Page 83/127



Unit: TSCM24 Planning

1 Contents of Unit

The Unit TSCM24 Planning contains the following topics:

Setting up strategy profiles

Setting up heuristic profiles

Maintaining the global settings

Creation of alert profiles

All these settings are APO-settings.








May 2003 Page 84/127



2.1 Prototype process 1: Integration with PR and FIN

Based on planned independent requirements that have been created in R/3 a (manual) multi-level MRP run for a finished product (bike) in plant 1100 should create a planned order and a purchase requisition for a component (e.g. break-system ) in APO. This can either be achieved by using the product-heuristic SAP_PP_02 in the product view for every product (i.e. first the finished product and after that the component) or by running the planning-heuristic SAP_MRP_001 (the heuristic plans both products).

The PR-team has to convert the purchase requisition to a PO, followed by GR and IV (in case of differences). FI continues.

After checking the alerts in PP/DS and the receipt elements in the product view, the planned orders for the finished product have to be converted in APO into production orders.

3 Settings in APO


Settings APO - Menu Path Comments

Create a strategy profile for integration to R/3

APO SCP PPDS Global settings Maintain Strategy Profile

Create a new Profile:

R3INT : R/3 Integration

Create and activate a new strategy

1:

Scheduling mode:

It is recommended to use this strategy in order to schedule the orders coming from R/3 without capacity constraints. Otherwise the Interface between R/3 and APO can get locked because of repeating the transfer from R/3 to APO an vice versa.

May 2003 Page 85/127




Infinite Scheduling

Planning direction

Backwards + Reverse

Desired Date: current date

Validity of orders: 0

Scheduling Submode: Schedule dependent operations according to scheduling mode

Relationships: always consider

Compact scheduling: No

Consider maximum intervalls: “X”

Fixed pegging: do not consider

Dynamic pegging: do not consider

Assign the Strategy to the global settings

APO SCP PPDS Global settings-Maintain Global Parameters and Defaults

Log Level: Detailed (additional information)

Schedule orders: strategy profiles:

R/3 Integration: R3INT

Create Heuristic Profile APO SCP PPDS Heuristics Maintain Heuristic Profile

Heuristic Profile: CS_MRP

The heuristic profile can be assigned to the user-settings in the product view.

May 2003 Page 86/127




Heuristic:

SAP_PP_02

SAP_MRP_001

After doing that, the path to the selection of a heuristic in the product view ( Interactive planning –> heuristics )

shows the 2 heuristics of our profile.

By running the heuristic SAP_MRP_001 it is possible to start interactively a multilevel planning.

Maintain Alert Profile Supply Chain Montoring Current Settings Set Alert Monitor

Maintain Profile Shift+F1

Name: CS_PPDS_PL Description: PPDS Alerts for Case Study (planning)

Assign to Appl PP/DS

Due date violation (dynamic pegging)

Receipt date too early(dynamic pegging)

Order creates overcoverage

Order creates undercoverage

The profiles are relevant in the product view or in the alert-monitor.

As an option it is also possible to use the alert-monitor by defining different settings containing the defined profile.

May 2003 Page 87/127




Product Selection:

Variant CS 1:

Products:

A list of finished products

Location Selection

Variant CS 2:

Location: 1100


May 2003 Page 88/127



Unit: TSCM34 Manufacturing

1 Contents of Unit

The Unit TSCM34 Manufacturing is divided in two parts and contains the following topics:

1) Manufacturing in R/3

R/3 Settings (discrete)

Changing order-Type dependent parameters

Defining selection profiles

Defining production scheduling profiles

Defining checking control for availability check

Defining scheduling parameters

Defining confirmation parameters

Defining print control

R/3 Settings (repetitive)

Changing repetitve manufacturing profile

Maintain entry parameters

May 2003 Page 89/127



2) Conversion of planned orders in APO and manufacturing in R/3

3) R/3 Settings (discrete)

Changing order-Type dependent parameters

Defining selection profiles

Defining production scheduling profiles

Defining checking control for availability check

Defining scheduling parameters

Defining confirmation parameters

Defining print control

R/3 Settings (repetitive)


Maintain entry parameters

APO Settings (discrete and repetitive)

Setting up strategy profiles

May 2003 Page 90/127



Setting up heurstic profiles

Maintaining the global settings

Creation of alert profiles

Setting up the layout of the product planning table

May 2003 Page 91/127










2.1 Prototype process 1: Integration with PR and FIN

1) Manufacturing in R/3

Based on planned independent requirements a planning run in R/3 for a finished product (bike) in plant 1100 should create a planned order and a purchase requisition for a component (e.g. break-system ). In case of repetitive manufacturing (e.g. gearshift) the planning run should create planned orders of type PE (run schedule quantity).


After checking the results of the planning run in the stock requirements list the planned orders for the finished product have to be converted in APO into production orders.

2) Conversion of planned orders in APO and manufacturing in R/3

Based on planned independent requirements that have been created in R/3 (manual) a multi-level MRP run for a finished product (bike) in plant 1100 should

May 2003 Page 92/127



create a planned order, dependent demands and a purchase requisition for a component (e.g. break-system ) in APO. This can either be achieved by using the product-heuristic SAP_PP_02 in the product view for every product (i.e. first the finished product and after that the component) or by running the planning-heuristic SAP_MRP_001 (the heuristic plans both products).

Based on the planned orders ( run schedule quantity) created in APO the repetitive manufacturing process can be done in R/3.


After checking the alerts in PP/DS and the receipt elements in the product view, the planned orders for the finished product have to be converted in APO into a production order.

2.2 Prototype process 2: Integration with FIN

The converted production orders will automatically be released. In case of availability problems the planner is able to decide how to proceed with the release. After the release the production order will automatically be printed. The MF – team checks the papers for the order and the goods-movements.

The MF-team checks the current situation on a certain resource in oder to see the current work-load.

After the the confirmation the team members have to show how the inventory of the finished products and the components have changed. They should also check if there are any capacity requirements or open reservations. In case of missing components the purchase requisitions should be transferred into purchase orders, this has to be done by the PR-Team.

FI continues.

May 2003 Page 93/127



3 Settings in R/3 and APO


3.1 Manufacturing in R/3


Change order type-dependent parameters

SPRO

Production SFC Master Data Order -> Define order type-dependent parameters

Plant : 1100

Order type: PP01

Documentation of goods movements:

GR for prod. Order

GI planned

GI unplanned

May 2003 Page 94/127




Define selection profiles SPRO

Production SFC Master Data Order -> Define selection profiles

Selection profile: Y000001

Selection conditions: REL and not CNF

The selection profile is necessary for the selection of relevant orders in LIS.

Define production scheduling profile

SPRO

Producton SFC Master Data Define production scheduling profile

Plant: 1100

Profile: CS0001

Automatic actions:

On release: Execute printing

(see informations “print-control)

APO

In case of triggering the conversion from planned orders into production orders in APO, the

Define Checking control for Availability Check

SPRO

Production SFC Operations Availability Check Define Checking control

May 2003 Page 95/127




Plant : 1100

Order-type: PP01

Business function

1 order creation

Material availability

Checking rule: PP

Type: ATP check

Collect.conversion : 2

PRT availability

No check

Capacity availability

No check

2 order release


Checking rule: PP

Type: ATP check


May 2003 Page 96/127




PRT availability

No check


Overall profile SAPSFCG013

Rel.capacities: 1

Specify scheduling parameters SPRO

Production SFC Operations Scheduling Define Scheduling Parameters for Production Orders

Plant : 1100

Order type: PP01

ProdScheduler: *

Detailed scheduling: Generate capacity reqs.

Scheduling type: Backwards

Confirmation SPRO

Production SFC Operations Confirmation Confirmation Parameters for Collective Confirmation/Fast Entry

Collective entry / Time Ticket

May 2003 Page 97/127




Proposal quantities:

Qtys. Immediatley

Proposal services:

Activites imm.

Identification:

Order/Sequence/opert

SPRO

Production SFC Operations Confirmation Single screen entry Define Parameters for Single screen entry

Confirmation Profile: SAP001 as standard profile

Header area: Order/sequence/operation

Confirmation type:

Autom. Final confirmation Post open reservations

May 2003 Page 98/127




Default Value

Quants: immediate prop.

Services: immediate prop.

Services to be displayed:

Setup

Machine

Labor

Print control IMG PROD SFC Operations Define Print Control

Spool parameters for users

Generic for all users in Plant 1100

The following list will be printed:

LGO01 Object list

LV02 Confirmation slip

LK01 Pick list

LK02 Goods issue slip

In case of printing problems with the standard settings choose one of the following settings:

1) Flow control should be “background” so the printing will not be started immediatley.

or

2) Assign the form “PSFC_STD_LAYOUT” to the list LG01


SPROProduction -> REM -> Control Data -> Define Repetitive Manufacturing Profiles

Planned order reduction:

Reduction period = 10 days

Maintain entry parameters SPRO Selection Period = 50

May 2003 Page 99/127




Production -> REM -> Planning -> Planning table -> Maintain Entry parameters

Scheduling level = Detailed planning

Capacity planning = X

May 2003 Page 100/127



3.2 Conversion of planned orders in APO and manufacturing in R/3.

R/3 settings


Change order type-dependent parameters

SPRO

Production SFC Master Data Order -> Define order type-dependent parameters

Plant : 1100

Order type: PP01

Documentation of goods movements:

GR for prod. Order

GI planned

GI unplanned

May 2003 Page 101/127




Define selection profiles SPRO

Production SFC Master Data Order -> Define selection profiles

Selection profile: Y000001

Selection conditions: REL and not CNF

The selection profile is necessary for the selection of relevant orders in LIS.

Define production scheduling profile

SPRO

Producton SFC Master Data Define production scheduling profile

Plant: 1100

Profile: CS0001

Automatic actions:

On creation: Release

On release: Execute printing

(see informations “print-control)

Define Checking control for Availability Check

SPRO

Production SFC Operations Availability Check Define Checking control

May 2003 Page 102/127




Plant : 1100

Order-type: PP01

Business function

1 order creation


No check

PRT availability

No check


No check

2 order release


Checking rule: PP

Type: ATP check


May 2003 Page 103/127




PRT availability

No check


No check

Specify scheduling parameters SPRO

Production SFC Operations Scheduling Define Scheduling Parameters for Production Orders

Plant : 1100

Order type: PP01

ProdScheduler: *

Detailed scheduling: Generate capacity reqs.

Scheduling type: Backwards

Confirmation SPRO

Production SFC Operations Confirmation Confirmation Parameters for Collective Confirmation/Fast Entry

Collective entry / Time Ticket

May 2003 Page 104/127




Proposal quantities:

Qtys. Immediatley

Proposal services:

Activites imm.

Identification:

Order/Sequence/opert

SPRO

Production SFC Operations Confirmation Single screen entry Define Parameters for Single screen entry

Confirmation Profile: SAP001 as standard profile

Header area: Order/sequence/operation

Confirmation type:

Autom. Final confirmation Post open reservations

May 2003 Page 105/127




Default Value

Quants: immediate prop.

Services: immediate prop.

Services to be displayed:

Setup

Machine

Labor

Print control IMG PROD SFC Operations Define Print Control

Spool parameters for users

Genric for all users in Plant 1100

The following list will be printed:

LGO01 Object list

LV02 Confirmation slip

LK01 Pick list

LK02 Goods issue slip

In case of printing problems with the standard settings and as a result possible CIF queue entries choose one of the following settings:

1) Flow control should be “background” so the printing will not be started immediatley.

or

2) Assign the form “PSFC_STD_LAYOUT” to the list LG01

May 2003 Page 106/127



APO settings


Setting up a strategy profile for integration to R/3

APO SCP PPDS Global settings Maintain Strategy Profile

Create a new Profile:

R3INT : R/3 Integration

Create and activate a new strategy

1:

Scheduling mode:

Infinite Scheduling

Planning direction

Backwards + Reverse

Desired Date: current date

Validity of orders: 0

Scheduling Submode: Schedule dependent operations according to scheduling mode

Relationships: always consider

Compact scheduling: No

It is recommended to use this strategy in order to schedule the orders coming from R/3 without capacity constraints. Otherwise the Interface between R/3 and APO can get locked because of repeating the transfer from R/3 to APO an vice versa.

May 2003 Page 107/127




Consider maximum intervalls: “X”

Fixed pegging: do not consider

Dynamic pegging: do not consider

Assigning the Strategy to the global settings

APO SCP PPDS Global settings-Maintain Global Parameters and Defaults

Log Level: Detailed (additional information)

Schedule orders: strategy profiles:

R/3 Integration: R3INT

Create Heuristic Profile APO SCP PPDS Heuristics Maintain Heuristic Profile

Heuristic Profile: CS_MRP

Heuristic:

SAP_PP_02

SAP_MRP_001

The heuristic profile can be assigned to the user-settings in the product view.

After doing that the path to the selection of a heuristic ( Interactive planning –heuristics )

shows the 2 heuristics of our profile.

By running the heuristic SAP_MRP_001 it is possible to start interactively a multilevel planning.

Maintain Alert Profile Supply Chain Montoring Current Settings Set Alert Monitor

The profiles are relevant in the product view or in the alert-monitor.

May 2003 Page 108/127




Maintain Profile Shift+F1

Name: CS_PPDS_EX Description: PPDS Alerts for Case Study (execution)


Alerts:

Receipt date in the past

Start date in the past

Confirmation date (operation) in the past

Order creates overcoverage

Order has undercoverage

Order not scheduled

Product Selection:

Variant CS 1:

Products:

A list of finished products

Location Selection

Variant CS 2:

Location: 1100


As an option it is also possible to use the alert-monitor by defining different settings and using one of the defined profiles.

May 2003 Page 109/127




Repetitive Manufacturing For repetitive manufacturing in APO the same additional settings as in R/3 cannot be made.

Based on the skills of the participants the trainer should decide if some special requirements need to be customized.

The initial view in the planning table should be SAP_REM.

May 2003 Page 110/127



Unit: THR14 Management / Administration

1 Contents of Unit

Personnel administration

Personnel Time Management

Payroll

Transfer of payroll results to FI/CO








2.1 Business Process 3: Personell Action and Payroll Accounting for Employees in Administration with Transfer to FI and CO (HR, FI/CO)

Students should implement their national payroll and then always use the MOLGA of the country concerned. Students will only use International Payroll with MOLGA 99 if the training system does not contain a country version for their country.

For reasons of simplicity, this document describes the international scenario with reference to the International IMG chapters. The structure of country-specific IMGs is very similar to the international one. Check whether this applies to your country or whether you need to carry out any additional steps to set up master data and execute the payroll run. Please also check the personnel master sheets. They may contain data that it is not legal to store in your country, or essential data may be missing for your country.

Customizing of HR-FI/CO interface is not discussed in the Academy.

May 2003 Page 111/127



Students are therefore dependent on help from the instructor. If a group is using chart of account INT, there is no need to change any settings for the interface. HR students have to consult with FI students to find out what chart of account is in use. Check symbolic accounts and make changes when needed. Check assignment of symbolic accounts to G/L sheet account Work together with FI group.

Students should show the Action Legacy data transfer with a short description of necessary infotypes, including important fields and customizing. After that they should show a list of all employees with Organizational Assignment (Cost Center), Salary and Work Schedule

2.2 Business Process 11: Time Management

a) Die Datenübernahme soll an dieser Stelle nicht gezeigt werden. Es sollen lediglich mindestens 3 PerNr mit den 3 unterschiedlichen AZP angelegt sein.

b) Gemeint ist hier: persönlichen Arbeitszeitplan über Report: RPTPSH10Daran erklären: Feiertagsklasse, Tagestyp, Feiertagskalender, Arbeitspausenplan, Tagesarbeitsplan, Sollstunden.

c) Es soll die Erfassung des Urlaubs und die Abtragung von einem eingerichteten Kontingent gezeigt werden. Zusätzlich soll die geforderte Kollision „Krankheitssatz mit Urlaubssatz in der IT-Pflege demonstriert werden. (Bei Fehlern kann die Abw.Art in der Tabelle T554S gepflegt werden. Die Zeitbindungsklassen sind schon richtig eingerichtet, und müssen nur noch in der T554S zugewiesen werden.)

d) Die Urlaubskontingente sollen für alle MA für nächstes Jahr aufgebaut werden. Die Demonstration soll über den Report RPTQTA00 erfolgen. (Fehlerursache sind häufig die Gruppierungen die in der Tabelle V_T503_ALL bzw. V_001P_ALL zu beheben sind. Seit 4.7 kann zur Fehlersuche auch der Report RPTQUOTA_CHECK eingesetzt werden.)

e) Der TMW soll den TN keinen zusätzlichen Customizingaufwand abverlangen.Sie können das Profil: SAP_XX_TIME_ADMIN mit den Kurzbezeichnungen: SET_DE / 002 verwenden. Die PNr können über eine vorbereitete interaktive Selektion schon in der MA-Liste aufgenommen sein.Es sollen die Kalendersichten (neu zu 4.7) gezeigt werden. Falls möglich sollten die TN auch eine Abwesenheit über Kurzbezeichnungen erfassen.

.

3 Settings in R/3 System


May 2003 Page 112/127



Settings Solution - IMG – Menu Path Comments

Set active/integration plan version

IMG: Personnel Management / Global Settings in Personnel Management / Plan Version Maintenance / ...

PLOGI PLOGI 01

Integration between organizational management and personnel administration

IMG: Personnel Management / Organizational Management / Integration / Integration with Personnel Administration / Set Up Integration with Personnel Administration

Feature PLOGI: set up integration for all EE’s

PLOGI ORGA X

Organizational structure, including positions

Human Resources / Organizational Management / Organizational Plan / Organization and Staffing / Create

Create objects and relationships with starting date of January 1.

External personnel number assignment

IMG: Personnel Management / Personnel Administration / Basic Settings / Maintain number range intervals for personnel numbers

... Determine defaults for number ranges

Use standard number range 01 (contains 0 – 9999)

Feature NUMKR: number range 01 for all EEs(standard)

Payroll area and control record

IMG: Personnel Management / Personnel Administration / Organizational Data / Organizational Assignment / ...... Create payroll area

... Check default payroll area

... Create control record

Create payroll area 01 for all employees.

Feature ABKRS: 01 for all employees.

Administrators IMG: Personnel Management / Personnel Administration / Organizational Data / Organizational Assignment / ...... Define administrator groups

... Define administrator

Feature PINCH

Create administrators according

May 2003 Page 113/127




to master data sheets

Periods of notice and continued pay

IMG: Personnel Management / Personnel Administration / Contractual and Corporate Agreements / Contract Elements / ...... Determine periods of notice

... Determine default contract elements

Create 6 weeks/quarter (standard: 05) and 4 weeks/month's end

Feature CONTR: set up default values for each employee subgroup

ESG collective agreement provision

IMG: Personnel Management / Personnel Administration / Payroll Data / Basic Pay / Define EE subgroup grouping for PCR and coll. agrmt. prov.

ESG for CAP:

Pay scale employees: 3

Non pay scale employees: 4

ESG for PCR: 3 for both ESG

Pay scale type IMG: Personnel Management / Personnel Administration / Payroll Data / Basic Pay / Check pay scale type

Create pay scale types:

Country 1 (standard)

Service sector

Management

Pay scale area IMG: Personnel Management / Personnel Administration / Payroll Data / Basic Pay /Check pay scale area

Create pay scale area for country 1

Default for pay scale data

IMG: Personnel Management / Personnel Administration / Payroll Data / Basic Pay /Determine default for pay scale data

Feature TARIF: default values dependent on personnel employee subgroups and personnel subareas

Pay scale groups and levels

IMG: Personnel Management / Personnel Administration / Payroll Data / Basic Pay / Revise pay scale groups and levels

See tables in case study materials for country 1 and

May 2003 Page 114/127




service sector

For management (non pay scale employees), create one pay scale group without amount

Working hours fixed by collective agreement

IMG: Personnel Management / Personnel Administration / Payroll Data / Basic Pay / Specify working hours fixed by collective agreement

Country 1: 45 hours , 6 daysService sector: 24 hours, 6 daysManagement: 37 hours, 5 days

Pay scale reclassification

IMG: Personnel Management / Personnel Administration / Payroll Data / Basic Pay / Pay Scale Reclassification / Check pay scale reclassification based on master data

For country 1 and service sector

Wage types for basic pay

IMG: Personnel Management / Personnel Administration / Payroll Data / Basic Pay / Wage types / Create wage type catalog

Wage types for basic pay: Monthly salary Contractual salary (management)Performance bonusCopy appropriate model wage types

Entry permissibility of wage types

IMG: Personnel Management / Personnel Administration / Payroll Data / Basic Pay / Wage Types /... Employee subgroups for primary wage type ... Define wage type permissibility per PS and ESG

Monthly salary only for pay scale employees, contractual salary only for management

Default wage types IMG: Personnel Management / Personnel Administration / Payroll Data / Basic Pay / Wage Types /... Enterprise structure for wage type model... Revise default wage types

Feature LGMST: default wage type model dependent on employee subgroup;Two wage type models: pay scale employees and management

Indirect valuation of IMG: Personnel Management / Personnel Administration / Payroll Data / Basic Pay / Wage Monthly salary

May 2003 Page 115/127




wage types using TARIF

types / Check wage type catalog / Check wage type characteristics

Indirect valuation of wage types using PRZNT

IMG: Personnel Management / Personnel Administration / Payroll Data / Basic Pay / Wage types / Define valuation of base wage types

Performance bonus

Personnel action for legacy data transfer

IMG: Personnel Management / Personnel Administration / Customize Procedures / Actions / ...... Define infogroups

... Set up personnel actions

... Create reasons for personnel actions

... Change action menu

Create infogroup with infotypes 0002, 0001, 0006, 0007, 0008, 0009, 0016, 2006 + county specific infotypes

Create action using own infogroup

Reason ‘blank’ (at least)

Insert action in action menu

Default values for infotype 0021 (Dynamic action)

IMG: Personnel Management / Personnel Administration / Customize Procedures / Dynamic Actions

Check whether a dynamic action already exits that creates a record of infotype 0021 (with subtype ‘child’ or ‘spouse’) when entering data in infotype 0002. If not, create a dynamic action using a suitable template.

SAP query, ad hoc query

IMG: Personnel Management / Human Resources Information System / HR Settings for SAP Query / Maintain Functional Areas

Create functional area with all relevant infotypes (at least 0001,

May 2003 Page 116/127




0002, 0007, 0008)

Create user group, passing user and functional area to user group

SAP query, ad hoc query

Human Resources / Information System / Reporting Tools / ..... .....SAP query.....Ad hoc query

Create SAP Query or Ad Hoc Query to meet requirements of the process a)

Holiday calendar IMG: Personnel Time Management / Work Schedules / Define Public Holiday Classes Check holiday calendar for country 1, perhaps create your own;

Define October 1 (holiday class between 3 and 9) and day before Easter as holidays (holiday class 1)

(You could also assign holiday class 1 or blank for October 1, but then you would have do define the day as special day)

Personnel subarea groupings

IMG: Personnel Time Management / Work Schedules / Personnel Subarea Groupings Use 01 for Star City, 02 for Call Center

Work schedules Since there are no people hired for Call Center in the Case Study, there is no need to create work schedules for Call Center. However, you should do this if you have time in order to see the

May 2003 Page 117/127




effect of groupings.

Daily work schedules IMG: Personnel Time Management / Work Schedules / Daily Work Schedules.. Define break schedules for management and pay scale employees in Star City and in Call Center

Define daily work schedules for management and pay scale employees in Star City and in Call Center

Don’t forget days off (OFF), work with variants.

Period work schedules IMG: Personnel Time Management / Work Schedules / Period Work Schedules ... Define period work schedules for:

Management in Star City (1 week)

Management in Call Center

Pay scale employees in Star City (1 week)

Pay scale employees in Call Center (3 weeks)

Day types IMG: Personnel Time Management / Work Schedules / Day Types / Define Selection Rules Create two selection rules: 01 – pay scale employees

May 2003 Page 118/127




(October 1 – day type 1)

02 – management(October 1 – day type 0)

Day types IMG: Personnel Time Management / Work Schedules / Day Types / Define Special Days If October 1 has holiday class blank or 1, define this day as a special day. For selection rule 01, this day has to be day type 1

Work schedule rules and work schedules

IMG: Personnel Time Management / Work Schedules / Work Schedule Rules and Work Schedules / Define Employee Subgroup Groupings

Set ESG for work schedules:

Pay scale employees: 1

Management: 2


IMG: Personnel Time Management / Work Schedules / Work Schedule Rules and Work Schedules / Define Groupings for the Public Holiday Calendar

Assign your public holiday calendar to your personnel subareas


IMG: Personnel Time Management / Work Schedules / Work Schedule Rules and Work Schedules / Set Work Schedule Rules and Work Schedules

Create following work schedule rules:

Pay scale employees in Star City

Pay scale employees in Call Center

Management in Star City

Management in Call Center

Generate monthly work schedules for the current year

May 2003 Page 119/127





IMG: Personnel Time Management / Work Schedules / Work Schedule Rules and Work Schedules / Generate Work Schedules ....

...manually

...in batch

Generate work schedules for the current year manually or in batch.

Make sure you have them created at least one month before hiring date of employees.

Default value for work schedule

IMG: Personnel Time Management / Work Schedules / Planned Working Time ... Feature SCHKZ: default values dependent on personnel subarea and employee subgroup

Absences IMG: Personnel Time Management / Time Data Recording and Administration / Absences / Absence Catalog / Define Absence Types.

There are different absences for management and pay scale employees. However, with the proposed enterprise structure, it is not possible to make this distinction, because there is only a PSG (not an ESG) for absences and attendances

Create absences:

Sick (management)Child sick (management)Vacation (management + (pay scale employees)Education (management)Sick without certificate (pay scale employees)Sick with certificate (pay scale employees)

May 2003 Page 120/127




Take care to observe the maximum duration indicated in the materials.

Absences IMG: Personnel Time Management / Time Data Recording and Administration / Absences / Absence Catalog / Determine Entry Screens and Time Constraint Classes

Absence counting IMG: Personnel Time Management / Time Data Recording and Administration / Absences / Absence Catalog / Absence Counting / Define Counting Classes for the Period Work Schedule

Absence counting IMG: Personnel Time Management / Time Data Recording and Administration / Absences / Absence Catalog / Absence Counting / Define Counting Classes for the Period Work Schedule

Absence counting IMG: Personnel Time Management / Time Data Recording and Administration / Absences / Absence Catalog / Absence Counting /Rules for Absence Counting (New)....

....Group Employee Subgroups for Time Quotas

.... Group Personnel Subareas for Time Quotas

.... Define Counting Rules

Define ESG for time quotas:1: pay scale employees2: management

01 for all personnel subareas

Absence quotas IMG: Personnel Time Management / Time Data Recording and Administration / Managing Time Accounts Using Attendance/Absence Quotas / ...

Store leave entitlement in infotype 2006, as taught in course. Do not use infotype 0005!

May 2003 Page 121/127




... Time Quota Types / ...

... Calculating Absence Quota Entitlements / ...

... Quota Deduction Using Attendances/Absences / ...

Create quotas for

Pay scale employees:(ESG for time quotas 1)LeaveChild sick

Management:(ESG for time quotas 2)LeaveEducation

Use appropriate templates (e.g. 03, 04 and 10).

Set up default values according to case study materials.Important: go through all steps.

Absence valuation

“All employees receive 20.00 per day if they are on vacation.”

Since absence valuation is not taught in the course, students have to find out on their own how this can be set up automatically, e.g. by reading IMG notes or asking the instructor. If there is no time to do so, students should set up a

May 2003 Page 122/127




wage type for entering leave allowance manually via infotype 2010. In the latter case, skip all steps marked as “Absence valuation”. Instead, perform steps “Vacation allowance via infotype 2010”.

Absence valuation:

Absence valuation rule for vacation

IMG: Payroll / Payroll: International / Absences /...

... Describe Absence Valuation Rules

... Group Absences for Absence Valuation

Use absence valuation rule 01

Assign vacation

Absence valuation:

Grouping for absence valuation

IMG: Payroll / Payroll: International / Absences / Define Grouping for Absence Valuation Check PCR XMOD, (MODIF A); use 01 (standard)

Absence valuation: Day rules

IMG: Payroll / Payroll: International / Absences / Define Day Rules Define day rule for work days

(Not necessarily needed)

Absence valuation: Counting classes

IMG: Payroll / Payroll: International / Absences / Valuation of Absences / Create Counting Classes for Absence Valuation

Use counting class 01 (standard) for valuation rule l 01

Absence valuation: Wage type "Vacation allowance"

oralternatively:

IMG: Payroll / Payroll: International / Absences / Create wage type catalog Set up wage type "Vacation allowance"

May 2003 Page 123/127




Vacation allowance via infotype 2010

IMG: Personnel Management / Personnel Administration / Payroll Data / Employee Remuneration Information / Wage Types / Create wage type catalog

IMG: Personnel Management / Personnel Administration / Payroll Data / Employee Remuneration Information / Wage Types / Check wage type catalog

Absence valuation:

Generate wage type

IMG: Payroll / Payroll: International / Absences / Valuation of absences / Valuate Absences by Constants/Averages

Assign vacation allowance to valuation rule 01

Time wage type valuation

IMG: Payroll / Payroll: International / Time Wage Type Valuation / Valuation Bases / Constant Valuation Bases / Define Wage Type-Dependent Constants

Use modifier for constant valuation 01 (MODIF 2, standard)Assign amount 20.00 to "Vacation allowance" wage type

Time wage type valuation

IMG: Payroll / Payroll: International / Time Wage Type Valuation / Valuation Bases / Assign Valuation Bases

Make sure that "Vacation allowance" wage type is valuated using a constant valuation basis (K).


Customizing of HR-FI/CO interface is not discussed in the Academy.

Students are therefore dependent on help from the instructor. If a group is using chart of account INT, there is no need to change any settings for the interface. HR students have to consult

May 2003 Page 124/127




with FI students to find out what chart of account is in use.


IMG: Payroll / Payroll: International / Reporting for Posting Payroll Results to Accounting / Maintain Wage Types / Define Posting Characteristics of Wage Types

IMG: Payroll / Payroll: International / Reporting for Posting Payroll Results to Accounting / Assign Accounts / ...

Check symbolic accounts and make changes when needed

Check assignment of symbolic accounts to G/L sheet account

Work together with FI group

May 2003 Page 125/127



4 HR - Case Study: common problems

P: Students try to hire employees with their original hire date from master sheet, but have created their org. structure starting 01.Jan. in the current year

S: Data should be entered “without any history”

P: Students did not use templates when defining their structures / wage types.

S: In Germany: for personnel area use DE01/ for personnel subarea DU and for wage types use MA10, MA3,… as templates.

P: When assigning cost center to org. unit appears message: “Cost Center cannot be assigned because of K….. and P……”

S: Cost Center is assigned to a Company code other then that the person is assigned to or

Cost Center is locked for postings – has to be changed from FI/CO Team members

P: When using Molga 99 there are “good templates” missing e.g. for PSA, Quota Deduction rules, wage types

S: PSA: make sure that the PSA grouping for time recording is set up (and all other groupings needed for payroll as well)

Quota Deduction Rule: make sure that the Deduction priority for absence quota types is filled in

Wage types: make sure the use of “good templates” e.g.:

M000 - Hourly rate

M020 - Monthly salary

M220 – Bonus by percentage

M400 – Vacation allowance (is not assigned to wage type group “absences”!!)

P: How to assign two holiday calendars?

S: no need to do so, use different holiday classes and day type selection rules

P: Payroll when county version is not installed

May 2003 Page 126/127



S: use Molga 99 and the International Payroll as in the exercises

P: Molga 99: which currency? Students are used to the UNI, but there is no UNI in the system

S: Use Molga 99 and your local currency (that means the currency of the company code)

P: Creating of Functional areas or user groups: Error Message: Convert first

S: Use RSAQUM40 for converting, run it first with option “convert all”, and again with “Set release flag”.

P: Bank Transfer with Molga 99

S: Do not perform Bank transfer, just posting to FI/CO

P: County specific Infotypes, required when using a National Payroll version

S: Provide help to set up these Infotypes. Country specific Payroll is not part of the lessons in academy, students should see that these Infotypes are required, but not spend too much time with it.

P: Set up the Interface to FI

S: Provide help if needed since Customizing of Interface is not part of the course

May 2003 Page 127/127