%20--%3e%3cdefs%3e%3cstyle%3e%20.st0%20{%20fill:%20none;%20}%20.st1%20{%20fill:%20%239dd5da;%20}%20.st2%20{%20fill:%20%23475e73;%20}%20.st3%20{%20clip-path:%20url(%23clippath);%20}%20%3c/style%3e%3cclipPath%20id='clippath'%3e%3crect%20class='st0'%20x='86.5'%20y='408.15'%20width='907'%20height='290.82'/%3e%3c/clipPath%3e%3c/defs%3e%3cg%20class='st3'%3e%3cpath%20class='st2'%20d='M867.51,525.76l-35-106.2c-.91-3.65-4.11-5.94-8.68-5.94h-43.83c-8.22,0-11.87,6.39-9.13,13.7l61.07,173.85,35.57-75.41Z'/%3e%3cpath%20class='st2'%20d='M983.29,413.62h-38.81c-6.39,0-10.05.46-13.24,5.94l-58.3,122.67-67.01,141.41c-3.2,7.31.91,14.15,9.13,14.15h43.83c4.11,0,7.76-3.2,9.13-6.39l124.39-264.08c3.2-6.85-.91-13.7-9.13-13.7'/%3e%3cpath%20class='st2'%20d='M755.37,614.52v-109.12c0-51.14-27.26-97.25-90.81-97.25h-7.2c-62.03,0-92.91,46.11-92.91,97.25v109.12c0,5.48,5.02,10.04,10.04,10.04h36.99c5.48,0,10.04-4.56,10.04-10.04v-109.12c0-27.39,10.96-44.29,36.53-44.29h3.72c25.57,0,36.53,16.89,36.53,44.29v109.12c0,5.48,4.57,10.04,10.04,10.04h36.99c5.02,0,10.04-4.56,10.04-10.04'/%3e%3cpath%20class='st2'%20d='M249.5,518.64c0,32.42-24.65,58.9-55.25,58.9s-54.79-26.48-54.79-58.9,24.2-57.53,54.79-57.53,55.25,25.57,55.25,57.53M302.46,518.64c0-59.36-48.4-109.58-108.21-109.58s-106.27,48.68-107.76,106.82v176.35c0,3.37,4.57,6.74,10.05,6.74h36.98c5.02,0,10.04-3.37,10.04-6.74v-32.19c0-9.62.02-26.75.05-43.71,15.11,8.42,32.34,13.26,50.63,13.26,59.81,0,108.21-50.68,108.21-110.95'/%3e%3cpath%20class='st1'%20d='M377.85,518.64c0-31.96,24.2-57.53,54.79-57.53s55.25,25.57,55.25,57.53-24.65,58.9-55.25,58.9-54.79-26.48-54.79-58.9M324.89,518.64c0,60.27,48.4,110.95,107.75,110.95s108.21-50.68,108.21-110.95-48.4-109.58-108.21-109.58-107.75,50.22-107.75,109.58'/%3e%3c/g%3e%3c/svg%3e)
Cross Landscape Distribution for SAP Cloud ALM with pony
With pony, Cross Landscape Distribution, or XLD, is integrated directly into the SAP Cloud ALM Feature process. Features, transports and target systems can be distributed and kept synchronized across system and landscape boundaries in a controlled way – including a consistency check before critical status changes.
Why XLD matters in SAP Cloud ALM
In complex SAP landscapes, transport-based changes often need to be distributed across system and landscape boundaries. This applies, for example, to parallel development and project landscapes, maintenance landscapes or rollout scenarios.
SAP Cloud ALM does not provide Cross Landscape Distribution as standard functionality. Without integrated support, manual intermediate steps quickly emerge: distribution is executed outside of SAP Cloud ALM, the Feature status has to be maintained manually afterwards, and there is a risk that the status in the Feature does not match the actual distribution status.
Execute XLD directly out of the SAP Cloud ALM Feature process
The pony variant integrates XLD directly into the SAP Cloud ALM Feature process. Users see the XLD status directly in the Feature, identify source and target systems, and can start the distribution from within the Feature.
The key differentiator: pony can verify whether the required Cross Landscape Distribution has already been completed before a critical status change is allowed. This makes it possible, for example, to prevent a Feature from being set to “Successfully Tested” while the required distribution has not yet been completed.
What pony delivers for XLD in SAP Cloud ALM
Execute XLD directly within the Feature
Distribution can be started directly from the SAP Cloud ALM Feature. Users do not have to leave the Feature process to run the distribution.
Consistency check on status changes
pony can verify whether XLD has been completed before a critical status such as “Successfully Tested” is set.
XLD app for control and traceability
A dedicated XLD app provides a dashboard, rules, history, analytics, inbound transports and an audit trail.
Make XLD visible and executable inside the SAP Cloud ALM Feature
With pony, a dedicated XLD area is provided directly inside the SAP Cloud ALM Feature. Users see the XLD status, the source system, the target system and whether the distribution is mandatory or optional.
Distribution can be started directly from the Feature. A guided procedure supports the selection of the relevant transports, the entry of additional information, the display of source and target systems, and the assignment to the matching target Features.
Status changes only after the distribution is complete
XLD with pony ensures that transport-based changes can be distributed and kept synchronized across system and landscape boundaries in a controlled way. To support this, pony can verify the status change of a Feature and block it when the required XLD has not yet been completed.
A typical example is the status “Successfully Tested”. When XLD is mandatory for a Feature, pony can prevent this status from being set while the distribution has not been completed. The user receives a clear message directly in the SAP Cloud ALM Feature.
Make XLD mandatory or optional depending on the scenario
Not every change has to be distributed via Cross Landscape Distribution. With pony, XLD can be mandatory or optional depending on the rule, scenario or Feature.
This lets companies represent their transport and distribution processes flexibly without treating every case the same. Critical changes can be protected, while less critical scenarios remain optional.
Dashboard, rules, history and audit trail
In addition to the integration in the Feature, pony provides a dedicated XLD app. It supports the control, monitoring and traceability of Cross Landscape Distribution.
- Dashboard for completed and open distributions
- Overview of connected landscapes
- History of executed distributions
- Rules that control when XLD is required
- Analytics on the status of XLD transports
- Inbound transports
- Audit trail of executed XLDs and technical background processes
Configure XLD rules without development
The XLD logic is configured in pony via graphical workflows. A typical workflow verifies, on a status change, whether the required XLD has already been executed. If the distribution is missing, the status change is blocked and the user receives a message.
XLD rules are therefore not hard-coded but implemented in a configurable way. Companies can define their own rules and align them with their SAP Cloud ALM processes.
Who Cross Landscape Distribution with pony is relevant for
Cross Landscape Distribution with pony is relevant for companies that use SAP Cloud ALM productively and need to manage transport-based changes across multiple system or landscape boundaries.
- SAP Cloud ALM owners
- Release managers
- Transport managers
- Development coordinators
- SAP project managers
- ALM architects
- Regulated companies with requirements regarding traceability and auditability
More details in the SAP Community Blog
A detailed technical description of the XLD integration with pony will be published in the SAP Community Blog soon.
Frequently asked questions about XLD in SAP Cloud ALM
Cross Landscape Distribution in SAP Cloud ALM – get started now
Book a free consultation and see XLD with pony live, based on your requirements.