The "Add Related Business Objects" feature provides guidance to a user for business objects that might also need to be added to a change set. Based on a business object already in the change set, related business objects are presented to the user and the user can determine if these should be added to the change set also.
This feature assists customers in transporting the correct changes to ensure data integrity on the target systems. The business object along with its related business objects is required to maintain the business object configuration data and relationships in the target system exactly as it exists in the source system. This helps to avoid application issues when the business object is used in the target system. If related business objects already exist on the target system, it may be unnecessary to transport them. Likewise if the change to be transported is a smaller one known to be localized to a particular business object, then it is fine to transport the single business object without its related business object. As there are lots of reasons for not transporting all related business objects, this feature provides guidance to users on what they may need to transport.
The "Add Related Business Objects" feature evaluates related business objects via database relationships; i.e. foreign key relationships or link tables. If any other type of relationship exists between business objects, this will not be reflected in the "Add Related Business Objects" feature. For example an API exists for Rate Table functionality and calls to this API from the codebase may introduce a relationship between a rate table and the calling business object but this won't be presented to the user as a dependent business object. Therefore the "Add Related Business Objects" feature should only be considered a tool to provide guidance about what needs to be transported.