Just want to ask if you also encountered this error ‘Provisioning configured but no provisioning rule present.’ when using the ‘SAP HR Modify Provisioning Rule’ for writing back Email attribute in SAP HR/HCM Connector.
We created Connector Rule and attached the rule in the SAP HR/HCM connector. Then, we created Create Account in SAP HR-HCM for Attrib Sync Enabling. After we run the attribute sync in SAP HR/HCM connector we got the error ‘Provisioning configured but no provisioning rule present.’.
How do you get the correct attaching and running of the rule to write the email address attribute to SAP HCM?
Based on your example though, it looks like you probably have, and started with the sameple for the SAP HR Modify Rule, which I included a screenshot of here:
The one difference I am noticing is that you have added the “Attribute Key” to the request, which is not needed for this.
To verify what has been set on the source after this, you can review the data that was returned for the call, or use the Source API to get the specific source by ID: get-source | SailPoint Developer Community
This will return the source and you can verify that the value is set correctly there. I suspect with the additional “Attribute Key” value that it may not have configured the rule in the correct location.
@Arun-Kumar may be correct here too in that you need to add a Provisioning Rule Call-out to get it to work. Unfortunately, I don’t have an SAP HR system to test this with, so take a look into that possibility as well.
Hi @Arun-Kumar good day. I still encountered the issue ‘Provisioning configured but no provisioning rule present.’ after adding the entry (‘See Screenshot’). Is there anything I missed?
No need to add that entry in the provisioning rule. The entry should be added to the source instead. Could you please confirm the name of the operation rule? I see SAPHCMWriteBack5 in the rule, but in the source, it is listed as SAPHCMWriteBack3 .
First, for clarity since it seems like you are using several rule names in your screenshots, let’s define what Rule you are working with. Currently we see SAPHCMWriteBack3 and SAPHCMWriteBack5 in screenshots.
Once you have verified that your rule exists, and you have the correct case for it, the next step will be attaching it to your source. You should only need to add this to the “saphrModifyProvisioningRule” attribute using the [ Update Source (Partial) API](https://developer.sailpoint.com/docs/api/v2024/update-source). You would do this with the code from the compass article that was linked or that @IAMpdu copied to here in his post. I copied it here for clarity of this:
[
{
"op": "add",
"path": "/connectorAttributes/saphrModifyProvisioningRule",
"value": "<Rule Name from above>"
}
]
Now, here is where I think there is some disconnect, and it may be worth going back and revisiting the documentation for the Patch Requests.
When discussing the “Attribute Key” and “Value” as it relates to doing a [ Update Source (Partial)](https://developer.sailpoint.com/docs/api/v2024/update-source)/PATCH API call, the “Attribute Key” is at the “path” used in the above request. The “Value” is the value in the request. In your latest Source listing, it looks like you have extra values which can be removed. You can use the same Update Source (Partial) endpoint with the “op” set to remove, and the “path” set to the values to be removed ( likely “/connectorAttributes//Attribute Key” and “/connectorAttributes/Value”)
Once you have the value added/updated with the Rule Name that matches the rule you’ve added, give it a test again.
Hi @gmilunich Thank you for the info. We already mapped the rule correctly and saw the value of Email in IdentityProfile was changed. However, in SAP HCM, the Email did not update correctly. What could be the possible reason why the Email in IdentityProfile was updated but not on the SAP HCM?
