Value mappings do a similar job like the code list mapping in SAP Sales and Service Cloud. In order to make use of a value mapping the iFlow, respectively the message mapping, must contain a valueMapping expression that specifies the source and target agency and identifier. They can be used when the source or target system do not offer such a feature. Value mappings can be re-used by multiple iFlows/message mappings while they are maintained in a central place.
In contrast to that there is the fixValueMapping expression that maps values that are maintained locally inside of an iFlow/message mapping. Although SAP Sales and Service Cloud offers the code list mapping, some codes can't be mapped due to technical limitations of the interface and the value mapping on SAP Cloud Integration is necessary. A good example is the mapping of ABC/Customer Classification between SAP Sales and Service Cloud and SAP ERP. The identifier in SAP ERP is called CustomerClassificationCode and can contain values with a length of 2 (e.g. "07"). The identifier in SAP Sales and Service Cloud is called CustomerABCClassification and is limited by the data type of the field to a maximum length of 1 (e.g. the value "A"). As the data type of the field does not allow values longer than 1, the system would throw an error if such a value is entered as external code inside the code list mapping and hence a value mapping inside SAP Cloud Integration must be used. SAP Cloud Integration Value Mapping can be maintained directly in SAP Cloud Integration Web UI.