The Planning Repository: HSP_ACCOUNT

Not to sound like a broken record, but…a few disclaimers:

  • This is the fun stuff…that voids your warranty.  Not that you have to tell Oracle that you poke around here, but if you do, they will blame anything and everything that’s wrong on you for being in there.
  • The content here has been tested and validated against 11.1.2.3.500 and 11.1.2.4.
  • The content here has been tested and validated against Microsoft SQL Server and Oracle 11g.
  • The content here is based on the Vision sample application.
  • The content here is totally unsupported by Oracle (in case you missed the first bullet).

So it’s been a while since we took at look at the Planning Repository.  Today we’ll move past the HSP_MEMBER table (and associated tables) to look at the first of our built-in Planning dimensions:  HSP_ACCOUNT.  As the name indicates, the HSP_ACCOUNT table contains properties related to the account dimension in Planning.  Let’s take a look at the table structure:

Field NameSQL Server TypeOracle TypeDescription
ACCOUNT_IDintNUMBER(38,0)The OBJECT_ID of the member.
USE_445smallintNUMBER(38,0)If you application is set to use weekly distribution, this field will be populated when the Distribution checkbox is checked.
0=don't adjust values
1=445 spread
2=454 spread
3=544 spread
TIME_BALANCEsmallintNUMBER(38,0)Determines the Essbase time balance attribute.
0=none
1=first
2=last
3=average
SKIP_VALUEsmallintNUMBER(38,0)Determines the Essbase skip attribute.
0=none
1=skip missing values
2=skip zero values
3=skip missing and zero values
ACCOUNT_TYPEsmallintNUMBER(38,0)Determines the account type.
1=expense
2=revenue
3=asset
4=liability
5=equity
6=statistical
7=saved assumption
VARIANCE_REPsmallintNUMBER(38,0)Determines the Essbase variance reporting attribute.
1=expense
2=non-expense
CURRENCY_RATEsmallintNUMBER(38,0)If your application is set to use the built-in currency functionality, this determines which rate to use for conversion.
0=none
1=average
2=ending
3=historical
PLANNING_METHODsmallintNUMBER(38,0)No idea on this one.
USED_INsmallintNUMBER(38,0)The plan type usage for the member. This is also a bitmask that tells us which plan types are used in a single integer. This field also appears in the HSP_MEMBER table and appears to stay in sync.
DATA_TYPEsmallintNUMBER(38,0)This field is also found in the HSP_MEMBER table. It is populated in HSP_MEMBER but is always NULL in this table.
SRC_PLAN_TYPEintNUMBER(38,0)"Indicates the source of data value for account." - Direct from Oracle.
SUB_ACCOUNT_TYPEintNUMBER(38,0)"Identifies the type of account and how its useds" - Direct from Oracle.

Overall, this table is pretty simple.  We could probably stop there, but hey, how about a quick query:

SELECT
	 po.OBJECT_NAME AS Parent
	,o.OBJECT_NAME AS Account
	,CASE a.USE_445
		WHEN 0 THEN 'None'
		WHEN 1 THEN '445'
		WHEN 2 THEN '454'
		WHEN 3 THEN '544'
		ELSE ''
	 END AS WeeklySpread
	,CASE a.TIME_BALANCE
		WHEN 0 THEN 'None'
		WHEN 1 THEN 'First'
		WHEN 2 THEN 'Last'
		WHEN 3 THEN 'Average'
		ELSE ''
	 END AS TimeBalance
	,CASE a.SKIP_VALUE
		WHEN 0 THEN 'None'
		WHEN 1 THEN 'Skip Missing'
		WHEN 2 THEN 'Skip Zeros'
		WHEN 3 THEN 'Skip Missing and Zeros'
		ELSE ''
	 END AS SkipValue
	,CASE a.ACCOUNT_TYPE
		WHEN 1 THEN 'Expense'
		WHEN 2 THEN 'Revenue'
		WHEN 3 THEN 'Asset'
		WHEN 4 THEN 'Liability'
		WHEN 5 THEN 'Equity'
		WHEN 6 THEN 'Statistical'
		WHEN 7 THEN 'Saved Assumption'
		ELSE ''
	 END AS AccountType
	,CASE a.VARIANCE_REP
		WHEN 1 THEN 'Expense'
		WHEN 2 THEN 'Non-expense'
		ELSE ''
	 END AS VarianceReporting
	,CASE a.CURRENCY_RATE
		WHEN 0 THEN 'None'
		WHEN 1 THEN 'Average'
		WHEN 2 THEN 'Ending'
		WHEN 3 THEN 'Historical'
		ELSE ''
	 END AS CurrencyRate
FROM 
	HSP_ACCOUNT a
INNER JOIN
	HSP_OBJECT o ON a.ACCOUNT_ID = o.OBJECT_ID
INNER JOIN
	HSP_OBJECT po ON o.PARENT_ID = po.OBJECT_ID
ORDER BY 
	o.POSITION

This is basically a decode of all of the different fields.  Here are the results:

SQL Server:

HSP_ACCOUNT_MOracle:

HSP_ACCOUNT_O

We’ll be keeping it simple for the next few posts, focusing on the built-in dimensions that we have left.  That’s all for now!


The EPM Week In Review: Week Ending April 16, 2016

This was a shorter week for me (vacation), so I may have missed some things.  If so, let me know so that I can update this post!

Patches and Updates:

The 11.1.2.4.102 Tax Governance Patch has arrived.  This one is totally out of my wheelhouse, so good luck!

Speaking of things out of my wheelhouse, the 11.1.2.3.817 Disclosure Management patch is out as well this week.  Again…good luck.

Now back to my wheelhouse.  Less than a week following the 11.1.2.4.008 patch, the Essbase 11.1.2.4.009 patch has dropped.  This looks to be pretty straight forward.  The version reporting seems to be the most consistent thing across the various readme’s.  I guess I’ll skip .008 in my lab as I didn’t even have time to deploy it yet.

New Blog Posts:

This week I blogged about nothing!  Gasp…we’ll see if I can fix this before the week is over.

Jake shows us an awesome way to set up PBCS test accounts.  I didn’t know that gmail could do that!

I mentioned Harry’s web-based interface for Essbase last week.  This week he is opening the product up for beta users.  E-mail him to get your copy for testing.  I know I will.

Summer actually received useful assistance from Oracle Support.  Check out her post about run-time prompts and calculate form options.  Next up…pink unicorns with rainbows…sorry Oracle.  Just kidding.  I get help from Oracle Support all the time.

Christian shows us how to install EPM Maestro.  I’m not an HFM guy, outside of extracting data from it for nefarious Planning and Essbase purposes, but the post is thorough and well-written.  So if HFM is your thing, check it out!

Vinjay shows us how to use external sources for a lookup property in DRM.  Because not everything has to exist in DRM.

Tim shows us a method for generating test hierarchies of a certain size.  I generally use my handy-dandy SQL data generator for something like this, but this is a cool free way to get there.

Keith explains a method for parallel ODI execution.  Cool stuff if ODI is your cup of tea.

The Baroness PM talks a bit about the new ODTUG careers initiative.  Check it out if you are interested in a career in EPM (or already have one).

Other News:

Collaborate 16 happened this week.  I’ve never actually been, but as a ODTUG member, I believe KScope to be superior. 😉

Opal just published her first book:  Look Smarter Than You Are with Oracle Enterprise Planning Cloud.  Normally I wouldn’t post a competitor’s website, but since it happens to be Opal…I’ll make an exception.  Congrats Opal!


The EPM Week In Review: Week Ending April 9, 2016

This was a big week for patch releases and as always, a lot of a great blogging.

Patches and Updates:

The Essbase 11.1.2.4.008 patch finally hit the Proactive Support blog along.  Last week we were missing EAS, Studio, and APS.  This week we have them!  Sadly, this patch does not fix my client’s issue.  Oracle just updated my ticket says, and I quote…”sorry”.

More importantly, Oracle’s cloud and on-premises worlds have finally collided!  The FDMEE 11.1.2.4.200 patch has finally arrived.  This added cloud integration along with a ton of other important bug fixes (including a lot of unmentioned one’s).

New Blog Posts:

This week I blogged about loading SQL data into ASO in parallel.

Harry is working on a pretty awesome web-based Excel-like interface for Essbase.  I’ll be installing this when he makes it available.

Christian shows us how to change the supervisor password in ODI.  Good article, though I fear that I will have to ask clients for their supervisor password in the future instead of just knowing what it is.

Ricardo and Rodrigo published a great article on OTN exploring Planning Security with ODI.

Glenn explains an undocumented change to the way that Essbase interfaces with SQL Server in 11.1.2.4.

If you’ve ever been fighting your co-workers for RDP access, check out Pete’s guide on enabling multiple users.

The DEVEPM crew shows us how to compress remote files into a ZIP file using ODI.

Sarah shows us how to install OBIEE 12c.  Handy for those of us in the EPM space that like to cross-over.

Missing your search-icon’s in the FDMEE POV selection dialog?  Terry shows you where to find them.

The Oracle CEAL team has posted a new PDF on integrating OBIEE 12c with HFM.  This goes through the entire install process for the drivers and configuring the ADM data source.

Kate shows us around the 11.1.2.4.330 patch for DRM.  She pays particular attention to the newly introduced DRM Analytics.

Other News:

Collaborate 16 starts tomorrow in Las Vegas!  You can still register on-site here.


Parallel SQL Server Data Loads with ASO Essbase

If you have a ASO cube where timing is everything or a cube with multiple large data sets, waiting for data loads to process in series can waste valuable time. Luckily, Essbase supports parallel data loads! Sadly…while the documentation for this isn’t bad, it is inaccurate.  I’m sure it was accurate a few (or many) versions ago, but the drive names have changed as have the DLL’s.  So first, let’s set up our MaxL rule to execute multiple parallel loads from a single SQL data source.  Here’s the code:

import database RetASO.RetASO data 
   connect as hypservice identified by 'Hyp3r10n!' 
   using multiple rules_file 'dRev', 'dExp' 
   to load_buffer_block starting with buffer_id 100 
   on error write to "e:\\data\\RetASO\\dRev.txt";

So this MaxL code assumes that you have at least two load rule developed.  I’ve built a load rule for revenue and a load rule for expense.  Each of these rules load roughly 2 million rows of data into my ASO cube.  So let’s execute this and see what happens:

Parallel01

If we read the error, it tells us exactly what the problem is.  We need a data source that supports multiple connections.  For this we can turn to the included Data Direct drivers. Let’s go ahead and create a new data source to use for Essbase that will support multiple connections.  We start by firing up our ODBC Data Sources (64-bit) in under Administrative Tools on our Essbase Server.

Parallel02

Click on the System DSN tab:

Parallel03

Now add a new connection:

Parallel04

Scroll down and select the DataDirect 7.1 SQL Server Wire Protocol (on 11.1.2.4) or the DataDirect 7.0 SQL Server Native Wire Protocol (on 11.1.2.3) driver from the list.Parallel05We also need to know the driver name, so scroll over to the right and make note of the name of the DDL file.  It should be ARSQLS27.DLL (on 11.1.2.4) or ARSQLS26.DLL (on 11.1.2.3).

Parallel06

Once you click Finish you should see a new window that will let you fill in your server and database information.  Enter your information and click Test Connect.

Parallel07

Enter your credentials.

Parallel08

Assuming we’ve done everything correctly, it should establish a connection.

Parallel09

Now we have a connection, but it does not support multiple connections by default.  This means we need to tell it to allow multiple connections.  We follow the docs and we create an esssql.cfg file in the bin directory of our Essbase server:

Parallel10This is where we have to change it up a little.  The docs haven’t changed in a while so they reference a very old version of the driver.  Try this out instead:

[
Description "DataDirect 7.1 SQL Server Wire Protocol"
DriverName ARSQLS27
UpperCaseConnection 0
UserId 1
Password 1
Database 1
SingleConnection 0
IsQEDriver 0
]

Or for 11.1.2.3:

[
Description "DataDirect 7.0 SQL Server Native Wire Protocol"
DriverName ARSQLS26
UpperCaseConnection 0
UserId 1
Password 1
Database 1
SingleConnection 0
IsQEDriver 0
]

Once we save our file, we are ready to restart Essbase and give our data load another try.

Parallel11

Success!  Parallel data loads are one of the many ways that we can improve our ASO process performance.  In the future we’ll cover other ways to address ASO load performance.  Hopefully this will help those of you that tried using the docs and did not find success.


The EPM Week In Review: Week Ending April 2, 2016

The EPM community never seems to slow down with providing great content.

Patches and Updates:

Essbase 11.1.2.4.008 has been released.  It has not yet hit the Proactive Support Blog.  So here it is:

Essbase Server 11.1.2.4.008 PSU 22674292

Essbase RTC 11.1.2.4.008 PSU 22674308

Essbase Client 11.1.2.4.008 PSU 22674304

Essbase Client MSI 11.1.2.4.008 PSU 22814465

It says this:

“Essbase Administration Services 11.1.2.4.008, Provider Services 11.1.2.4.008, and Essbase Studio 11.1.2.4.008 are supported for use with Essbase 11.1.2.4.008.”

But…I can’t actually find those.  So if you happen to be able to find those, drop me a line.  Perhaps this is why it isn’t on the Proactive Support Blog yet?

New Blog Posts:

This week I covered upper-level drill-through using Drillbridge.  I really like this product more the more I use it.  I’m currently working on several more posts around advanced functionality and comparing the free version to the enterprise version.

Francisco tells us that hard-coding passwords is bad and shows us how to take care of the problem.

Summer tells us about a random date issue in Planning.

Henri shows us how to get back some of the functionality from the HFM Copy Utility in 11.1.2.4.

Cameron continues his series on PBCS in Part 9: EPM Automate.

Interested in a career in ETL?  Probably not if you read my blog…but just in case, the DEVEPM guys have a presentation coming up next week on just that topic.

Dayalan shows us how to change the default number of columns and rows loaded in Planning 11.1.2.4 and PBCS.

Celvin give the community a heart-felt thank you after his well-deserved upgrade to Oracle ACE Director status.   Personally, if I make it to director level, I’m finding a newspaper that still actually prints papers and taking out a giant advertisement.  But his post is far classier.

Doug and Joe demonstrate how easy it is to copy data from HFM to Planning using FDMEE.  I’ll be trying this on my home lab soon.

Opal gives us a little more information about FCCS now that it has made its way to Oracle site.  Ringing in at $250 per user per month, it is the most expensive of the Oracle EPM Cloud offerings so far.


Drillbridge: Enabling Upper Level Drill-through

In our last post about Drillbridge, we did the basic introduction and then ran through the steps to get it up and running. But, in the interest of simplicity, we kept it simple. Now we are ready to get a little more complex.

For today, a little more complex will be upper level drill-through.  This is one of those things that can make Essbase admin’s and DBA’s run from a building like it’s on fire.  Why?  Because upper level drill-through relies upon the end-users ability to not do something stupid.  As we all know…it’s a virtual certainty that they will.  This is where Drillbridge really shines.  We have several mechanisms to control the level of stupidity that we allow our users to engage in before we shut them down.

So let’s get started.  Log into your Drillbridge server and start by changing up the Deployment Spec.  If you remember from our first post, we started with this:

@RELATIVE("Year", 0),@RELATIVE("Measures", 0),@RELATIVE("Product", 0),@RELATIVE("Market", 0),"Actual","Budget"

We also checked the box indicating that this was Level-0 only.  Now let’s change that specification to this:

@IDESC("Year"),@RELATIVE("Measures",0),@IDESC("Product"),@IDESC("Market"),"Actual","Budget"

We have switched our Year dimension to use the IDESC function.  We have left the Measures dimension at level-0, since many times we can’t tie numbers out at upper level due to upper-level aggregation operators.  We have also switched Product and Market to IDESC as well.  We’ve left Actual and Budget alone since there is no upper level in the Scenario dimension.  We’ll also un-check the Level-0 members only option.  At the end, it should look something like this:

DrillbridgeUpper01This is our first method of preventing stupid user tricks.  We only allow drill-through that makes sense.  Now that we have our deployment spec configured, we can move on to the report.

Before we get too deep into the report, let’s first talk about how upper-level drill-through really works.  If a user chooses to drill-through on Qtr1 for instance, what does that mean?  Essbase is simply going to pass that value through, Qtr1.  But Drillbridge takes that member and uses the Essbase JAPI to determine the level-0 descendants of the member.  In our simple case, this is just Jan, Feb, and Mar.  But wait, we can’t use an equals sign in our SQL statement and evaluate multiple values, can we?  No, no we can’t.  So let’s look at a sample SQL statement that will enable our upper-level drill-through:

SELECT
	 DimMarket
	,DimMeasures
	,DimProduct
	,DimScenario
	,CONVERT(VARCHAR(10),CAST([DimYear] AS DATETIME),101) as [Date]
	,CONVERT(CHAR(3), CAST([DimYear] AS DATETIME), 0) AS DimYear
	,TransactionNumber
	,Amount
FROM
	[SampleBasic].[dbo].[FactSample]
WHERE
    DimMarket  IN {{ "name" : "Market",    "expression": "#Market", "drillToBottom" : "true" }} AND 
    DimMeasures = '{{ "name" : "Measures", "expression": "#Measures" }}' AND
    DimProduct IN {{ "name" : "Product", "expression": "#Product", "drillToBottom" : "true" }} AND
    DimScenario  = '{{ "name" : "Scenario",  "expression": "#Scenario"  }}' AND
    CONVERT(CHAR(3), CAST([DimYear] AS DATETIME), 0)  IN {{ "name" : "Year", "expression": "#Year", "drillToBottom" : "true" }}

In our last post, we didn’t really talk about the query, we just used the simple sample.  Let’s take some time now to actually understand how the query engine in Drillbridge works.  First, you’ll notice double curly braces in our where clause.  This is what tells Drillbridge to evaluate an expression.  Inside of our curly braces, we have three settings that we need to define to get back upper-level members.

First we specify the dimension that we want to pull back from Essbase.  This is the Name property.  Next we have the actual value and how we want to format it.  This is the Expression property.  If you take a look at the PDF that included with Drillbridge, you can get an idea of all of the possible expressions, but for today we’ll keep this part simple and just use #DimensionName.  Our last property is optional if we don’t care about upper-level data.  But, because we care, we must set the drillToBottom property to true.

This is the setting that tells Drillbridge to take Qtr1 and find all of the level-0 descendants.  Now all we need to do is modify our SQL statement to use an IN instead of an =.  And with that we should be ready to deploy our new report.  So let’s try it out.  Let’s start by drilling into level-0 for everything but our Year dimension.  For the Year dimension we’ll try an upper-level query:

DrillbridgeUpper02

Once we drill-through, we see that we have Qtr1 in our POV and multiple months of data:

DrillbridgeUpper03

Excellent!  We have upper-level drill-through.  But wait, what about stupid user tricks?  Let’s take a look back at our report:

DrillbridgeUpper04

Here we have two ways to prevent long-running queries executed by users.  First, we can set a row limit.  This is generally enough, but sometimes, a user can find a way to execute a query that returns a low record count, but it still takes forever.  So as a safe-guard, we can also add a query timeout.  This way we are protected on both fronts.  So let’s start with the row limit.  If we enter a row limit of 10 and try out the drill-through again, we get this:

DrillbridgeUpper05

Great!  Only 10 rows!  But wait…what about the other rows?  The downside to the Community edition is that it does not offer a message to users to let them know that additional rows were suppressed.  Bummer.  But don’t worry too much, as we have a way around this that I’ll cover in my next Drillbridge post.  We’ll also cover query time limits in a later post as I still have to resolve the issue I’m having.

And with that, you should now have working upper level drill-through with at least a row limiter.  Our next Drillbridge post will cover some of the advanced features.


PBCS April 2016 Update: FDMEE On-Premise Is Here, Kinda…

Another month…another update to PBCS.  This month we have a few very interesting items.  First, we have a new version of the EPM Automate Utility with a few new commands:

  • copysnapshotfrominstance – This command can essentially replicate one instance to another.  This could make migrations a bit faster and more streamlined and possible less error prone.
  • provisionreport – This provides a report of which roles are assigned to which users.  The cool part here is that it also shows the “sequence of inheritance”.
  • userauditreport – In case you wonder who is actually using PBCS, this report should tell you who logs in and when.
  • setsubstvars – Similar to the MaxL command that performs the same function, we can now use the EPM Automate tool to create and set substitution variables.

Now let’s talk about what really makes this release interesting.  PBCS now supports integration with on-premise FDMEE!  This is great news that we have all been waiting for.  But wait…it requires FDMEE 11.1.2.4.200.  This confirms the rumors we’ve been hearing.  So what’s the problem?  11.1.2.4.200 of FDMEE isn’t actually available yet.  On the bright side, hopefully this means it will be released by the end of April…before the May update of PBCS.

Of course we also have the long list of defects fixed in this release.  I’ll let you look at the PDF for the list:

RCD_PBCS_April


The EPM Week In Review: Week Ending March 26, 2016

Because this is a 3-day weekend for many, I’m posting this a day early.  Also, today is the last day for early bird registration for KScope16.  So what’s new this week?

Patches and Updates:

DRM 11.1.2.4.330 has been released.  This includes a ton of new features and patches.  This patch as previously been released, but has been pulled and moved around and required a password at one point.

FCM 11.1.2.4.102 has been released.  There are quite a few bug fixes, especially for ARM.

New Blog Posts:

This week I continued my series on PowerShell and Hyperion.  I focused on executing the outline load utility from a remote server.

Amit shows us how to encrypt our password using the EPM Automate tool.

Celvin has cracked the Hyperion Planning API…cool stuff.  He has also made some updates to his Essbase Member Operations utility.  Busy week for Celvin!

Eric gives us a lot of great information about Exalytics.

Kate walks us through the new features found in the recently released 11.1.2.4.200 patch for HFM.

Sarah (now over at Big Red) shows us how to find the REST URL in the Cloud.

With KScope16 rapidly approaching and presentations due in just over two months, Heli’s post about how long it takes to prepare seems appropriate.

Opal discusses the future of the cloud as it relates to Oracle and customers having the cloud on site!  It is very interesting…but not yet coming to the EPM space.  Good read either way.

John Goodwin continues his series on the FDMEE Web Services.

Other News:

Today is the last day to sign up for the reduced early registration price at KScope16.com.  Be sure to use the US-Analytics code of USA to save an additional $100.


Hyperion and PowerShell: Executing Remotely

In our last PowerShell post, we covered using the Outline Load Utility with Hyperion Planning from PowerShell.  But, now we have MaxL scripts doing data loads and Outline Load Utility scripts doing meta-data loads and they are happening on two different servers. We need a nice way to join all of this together in a single batch process controlled by one server.  This let’s us have a true start-to-finish process that we can rely on.

But wait…how do we do that exactly?  First we have some pre-work to get out of the way before we can actually execute a process remotely.  To execute a process remotely, PowerShell has an invoke command that will create a remote session on another server with specified credentials and then execute a script.  First, log into the server on which you will be executing remote commands.  Start PowerShell with Administrative rights and execute this command:

Enable-PSRemoting -Force

Because we are passing credentials, we need to keep our password out of plain text.  So, let’s start by opening up PowerShell and executing this command to generate an encrypted copy of our password:

"YourPasswordGoesHere" | ConvertTo-SecureString -AsPlainText -Force | ConvertFrom-SecureString | Out-File "PasswordFile.pass"

One quick note on passwords.  If you have special characters that cause login failures, use the ` as an escape character in front of your special character.  I’m using the password to my Hyperion Service account from my Hyperion domain.  This generates a nice new file that we’ll use to pass our password later.  For now, let’s focus on the reason you’re here…free code:

###############################################################################
#Created By:	Brian Marshall
#Created Date:	2/16/2016
#Purpose:		Sample PowerShell Script for HyperionEPM.com
###############################################################################

###############################################################################
#Variable Assignment
###############################################################################

$PowerShellUsername = "Hyperion\hypservice"
$PowerShellPasswordFile = "PasswordFile.pass"
$PlanningComputerName = "HyperionPL"
$PlanningCommand = {C:\Data\HyperionEPM\PowerShell\Blog2Sample1.ps1}

###############################################################################
#Create Credential for Remote Session
###############################################################################
$PowerShellCredential=New-Object -TypeName System.Management.Automation.PSCredential -ArgumentList $PowerShellUsername, (Get-Content $PowerShellPasswordFile | ConvertTo-SecureString)

###############################################################################
#Create Remote Session Using Credential
###############################################################################
$PlanningSession = New-PSSession -ComputerName $PlanningComputerName -credential $PowerShellCredential


###############################################################################
#Invoke the Remote Job
###############################################################################
$PlanningJob = Invoke-Command -Session $PlanningSession -Scriptblock $PlanningCommand
echo $PlanningJob

###############################################################################
#Close the Remote Session
###############################################################################
Remove-PSSession -Session $PlanningSession

And there you have it…set our variables, create a new credential for our connection, use that credential to create a remote session, execute a job, and kill the session.  So what happens when we execute this?

OutlineLoad8

Uh oh…is the PG version of what I actually said when I received this nice little message.  But, upon some research, it appears that the Outline Load Utility uses more than 150 MB of memory on execution.  But, the default limit for a remote session is 150 MB.  So now we have to connect to our remote server and start up a administrative command prompt.  Once you’ve done that, execute this:

winrm set winrm/config/winrs @{MaxMemoryPerShellMB="2048"}

You should get something like this if it goes properly:

OutlineLoad9

Now then…we can try again…

OutlineLoad10

We have a winner!  We have officially remotely executed an Outline Load Utility script…on another computer.  Cool isn’t it?


The EPM Week In Review: Week Ending March 19, 2016

This was a bit of a slow week…until it wasn’t.  Things picked up late this week.

Patches and Updates:

DRM 11.1.2.4.322 has been released.  Fixes a few bugs.

Disclosure Management 11.1.2.4.200 has been released.  There appear to be quite a few bug fixes.

The FDM to FDMEE Migration Utility V1.1 has been released.  Seems to fix a few bugs, hopefully the one making your migration difficult!

New Blog Posts:

This week, I blogged about the removal of the delete plan types button and started down the software path of the Hyperion Home Lab.

Vijay tells us how to solve IE-related issues in DRM with compatibility view settings.

Glenn reminds us not to be Glenn…oh, and he also mentions something about issues in older versions not being the solution to problems in the new versions.  But really…just don’t be Glenn! 😉

Jason tells us what he is looking forward to a Kscope this year.  I’m going to pretend I made the list…

Harry has released a new version of his cubeSavvy Utilities.

Robert tells us about Pi Day and more importantly the NGCP.  Not exactly EPM related, but I’m all for getting girls more excited about STEM.

Ludovic tells us about the member selection feature in Smart View that allows you to select either vertical or horizontal display.

Kate shows us a DRM quick tip on tracking changes to properties.

Cameron take a look at Smart Forms in his on-going PBCS series.  I have to say…Smart Forms are pretty cool.

Vijay shows us how to hack the DRM repository to rename objects.

Other News:

KScope16 early bird registration ends in a few days! Register by March 30 and use code USA to save a total of $400 on your Kscope pass.