Skip to Main Content
Forums

Analytics Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Dynamic Dimension member creation in Essbase

870777Aug 18 2014


Hi All,

I have a scenario where I need to create a Policy diemension which will hold the policy nos as dimension members in Essbase.The company has floated huge no of policies in the market so we cannot take them as static data and put it in my application.

I want to design a mechanism that as data comes in for policy then that Policy no should get added in the Dimension as a member.So the step which I want should be:

1-Extract all the policy nos from the application

2- Compare it with the list of todays list of policy

3- If there are any new polciies then add it as dimension member

4- Now load the data.

Kindly guide me as how this can be achieved.

regards

Abhi

Comments

Kamal Kishore
Try adding the PRAGMA to the function. 
FUNCTION function_name(...) RETURN VARCHAR2 ;
    PRAGMA RESTRICT_REFERENCES(function_name, WNDS, RNDS, WNPS,RNPS);
APC
There are a number of things it could be.

My #1 candidate is, we can only use functions in SQL statements that are public i.e. declared in a package spec. This is the case even for SQL statements executed within the same Package Body. The reson is that SQL statements are executed by a different engine which can only see publicly declared functions.

Cheers, APC
32685
Hi Andrew

That's exactly it! I moved the functions back to the original package, published them in the spec and it worked. Excellent!

Cheers

David
446518
Great!!

Helped me a lot

Though the message - function XX may not be used in SQL, is not relevent.

Krishna
564378
Wow, that cost me some time.
Thanks a lot, it saved my day.
450441
My god, users who search the forum before posting.

Surely it's a sign of the End of Days.
Amritpal
Thanks a lot, I just Googled the error PLS-00231, the very first link brought me here, and you were spot on. Declare the functions in the Package Spec to make them Global, and that solved the issue.

Thanks.
Amrit
659130
I also have this problem.

Making the function public helps ... but I can not make the function public. This violates the design.

The PRAGMA also says that it must be right behind the function definition AND in the package specification.


Is there a other - a private - way?

(Oracle 8i / PLSQL 8.1.7.4.0)



I also can not split the call from the SQL Statement, because it is part of a cursor loop: 
FOR a IN (SELECT asd,
                         asaa,
                         asdasda,
                         h.sssde,
                         HLP_FNC_GET_BLABLUBB(j.adasdassss) dasdasssss
                  FROM   T_fhexxxsadfast h,
                         t_FFasee112w_SA   j
                  WHERE  h.soasde = j.soasde) 
        LOOP
anonymized code.

Edited by: user5828099 on 10.09.2008 07:57

Edited by: user5828099 on 10.09.2008 08:02
1 - 8
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Sep 15 2014
Added on Aug 18 2014
#business-intelligence-applications, #performance-management-applications, #planning-and-budgeting
0 comments
422 views