When we do admin personalization (Content Admin Preview), It is not asking for a backend Transport when I save the changes

[Former Member]

Hi,

I'm trying to personalize via admin for WebDynpro ABAP iView.  After done with the changes, while saving, it should prompt for backend transport.  But the prompt is not getting while saving. 

Does anyone have faced this problem?  What is missing either in portal or in backend so that the transport prompt is not getting displayed while saving.

Regards,

Vijaya.

[siddharthrajora]

SInce it is WD ABAP, You can use SE80, intead of portal

and also it is not transportable

WD_ANALYZE_CONFIG_USER to check the actual personalizations.

The personalization is done based in ABAP; the Portal cannot be
involved in this step.

1. Configuration, which is a development object and is deliverable by
SAP to all our customers. This needs a package and a transport.
2. Customizing, which is done by the administrator for a specific
client, and is used for any user in this client. This can be
transported, but may not.
3. Personalization, which is dedicated to a special user, and entered by
themselves. This is not transportable. The reason is that we assume
different users in different systems.

Thus, using personalization and not being asked for a transport is a
standard behavior.

If you want to get rid of the already existing end user personalization
for the application, you can use the Web Dynpro application
WD_ANALYZE_CONFIG_USER. Here you can specify the Web Dynpro Component
and the user name and delete the existing personalizations. Afterwards
your application should display the UI elements that had disappeared.

Please also visit our SAP Help Portal for more information about
personalization settings:

http://help.sap.com/saphelp_nw70ehp2/helpdata/en/

73/142b2a79fb4884a4b4e87fa88f4115/frameset.htm

Further information can also be found under the link "Personalization
and Customizing":

http://help.sap.com/saphelp_nw70ehp2/helpdata/en/
47/ac6c53fd5b3020e10000000a42189d/content.htm

[Former Member]

Thanks everyone.  Issue got resolved.  I selected the option "changes and transports for client specific objects" in SCC4.  Then after saving from portal, the transport created in the backend.

[Former Member]

What you could do is, try the personlization in Dev, Test and confirm it works, Create an instruction so that Basis (or someone who has production content access) can redo them manually in QA and Prod

I believe thats is what we have done. Portal changes does not ask for transport. Instead you should have a transport package and move the content

This behaviour is dependent on the version of the NW. For my Ehp3 based client we did change in each client.