My recommendation is to have the standard transaction code LPD_CUST added with CREATE authorisations to the security role so the Launchpad can be created in each client manually. This is especially true if the Launchpad entries contain client-specific application targets which would require multiple transports to manage. If not a big requirement, then can add the customizing to a standard transport request.
Could you please guide how to add the customizing to a standard transport request.
I have created a customer Launchpad copying from the standard, wanted to transport it from development to quality. I tried to transport manually. System ask for package name, when enter Z* package, throws an error cannot be saved in Z* package.
Find another Z package that it will accept (created by a developer using their developer key) or use standard SAP package (may be overwritten in future upgrade).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.