Member Lists

For member lists it is possible to define whether they will be transported or not.
Whether member lists cane be transported or not, always depends on the client settings (transaction SCC4) and can be further restricted by setting "Tp. header data", but cannot be enhanced. If a client is set to not automatic record customizing settings, it cannot be enabled with this settings.

*Field*	*Description*
Tp. header data	The following options are provided: Automatic transport Automatic recording of changes in a transport, if client settings allow so. Manual transport Changes will not be recorded automatically. Member lists can be added manually to a transport request, if transports are allowed acc. to the client settings. Do not transport Member lists cannot be transported. Because they are not linked with the transport system, they can be changed, even no changes are allowed acc. client settings.
	The deleting of positions will not be recorded and cannot be added to a transport request.
Always allow changes	If this option is activated, changes can also be made, when member lists are transported in general (manually and automatically, but the current systems won't allow any changes on the customizing data (e.g. productive system). This scenario is often needed, when the member list can not be maintained because of missing user on the customizing system. In this case, the header of member lists will be created and transported on the customizing system, however the users will be assigned only on the target system.
MBL change doc. active	Activation of the change documentation of ProNovia MBL/user groups. The recording of changes will be activated directly after the activation.