Skip to Content

SAP Personas - Flavor creation


Our development system has 2 clients:

  • 110 to create new objects or modify existing objects. On client 110 we have no data.
  • 120 to do our U.T. .

The logic is to create a new flavor on client 110 because our transport root is the client 110, but whitout data is impossible to navigate into the transaction. So I have create a new Flavor on client 120. When I use the same link with client 110 or 120, I see my Flavor. But not in the transaction /PERSONAS/ADMIN on ECC/110. Only in ECC/120.

Why do we saw the Flavor both in client 110 and 120 in the browser, but not in ECC with the SAP GUI?

Does someone of the community was confronted with such a configuration and could give to us the good practice, please?

Have a good day.

Best regards.

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Posted on Mar 19 at 09:23 PM

    In your situation, I would create the flavors in the client where there is sufficient business data (so 120). Then, to handle the transports, there is the concept of 'push to client', which lets you send these flavors to client 110 and do your transports from there as usual.

    Of course you could also transport the objects to 110 first as well, but pushing them seems to be the simpler setup.

    We have a corresponding KB article that should help.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Mar 23 at 08:14 AM

    Thank you for your reply.

    Finally, we decided to create into client 120, export from 120 and import into 110 and than transport from 110.

    Have a good dayt.

    Add a comment
    10|10000 characters needed characters exceeded

    • It would be much simpler and better to use the push feature, which retains the original client where the flavor was developed (120). This gives the opportunity to ensure that you only make changes to the flavor in a single (originating) location. But do whatever works for you.

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.