SAP BASIS ADMINISTRATION

Tcode to find all the tables in SAP

How to find all the tables in SAP

To find the list of all the tables in SAP, Goto transaction SE16 and enter the below mentioned table name to get the list of SAP Tables.

Table Name - Description

D010TAB - All SAP Table with Report Name
DD02L - All SAP tables
DD02T - All SAP table texts

for eg : If we want to find all the SAP tables with text, then Goto SE16 tcode and enter table name as " DD02T" and press " Enter".

In the next screen , If you want to know the information about USR tables then mention from and to info and enter number of hits and press execute button

Select the Table and press display to get the details of the table.

0 comments

Adding SAP tcode to Favorites

1. In the SAP Easy Access screen, choose Favorites _ Insert Transaction and enter SIMGH.

The entry IMG hierarchy maintenance appears in your favorites list.

2. Choose IMG hierarchy maintenance.
The Edit IMG structure screen appears.

3. In the IMG Structure field, choose the F4 options.

4. In the Title field, enter Title eg:- Salary Packaging and choose Execute.

5. Select Salary Packaging and choose Favorites.
The IMG structure Salary Packaging is now in your favorites list.

6. Select Salary Packaging and choose Display IMG Structure.

0 comments

Execute OS level Commands from SAP

To Execute OS Commands from SAPGUI

Goto transaction SE38 or SA38

Enter the report/Program name as " RSBDCOS0".

Executing the report will takes you to the screen pasted below.

In the yellow field enter the command you want to execute and press enter

for eg in Unix, enter pwd in the above screen and press enter

1 comments

Prohibit SAP users from choosing passwords

Most of the Password rules can be set using profile parameters.

We can also prohibit users from choosing passwords that you do not want to allow like company name etc.

1) If you want to prohibit the use of a password, enter it in table USR40. From SM30 tcode maintain the table USR40. In USR40, you can specify impermissible passwords.

There are two wildcard characters(* and ?):

• ? stands for a single character
• * stands for a sequence of any combination characters of any length. For example,
• 123* in table USR40 prohibits any password that begins with the sequence "123."
• *123* prohibits any password that contains the sequence "123."
• AB? prohibits all passwords that begin with "AB" and have one additional character: "ABA", "ABB", "ABC" and so on.

Note: SAP default value is that all passwords, except PASS and SAP* are allowed.

2) Apart from this following settings are predefined by SAP.

• The password cannot be more than 40 characters long Until SAP NetWeaver 6.40 (inclusive), passwords could not be more than 8 characters long.
• The first character may not be an exclamation point (!) or a question mark (?).
• The first three characters cannot all be the same.
• The password can only be changed after the old password has been entered correctly. Up to SAP Web AS 6.10, the user can only change the password during the logon procedure. As of SAP Web AS 6.20, the user can also change the password by transaction SU3.

1 comments

Monitoring SAP Gateway

SAP Gateway Monitoring via SMGW

The SAP Gateway carries out CPI-C services within the SAP world, which are based on TCP/IP. These services enable SAP Systems and external programs to communicate with one another.

CPI-C services can be used either in the ABAP program or for the external programs via the interfaces. As RFC (remote function call) is based on CPI-C, all RFC connections also pass through the SAP Gateway.

Monitoring SAP Gateway

The Gateway Monitor is used for analyzing and administrating the SAP Gateway in the SAP system.

SAP Tcode for SAP Gateway monitoring is SMGW

The initial screen of the gateway monitor shows all the active gateway connections on this instance. Please find the screenshot attached below.

0 comments

SAP Synchronous and Asynchronous Communication

Synchronous and Asynchronous Communication

Communication between two systems can be basically split into two types: Synchronous and asynchronous communication. Both forms of communication have specific advantages and disadvantages, relating to either the business application or the system administration.

Synchronous Communication

Synchronous communication uses a single function call. Prerequisite for this is that at the time the call is made (or the message is sent), the receiving system is also active and can accept the call and further process it if necessary.

· Advantage: Synchronous communication can be implemented in function calls that require the immediate return of data to the sender system.

Example: You create a purchase order with account assignment in the sender system, and you want to perform a budget check in central accounting before you save the purchase order.

· Disadvantage: You need to ensure that both systems are active and can be contacted. If they are not, this can lead to serious disruption of processes. In particular, problems can arise if the receiving system is not available for long periods of time due to maintenance (for example, for a system upgrade).

Asynchronous Communication

For asynchronous communication, the receiving system does not necessarily have to be available at the time a function call is dispatched from the sender system. The receiving system can receive and process the call at a later time. If the receiving system is not available, the function call remains in the outbound queue of the sending system, from where the call is repeated at regular intervals until it can be processed by the receiving system.

· Advantage: The receiving system does not have to be available at the time the function call is made. If the system is unavailable for a long period of time, for example, for an upgrade, it can still process the data that has been sent in the interim at a later time, and processes in the sending system remain unharmed.

Example: You are sending a purchase order to a vendor system. The sending system cannot influence the availability of the receiving system. If the receiving system is not available, the purchase order can be sent repeatedly until the vendor system is available again.

· Disadvantage: Processes that require an immediate response to the sender system cannot be executed using this method.

0 comments

SAP RFC, SAP Remote function call

RFC ( Remote Function Call)

Communication between applications in different systems in the SAP environment includes connections between SAP systems as well as between SAP systems and non-SAP systems. Remote Function Call (RFC) is the standard SAP interface for communication between SAP systems. RFC calls a function to be executed in a remote system.

Synchronous RFC

The first version of RFC is synchronous RFC (sRFC). This type of RFC executes the function call based on synchronous communication, meaning that the systems involved must both be available at the time the call is made.

Transactional RFC (tRFC)

Transactional RFC(tRFC, previously known as asynchronous RFC) is an asynchronous communication method that executes the called function module just once in the RFC server. The remote system need not be available at the time when the RFC client program is executing a tRFC. The tRFC component stores the called RFC function, together with the corresponding data, in the SAP database under a unique transaction ID (TID).

If a call is sent, and the receiving system is down, the call remains in the local queue. The calling dialog program can proceed without waiting to see whether the remote call was successful. If the receiving system does not become active within a certain amount of time, the call is scheduled to run in batch.

tRFC is always used if a function is executed as a Logical Unit of Work (LUW). Within a LUW, all calls

· are executed in the order in which they are called

· are executed in the same program context in the target system

· run as a single transaction: they are either committed or rolled back as a unit.

Implementation of tRFC is recommended if you want to maintain the transactional sequence of the calls.

Disadvantages of tRFC

· tRFC processes all LUWs independently of one another. Due to the amount of activated tRFC processes, this procedure can reduce performance significantly in both the send and the target systems.

· In addition, the sequence of LUWs defined in the application cannot be kept. It is therefore impossible to guarantee that the transactions will be executed in the sequence dictated by the application. The only thing that can be guaranteed is that all LUWs are transferred sooner or later.

Queued RFC (qRFC)

To guarantee that multiple LUWs are processed in the order specified by the application, tRFC can be serialized using queues (inbound and outbound queues). This type of RFC is called queued RFC (qRFC).

qRFC is therefore an extension of tRFC. It transfers an LUW (transaction) only if it has no predecessors (based on the sequence defined in different application programs) in the participating queues.

Implementation of qRFC is recommended if you want to guarantee that several transactions are processed in a predefined order.

Data transfer

All RFC types are transferred by means of CPI-C or TCP/IP. They represent a kind of Gateway Communication.

0 comments