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

Similar Messages

  • Error reading IDoc Metadata from CRM 5.0 (Basis 7.0) through XI 3.0

    We are not able to generate the IDoc metadata from XI 3.0 through IDX2 for port/RFC destination pointing to SAP CRM 5.0 which runs on the Basis 7.0 Web application server.
    Has anyone run into this issue?  We get the dialog box with information "I::000" Message no. 000.  The metadata is not generated at all.
    We have no problem generating IDoc metadata for other SAP systems including 6.40 and 4.6C basis layers.  Is there something different with 7.0 Basis?
    Thanks,
    Jay Malla
    SAP XI Consultant
    Licensed To Code

    Hi Renjith,
    Thanks for the suggestion.  We've already tried that out - the RFC call IDX_STRUCTURE_GET works from SE37 using the RFC destination that we have defined for the CRM system which is referenced in the port.  We can debug from the XI system into the CRM system and the data is returned correctly.  We can also generate the IDoc schema from the Integration Builder Repository.
    However, we cannot generate the metadata from IDX2.  If we point the port in IDX1 to another RFC destination for a non Basis 7.0 system, the metadata generation works.  So it seems that something is strange regarding generating the IDoc metadata for Basis 7.0 systems.
    Regards,
    Jay

  • I am unable to import my favorites from internet explorer dueto the import data from option being grayed out under history, library, import tab, any help please

    i am unable to import my favorites from internet explor due to the import data from... option being grayed out under his, library, import. any help please

    Make sure that you do not run Firefox in permanent Private Browsing mode.
    *https://support.mozilla.com/kb/Private+Browsing
    To see all History and Cookie settings, choose:
    *Tools > Options > Privacy, choose the setting <b>Firefox will: Use custom settings for history</b>
    *Deselect: [ ] "Always use private browsing mode"

  • Import XMP Metadata From File

    In Beta4, the Import XMP Metadata From File command would import data found in an xmp file.
    In V1, it's not working...or am I missing something.
    (I do understand that Export XMP to File will write the data into the image file itself.)
    Ideas?
    Pete

    Here's a sample xmp I created...in case it's wrong..but it was working in B4.<br /><br /><x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="Adobe XMP Toolkit 3.3-016, build -num-, -date-"><br /> <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"><br />   <rdf:Description rdf:about=""<br /> xmlns:dc="http://purl.org/dc/elements/1.1/"><br />    <dc:description><br />     <rdf:Alt><br />      <rdf:li xml:lang="x-default">: Geese at sunset. Finley National Wildlife Refuge, Oregon</rdf:li><br />     </rdf:Alt><br />    </dc:description><br />    <dc:creator><br />     <rdf:Seq><br />      <rdf:li xml:lang="x-default">Peter K. Ziminski</rdf:li><br />     </rdf:Seq><br />    </dc:creator><br />    <dc:rights><br />     <rdf:Alt><br />      <rdf:li xml:lang="x-default">Peter K. Ziminski</rdf:li><br />     </rdf:Alt><br />    </dc:rights><br />    <dc:subject><br />     <rdf:Bag><br />      <rdf:li>Sunrises and Sunsets</rdf:li><br />      <rdf:li>Birds</rdf:li><br />      <rdf:li>Landscapes</rdf:li><br />      <rdf:li>Animals</rdf:li><br />      <rdf:li>Oregon</rdf:li><br />      <rdf:li>Finley National Wildlife Refuge</rdf:li><br />     </rdf:Bag><br />    </dc:subject><br />   </rdf:Description><br />   <rdf:Description rdf:about=""<br />    xmlns:Iptc4xmpCore="http://iptc.org/std/Iptc4xmpCore/1.0/xmlns/"><br />     <Iptc4xmpCore:Location>Finley National Wildlife Refuge, Oregon</Iptc4xmpCore:Location><br />    </rdf:Description><br /> </rdf:RDF><br /></x:xmpmeta>

  • Unable to import .avi files from digicam

    I'm unable to import .avi files from my finepix digicam. I get a message that says the files are unreadable. With the previous iPhoto version (v 06) I didn't have any problems. Any thoughts?

    I agree with TD regarding Image Capture. I have the same problem with larger video clips and iPhoto 6. You can use Image Capture, choose "Download Some", select just the movie, and upload it to your Desktop. Ignore the blue Progress bar, as it seems to jump from zero to 100% with no real indication of the download progress. Be patient, leave it alone, and eventually the movie should appear on your Desktop. Once there, iPhoto should have no trouble importing it.
    Regards.

  • 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 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 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 XI’s 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”.
    •     &#61472;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 XI’s 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.
    •     &#61472;Double-click on the business system in the Integration Directory.
    •     &#61472;Switch to Edit mode.
    •     &#61472;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.
    •     &#61472;The RFC Destination is from step 3.1.
    •     &#61472;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

  • 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]

  • Unable to import movie files from iphoto '08 into imovie HD

    I have recently bought a 2008 macbook (2.2 GHz) and have recently downloaded imovie HD in addition to owning iLife '08 due to its extra capabilities. I have found that I am unable to import any of my movie files from my iphoto library folder as it seems to need to open the actual iphoto application before the files can be accessed. In addition, when not using any specific program it would be nice to be able to access my photo/video files within the iphoto folder without iphoto automatically opening as the default viewer.
    Any ideas??!! Thanks.

    ahostmadsen wrote:
    .. and I import AVI video clips directly without converting to .dv, without problems.
    lucky you.. .avi is just a container, no 'format'/codec .. I can show you dozends of .avis, which will NOT import into iMHD6, due to being playback-codecs, not convertable by the underlying Quicktime engine into separte, editable audio+video streams ..
    .. If you convert to .dv, the size just blows up.
    dv is 13GB/h and a codec meant for editing; e.g. it stores every frame (video=30 frams/sec) of a recording, as mpegs usually doesn't do so.. = your Mac has to estimate content, when converting and 'recovering' the content = lossy process.
    iMHD6 is a dv-editor; the mpeg4 feature is only a toy, to spice up iSight recordings.. for sure, the QTengine can convert a lot, but too much conversion (from one lossy codec, e.g. divx, into another, e.g. mp4) means a (dramatic) loss of pic quality..
    my 5€ cents ..

  • Problem in importing idoc metadata

    Hi all,
    i have problem in loading metadata in idx2. idoc details are AFS/ORDERS05/ZADIORDCONF port: SAPAGS client 003 . i could see an idoc metadata with name ORDERS05 under the corresponding sap system (SAPAGS with client 003) but with out any extension.
    now i tried to create another with idoc type : ORDERS05
                                                    Extension: ZADIORDCONF
                                           and    Source port:SAPAGS
    it is giving error msg Extension ZADIORDCONF is not assigned to basic type OREDERS05.
    wat could be the reason , please help to solve it
    Thanks and Regards
    Jhansi

    Hi,
    There is no need to add anything to idx2. You could delete the existing metadata from idx2 and reimport it.
    In some cases even this would not work. In that case, you could refresh the entire metadata by running report IDX_RESET_METADATA. However, use this report only if the above option does not work, since this report will reset your entire metadata.
    Thanks,
    Bhavish
    Reward points if comments helpful

  • 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: <b>Schema for type EDI_DC40.ASN_OUT.DELVRY01.Z1DELVRY (category Data Type) not found</b>. 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

  • Unable to import Software component from SLD :PI71 SP05

    HI Friends,
         We have created  SWC in SLD.
    From ESR when we click on "Import from SLD".I am getting error "Could not read list of Software component versions from SLD".In details the error is as follows.
    "-- error description--
    Could not read list of software component versions
    from SLD (COULD_NOT_READ_SWCV)
    User credentials are invalid or user is denied access
    All the eight roles for SLD have been provided in SU01.
    SAP_SLD_ADMINISTRATOR
    SAP_SLD_CONFIGURATOR     
    SAP_SLD_DATA_SUPPLIER     
    SAP_SLD_DEVELOPER
    SAP_SLD_GUEST     
    SAP_SLD_ORGANIZER
    SAP_SLD_SUPPORT
    SAP_SLD_CONTENT_SYNC
    In Addition to this any new role need to be assigned?
    Regards
    chandra dasari

    Hi,
    Refer this thread..
    unable to import from SLD
    Hope it helps...
    Thanks,
    Kumar.

  • Unable to import new images from finder into lightroom 5 since update

    Since I updated my Lightroom 5 and Photshop CS6, I have been unable to import images from my finder (MacPro) or save edited images from Photoshop editor back into my Lightroom 5 library. Please help!

    I Managed to edit images in Lightroom and then clicked on photo editor photoshop to make further editiding.After i click on save, it doesn't come back into my Lightroom 5 library.
    i Then saved the image into my computer and tried to import from there, but images quickly appear and then disappear :-(
    thanks for the quick reply!

Maybe you are looking for

  • [Locked] Centering an oversized web page in dreamweaver

    for a web programming class an extra credit challenge is to fix all found issues with some example web pages in dreamweaver in the first example page the most obvious problem is that the page has oversized dimensions which are 1680 x 1050 so the main

  • Where should I get my domain name from

    where should I get my domain name from

  • Error msg raised in a trigger into an APEX validation box?

    Hi, I am working on a FORMS to APEX conversion. In the application we are converting, there are a lot of triggers containing validations using a RAISE_APPLICATION_ERROR. For example, there could be a validation on a status change in a "before update

  • DDE Server Windows Acrobat.exe - Erreur d'application

    DDE Server Window: Acrobat.exe - Erreur d'application L'instruction à "0x0319b3b2" emploie l'adresse mémoire "0x02b9fb08". La mémoire ne peut pas être "read". Cliquez sur OK pour terminer le programme. Cliquez sur Annuler pour déboguer le programme.

  • Minimum windows size of Xcode 4.1 ?

    Prior to Xcode 4, I could resize the windows to any size I wanted. This was very useful as I could place two windows side by side when I wanted to compare two documents. Xcode 4 onwards, each windows has a minimum size. Because of this limit, I canno