Unable to delete IDoc meta data

Hi,
    When I'm trying to load the IDoc meta data from IDX2 it is telling first delete the old one and then reload. But, the problem is we are unable to see the already existing IDoc meta data.
Can some one suggest how to see meta data all the loaded IDocs.
Regards,
Jeevan.

Hi Jeevan,
You may be checking for the IDoc meta data in the wrong port.
Make sure that you are looking in the correct port.
>>Can some one suggest how to see meta data all the loaded IDocs.
1. In IDX2 expand the Port that you are trying to import the IDoc.
2. Locate the IDoc type in that port and hit Delete.
Thanks
SaNv...
Edited by: Sãnthosh Kûmãr  V on Oct 23, 2008 11:20 AM

Similar Messages

  • IDoc meta data not getting imported

    Hello
    I am trying to get IDoc meta-data using transaction IDX2. I have configued RFC destinations of type R3 in both the systems (ECC and XI). Also I have created port using transaction IDX1.
    When tried to import MATMAS04 using the defined port it gives Information box displaying "I::000" and nothing happens. The information box does'nt contain any message.
    Anybody faced this problem with IDoc?
    Thanks in advance.
    Regards
    Rajeev

    Hi,
    actually it was authorization problem which I noticed when I checked the short dump in ECC.
    anyways thanks for the reply.
    Regards
    Rajeev

  • Loading IDOC meta data into Xi not working

    Hello,
    I'm trying to load IDOC meta data using trx IDX2 but the program is not able to recognize the port "SAPRD1_222" I previously defined in trx IDX1.
    Any ideas, what Im missing here?
    Ruud

    Ruud,
    Pls take a look of this thread:
    Re: Importing Metadate from IDES 4.7 into Integration Server Rep

  • IDOC meta data

    Hi All,
    I am trying a file-idoc scenario. I have imported the IDOC in IR and done with the mappings. I have created a RFC destination to R/3 server of type 3. Also I have created a port in IDX1 with the created RFC destination.
    In IDX2 I cant find the meta data for my imported IDOC. Should I do it manually? If so how?
    Thanks & Regards,
    Jai Shankar.

    Re: Importing Metadate from IDES 4.7 into Integration Server Rep
    Re: IDoc Meta Data Problem
    Have a look into these !!!

  • Idoc meta data does not come up in trx idx2

    Hi there,
    Im importing IDOC meta data into XI (using trx idx2) from a CRM 4.0 idoc basic type CRMXIF_PARTNER_SAVE_M02.
    No idoc meta data is imported, instead the transaction is giving me back an information message: I::0000
    When I click on the pop-up window, the description provided is only: "Message no.000"
    Does anyone knows what this message really means?
    SLD setup is ok, RFC connections are also ok, IDOC port seems also to be OK.
    Any feedback is appreciated,
    Rob.

    Noriko,
    this error is authorization related. There are a couple of function groups which are called in the target system and the user in the RFC Destination to the target system might not have sufficient authorization. Just look into transaction SU53 in the target and select the user used in the RFC destination. This should show you the failed authorization checks.
    Also SAP Note 940313 some hints on what you can check for this error. 
    Regards
    Christine

  • IDoc Meta data Error at XI server

    hai all,
    I triggered IDoc from R/3 System and after observing XI server, it shows the following Adapter Meta data Error .RFC destination and ports are correct. Please can any one comment on this.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
      <SAP:P1>I::000</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error: I::000</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Thank u.

    Hi Nani,
    go to transaction IDX2 and try to download
    the metadata manually to see if there are
    any errors over there
    you can also find the same approach
    (loading, reloading and comparing metadata) in my book:
    <a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • Delete location meta data

    In the interest of discretion and safety I do not wish to publish the location meta data (places) with any of my photos that I post online. While I've read that you can open a photo (jpeg) in Preview, change it to an .png, then back to a .jpeg and the meta data will be lost I cannot do that with several hundreds of photos. Is there a way to batch this process? A way to do it in iPhoto? TIA

    You can make an Automator Actior or Workflow to automate the process. You can do batch conversions with Graphic Coverter, or, finally, you can simply export the files from iPhoto without checking the 'location information' check box in the export dialogue, and the Places data will not be written to the file.
    Regards
    TD

  • IDoc meta data load problem in IDX2

    I have been trying to load meta deta for some idocs and am getting message 'Basic type <idoc_type> is unknown'. Interesting to note is that I could load ECMMAS01 idoc type but other idoc types like MATMAS01 ..04, ORDERS01 ...04, DOCUMENT_LOAD01 ... and many others that I tried, I got the same message. The config has been done in IDX1 and IDX2 (that's how I got the ECMMAS01 in).
    There is an OSS note '0000751839 IDoc Adapter: Basic type 'XYZ' is unknown.  ' It seems we are already on that patch level. Can't verify if the note has been really applied or not for authorization issues for now. The note also mentions about a workaround to set the category level to '0' (i.e. blank) in the Integration server configuration. But that doesn't seem to help either.
    Anyone else had this problem and resolved it?
    Harshad

    Problem stands resolved. I realized that the RFC destination in XI for the R/3 system had a problem. What still is not answered is how come I was able to import ECMMAS01?!?! One explanation could be that the RFC connection was ok then. Don't know, but I am happy that it works now.

  • SPROXY unable to get Interface meta-data from XI Server

    Hi,
    In our SAP R/3 Enterprise system, the transaction SPROXY complains that "No connection to Integration Builder (only local data visible)".  It is unable to get the message interfaces defined in the SAP XI Server.
    Connection to SLD is configured correctly, and transaction SLDCHECK works correctly.
    Where can I configure the SAP R/3 system so that it can retrieve the message interfaces from SAP XI system ?
    thanks,
    Manish

    Hi Manish -
    Did you maintain the RFC destinations LCRSAPRFC and SAPSLDAPI?  And the corresponding J2EE connections?  These must be completed in addition to other possible configurations.
    Please check XI 3.0 Configuration Guide, section 8 (Connecting Business Systems with an Integration Engine to the Central Integration Server).  These have all the necessary steps.
    Regards,
    Jin

  • Unable to delete the Master Data

    Hello Gurus--
    How to delete the unused MD for an Infoobject,.
    Unused MData were in A version in M,P and text tables.
    Thru the program "RSDMD_DEL_PARALLELIZER" and "RSDMD_DEL_BACKGROUND"  The MD hadn't got deleted.
    Scheduled the above programs and checked the logs in SLG1 for both used and unused MD,.
    The logs says that
    a) Checked,.and I confirm that the unused MD is not present in any targets.
    b) MD deletion hadn't happened for my unused MD.
    --> The MD is in A version in the M,P, Text tables, if it is in M version  these data can be deleted,,
    Checked for the same in all the forums .
    Couldn't able to find the same.
    Very very Ungent sirs' !!!
    Regards
    Vishwa.

    Infoobject --> right clikc --> maintain master data
    Select rows u wanted to delete and click 'Delete' icon. And SAVE.
    If system prompt u 'some master data cannot be deleted' .. continue with this message.
    then goto tcode SLG1-- enter Object: RSDMD and Subobject: MD_DEL and User: ur userID and F8
    In the next screen Expand node and dbl click 'Problem class additional information'
    This will give u which ever objects using SIDs of this master data.
    U should delete this SID according to that list.
    Then U should delete particular data from DSO/Cubes.
    Once data deleted from cube, then
    Use Tcode RSRV -> Tests in Transaction RSRV -> All Elementary Tests -> Transaction Data -> Entries Not Used in the dimension of an InfoCube (Dbl Click)
    From the right side window, expand u201CEntries Not Used in the Dimension of an InfoCubeu201D Node &
    Enter InfoCube (like 0SD_C01), click u201CTransferu201D
    Now, click u201CExecuteu201D (Toolbar)u2026 and the results displayed in the right side window..
    Now, click u201CCorrect erroru201D (Toolbar)
    Delecion of the master data

  • Doubt about idoc meta data

    hi this is seshagiri. i have one doubt while in sending idoc to xi server in the idoc to file scenario, can we do with out configuring metadata in idx2.
    if can we do means wat is the procedure.
    please clarify me
    thans & regards
    giri

    Hi Sesha giri,
        If you are dealing with Idoc to File Scenario...you need to create
    1) RFC Destination in R/3 pointing to XI.
    2) Ports in R/3.
    3) PartnerProfiles
       we need to send idoc from R/3...so we have to do ALE configuration.
       Please see the below link for more details.
      /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    Hope I am clear.
    Please let me know if you have any queries...!
    Thanks and Regards,
    Chandu

  • IDoc Meta Data Problem

    Hello i am getting the following error not clear of what might be the cause.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
      <SAP:P1>FM NLS_GET_LANGU_CP_TAB: Could not determine code page with <Client> Requested parameter does not exist FM NLS_GET_LANGU_CP_TAB</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:Add
    itionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error: FM NLS_GET_LANGU_CP_TAB: Could not determine code page with <clinet> Requested parameter does not exist FM NLS_GET_LANGU_CP_TAB</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Please suggest

    Hi,
    I am just replying that..
    Just go to Tcode SM59 in XI system and then go to RFC connections and then check for the RFC destinations created for the R/3 system. And then click on that will lead into different screen. Then click on Test Connection tab. If it is successfully connecting to R/3 system, then RFC destination is correct.
    http://help.sap.com/saphelp_nw2004s/helpdata/en/22/042638488911d189490000e829fbbd/frameset.htm
    /people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
    Hope this helps..
    Regards,
    Moorthy

  • Issue loading Meta Data for IDoc Type WPUKSR01 in XI Integration Repository

    Hi,
    I want to load the Meta Data for IDoc Type WPUKSR01 in XI Integration Repository out of BI. Unfortunately, this IDoc is not available in the IDoc List. I checked in BI and the IDoc Type is available in WE60 and WE30. Also, I can load the Meta Data for the Idoc in XI ABAP (IDX2).
    Can someone tell me why the IDoc doesn't show up in XI Integration Repository Import Object List?
    Thanks in advance.
    Best Regards.
    Alex

    Hi Aamir,
    The Idoc is released since Release 30A. I also tried to load the IDoc Meta Data from ERP with the same result: it does not show up in the list.
    Thanks anyway.
    Alex

  • Meta Data issue

    Hi,
    When I'm trying to load the IDoc meta data from IDX2 it is telling first delete the old one and then reload. But, the problem is we are unable to see the already existing IDoc meta data.
    Can some one suggest how to see meta data all the loaded IDocs.
    Regards,
    Anitha.

    Hi,
    Try answers from this link
    Re: How to refresh metadata in XI for IDOC
    Thanks!

  • 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

Maybe you are looking for