Renew SAP Router Certificate on Windows Server

By default, SAP Router certificate will be expired each one year. SAP router is used to connect between your local SAP server to SAP server. It is used for an example to download and install new NOTE from SAP.

Check the connection of SAP router:

  • Login to SAP R/3
  • Open t-code SM59 - Configuration of RFC Connections
  • Open folder ABAP Connections > SAPOSS > Connection Test
  • If connection return an error such below, there is posibility that your SAP router certificate has been expired and need to be renewed.
Error message:
Logon              Connection Error
Error Details     Error when opening an RFC connection
Error Details     ERROR: CPIC program connection ended (read error)
Error Details     LOCATION: SAP-Server TRHP01_DBW_00 on host TRHP01 (wp 1)
Error Details     COMPONENT: CPIC
Error Details     COUNTER: 6
Error Details     RETURN CODE: 223
Error Details     SUBRC: 0
Error Details     RELEASE: 700

Renew SAP Router Certificate

Please follow screenshot below:

Saturday, August 16, 2014

3 steps to delete client from SCC5, SAP Basis

To safely delete SAP client, it's strongly advice to use t-code SCC5, Delete Client.


  • User access to target client
  • Assign authorization SAP_ALL profile, to ensure there's no error during deletion
3 steps to delete client from SCC5
1. Get into deleted client, run client deletion from tcode SCC5

2. Monitor the process from tcode SCC3

3. Delete unused logical client from BD54 (optional)

Wednesday, March 26, 2014

10 things that drove me out of IT (as technical support)

After six years of working as a remote support tech for a managed service provider, Jack Wallen threw in the towel. If you've ever been tempted to quit IT, his reasons may sound familiar. 

Some people assume that the world of PC support is a glamorous, Sheila E sort of life. After all, it's technology, geeking out all day long. What's not to love?

Famous last words.

For what seemed like an eternity, I served as a support tech for a managed service provider (MSP). Starting the job, I had no idea what I was getting into. As the saying goes, "If I knew then what I know now…." Would I have stepped foot into the world of remote support? It's hard to say. What is not so hard to say is why I eventually gave up being a support technician. In fact, I can give you 10 reasons why.

1: Stress

This is the number one reason why I left. If you've never experienced the levels of stress associated with managed service providers, you're in for a real treat. You have (possibly) hundreds of clients calling in all day to report their computers "aren't working." The queue lines up with people who can't get their work done because "you haven't fixed their problems." It's disaster management and triage all day and it never lets up.

2: Pay

The pay for an MSP engineer is not what you'd think it would be. I nearly exploded with laughter every time I heard a client say, "That's why you get paid the big bucks." I wanted to say, "You probably get paid more than I." But I refrained. Every time. The truth is, the pay just wasn't enough to offset the high levels of stress and frustration. It made more sense to move on.

3: Printers

Nearly half of what I did all day was fix printers. That's how I came to the conclusion that the very foundation of printing is broken. I never signed up to be a printer technician and would feel my blood boil every time I saw a support request come through that said, "My printers stopped printing!"

4: Ignorance

I hate to be one of "those people," even momentarily. Still, the levels of ignorance I dealt with on a daily basis were staggering. I was always professional, and I tried to be patient and kind. But fielding the same questions over and over — things as basic as, "What's a web browser?" — eventually wore me down.

5: Micromanaging

As a contract company, MSPs need their engineers working at 150 percent all day, every day, and each second must be accounted for and billed. So it's not surprising that they tend to micromanage the staff. Some people can handle this management technique. But it drove me mad to have someone breathing down my neck all day. There was also an avalanche of paperwork we had to do to ensure that we'd be covered in case of a disaster.

6: The pace

The world of PC support (especially of the remote flavor) can be boiled down to this: You have way too much to do, not enough time to do it, and not enough help to get it done. And as that workload piles up, you have angry clients who can't get their own work done. To accommodate this, you have to work at a pace you can't maintain for any length of time (which leads us back to #1: stress).

7: Windows

I've always been upfront about my opinion that Microsoft Windows is the reason tech support is so busy. I mentioned that half of my job was fixing printers. The other half seemed to be malware and viruses. Every day I fought the urge to blurt out, "If you used Linux or Mac, you wouldn't have these problems and you'd save a ton of money!" But I refrained. Every time. If you've experienced the stability and reliability of "the other platforms," you get this. You don't want to spend your day supporting Windows. You'd rather spend a portion of your day training users on another platform and watching them work happily ever after.

8: Multitasking madness

I am a multitasker. I often have two to three major tasks running at once. I'll be writing a tech piece, a work of fiction, and getting intense on social media. But the problem with working directly in IT is that you get your head buried in something you've been told is critical... only to be yanked from that task to do something like fix a printer for a CEO. You come back to the original task(s) and find your flow completely ruined and you're back to square one. This happens more often than not, and you lose a lot of work as a result.

9: The love of technology

It can be tricky when your work intersects with something you're passionate about. For me, technology is one such passion. But having to deal with tech issues (often caused by user-error or platform inadequacies) day in and day out was starting to ruin it. I even began to hate it. That caused serious problems for me, as I had to go home and toil away in front of a computer to create works of fiction, which is something that usually brings me great joy. It wasn't until I left the support industry that I regained my love for technology.

10: Burnout

There is no avoiding this. You will burn out. The pace and stress tend to remain neck and neck in the race to subvert your sanity. Working support will eventually take you down. And (at least for me), you'll find yourself carrying that stress home with you. You'll go through periods where that stress doesn't seem to want to wash down the drain and it turns you inside out. For me, that was too big a price to pay.

The last straw
Not every company and not every person is cut from the same cloth. There are those out there who will gladly tolerate what, in the end, sent me packing. I am also not pointing any fingers at any one company. Ultimately, the killing blow was my own lack of resilience and my inability to keep up with the choking pace of the managed service provider industry.

Related post: Top 10 reasons to stay in IT

By Jack Wallen in 10 Things
Original source

Saturday, March 22, 2014
Tag :

What is the difference between SAP Update and Upgrade

During SAP upgrade from ECC6 R3 to ECC6 EHP5, there is a question: "What is the difference between update vs upgrade?"

Updating SAP products is for applying support packs, patches or hotfixes. Upgrade term is used exclusively when product release is changed.

Sunday, December 1, 2013

4 things you shouldn't do as an IT

 Thousand ways to Rome

That proverb applicable also to work in IT field. Higher pay salary, flexible time hours (for some position), get extra facilities (especially in techno), high demand jobs, and other things become magnets to work in IT.

But, some (or most) IT professional trapped on their job! They just realized after 30s or 40s, which is harden to move freely as before. Or some create wrong step, that blocked their future opportunity. Here are 4 things you shouldn't do as an IT.

1. Work for Money

Not just in IT, but also other field. If you work for money, in certain step it will get boredom to the max. Work for passion/strength that you good at!

If you really love IT, give all you got to this job seriously. Serve the customer 110%, respond all problems ASAP, read IT articles more frequent, update your skill with seminars, etc.

2. Become Generalist

This is a debatable topic for fresh graduate, "should I become specialist or generalist?"

Most seniors will say be specialist! Some people say that CIO won't handle technical things, it's true! But if they know one or two specific areas, they can communicate better with the subordinate (and earn respect easier).
  • If you're still in colleagues, start take specific topic that you like most, and stick with it.
  • If you just employed, see what specific area you can take in current office. If you can't find any, move to other company as soon as possible!
  • If you're 30s now, find a credible course for specific subject. Don't wait, time flies! You might be start your career from bottom, recalculate with the acceleration and job security
  • If you're 40s above, take your future step carefully. If there's a good opportunity to become specialist, take it. But if you can't, create strategy for higher position directly as manager, IT GM, or CIO.

3. Think you're an expert already

IT is one of fastest growing industry. If you think that you're an expert already & stop learning, you'll die pretty soon! Never stop learning, period.

4. My customer is computer

If you think your only partner is computer, you completely wrong! IT professional never work alone. 
Each day you might see computers, servers, routers; but it doesn't mean you no need others. User, vendor, management, colleague, boss, all of them are the resources we have to worked with.

- Copyright © Ady Purnama -Metrominimalist- Designed by djogzs -