Local vs transported packages

[larshp]

https://github.com/SAP-samples/abap-platform-refscen-flight/blob/ABAP-platform-2023/README.md#download

In your ABAP project, create the package /DMO/FLIGHT as target package for the demo content. Use HOME as software component. Assign it to a new transport request that you only use for the demo content import.

I recommend customers to transport transported objects, ie. everything that is transported must go to production. Or in other words, if there are no open transports then its safe to assume that production and development match. If thats not the case, bad things can happen when doing transports.

Anyhow, I think most customers would like to avoid having demo content in the productive business system, so I suggest changing the guide so it suggests to put the demo code in a local package. Or adding a note that the user must consider if it should be transported or local.

local packages also makes it a lot easier to remove from the system, if needed

[VolkerDrees]

Demo content should definitely not be transported into production. That's the reason why we have chosen github as the delivery channel.
Using a local package i.e. a package with software component LOCAL would have been our preferred approach as well. But this doesn't fit to the usage of the namespace /DMO/.