Error in importing idoc cremas03

Dear all,
I am trying to import an idoc cremas.cremas03 in XI but it is giving following messages
" import started"
" Idoc type cremas03 contains error(unable to read segments)
" idoc import failed with 1 error "
i have tried to import 4 to 5 idoc types but all of them are giving the same error
kindly help
Regards
Tarang

Hi,
Refer the following Link
Import IDOC into XI fails - unable to read segments
Regards,
Ashwin M
[Dont forget to mark Useful replies]

Similar Messages

Error when importing IDOC structure from SAP - Control record missing

Hi!
We are hitting problems when importing IDOCs from SAP into the Integration Builder. The import ends successfully but when we drill into the IDOC structure we get a message: Schema for type EDI_DC40.ASN_OUT.DELVRY01.Z1DELVRY (category Data Type) not found. This is only happening for one specific IDOC type only. We have checked all we can think of but cannot get this to work. Any help would be very much appreciated. Of course, points awarded for any good ideas. Thx, Duncan

Hi Duncan,
Taka a look at these threads which address similar issues:
Error during import of FIPARQ01 Idoc
Error during IDoc Import
Importing idocs:
http://help.sap.com/saphelp_nw04/helpdata/en/2b/a48f3c685bc358e10000000a11405a/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/78/21753251ce11d189570000e829fbbd/content.htm
Hope these help!.
Cheers,
Chandra
Message was edited by: chandravadhana gopalakrishnan

Error while Importing Idoc with Extension

Hi All,
I already imported idoc with extension and working fine. When I tried to transport the Idoc from Dev XI to Prd XI . I got the following error
The objects as displayed in the navigation tree are possibly not up-to-date.
So I tried to Re import the Idoc in IR but it is ending with below error
+ com.sap.aii.ibrep.sbeans.upload.RemoteUploadException: The objects as displayed in the navigation tree are possibly not up-to-date.
I already saw some threads in SDN for this error but I am not getting solution.
Can anyone provide a solution ASAP for the above error .
Regards,
Prakash

> When I tried to transport the Idoc from Dev XI to Prd XI . I got the following error
Why are you transporting it form Dev? Why not from QA to Prd.
Since this is a Z-IDOC so check if the extension has been released from R3 after doing any modification.
Regards,
Sarvesh

Error while importing idocs in IR

This is the error when I try to import Idocs in IR.
"Unable to establish connection to R/3 system FR3 (client=850) Troubleshooting tips:
Is the target system online?
Check the connection data (note that server names and groups are case-sensitive)
Tips for administrators (see the configuration guide for more details):
Does the user have the required authorizations in the target system?
Is the target system configured correctly in "etc/services"?"
I have logged into the system and I have all the rights but still not able to figure out why I am unable to import Idocs /RFC

Hi ,
Check if the logsys name maintained in SLD is the same.
You can view using the t-code scc4. Note that the entires are case sensitive.
Also see if the tRFC port port cofiguration for importing metadata is correct ( Used tc IDX1 )
Reward points if found useful
Rgds,
Sandeep

Regd internal error while importing IDOCs and RFC's

Hi All,
Any idea, why i am getting internal error while importing RFX from ECC system to Dev system of PI.
It takes lots of time to import and many times it shows internal error.
I am able to login and select the RFC ... but all of sudden after selection ..the window gets freezed and i have to End task the IR part.
Is this a system error which only basis can fix?, have anyone faced similar issue.If yes please reply ..
Regards
Srini

Hi Srinivas
sevral times i faced this issue , ask your basis person , to increase the heap size a little more at XI server ,
and most of the time it happens due to Network down / connectivity .
take the help of your network team and basis team .
Regards
Abhishek

Password Error when importing IDOCs or RFC

After spending a long time figuring out why the import IDOC function in Integration Builder kept rejecting my password - it finally occurred to me to try it in UPPERCASE even though the password is in lower case it worked. I guess this is a bug in the logon module for importing RFC's and IDOCS as imported objects.

Hi Andrew,
Welcome to the party
Is your XI system on SP 11 ?
Read this Thread:
Re: Unable to Connect to SAP R/3 System
Regards,
Sridhar

Error in importing IDOC

The Same Error is displayed for many idoc s which i am trying to import
Hrmd_a06,05..
Import started...
HRMD_A.HRMD_A05:
+ com.sap.aii.ibrep.sbeans.upload.RemoteUploadException: Documentation DE.OBJEKTID | urn:sap-com:document:sap:docu is already locked in another change list by user gopaln
Import failed with 1 error
Pl say what could be the reason.
I checked in the change list of gopaln and found no idocs there also I checked if it is locked in administration no locks are there
Pl clarify
Thanks
Srini

Hi Srinivas,
1. Pls do check whether any other user tried to import this idoc and is in his change list w/o being activated. If so transfer the same to your user id and get it activated.
2. Pls do check http:<server>:<J2EE port>/rep/support/public/LockAdminService (for this link mostly a user with XISUPER only will work) and delete the locked objects from the list and try activating it again.
Cheers
JK

Unable to Import Idoc from R/3 System.

Hi,
I am facing an error while importing Idoc (SERDAT.SEERDAT01) from 4.6c R/3 system, the errror is "unable to read the segments" and the same Idoc I am able to import successfully from ECC6 system. Please let the solution for the same.
Thanks & Regards,
Pragathi.

check if you have the proper authorizations
From Note: 837595
Authorization object S_RFC
Field name RFC_TYPE value FUGR
Field name RFC_NAME value EDIMEXT, SDTX
Field name ACTVT    value 16
Authorization object S_IDOCDEFT
Field name ACTVT   value 03
Field name EDI_CIM value ' '
Field name EDI_DOC value TXTRAW01
Field name EDI_TCD value WE30
Authorization object S_CTS_ADMI
Field name CTS_ADMFCT value TABL
Authorization object S_TABU_DIS
Field name ACTVT      value 03
Field name DICBERCLS value

Not able to import Idoc in to XI Design Environment

Hi all,
I am facing error while importing Idoc from a SAP Retail R/3.
the error is :

>>>Is the target system online?
>>>Check the connection data (note that server names and groups are case-sensitive)
>>>Tips for administrators (see the configuration guide for more details):
>>>Does the user have the required authorizations in the target system?
>>>Is the target system configured correctly in "etc/services"
I would also like to clear that,
1 the system is online
2 Connection data is correct
3 etc/services an entry already exists in XI server as well as retail system
Regards,
Ramesh P

In addition to what has already been said; Also make sure you have the proper authorizations to import IDoc into XI.
Ref:
From Note: 837595 
Authorization object S_RFC
Field name RFC_TYPE value FUGR
Field name RFC_NAME value EDIMEXT, SDTX
Field name ACTVT value 16
Authorization object S_IDOCDEFT
Field name ACTVT value 03
Field name EDI_CIM value ' '
Field name EDI_DOC value TXTRAW01
Field name EDI_TCD value WE30
Authorization object S_CTS_ADMI
Field name CTS_ADMFCT value TABL
Authorization object S_TABU_DIS
Field name ACTVT value 03
Field name DICBERCLS value

Urgent: Error during Import Metadata for IDoc

Hi
We successfully imported the metadata for IDoc from R/3 in Development and Test box and everything worked fine.
Now, when we try to import the metadata for IDoc in Production box it gives me an error" Basic type 'IDoc name' does not exist". I went back to the development box and I try to import some other Idoc metadata and it gives me the above error message.
I checked RFC destination, IDX1 and everything seems to works fine. Any suggestions will be helpful.
Thanks
Mohan

Hi Mohan,
Did you execute IDX2? And if so, please delete existing meta data for port and reimport, if you still receive an error check your R/3 connections (SM59) and port definitions in the receiver IDOC channel (directory)!
Cheers,
Paul

Error in importing an idoc

hi friends,
i am new to xi.when importing an idoc say from ecc5 to xi for a file to idoc scenario,I am getting this message-'System ECC is running on the specified application server. However, source system sapecc50 is specified in software component version FILE_TO_IDOC_COMP , 3.0 of sap.com Do you want to disconnect?' - Could anyone help me out.Thanks in advance

hi karthik,
this is just a message.. you can say yes and give the necessary details to connect to the system and import the idoc.
when you double click on your SCV, there is a system that is specified there.. i guess, the idoc you are trying to import is from another. hence, you can give the details of the system you want to import idoc from.

Unable to import idoc into PI 7.0 system from SAP r/3 system

Hi Experts,
    I am getting an error while importing an Idoc structure from SAP r/3 system. The error says "unable to read Idoc segments". The Idoc has recently undergone changes. When We are looking at the struture of idoc through IDOCSYN table it is showing updated structure in SAP R/3 system but import to SAP XI is failing.
Can you suggest some way to tackle this kind of problem.
regards
Anupam

Hi Francis,
   This was indeed an authorization issue. Thank you so much for your valuable suggestion. The user lacked proper authorization to import the idocs.
Hi All,
    Thank you for all your support.
Regards
Anupam

SM 58 error while posting Idoc

Hi
I have installed a Netweaver XI 7.0 recently and have completed postinstallation tasks.
Communication between all XI components (i.e IR, ID and SLD is working.)
I am trying to test an Idoc to File scenario and while posting an Idoc from my R/3 system I am hitting upon this error "No service for system SAPD46, client 800 in Integration Directory".
I have scanned SDN forums and came across note 940313 which talks about the registration of R/3 system on SLD by one of the two methods as below..
Business system
Activities in the System Landscape Directory (SLD)(Create technical system):
      Create a technical system for system ABC in the SLD, and create the client for this. Do not forget to assign an "ALE logical system" (for example, "ABCCLNT123") to this technical system.
      SLD (Business system):
      You can now explicitly assign a business system to this client.
      For more details, refer to the SLD documentation.
      Activities in system ABC (self-registration in the SLD):
      Alternatively, you can register the system in the SLD in system ABC with Transaction RZ70. You will find detailed information about the SLD registration of systems on the SAP Service Marketplace for the "Exchange Infrastructure" in the document "Exchange_Installation_Guide.pdf".
      In system ABC, you can check your configuration with Transaction SLDCHECK.
      Activities in Integration Directory (import business system from SLD):
      You will find the business systems under Services Without Party in the Integration Services. In the Service menu, you will find the system identifiers, the client, and the corresponding ALE logical system under "Objects"->"Adapter-specific identifiers".
      Use the Import/Update button to copy the data from the SLD, to create business systems, or to update their identifiers.
I have performed activities highlighted in BOLD. But still error is same.
My question from XI Gurus is that is there any way to know if the manual step of registering my R/3 system in SLD is sufficient (As the SLD bridge for my R/3 system is not configured and I can not use auto registartion.)
Is there any way to check if the R/3 system is successfully registered.
Thanx
Lovein
Edited by: Lovein Khullar on Sep 17, 2008 11:16 AM

Hi,
I think it is due to basis problem, at ID one of service is not working. Please check below mention link for configuration steps
http://help.sap.com/bp_bpmv130/Documentation/Installation/Configuration_Guide_FP.pdf
Meanwhile check all authorization for IDOC processing, else can't process idoc in XI
For IDOC to FILE scenario follow below steps
1. Define Logical system through BD54 after that assign logical system to client through SCC4 window in R3 & XI systems
2. Define RFC destination through SM59 window in R3 & XI
3. Define Port & partner profile through WE21, WE20 windows
4. Trigger idoc from transaction code or test window through WE19.
5. In XI configure SLD under define Product, Component, Technical & business system, it should be WEB as ABAP type.
6. Import component from SLD to ID window meanwhile import idoc from R3
7. Define target structure according to ur requirement and map accordingly
8. Define ports IDX1 & IDX2 in XI
9. In ID define scenario under import business system and configure steps according to ur requirement. Here IDOC is sender so no need communication channel and sender agreement.
It will work without fail

Could not log on to SAP R/3 from XI system to import IDOC/RFC objects

Could not log on to SAP R/3 systems from XI system to import IDOC/RFC objects:
As soon I enter the SAP IP address, system number, user id and passowrd , getting following error.
Details
java.lang.ArrayIndexOutOfBoundsException
STACKTRACE:
com.sap.aii.ibrep.sbeans.upload.RemoteUploadException: java.lang.ArrayIndexOutOfBoundsException
 at com.sap.aii.ibrep.sbeans.upload.UploadServiceBean.openSAPSource(UploadServiceBean.java:79)
 at com.sap.aii.ibrep.sbeans.upload.UploadServiceRemoteObjectImpl0.openSAPSource(UploadServiceRemoteObjectImpl0.java:320)
 at com.sap.aii.ibrep.sbeans.upload.UploadServiceRemoteObjectImpl0p4_Skel.dispatch(UploadServiceRemoteObjectImpl0p4_Skel.java:196)
 at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:291)
 at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
 at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
 at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
java.lang.ArrayIndexOutOfBoundsException
Can anyone help me to solve this issue.

Venkat,
You can download them from http://service.sap.com/download
For 4.6c follow
Download
 Support Packages and Patches
 Entry by Application Group
Select Support Packages and Patches -> SAP Application Components -> SAP R/3 -> SAP R/3 4.6C -> Entry by Component
Mainly You need SAP ABA 4.6C and SAP BASIS 4.6C and SAP APPL 4.6C
The most latest one is Support Package 50. What you can do is after applying half of them you can try to logon from XI system for import of RFC/IDoc.
regards
SKM

Unable to import IDoc into NWBPM from NWDS

Dear PO Experts,
We are migrating an existing interface
(IDoc<-->PI<-->SOAP using BPM (Multiple sync calls)).
We are un able to import IDoc into NW BPM project as a service Interface. (For BPM we exported IDoc into local system as an external definition and did few modifications to the xsd as per below blog and exported back to PO server as an external definition.Create Service Interface for the same .
http://scn.sap.com/community/process-orchestration/blog/2014/09/24/idoc-to-nw-bpm-scenario#comment-542653 )
We are getting below exception while importing IDoc Service Interface into BPM project.I have attached IDoc WSDL file for your reference.Could you please share your expertise on this issue.
>>>An internal error occurred during: "Importing MOIN models for XSDs and WSDLs...".
java.lang.OutOfMemoryError: Java heap space
at java.util.ArrayList.<init>(ArrayList.java:112)
at org.eclipse.xsd.impl.XSDParticleImpl$XSDNFA.initialize
(XSDParticleImpl.java:1271)
at org.eclipse.xsd.impl.XSDParticleImpl$XSDNFA.<init>
(XSDParticleImpl.java:1050)
at org.eclipse.xsd.impl.XSDParticleImpl$XSDNFA.initialize
(XSDParticleImpl.java:1149)
at org.eclipse.xsd.impl.XSDParticleImpl$XSDNFA.<init>
(XSDParticleImpl.java:1039)
at org.eclipse.xsd.impl.XSDParticleImpl$XSDNFA.initialize
(XSDParticleImpl.java:1272)
at org.eclipse.xsd.impl.XSDParticleImpl$XSDNFA.<init>
(XSDParticleImpl.java:1060)
at org.eclipse.xsd.impl.XSDParticleImpl.getDFA
(XSDParticleImpl.java:2041)
at org.eclipse.xsd.impl.XSDModelGroupImpl.validateRoot
(XSDModelGroupImpl.java:599)
at org.eclipse.xsd.impl.XSDComplexTypeDefinitionImpl.validate
(XSDComplexTypeDefinitionImpl.java:1408)
at org.eclipse.xsd.impl.XSDConcreteComponentImpl.validate
(XSDConcreteComponentImpl.java:565)
at org.eclipse.xsd.impl.XSDSchemaImpl.validate(XSDSchemaImpl.java:1653)
at com.sap.tc.esmp.tools.core.util.EMFUtils.validate(EMFUtils.java:613)
at
com.sap.tc.esmp.tools.xsd.xml.EmfSchemaImporter.calculateAffectedPartitions(EmfSchemaImporter.java:903)
at
com.sap.tc.esmp.tools.wsdl1import.Wsdl1Importer$ImportChain.calculateAffectedPartitions(Wsdl1Importer.java:365)
at
com.sap.tc.esmp.tools.wsdl1import.Wsdl1Importer$ImportChain.resolveImportLink(Wsdl1Importer.java:545)
at
com.sap.tc.esmp.tools.wsdl1import.Wsdl1Importer$ImportChain.createChainLink(Wsdl1Importer.java:522)
at com.sap.tc.esmp.tools.wsdl1import.Wsdl1Importer$ImportChain.init
(Wsdl1Importer.java:461)
at com.sap.tc.esmp.tools.wsdl1import.Wsdl1Importer$ImportChain.<init>
(Wsdl1Importer.java:337)
at com.sap.tc.esmp.tools.wsdl1import.Wsdl1Importer.prepareWsdlImport
(Wsdl1Importer.java:1381)
at com.sap.tc.esmp.tools.wsdl1import.Wsdl1Importer.prepareWsdlImport
(Wsdl1Importer.java:1368)
at com.sap.tc.esmp.tools.facade.Import.prepareWsdlImport
(Import.java:106)
at
com.sap.tc.esmp.tools.editor.jobs.RepositoryMetadataProcessor.doImportFiles(RepositoryMetadataProcessor.java:298)
at
com.sap.tc.esmp.tools.editor.jobs.RepositoryMetadataProcessor.access$300(RepositoryMetadataProcessor.java:52)
at com.sap.tc.esmp.tools.editor.jobs.RepositoryMetadataProcessor$4.run
(RepositoryMetadataProcessor.java:248)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Regards
Venkat

Hi Venkat,
Find the below link.
http://scn.sap.com/community/process-orchestration/blog/2014/11/29/using-idocs-in-nwbpm

Error in importing idoc cremas03

Similar Messages

Maybe you are looking for