System Alias from 100 client to 200 client for HR Renewal Applications

[former_member214868]

Hi All,

We are implementing the HR Renewal 2.0 UI5/OData based ESS/MSS applications.

In development server 100 is the development/config client  and 200 is the testing client.

I am started with the Activate and Maintain service by selecting the System Alias as Local and the SAP Provided  External Service Name and then added to the Customer Namespace.

(Set Current Client as Default Client in ICF Node checkbox also checked as attached in the screen shot)

I am able to test in client 100, but when I check in the client 200, the System Alias Local is missing for all the Services Activated.

The System Alias Local is available in 200 client as well.

Please let me know how to get the System Alias Local in the 200 client as well.

Do I need to uncheck the (Set Current Client as Default Client option while activating the service?)

Please clarify.

Thanks.

[agentry_src]

Hi Urmilla,

For which Fiori apps are you activating the HR Renewal services?

If you are not using Fiori apps, please let me know as your Discussion should then be moved to a more appropriate venue.

Regards, Mike (Moderator)

SAP Technology RIG

[former_member214868]

Hi Michael,

We are implementing the HR Renewal 2.0 based UI5 applications as well as the HCM Fiori applications.

To start with Mobility Roadmap, we are implementing Leave Request and Leave Approval applications in the first phase.

Thanks,

[kammaje_cis]

Urmila,

You have to ask your Basis team to "add the system alias manually to the service" in client 200.

You have to repeat it for QA and Prod as well.

Thanks

Krishna

[former_member214868]

Hi Krishna,

Our Gateway system is Embedded system and the HCM also installed in the same system.

In that case, I can use Local to connect to the local gateway.

The System Alias Local was available by default after the BASIS team handed over the system and we did not change anything. In the fresh system, the System Alias Local was there in both 100 and 200 clients.

In this case, when I choose the System Alias as Local and activate the service, it should reflect in 200 as well.

Upon activating the services in a TR which is a work bench request and hence it is cross client.

Do I need to create/edit a system alias Local so that a customizing request can be created and that can be moved to 200 and  after that activating all the services will work?.

In our case, dev client 200, QA and Prod clients are non modifiable and everything has to be through the TR.

For another project, We had earlier one client in Dev and in the same way we used the Local System alias and moving the TR to QA worked fine without any issues.

Any idea/suggestion is appreciated.

Thanks

[masa_139]

Hi Urmila,

The roort cause is that client 200 does not have correct setting. You can manually change it or you can make a transport.

Regards,

Masa / SAP Technology RIG