Read without ads and support Scribd by becoming a Scribd Premium Reader.
See Premium Plans
 
ERP
E
NTERPRISE
R
ESOURCE
P
LANNING
Page 17/30/2008
 
T
ABLE
 
OF
C
ONTENTS
1. INTRODUCTION......................................................................................................................3
1.1 P
URPOSE
 
OF
 
THIS
I
NTRODUCTION
................................................................................................31.2 W
HY
ERP?.........................................................................................................................3
1.2.1 Merits........................................................................................................................... ...41.2.2 Demerits.......................................................................................................... ...............5 
2.SAP..............................................................................................................................................7
2.1H
OW
 
TO
P
RONOUNCE
SAP?.....................................................................................................72.2W
HAT
 
IS
SAP R/3?...............................................................................................................72.3W
HY
SAP?..........................................................................................................................7
2.3.1Business Process Reengineering (BPR).........................................................................8 2.3.2Workflow Perspective............................................................................................ ..........92.3.3Software Alternatives.................................................................................................... ...92.3.4Software Complexity......................................................................... ............................10 2.3.5SAP R/3 Adoptions................................................................................. .......................112.3.6Best Business Practices............................................................................. ...................112.3.7Event Driven Transaction Processing............................................................................12 
3. ABAP WORKBENCH ENVIRONMENT AND TOOLS...........................................................13
3.1I
NTRODUCTION
.......................................................................................................................13
3.1.1 Workbench Tools................................................................................................ ..........13
3.2 ABAP E
DITOR
 
AND
F
UNCTIONS
...............................................................................................15
3.2.1Front End Editor ...................................................................................... .....................15 3.2.2Back End Editor ....................................................................................................... .....16 
3.3 ABAP D
ICTIONARY
..............................................................................................................19
3.3.1Creating Tables ............................................................................................................ .213.3.2Creating Views.................................................................................... ..........................233.3.3Creating Types.................................................................................... ..........................26 3.3.4Creating Lock Objects................................................................................ ...................28 
3.4S
CREEN
P
AINTER
..................................................................................................................28
3.4.1Creating Screens.................................................................................................. .........29
3.5M
ENU
P
AINTER
.....................................................................................................................32
3.5.1Creating GUI Title.................................................................................................. ........333.5.2Creating GUI Status.............................................................................. ........................333.5.3Creating Context Menu.............................................................................................. ....34
3.6O
BJECT
N
AVIGATOR
...............................................................................................................35
3.6.1Areas of Navigation in Object Navigator........................................................................37 3.6.2Objects Lists in Object Navigator..................................................................................38 
3.7E
XERCISE
............................................................................................................................40
Page 27/30/2008
 
1. Introduction
1.1Purpose of this Introduction
This introduction is intended to give brief idea about ERP (Enterprise ResourcePlanning Techniques). The term ERP originally implied, to plan the utilization of enterprise-wide resources. Although the acronym ERP originated in the manufacturingenvironment, today's use of the term ERP has much broader scope. ERP’s typicallyattempt to cover all basic functions of an organization, regardless of the organization'sbusiness or charter. Business, non-profit organizations, governments, and other largeentities utilize ERP systems.
1.2Why ERP?
Prior to the concept of ERP systems, departments within an organization would havetheir own computer systems. For example - the Human Resources (HR) department,the Payroll (PR) department, and the Financials department have their own systems.The HR computer system (Often called HRMS or HRIS) would typically containinformation on the department, reporting structure, and personal details of employees.The PR department would typically calculate and store paycheck information. TheFinancials department would typically store financial transactions for the organization.Each system would have to rely on a set of common data to communicate with eachother. For the HRIS to send salary information to the PR system, an employee numberwould need to be assigned and remain static between the two systems to accuratelyidentify an employee. The Financials system was not interested in the employee leveldata, but only the payouts made by the PR systems, such as the Tax payments tovarious authorities, payments for employee benefits to providers, and so on. Thisprovided complications. For instance, a person could not be paid in the Payroll systemwithout an employee number.
After the evolution of ERP software, among other things, combined the data of formerlydisparate applications. This made the worry of keeping employee numbers in
Page 37/30/2008
Search
Search History:
Searching...
Result 00 of 00
00 results for result for
  • p.
    • Notes
    Load more