Skip to Content
avatar image
Former Member

Fiori Launchpad and Role Administration Problem RFC Destination

Dear experts. I need a little guidance related to Fiori Launchpad and Roles administration subject:

Currently we are implementing SAP S4/HANA Fiori fresh instalation.

Scenario:

For this example i created a test role in SAP DEVCLNT100 -> added a catalog using "Remote Front-End Server" -> "RFC Destination" and poiting to SAP FIDCLNT100 System (where the catalog originally exists) -> and then proceeded to transport the Role to SAP QASCLNT200 System.

When i loged on to SAP QASCLNT200 System to check the process i noticed that the node keeps the reference to SAP FIDCLNT100.

Question:

Is this correct or am i doing something wrong in the process?.

My concern is what will happened if DEV System is down for maintenance, will this affect our Production System in anyway?.

The screenshots below are from QASCLNT200 System:

print1.png (27.2 kB)
print2.png (22.9 kB)
print3.png (6.2 kB)
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Jun 16, 2017 at 03:46 AM

    Hmmm Enrique ... definitely we don't want that happening.

    Have you tried using an RFC Variable instead? You maintain those in table SSM_RFC and that then points to your RFC Destination... allowing you to change which destination is used by repointing the variable in DEV vs. QAS.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jun 16, 2017 at 07:30 PM

    Jocelyn thank's for the reply. I just test that option but it seems that once i transport the role to QAS it doesn't push the authorizations correctly from DEV to QAS.

    Do you have any more information about Variable RFC Destination?.

    Greetings!

    Add comment
    10|10000 characters needed characters exceeded