Skip to Content
0
Former Member
Dec 18, 2007 at 08:11 AM

JCO.Client not connected in repository call

38 Views

I am getting following error during template implementation for BI.

Element 'SAPConfigLib.IDS.Unclassified.createRfcDestination':!BrokerImport.import_of_element_failed!!BrokerImport.Fehler!com.sap.tc.lm.ctc.cul.cpi.exceptions.CPIBaseException: < Localization failed: ResourceBundle='com.sap.tc.lm.ctc.cul.cpi.CPIResourceBundle', ID='com.sap.tc.lm.ctc.cul.cpi.BaseException_BASE_EXCEPTION', Arguments: [] > : Can't find resource for bundle java.util.PropertyResourceBundle, key com.sap.tc.lm.ctc.cul.cpi.BaseException_BASE_EXCEPTION:com.sap.tc.lm.ctc.provider.javaServiceProvider.JavaServiceWriter.writeElement!BrokerImport.LINE!157-:com.sap.tc.lm.ctc.cul.broker.BrokerImport.importElement.86

-:com.sap.tc.lm.ctc.cul.broker.BrokerImport.importElement.128

-:com.sap.tc.lm.ctc.cul.broker.BrokerImport.importElement.128

-:com.sap.tc.lm.ctc.cul.serviceimpl.importservice.CULConfigurationImport.importConfiguration.96

-:com.sap.tc.lm.ctc.ccl.templateinstaller.StepExecuter.run.41

Element 'SAPConfigLib.IDS.Unclassified.createRfcDestination':Error during executing Java Reflection:JCO.Client not connected in repository call

2 Update Table RSPOR_T_PORTAL Not executed yet

I tried to apply SAP note:677732 for this issue:

Reason and Prerequisites

The SAP S_DDIC_MDI profile that contains the minimum authorizations for accessing the DDIC using MDI does not yet exist in the R/3 System. This profile is not normally available in 4.6C and 4.6D, but it is available as of a particular Support Package in 6.10 or 6.20.

Solution

1. Create a Z_RFC_DD_MDI authorization (you can also select a different name) for the S_RFC authorization object of the AAAB class with the following instances:

Activity: 16

Name of the RFC object to be protected: RFC1, RFC2, SDDO, SDIFRUNTIME, SG00, SRFC, SYST, SYSU, SIFD, SIMG, SDNT

Type of RFC object to be protected: FUGR

1. Create a Z_DDIC_MDI profile (you can also select a different name) and insert the Z_RFC_DD_MDI authorization into this.

Still having same issue. Any sugession.