This scenario triggers the following errors in logs:
INVALID_INPUT_DATA In payload invalid value for field [FIELD]'. You cannot have non-cmdb class name  here.
Configuration Item not processed. IRE Identification Engine marked this Configuration Item as an Erroneous in the importSet under processing [PAYLOAD] "message":"In payload invalid value for field [FIELD]'. You cannot have non-cmdb class name  here."
These errors are caused by the incoming value in the payload attempting to be inserted into the field displayed in the log error. In summary, this value is a sys_choice and was not able to be inserted into the target table because there was no choice record created for the CI table with the value inserted by the payload.
To fix this, it is advisable to create the required choice in the sys_choice table. This can be accomplished manually or it can be an automatic process if the property x_nexsa_sg.create_references is set as true and the scheduled job executed once again.
This can also potentially be caused by the issues explained in section Discovery_source choice not created.