SAC - SAP IBP - issue in loading the model into SAC

[silvia_codinotti]

Hello Everyone.

We are facing an issue in loading the KF from IBP to SAC. Could you please help us?

Thanks a lot!

Best regards

DETAILED ERROR -

The following error message comes from the external data service: status: 400 body: {"error":{"code":"SY/530","message":{"lang":"en","value":"An exception with the type /IBP/CX_CALCVIEW_NOT_VISIBLE was raised, but was not handled locally or declared in a RAISING clause."},"innererror":{"application":{"component_id":"SCM-IBP-INT-ODT","service_namespace":"/IBP/","service_id":"EXTRACT_ODATA_SRV","service_version":"0001"},"transactionid":"24A4069697F401D0E0060F6A38275D26","timestamp":"20210720102223.8475670","Error_Resolution":{"SAP_Transaction":"For backend administrators: use ADT feed reader \"SAP Gateway Error Log\" or run transaction /IWFND/ERROR_LOG on SAP Gateway hub system and search for entries with the timestamp above for more details","SAP_Note":"See SAP Note 1797736 for error analysis (https://service.sap.com/sap/support/notes/1797736)"},"errordetails":[{"code":"","message":"An exception with the type /IBP/CX_CALCVIEW_NOT_VISIBLE was raised, but was not handled locally or declared in a RAISING clause.","propertyref":"","severity":"error","transition":false,"target":""}]}}}

[Alecsandra · Accepted solution]

Hi Silvia

I saw this error before, and it was linked with missing configuration in IBP - the corresponding business user was not defined in the communication arrangement used to connect IBP with SAC. Through this step, you assign specific authorization on planning area, key figures, master data etc to the communication user.

Best

Alecsandra

[avsalynin]

silvia.codinotti have you watched the given Note from the error?

"The Troubleshooting Guide is supporting the user in error handling. Therefore the guide describes how an error can be analyzed and gives hints how to solve it.
See attachment."

I cannot add here, tk. it is more than 1mb

[silvia_codinotti]

Thanks Aleksey!!!

Following the Alecsandra suggestion we solved the issue 🙂

ciao