Академический Документы
Профессиональный Документы
Культура Документы
Introduction
1.1 Project Acer
Acer is implementing sap in Project UCB to have latest and standard version of software to make things flow in
standard and fluent manner using SAP suite of applications.
1.2 Implementation Mythology
Project Acer is being implemented using Accelerated SAP (ASAP) methodology, SAP leverages a core set of
methodologies and tools designed to deliver rapid, reliable results, and to help our customers get the most from their
solutions. These include the ASAP Methodology for Implementation (content the project team follows to implement
SAP software efficiently).
The ASAP methodology adheres to a specific road map that addresses the following five general phases:
Project Preparation:
In this step the project team is identified and mobilized, the project standards are defined, and the project
work environment is set up.
Business Blueprint:
In this step the business processes are defined and the business blueprint document is designed.
Realization:
In this step the system is configured, knowledge transfer occurs, extensive unit testing is completed, and
data mappings and data requirements for migration are defined.
Final Preparation:
In which final integration testing, stress testing, and conversion testing are conducted, and all end users are
trained.
II
OM - Organization Management
Serial No.
2.1
2.1.2
2.2.1
Table Contents
Content
Configuration
Setup Number Assignment for all
Plan Versions
Set Active Plan Version
Page No
02
02
04
05
2.3.1
2.4.1
13
2.5.1
2.5.2
2.5.3
Infotype maintenance
Maintain Sub Infotye
Maintain User-Defined Settings
for Infotypes
Relationship maintenance
Evalution Path Maintenace
Setup Transport
Organization Structure Creation
14
16
18
Organization Structure
Modification
Organization Structure Display
28
2.2.2
2.6.1
2.7.1
2.7.1
3.2.1
3.2.2
3.2.3
07
11
20
21
23
25
31
Configuration
The configuration involves four broad areas viz.
a.
b.
c.
d.
III
Our Number Assignment is going to be Plan Version Independent i.e. it will be the same across all Plan
Versions. The benefit of this option is that there is no danger of parallel number intervals occurring i.e. the
same number interval for one object in one plan version and for a different object in another plan version.
Configuration Path:
SPRO>>>>SAP Reference IMG>>>>Personnel Management>>>>Global Setting In Personal
Management>>>>Plan Version Maintenance>>>>Maintain Plan Version.
IV
VI
VII
VIII
IX
10
XI
Click Intervals
Insert specific numbers. Similarly for 21S, 21O, 21C. Click on save button.
2.3.1 OM PA Integration
In the SAP system the integration is controlled using switches. All the integration switches are stored in
table T77S0. PA OM integration is defined by PLOGI ORGA in below table.
11
XII
Configuration path:
SPRO>>>>SAP Reference IMG>>>>Personnel Management>>>>Organizational
Management>>>>Integration>>>>Integration with Personnel Administration OR use TCODE:SM30
OR SM31 to change table T77S0.
12
XIII
. Click on Go back
13
XIV
14
XV
15
XVI
16
XVII
17
XVIII
18
XIX
19
XX
20
XXI
21
XXII
22
XXIII
23
XXIV
24
XXV
25
XXVI
26
XXVII
Setup Date
27
XXVIII
28
XXIX
Click on PPOC_OLD_Change
29
XXX
XXXI
31
XXXII
32