How to install and configure the SAPGUI in Linux OS?

Unknown

Prepare these stuffs before you can proceed to installation :

1) You have to make sure that your Linux system has been installed with JRE (Java Runtime Environment) from SUN Microsystem (http://java.sun.com).  If you don't have it, just download it from http://java.sun.com/.  Some of linux distros such as Fedora, Ubuntu, OpenSuSE etc using JRE from GNU called GIJ (GNU for Java). We can’t use this JRE.  We need to replaced it.  I’ll show you how to changed it later.

2) You also need SAPGUI for Java installer. You can download it freely from ftp://ftp.sap.com.

After you have all prerequisite, you can proceed to next step to extract and change your JRE.  This step is valid for Fedora, Ubuntu, and OpenSuSE. 
1) Logon as root

2) Copy your JRE installer file to /opt folder.Please use .bin extention file.

3) Change file permission if needed to executable. Use this command : #chmod 755 jre-1.xxx.bin (xxx = refer to JRE version you’re using).

4) Extract JRE files. Use this command : #./jre-1.xxx.bin

5) Install JRE you just extracted inside alternatives system. Use this command : #/update-alternatives –install /usr/bin/java java /opt/jre1-xxx/bin/java 2

6) Update java command configuration on alternatives system. Choose java number 2 because usually GIJ had number 1 position. Use this command : #update-alternatives –config java

7) Use this command to verify your JRE configuration. You can use this command : #java -version

8) If you get something like this on your screen then you are succeeded. java version “1.6.0"

Java(TM) SE Runtime Environment (build 1.6.0-b105)

Java HotSpot(TM) Client VM (build 1.6.0-b105, mixed mode, sharing)

After you finish this step, you can proceed to SAPGUI for Java installation. 

1) Logon as root

2) Use this command (on terminal) to install SAPGUI for Java. #java -jar PlatinGUI-Linux-xxxx.jar (Use the latest version).

3) Installed on /opt folder as default (usually on /opt/SAPClients folder)

Next step is configure your SAPGUI for Java and try to test to SAP R/3 server connection.

1) Run executable file called guilogon (reside on /opt/SAPClients/SAPGUI700rev1/bin). It will pop up SAPGUI for Java window.

2) Click New button.

3) Fill the Description column as you like.

4) Click Advanced Tab.

5) Give check (V) to Use Expert Configuration

6) Fill the connection string. If your server using load balancing configuration, use this connection string conn=/M/(IP_Address_Message_Server)/S/36(system_number)/G/(nama_group) and use this connection string configuration if your SAP R/3 server are not using load balancing system, conn=/H/(IP_Address_server_SAP)/S/32(system_number).

There you go! 
Now, you can use your SAPGUI for Java to access your SAP R/3 server.
Read More
6:27 PM ,

Difference Between System Copy and Client Copy in SAP

Unknown

Read More
6:13 PM ,

DB Refresh Steps in SAP

Unknown
PROCEDURE FOR DB REFRESH:

1)      Take full offline backup of database using BRTOOLS/DB13.
Brbackup –u –p init<sid>.sap –d disk –t offline –m all
2)      Generate the control file
SQL> alter database backup controlfile to trace;
Get the trace file from user trace directory and modify the file as following
  1.    Rename the file to control.sql.
  2.  Remove all the content above the line  STARTUP NOMOUNT and below CHARACTER SET URF8;
  3.    Replace NORESETLOGS with RESETLOGS.
  4.    Replace ARCHIVELOG with NOARCHIVELOG.
  5.    Replace S_sid with T_sid.
3)      Change the S_sid with T_sid in b***.afd backup log file.
4)      Change the S_sid with T_sid  in the first file of backup folder and rename to target sid.
5)      Restore the database using the command
Brrestore –u 0b b***.afd -d disk –k yes -m all
6)      Login to database start the database(startup nomount).
7)      Run @contro.sql file.
SQL>select status from v$instance; it is in mounted state.
SQL>alter database open resetlogs; now it goes to open status.
SQL> select username from dba_users;
8)      Now copy ORADBUSR.SQL file from installation folder copy to sap backup directory and run.
SQL> @ORADBUSR.SQL
Enter value for         1: schema owner ID SAPSR3
                                2: file system NT
                                3: host name
                                4: SAP SID
Now again check the users
SQL>select username from dba_users;
Now you can see target system users only. Remove the source system users.
9)      Drop user
OPS$HOSTNAME\SIDADM  cascade.
10)   Now provide the permission to the target system users.
SQL> grant connect sapdba to “OPS$Hostname/SIDADM”;SAPSERVICESID;
SQL>grant dba to  “OPS$Hostname/SIDADM”;SAPSERVICESID;
11)   Now start the SAP system and is working or not.

Read More
11:01 AM , ,

what is Workprocess in SAP (SM50)

Unknown
Transaction code SM50 is used to monitor and manage work processes. In the work process overview, you can:
• End an ABAP program that is running.
• Debug an ABAP program that is running.
• Cancel a process (with or without core) – long running jobs
• End a session
• Activate/deactivate the restart option after an error
• Execute various functions for the process trace

No.

The internal ID number of a process. Used to identify messages that belong to a work process in the system log.

Type

• DIA: Work process for executing dialog steps in user transactions.
• UPD: Update process for making U1 (time-critical) database changes.
• UP2: Update process for executing U2 (not time-critical) database changes.
• ENQ: For locking or releasing SAP lock objects.
• BTC: For processing background jobs.
• SPO: For spool formatting processes.

PID

Process ID of the work process (on the operating system).

Status

• Running (executing a request)
• Waiting (idle and waiting for work)
• Hold (held for one user) is not an abnormal state, but a work process can only serve a single user. If too many processes are in hold status, then system performance suffers. You can use the Reason column to identify work processes with status hold that can be released.
• Stopped (aborted with Restart set to No)

Reason

If a work process is in hold status, the reason is displayed. Typical reasons are: Debugging, CPIC activity, locks, updates, GUI (system waits for response from the SAPGUI front-end program, for example, for a remote function call (RFC)). You may also see PRIV (PRIVate use) as a reason for holding a work process. PRIV indicates that a work process is reserved for a single user for memory management use. The work process has exceeded the limit of the SAP memory that is used by other processes. The process is held as long as the current user requires local memory.

Start

Indicates whether the process should be automatically restarted if a process ends prematurely. You can change the restart status of a process by choosing Process > Restart after error > Yes/No. Normally, leave Restart set to Yes. If a work process aborts during its startup, the system automatically sets Restart to No. This measure protects against endless attempts to restart a process if a database system is not available, or another serious problem is affecting the system. After correcting the problem, you can change Restart to Yes so that the system starts the work processes.

Error

Indicates how many times a work process has aborted.

Sem

Indicates the number of the semaphore for which a work process is waiting. Normally, this field should be empty. If one or more semaphore numbers frequently appears, evaluate the performance of your system using the Performance Monitor.

CPU

Cumulative CPU time since the start of a work process.

Time

Indicates the elapsed time used by a work process for the dialog step that it is currently processing
• Report – ABAP program or report that is currently being executed
• Client – Client for the session that is currently being executed
• User – User whose request is currently being processed
• Action – Action that is being executed by the current program. The actions displayed are recorded by the SAP Performance Monitor. The Performance Monitor must be active (SAP profile parameter stat/level = 1(default)) for actions or database table accesses to be displayed.
• Table – If the database is being accessed, this column shows the name of the table being accessed.
Read More
9:30 AM ,

What SAP Fiori

Unknown
What is Fiori?

           SAP Fiori is a set of apps, newly written by SAP, that address the most broadly and frequently used SAP functions, such as workflow approvals, information lookups, and self-service tasks. They provide simple and easy-to-use access across desktops, tablets, and smartphones.

To get a quick idea of what Fiori is all about, watch this short video with examples of SAP Fiori apps for managers.

Fiori is more than just a new user interface. It is a set of cross-device applications that, among other things, allow users to start a process on their desktop and continue it on a tablet or smartphone. SAP is developing its Fiori apps on its latest user interface framework, SAPUI5.
SAP lists three types of Fiori apps: 
  1. Transactional apps, which allow users to perform SAP transactions on mobile devices as well as desktops. For instance, there is a transactional app for creating a leave of absence request and another for approving a purchase order.

  2. Fact sheets, which display information about key business objects in SAP. For example, there is a fact-sheet app for viewing a central purchase contract; it allows users to also drill down into related entities, such as vendor contacts, items under contract, and terms.

  3. Analytical apps, which allow users to display key performance measures and other aggregate information about the business.
A complete list of current Fiori apps is available on SAP's website. So far, SAP has released two waves of Fiori apps of 25 apps each, with additional waves under way.

It is important to note that Fiori will never be a comprehensive user interface replacement for SAP. The reason for this is that most SAP ERP processes cannot be performed with Fiori, not now or in the future. Those SAP processes are simply too complex in their design and do not lend themselves to deployment on a smart phone or tablet. Everyone knows, for example, that you can do much more with the desktop version of Netflix than you can on the Netflix iPhone or iPad app. Likewise, it is difficult to take a complex SAP process and dumb it down to the point where you can deploy it on a smartphone.

Complicating things, Fiori is not the only development effort involving SAP's user interface. SAP has also released a product dubbed Screen Personas, which allows users to customize standard SAP screens to their liking. For example, using Personas, a user could remove fields of no interest or change the placement of fields on the screen.


Read More
6:09 PM ,

Display all tables in SAP with DD02T

Unknown

  • Execute SE16,
  • Enter DD02T
  • Click display table contents
  • Enter table name (eg: AGR* or GRAC*)
  • Execute


Read More
5:34 PM , ,

Types of RFC communication in SAP?

Unknown
There are mainly 4 types of RFC communication in SAP.

  • Synchronous RFC
  • Asynchronous RFC
  • Transactional RFC
  • Queued RFC

Synchronous RFC (sRFC) :  In this type of RFC communication, the calling program waits until the requested processing step on the remote system has ended and then continues to work locally.
In other words, both the systems involved must be available at the time the call is made.

Asynchronous RFC (aRFC) : In this type of RFC communication, the calling program gives the request to the remote system and immediately continues to work locally. The requested processing step is executed on the remote system in isolation.
If the remote system cannot be reached at the time of the call, the asynchronous calls of the RFC client are lost

Transactional RFC (tRFC) : This type of RFC communication is similar to asynchronous RFC but by allocating a transaction id(TID)  it guarantees  that if a request is sent several times because of network problems  it is processed only once. Unlike asynchronous RFC,  in Transactional RFC the remote system does not have to be available at the moment the RFC client program start the call. The data is held in the source system until the target system is available.
The report program RSARFCSE is called in the background at regular intervals and tries to place the unsuccessful requests, identified by their transaction id again.

Queued RFC (qRFC) : This RFC communication is an extension to the transactional RFC. In this method, all the requests are queued up(inbound queue and outbound queue) and are processed in a sequence only if it is certain that all preceding calls are processed correctly. This method guarantees that all the requests are processed in the sequence in which they are received.
This type of RFCs will be used in SCM (APO) systems for CIF queues etc where requests have to be processed in an order.
Read More
9:17 AM ,

What are the SAP Profiles?

Unknown
SAP R/3 systems uses  Profiles  to define the properties of an SAP R/3 Instance such as the type and number of work processes, the size of main memory reserved for SAP R/3 and various parameters like multiple logon, idle time out value. 
 3 types of profiles in SAP.

  • DEFAULT.PFL (known as System Profile)
  • Start Profile
  • Instance Profile

START PROFILE :   Unlike default profile, the start profile is specific to an instance. It means if there are 5 application servers each will have one separate start profile with the settings specific to an instance.
The startup process of the SAP system is controlled by the start profile that is read by the start program [sapstart]. Here the services(eg: message, gateway, dialog , batch etc) that are to be started are listed. Hence every instance will have separate start profile.
In other words, the start profile determines how, where and under what name individual SAP R/3 services and processes are to start.
The naming convention of START PROFILE will be as below :
START_<instance><instance_number>_<host_name>
Eg: START_DVEBMGS00_prdserv4
For the start profile default names are assigned during the installation of an instance based on the services that are running on the instance. For example, DVEBMGS in the start profile above confirms that following services are available for that instance.
D – Dialog
V – Update
E – Enqueue
B – Batch
M – Message
G – Gateway
S -  Spool

INSTANCE PROFILE :   Like start profile, Instance profile is specific to an instance. It means if there are 5 application servers each will have one separate start profile with the settings specific to an instance.
 The runtime environment of the instance is configured in the instance profile.  In instance profile parameters specific to an instance can  be set like auto gui logout time(rdisp/gui_auto_logout), number of various workprocesses (rdisp/wp_no_dia),  memory related parameters like abap/buffer_size, em/initial_size_MB, rdisp/PG_SHM, rdisp/ROLL_SHM etc
The naming convention for the instance profile will be as below :
<SID>_<instance><instance_number>_<hostname>
Eg :  SQ1_DVEMBSG00_prdsapk1

During the installation of an SAP R/3 system, the profiles are created with standard values. Later it  is Basis administrator’s responsibility to tune the parameters.
The source code of the SAP Kernel already sets standard default values for most of the system parameters. However, you must specify some specific details like computer name, system name and distribution of resources in the profiles.
The SAP profiles are read during the startup of an instance. The values defined in the system profile (ie. DEFAULT.PFL) overwrite the standard settings in the source code. The values defined in the instance profile overwrites the parameter values of DEFAULT.PFL for the instance.

In case of any changes to System Profile ( DEFAULT.PFL or Default Profile), you must restart all the instances of the SAP system as this is common for all instances.
However in case of any changes to instance profile, it is sufficient to take restart of only that particular instance for the changes to take effect.

Sequence of SAP profiles that are read while starting SAP system :
  • First start profiles of various instances are read by the sapstart program
  • Secondly Default profile is read
  • Finally, instance profiles of various instances are read.

Read More
9:14 AM ,
Subscribe to: Posts ( Atom )

Histats

Total Pageviews