cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

SAC Data Action Error: : Member “#” not found

PS_1978
Active Participant
0 Likes
1,480

Hello All - I am pretty new to SAC and supporting a process that is recently deployed to production. One of the data actions in production environment shows the error message, "COSTCENTER: Member “#” not found". I checked the dimension and a member with "#" exists in the dimension. I don't have this issue in QA environment. Attaching the screenshot with error.

Can you help fix the issue?

Thanks,

Phani

Accepted Solutions (0)

Answers (5)

Answers (5)

William_Yu1
Product and Topic Expert
Product and Topic Expert

Probably you can check if member "#" is part of the cost center hierarchy you used in the step.

PS_1978
Active Participant
0 Likes

Hello nikhil_1486 - Yes I do see HIERARCHY.CONFIG statement. Please check below screens.

Thanks,

Phani

SeerOfSig
Product and Topic Expert
Product and Topic Expert
0 Likes

If you confirm that the COSTCENTER dimension and data action are exactly the same in your QA and Prod(?) environment then the issue MAY be due to an issue with the # member itself. Since certain members are system generated, there can be issues when a dimension member that should be system generated is manually created or copied instead.

It's not clear if that is the issue here, but if you are certain that your two tenant environments are the same you will need to open a support case so that we can access your tenant and investigate.

Regards,

Peter

PS_1978
Active Participant
0 Likes

Hello peter.kreutlein - Sure. I shall check and open a support ticket.

Thanks,

Phani

PS_1978
Active Participant
0 Likes

Hello william.yu - I just checked and it does exists in hierarchy too.

Thanks,

Phani

N1kh1l
Active Contributor

sivapuram.phanikumar

Does your Advanced Formula have a HIERARCHY.CONFIG statement defined ? If yes please put a snapshot of the statement and also the snapshot of the # member in the cost center dimension along with the headers. This will help to understand the issue.

Nikhil


PS_1978
Active Participant
0 Likes

hello william.yu - Sorry, I should have mentioned earlier. Yes the member # exists in COSTCENTER dimension.

Thanks,

Phani

William_Yu1
Product and Topic Expert
Product and Topic Expert
0 Likes

I mean hierarchy, if cost center has hierarchy, "#" should be in that hierarchy as well.