SAP BASIS JOBS IN INDIA

SAP Basis Adminsitration Jobs in India

2009-05-17T11:13:00.001-07:00

My client is a well-established public listed company looking for dynamic individuals to join their team:

Responsibilities:

Administer and support SAP R/3 & BW infrastructure such as DB/CI server, application servers, printing devices and SAPGUI setup Participate in SAP related project implementation Responsible for database administration of SAP systems Conduct capacity planning and monitor the health of the SAP systems to meet service level agreement Conduct disaster recovery planning and exercise Requirements:
Degree with at least 3 years of related experience Good project management skill Familiar with Windows and Unix operating system and Microsoft Clustering Services Good knowledge in new technologies of SAP. SAP XI/EP is added advantage, network infrastructure and database administration (Oracle, SQL Server) is a must Others:
Working location: Anywhere in India. Salary Range: Negotiable

SAP BASIS Jobs in India

2009-05-17T10:15:00.000-07:00

Requirements:Candidate must possess at least a Diploma, Advanced/Higher/Graduate Diploma, Bachelor's Degree, Post Graduate Diploma, Professional Degree or Master's Degree in any field.Required skill(s): SAP.At least 3 year(s) of working experience in the related field is required for this position.Preferably Senior Executives specializing in IT/Computer - Software or equivalent. Job role in Software Engineer/Programmer or equivalent.7 Full-Time and Contract position available.Applicants should be Singaporean citizens or hold relevant residence status.
SAP BASIS Consultant• 3+ Yrs. SAP BASIS Administration Experience • Exp. in Netweaver /WebAs Installations/Upgrades • SAP System Integration/Multi Mixed Systems
SAP PP Consultant• Requires at least 1 SAP PP full development life-cycles on major projects. • 2+ years SAP PP Configuration skills • Strong Communication skills, project management skills, written and analytical skills
SAP DP Consultant • This role will support the implementation of mid-term solution, a software upgrade, and long-term solution in improving the demand planning process. • Min 3 yrs of experience is required• SAP APO Demand Planning Configurations • Preferred: SAP BW and integration with APO DP
SAP_ABAP Technical Consultant• Two or more years of experience in ABAP. • SAP ABAP Implementation experience – at least one complete lifecycle

To apply, please send a copy of your updated resume to neha@ssn.co.in mentioning your salary details, Notice Period & Reason of leaving org

SAP Basis Jobs in India

2009-05-16T11:17:00.000-07:00

SAP Consultant/Basis/ABAP - multiple openings Responsibilities and Requirements

SAP Consultant (various modules)
· Recognized Diploma or Degree in IT or equivalent
· 2-3yrs consulting experience in any one of these modules: SAP FICO, SD, MM, HR or XI
· Perform requirement gathering, prepare specifications and ensure smooth roll-out of projects
· Skilled with latest version of SAP, especially ECC 6.0 and solve integration issues
· Good knowledge of ABAP; techno-functional role
· Comfortable with client facing- mixed-consultancy environment
· Good communication skills
· Senior candidates will be considered for SAP architect position (Insurance industry experience needed)

SAP ABAP Consultant
· Recognized Diploma or Degree in IT or equivalent
· Define project specifications, support UAT and SI tests
· 2-3yrs strong technical experience in ABAP
· 2-3yrs experience in project implementation
· Good communication skills

SAP Basis Consultant
· Recognized Degree in IT or equivalent
· Participate in Basis (version 4.5B onwards) project implementation, disaster recovery planning and support SAP applications team upon roll-out
· Experience in administer and upgrade SAP database in Oracle SQL server
· Familiar with Windows environment and MS clustering services and provide network infrastructure support
· Experience in ABAP and BW module is an advantage

SAP Job Market

2009-02-10T10:49:00.000-08:00

Though the Jobs for SAP Basis have been lessen because of Economic crisis, It is very much less when compared to Other technologies. Good news is from the last month, the companies are conducting interview in the plan to recruit people by the end of March/April'09 and the most companies are looking only for SAP.

SAP Trex Configuration Document

2009-02-10T10:47:00.000-08:00

TREX consists of the following components

JAVA client

TREX provides several interfaces that can be used to integrate TREX functions into an application. The Java client is an interface that Java applications can use to access TREX. The Java client is integrated into Content Management. This means that the TREX functions are available in Content Management and therefore in the portal.

Web Server with TREX Extension
Content Management (more precisely, the Java client) accesses the TREX functions using aWeb server. Communication between Content Management and the Web server takes place using HTTP/HTTPS and XML. The Web server receives requests and forwards them to the index server and queue server. The servers then process the requests. A TREX component that enhances the Web server with TREX-specific
functions is installed on the web server. On windows this component is realized as as an ISAPI server extension for the Microsoft Internet Information Server.

Queue Server

The queue server enables the asynchronous indexing of documents. It has a separate queue for each index. It gathers documents to be indexed into one of the queues. It transfers documents to the index server for the actual indexing process at regular intervals. You can use the queue parameters to control when and how many documents are transmitted. This allows you to schedule indexing for times at which the index server does not receive a large amount of search requests. The queue server forwards the documents to the preprocessor before transmitting them to the index server.

Preprocessor

The preprocessor has two tasks:
1. When TREX processes search requests, the preprocessor carries out a linguistic analysis of search queries. The preprocessor passes the results of the analysis to the index server, which then processes the query further.

2. When TREX receives documents to be indexed, the preprocessor prepares the documents for the actual indexing process.

Name Server
The name server is used with large distributed TREX installations. It uses its databasis to store and coordinate system-wide information. It also ensures that the TREX servers can communicate with each other and that TREX can communicate with Content Management. The name server is also responsible for distributing the system load if more than one TREX server is capable of carrying out a task. In a distributed scenario, you can install several name servers to ensure that a name server is always available. A replication procedure ensures that the databases of the different name servers are synchronized.

TREX service
After the TREX installation, a TREX service (daemon on UNIX platforms) runs on each host. The TREX service is a central service that starts the actual TREX servers (index server, queue server, and so on) and monitors them during routine operation. If a server
becomes unavailable, it is automatically restarted by the daemon. In the standard configuration, the TREX service starts all servers that have to run for a minimal TREX system. For a distributed installation, you can use the service configuration file to control which servers the service starts on individual hosts.

Python Support and Python Extensions
Python support includes scripts that are used to test TREX functions. For example, you can test creating indexes as well as indexing and searching documents. Python support also includes a tool for administrating the name server (name server administration). Some name server functions can only be administrated using this script. Python extensions are scripts that enhance standard TREX functions with optional features. Index replication is one of these optional features.

SAP RSABAPSC - Auth-Check Command Objects

2009-02-10T10:46:00.002-08:00

RSABAPSC - Auth-Check Command Objects

To know all the Auth-Check command objects used in any Transaction/Program

Report RSABAPSC is useful in finding the Authorization check command objects used in any Program/ Function Module/ Transaction.
This is helpful in finding the objects either not listed in SU24 and also in case of customer developed programs.

Steps:

1. Run the report RSABAPSC in SE38. And enter the desired Program/ Function Module/ Transaction code in the appropriate field and Execute.

e.g. for report RFITEMAR

Or for Transaction Code FBL5N.

2. The result specifies all the Auth Checks used in the code.

NOTE: This report may not work on few Transaction codes.

Assigning Full SAP Authorizations ( * ) in Roles

2009-02-10T10:46:00.001-08:00

Assigning Full Authorizations ( * ) in Roles

Easy way of Setting full authorization ( * ) to fields in PFCG.

Using the button , you can set the authorization fields to '*' (full authorization) very quickly. This can be done either for Individual objects, for the whole class or for the whole role in one go. All you have to do is to click the button adjacent to required object/class etc.

Note: Full authorization( * ) is assigned to all unmaintained fields except for fields controlled from ORG. levels. ORG level fields can be maintained separately.

This is particularly helpful while creating roles having full authorization on most of the fields.

SAP XI Transaction codes

2009-02-10T10:45:00.001-08:00

Click here for more topics on SAP BASIS
Click here for more topics on SAP Enterprise portal
Click here to Earn Money online for free
Other Useful SAP Websites

1.SXMB_IFR -> Start Integration Builder
2.SXMB_MONI -> Integration Engine - Monitoring
3.SXI_MONITOR -> XI: Message Monitoring
4.SXI_CACHE -> To Access IS runtime cache
5.sxi_cache -> XI data directory cacheidx1 -> idoc adapter
6.idx2 -> idoc metadata
7.idx5 -> monitocr idoc adapter
8.sm21 -> log di sistema
9.st22 -> dump abap (analisi di eccezioni)
10.smq1 -> messages inbound e outbound queue
11.smq2 -> messages inbound e outbound queue
12.smicm -> J2EE administration
13.st06 -> stato della macchina cpu memory filesystem machine status - cpu,
14.memory and file system.
15.st03 -> workload.
16.scc4 -> visualizza mandanti del sistema
17.we20 -> partner profiles
18.sale - ale settings
19.rz10 - edit system profile
20.sm59 ->mantain rfc destinations
21.bd64 -> mantain distribution model (trasformazioni)
22.SU01 -> users
23.AL08 -> list all logged users(user login logon)
24.SE10 -> Change Request
25.SE09 -> Change Request
26.WE05 -> All idocs
27.WE19 -> IDoc Test Tool
28.WE21 -> port definition
29.SE11 -> Data dictionary
30.SM21 -> log sistema xi
31.se37 -> mantain funcion modules
32.SICF -> http server configuration
33.SMGW -> trace, alzare livello di trace.
34.BD13 ->
35.BD64 -> modelli di distribuzione
36.pfcg -> Roles
37.tabella TSTC -> sap transactions codes
38.tabella TSTCT -> transaction descriptions
39.STMS -> transports management
40.SPAM -> apply ABAP support packages
41.SPAU -> manage objects after apply support packages
42.SE01 -> manage change requests
43.SLDCHECK -> Test SLD Connection
44.SLDAPICUST-> SLD API Customizing
45.SXMB_ADM -> Integration Engine - Administration
46.SXMB_MONI_BPE -> Process Engine - Monitoring
47.SE38 -> ABAP Editor
48.SE11 -> ABAP Dictionary
49.ST22 -> ABAP dump analysis
50.SPROXY-> ABAP Proxy Generation
51.SE80 -> Object Navigator
52.ABAPDOCU -> ABAP Documentation and Examples
53.SE24-> Class Builder
54.SM21-> Online System Log Analysis
55.SMQ1-> qRFC Monitor (Outbound Queue)
56.SMQ2-> qRFC Monitor (Inbound Queue)
57.RZ70-> SLD Administration
59.SM58-> Asynchronous RFC Error Log
60.SM59-> RFC Destinations (Display/Maintain)
61.SMICM-> ICM Monitor
62.WE60-> Documentation for IDoc types
63.BD87-> Status Monitor for ALE Messages
64.IDX1-> Port Maintenance in IDoc Adapter
65.IDX2-> Meta Data Overview in IDoc Adapter
66.WE05-> IDoc Lists
67.WE02-> Display IDoc
68.WE19-> Test tool
69.WE09-> Search for IDocs by Content
70.WE20-> Partner Profiles
71.WE21-> Port definition in XI
72.SE16-> Data Browser
73.SE93-> Maintain Transaction Codes
74.SM30-> Call View Maintenance
75.SU01-> User Maintenance
76.SM02-> System MessagesSWXF_PBUILDER -> for Detail BPM Process
SMQS - > to register the destination in QOUT scheduler
WEOUTQUEUE - > to start the queue processing
SMQR - > to register the queue
Idxpw - > to activate the IDOC message package
IDXP - > to monitor the message packages.

Click here for more topics on SAP BASIS
Click here for more topics on SAP Enterprise portal
Click here to Earn Money online for free
Other Useful SAP Websites

What is SAP Basis?

2009-02-10T10:42:00.002-08:00

Click here for more topics on SAP BASIS

Click here for more topics on SAP Enterprise portal

Click here to Earn Money online for free

Other Useful SAP Websites

What is SAP?

"SAP" stands for Systems, Applications, and Products in Data Processing. In 1972, five former IBM employees founded SAP. Their vision was to develop standard application software for real-time processing and to provide customers with the ability to interact with a common corporate database for a comprehensive range of applications. Gradually, the applications have been assembled and today many corporations, including IBM and Microsoft, are using SAP products to run their own businesses. SAP is a world leader in business solutions, offering comprehensive software and services that address the unique needs of customers around the world.

SAP applications, built around their latest R/3 system, provide the capability to manage financial, asset, and cost accounting, production operations and materials, personnel, plants, and archived documents. The R/3 system runs on a number of platforms including Windows 2000 and uses the client/server model. The latest version of R/3 includes a comprehensive Internet-enabled package.

SAP has recently recast its product offerings under a comprehensive Web interface, called mySAP.com, and added new e-business applications, including customer relationship management (CRM) and supply chain management (SCM).

As of January 2007, SAP, a publicly traded company, had over 38,4000 employees in over 50 countries, and more than 36,200 customers around the world. SAP is turning its attention to small- and-medium sized businesses (SMB).

What is SAP Basis?

Basis is a business application software integrated solution. Simply, Basis is the administration of the SAP system.

A set of middleware programs and tools that provide the underlying base that enable applications to be interoperable across operating systems. SAP Basis includes a RDBMS, GUI, and client server architecture. Beyond the interface aspect of Basis, it also includes such components as a data dictionary as well as user and system administration.
It's a piece of middleware which links the application with the database and the operating system. Basis is most commonly associated with the GUI interface to the SAP, and the Basis administrator is an SAP, professional who is responsible for configuring the SAP environment, including the GUI screens and SAP application servers.
Basis Administrator administers the SAP application using the tools or transactions available under Basis component. Normal functions like creating user, assigning access rights, backup, restore, check the performance are some of the transaction available under Basis component in SAP.

Click here for more topics on SAP BASIS
Click here for more topics on SAP Enterprise portal
Click here to Earn Money online for free
Other Useful SAP Websites

To visit Home page please click

Handling roles easily in SAP

2009-02-10T10:42:00.001-08:00

Handling Roles Easily

Use Download/ Upload feature:

While running PFCG, Type the name of the desired role, and from the Role menu on the top, you can use Download or Upload:
• Download: will create a file in the local machine. This will save all of the settings of that role, including the T-Codes and values at object level in the profile generator.
• Upload: will upload into the SAP system, the previously saved role. You might be required to attach Users in this role and generate the profile once again.
You can use these features in cases:
• If you want to have a backup of role before making changes,
• Or you need to create the same role in a different client or different system. It will reduce the efforts of creating new role or transporting the role.

B. Easy comparison of roles (PFUD):
Many times the Role Comparison (Profile match up) is required after the transport of roles. One usually does it from PFCG for each role individually.

Audit of Locked T-Code/ Compare User

2009-02-10T10:41:00.002-08:00

Audit of Locked T-Code/ Compare User

A. Report for audit of Lock Transaction codes:
The ABAP report rsauditc gives you the facility to see all the transaction codes which are locked in SAP system:
• Usually we find out the same by displaying the contents of Table TSTC. This report offers you a better output and a good selection screen.

B. Easy comparison of roles (PFUD):
The T-Code S_BCE_68001430 allows comparing the authorizations of 2 different users. This might be handy at certain places.

SAP ENQUEUE ANALYSIS

2009-02-10T10:41:00.001-08:00

SAP ENQUEUE ANALYSIS

A Brief Explanation on Oracle Wait Events :

At any given moment, when an Oracle process that is not busy, it would be waiting for one of the events to occur. These events are known as Oracle wait events. Suppose an application has submitted a COMMIT statement and the server process is waiting for the LGWR process to signal that the redo log buffer has been flushed to disk. This wait event is called "log file sync." Another dedicated server process might be waiting for a row-level lock on the INVOICES table to be freed so that a SELECT FOR UPDATE statement can continue. That wait event is called "Enqueue."
It is very beneficial that Oracle is diligent about tracking wait event information and making it available to DBAs. We call this the "wait event interface."
Oracle10g has brand-new wait events and the database kernel now captures statistics on more than 800 specific wait events. These new wait events are the result of Oracle breaking-out their latch waits into their individual components and breaking-out enqueue waits (locks) into a finer level of granularity.
Some of the oracle views available are given below :
V$ACTIVE_SESSION_HISTORY - Displays the active session history (ASH) sampled every second.
DBA_HIST_ACTIVE_SESS_HISTORY - Displays the history contents of the active session history.
DBA_HIST_SNAPSHOT - Displays snapshot information.
DBA_HIST_SQL_PLAN - Displays SQL execution plans.
DBA_HIST_SQLTEXT - Displays the text of SQL statements.
DBA_HIST_SYSTEM_EVENT - Displays historical information on total waits for an event.
ENQUEUE ANALYSIS with ORACLE WAIT EVENTS :

Starting from Oracle 10g, with the introduction of AWR (Automatic workload repository) functionality, we can analyze the past lock wait situations and in many times can find out the root cause of the issue. However, the default retention period for AWR data is seven days.
The sql statements mentioned below can be executed in any of the following methods.
a) At Oracle level.
b) In SAP, using RSORADJV report.
c) In SAP, Tx. ST04n -> Additional Functions -> Arbitrary Monitoring ( Join-Select)
d) In SAP, new kernel version, Tx ST04 -> Additional Functions -> SQL Command Editor.

1. Sql Statement to Check the Distribution of different Oracle Wait Times of the System

SELECT
EVENT,
TOTAL_WAITS,
TIME_WAITED,
AVG_MS,
ROUND(RATIO_TO_REPORT(TIME_WAITED) OVER () * 100) PERCENT
FROM
( SELECT
SUBSTR(EVENT, 1, 30) EVENT,
TOTAL_WAITS,
TIME_WAITED,
ROUND(TIME_WAITED_MICRO / TOTAL_WAITS / 1000, 2) AVG_MS
FROM V$SYSTEM_EVENT
WHERE
WAIT_CLASS != 'Idle' AND
EVENT NOT IN
('db file parallel write', 'log file parallel write',
'log file sequential read', 'control file parallel write',
'control file sequential read', 'Log archive I/O')
UNION
SELECT 'CPU' EVENT, NULL, VALUE, NULL
FROM V$SYSSTAT
WHERE STATISTIC# = 12
ORDER BY 3 DESC)
WHERE ROWNUM <= 10;

Explanation:
This sql statement gives an overview how the database resources are being utilized. And the other wait events which are not relevant from the view of SAP performance are ignored.

Example:
In the example, it shows that since start of the system, 11% of the oracle server time was used for enqueues, which is much higher than normal and could have significant impact on the system performance. This needs to be investigated further for the root cause.

2. Sql Statement to check the Enqueue Peak Time.

SELECT
TO_CHAR(END_INTERVAL_TIME, 'YYYY-MM-DD HH24:MI:SS')
END_INTERVAL_TIME,
TOTAL_WAITS,
TIME_WAITED_MICRO,
ROUND(DECODE(TOTAL_WAITS, 0, 0, TIME_WAITED_MICRO /
TOTAL_WAITS / 1000), 2) AVG_WAIT_MS
FROM
( SELECT
HSS.END_INTERVAL_TIME,
HSE.EVENT_NAME,
HSE.TOTAL_WAITS - LAG(HSE.TOTAL_WAITS, 1) OVER
(ORDER BY HSS.SNAP_ID) TOTAL_WAITS,
HSE.TIME_WAITED_MICRO - LAG(HSE.TIME_WAITED_MICRO, 1) OVER
(ORDER BY HSS.SNAP_ID) TIME_WAITED_MICRO
FROM
DBA_HIST_SYSTEM_EVENT HSE, DBA_HIST_SNAPSHOT HSS
WHERE
HSE.SNAP_ID = HSS.SNAP_ID AND
HSE.EVENT_NAME = 'enq: TX - row lock contention'
ORDER BY
HSS.SNAP_ID DESC
)
WHERE
TOTAL_WAITS >= 0;

Explanation:
This sql statement gives the information of the enqueue situation in the system during different time periods. It queries the DBA_HIST_SYSTEM_EVENT and DBA_HIST_SNAPSHOT views for the enqueue event ‘enq:TX – row lock contention’.

Example :

Here, we can observe that there have been high number of lock waits during the time period ending 03:00:00 and 4:00:00 on 2008-07-10. So we need to analyze further on this time period and try to find out what happened in the system during this time.

3. Sql Statement to check which enqueue waits occurred during a given time period.

SELECT
TO_CHAR(ASH.SAMPLE_TIME, 'YYYY-MM-DD HH24:MI:SS')
SAMPLE_TIME,
ASH.SESSION_ID,
ASH.BLOCKING_SESSION,
O.OBJECT_NAME,
S.SQL_TEXT
FROM
DBA_HIST_ACTIVE_SESS_HISTORY ASH,
DBA_HIST_SQLTEXT S,
DBA_OBJECTS O
WHERE
ASH.SQL_ID = S.SQL_ID (+) AND
ASH.CURRENT_OBJ# = O.OBJECT_ID (+) AND
ASH.EVENT like 'enq: TX - row lock contention' AND
ASH.SAMPLE_TIME BETWEEN
TO_TIMESTAMP('10.07.2008 02:30:00', 'dd.mm.yyyy hh24:mi:ss') AND
TO_TIMESTAMP('10.07.2008 04:00:00', 'dd.mm.yyyy hh24:mi:ss') AND
ASH.SESSION_STATE = 'WAITING'
ORDER BY
SAMPLE_TIME DESC;

Explanation:
This sql statement gets the information about the enqueue waits during the mentioned time period. It queries the views DBA_HIST_ACTIVE_SESS_HISTORY , DBA_HIST_SQLTEXT & DBA_OBJECTS.

Example :

In this example, we observe that may oracle sessions were waiting for the object USR02 till 03:22:45 system time. The column ‘Blocking_session’ gives the session id which was blocking the object, in this example session ‘248’ held the object ‘USR02’.
We can try and correlate this to the other activities that happened in the system during the same time period. In this example scenario, we found a batch job running during this time which was caused the lockwait situation.

4. Sql Statement to check the Oracle holders during a given time period.

SELECT
TO_CHAR(ASW.SAMPLE_TIME, 'YYYY-MM-DD HH24:MI:SS')
SAMPLE_TIME,
ASW.BLOCKING_SESSION SESSION_ID,
COUNT(*) "#WAITERS",
ASH.BLOCKING_SESSION,
ASH.TIME_WAITED,
DECODE(ASH.SESSION_STATE, NULL, 'INACTIVE',
'WAITING', ASH.EVENT, 'CPU') ACTION,
TO_CHAR(SUBSTR(HST.SQL_TEXT, 1, 4000)) SQL_TEXT
FROM
DBA_HIST_ACTIVE_SESS_HISTORY ASH,
DBA_HIST_ACTIVE_SESS_HISTORY ASW,
DBA_HIST_SQLTEXT HST
WHERE
ASH.SQL_ID = HST.SQL_ID (+) AND
ASH.SAMPLE_TIME (+) = ASW.SAMPLE_TIME AND
ASH.SESSION_ID (+) = ASW.BLOCKING_SESSION AND
ASW.EVENT = 'enq: TX - row lock contention' AND
ASW.SESSION_STATE = 'WAITING'
GROUP BY
TO_CHAR(ASW.SAMPLE_TIME, 'YYYY-MM-DD HH24:MI:SS'),
ASW.BLOCKING_SESSION,
ASH.BLOCKING_SESSION,
ASH.TIME_WAITED,
DECODE(ASH.SESSION_STATE, NULL, 'INACTIVE',
'WAITING', ASH.EVENT, 'CPU'),
TO_CHAR(SUBSTR(HST.SQL_TEXT, 1, 4000))
ORDER BY
TO_CHAR(ASW.SAMPLE_TIME, 'YYYY-MM-DD HH24:MI:SS')

Explanation:
This Sql statement shows the activities of the oracle lock holders during the given time. It queries the view DBA_HIST_ACTIVE_SESS_HISTORY & DBA_HIST_SQLTEXT.

Example :

It shows which sql statements were being executed by the oracle session The status INACTIVE shows that it might have been active on SAP side during that time.

How to Create a User in SAP EP

2009-02-10T10:40:00.002-08:00

To create user in SAP Enterprise portal,

we have user administration role.

Go to User administration → Identity Management → Create UserKey in the User information .

In General Information iView: Logon ID,
Define Initial Password,
Confirm Password, Last Name, First Name, Email AddressAccount Information
iView:Key in the User Account Locked,
Start date of account Validity,
End Date of account Validity
Contact Information iView:Telephone, FAX, Mobile, Street, city, state, country, Time Zone.

Additional InformationOrganizational Unit, Position, Department.Then finally save it.

Assigning Roles to User Go to User administration → Identity ManagementSelect User, whether UME database or LDAP, User ID. Then Go.Select the User then go to Assigned RoleClick the “Modify” tabIn Available Role, Select the “Portal Role”, Name of Role (Eg: *super*)Select the appropriate role and add it. Then save it.In Assigned Role, We can see the assigned role of particular user.

Assigning Groups to User Go to User administration → Identity ManagementSelect User, whether UME database or LDAP, User ID. Then Go.Select the User then go to Assigned GroupsClick the “Modify” tabSelect whether the “Built in Company Groups or Built in Groups Adapter” and Group Name.Select the Group and add it. Finally save it.
Assigning Groups to UserGo to User administration → Identity ManagementSelect User, whether UME database or LDAP, User ID. Then Go.Select the User then go to Assigned GroupsClick the “Modify” tabSelect whether the “Built in Company Groups or Built in Groups Adapter” and Group Name.Select the Group and add it. Finally save it.

SAP Upgrade notes for download

2009-02-10T10:40:00.001-08:00

UPGRADE to ECC

Need of Upgrade : Enhancements, Functionalities, Introducing new modules and SAP is going to stop the support to the older versions

If the client or customer is not going for any other new modules or new functionalities. No need of Upgradation

The need for an Upgrade
Upgrade documentation
Upgrade tools
Phases of PREPARE
Modification adjustment
Phases of the Upgrade
Troubleshooting
Upgrade strategy
Shadow instance
Incremental conversion
Support Packages and Add-On’s
Upgrade Planning & Preparation
Customer- Based Upgrade
SAP Upgrade offerings
Appendix: Deltas in Upgrades
Appendix: Java Upgrade
Unicode conversions

First we need to download the Upgrade Master Guide from Service .SAP.com.

Component Upgrade Guide Structure:

SAP Notes for the Upgrade
Step by Step
Planning
Preparation
Upgrade process
Fallow-Up activities

Troubleshooting
Upgrade Administration
Upgrade Tools

Upgrade Tools:

1. SGEN
2. ICNV (
3. PREPARE

PREPARE: It is divided into four levels:

1. Can be started at any time
2. It is performed only once
3. Includes all checks requiring short run times
4. Including long running jobs:

- Calculate modification adjustments
- Calculate future inconsistencies in the ABAP Dictionary
- Run an extended free check

Dump the Upgrade software in the local system.

It will be in 7 directories
501 –683
xxxxx_1
xxxxx-2

Patches

PREPARE

- Upgrade Assistant
- Upgrade Monitor
- ABAP load generator (SGEN)

Before starting PREPARE Stage. We need to create one directory called PUT in /usr/sap.

Get into the first directory Master Upgrade software directory 501—683

Select the file Prepare.bat
It will Extract the some files. To extract it will ask the directory

By that time we need to give /usr/sap/put

After extracting the UA and UAGUI directories will be created in /usr/sap/put directory.

Ua.jar & UaGui.jar files are created in Ua and UaGui directories

To Start the UA Server:

/usr/sap/put/Ua> Java –cp Ua.jar UaServer (letters are casesensitive)

It will give three options 1, Server 2. Memory. 3. Status. We need to give Server. It will give ready message.Here it will open the Port 4240 on CI.

Minimise the screen.

Note: It opens the port 4241 on UA Server & Through web browser http:// : 4239

Port 4239 opens on web browser on UA Server.

Here login to Server at SAP level. Change Parameter called DIR_PUT to /usr/sap/put in RZ11.

/usr/sap/put/UaGui/UaGui.jar UaGui

It will lead to Ua Tool.

It will ask Host name

Click on Ok

It will ask User name & PSWD.

Enter User Name & Pswd ( for administrator/admin , Observer/observer)

Port number automatically come.

Now in Ua tool -à click on administrator in menu barà Select Start Prepare

Click on continue. à It will ask for Mount points give the directories path which are dump of upgradation at least two. Click on OK. It will lead to modules screen check the boxes which ever you want check.

Click on OK

Check execute and click on OK

Here it will extract the mount points and shows the errors. If any file doesn’t exist in put directory for upgrade. It will give the SAP Note number. This note will give the link for missed file software download it from Service.sap.com. store it in put directory.

Close the error message and check retry and click on OK.
It may ask for SAPup Keyword. This will be available in SAP Note which is given in error message in service market place.
It leads to check SAP & DB server details and it will asks DDIC Password & asks for confirmation. And also Batch Host.

à Max uptime processesà 2* CPUs

à R3trans processesà 2*CPUs but it should not greater than MUP.

à Max sync time 120.

Here it will ask OS PSWD

Here it will ask for Solution Manager Key. We need to provide it.

Ua tool checks all modules in the server gives the information.

If any SPDD & SPAU objects needs to adjust it will check and give you the information.

For SPDD you need to take the help from ABAPers. SPAU you skip or ignore it. SPAU will run in upgradation phases other wise you can execute it after upgradation.

We can check the Ua logs in /usr/sap/put/log/check.log.

And we need to select Upgrade method ( Downtime minimize/ Resource minimize).

Ask for archive log needs to be on/off for shadow instance. Ask for instance number. We need to give instance number which is not available with any other application server.

Here everything is Ok it will give the message as Shadow instance created.

This shadow is created in Production it self but there will not be physical instance.

This total PREPARE phase run in 367 phases. It will take time 4 hrs to 2 days that is depending on your database size.

Till here PREPARE Phase completed.

Here you take the backup of PUT directory.

After PREPARE phase one directory will be created in PUT directory called HTDOC.( which is attached to the mail as zip file)

In this directory there will be a link called Phases list.

If you click on this. It will all phases which will run in upgrade process & for each particular phase give the which log file & note number(if available) needs to check when you get the error.

All log files will be created in /usr/sap/put/log.

ICNV: ( Not Mandatory)

It is Incremental conversion of large tables. We use it for to minimize the downtime. ICNV is a transaction code. If you have any large size tables we use it. We will execute it in CI after PREPARE phase. It will show the all table large to small. We can select the tables and execute it. ICNV will copy the data from CI to Shadow but end users can work on CI.

Once ICNV copy the each record CI Table to Shadow Table. End users can modify existed records or insert the new records in those tables. At this time Modified records will one flag called “X”. Inserted records will be empty. Now the ICNV will start copying from CI Tables to Shadow Tables. But this time it will read only the records which having flags & newly inserted records. It will not read already copied records.
It will continue till downtime started.

Now the actual upgrade will start.

Now the shadow instance is having total structure of CI.

We can login to the shadow instance using DDIC user & PSWD of CI.

Here we need to create the New user id by copying the DDIC authorizations in 000 client.

Now logout from DDIC user. Anything you want to do in shadow instance you should use new user id which is created earlier.

Now go to UaGui

Click on Administrator in Menu bar -à Click on SAPup

Here upgrade will start.
It will run in 468 Phases. Ua tool will give you the full information. If any background jobs needs to run in shadow system. Any tables need adjustments. If you get any errors you can check in HTDOC/Phases list. There go to particular phase check which log file or Note needs to check. Check those things follow as per logs. Then continue upgrade process.

Some particular phase downtime will be started at the phase it will ask you take the full backup. You need take the backup of database as well as PUT directory.

You need to down the CI manually automatically Ua tool will do every thing.

In the downtime total database will copied to Shadow instance. Automatically instance will up after completion of copying. Now the shadow instance will be disabled. If you login to CI. It will show ECC 6 screen.

After successfully completion of 468 steps it will give message as “Upgrade successfully completed”.

Post Upgrade steps.

After upgrade EXE folder will be created in PUT directory. You need to replace this EXE directory with RUN directory ( Kernal).

Upgrade Application servers.

Configuring TMS

Uploading Deltas.

Execute SGEN.

SAP RFC INTERFACE

2009-02-10T10:39:00.000-08:00

A Remote Function Call is a call of a function module that is running in a different system to the calling program. You can also call a function module in the same system as an RFC; however, RFCs are usually used when the calling and called function modules are running in different systems.

In the SAP system, the RFC interface system provides this function. The RFC interface system allows function calls between two SAP systems or between an SAP system and an external (non-SAP) system.

RFC is an SAP interface protocol that is based on the Common Programming Interface for Communication (CPI-C) and allows cross-host communication between programs.

This means that ABAP functions can be called from external applications and tools, and that external applications can be called from the SAP system.
RFC means that the ABAP programmer does not have to write his or her own communication routines. For an RFC call, the RFC interface

• Converts all parameter data to the format required in the remote system
• Calls the communication routines that are required to communicate with the
remote system
• Handles errors that occur during the communication

The RFC interface is easy for the ABAP programmer to use. The processing steps for calling external programs are integrated into the CALL FUNCTION command.

To call a function module on a remote system, you must define the remote system as a destination in your calling system. You also require access authorization for the remote system.

You can administer these remote connections in the calling system. To do this, call the Display and Maintain RFC Destinations screen, either by choosing the menu path

Tools → Administration → Administration → Network → RFC Destinations or by
calling transaction SM59 directly.

The connection types and all existing destinations display in a tree structure on the initial screen. For details about all available connection types, see the documentation.

There is a search function for destinations that have already been set up. To search for a destination, choose Find and enter your selection. The system displays a list of all matching entries. You can display all available information for each entry.

To change an existing RFC destination, choose the relevant RFC destination in the menu tree and choose Change.

SAP Archive customizing settings

2009-02-10T10:38:00.000-08:00

During Archiving Customizing, you set parameters that affect the execution of data archiving. Customizing is structured into the following areas (examples are given for each):

• General Customizing (Basis Customizing)
– Defining logical path and file names
• Cross-archiving object Customizing
– Define the server group for background processing
• Archiving Object-Specific Customizing
– Sizeofanarchive file
– Settings for the delete program
You can call the Customizing settings by choosing the Customizing button on the initial screen of transaction SARA (Archive Administration,

menu path Tools → Administration → Administration → Data Archiving).
In the general Customizing (Basis Customizing, switch to the transaction FILE), you first define - if it does not already exist - a logical file path as the global path for data archiving and assign a physical path to this logical path. The logical path acts only as a placeholder for the physical path created at runtime.

You also maintain a logical file name here for naming the archive file for the archiving of application data and assign it a physical file name that is generated at runtime and used as the file name.
In Cross-Archiving Object Customizing, you can specify, among other things, whether the data archiving monitor in CCMS monitoring (transaction RZ20) should be active, or which server group is selected for background processing (this setting is new as of SAP Web Application Server 6.10).
In Archiving Object-Specific Customizing, you maintain a logical file name for the specific archiving object and settings for the delete program. You can set whether the delete program is to be automatically executed after the creation of an archive file. In this area, you also create a variant for the test run and a variant for the production run, and specify the maximum size of an archive file, among other things.

The following figure illustrates the relationship between the name of the archiving object and the stored logical and physical file and path name.

How to Monitor SAP Archive Run

2009-02-10T10:37:00.000-08:00

The actual archiving run is scheduled and processed as a background job. It selects the data objects from the database. When doing this, the integrity conditions that characterize a data object are taken into account. The system then checks whether each data object can be archived. If it can be archived, the data object is written to the archive file. If the Customizing settings specify that the delete program is to run automatically, the associated deletion run is automatically started when a file is closed.

The delete run must be separately scheduled, if the delete program is not automatically run by the settings in the archiving object-specific Customizing. When scheduling separately, you must also select the archive files, from which the data objects are to be read in the current delete run, and then deleted from the database.

An archiving run is scheduled using transaction SARA by choosing the Write button.

It is divided into four steps:
1. Create an archiving variant
2. Specify the execution user
3. Specify the start time
4. Definine the spool parameters

The data that is to be archived for the selected archiving object is specified in archiving variants. In principle, archiving variants can only be reused if the associated jobs are deleted. The definition of the variant must also specify whether it is a test run or a production run.

The user under which the archiving program is started requires at least an appropriate authorization for the authorization object S_ARCHIVE. S_ARCHIVE is the main authorization object used for data archiving. By selecting the corresponding field entries for this authorization object, you can restrict the archiving objects to be used.

The user also requires the relevant authorizations for the application transaction for which data is to be archived. As data archiving runs in the background, the user also requires authorizations for background processing (authorization object S_BTCH_JOB).

The start times to be specified for archiving jobs are the same as those for standard job scheduling.

Since job logs can become large, it is advisable to set under Spool Parameters that the log is not immediately output on the output device. The selection options are the same as the standard background printing parameters.
Monitoring an Archiving Run There are various system administration tools available to monitor archiving runs:
. Background processing tools
. Joblogs
. Spool lists (if created)
. System monitoring tools
. Data Archiving Monitor in the CCMS monitor sets
A log is created during an archiving run. If the application creates a specific log, this is used; otherwise, the standard log is used. The standard logs contains the number of archived data objects, the affected tables, the number of processed table entries, and the file sizes. The contents of the archiving can be stored to document level in application-specific logs.

You can trace the process of an archiving run with the monitoring of the background work processes using the transaction Simple Job Selection (transaction code SM37).
By choosing Job Overview, you can move directly from the initial screen of transaction SARA to transaction SM37. By choosing Management (after you have maintained an appropriate archiving object on the initial screen of transaction SARA), you can display a short log file of an archiving run from transaction SARA.

In addition, there is a specific data archiving monitor (monitor Data Archiving in the monitor set SAP CCMS Monitor Templates) in the CCMS monitor sets (transaction RZ20). It is intended for system administrators, so that they can monitor archiving runs in their familiar environment, the CCMS monitor. You can use the Data Archiving monitor to obtain an overview of the archiving objects in the system for which there are already runs. You can use the cross-archiving object Customizing to activate or deactivate it.

SAP ABAP Dump procedure

2009-02-10T10:36:00.000-08:00

ABAP programs are checked statically when they are created and dynamically when they are running. Error states, which are not statically predictable and only occur at runtime are dynamically identified by the ABAP runtime environment. States of this type lead to exceptions. If an exception is not handled or cannot be handled, a runtime error occurs. If a runtime error occurs, the ABAP runtime environment terminates the execution of the program, generates a short dump and branches to a special screen for analyzing the short dump. You can also find short dumps in transaction ST22

or by choosing the menu path Tools → ABAP Workbench → Test → Dump Analysis.

A short dump is divided into different sections that document the error. The overview shows what other information is output in the short dump, such as contents of data objects, active calls, control structures, and so on. You can branch to the ABAP Debugger at the termination point from the short dump view. The following different error situations exist:

. Internal Error

The kernel identifies an error state. In this case, notify SAP.
. Installation and Environment/Resource Error
In this case, an error occurred that was caused by incorrect system installation or
missing resources (such as the database being shutdown).
. Error in Application Program
Typical causes of errors are:
. Content of a numerical field not in the correct format
. Arithmetic overrun
. An external procedure is not available
. Type conflict when transferring parameters to an external procedure
By default, short dumps are stored in the system for 14 days. The transaction for managing short dumps is ST22. You can delete short dumps in accordance with a time specification using the Reorganize function, which you can call by choosing Goto → Reorganize. You can save a short dump without a time limit using the Keep function, which you can choose under Short Dump → Keep/Release.
If problems that you cannot solve yourself occur with ABAP programs, you can send an extract of the short dump to SAP. A short dump is the basis on which the SAP Hotline and remote consulting solve problems.
. If a runtime error occurs, a short dump is generated. You can use transaction ST22 to analyze this short dump.
. Dump data is stored in the database.
. Dump data can be reorganized.
. Individual short dumps can be flagged for retention.

SAP System Trace

You can use the system trace to record internal system activities. The system trace is primarily used if an authorization trace is to be created. SAP recommends that you use the system log or the developer trace for system monitoring and problem analysis.

You can call the SAP System Trace using transaction ST01 or by choosing the menu path Tools → Administration → Monitor → Traces → System Trace. You can also use transaction ST01 to display the inactive trace file.
You can use the SAP system trace to monitor the following components:
. Authorization checks
. Kernel functions
. Kernel modules
. DB accesses (SQL Trace)
. Table buffers
. Lock operations (client-side)
You select the components to be logged on the initial screen. If the trace is activated for the authorization check, all authorization checks performed by the system are recorded. During the evaluation, you can identify which authorizations the system checked at which times. The following detail information is also provided: Date, time, work process number, user, authorization object, program, line, number of authorization values, authorization values.
You can use the SQL Trace to follow how the Open SQL commands in reports and transactions are converted to standard SQL commands and the parameters with which the SQL commands are transferred to the database system in use. The results of the SQL command are also logged, such as the return code and the number of records found, inserted, or deleted by the database. Logging the execution time and the callpoint in the application program allows you to perform more advanced evaluations.
With the enqueue trace, you can follow which lock instructions the SAP system performs on which lock objects, and which parameters the system uses for these locks.
The program that triggered the lock, the owner of the lock, and the time that the enqueue server required to release the lock again are all also logged in the trace file.
You can use the RFC trace to follow which remote calls the SAP system executes, and the instance on which these calls are executed. You can see from the trace which function modules were called remotely by the program that is to be analyzed, and whether the RFC was successfully executed. The total time required for the execution of the remote call and the number of bytes sent and received during the RFC are also logged in the trace file.

Earn $300 Daily from Work from Home Jobs

2009-02-10T10:35:00.000-08:00

Spend 30 mins per day and earn $300/ daily.

Easy and outstanding online earning jobs. No need to work every day, work only in spare time. Earn $300 /day. Click here for more info.

World is moving online, the number of peoples who are making money online are also increasing day by day. As with any task that generates revenue it is not as easy at it sounds like because if it had been so, it would have been tried out by too many people.It is not simple and neither is it uncomplicated. However there is some easier ways of making money online that we have been trying to help our viewers. It is also which you might have already guessed like blogs, Online Surveys, Data entry jobs, etc.Here we tried to show some money making tips, which are easy and helps in making more money with less effort.

Click n Earn Money: Easy and High Paid online Jobs

Signup for free Bux,to :You get paid to click on ads and visit websites. The process is easy! You simply click a link and view a website for 30 seconds to earn money. You can earn even more by referring friends. You'll get paid $0.01 for each website you personally view and $0.01 for each website your referrals view. Payment requests can be made every day and are processed through Alert Pay. The minimum payout is $10.00. Click here to Signup for free

jai ganesha

2009-02-10T10:14:00.001-08:00

jai ganesha

Privacy Policy for www.sapbasisjobsinindia.blogspot.com

2009-02-01T07:30:00.000-08:00

Privacy Policy for www.sapbasisjobsinindia.blogspot.com/

If you require any more information or have any questions about our privacy policy, please feel free to contact us by email at skumar.basissupport@gmail.com.

At www.sapbasisjobsinindia.blogspot.com/, the privacy of our visitors is of extreme importance to us. This privacy policy document outlines the types of personal information is received and collected by www.sapbasisjobsinindia.blogspot.com/ and how it is used.

Log Files
Like many other Web sites, www.sapbasisjobsinindia.blogspot.com/ makes use of log files. The information inside the log files includes internet protocol ( IP ) addresses, type of browser, Internet Service Provider ( ISP ), date/time stamp, referring/exit pages, and number of clicks to analyze trends, administer the site, track user’s movement around the site, and gather demographic information. IP addresses, and other such information are not linked to any information that is personally identifiable.

Cookies and Web Beacons
www.sapbasisjobsinindia.blogspot.com/ does not use cookies.

Some of our advertising partners may use cookies and web beacons on our site. Our advertising partners include Google Adsense, Linkshare, .

These third-party ad servers or ad networks use technology to the advertisements and links that appear on www.sapbasisjobsinindia.blogspot.com/ send directly to your browsers. They automatically receive your IP address when this occurs. Other technologies ( such as cookies, JavaScript, or Web Beacons ) may also be used by the third-party ad networks to measure the effectiveness of their advertisements and / or to personalize the advertising content that you see.

www.sapbasisjobsinindia.blogspot.com/ has no access to or control over these cookies that are used by third-party advertisers.

You should consult the respective privacy policies of these third-party ad servers for more detailed information on their practices as well as for instructions about how to opt-out of certain practices. www.sapbasisjobsinindia.blogspot.com/'s privacy policy does not apply to, and we cannot control the activities of, such other advertisers or web sites.

If you wish to disable cookies, you may do so through your individual browser options. More detailed information about cookie management with specific web browsers can be found at the browsers' respective websites.

SAP Basis Jobs in india

2009-01-01T11:36:00.000-08:00

Job Title: SAP Basis Jobs in India-Basis
Job ID: BASIS
Company: cybertech systems and software Inc
Position Type: Permanent
Pay Rate: $40-45/hr
Date Posted: Apr-08-09

Browse Similar Postings

By employer...
- Jobs from cybertech systems and software Inc

By location...
- Tech jobs in Trevose, PA
- Tech jobs in Pennsylvania
- ERP jobs in Pennsylvania
- SAP Basis Jobs in India jobs in Pennsylvania

By category...
- SAP Basis Jobs in India-Basis jobs
- SAP Basis Jobs in India jobs
- ERP jobs
- Tech jobs

By career level...
- Mid-level SAP Basis Jobs in India jobs
- Mid-level ERP jobs
- Mid-level Tech jobs

ShareThis
Job Description
Subject-area expert in SAP Basis Jobs in India Basis from SAP Basis Jobs in India R/3 4.6C to Net weaver 7.0. This technical expertise and his extensive experience is used in SAP Basis Jobs in India maintenance and support. Responsibilities include managing software life-cycle and providing SAP Basis Jobs in India BASIS support globally in 24x7 environments
Candidate Profile :
Provide on-call 24x7 support for SAP Basis Jobs in India Basis issues •
Co-ordinate and interact with support client on site.
• Ensure smooth support and delivery for support client onsite and from off shore.
• Solid experience in planning and execution of new SAP Basis Jobs in India installations. Related database experience is mandatory.
• Extensive experience applying Support Packages, Kernel Upgrade, OSS, CTS, Client / Users Maintenance, Printer / Spool Management, daily PRD monitoring & support
• High level experience in Oracle and MS SQL Database administration.
• Ability to perform tuning, daily monitoring and troubleshooting.
• Extensive experience with Monitoring Key Performance Indicators, database, all application processes, interfaces and tuning the required parameters and necessary actions for better performance
• Experience with setting up production system/database copy, system refresh
• Experience working with Br*Tools.
• Transport Management
• Familiarity with SAP Basis Jobs in India R/3 data archiving including administration and backend integration with 3rd party tools.
• Experience with helpdesk, resolving ticket issues and troubleshooting support problems which include problems like printer problems, SAP Basis Jobs in India GUI problems, transport problems, backup failure problems etc
• Ability to coordinate, troubleshoot, and support through different time zones
• Provide dump analysis and trouble-shooting within SAP Basis Jobs in India
• Perform SAP Basis Jobs in India administration tasks (system messages, system logs, etc.)
• Troubleshoot SAP Basis Jobs in India GUI issues
• Log problems with OSS
• Apply changes to SAP Basis Jobs in India objects in OSS
• Perform database sizing tasks using SAP Basis Jobs in India tools
• Perform database performance monitoring and tuning
• Perform database error analysis according to SAP Basis Jobs in India specifications
• Hands on Unix and Windows OS management
SAP Basis Jobs in India Skill Set
Databases : MS-SQL Server 2005,
Oracle9i, 10g.
Operating systems : Windows 2003, HP-UXSAP Basis Jobs in India Products : SAP Basis Jobs in India R/3 4.x, ECC 5.0/6.0, SM
4.0/7.0, EP 6.0, Net weaver
2000/2004s, Bi 7.0