ABAP Cloud - Transport of the Software Component
What about the transport of software components in the ABAP Cloud? Do you also need the on-premise component in the test and production system?
Table of contents
In this article we will look at the question of whether we also need the software component in the subsequent system and how we can provide it. Finally, we will look at scenarios where it really makes sense.
Introduction
Software components, or SWC for short, are a central part of development with ABAP Cloud. They give you the opportunity to structure your packages cleanly and to differentiate them from one another. This should ensure a clean architecture. You should ask yourself whether you only want to use one SWC for TIER-1 or whether you would rather use more components for a clear demarcation. You can find further information in these articles:
Transport
If you create a software component using the report RSMAINTAIN_SWCOMPONENTS, you will not be required to submit a transport request after creation. In principle, we would now assume that we only need the SWC in the development system. That's why in the past we only created these on these systems to make them available to colleagues.
In principle, you can also assign a software component to a transport. To do this, select the component to be transported and choose transport recording (truck) from the menu.
After selecting the transport, an entry is written in it. The VERS object is then brought to the next systems with the other objects.
Usage
Now there are certain Core Data Services or classes that check whether we pass them an object that is of the ABAP Cloud type and/or uses a software component of the ABAP Cloud type. An example is the Core Data Service DDCDS_CUSTOMER_DOMAIN_VALUE. This has an INNER JOIN on ARS_OBJECTS_ALL_SW_COMP_SCP, plus the documentation from the view:
The view actively checks whether the transferred object is assigned to a SWC, and therefore requires the configuration of the software component in the system. This was just an example of where the SWC is still used everywhere in the system to ensure the consistency of ABAP Cloud.
Error
At the moment, however, there is a bug that means that after importing the software component into the target system, it is created as "Standard ABAP". This means that the component must first be converted to ABAP Cloud. This then applies to all subsequent systems.
There is note 3401565 which you can import. This provides the report ABAP_LANGU_SWCMP_SYNC, which you can use to synchronize the component in order to restore the correct status in the system. SAP is already working on correcting the problem so that this step is no longer necessary.
Conclusion
In principle, a software component, i.e. the content, works even without transporting the SWC. However, some features and tests require the entry, so we recommend always transporting the entry.
