Symptom
A KUT field you created in one BO, for example Appointments has a value set in your appointment TI, but this value does not reflect to the corresponding field in another BO, for example Opportunities.
Environment
SAP Cloud for Customer
Cause
The field has the wrong Business Context to transport values between the two BOs you selected. Both Business Context and Extension Scenarios dictate how a field transports between BOs.
Resolution
Please re-create the KUT field from the appointment header.
In our example: when you create a KUT from for example the appointment overview facet, it will have Business Context:
Activities General Information. The value will not transport to the Opportunities TI > Sales Activities facet.
If you create the KUT field from the Appointment TI header, the field will have Business Context:
'Header Section Group Anchor' and the values can transport over.
Keywords
KUT, empty, missing, wrong, extension , KBA , LOD-CRM-OPP , Opportunity Management , AP-RC-UIF-FLX , Page Layout & Key User Configuration , LOD-CRM-ACT , Activities , How To