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.

[stefan_grosskinsky]

Hi Peter,

I would like to add something. 

You said 'I have a need to move some objects a month or more BEFORE the other objects. Hence I need 2 separate collections.'

I would like to add that moving items to other software collections is NOT the target solution for that requirement. You should use the 'Add to Hotfix' feature WITHIN the same software collection.

While the option 'Export->Changed and Deleted Items' will export all items having such a status the hotfix will only export the items that are contained in the hotfix. With that you can create a list of items that can be exported separately.

However you will still need to include dependent items that have been changed at the same time. But you will be able to ignore all other changed items in the same collection.

Kind regards

Stefan 

[peter_munt4]

Although the new CDS View YY1_PersWrkAgrmt_API_V1 has a custom field that is referenced in other objects; that custom field is already in Production.   I want to just move in the CDS View YY1_PersWrkAgrmt_API_V1.   So taking your advice, and reading the help again on this, I will add it as a HotFix on its Software Collection.