3590283 - Behavior of Partial Transport of Code List Restrictions From Source to Target.

This KBA explains the behavior of partial transport of Code list restrictions from source to target.

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental." 

SAP Cloud for Customer.

1.In source tenant create multiple CLR's with same BO/Code to restrict/control field example(Account/Industry/ABC classification)

2.Assign different Business roles to the code list restriction and Value allowed based on the business requirement.

3.Perform a UTM and transfer all the newly created CLR from Source to target tenant.

4. In the Source tenant make few changes in the CLR for values allowed .

5.Perform Partial UTM which includes only the changes made to the CLR.

Result: Some of the CLR in few cases all the CLR with same BO/Code to restrict/control field gets deleted in the target tenant.

In some cases, even though logic supports partial UTM in few instances causes inconsistency.

We recommend customer to proceed with the full UTM of CLRs for the entire BO (in this example Account BO). Post UTM user can compare the CLRs in the target tenant to those in the source to confirm consistency (it will be replica of the source system) 

Code list restriction, CLR, partial UTM, CLR transport. , KBA , LOD-LE-RC-CLR , Code List Restriction , Problem