SAS® Financial Management reports and forms might display red cells after you update one or more dimensions


An issue might occur where all cells are red when you open SAS Financial Management reports (read-only and CDA tables) or forms (data-entry tables).

If the red cells are displayed after a dimension loads, the changes that you made to the formula might cause this issue to occur when the report or form includes a dimension member with a modified formula.

When this issue occurs, an error similar to the following should be displayed in the <SASConfig>\Lev1\Web\Logs\SASServer3_1\SASFinancialManagement5.x.log:

WARN  RemoteInvocationTraceInterceptor Processing of HttpInvokerServiceExporter remote call resulted in fatal exception: com.sas.solutions.odcs.client.interfaces.VCubeManagerInterfaceRemote.loadVCube
java.lang.NoClassDefFoundError: Scope690853320815280 (wrong name: Scope6908530815280)

This error means that there is something wrong with the scoping. You can break the ScopeId down into  
ScopeId class name = formulaId + oldRevision + (-targetDimInternalId) + targetMemberId.

To identify the ID, complete the following steps:

1. Compare the two scope numbers and make note of the common parts, as shown in the following example:

2. Then, run the following code using an SAS Enterprise Guide session that runs on the Compute tier (and is customized to access your environment):

LIBNAME SASSDM POSTGRES  PRESERVE_COL_NAMES=NO  PRESERVE_TAB_NAMES=NO  DATABASE=sassdm  SERVER="ServerName" PORT=9632  USER=sassdmdbadm  PASSWORD="XXX" ;

proc sql;
select member_id, member_cd
from sassdm.sas_member
where member_id in (
   select target_member_id
   from sassdm.sas_formula_target
   where formula_id = 690853 );
quit;

This code verifies that the formulaID of 690853 exists. Now, you have the name of the target_member_id and the target_desc (which is the name of the formula).

Workaround

To solve the error, complete the following steps:

  1. Look up the target_member_id from the sas_member table, which gives you the member_cd.  
  2. Remove and then re-add the scope for the member in the message.
  3. Restart servers 3, 4, and 5.

Note: These steps circumvent the issue except when the formula scope is more than one.