Public Dimension Table Import Job Error

[atillacemyildiz]

Hello everyone
Since Sunday, we have been receiving an error in our oData Import Jobs that update the Data Access Control in the Public Dimension Table as 'An unexpected error occurred while trying to update the dimension data.' Could this be related to the SAC 2024 Q4 update? Does anyone have any information?
Thank you in advance

[m-sapey]

I have the same issue on a couple of our dimensions.
In our environment there are 3 copies of one dimension that import from the same master data.
One is working and 2 others not.
Did you manage to fix the issue on your side yet?

[m-sapey]

Hi, I have the same issue on a couple of our dimensions. In our environment there are 3 copies of one dimension that import from the same master data. One is working and 2 others not.

[m-sapey]

SAP Note 3538935 indicates that this is an issue caused by the Q4 drop

[bibi]

Hi, the SAP note indicates that the issue has been fixed and deployed as part of the patch 2024.21.7.We are on 2024.21.8 version and still facing this issue.

[bibi]

Is this fixed on your side?

[atillacemyildiz]

Hello Bibi,

Yes, it fixed for us. Maybe you must check your import job.

[atillacemyildiz · Accepted solution]

As stated in SAP Note 3538935, the issue has been fixed with the new patch.

[MM72]

In our case we were facing the issue when loading an empty Dimension the first time. We got the error, but when checking the Dimension Table we saw that there was data loaded. I tried then to change something and when saving i got the message that the Line "Not in hierarchy" is missing and should be added manually.

After adding the line and saving the changes the refresh succeeded. 

[bibi]

Hi, we had an issue in one hierarchy of the public dimension too. Some members were not in the hierarchy. Once we added them manually the import jobs started refreshing successfully again. Thanks

[Alex23081990]

Hello,

is for this public dimension currency property in place and is the dimension used ? 

If yes, then you might need to fill for every empty currency entry some default value. That was one of the solution, which helped to fix the import jobs again.

Br,

Alex

[atillacemyildiz]

Hello Alex,

No our PDT hasn't currency field. It's contains data access for company.