Unable to Import IDOCs

Hi all,
i'm trying to Import IDOCs from R/3 4.6C using Integration Bilder(XI, SP level 11) but get the message saying :
"Attempt to log on failed (authorization insufficient)."
The user has SAP_ALL profile assigned in the source system. I've also already checked SAP Notes 677732 (authorizations), 672745 (missing function modules), 212011 (access to IDoc metadata), and 718320.
Has anyone clue, what else should I check ?

Hi Boris,
1. you can check the OSS note: 0000751839
2. check your RFC connection
Regards,
Michal Krawczyk
https://www.sdn.sap.com/sdn/weblogs.sdn?blog=/pub/u/34500 [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken]

Similar Messages

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

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

Unable to import IDOC metadata from 4.6C based R/3 system

As part of a project we are trying to import IDOC interface definition into XI3.0 from our 4.6C based R/3 System. I have gone through the pre-requisites mentioned at
http://help.sap.com/saphelp_nw04/helpdata/en/2b/a48f3c685bc358e10000000a11405a/frameset.htm
One of the OSS notes 672745 in the above pre-requisites talks about applying basis component patch SAPKB46C46. Our current R/3 System is on the basis patch SAPKB46C39. Is there a way to import just the required function modules without applying the whole patch so that we can
continue with the projet ?
cheers.
Ramesh Babu

<i>There is no SM59 RFC destination involved.</i>
Go to SM59 of the XI box and check, the R/3 system for which XI is having RFC destinations.
And before importing, hope you have given R/3 system IP address, client , user id and Password correctly in the Software componenet version.
<i>Is there a workaround for this?. I remember reading in this forum, that there are other ways of importing IDOC message and interface objects as XSD files directly instead of using import wizard.</i>
>> For this you need to download the Idoc Schema from the R/3 system and then import this schema in the External Definition as a xsd type.
But you need to connect to R/3 system and import the Idoc, Because in the directory, you are going to use Idoc itself as an Message Interface. So the xsd used for changing the occurence of the Idoc type, so that you can post mulitiple idocs.
Hope this helps,
Regards,
Moorthy

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

Unable to import IDoc from ECC to PI 7.1(ESR)

Hi,
I am creating an IDoc to File scenario in PI7.1 . I am trying to import the MATMAS IDoc from ECC to PI 7.1.So under the SWCV -> Imported Objects - > Wizard to import IDod/RFC opens -> I enter the ECC system login details -> But when I expand the IDoc node here,I find no IDoc from ECC ,moreover it throws me an error " component should be attached to some frame or dialog"
Can you please suggest me as what is going wrong.
Thanks,
Venu

Hi all,
I am using PI 7.3
When I Import object and passing parameter like application server, system number, uid and password.
I got this error
Unable to establish connection to R/3 system servertm_TM9_06 (system=00, client=001)
Troubleshooting information:
Is the target system online?
Check the connection data; server name and group fields are case-sensitive
Tips for administrators (see configuration guide for details):
Does the user have sufficient authorization in the target system?
Is the target system configured correctly in etc/services?
See error logs for details
Please help me.

Unable to import IDoc into IR

Hi - For no reason i can't import the IDoc into XI.
The problem seems to be that in backend system is a problem. The basis-type and the segments are all released - to me because i released and de-released them. The Idoc was developed in client 010 and i want to import ist from 011 - of course there was some kind of transport!
In WE20 of backend system i am not able to pick this IDoc for Incoming parameter, no idea why.
In XI i am able to import MetaData via IDX2 but i am still not able to import the IDoc!!
can somebody help?! br Jens

Hi,
1 Scenario
This guide deals with all the configurations required to create an IDoc adapter in Exchange Infrastructure
3.0 to send an IDoc from XI to the SAP backend system.
Unlike other types of adapters, the IDoc adapter has dependencies on the XI 3.0 ABAP configurations and
the backend SAP system configurations. Those configurations information will have to be either created
first or retrieved in order to complete the IDoc adapter configuration.
2 Introduction
Configuring IDoc adapter in Exchange Infrastructure 3.0 requires some configuration on the SAP
systems, for both XI and the backend system where the IDoc message is to be sent. These steps, although
simple, are many times missed or mis-configured, causing the delivery of messages to fail.
Since IDoc adapter uses the ABAP stack, instead of J2EE, the configuration requirements are mainly in
ABAP.
Setting up IDoc adapters requires the XI integration server to be able to communicate with the backend
SAP system, and also to make sure that the Logical System Name used when posting IDoc exists on the
backend SAP system.
3 The Step By Step Solution
The basic steps for the IDoc configuration are outline below:
1. Configure SM59 on XI to communicate to SAP backend system.
2. Configure port on XI for IDoc communication.
3. Create or verify the Logical System Name on the SAP backend system.
4. Create or verify business system in XIs System Landscape Directory.
5. Verify the Logical System Name of the business system.
6. Verify or add the Logical System Name for the sender business system.
7. Create/configure the Communication Channel for the IDoc receiver adapter
3.1 Configure SM59 on XI to communicate to SAP backend system.
1. Using transaction SM59, create an RFC destination with Connection Type = 3.
In this example, the RFC destination name is NDVCLNT510.
2. Enter the logon information:
3. Test the connection by clicking on Testing connection and Remote logon.
Both must be successful.
3.2 Configure port on XI for IDoc communication.
4. Go to transaction IDX1 on XI, and create a port. In this example, the Port name is SAPNDV.
     The Port name must be in the form of SAPxxx, where xxx is the system ID of the backend SAP
system.
     The Client must be the client number of the backend SAP system.
     Select the RFC Destination which was created in the previous step.
3.3 Create or verify the Logical System Name on the SAP backend system.
5. Enter transaction SALE on the SAP backend system.
6. Create or verify the Logical System Name. In our example, NDVCLNT510 is verified.
3.4 Create or verify business system in XIs System Landscape Directory.
The business system name for the SAP backend system must contain a valid Logical System Name. This Logical System Name is the one verified or created in the previous step.
7. In the System Landscape Directory, select the SAP backend business system. If one does not exist, then create the business system. Verify the Logical System Name.
3.5 Verify the Logical System Name of the business system.
8. In the Integration Directory, doubleclick on the business system (in our example, it is NDVCLNT510).
Navigate the menu:
Service Adapter Specific Identifiers.
If information is empty or incorrect, then it will have to be synchronized with the content of the System Landscape Directory. Follow the steps below for synchronization.
9. (Optional) Synchronization of the business system in Integration Directory to the business system in System
Landscape Directory.
     Double-click on the business system in the Integration Directory.
     Switch to Edit mode.
     Select menu: Service Adapter-Specific Identifiers
10. (Optional) Within the dialog box, click on the button as indicated below to resynchronize.
11. (Optional) If the expected data from the System Landscape Directory is not updated, then the SLD cache may need to be cleared first.
3.7 Create/configure the Communication Channel for the IDoc receiver adapter.
15. In the Integration Directory, create an IDoc receiver communication channel.
     The RFC Destination is from step 3.1.
     The Port is from step 3.2.
NOTE:
There is no need to create an IDoc sender Communication Channel for XI. Instead, the backend SAP system must be configure to send the IDoc to XI.
4 Appendix
Transaction: IDX2
There are a couple of situation where IDX2 can be useful on the XI system.
1. When we want to test connection between the XI and SAP backend system.
2. When an IDoc has changed, and the meta data stored in XI needs to be update. When an IDoc is sent from the SAP backend system to XI, XI will first check to see if the meta data for the IDoc is already in its persistent cache. If not, then XI will use the configuration in IDX1 to retrieve the IDoc meta data from the backend system. If the
meta is already in cache, then it will NOT do so. Therefore, when an IDoc has changed, it is necessary to manually update the new meta data on XI, or delete it from the cache, so that the latest version can be retrieved. IDX2 is used for this purpose.
Go to transaction IDX2 and click on Create.
Enter the IDoc Type and the Source Port as defined in step #2. Click Continue.If successful, the following will show up. If error occurs, then the IDX1 configurations will need to be re-checked.
Regards
Hemant
Award point if find helpful

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

UNABLE TO IMPORT THE IDOC IN XI

hi
We have extended IDOC INVOIC.INVOIC02.ZINVOICO2EX with a custom segment. But when we try importing the same in XI it gives the following error:
+ Error: IDoc type INVOIC02 contains errors (unable to read segments)
We are unable to understand the root cause of the problem and how to fix the same.
Any help is welcome.

Hello,
You could also check the following:
1. Check the IDoc type in transaction WE60 (try to create a parser). I
   prompted, check the segment definition of any erroneous segments in
   transaction WE31.
2. Check whether the user has the necessary authorizations; for more
   information, see the #Importing IDocs and RFCs# in the SAP Help
   section and SAP Note
   #677732 - Authorization for MDI within framework of adaptive RFC.
3. Check whether the necessary function modules are available. See SAP
   Notes:
   #672745 - Missing function modules for mdi and
   #212011 - EDI/IDoc: Access to IDoc metadata.
4. Check whether the RFC function module DD_DOMA_GET is remote-enabled
   See SAP Note:
   #718320 - Problems using mdi to access DDIC types.
5. Check whether any short dumps or errors are written in the source
   system.
Regards,
Sarah

File to Idoc -- Unable to interpret IDoc interface mi_Orders05_In_Asyn..??

Hi All,
Im trying the File to Idoc scenario.. and im getting the following error in SXMB_MONI,
Anyidea what might have gone wrong??
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
<SAP:P1>mi_Orders05_In_Asyn</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
+<SAP:Stack>Unable to interpret IDoc interface mi_Orders05_In_Asyn</SAP:Stack>+
<SAP:Retry>M</SAP:Retry>
Waiting for your answers.
Thank You.
Seema.

Hi Seema,
I think you are using mi_Orders05_In_Asyn as the IDOC interface.
Use the imported idoc as the interface. i.e you dont need to create Inbound Message interface for IDOC. You can use the imported idoc structure as interface.
Let us know if that doesnt solve your problem.
Regards,
Sumit

Unable to find Idoc in XI

Hi,
Idoc -> XI -> File
I am trying to send an Idoc (ZANSO_MT) from R/3 side to XI.
Status of the message is green in we05 in R/3 but I am unable to find it in XI. I have checked in idx5, we05.
All the RFC connections are working fine with authorization test.
Althought, I was successfully able to import Idoc metadata in IR but I have an error in idx2 "Basic Type ZANSO_MT is unknown". This IDoc is released in R/3 side and I am successfully able to generate and send it.
Pls let me know where to check.
Regards,
Anirudh.

Thank you all for your responses.
@Jayasimha
RFC destinations are working fine as mentioned in my first post.
I have done connection test and also authorization test.
I can see the IDoc successfully sent in we05 in R/3.
I have also changed the port name in idx1 in XI same as in R/3 but still no success.
@Vijayanth
Check smq1,2. Both are empty. I can import Idoc metadata for ORDERS03 or WP_PLU03 from R/3 but not ZANSO_MT.
I created this custom Idoc in R/3 and I am able to import it in IR.
@Nallam
I have released Idoc in R/3 with transaction we30, we31 and we82. I am successfully able to import this Idoc in IR.
@Seshagiri
I have created this basic type in R/3 and able to import it in IR.
The problem is that in idx2 when I try to import it, it doesn't work but other Idocs like orders etc are getting imported successfully.
@NagaDurga
Tried it but no success.
@Jakub
I can see some errors for this Idoc in sm58 in R/3 but many ZANSO_MT Idocs are successfully processed and their status is green in we05.
Regards,
Anirudh.

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]

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: Unable to import the ZINV_EX(unable to read the segment).

Hi ALL,
i have a requirement. were i have to add a custom segment(Z1_E1EDP01) to standard Invoic02 Idoc and created extension of invoic02(basic type) as ZINV_EX.
i added the segment and populated the values accordingly to the newly created segment.
the problem I'm facing is when i try to import this ZINV_EX custom idoc we getting an error :
Unable to import the ZINV_EX(unable to read the segment).
I'm done with the port creation and all the required configuration in idx1 and idx2.
Please can anyone to tell how to resolve this issue.
Thank you,
Lalit.

> the problem I'm facing is when i try to import this ZINV_EX custom idoc we getting an error :
> Unable to import the ZINV_EX(unable to read the segment).
You are getting this error because the segment Z1_E1EDP01 is not following certain naming conventions which we require for IDOC. So change the segment name as Z1E1EDP01 and then try. And don't forget to release the segment.

I am unable to import pictures from my iphone to my computer. Can anyone help?

I am unable to import pics.

It sounds like you are using an application to import. You can do it manually.
Start > Computer (on the right) > scroll to the bottom and you will see your iPhone under Portable Devices > Open it and you will see a Drive, open that and there will be a DCIM folder. That is where your photos will be (There may be other folders each holding photos).

Unable to Import IDOCs

Similar Messages

Maybe you are looking for