Steps to maintain routes & zones

Steps to maintain routes & zones

 

Define, copy, delete, check shipping point

Contents

Steps to maintain routes & zones    1

Define, copy, delete, check shipping point    1

Define Transportation Zones    2

Maintain Country And Transportation Zone For Shipping Point    3

Define Routes and Stages    4

 

 

Define Transportation Zones

 

Maintain Country And Transportation Zone For Shipping Point

 

 

Define Routes and Stages

 

Maintain Route Determination

 

 

Useful SAP System Administration Transactions

Tags

,

Useful SAP System Administration Transactions

AL01  SAP Alert Monitor
AL02  Database alert monitor
AL03  Operating system alert monitor
AL04  Monitor call distribution
AL05  Monitor current workload
AL06  Performance: Upload/Download
AL07  EarlyWatch Report
AL08  Users Logged On
AL09  Data for database expertise
AL10  Download to Early Watch
AL11  Display SAP Directories
AL12  Display table buffer (Exp. session)
AL13  Display Shared Memory (Expert mode)
AL15  Customize SAPOSCOL destination
AL16  Local Alert Monitor for Operat.Syst.
AL17  Remote Alert Monitor for Operat. Syst.
AL18  Local File System Monitor
AL19  Remote File System Monitor
AL20  EarlyWatch Data Collector List
AL21  ABAP Program analysis
AL22  Dependent objects display
CREF  Cross-reference
BD64
BSVW  Linkage Status Update-Workflow Event
CMOD  Enhancements
DB01  Analyze exclusive lock waits
DB02  Analyze tables and indexes
DB03  Parameter changes in database
DB11  Early Watch Profile Maintenance
DB12  Overview of Backup Logs
DB13  Database administration calendar
DB14  Show SAPDBA Action Logs
DB15  Data Archiving: Database Tables
DB16  DB System Check: Monitor
DB17  DB System Check: Configuration
DMIG  Start Transaction for Data Migration
DB2   Select Database Activities
DB20  DB Cost-Based Optimizer: Tab. Stats
DB21  DB Cost-Based Optimizer: Config.
DB24  Database Operations Monitor
DB26  DB Profile:Monitor and Configuration
DB2J  Manage JCL jobs for OS/390
DBCO  Database Connection Maintenance
FILE  Cross-Client File Names/Paths
NACE  WFMC: Initial Customizing Screen
OAA1  SAP ArchiveLink: Maint.user st.syst
OAA3  SAP ArchiveLink protocols
OAA4  SAP ArchiveLink applic.maintenance
OAAD  ArchiveLink Administration Documents
OAC2  SAP ArchiveLink: Globaldoc. types
OAC5  SAP ArchiveLink: Bar code entry
OACA  SAP ArchiveLink workflow parameters
OAD0  SAP ArchiveLink: Objectlinks
OAD2  SAP ArchiveLink document classes
OAD3  SAP ArchiveLink: Link tables
OAD4  SAP ArchiveLink: Bar code types
OAD5  SAP ArchiveLink: Customizing Wizard
OADR  SAP ArchiveLink: Print list search
OAM1  SAP ArchiveLink: Monitoring
OAOR  SAP ArchiveLink: Storeddocuments
OARE  SAP ArchiveLink:St.syst.return codes
OS01  LAN check with ping
OS03  O/S Parameter changes
OS04  Local System Configuration
OS05  Remote System Cconfiguration
OS06  Local Operating System Activity
OS07  Remote Operating SystemActivity
OSS1  Logon to Online ServiceSystem
OY18  Table history
OY08  Development Class Overview
PFCG  Activity Group
PFUD  Authorization Profile comparison
RLOG  Data migration logging
RZ01  Job Scheduling Monitor
RZ02  Network Graphics for SAP Instances
RZ03  Presentation, Control SAP Instances
RZ04  Maintain SAP Instances
RZ06  Alerts Thresholds Maintenance
RZ08  SAP Alert Monitor
RZ10  Maintenance of profile parameters
RZ11  Profile parameter maintenance
RZ12  Maintain RFC Server Group Assignment
RZ20  CCMS Monitoring
RZ21  Customize CCMS Alert Monitor
SA38  ABAP/4 Reporting
SAD0  Address Management call
SADC  Address: Maint. communication types
SALE  Display ALE Customizing
SAINT Plug-in Installation
SARI  Archive Information System
SAR3  Customizing Archiving
SAR4  Define Archiving Class
SAR5  Assign Archiving Class
SAR6  Archiving Time Generator
SARA  Archive management
SARL  Call of ArchiveLink Monitor
SARP  Reporting (Tree Structure): Execute
SART  Display Reporting Tree
SB01  Business Navigator – Component View
SB02  Business Navigator – Process flow vw
SBAS  Assignments to Process Model Elemts
SC38  Start Report Immediately
SCAT  Computer Aided Test Tool
SCC0  Client Copy
SCC1  Client Copy – Special Selections
SCC2  Client transport
SCC3  Client Copy Log
SCC4  Client administration
SCC5  Client Delete
SCC6  Client Import
SCC7  Client Import – Post Processing
SCC8  Client Export
SCC9  Remote Client Copy
SCCL  Local Client Copy
SCDO  Display Change DocumentObjects
SCMP  View / Table Comparison
SCOM  SAPcomm: Configuration
SCON  SAPconnect – Administration
SCPF  Generate enterprise IMG
SCPR1 Customizing Profiles : Maintenance Tool
SCPR2 Comparing Customizing profiles
SCUA  Central User Administration : Distribution Model Assigment
SCUG  Central User Administration Structure Display
SCUL
SCUM  Central User Administration Field Selection
SCU0  Table Analyses And Comparison
SCU1  Table Comparison – Export to Tape
SCU2  Table Comparison Against Tape
SCU3  Table History
SD11  Data Modeler
SDBE  Explain an SQL Statement
SECR  Audit Information System
SE01  Transport and Correction System
SE02  Environment Analyzer
SE03  Transport Utilities
SE06  Set up Workbench Organizer
SE07  Transport System Status Display
SE09  Workbench Organizer (Initial Screen)
SE10  Customizing Organizer
SE11  Data Dictionary Maintenance
SE12  Data Dictionary Display
SE13  Maintain Technical Settings (Tables)
SE14  Convert Data Dictionary tables on Database Level
SE15  Repository Info System
SE16  Display Table Content
SE17  Generate Table Display
SE30  ABAP Objects Runtime Analysis
SE32  ABAP Text Element Maintenance
SE33  Context Builder
SE35  ABAP/4 Dialog Modules
SE36  Logical databases
SE37  ABAP Function Modules
SE38  ABAP Editor
SE39  Splitscreen Editor: Program Compare
SE40  MP: Standards Maint. and Translation
SE41  Menu Painter
SE43  Maintain Area Menu
SE51  Screen Painter
SE52  Parameterized screenpainter call
SE54  Generate table view
SE55  Internal table view maintenance call
SE56  internal call: display table view
SE57  internal delete table view call
SE61  R/3 Documentation
SE62  Industry Utilities
SE63  Translation: Initial Screen
SE71  SAPscript form
SE72  SAPscript Styles
SE73  SAPscript font maintenance (revised)
SE74  SAPscript format conversion
SE75  SAPscript Settings
SE76  SAPscript: Form Translation
SE77  SAPscript Translation Styles
SE78  SAPscript: Graphics administration
SE80  Object Navigator
SE81  Application Hierarchy
SE82  Application Hierarchy
SE84  R/3 Repository Information System
SE85  ABAP/4 Repository Information System
SE86  ABAP Repository Information System
SE88  Development Coordination Info System
SE89  Maintain Trees in Information System
SE91  Maintain Messages
SE92  New SysLog Msg Maintenance as of 46A
SE93  Maintain Transaction Codes
SE94  Customer enhancement simulation
SE95  Modification Browser
SEPS  SAP Electronic Parcel Service
SERP  Reporting: Change Tree Structure
SEU   Repository Browser
SF01  Client-Specific File Names
SFAW  Field Selection Maintenance
SIAC1 Web Object Administration
SHDB  Record Batch Input
SICK  Installation Check
SIN1  SAPBPT: Inbox
SINA  SAPBPT: Maintain Standard Config.
SLG0  Application Log: ObjectMaintenance
SLIN  ABAP: Extended Program Check
SM01  Lock Transactions
SM02  System Messages
SM04  User Overview
SM12  Display and Delete Locks
SM13  Display Update Records
SM14  Update Program Administration
SM21  System log
SM23  System Log Analysis
SM28  Installation Check
SM29  Model Transfer for Tables
SM30  Call Up View Maintenance
SM31  Table maintenance
SM31_OLD  Old Table Maintenance
SM32  Maintain Table Parameter ID TAB
SM33  Display Table ParameterID TAB
SM34  Viewcluster maintenancecall
SM35  Batch Input Monitoring
SM36  Batch request
SM37  Background job overview
SM38  Queue Maintenance Transaction
SM39  Job analysis
SM49  Execute Logical Commands
SM50  Work Process Overview
SM51  List of SAP Servers
SM54  TXCOM maintenance
SM55  THOST maintenance
SM56  Number Range Buffer
SM58  Asynchronous RFC Error Log
SM59  RFC Destinations (Display/Maintain)
SM60  Borrow/Return Objects
SM61
SM62
SM63  Display/Maintain Operating Mode Sets
SM64  Release of an event
SM65  Background Processing Analysis Tool
SM66  System-wide Work Process Overview
SM67  Job scheduling
SM68  Job administration
SM69  Display/Maintain Logical Commands
SMEN  Dynamic menu
SMGW  Gateway Monitor
SMLG  Maintain Logon Group
SMLI  Language import utility
SMLT  Language transport utility
SMOD  SAP Enhancement Management
SMT1  Trusted Systems (Display <-> Maint.)
SMT2  Trusting systems (Display <->Maint.)
SMW0  SAP Web Repository
SMX   Display Own Jobs
SNRO  Number Range Objects
SO02  SAPoffice: Outbox
SO03  SAPoffice: Private Folders
SO04  SAPoffice: Shared Folders
SO05  SAPoffice: Private Trash
SO06  SAPoffice: Substitutionon/off
SO07  SAPoffice: Resubmission
SO10  SAPscript: Standard Texts
SO12  SAPoffice: User Master
SO13  SAPoffice: Substitute
SO15  SAPoffice: DistributionLists
SO16  SAPoffice: Profile
SO17  SAPoffice: Delete Shared Trash
SO18  SAPoffice: Shared Trash
SO19  SAPoffice: Default Documents
SO21  Maintain PC Work Directory
SO22  SAPoffice: Delete PC Temp. Files
SO23  SAPoffice: DistributionLists
SO24  SAPoffice: Maintenance of default PC
SO28  Maintain SOGR
SO30  SAPoffice: Reorg.
SO31  Reorganization (daily)
SO36  Create Automatic Forwarding
SO38  SAPoffice: Synchr. of Folder Auths.
SO40  SAPoffice: Cust. LayoutSet MAIL
SO41  SAPoffice: Cust. LayoutSet TELEFAX
SO42  SAPoffice: Cust.Layout Set TELEFAX_K
SO43  SAPoffice: Cust.Layout Set TELEFAX_M
SO44  SAPoffice: Cust. LayoutSet TELEX
SO70  Hypertext: Display/Maint. Structure
SO71  Test plan management
SO72  Maintain Hypertext Module
SO73  Import graphic into SAPfind
SO80  SAPfind: Free Text Retrieval Dialog
SO81  SAPfind: Free Text Indexing (Test)
SO82  SAPfind: Free Text Retrieval Batch
SO95  Pregenerated Search Queries – Selec.
SO99  Put Information System
SOA0  ArchiveLink Workflow document types
SOBJ  Attribute Maintenance Objects
SOLE  OLE Applications
SOLI  Load OLE type info
SOPE  Exclude Document Classes
SOTD  SAPoffice: Maintain Object Types
SOY1  SAPoffice: Mass Maint. Users
SOY2  SAPoffice: Statistics data collect.
SOY3  SAPoffice: Statistics Evaluation
SOY4  SAPoffice: Access overview
SOY5  SAPoffice: Inbox overview
SOY6  SAPoffice: Document overview
SOY7  SAPoffice: Folder overview
SOY8  SAPoffice: Mass Archiving
SOY9  SAPoffice: Inbox Reorg.
SOYA  SAPoffice: Change folder owner
SP00  Spool and Relate Area
SP01  Spool Control
SP02  Display output Requests
SP03  Spool: Load Formats
SP11  TemSe Contents
SP12  TemSe Administration
SPAD  Spool Management
SPAM  SAP Patch Manager (SPAM)
SPAU  Display Modified DE Objects
SPCC  Spool Consistency check
SPDD  Display Modified DDIC objects
SPHA  Telephony administration
SPIC  Spool : Installation Check
SPRM  Current Customizing
SPRO  Customizing
SQ01  SAP Query: Maintain queries
SQ02  SAP Query: Maintain funct. areas
SQ03  SAP Query: Maintain user groups
SQ07  SAP Query: Language comparison
SQVI  QuickViewer
SSAA  System Administration Assistant
SSCA  Appointment Diary: Administration
SRZL  CCMS
SSM1  Session Manager generation call
SSM5  Create Activity Group
ST01  System Trace
ST02  Setups/Tune Buffers
ST03  Performance, SAP Statistics, Workload
ST04  Select activity of the databases
ST05  SQL Trace
ST06  Operating System Monitor
ST07  Application monitor
ST08  Network Monitor
ST09  Network Alert Monitor
ST10  Table Call Statistics
ST11  Display Developer Traces
ST12  Application Monitor
ST14  Application Analysis
ST22  ABAP Runtime Error Analysis
ST22  ABAP/4 Runtime Error Analysis
ST62  Create industry short texts
STAT  Local transaction statistics
STMS  Transport Management System
STUN  Performance Monitoring
STW1  Test Workbench: Test catalog
STW2  Test workbench: Test plan
STW3  Test workbench: Test package
STW4  Test Workbench: Edit test package
STW5  C maintenance table TTPLA
STZAC Maintain time zone act.in client
STZAD Disp.time zone activat.in client
SUMM  Global User Manager
SU01  Maintain User
SU01D Display users
SU02  Maintain Authorization Profiles
SU03  Maintain Authorizations
SU05  Maintain Internet Users
SU10  Mass changes to User Master
SU11  Maintain Authorizations
SU12  Mass Changes to User Master Records
SU2   Maintain User Parameter
SU20  Maintain Authorization Fields
SU21  Maintain Authorization Objects
SU22  Auth. object usage in transactions
SU24  Disables Authorization Checks
SU25  Imports SAP Check Indicators defaults
SU26  Adjust Authorization checks
SU30  Total checks in the area of auth.
SU52  Maintain own user parameters
SU53  Display check values
SU54  List for Session Manager
SU56  Analyze User Buffer
SUPC  Profiles for activity groups
SUPF  Integrated User Maintenance
SUPO  Maintain Organization Levels
SUIM  Repository Info System
SWDC  Workflow Definition
SXDA  Data Transfer Workbench
TU02  Display Active Parameters
USMM  Customer measurement

 

Upload Purchase Order data using multiple flat files (LSMW)

From Muthuvel Kumaran, Kaavian Systems

 

In this tutorial Muthuvel show how to generate Purchase Order using LSMW in Standard Batch/Direct Input Method using two flat files for generating the PO, one file for Header data and another one for Item data.  

 

Step I:  

Before, we go to the LSMW Process. Make the Flat files as shown below with the delimiter as ‘Tabulator’.  

Header file:  

Item file:


Step II:  

Create an Object in T-Code: LSMW.  


Step III:  

Press ‘F8’ for Execute the object.

Step IV:  

Initial screen for LSMW object  


Step 1: 

a). Double Click ‘Maintain Object Attributes’ and below screen show and click Standard Batch/Direct Input  and click the F4 for Object and select 0085 Purchase order  

 

b). Click ‘F4′ for choosing the method and select ‘0001′ ‘Purchase order’  ‘RM06EEI0’ and press Enter. Then Save and Back.  

 

Step2:  

a). Double Click on ‘Maintain Source Structures’ then click create a structure(CTRL+F4)

 

b). Create structure for Header data and Save it.

 

c). Then click the header structure and create the second structure for Item data and define the relationship in Lower level and press Enter.


 

 

d). create the source structure for Item data and Save it.  

 

e). You will the screen like this.

 

Step3: 

a). Double click on ‘Maintain Source Fields’.    


b). click the zheader (source fields) and click the copy fields (CTRL+F8) and select the radio button ‘Date file (Field name is 1.line)’ and press Enter .  


c). Give 99 or more for two fields and press Enter.

 

d). Browse the header file for source fields and press Enter.  


e). Source fields created as below.

 

f). Click the zline (source fields) and proceeds the same procedure as above step and the source fields created for Item data, then below screen appears. Finally Save and go Back.


Step4:  

Double click on ‘Maintain Structure Relations’

a). Click the Purchase order header  and create the Relationship or CTRL+F4.

 

 

 

b). After created the relationship for header and select the source structure zheader and press Enter.  

 

c). Then Click the second one (Purchase order item) and do the same procedure for Create the Relationship and assign source structure for Item.


d). Save and Back.


http://www.saptechnical.com/Tutorials/LSMW/PO/Page3.htm

 

Double click on ‘Maintain Field Mapping and Conversion Rules’.  


a).  Go to ‘Extra’ in menu bar and select the ‘Auto field mapping‘.


b). Select the Radio button as same as shown in the below screen and press Enter.  


c). You will get the Popup window as shown below and press Enter.

 

d). After the Auto field mapping completed. You will get the screen like this  


e). Add the code for LIFNR conversion routine and double click on the LIFNR field. You will get this code screen ‘MBEPOH-LIFNR = ZHEADER-LIFNR’.

f). Add the code:  

CALL FUNCTION ‘CONVERSION_EXIT_ALPHA_INPUT’

EXPORTING

INPUT =  ZHEADER-LIFNR

IMPORTING

    OUTPUT = MBEPOH-LIFNR.  

After entered the code ‘Save and Back (F3)’.  


g). Double click the code: ZHEADER-BEDAT (BEDAT) for conversion routine and add the code as shown below:  

CALL FUNCTION ‘DATE_CONV_EXT_TO_INT’

EXPORTING

i_date_ext       = ZHEADER-BEDAT

IMPORTING

E_DATE_INT       = MBEPOH-BEDAT.  

After entered the code ‘Save and Back (F3)’.  


h). Double click on Code: MBEPOI-EINDT = ZLINE-EINDT, then add the below code.

CALL FUNCTION ‘DATE_CONV_EXT_TO_INT’

EXPORTING

i_date_ext       = ZLINE-EINDT

IMPORTING

E_DATE_INT       = MBEPOH-EINDT.  

Then Save and Back (F3).  


i). Save and go Back.  


http://www.saptechnical.com/Tutorials/LSMW/PO/Page4.htm

 

Step8:  

a). Double click  on  ‘Assign Files’ and click zheader  and then click the ‘Assignment‘  button or (CTRL+F2).

 

b). Select the header file and press Enter.


c). Assign files for Item data and click the Assignment button. Then Save and go Back.  

 

Step9:  

a). Double click on  ‘Read Data’ and press F8.  

 

b). After the execution and make sure ‘Not written’ is 0 like the below screen and go Back.

 

Step10:  

a). Double click on  ‘Display Read Data’ and Dialog screen appears and press Enter.


b). If you want to check the data, just double click on the fields.


c). Verify the data should be correct or not and go Back.  

 

Step11:  

Double click on ‘Convert Data’ and  Check with that below screen.  


Step12:  

Double click on ‘Display Converted Data’ and Check with that below screen.  


Step13:  

Double click on ‘Start Direct Input Program’ and Click the radio button ‘With database update’ and ‘Log with error messages’.  Then press F8.


Step V:  

Once, the database updated successfully, you will get the screen as shown below and in the meantime Purchase order numbers also created.  


 

 

 

Maintain COPA characteristic value – ORKE

ORKE

 

We can get access all transaction to maintain COPA in SAP by T-Code ORKE.

 

ORKE – MAINTAIN OPERATING CONCCERN

 


 

Make Characteristics Available For The Operating Concern. 

SPRO > Controlling > Profitability Analysis > Structures > Define 
Operating Concern > Maintain Characteristics. 

T-Code: KEA5.

Maintain Operating Concern to now ‘use’ the new fields selected 
from above. 

 

SPRO > Controlling > Profitability Analysis > Structures > Define 
Operating Concern > Maintain Operating Concern. 

T-Code: KEA5.

 

Transport New Structures to Destination Clients 

SPRO > Controlling > Profitability Analysis > Tools > Production Startup 
> Transport. 

T-Code: KE3I

 

Generate Client Dependant Items 

After the transport has been completely imported to the destination 
client(s) … (Allow some minutes for this complete)
 
Log into the client and go into COPA and SET THE OPERATING CONCERN
 
(Accounting > Controlling > Profitability Analysis > Environment > Set
 
Operating Concern)
 
Set for operating concern (your operating concern) 

T-Code: KEBC.

Assign Controlling Area to Operating Concern
SPRO > Enterprise Structure > Assignment > Controlling > Assign Controlling Area to Operating Concern
 Creation of Number Ranges for Actual Postings in PA
SPRO > Controlling > Profitability Analysis > Flows of Actual Values > Initial Steps > Define Number Ranges for Actual Postings
 Activation of Profitability Analysis (KEKE)
SPRO > Controlling > Profitability Analysis > Flows of Actual Values > Activate Profitability Analysis
Go to Controlling Area XYZ and give Active Status: 4 (Component Active for Both Types of Profitability Analysis, Costing Based & Account Based)
Activation can be verified in OKKP

 

 

Assigning Value Fields in COPA:


SPRO > Controlling > Profitability Analysis > Flows of Actual Values > Transfer Billing Documents > Assign Value Fields
Double click ‘Maintain Assignment of SD Condition Types to COPA Value Fields’
Operating Concern: idea (Operating Concern IDES worldwide) & Enter
Watch the Value Fields and Assign the same Fields in Your Company Code in Real Time.

For Assigning Qty Fields:
SPRO > Controlling > Profitability Analysis > Flows of Actual Values > Transfer Billing Documents > Assign Quantity Fields
Watch the Structure and Copy in your Company Code in Real Time.
 Direct Postings from MM/FI (KEI2)
SPRO > Controlling > PA > Flows of Actual Values > Direct Postings from FI/MM > Maintain PA Transfer Structure for Direct Postings

Change Field Status Group to make Profitability Segment mandatory
SPRO > Financial Accounting > FAGS > Document > Line Item > Controls > Maintain Field Status Variant

 

 

a-short-tutorial-on-user-exits

 

1. Introduction:


User exits (Function module exits) are exits developed by SAP. The exit is implemented as a call to a function module. The code for the function module is written by the developer.

You are not writing the code directly in the function module, but in the including is implemented in the function module.


The naming standard of function modules for function module exits is:  EXIT_<program name><3 digit suffix>.
The call to a function module exit is implemented as:
CALL CUSTOMER.-FUNCTION ❤ digit suffix>


Example:
The program for transaction VA01 Create sales order is SAPMV45A
If you search for CALL CUSTOMER-FUNCTION program
SAPMV45A you will find (Among other user exits):

 



Example:

 

The exit calls function module EXIT_SAPMV45A_003


  exporting

    xvbak   = vbak
    xvbuk   = vbuk
    xkomk   = tkomk
  importing

    lvf_subrc = lvf_subrc
  tables

    xvbfa = xvbfa
    xvbap = xvbap
    xvbup = xvbup.

2. How to find user exits?


If you know the Exit name, go to transaction CMOD.


Choose menu Utilities->SAP Enhancements.

Enter the exit name and press enter.
You will now come to a screen that shows the function module exits for the exit.

 

Example:

 

Using Project management of SAP Enhancements, we want to create a project to enhance transaction VA01.
– Go to transaction CMOD
– Create a project called ZVA01
– Choose the Enhancement assign radio button and press the Change button
In the first column enter V45A0002 Predefine sold-to party in sales document. 
Note that an enhancement can only be used in 1 project. If the enhancement is already in use, and error message will be displayed
Press Save
Press Components.

You can now see that enhancement uses user exit EXIT_SAPMV45A_002. Double click on the exit.

 



Now the function module is displayed. Double click on include ZXVVAU04 in the function module :

 



Insert the following code into the include:

 

E_KUNNR = ‘9999’.


Activate the include program. Go back to CMOD and activate the project. 
Go to transaction VA01 and create a sales order. 
Note that Sold-to-party now automatically is “9999”

 

ABAP, CMOD, Enhancement, Module, Tutorial, User Exits  

SAP SALARY: HOW MUCH YOU EARN THIS YEAR

The earnings of an SAP professional depend on many variables, including education level, experience, the location of the company they work for, and the industry they are in.

This survey from Sap FICO help you compare your compensation makeup to industry peers, better understand what drives compensation in this market, and get useful ideas for increasing your value.

 

SAP SALARY BY LOCATION

 

The median salary of SAP professionals working for companies based in North America is 10% higher than the median salary of those working for companies based in Europe and as much as 25-80% higher than those working for companies based in other parts of the world.

 

SAP SALARY BY COMPANY REVENUE

 

Salaries of employees of SAP customers tend to be higher for those employed by companies with higher revenues, while salaries of partners and integrators are highest at companies with revenues below half a billion dollars.

 

SAP SALARY BY INDUSTRY

 

When looking at respondents’ industries, median salaries are the highest for those working for companies in aerospace & defense, professional services, healthcare, and financial services. The lowest medians are for those working in the public sector & education, logistics & transportation, and communications.

SAP SALARY BY FUNCTION

As expected, professionals in director and manager positions earn the most, while SAP trainers have the lowest salaries. The median for the highest earning positions (CIO) is as much as 165% higher than the median for the lowest earning position (SAP Trainer).

 

SAP SALARY BY EXPERIENCE

 

Job experience plays a major role in determining salary levels. The median salary for respondents with more than 10 years of experience is more than double (124% higher) than for those with 1-3 years of experience.

SAP SALARY BY EDUCATION

 

With some exceptions, higher education corresponds with higher earnings for SAP professionals. The median salary for respondents with a doctoral degree is 21% higher than the median salary for those with a master’s degree and 34% higher than the median salary for those with a bachelor’s degree.

Surprisingly, the median salary for those with only a high school diploma is 7% higher than the median salary of those whose highest education is a Bachelor’s degree.