With this blog I want to highlight a very helpful note (1790924) which includes also an implementation example.
Sometimes customers run into issues within the registration process in Web Channel Experience Management against an ERP-Backend, because not all fields of the reference customer are copied to the new registered customer. If these fields are mandatory in the backend-system the registration will fail.
Typical fields are company codes or different partner functions etc.
Within the registration of a consumer the user will get an error-message "Error in user management. Please contact support". This message is very generic and only the support can identify the issue with debugging. In the described issue there is at least one field which will get identified as mandatory field but not maintained for the new registered consumer.
For sure, this issue is not specific for the consumer-scenario and can also affect the registration of a new contact.
If the customer checks the reference consumer he will see that the field is maintained for the reference consumer but not copied to the new created consumer.
The reference customer number is maintained in the Web Channel Builder. The standard copy mechanism only allows copying a certain set of fields from the sales area. A BAdI definition in a lower layer allows copying additional data without modifying SAP standard coding. As there is no direct link between the BAdI definition and WCEM coding a function group will be used to transport information fourth and back.
The issue has been described in Note 1790924.
The note also contains such an example how to do a modification free implement within the customer’s namespace to add additional fields from the reference consumer to the new created consumer.
