Page tree
Skip to end of metadata
Go to start of metadata


This page gives a step by step explained guide about how to transport launchpads.
Launchpads are transported in the customizing client. The customizing request includes table entries for the following tables:
  • APB_LPD_CONTROL (not needed if a customer version for an existing SAP version is transported)
  • APB_LPD_REPOS (if links to an repository launchpad exist)
  • APB_LPD_ADD_XMLS (only system alias mapping)

In addition, the user needs a workbench request for transport of long texts (transport object DOCV / DOCT) and short texts (logical transport object R3TR LPDS for SAP launchpads, R3TR LPDC for customer launchpads). Both transport requests must be released and transported to the target system.

When triggering the creation of transport requests via transaction LPD_CUST, entries in table TADIR will be created (one entry for each long text and one entry for all short texts). With launchpad version 4.0 long texts have TADIR key R3TR DOCV, object name is determined via function module DOCU_TR_OBJECT_CHECK.

Transport process


Popup: Do you really want to transport this launchpad? It will be visible in all systems.

Check whether the launchpad is already assigned to a package / Package assignment

Check text tables & Adapt Launchpad (Customer namespace, etc.)

Build up table APB_LPD_CHNGELOG

GET_TRANSPORT_KEYS (Get keys for customizing transport)

Get entries from APB_LPD_OTR_KEYS and add them to the object list of the customizing request (Including creation of TADIR entries for the texts)

BUILD_TRANSPORT_REQUEST (Customizing request)

Build object list for workbench request - list of entries from APB_LPD_OTR_KEYS and LPDS/LPDC for short texts



Show popup for created transports


Related content