File to idoc scenario error - not working yet :(

Hello! I'm trying to make changes in business partner record in CRM using idoc CRMXIF_PARTNER_SAVE_M01
I have an error 56 EDI: Partner profile not available.
In Control record in we02 transaction, I have right Partner number for Recipient information - logical system name like CRM has in SLD.  But there is no Port.
In Sender information I have right Partner number, like my filesystem business system has in SLD and have a port SAPP1D - but  I have nowhere entered it!
And one more little question. In we20 transaction am entering inbound parameters for partner:
CRMXIF_PARTNER_SAVE
CRMXIF_PARTNER_SAVE_M
1) Is this right inbound parameters for my idoc?
2) What Process code should I use ?

Hi,
in XI in IDX1 transaction, maintain a port for CRM system specifying the CRM port and the client and the RFC destination from XI to CRM system.......moreover if you are using apply control record values from payload option in reciver IDOC comm channel, then in the IDOC control record in msg mapping map the sender port to CRM port, partner number as logical system of CRM ie C2DCLNT100 and partner type as LS..........then when you will re-run your scenario, your IDOC will have CRM port also in the control record..........
in CRM system your WE20 for LS for XI should have as an inbound parameter your IDOC - which i think you have already done.........
One more thing - put everything in uppercase letters everywhere in msg mapping in control record data, in we20 setting etc.
Regards,
Rajeev Gupta

Similar Messages

  • File to IDoc scenario-CREMAS not getting posted

    Hi Experts,
    i am doing a file to idoc scenario in which i am giving the xml file from MDM ,consisting of Vendor Master data and posting the address and the general data into the ADRMAS and CREMAS idocs into the R/3 system.
    The problem that i am facing is that the ARMAS is getting posted correctly but the CREMAS is getting posted with the red signal,status 51.It says "Not authorized to change the Vendor Centrally."
    Can anyone please tell me what is the reason and the solution for this problem?
    Is this a data error or XI error?
    Thanks in advance,
    Shweta.

    Hi Shweta
    Status 51, 52 means Posting error 
    Please check wheteher all the configuration has been done or not
    SM59-rfc destination
    IDX1-port
    IDX2-load metadata
    we05-IDoc status records
    BD54-Create Partner Number
    We20-Create Partner Profile
    WE19-Testing IDoc Processing
    After That check the solution it is due to Authorization
    File to idoc - IDX5 Error
    Regards
    Abhishek Mahajan
    *Please reward points if helpful**

  • File to IDOC scenario error...

    Hi all,
    we hhave created an File to Idoc scenario .
    we are getting the following error in SXMB_MONI t-code.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <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_INV_SND_SERV</SAP:Code>
      <SAP:P1>BUS_SENDER</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Unable to convert sender service BUS_SENDER to an ALE logical system</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    can any one plz say wat this error might be..
    TIA
    Regards,
    Raj

    Hi,
    The problem occurs when sender and receiver business system or business service does not have a logical system name.
    ID - Integration Directory
    Posting the IDOC'S into SAP R/3 System, sender and receiver business system or business service requires the logical system name. If the business system (Web As ABAP) does not have the logical system name, then add the logical system for business system.
    If business system type = Web AS ABAP, then add the Logical system in Technical System level and Save.
    If business system type = Third-Party, then add the logical system in business system level and Save.
    If the business service does not have the logical system name in ID, it needs to be configured as follows.
    Go to ID and click the Business service -> Services -> Adapter Specific Identifiers. Enter the logical system name and Save.
    Apply and activate.
    hope this will help you.
    regards
    Aashish Sinha
    PS : reward points if helpful

  • File to IDOC scenario : Error with mapping due to Context handling

    Hi Experts.
    I have a file to IDOC scenario which need your advice.
    Source File structure as follows:
    Control_Header     <1:1>
    Invoice_Header     <1:unbounded)
    Invoice_Line          <1:unbounded)
    Trailer                    <1:1>
    Payload as follows capture from SXMB_MONI
    - <Control_Header>
            <Key>999</Key>
            <TransactionID>RCTV</TransactionID>
      </Control_Header>
    - <Invoice_Header>
        <Key>000</Key>
        <BusinessUnit>HDB05</BusinessUnit>
        <InvoiceNo>64471</InvoiceNo>  
    </Invoice_Header>
    - <Invoice_Line>
          <Key>001</Key>
          <UnitPrice>7.00000</UnitPrice>
          <Quantity>1.0000</Quantity>
          <GSTAmount>0.49</GSTAmount>
          <GSTRate>0.07</GSTRate>
      </Invoice_Line>
    - <Invoice_Line>
          <Key>001</Key>
          <UnitPrice>8.00000</UnitPrice>
          <Quantity>1.0000</Quantity>
          <GSTAmount>0.56</GSTAmount>
          <GSTRate>0.07</GSTRate>  
    </Invoice_Line>
    - <Invoice_Header>
          <Key>000</Key>
         <BusinessUnit>HDB21</BusinessUnit>
         <InvoiceNo>6Y0575</InvoiceNo>
    </Invoice_Header>
    - <Invoice_Line>
        <Key>001</Key>
        <UnitPrice>49.50000</UnitPrice>
        <Quantity>1.0000</Quantity>
        <GSTAmount>3.47</GSTAmount>
        <GSTRate>0.07</GSTRate>
    </Invoice_Line>
    - <Trailer>
         <Key>TRL</Key>
         <TransactionID>RCTV</TransactionID>
         <TotalFeedLine>96</TotalFeedLine>
         <HashTotalValue>212.00</HashTotalValue>
    </Trailer>
      </ns:MT_EINVOICE>
    Mapping as follow:
                                                   IDOC
    <Control_Header>   ->    <Control_Header>
    <Invoice_Header>   -->  <Header_Invoice>
    <Invoice_Line>      --->        removeContext  -->  <Line_Invoice>       this is the child node of <Header_Invoice>
    <Trailer>               -
    >    <Trailer>
    The result of the using the above Payload get the following result which not wht I seek
    <Control_Header>
    <Header_Invoice>
          <Line_Invoice>
          <Line_Invoice>
         <Line_Invoice>   *** This belong to the Invoice_Line of the second <Header_Invoice> at the payload
    <Header_Invoice>
         <Line_Invoice>   *** THis segment is empty
    <Trailer>
    I required the Line_Invoice to belong to the child of the second <Header_Invoice>, I have tried using
    removecontext with splitVaue and collaspeContext but to no avail.
    May I know what is my mistake on the mapping of the Invoice_Line to Line_Invoice>
    Rgds
    FNG

    Hello,
    There should be something that could correlate the Invoice_Header/Key and Invoice_Line/Key. In your example, both are the same for the first and data set. If the sample looks like the one below, it is possible to sort things by correlating the Invoice_Header key and Invoice_Line key
    <Invoice_Header>
      <Key>000<Key>
    </Invoice_Header>
    <Invoice_Line>
      <Key>000<Key>
    </Invoice_Line>
    <Invoice_Line>
      <Key>000<Key>
    </Invoice_Line>
    <Invoice_Header>
      <Key>001<Key>
    </Invoice_Header>
    <Invoice_Line>
      <Key>001<Key>
    </Invoice_Line>
    An example mapping could look like this
    For Header
    Invoice_Header --> Header_Invoice
    For Line
    /InvoiceLine/Key --> removeContext --> splitByValue:valueChanged --> Invoice_Line
    The subfields of the invoice line would also follow a similar logic, you just need to use formatByExample --> splitByValue:eachValue so that the context levels are the same.
    Hope this helps,
    Mark

  • RBDMANI2 for IDOCs in error not working in Background..

    Dear All,
        We have an ALE-IDOC scenario in which our IDOC gets posted in the destination system with status 51 as per business reqt. We schedule a job in the background using program RBDMANI2 which is used to manually reprocess IDOCS in error.
        This background job was working fine in the 4,7 R/3 Server, but we have upgarded the receiving system to ECC 6.0. Now the problem is dat when we try to reprocess the IDOC using this job, the IDOC are not processing further.. It ideally is supposed to do further processing as per the code writen.
      We tried debugging the code(RBDMANI2) in background. But, its not helping.
    Kindly advise.
    Regards,
    Santosh Reddy.

    On primary research I found that there is a call to this FM 'SAPGUI_PROGRESS_INDICATOR' .
    In that FM see line 12.
    IF SY-BATCH <> SPACE.
              EXIT.    "do nothing in batch
           ENDIF.
    May be this is the cause of your error.
    Rhea.

  • File to Idoc Scenario. Pls advice

    Hi All,
    I have implemented File to Idoc Scenario and it worked fine.
    I have 2 doubts:
    My Scenario: File -- XI -- R/3 system named D01
    1. In Configuration: In Receiver Aggrement why we put  
        XI Business System name in Sender Service?
    2. In Configuration when I open my R/3 Business system  
        (D01CLNT100) and click on Adapter Specfic Identifiers I can
        see my Logical System Name as D01CLNT100.
        When I use SALE tx. in D01 R/3 system I can see 
        D01CLNT100 as logical system
        Question:  If I use SALE transaction and change my
        logical system name to "test" , do I need to change the
        name "test" in SLD and then for R/3 Business system  
        (D01CLNT100) in Adapter Specfic Identifiers I will see new
         Logical System Name as test.
    Regards

    Hi,
    Question: If I use SALE transaction and change my logical system name to "test" , do I need to change the name "test" in SLD and then for R/3 Business system (D01CLNT100) in Adapter Specfic Identifiers I will see new Logical System Name as test
    Yes , you need to Update the name in SLD and just Do SLD Data Cache in ID-- Environment to reflect the same name in Identifiers place.
    >>1. In Configuration: In Receiver Aggrement why we put XI Business System name in Sender Service?
    You might have used XI as Sender and you might have placed the file in XI Server to pickup.
    Thats why you are using Xi's Business System name as Sender Serveice.
    Regards
    Seshagiri

  • File to IDOC scenario not working

    I have configured a file to idoc scenario and kept the XMl file in a shared location on XI server.
    I have also created and checked the communication channels correctly.
    Once Everything is done my xml file does not get picked up at all. Also the SXMB_MONI does not show any messages for my service.
    How do I find out what is the error ??

    Hi Kapil,
    Just check the File path that was in shared location once and the file name is properly mentioned or not..
    And also one thing after activating all IR and ID just goto SXI_CACHE and press <b>F6</b> to update cache refresh
    And also in RWB --> Message Monitoring --> Adapter monitoring --> check the status of the sender
    Regards,
    Sridhar

  • Error in File-PI-Idoc scenario

    Dear All,
    While working on File-PI-Idoc scenario, I am getting the error as
    <?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="1">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">UNAUTHORIZED</SAP:Code>
      <SAP:P1>401</SAP:P1>
      <SAP:P2>Unauthorized</SAP:P2>
      <SAP:P3>(See attachment HTMLError for details)</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    I have checked various other posts on the same error but still I am not able to resolve this.
    Please help me in resolving this error.
    reg,
    nj

    Nishu,
    Please check whether you have assigned the following roles to the particular user you are using for data communication.
    Roles:
    SAP_XI_IS_SERV_USER,
    SAP_XI_APPL_SERV_USER
    Regards,
    Sugata

  • Message has error status at outbound side File To Idoc Scenario

    hi ,
    In my File to Idoc scenario , when i go to sxmb_moni , i found that its showing red flag at Outbound Status Tab and showing message "Message has error status at outbound side".
    When i go to IDX5 and and select my idoc and click on Transaction Id it shows "Password logon no longer possible - too many faile" .
    Please suggest what may be the problem ?
    Regards,
    Rohit

    1. First check the RFC destination name used in receiver Idoc adapter communication channel.
    2. As i said earlier, in sm59 transaction in XI gui, u can check same rfc destination under type 3. There check the logon credentials and the username.
    3. Now goto the R3 system GUI and check in su01 that same user is locked or not. If locked unlock it.
    4. And if u change the password of that user, then do the similar change in XI -> sm59 -> rfc destination logon credential
    Regards,
    Prateek

  • IDocs not created in file to IDoc scenario

    Hi all
    I am trying this file to IDoc scenario.
    File picked up successfully and sent to R/3 Backend…But Idoc is not posted…the status records
    In /n we05 in R/3 Backend shows that EDI: Partner profile inbound not available
    I created/tested all basics like RFC dest, port etc.
    File service that I am using is a business service …hence I am specifying a Logical system name in
    <b>Adapter specific Identifiers</b> of the file service.
    I disabled EDI_DC40 control tag record as IDoc adapter
    takes care of it.
    So at first I tried the configuration of IDoc comm. Channel by checking the Apply control record values from payload
    But SXMB monitor gave an error regarding this control record tag…I guess as we have disabled it so there won’t be any values
    for control record in payload (correct me if I am wrong).
    So I unchecked the checkbox Apply control record values from payload and monitor showed up as successfully processed.
    But in the backend I am getting this error regarding partner profile.
    I also tried to use an existing profile (<b>LS</b> type) by modifying it’s inbound parameters to accept <b>CREMAS</b> Idoc.
    But the error is as persistent as me
    Pls help
    Sudhir

    Hi
    Sender --> LEGACY, maintained in SLD (Logical system).
    Receiver--> ENI maintained in SLD with logical sys name M700.
    Partner Profile LEGACY maintained in R3.
    <b>Following is the IDocOutbound in SXMB monitor in XI</b>.
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Response
      -->
    - <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <SAP:TABNAM>EDI_DC40</SAP:TABNAM>
      <SAP:MANDT>100</SAP:MANDT>
      <SAP:DOCREL>640</SAP:DOCREL>
      <SAP:DOCNUM>0000000000001013</SAP:DOCNUM>
      <SAP:DIRECT>2</SAP:DIRECT>
      <SAP:IDOCTYP>CREMAS03</SAP:IDOCTYP>
      <SAP:CIMTYP />
      <SAP:MESTYP>CREMAS</SAP:MESTYP>
      <SAP:MESCOD />
      <SAP:MESFCT />
      <SAP:SNDPOR>SAPAXI</SAP:SNDPOR>
      <SAP:SNDPRN>LEGACY</SAP:SNDPRN>
      <SAP:SNDPRT>LS</SAP:SNDPRT>
      <SAP:SNDPFC />
      <SAP:RCVPOR>SAPENI</SAP:RCVPOR>
      <SAP:RCVPRN>M700</SAP:RCVPRN>
      <SAP:RCVPRT>LS</SAP:RCVPRT>
      <SAP:RCVPFC />
      <SAP:TEST />
      <SAP:SERIAL />
      <SAP:EXPRSS />
      <SAP:STD />
      <SAP:STDVRS />
      <SAP:STATUS />
      <SAP:OUTMOD />
      <SAP:SNDSAD />
      <SAP:SNDLAD />
      <SAP:RCVSAD />
      <SAP:RCVLAD />
      <SAP:STDMES />
      <SAP:REFINT />
      <SAP:REFGRP />
      <SAP:REFMES />
      <SAP:CREDAT>0000-00-00</SAP:CREDAT>
      <SAP:CRETIM>00:00:00</SAP:CRETIM>
      <SAP:ARCKEY>DF57A2C0532811D9AD84000F206A031B</SAP:ARCKEY>
      </SAP:IDocOutbound>
    <b>Control record of IDoc in R3</b>
    Tab: Typeinfo
         Basic type-->CREMAS03
         Message Type-->CREMAS
    Tab: Partner
         Recipient
          Port  -->SAPENI
          Partner Number--> M700
          Partner Type-->LS
         Sender
          Port  -->SAPAXI
          Partner Number--> LEGACY
          Partner Type-->LS
    Pls help
    Regards
    Sudhir

  • IDOC is posting with Errors in File to IDOC scenario

    Hi,
       I did the File  to IDOC scenario for CREMAS  . IDOC is posting with Errors .. i.e. in the status record it was showing  56- EDI: Partner profile inbound not available  ..
    If I manually process that IDOC in WE19 , then it was processing successfully..    and in the  we19 it was showing Inbound Processing : Port Not Maintained    but even though manually it was posting fine...
    any ideas regarding this will be appriciated..... 
    Regards
    Babu

    Please check whether you had done the following assuming your doing File to Idoc
    Settings in your Business service for the receiving system
    Please specify the RFC detination, SAP System and Client of the Receiving System in the adapter specific detials.
    Settings in R/3
    WE20 - Add the partner profile for the particular message type cremas and process code.
    Your statement
    " and that same logical system name  had given as Message Specific Attributes in the Sender Business Sevice parameters in I.D "
    Please do mention R/3 Details in the receiver business service or system.
    Thnz

  • ** File to IDoc scenario - IDoc not created in target system

    Hi friends,
    We are doing File to IDoc scenario. We made required setting in both application as well as XI system. While test the scenario, the file is picked up and successfully processed in SXMB_MONI, but the inbound IDoc is not created in target system. What could be the problem?
    We are using DEBMAS message type DEBMAS06 IDoc type. We checked the following.
    1) SM59 - Connections are OK both application and XI system
    2) IDX1 - In XI System, we have assigned SAP<R/3> port.
    3) IDX2 - IDoc is imported.
    4) In ID - Sender File - Business Service - Adapter-Specific Identifier - Logical System name is given.
    5) In application system. - Partner Profile maintained correctly.
    6) SM58 - There is no error.
    So, what could be the reason ?
    Kindly reply, friends,
    Thanking you.
    Kind Regards,
    Jeg P.

    Hi,
    Check all the steps ..
    File to IDOC
    Do these configurations in R/3 and in XI...
    SAP XI
    1) RFC Destination (SM59)
    a) Choose create.
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#.
    e) Enter the Gateway host as same details above SID/URL.
    f) Gateway service is 3300+system number#.
    g) In the Logon /Security tab, enter the client user & Password details of Destination system.
    h) Test the connection and remote logon.
    2) Create Port (IDX1)
    a) Select create new button
    b) Enter the port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client.
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    3) Load Meta Data for IDOC (IDX2)
    a) Create new
    b) IDOC Message Type
    c) Enter port created in IDX1.
    SAP R/3
    1) RFC Destination (SM59)
    a) Choose create.
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#.
    e) Enter the Gateway host as same details above SID/URL.
    f) Gateway service is 3300+system number#.
    g) In the Logon /Security tab, enter the client user & Password details of Destination system.
    h) Test the connection and remote logon.
    2) Create Port (We21)
    a) First Select Transactional RFC and then click create button
    b) Enter the destination port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client.
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    3) Create Partner Profile (WE20)
    a) Create New
    b) Create the Partner no. name as same the logical system name of the destination system.
    c) Select Partner type LS
    d) Enter details for Type: US/USER, Agent, and Lang.
    e) Click on the + button to select the message type.
    f) Select Partner no. and LS which ever create above.
    g) Select Message type
    h) Select Process code related to the Message type.
    I) save.
    Thanks,
    Satya

  • Not sure if IDoc was created or received in file to idoc scenario

    Hi,
    I configured a file to idoc scenario in my test client for idoc MATMAS.MATMAS02 , now after going thru all the phases of design and configuration and creating partner profile using we20 , when I m executing the scenario , I am not sure wht happened to the idoc becz i can't see in the R/3 system using we05/02 or BD87 in the XI system .
    Pl help how to rectify the error and find out where the error has actually occured.
    ans will be rewrded
    rgds
    mojib

    Hi Mojib,
    first check in SXMB_MONI whether you have a success chequered flag for the file messge.................if there is error here, then rectify your this error and re-run your scenario................if you cannnot see your file msg in SXMB_MONI, then go to RWB and in comm channel monitoring, see the error in sender file comm channel status and rectify the error in sender file comm channel in ID and save and activate it and then re-run your scenario............
    then execute SM58 to see in there is anything in tRFC.........if there is not anything here, then it means your IDOC has reached R/3.................
    then in R/3, execute WE05 for the relevant period, then you will see your IDOC there with some status..........
    Regards,
    Rajeev Gupta

  • File to IDoc scenario( Bypass)-- Error ( Segment is missing) -- urgent pls.

    Hi All,
    I am doing File to IDoc scenario( Bypass) for Orders05.
    File is picking succesfully and not posting the idoc in the SAP..
    My source file(idoc-xml) consists of all the required data to post the idoc including the segment 'E1EDK01'.
    but the error it is showing is <b>" Obligatory node 'E1EDK01' missing in the structure ORDERS05 "</b>
    Please suggest me ASAP what is going wrong .
    Thanks in Advance.
    Regards
    Seema.

    The source File is not the idoc XML. It is invalid. You might need to ask the source to change the XML or use a Mapping to do this.
    This is how it should look, ( check the parts in bold),
    <?xml version="1.0"?>
    <ORDERS05>
    <IDOC <b>BEGIN ="1"</b>>
    <EDI_DC40 SEGMENT="EDI_DC40">
    <DOCNUM>1</DOCNUM>
    <DIRECT>2</DIRECT>
    <IDOCTYP>ORDERS05</IDOCTYP>
    <CIMTYP></CIMTYP>
    <MESTYP>ORDERS</MESTYP>
    <SNDPOR>XXXXXXXXX</SNDPOR>
    <SNDPRT>LS</SNDPRT>
    <SNDPFC></SNDPFC>
    <SNDPRN>XXXXXXXX</SNDPRN>
    <RCVPOR>XXXXXX</RCVPOR>
    <RCVPRT>LS</RCVPRT>
    <RCVPFC></RCVPFC>
    <RCVPRN>XXXXXXXX</RCVPRN>
    <CREDAT>20070511</CREDAT>
    <CRETIM>152803</CRETIM>
    </EDI_DC40>
    <E1EDK01 <b>SEGMENT = "1"</b>><BELNR>AAAAAAAAA123</BELNR>
    </E1EDK01<b>SEGMENT = "1"</b>>
    <E1EDKA1 ><PARVW>EK</PARVW> <ILNNR>231654845121</ILNNR>
    </E1EDKA1>
    <E1EDKA1 <b>SEGMENT = "1"</b>><PARVW>LF</PARVW>
    <NAME1>international</NAME1>
    <NAME2>Delhi</NAME2>
    <ILNNR>2121211545</ILNNR>
    </E1EDKA1><E1EDK02 <b>SEGMENT = "1"</b>><QUALF>001</QUALF>
    <BELNR>AAAAAAAAA123</BELNR>
    </E1EDK02><E1EDK02 <b>SEGMENT = "1"</b>><QUALF>002</QUALF>
    <BELNR>AAAAAAAAA123</BELNR>
    </E1EDK02><E1EDP01><POSEX>45</POSEX>
    <E1EDP19 <b>SEGMENT = "1"</b>><QUALF>001</QUALF>
    <IDTNR>00000000002150059</IDTNR>
    <KTEXT>Reddy</KTEXT>
    </E1EDP19><E1EDP19>
    <QUALF>003</QUALF>
    <IDTNR>5484218521214</IDTNR>
    </E1EDP19></E1EDP01>
    </IDOC></ORDERS05>
    Regards
    Bhavesh
    PS : You need to add SEGMENT = "1" for every segment. Please do add it if I have missed in the XML above.

  • File to IDOC Scenario Not able get Metadata (IDX2)

    Hi,
    I am doing File to IDOC scenario. I have done all configurations in IR and in ID. But it is throwing error like ATTRIBUTE_IDOC_METADATA-Basic type ZOIDOC does not exist.
    Where as my custom idoc is a not exit in metadata (IDX2). Also I am trying to reload same manually but I am not able to reload it. I have all required configuration in SAP R/3 side like partner profile.
    I would appreciate yours inputs.

    Hi Sunil,
    You are saying that you are unable to load the Metadata even manually.
    There could be a problem with the RFC destination defined within the IDX1 port. So first test the RFC destination using SM59.
    Also ensure that you have used the right naming conventions for the PORTS and RFC destinations as below:
    <SID>CL<ClientNo> e.g  DXXCL055 where DXX is the SID and 055 is the Client No.
    Rgds
    RC

Maybe you are looking for

  • ITunes Home Sharing not loading over VPN after upgrade to 10.10.2

    Hey, all. For years I have used a VPN to stream my iTunes library from my home computer to my work computer (who wants to bring a drive around with them everywhere?).  It works flawless on 10.8.5... Ever since I upgraded to 10.10.2 on my Mac Mini, th

  • Foran document attachment in DMS

    hi all I would like to Display FORAN Drawing document(which is of VRML format) from SAP. any one can help me . with regards amit ranjan

  • Photoshop Elements 13 Organizer will not open.

    Trying to open the program after initial install, I get the error message ""DirectX/Direct Play could not be initialized."" Direct X is installed on my PC. How can I get Organizer to open?

  • JSP to write javascript code

    somebody in the net say : " You could however have JSP write javascript code when creating the page that would set the javascript variables with values from your JSP variables. " how can we do that ?? can somebody show me a sample code ??

  • Spring framework

    how can i lookp ejbs using service locator