You want to call an RFC function in another system but, because you’re not a carrion eater, you only want to do it if it’s alive.

Hence, you need a way of checking whether that particular destination RFC system is alive.

How do you do that?

Charles Santana does it like this:

DATE: rfcdest         TYPE rfcdest,
           ping_status TYPE /sdf/e2e_traffic_light_numeric.

CALL FUNCTION '/SDF/RFC_CHECK'
 EXPORTING
   iv_destination = rfcdest
   iv_ping        = 'X'
*    iv_logon       = 'X'
*    iv_latency     = 'X'
 IMPORTING
   ev_ping_status = ping_status.
if lv_ping_status <> 1.
* it’s dead.
endif.

Thanks Charles.

You’ve screwed up the productive system. You made a change to a method of a class (or to a function, whatever). Someone else makes another change to another method of the same class (or to another function of the same group of functions, whatever) and saves it to a different transport. When you transport your changes to the productive system, you discover that the class (or function, whatever) now has a syntax error because the changes had interdependencies. You also discover that now, until you get this problem resolved, all your functional co-workers hate you.

If you really need to access an SAP and nobody lets you, and you don’t have a computer where you can install it or you don’t have enough know-how or patience to do it, you can always rent.

It’s been a while since Abapinho played with fire. Today he will.

Because today he’ll show you how to execute DOS commands on the user’s local machine. After you finish reading this article, you’ll be ready to format the hard disks of all your users. Dealing with danger helps make us aware of the power we have and the responsibility that comes with it. Dear reader, listen to your conscience.

SAPlink is a Z program that is installed in the development environment and which enables a wide variety of object types to be imported and exported from the Workbench.

Take a look here at some examples of how SAPlink can be used:

• To transfer a table from one SAP system to another

• To share a class on the internet

• To make a local security backup of a set of programs before making a dangerous change

• To keep a development in our personal repository (in Evernote, of course) in case you need it later in another project

• Etc.

There are some projects in which the authorisations group associated with table maintenance is always &NC;&, that is, Not Classified. It signals that everything there is friendly and nobody is hurting anyone else. But there are other projects where authorisation groups are taken seriously. But this is not synonymous with saying that they are organised. Serious or not, usually it all ends in a big mess, with nobody knowing who is authorised to do what.

This tip may help.

It is not uncommon for us to be emotionally attached to our passwords. Therefore, it is always rather painful to receive those despicable threatening notices that say “your password is going to expire”. Soon followed by the blow we receive to our heart on the appearance of the inevitable vile invective that “your password has expired.” At such times, the hurt is so great that all the muses leave us, we have imagination cramp and remain stuck there, staring and drained, emptied of any idea to help us choose our next password.