Software Collections in S4HC and so called dependencies

[peter_munt4]

In our 2-Tier S4HC Public Cloud we want to move some objects from our DEV landscape to PROD and that is done via a Software Collection.

I have a need to move some objects a month or more BEFORE the other objects.  Hence I need 2 separate collections.   So called dependencies prevent it - why does this happen and can it be overcome?.

Moving an object from one to another Software collection does detect dependencies however other non-related objects also are 'detected' incorrectly.  For example I had 1 Brand new CDS API View and an associated Custom Comms Scenario – on attempting to move that object, it detected 30+ other non-related objects that I did not want moved.

So trying to move this

But am prevented as it also wants to drag in all these unrelated objects.

[Tayane · Accepted solution]

Dear Peter,

Kindly refer to the documentation SAP Help Portal | Transport Dependencies

[peter_munt4 · Accepted solution]

Hi thanks for the reply. I've answered by question....If there are dependencies, you need to check using the Extensibility Inventory app as this showed me why exporting 1 object it wanted to include dozens of other things. I had forgotten that the CDS view references a custom field that is when used in other objects such as BADIs. It is not mentioned in the SAP Help on the Software Collection section... this should be highlighted somewhere in it's Add Missing Items section when it talks about Dependencies. I have made that suggestion on the SAP Help page.