Error in Importing Objects

Hi,
I am following the below weblog for transporting XI objects:
/people/sap.india5/blog/2005/11/03/xi-software-logistics-1-sld-preparation
We are able to export the CIM file, while importing it in the target SLD, it is showing
"The target namespace for the special import already contains data for one or more export lines. Continuing this import may corrupt the state of your data."
when i hit on "anyway import" it is showing "
"Import finished with 8 errors: 9 of 17 objects loaded (Details)". when i hit on details
Import finished with 8 errors: 9 of 17 objects loaded
The Errors:
CIM_ERR_FAILED: SAP_BusinessSystem.CreationClassName="SAP_BusinessSystem",Name="DXI" referenced by association SAP_BusinessSystemExchangeServer.Antecedent=ref"SAP_BusinessSystem.CreationClassName=\"SAP_BusinessSystem\",Name=\"BS_DXI_JAVA\"",Dependent=ref"SAP_BusinessSystem.CreationClassName=\"SAP_BusinessSystem\",Name=\"DXI\"" does not exist.
SAP_BusinessSystemExchangeServer.Antecedent=ref"SAP_BusinessSystem.CreationClassName=\"SAP_BusinessSystem\",Name=\"BS_DXI_JAVA\"",Dependent=ref"SAP_BusinessSystem.CreationClassName=\"SAP_BusinessSystem\",Name=\"DXI\""
CIM_ERR_FAILED: SAP_BCClient.CreationClassName="SAP_BCClient",Name="120.SystemName.R3D.SystemNumber.0020212393.SystemHome.sapdev2" referenced by association SAP_BusinessSystemViewedBCClient.SameElement=ref"SAP_BusinessSystem.CreationClassName=\"SAP_BusinessSystem\",Name=\"BS_R3D_120\"",SystemElement=ref"SAP_BCClient.CreationClassName=\"SAP_BCClient\",Name=\"120.SystemName.R3D.SystemNumber.0020212393.SystemHome.sapdev2\"" does not exist.
SAP_BusinessSystemViewedBCClient.SameElement=ref"SAP_BusinessSystem.CreationClassName=\"SAP_BusinessSystem\",Name=\"BS_R3D_120\"",SystemElement=ref"SAP_BCClient.CreationClassName=\"SAP_BCClient\",Name=\"120.SystemName.R3D.SystemNumber.0020212393.SystemHome.sapdev2\""
CIM_ERR_FAILED: SAP_BCClient.CreationClassName="SAP_BCClient",Name="110.SystemName.R3D.SystemNumber.0020212393.SystemHome.sapdev2" referenced by association SAP_BusinessSystemViewedBCClient.SameElement=ref"SAP_BusinessSystem.CreationClassName=\"SAP_BusinessSystem\",Name=\"BS_R3D_110\"",SystemElement=ref"SAP_BCClient.CreationClassName=\"SAP_BCClient\",Name=\"110.SystemName.R3D.SystemNumber.0020212393.SystemHome.sapdev2\"" does not exist.
SAP_BusinessSystemViewedBCClient.SameElement=ref"SAP_BusinessSystem.CreationClassName=\"SAP_BusinessSystem\",Name=\"BS_R3D_110\"",SystemElement=ref"SAP_BCClient.CreationClassName=\"SAP_BCClient\",Name=\"110.SystemName.R3D.SystemNumber.0020212393.SystemHome.sapdev2\""
CIM_ERR_FAILED: SAP_J2EEEngineCluster.CreationClassName="SAP_J2EEEngineCluster",Name="DXI.SystemHome.sapxidev" referenced by association SAP_BusinessSystemViewedJ2EEEngineCluster.SameElement=ref"SAP_BusinessSystem.CreationClassName=\"SAP_BusinessSystem\",Name=\"BS_DXI_JAVA\"",SystemElement=ref"SAP_J2EEEngineCluster.CreationClassName=\"SAP_J2EEEngineCluster\",Name=\"DXI.SystemHome.sapxidev\"" does not exist.
SAP_BusinessSystemViewedJ2EEEngineCluster.SameElement=ref"SAP_BusinessSystem.CreationClassName=\"SAP_BusinessSystem\",Name=\"BS_DXI_JAVA\"",SystemElement=ref"SAP_J2EEEngineCluster.CreationClassName=\"SAP_J2EEEngineCluster\",Name=\"DXI.SystemHome.sapxidev\""
CIM_ERR_FAILED: SAP_InstalledProduct.CollectionID="54a3cc70-223a-11db-a3df-f24b96623c12",ProductIdentifyingNumber="0",ProductName="NEOPOST_INTERFACES",ProductVendor="NEOPOST_INTERFACES",ProductVersion="1.0",SystemID="R3D.SystemNumber.0020212393.SystemHome.sapdev2" referenced by association SAP_InstalledProductLogicalApplicationSystem.Product=ref"SAP_InstalledProduct.CollectionID=\"54a3cc70-223a-11db-a3df-f24b96623c12\",ProductIdentifyingNumber=\"0\",ProductName=\"NEOPOST_INTERFACES\",ProductVendor=\"NEOPOST_INTERFACES\",ProductVersion=\"1.0\",SystemID=\"R3D.SystemNumber.0020212393.SystemHome.sapdev2\"",System=ref"SAP_BusinessSystem.CreationClassName=\"SAP_BusinessSystem\",Name=\"BS_R3D_110\"" does not exist.
SAP_InstalledProductLogicalApplicationSystem.Product=ref"SAP_InstalledProduct.CollectionID=\"54a3cc70-223a-11db-a3df-f24b96623c12\",ProductIdentifyingNumber=\"0\",ProductName=\"NEOPOST_INTERFACES\",ProductVendor=\"NEOPOST_INTERFACES\",ProductVersion=\"1.0\",SystemID=\"R3D.SystemNumber.0020212393.SystemHome.sapdev2\"",System=ref"SAP_BusinessSystem.CreationClassName=\"SAP_BusinessSystem\",Name=\"BS_R3D_110\""
CIM_ERR_FAILED: SAP_InstalledProduct.CollectionID="54a3cc70-223a-11db-a3df-f24b96623c12",ProductIdentifyingNumber="0",ProductName="NEOPOST_INTERFACES",ProductVendor="NEOPOST_INTERFACES",ProductVersion="1.0",SystemID="R3D.SystemNumber.0020212393.SystemHome.sapdev2" referenced by association SAP_InstalledProductLogicalApplicationSystem.Product=ref"SAP_InstalledProduct.CollectionID=\"54a3cc70-223a-11db-a3df-f24b96623c12\",ProductIdentifyingNumber=\"0\",ProductName=\"NEOPOST_INTERFACES\",ProductVendor=\"NEOPOST_INTERFACES\",ProductVersion=\"1.0\",SystemID=\"R3D.SystemNumber.0020212393.SystemHome.sapdev2\"",System=ref"SAP_BusinessSystem.CreationClassName=\"SAP_BusinessSystem\",Name=\"BS_R3D_120\"" does not exist.
SAP_InstalledProductLogicalApplicationSystem.Product=ref"SAP_InstalledProduct.CollectionID=\"54a3cc70-223a-11db-a3df-f24b96623c12\",ProductIdentifyingNumber=\"0\",ProductName=\"NEOPOST_INTERFACES\",ProductVendor=\"NEOPOST_INTERFACES\",ProductVersion=\"1.0\",SystemID=\"R3D.SystemNumber.0020212393.SystemHome.sapdev2\"",System=ref"SAP_BusinessSystem.CreationClassName=\"SAP_BusinessSystem\",Name=\"BS_R3D_120\""
CIM_ERR_FAILED: SAP_LogicalALESystem.CreationClassName="SAP_LogicalALESystem",Name="110.SystemName.R3D.SystemNumber.0020212393.SystemHome.sapdev2" referenced by association SAP_ALESystemViewedBusinessSystem.SameElement=ref"SAP_LogicalALESystem.CreationClassName=\"SAP_LogicalALESystem\",Name=\"110.SystemName.R3D.SystemNumber.0020212393.SystemHome.sapdev2\"",SystemElement=ref"SAP_BusinessSystem.CreationClassName=\"SAP_BusinessSystem\",Name=\"BS_R3D_110\"" does not exist.
SAP_ALESystemViewedBusinessSystem.SameElement=ref"SAP_LogicalALESystem.CreationClassName=\"SAP_LogicalALESystem\",Name=\"110.SystemName.R3D.SystemNumber.0020212393.SystemHome.sapdev2\"",SystemElement=ref"SAP_BusinessSystem.CreationClassName=\"SAP_BusinessSystem\",Name=\"BS_R3D_110\""
CIM_ERR_FAILED: SAP_LogicalALESystem.CreationClassName="SAP_LogicalALESystem",Name="120.SystemName.R3D.SystemNumber.0020212393.SystemHome.sapdev2" referenced by association SAP_ALESystemViewedBusinessSystem.SameElement=ref"SAP_LogicalALESystem.CreationClassName=\"SAP_LogicalALESystem\",Name=\"120.SystemName.R3D.SystemNumber.0020212393.SystemHome.sapdev2\"",SystemElement=ref"SAP_BusinessSystem.CreationClassName=\"SAP_BusinessSystem\",Name=\"BS_R3D_120\"" does not exist.
SAP_ALESystemViewedBusinessSystem.SameElement=ref"SAP_LogicalALESystem.CreationClassName=\"SAP_LogicalALESystem\",Name=\"120.SystemName.R3D.SystemNumber.0020212393.SystemHome.sapdev2\"",SystemElement=ref"SAP_BusinessSystem.CreationClassName=\"SAP_BusinessSystem\",Name=\"BS_R3D_120\""
did anybody come accrossed this problem? what could be the error? and also tell me how to undo this in target system?
regards

Hi Osman,
All my RFCs are working fine whether it be from the DEV system to QTY or vice versa.
Is there anything else we could check?
PFA the screenshot for your reference.
Another confusion is when try to import lat time, in log its showing error occurred for ID object,here is the screen shot,
Is there any prerequisite to transport ID object to QTY environment or any dependencies?
Regards,
Arthita

Similar Messages

"error when importing object" when selecting variant

Hello,
we recently migrated from 4.6 to 4.7.
For some programs, when selecting a variant, this gives a runtime error, like
Error when importing object "C131A2"
What is the cause of this? Because the values in the variant aren't valid anymore?
How can this be solved?
Thanks in advance for the help

Glad to help - you'll likely have to run it after every upgrade (for different reports).
Rob

Error when importing object P_lis

Hello Experts ,
I have a task assigned to me where i have to write a program to get all the reports and their variants( variants without space and non obselete variants)
When i am trying to access the variant SDCAS_ADRSEL , I am getting a dump "Error when importing object P_lis ". It has got only one variant JOJO1 in the vari table . Please help me out with this.

Hi Aditya,
You might need to provide a few more details on the dump.
I.e.
Exact details of the error that occured.
Where the error occurred
You can grab these out of the dump in ST22. That should help people out, to help understand what you are doing, as it's not really clear from your current description.
Cheers,
Katan

Got error while importing objects

Hi,
I got error with return code 8 while importing objects.
Actually, i created Multiprovider and Two queries on that and transported those objects in the same request and released in SE09 and while importing these objects I got error with Return Code 8.
Pls Help me, what i should do now.
Thanks&Regards,
Rafi

Hi Mohd.
Return code 8 is an error which indicates that some objects are missing. You will have to include these missing objects before you can create the transport successfully. In your scenario it might be a structure, CKF, RKF, missing info providers etc.
Hope it helps.
BR
Stefan

Error when importing object "MC11VA0ITM_TAB".

Hi SDN,
Error in ABAP application program.
The current ABAP program "SAPLMCEX" had to be terminated because one of the statements could not be executed.
This is probably due to an error in the ABAP program. When attempting to import data, the structure of the complex object "MC11VA0ITM_TAB" was not compatible with thetarget object.
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_IMPORT_MISMATCH_ERROR',
was neither
caught nor passed along using a RAISING clause, in the procedure
"MCEX_BW_LO_API" "(FUNCTION)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
When attempting to import data, the structure of the complex object
"MC11VA0ITM_TAB"
was not compatible with the target object. The error occurred with
component no. 522.
any inputs ...
Regards,

Hello Shiva,
It sounds like there was a change made to the extract structure while there was still data in SM13 or RSA7 or the setup tables.
This situation is described in SAP note 328181.
The solution is usually to delete the data in the setup tables and reinitialise the datasource again.
Best Regards,
Vincent

REG: Error while importing objects in SLD

Hi All,
            While importing SLD objects from Development to Production I am facing following problem
             The selected import requires model version 1.6.16 or higher. The model version of target namespace sld/active is outdated and must be updated to the required version before this import can be performed
             The error is due to different Model versions of SLD. Development is pointing 1.6.16 where as Production is pointing to 1.5.42.
        How do I upgrade my production SLD Model version to 1.6.16 ?
Thanks,
Siva

You need to download the modal content from SAP marketplace and apply it. Usually basis team is responsible for this.
VJ

Error in importing objects in STMS_IMPORT

Hi Experts,
Urgent!!
I have exported IR & ID objects under one TR (using CTS organizer) from DEV environment. While importing by using STMS_IMPORT in PI QTY system I got the following error.
RFC communications error with system/destination
%%ashost=BLPIQTY,sysnr=,lang=E,client=220,pcs=2,ic
RFC destination
%%ashost=BLPIQTY,sysnr=,lang=E,client=220,pcs=2,icce=1,cf
it=0x20 does not exist.
Please suggest some way out !!
Thanks,
Arthita

Hi Osman,
All my RFCs are working fine whether it be from the DEV system to QTY or vice versa.
Is there anything else we could check?
PFA the screenshot for your reference.
Another confusion is when try to import lat time, in log its showing error occurred for ID object,here is the screen shot,
Is there any prerequisite to transport ID object to QTY environment or any dependencies?
Regards,
Arthita

Error while import objects:view or table

Action: Right click on views under the module tree. select import menu. select view checkbox. Click on view (trying to import view)
API2206:Connection to source failed.
ORA-02019:Connection descriptor for remote database not found.
The error is so obvious, but I can not figured out what's run on my setup. Can anyone help? Did I miss anything else? Thanks.
This project runs OK in owb 9i. I imported the mdl to owb client 10g.
Create location, connector, deploy and register to runtime on 10g instance OK. Create a runtime and connection through deployment manager is OK.
Property of this module is updated with the new location.Source for metadata import is through dictionary.

Hi,
Do you know what's the "connection descriptor" the error msg is referring to? I thought it may be the connector. But it's set OK.
Under the "connection" tab from the module property, I check the first checkbox, Oracle Data Dictionary, for Source for Metadata Import. It's working OK before.
Thanks.

Error when attempting to IMPORT object "TS_CHECK".

When using in BI SAP NetWeaver 2004s (700 - SP 15) the transaction ST04old -> Detail analysis menu -> Summary report
The following short dump occurs:
Runtime Errors         CONNE_IMPORT_WRONG_COMP_TYPE
Except.                CX_SY_IMPORT_MISMATCH_ERROR
Date and Time          19.11.2008 15:14:08
Short text
Error when attempting to IMPORT object "TS_CHECK".
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLSTD4" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_IMPORT_MISMATCH_ERROR', was
not caught in
procedure "DB02_ORA_FILL_TS_CHECK__CRITOB" "(FUNCTION)", nor was it propagated
by a RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
When importing the object "TS_CHECK", the component no. 4 in the
dataset has a different type from the corresponding component
of the target object in the program "SAPLSTD4".
The data type is "I" in the dataset, but "N" in the program.
Missing RAISING Clause in Interface
Program                                 SAPLSTD4
Include                                 LSTD4U03
Row                                     1
Module type                             (FUNCTION)
Module Name                             DB02_ORA_FILL_TS_CHECK__CRITOB
Trigger Location of Exception
Program                                 SAPLSTD4
Include                                 LSTD4U03
Row                                     51
Module type                             (FUNCTION)
Module Name                             DB02_ORA_FILL_TS_CHECK__CRITOB
Source Code Extract
Line
SourceCde
21
DATA: BEGIN OF TD110.
22
INCLUDE STRUCTURE TD110_STRU.
23
DATA: END OF TD110.
24
25
CURR_TIME = SY-UZEIT.
26
CURR_DATE = SY-DATUM.
27
28
CALL FUNCTION 'GET_DB_ORA_RELEASE'
29
IMPORTING
30
ORACLE_RELEASE = ORA_REL.
31
32
IF FLAG_REFRESH = 'y'. FLAG_REFRESH = 'Y'. ENDIF.
33
flag_refresh = 'Y': Es soll in jedem Fall auf die DB zugegriffen werd.
34
35
CLEAR TS_CHECK. REFRESH TS_CHECK.
36
CLEAR CRITOBJ. REFRESH CRITOBJ.
37
CLEAR NR_CRIT_OBJ.
38
39
IF FLAG_REFRESH <> 'Y'.
40
41
Suche zunächst im Arbeitsspeicher !
42
CLEAR TS_CHECK_CACHE. READ TABLE TS_CHECK_CACHE.
43
IF NOT ( TS_CHECK_CACHE IS INITIAL ) .
44
TS_CHECK[] = TS_CHECK_CACHE[].
45
CRITOBJ[] = CRITOBJ_CACHE[].
46
OK_1 = 'Y'.
47
48
Suche danach in 'MONI' !
49
ELSE.
50
PERFORM PREPARE_MONIKEY USING 2.
>>>>>
IMPORT TS_CHECK CRITOBJ FROM DATABASE MONI(DB) ID MONIKEY.
52
53
IF SY-SUBRC = 0.
54
OK_1 = 'Y'.
55
TS_CHECK_CACHE[] = TS_CHECK[].
56
CRITOBJ_CACHE[] = CRITOBJ[].
57
ENDIF.
58
ENDIF.
59
60
'Same procedure' für datetime:
61
IF NOT ( TD110_CACHE IS INITIAL ).
62
DATETIME-MONI_DATE = TD110_CACHE-DATUM.
63
DATETIME-MONI_TIME = TD110_CACHE-UZEIT.
64
ELSE.
65
PERFORM PREPARE_MONIKEY USING 3.
66
IMPORT TD110 FROM DATABASE MONI(DB) ID MONIKEY.
67
IF SY-SUBRC = 0.
68
DATETIME-MONI_DATE = TD110-DATUM.
69
DATETIME-MONI_TIME = TD110-UZEIT.
70
TD110_CACHE = TD110.
Only related SDN post is following, but solved by changing permissions for saposcol.
Only related SAP Note is SAP Note Number 597743 "DB02: Poor entries for critical objects list", but not applicable for current SAP version.
For me strange is that this issue occurs on the development system, but not on the acceptance and production system.
Thanks in advance for any assistance.
KR
Gidion

Received the solution from SAP Active Global Support:
This error occurs due a corruption in the table MONI.
For solving this issue you need to clean the records of this table via the following path :
1. Call transaction ST03
2. With GOTO -> Performance database -> Content of database
3. Push button Delete data group
4. Enter ID DB
5. Continue
6. Confirm the delete
If you wish to backup the data before deleting the entry please follow the steps in the note 1000275 "DB02: history data backup procedure".
Regards,
Gidion

Error importing objects into a client

Hi All
I have a scenario where i am getting the following error.
Import failed because of business system transfer of object Communication Channel | XXX_123 | RFC_ABC_Receiver_XX: Obligatory transport target for business system XXX_123 not found in System Landscape Directory
Currently we have in Test Environment, a scenario where the data is sent to 2 clients, so all the changes have made in the Receiver determination for the data to go 2 clients. But when we transport all the objects to another testing environment, there is only one client where the data has to go to. When i am trying to import, i am getting this error. Is there a work around for this ? I dnt want to go back and make changes in Dev, Test again. I just dont want those Business system to be mapped to something ( Is there an option for it to skip mappings to get imported )
Please suggest.

Hi,
Check the similar discussion
Re: Error During Transport
Re: Transport error from XI 3.0 to PI 7.0
Thanks!

Error while Importing SYSTEM objects into 9.2.0.6

HI,
I got the following error while importing data into 9.2.0.6 DB .
It is related to a SYSTEM object.
. importing SYSTEM's objects into SYSTEM
IMP-00017: following statement failed with ORACLE error 2270:
"ALTER TABLE "DEF$_CALLDEST" ADD CONSTRAINT "DEF$_CALL_DESTINATION" FOREIGN "
"KEY ("DBLINK") REFERENCES "DEF$_DESTINATION" ("DBLINK") ENABLE NOVALIDATE"
IMP-00003: ORACLE error 2270 encountered
ORA-02270: no matching unique or primary key for this column-list
Constarint exists on Composite Primary Key on the parent table.
Can anybody help me out on this.
Regards,
Sumit Singh Chadha

Hi,
don't mentioning why are You importing SYSTEM objects, the error that You have, just looking the message, is due to an export done without the clause CONSISTENT=Y (so all relations parent/child preserved) having the replication (the table in error is one of the replication dictionary table) active (not quisced)
Repeat the export operation using CONSISTENT=Y an stop replication activity.
Hope this helps
Max

Error in importing Configuration objects of PI 7.0 to PI 7.1

Hi All,
My server is upgraded from PI 7.0 to PI 7.1.
I am getting Error while importing Configuration objects of PI 7.0 to PI 7.1 now.
Pls see the below error
Attempt to access the 1 requested objects on 1 failed. Detailed information: com.sap.aii.ib.core.roa.RoaObjectAccessException: Attempt to read object Adapter Metadata Mail | http://sap.com/xi/XI/System, type AdapterMetaData from application REPOSITORY on system REPOSITORY failed. Object does not exist. Detailed informatio n: Software component version with key ID: b38bcd00e47111d7afacde420a1145a5 not found
Pls suggest

Hi,
It seems that adapter metadata has not been loaded into integration repository and because of that when you are trying to import configuration objects in ID then you are getting the error.
The SAP adapter metadata objects are located under the namespace http://sap.com/xi/XI/System of software component SAP BASIS.
What you can do is, if you have installation dvd's then you can copy from their or you can simply [_DOWNLOAD_|https://websmp205.sap-ag.de/~form/handler?_APP=00200682500000001943&_EVENT=SEARCH&HIDE=&SEARCH_SPAT=X&SEARCH_BPAT=X&SEARCH_CD=X&SEARCH_P=X&SEARCH_PV=X&SEARCH_C=X&SEARCH_CV=X&SEARCH_TA=&SEARCH_V=&HIDE_EXPERT_SEARCH=X&SEARCH_MAX_RESULT=20 ] from sap market place (refer this [thread|how to import Adapter metadata;) (you must have S-user id for this) and then after you need to do as mentioned below...
1. First unzip the file (if it is zipped) and then put it in the import directory: \usr\sap\<SID>\SYS\global\xi\repository_server\import\
2. Now login to IR and then from menu TOOLS ---> Import design objects and import it.
3. After that in ID, Environment ---> Clear SLD Data Cache
4. Now you can try to import configuration objects...
Regards,
Sarvesh

Error : while Importing SAP Objects in ESR.

I am getting error, while importing SAP object in a scenario in ESR.
What can be the issue ? as we have configured all the beckend settings & sldcheck is also OK.
Also, we are using proxy scenarios are working fine on system.
The details are as below :
    at com.sap.aii.ib.server.upload.UploadServiceBean.openSAPSource(UploadServiceBean.java:88)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatefulTransactionAssociation.invoke(Interceptors_StatefulTransactionAssociation.java:43)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatefulSessionInstanceGetter.invoke(Interceptors_StatefulSessionInstanceGetter.java:37)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
    at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
    at $Proxy1366.openSAPSource(Unknown Source)

Hello,
Have you used the notes to import ESR content?
Refer to one of them according to your system version:
PI 7.1X:
#1152640 - SAP NetWeaver 7.1 including EHP 1: Importing ESR content
XI 7.0:
#836200 - SAP NetWeaver 7.0: Importing Process Integration Content
XI 3.0:
#705541 - XI 3.0 (SP1 and higher): Importing XI Content
Regards,
Caio Cagnani

Error in BW import objects

Hello,
We're trying to import into Quality BW environments the required objects to store the information generated by SAP Data Service information.
In tx RSA1 the source system for DS has been created and check works fine, but when we import the transport order following error is showed:
Could you help us?
Thanks,
Àlex

Hi Alejandro,
Exactly this error due to the mismatch source type. May be the configured QA source system working fine but importing object from Development referring different source type.
Hope the problem will be resolved after correcting the source type.
Regards
M Ramesh

Error during Directory Objects Import

Hello,
I am facing an error while importing Directory objects as
Import Failed due to Business system Transfer of Objects.
Obligatory Transport Target Business system not found in Systtem Landscape
Directory. Please advise what could be the issue.
Mohit

Mohit,
In order to transport objects in the Directory, the SLD has to contain information on transport targets. This information is needed to replace systems in your transport source with their equivalent in the transport target environment. For instance, if your transport comes from development and contains a receveir determination for an IDoc coming from your ERP system called 'DEV', XI will try to replace the system 'DEV' with the equivalent in your acceptance environment ('ACC'). This informantion needs to be entered in the SLD. See [Configuring Groups and Transport Targets|http://help.sap.com/saphelp_nw04/helpdata/en/ef/a21e3e0987760be10000000a114084/frameset.htm] for more information.
Kind regards,
Koen

Error in Importing Objects

Similar Messages

Maybe you are looking for