Short dumps caused by Solution Manager BW

[Former Member]

We encounter short dumps caused by Solution Manager BW:

Category               ABAP Programming Error

Runtime Errors         SAPSQL_INVALID_TABLENAME

Except.                CX_SY_DYNAMIC_OSQL_SEMANTICS

ABAP Program           SAPLSCSM_BI_DATALOAD

Application Component  SV-SMG

Date and Time          24.04.2013 13:42:34

...

An invalid table name "/BI0/ACCMCURR200" was specified in an Open SQL command:

The steps in note 1830835 can't be executed, when I try to I get the error message

RFC destination to BI system/client not found. Set it in step "Specify
SAP BW System" of "Basic Configuration"

When I try to set it, nothing happens (step remains green). I also tried to use a remote BW system which doesn't work as well... Note 1715482 is not relevant for my patchlevel (Solution Manager 7.1 patchlevel 8). I raised an OSS message, but maybe someone else encountered the same problems - any help is appreciated.

[Former Member · Accepted solution]

SAP support solved this problem, we needed to implement note 1793384.

[Former Member]

Hi Daniel,

please check with FM(SE37):   RS_MANDT_UNIQUE_GET  the BW - MANDT.

If theres is no entry you cat set the BW Mandant (usually  BW-Mandt  =  SolMan Mandt) via FM: RS_MANDT_UNIQUE_SET.

Afterwards execute all steps mentioned in step 5 of Basic Configuration (especially BW part of configuration step).

regards

Volker

[Former Member]

Hi Volker,

RS_MANDT_UNIQUE_GET returns 001 as BW client but no RFC... Is there a way to set the RFC destination to NONE?

Best regards,

Daniel

[Former Member]

Hi Daniel,

is your SolMan client also '001' ?

If yes than goto SM59 an create a NONE (ABAP) Connection or choose the name of yout SolMan <SID> .

If your SolMan Client <>  BW Client, please  use FM RS_MANDT_UNIQUE_SET   MANDT = <SolManClient>

regards

Volker

[Former Member]

The SolMan client is 001, and NONE exists already.