cancel
Showing results for 
Search instead for 
Did you mean: 

LM - Native HANA Transport Changelists

SergioG_TX
Active Contributor
0 Kudos

hello all,

I am working on a system which has LM enabled. It is working fine to record changes, assign changes, approve and release changes.

The HANA admin had created a DU and assigne the packages to it.

As developers we create changelists and approve changes. Then these changes are released.

During the intial migration, we noticed all objects were moved. We are ok with that.

During a second migrationm, which involved having an additional changelist created and selected as individual changelist to be transported... there was an error during the migration as the predecessor changelist(s) were included and also it seems like other files from other packages were also included.

shouldnt the new release only include the selected changelist? what am i missing?

why is it including other files?

why do we need a DU and also select individual Changelists?? i was hoping that we should only include changelists as we do not need to move an entire DU

please advise. thanks in advance

Accepted Solutions (0)

Answers (3)

Answers (3)

0 Kudos

Hell Sergio,

Recently I encountered the similar situation when transporting one changelist with only two objects included, after importing the transport request, I found that some other views were overwritten by out-of-date versions. However, this seems like a normal behavior of HANA ALM because the system will check the predecessor of the changelist and includes them in the same transport request. If the predecessors are not expected, you may need to remove them manually before releasing the TR.

For the definition of the "predecessor" and more details, please refer to

Export Changelists for CTS Transport - SAP HANA Developer Guide for SAP HANA Studio - SAP Library

I could see an option "Ignore Predecessor Relations" when importing the TR, but I am not sure if this is a faster way to exclude the import of predecessor changelist.

Regards,
Jonathan

SergioG_TX
Active Contributor
0 Kudos

the issue with the LM is because there were other subpackages in the DU. As soon as we removed the subpackages from the DU, now the deployment worked fine. I thought the purpose of changelist was supposed to be able to select which dev artifacts someone needs to deploy.. in our case HANA  SP09 - we wanted to release only a few objects and the LM was trying to move other dev artifacts from other subpackages. i think this is a bug on SAP LM feature that should be looked at

SergioG_TX
Active Contributor
0 Kudos

anyone??? am i the only one doing this incorrectly?