RFC error when using BICA in Production

Question

Hi,
After final transport to Prod, we are unable to import schema from queries with dimensions in Prod. Queries without dimensions are OK.
After investigations, we noticed that we have a RFC error :
TRACE BWP dev_rfc.trc
Trace file opened at 20110222 142806 CET SAP-REL 700,0,245 RFC-VER nU 3 1139952  
======> CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 thRc=223                                                         
ABAP Programm: SAPMSSY1 (Transaction: )                                              
Called function module: BAPI_MDPROVIDER_GET_LEVELS                                    
User: BWPADM (Client: 101)                                                            
Destination: psbwpvip1_BWP_30 (handle: 1, 05465956, )                                
SERVER> RFC Server Session (handle: 1, 05465956, )                                    
SERVER> Caller host:                                                                  
SERVER> Caller transaction code:  (Caller Program: lss)                              
SERVER> Called function module: BAPI_MDPROVIDER_GET_LEVELS                            
Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 3349                                      
CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 thRc=223                       
We tried to reroute our Prod server to BW Quality in file LSDAL.ini and it is working. It seems that we have a communication problem with our BW Prod.
Have you idea of what I should check to solve it ?
Thanks
Matt

Answer 1

Hi Matt,
If you think you may be hitting a PAS maximum for # of hierarchies, you could enable PAS trace and reproduce the import and see if the trace file reports a problem with maximums.
In 7.5 you can enable this from the Administration section -> Set Application Defaults (system defaults?)
This will then automatically create files like:
a.     DEFAULTGUEST436816399_both.txt
b.     DEFAULTGUEST436816399_cmd.txt
c.     DEFAULTGUEST436816399_time.txt
in your u2018/Homeu2019 directory (u2018...Files\SAP\SSM\ApplicationServer\homeu2019).
In this instance DEFAULT is the context name, GUEST the PAS username for the context, and the number a numeric sequence generated for uniqueness. You may need to shutdown the SSM Extended Listener service in order to look at the trace files.
The _both.text file has the best info.
Can you restrict the dimension in the query before you import it to see if it loads?
Thanks,
Bill