Profitability and Cost Management

Get Involved. Join the Conversation.

Comments

  • Mark Drayton

    Hi Alecs,

    Thanks for posting up.  I'm trying to replicate a pass-through allocation (simple in Standard Profitability) using multiple (different) dimensions with the same structure.  I'm using the member formula to pivot source data to use it as a driver value.

    Thanks,

    Mark

  • Mark Drayton

    Hi Don,

    The "penny-dropped" earlier when reading Alecs's post - I was thinking the issue was with the Custom Calculation, but I think I'll need to add in the NONEMPTYTUPLE statement in the member formula and in turn this will improve the Custom Calculation.  Once I've had the opportunity to update and test I'll post back up for completeness.

    Thanks for taking the time to respond.

    Many Thanks,

    Mark

  • Don Bean

    Mark;

    Custom Calculation Rules in 11.1.2.4.129 only support the limited syntax you described - true, but member formulas support the full MDX as described in Essbase docs.

    Don

  • Alecsandra Mlynarzek

    Hey there Mark,

    I've done the same in the past - spread the load by a low maintenance split (nodes or a static dimension even, when we have that luxury). Like Don mentioned, we used NONEMPTYTUPLE and the formula performed fairly well. You lost me on the Same as Source replication. I thought you were looking for a way to replicate a dynamic driver in a more efficient way, also with the wider option of using any command/function that can be achieved via a Dyn Calc member formula. 

    Also - a tip for enhancement requests - they have something called Idea Lab on this page. That's where you can request enhancements , besides the Oracle support website. When posting an enhancement request in this location, it will get lost in conversations.

    Here's an intro on the Idea Lab:"The Idea Labs are forum-based feedback channels which allow Oracle Cloud customers to submit new ideas, comment on existing ideas, vote for their favorites, and see which requests have been implemented by Oracle.  These forums provide the simplest and most direct way for customers to share their ideas and enhancement requests with Oracle Development, while collaborating with other Cloud customers and Oracle partners. "

    And here's the link: https://cloudcustomerconnect.oracle.com/resources/0ce2e1914b/summary

    Have a lovely day!

    Alecs

  • Alecsandra Mlynarzek

    thanks for the update! This is useful to know since we generally have an automated job to update the EPMAuto version thinking the newer versions were always backwards compatible.

  • Mark Drayton

    Hi Don,

    Thanks for your reply, use of MDX is limited with this particular version - I believe I have to use "MDX lite", for example:

     </Stored_Driver/> = </Dynamic_Driver,NoRule /> 

    If there are any other options I'd be interested, if not I'm thinking for creating multiple Custom Calculations to spread the load.  To provide some context to my requirement; I'm actually trying to replicate the "Same as Source" / "Same as Dimension" PCMCS functionality (see attached) - it would be great if this could be made available in the on-prem world!

    Thanks,

    Mark

  • Don Bean

    Mark;

    The challenge with using members with a formula in any range based calculation process is that the potential that a cell *might* have a value that resulted from the formula requires Essbase to compute a value for *every* intersection in a range.  Range is determined by the definition of the Allocation rule source/destination or Custom Calculation rule target.  This is why member formula are best reserved for reporting uses and not calculation uses.

    If you need to use a member formula for a calculation related purpose then its best to use a custom calc rule to copy that value to a stored member so that the expensive range based operation only has to be performed once.

    Essbase MDX supports use of optimization methods that help it distinguish between empty space and non empty space and you can use this to your advantage in member formula as well as in custom calc formula syntax.   its a bit too detailed to discuss here but review the use of the non empty tuple method described in Essbase docs here: https://docs.oracle.com/cd/E57185_01/ESBTR/mdx_properties_opt.html

    Don

  • SanDip

    Apparently it was the EPMAutomate version. With Oracle's suggestion we downloaded epmautomate version 18.8 to match with the POD 18.8 version and it worked. 

  • Don Bean

    SanDip

    There's enough complexity here due to the differing versions that it will be difficult to diagnose on Customer Connect Forum.

    Please file an SR and include the exportsnapshot_<timestamp>.log from the local machine epmautomate was run.

    EPMautomate and system versions matter too so please describe the exact combination of versions you are using when things fail - as well as the combinations used when things succeed. 

    Don

  • SanDip

     Hi Alecsandra,

                     Here are my short answers to your below questions..

    So the issue here is strictly related to automation of snapshot import and export, and the fact that it returns an error code in your EPM Automate session, yet it completes without issues in the Cloud. Is my understanding correct? YES

    Are there any other processes returning similar error codes yet completing successfully, or is this issue strictly related to the snapshot import / export status?

    its strictly related to IMPORT/Export only. I was able to update dim, Deploy cube etc with successful exit codes

    Were there any updates to your network or proxy settings recently?  Any updates to your antivirus or software? No

    Also - have you tried to launch the same command on a different network or from a different workstation? Yes I have export/import on PCMCS version 19.3 and no issues.

     

  • Alecsandra Mlynarzek

    Hey there SanDip,

    So the issue here is strictly related to automation of snapshot import and export, and the fact that it returns an error code in your EPM Automate session, yet it completes without issues in the Cloud. Is my understanding correct? 

    Are there any other processes returning similar error codes yet completing successfully, or is this issue strictly related to the snapshot import / export status? 

    Were there any updates to your network or proxy settings recently?  Any updates to your antivirus or software?

    Also - have you tried to launch the same command on a different network or from a different workstation? 

    More questions than answers - sorry - just trying to get a better understanding of the issue. 

    Thanks! 

     

  • SanDip

    Hey Evan,

                     Thanks for the comment. Yes, the SNPCM_EXP exists in the environment. I just tried reset service with EPMautomate Ver.19.3 and still yields exit code 6.

     

  • Evan Leffler

    Hi SanDip,

    First, can you confirm that the snapshot named SNPCM_EXP exists in the environment you are attempting to export the snapshot from? 

    Second, have you tried running the "resetservice" command and rerunning your command to see if you get a different response?  I've attached a screenshot of the documentation for this command.

    Finally, I see you mentioned you are on an earlier version of PCMCS, however, you may want to try and upgrade your version of EPMAutomate as you are currently on EPM Automate Version 18.12.56 and the latest version is currently Version 19.03.08.  You can do so by running EPMAutomate from the CMD prompt and utilizing the "upgrade" command.

  • Ayeshan Peiris

    Hi Alecsandra,

    This post is a useful one. I have a clarification. For a profit curve in PCMCS, this note mentions about category analysis which uses attribute dimensions to analyze based on categories (Attributes). I want to know this option is available for bar charts and pie charts also? I have a requirement to create bar charts and pie charts based on an attribute dimension on the row of the charts. Your expertise on this is highly appreciated.

    Thanks,

    Ayeshan

  • Alecsandra Mlynarzek

    Hi Ayeshan,

    I have shared with you the stats on max number of members in PCM applications on your second post on metadata automation. The reality is you can push the metadata to a granular level but you should consider two options :

    - keep only what you need in your metadata. Define a purging mechanism to keep your app slim and efficient.

    - do you really need that level of detail in PCM for your allocations? 

    While 60 k is not yet reaching the limits of max nb of members / dimension, you have to expect performance impact with such volumes, whether with data processing or with reporting. Have a conversation with your client and try to evaluate what is necessary vs what is nice to have.

    Kind regards,

    Alecs