Upgrade EA-HR 600 and SAP_HR 600 to 604/606

[Former Member]

Dear Experts,

I am new to SAP BASIS and Solution Manager,

Now we are on EHP6 for ERP6.0
But it seems, the software(HR) componenets SAP_HR and EA-HR are of release 600.

Could anyone help/Explian me how to upgrade these components?

I have downloaded the patches SAP604 and EA-HR607, and during installation, in MOPZ i am getting an error

'Error during call of SAP back end system'

as i am new to these concepts i am not sure, if i am on the right track, please give suggestions.

<note : we do not have a basis team reachable now>

Thanks in advance

[Former Member]

Hi Experts,

While performing the Connection test on SAP-OSS, I am getting the following error,

could you please help me ?>
what am i supposed to do?

[Former Member]

Hi,

Have you checked that sap router process is running.

If not please check where the sap router is installed and see if you can see the process .

Thanks

Rishi Abrol

[Former Member]

Hi Rishi,

I checked the sap router,
seems that the router is not expired and working perfect.

while double clicking the SAP-OSS to display , i get the following error also, do you have any idea?

solution manager 7.01

details -

Host name /H/xxx.xx.xxx.xx/S/sapdp99/H/xxx.xx.xxx.xx/S/sapd unknown

Message no. SR010

Diagnosis

The specified host name is unknown in your system.

Procedure

Check that the host name is correct.

kindly suggest  possible ways to correct it

thanks in advance,

[Former Member]

Hi,

Can you please check that sapserX(where x is number of saprouter that you are using) is known to the server.

So please check if it is entered in the host file .

Where is the router is it on the same solution manager. If yes  then can you please check that you can telnet sapservX 3299.

Thanks

Rishi Abrol

[Former Member]

Hi Rishi,

1. Router is not on the Same Solution manager.
2. I Checked sapservX in OSS1. seems the following result

- I found that we gave 'Name' as sapserv instead sapserv9 (According to SAP note 33135-Guidelines for OSS1. is itr related to Naming issues?

am i suppsed to change that name? will it affect our SAP syatem adverse if i make any changes on the name field?

can you please give suggestions?

[Former Member]

There should not be any issue if you change the SAP saprouter name, and its only used for the connectivity from your SAP system to the SAP router system. No downtime required to change this setting and you can revert back if you want.

[Former Member]

Hi Sunil,
i just changed tha name and found no new changes from the existing error! so what is it reagrding the sapservX components?

[Former Member]

You have to change the name to sapservX (1-9) depends on the type of connection you have from your saprouter to SAP.

did you tried with actual server name sapserv9

[Former Member]

Hi,

am i suppsed to change that name?

It would make a difference if the same name is not used in the route tab file.

Please check the below link and see that the configuration are as is.

https://websmp104.sap-ag.de/saprouter-sncdoc

Now if the router is on different server can you please check that you can ping the saprouter and try the below command.

From this sap system.

telnet <hostname of your router> 3200

From your router server

telnet <saprouter name> 3299

Thanks

Rishi Abrol

[Former Member]

Hi Rishi,
i just checked with rout tab, seems everything is fine.

plus,

Rishi, everything reagrding Solution manager was working perfect before, but now i see these kind of errors, please help me

[Former Member]

Hi,

If all the things were running perfectly .

Either it can be network issue or your cert are not valid.

To check the certs you can run the below command.

sapgenpse seclogin –l

sapgenpse get_my_name -v -n Issuer

sapgenpse get_my_name -n validity

Do you see any issue in the router logs.

did you try the telnet command.

If you say that the things were working before ,so is this issue with all the system or only with solution manager.

Thanks

Rishi Abrol

[Former Member]

Hi,

Please check the user id in the back rfc in solution manager that is pointing to the system for which you are generating the MOPZ.

So go in Sm59 and then select the BACK rfc for that system and do authorization test.

Thanks

Rishi Abrol

[Former Member]

Hi Rishi,

sorry for the duplicate post! it was a network failure when i posted it first time.

regarding my issue, what is BACK RFC ? what am i suppose to check in that?
how do i check that?

[Former Member]

RFCs connections created during the solman configuration for ERP system,

On solman system check the connection test for SM_<SID>_TRUSTED_BACK and others starting with SM_<SID>* and make sure it is working.

on ERP system perform the connection test for Solman RFCs SM_<SID>*.

[Former Member]

Hi Suil,

I made a connection test for SM_<SID>* and seems its working fine.
but during performing connection test for SAP*<OSS>*, i see lot of errors, what i can do to rectify it?

i have gone through some notes,and blogs. they suggest to do some changes on DSWP. but when tried to access the transaction DSWP, it says its obsolote.

please help me
thanks in advance

[Former Member]

Hi,

Login in solution manager .

Sm59 then ----> connection type as ABAP.

double click on the below rfc.

SM_<SIDCLNT(client)>_READ

SM_<SIDCLNT(client)>_TMW

Check the user id used in this RFC is correct and has correct authorization. Do authorization test for these two.

Now login in ERP system

Sm59 then ----> connection type as ABAP.

double click on the below rfc.

SM_<Solutionmanagersid>CLNT(client)_BACK

Check the user id used in this RFC is correct and has correct authorization. Do authorization test for this one.

Hope that you have trusted connection for the trusted rfc to work.

Thanks

Rishi Abrol

[Former Member]

The DSWP is now obsolete in Solman 7.1 onwards, you have to use tcode 'sm_workcenter'.

If the SAPOSS RFC connection not working then check the saprouter is up or not. Below is the syntax you can find in the SAPOSS RFC destination.

/H/<saprouter IP>/S/sapdp99/H/<sapserv IP>/S/sapdp99/H/oss001