Skip to Content

Transport System Alias for Odata services to Quality and Prod

Hello, We have started a new implementation for a Fiori Application. The issue remains same as of Assigning Alias system for OData services. After going through different posts I found the way but need some clarifications. The landscape is such that we have:

1. Dev client 100 for Development
2. Dev Client 110 for testing ( For testing, we are planning to build system Alias pointing to 110 )

3. Additionally we have Quality and Prod where the assigned way discussed in different posts work. Below is the link

https://blogs.sap.com/2013/05/31/how-to-maintain-sap-system-alias-entries-in-productive-systems/

So is there any thing that changes with ECC in Release 740 and is the approach correct for different systems?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Aug 18, 2017 at 03:55 AM

    There are no changes in 740/750. The approach mentioned in the blog is still the right way.

    Add comment
    10|10000 characters needed characters exceeded

    • For a demo , we create a dummy service to test the functionality. However, assigning of system alias to OData services do not happen in Client 110. As mentioned in the blog, these entries cannot be transported and need to be manually taken care of. The entries mentioned in the picture do not appear in 110 and they are there in 100. How can we handle it.

      issue.png

      issue.png (27.1 kB)