About sending idoc

hi,
How to send control data with doing any mapping functionality?
How can i send header data of an i doc to sap sys without mapping ?
pls give full details on this.
ravi

*Like Mahesh said about the ale settings u need to do the  following  ....
To Configure the IDOC SCENARIOS ,PROCEED AS FOLLOWS
STEP 1:ALE SETTINGS TO POST IDOC INTO SAP R/3
We need to do the following settings in XI
1)   Create an RFC Destination to the Receiving System in transaction code (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.Both should be succesful
2) Create Port Using Transaction Code  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 XI towards R/3
e)   Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a)  Create new
b)  IDOC Message Type
c)  Enter port created in IDX1
                    SETTINGS IN SAP R/3
     We need to do the following settings in R/3
     Logon to Sap R/3 System
1)   Create an RFC Destination to XI in transaction code  (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.Both must be succesful
2)   Create communication Port for Idoc processing Using Transaction(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)
d)   Enter the RFC Destination created in SAP R/3 towards other system.
e)   Save
3)   Create Partner Profile with Inbound Parameters (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
     Then Save
e)   Select Partner no. and LS which were create above
f)   Now we have to give some Inbound Parameters.So click on ADD TO Create Inbound Parameter
g)   Select Message type
h)   Double click on Message Type and Then Enter the details  for Message Type and Process Code.
I)   save
4)   In Transaction SALE, Create Logical System
a).  Go to Basic Settings-> First Define logical systems
     and then assign logical systems
b)   Double click on Define the logical systems
c)   Give data for your Logicaal System and Name
d)   Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e)   Assign the logical system name to the client
I think these steps will help
Edited by: Tom  Jose on Jan 22, 2008 9:36 AM

Similar Messages

  • Sender IDOC and Receiver Soap

    Hi,
    I dont Know how to do the Scenario.
    I never used Sender IDOC in XI.
    I am Using Now.
    Cany Any one of u Explain in Detail about Sender IDOC How to configure..
    I Dont Know How to define Logical system and where to define and when to use.
    I need compl,ete Information/
    Ponts willbe awarded.
    Regards,
    Jayasimha
    [email protected]

    Hi ,
    Go thru this Blog for posting the IDoc from R/3 to XI.
    <a href="/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi Steps for Posting IDOC's</a> by Ravikumar Allampalam
    <a href="/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi Configuration for Pushing IDOC's from SAP to XI</a> by Swaroopa Vishwanath
    This Blog explains the RFC to WEBSERVICE scenario.
    Configure your scenario like this except making the changes to the sender as IDoc instead of RFC.
    <a href="/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1 -> XI -> WebService - A Complete Walkthrough (Part 1)</a> by Shabarish Vijayakumar
    <a href="/people/shabarish.vijayakumar/blog/2006/03/28/rfc--xi--webservice--a-complete-walkthrough-part-2 -> XI -> WebService - A Complete Walkthrough (Part 2)</a> by Shabarish Vijayakumar
    Regards
    Santhosh
    Remember to set the thread to solved when you have received a solution
    [url=Use a Good Subject Line, One Question Per Posting - Award Points;  Use a Good Subject Line, One Question Per Posting - Award Points[/url]

  • Idoc to file scenaro ( sending IDOC as it is to NON-SAP)

    Hi Experts,
    I am doing idoc to file scenario.
    I am having SAP R/3 system with 3 clients(100, 200 & 300), IDOC is comming from SAP R/3( any one of the client)
    In this is scenario, I am sending IDOC-XML as it is to the NON-SAP system.
    I heard that, i can do in 3 ways. those are
    1. Without any repository objects: you can go ahead with No interface mechanism on the target side.
    2. Without message type: create a message interface whose message type would be idoc itself
    3. With message type: export the IDOC as xsd file and re import the xsd file as an external definition.
    If i  go without IR objects,Please tell me whether i need to create Interface objects(i.e. DT,MT & MI) & Mapping objects (MM & IM) or not for the reciever.
    MY ASSUPTION:
       step1: I will import the IDOC into IR.
       step2: Directly i will go to the ID without desiging any object in IR ( is it ok).
      Is my assuption or correct or not?, please tell me.
    So please tell me the entire scenario how to achieve this.
    Please help in this issue.

    Hi Laxmi
    1. Without any repository objects: you can go ahead with No interface mechanism on the target side.
    -- Not Possible
    2. Without message type: create a message interface whose message type would be idoc itself
    -- No need for the Message Interface for IDOC. You will directly import the IDOC and do the Mapping
    3. With message type: export the IDOC as xsd file and re import the xsd file as an external definition.
    -- This is Possible. you are export the IDOC as XSD File and reimport the same. so there is no difference. If you are going to change the IDOC Structure then this is possible.
    Here I am sending some links which are useful for IDOC to File Scenario. Please go thru the links given below..
    While doing an IDOC -> XI -> File scenario, The Points to noted are:
    1. You don’t need a DT, MT or a message interface for the IDOC as it itself acts as the Message Interface.
    2. You import the IDOC and use the same in your mapping.
    3. In this configuration note that you don’t have a sender agreement as you don’t have a sender IDOC adapter.
    If it is that you wanted to send an IDOC from XI (File to IDOC) , then in this case:
    points 1 and 2 will remain, but the 3 will not. You will need a sender agreement for the file and a receiver agreement for the IDOC.
    IDOC -> File scenario ref:
    IDoc-XI-File scenario
    File -> IDOC ref:
    File to IDOC
    To be able to trigger your IDOC from the SAP ISU system, you will have to set the partner profile in we20. Select your Business System (mostly under Logical system) and then create Outbound entries for whichever IDOC you want to trigger.
    You define your basic type also in your partner profile settings, Please go thru the following links to get a better idea about partner profile:
    http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b833243d711d1893e0000e8323c4f/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7cd343d711d1893e0000e8323c4f/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/32/692037b1f10709e10000009b38f839/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/5e/b8f8bf356dc84096e4fedc2cd71426/frameset.htm
    Also, I would suggest that you go through this blog by michal if any issue arises,
    /people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
    /people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
    I hope this answers your query.
    Award the POINTS if it is useful **
    Cheers
    Vasu

  • Error in Sending IDoc to XI

    Hi Gurus,
    We are not being able to send Idocs from one of our Back-end SAP system. The Idoc status in we05 is successful but it doesn't reach XI. So we checked in SM58 in the Back-end R/3 system and there it shows the error:
    No Service For System  SAP*** , Client *** in Integration Directory
    We tried almost every possible setup
    -The System is defined in SLD and has the logical system name.
    -The Adapter Specific Identifiers are correct for the corresponding business system in ID
    -The RFC destination in R/3 system is defined.
    - Read through other similar threads in SDN about the similar problem.
    Do anyone have a more definite solution for this particular problem? The other R/3 systems are connected to XI system and all IDocs from those systems are arriving at XI.
    Waiting for your valuable advices!
    Regards,
    Suddha

    Hi All,
    We had eventually found the solution to this problem we were facing in sending IDoc, though I couldn't manage to update the thread with the solution. I think this would be a very helpful information for those who face similar problems.
    Let me describe the scenario first briefly,
    We are sending an IDoc (Idoc extension), from SAP system to XI and then send the XML payload as mail attachment to the receiver via receiver mail adapter. Since this is a cross company transaction, hence we have configured the scenario as a B2B in ID, which means we use Parties for both the sender and receiver.
    Now in the ID we had done all necessary configurations and used parties and services under Party. For the sender SAP system we assigned a Business System to Sender Partner, configured the Party Alternative Identifiers correctly. The ports were created in IDX1.
    On the other hand the SAP system was also configured successfully - including Partner Profile, Distribution List, RFC destinations and ports.
    In SLD we created Business System for the SAP system and in ID the Business System under party had the correct logical system name as Adapter Specific Identifiers.
    But after all these, the IDoc was not arriving at XI, though in R/3 the status of the IDoc was 03 in we02. When we checked in sm58 in R/3, it showed us the error message that "No Service For System  SAP*** , Client *** in Integration Directory".
    The cause to this problem was:
    We created (assigned from SLD) Business System only under Party (Sender), as this was a B2B scenario, and didn't create (assign) a Business System without Party, as we didn't need one at all in the scenario configuration. And this the reason behind this error. When an Idoc arrives at XI, before the Inbound IDoc adapter converts the IDoc to IDoc XML using IDoc metadata............it checks in Configuarion to see if any Service without Party (Busniess System) is defined for the Sender SAP System and Client (The SNDPOR and MANDT field values from IDoc Control header are taken as the SAP SID and Client). If it finds one it accepts the IDoc and starts the Normalization (Sender Party, Service......in the message header) and IDoc to XML conversion. If it cannot find an Service without Party in ID for sender system, it rejects the Idoc with the error message that we saw in sm58 in backend R/3 system.
    In this step the Service under Party doesn't help, because at this point the Inbound IDoc adapter can not deterimine the sender party.
    Hence for sending an IDoc from an SAP system to XI, we need to have an Service Without Party in ID, whether or not we require it in our actual Scenario Configuration, which is ofcourse not a case for the Reverse Scenario, ie Sending an IDoc into SAP system from XI.
    This is the similar with BC adapter as well. I was already aware about this behaviour of BC adapter from my past experience and this actually helped to troubleshoot this IDoc adapter problem.
    This was ofcourse a useful and new learning for me and hope would be helpful to others as well. Let me know if anyone has any doubts on this.
    Regards,
    Suddha
    Edited by: Suddhasatta Guha on Aug 28, 2008 1:03 PM

  • Send idoc to other system via SOAP

    Hi,
    I intend to implement an interface with other system non SAP, to send idocs via SOAP.
    I've read some documentation on sdn but i'm very confused about Was / XI / BSP and some others terms.
    Please, can someone help me, driving me to the right way and where to start ?
    I don't know either if this the best solution to send many idocs... I'm talking about 10000 idocs each time.
    In advance, thanks.

    Vitor,
    I suppose u want to distribute data of Idocs to a system which accepts SOAP request. For the same u can use XI with necessary distribution model on R/3 side to post the IDoc to XI and XI SOAP receiver adapter making a call to necessary SOAP server to post the data.
    Regards
    Rajeev

  • Thirdparty sending Idocs to PI

    Hi All,
    We have a requirement in which thirdparty can sending Idocs directly.
    So we configured scenario as below:
    1)Thirdparty will send Idoc to PI
    2)PI will do the data modifications in mapping
    3)And forward idoc to SAP.
    now here when Thirdparty system is trying to send some Idoc we get error "RFC_ERROR_SYSTEM_FAILURE".
    Can anybody suggest me some blog or link which talks about similar requirments?
    We have created Logical system , Business system in PI Development and configured further ID settings.
    I am not sure what is wrong in this?
    Thanks and Regards,
    Atul

    Hi,
    Since you're having problems determining the queue i suggest a different approach,
    look for the RFC destination (transaction SM59) that your IDoc adapter is using and deliberately make the connection fail e.g. remove the user for the RFC (NOTE: this is applicable only if you want ALL message types for that destination to be stopped, otherwise if there is only a specific message type that you want to stop then go to IDX2 and delete the metadata for that message type)  both of this will result to your IDocs being stucked tRFC (transaction SM58)  you have stopped the IDoc flow with this
    Then you can go to transaction SMQ1 of XI and you will see there the queue that your IDocs are using, as suggested by others most likely of queue name XBTO***
    You can revert back the alterations done once you want the IDoc to flow again, stucked entries in SM58 you can process by running report RSARFCEX from transaction se38
    Hope this helps
    IF this is an XI Production box you may need to get the appropriate changes be approved by your Controller as this is only a temporary change and not a change request, hence only a workaround
    Edited by: HJ Dlec on Jul 17, 2008 7:38 AM

  • Problem while sending IDOC to File Senario

    Hi Experts
        I am having problem while sending the Idoc from SAP R/3 to File
       I have done all the setting in SAP as well in XI but while pushing IDOC
       I am getting error in the transaction sm58 in SAP R/3
      " <b>The service for the client 300(My SAP R/3 client) is not present in Integration
      Directory</b>"
    I can any one explain me what to done on this....all the connections are fine
    Waiting for Response
    Adv points and thanx
    Rakesh

    Reason and Prerequisites
    You send IDocs from system ABC to the exchange infrastructure (XI) of system XIZ, and error messages are issued in system ABC (Transaction SM58) for the IDOC_INBOUND_ASYNCHRONOUS function module.
    This note proposes solutions for the following error messages:
    a) No service for system SAPABC client 123 in the integration directory
    b) Transaction IDX1: Port SAPABC, client 123, RFC destination
    c) ::000
    d) NO_EXEC_PERMISSION: "USER" "Business_System"
    e) IDoc adapter inbound: Error error ...
    Solution
    a) Error message: No service for system SAPABC client 123 in the integration directory
    Solution:
    You send IDocs from system ABC to XI. In the control record of the IDoc, the SNDPOR field contains the value "SAPABC". The client of the sending system is determined by the MANDT field of the control record. The system ID and client are then used to determine a service without party of the type (business-system/business-service):
    Business system
    Activities in the System Landscape Directory (SLD)(Create technical system):
    Create a technical system for system ABC in the SLD, and create the client for this. Do not forget to assign an "ALE logical system" (for example, "ABCCLNT123") to this technical system.
    SLD (Business system):
    You can now explicitly assign a business system to this client.
    For more details, refer to the SLD documentation.
    Activities in system ABC (self-registration in the SLD):
    Alternatively, you can register the system in the SLD in system ABC with Transaction RZ70. You will find detailed information about the SLD registration of systems on the SAP Service Marketplace for the "Exchange Infrastructure" in the document "Exchange_Installation_Guide.pdf".
    In system ABC, you can check your configuration with TransactionSLDCHECK.
    Activities in Integration Directory (import business system from SLD):
    You will find the business systems under Services Without Party in the Integration Services. In the Service menu, you will find the system identifiers, the client, and the corresponding ALE logical system under "Objects"->"Adapter-specific identifiers".
    Use the Import/Update button to copy the data from the SLD, to create business systems, or to update their identifiers.
    Business service
    Activities in the Integration Builder directory:
    You want to create a service without party that is not part of your system infrastructure and is therefore not maintained in the SLD.
    In the Integration Builder directory, you will find the "Business-Services" under Services Without Party. In the Service menu, you will find the system identifiers, the client, and the corresponding ALE logical system under "Objects"->"Adapter-specific identifiers".
    Activate the change list in Integration Directory.
    In system ABC, you can restart the incorrect entry from Transaction SM58 .
    b) Error message: Transaction IDX1: Port SAPABC, client 123, RFC destination
    Solution:
    The Integration Server tries to load the IDoc metadata from the sending system. The IDoc schemas from the Integration Repository cannot be used because they are release-dependent.
    The sending system is determined by the value of the "SNDPOR" field from the IDoc control record (for example, "SAPABC").
    Activities in the central XI system:
    In Transaction IDX1, you can assign an RFC destination to the sending system (for example, "SAPABC"). This must be created beforehand in Transaction SM59.
    Note that the IDoc metadata is cross-client data. In Transaction IDX1, only one entry must be maintained for each system. Only the lowest client is used by the runtime for Idoc metadata retrieval with RFC.
    Ensure that only SAPABC and not "SAPABC_123" is entered in the port name.
    c) Error message: "::000"
    Solution:
    This error occurs if the central XI system tries to load the IDoc metadata from the sending system by RFC.
    There may be several different reasons for the failure of the metadata import, the error is not transferred in full by tRFC completely, and this results in the error message above.
    User cannot log onto sending system
    User/password/client is not correct or the user is logged due to too many failed logons.
    Activities in sender system ABC:
    Transaction SM21 contains entries for failed logons.
    Activities in the central XI system:
    Determine the sending port from the IDoc control record of the IDoc. If the ID of the sending system has the value "ABC", the value of the sending port is "SAPABC". You will find the RFC destination used for the "SAPABC" sending port with the lowest client in Transaction IDX1. In Transaction SM59, you will find the RFC destination containing the maintained logon data .
    User does not have the required authorizations
    Activities in the sender system ABC:
    In Transaction SM21, you will find entries relating to authorization problems and more exact details.
    Contact your system administrator and, if necessary, assign the user the required roles in user administration.
    IDoctyp/Cimtyp cannot be loaded
    Activities in sender system ABC:
    In the sender system, you can check your IDoc types in Transaction WE30 (IDoc type editor)  Take note not only of the errors, but also of the warnings.
    The most common errors are:
    - IDoc type or segments not released
    - Segments that no longer exist are listed in the IDoc type
    - Data elements that do not exist in the DDIC are assigned to fields
      in the segment.
    Contact your system administrator and correct these errors in the IDoc type.
    d) Error message: NO_EXEC_PERMISSION: "User" "Business_System"
    Solution:
    You created a list of users in the directory who are authorized to use the "Business_System". The user in the error message is not on the list.
    Alternatively, the same error is used if you have created a sender agreement with a channel of the IDoc type for the "Business_System" and the interface used. The user in the error message is not contained in the list of all authorized users defined there.
    e) Error message: IDoc adapter inbound: Error error
    Solution:
    You send IDocs to the central XI system, where they are received by the IDoc adapter. The IDocs are converted into IDoc XML, and a corresponding XI message is generated and transferred to the XI Runtime Engine. The Engine tries to read its own business system from the "Exchange Profile". If the Exchange Profile is currently unavailable, the message is not processed and it is returned to the sending system with an error message.
    Regard's
    Prabhakar.....

  • RFC error "No authorization to send IDOCs with message type ..."

    Hi all,
    I have now tried just about everything I could think of, applied all the notes mentioned on this forum but still no luck. Can anyone please help ...
    I have got a file to idoc scenario, the status in the sxmb_moni is successful, but the outbound processing logs an error. When I go to transaction SM58 I get an error for the user XIAFUSER with the message "No authorization to send IDOCs with message type WPUUMS".
    I have tried giving this user SA_ALL access and still got the same error thus concluding that this is not an authorisation error.
    Any suggestions?
    Regards,
    Liesel

    Hi Liesel,
    The RFC destination that you have put in IDoc communication channel must be present in your SAP XI system, transaction SM59 also.
    Please check if the user id/Password that you have given has all the authorization.
    Also check the User ID and passwrord in SM59 in R3 and see if a Remote Login is possible.
    There is also some configuration by which the clients are allowed / blocked from receiving Idocs from XI. Basis guys can do it for you. Please approach your basis consultant. Hopefully that helps..
    Regards,
    Abhy Thomas

  • Error sending IDOC from external Java application to Sap ERP system

    Hi Experts!
    When I try to send Idoc from Java application to XI an error occurs : no service for system CLNTJAVA, client in Integration Server.
    My question is: What value the setSenderPort() is excepting?The Java third party business system's logical name or the ERP business system's logical name where the JCO can be found?I tried both of them, but still have the problem.
    Please help. I read all threads about this error, but non of those can help me.
    My relevant java sourcecode:
                doc.setSenderPort("CLNTJAVA");
    The XI documentation says that:In the case of non-SAP senders, the entry in the SNDPOR field is interpreted as a logical system name, and the corresponding business system is searched for in the runtime cache.
    Both case(third party business sytem and erp business system) I have configured the ID    i think correctly. I  made a business systems,I configured the adapter specific identifies,I  made the IDX1 port,I made the RFC destination,I polled the IDOC type with IDX2 transaction, I have made full cache refresh,I configured the INTEGRATION_DIRECTORY_HMI rfc destination,but I do not made any communication channels, receiver determinations, receiver agreement.
    My configurations if it can help for you.
    Hostname:sapsp5
    System name: NE2
    Clients:
    000 ERP
    001 Integration Server
    <b>SLD configurations:</b>
    Third Party Technical system name: Java_sytem
    Business System:CLNTJAVA
    Logical system name: CLNTJAVA
    <b>ID configurations:</b>
    Business System:CLNTJAVA
    adapter-specific identifiers:logical system:CLNTJAVA, <u>the rest is initial</u>,because I cant change it.
    IDX1 port name: CLNTJAVA the client is 001. the rfc destination is client_001.
    I think the IDX1 port and the adapter specific identifiers are wrong. is it?
    my java source if the sender is the JCO
    doc.setSenderPort("INTSERV");
    My configurations if the sender is the JCO.
    <b>SLD configurations:</b>
    Technical system name: NE2
    Business System:INTEGRATION_SERVER_NE2
    Logical system name: INTSERV
    <b>ID configurations:</b>
    Business System:INTEGRATION_SERVER_NE2
    adapter-specific identifiers:logical system:INTSERV,system NE2,client 001.
    IDX1 port name: INTSERV the client is 001. the rfc destination is client_001.
    Could this error be an autorization error?I tired to connect to the xi from the Java, with the user PIISUSER extended with PISUPER roles.
    Thank very much.

    Hi!
    My SNDPOR already set to my source business system's logical name if you check my configurations(JAVACLNT), so there is another problem unfortunately. I set SNDPRN to JAVA, but it still does not work.
    Check this configuration please(posted here:
    No service for system ... in Integration Directory)
    doc.setMessageType("ACC_DOCUMENT");
    doc.setRecipientPort("SAPSE1"); // get stuck in XI mapping if not set
    doc.setRecipientPartnerType("LS");
    doc.setRecipientPartnerNumber("SE1CLNT500");
    <b>doc.setSenderPort("SAP3MA");</b>
    doc.setSenderPartnerType("LS");
    <b>doc.setSenderPartnerNumber("TREMACLNT");</b>
    doc.setClient("100");
    Inside XI configuration integration builder
    <b>Business Service: Service: TREMACLNT</b>
    Under the menu Service - Adapter specific identifiers
    Idoc Adapter Logical system: TAPPMAN (This thing is important when sending idoc XI -> SAP and should match the logical sys in the receiving SAP system)
    IDoc Adapter and RFC adapter R/3 Sysytem ID: 3MA
    Client: 100
    In IDX1 trans
    <b>Port: SAP3MA</b> (Note that the 3MA here is matched against the IDoc Adapter and RFC adapter R/3 Sysytem ID: 3MA)
    (a not so well documented feature)
    Client: 100
    RFC Destination: SE1 (A SAP test system from where IDOC def can be imported, rfc dests are setup in SM59)
    I guess that your idx1 port name is the same as the SNDPOR value. I think it should be, because the XI is whatching the IDOC traffic in the idoc adapter port, so you should send the IDOC from external system to the adapter port. Is it right?
    My idx1 port is the same as my SNDPOR value in Java,but still came the error.

  • HELP Sending IDOC

    Hi,
    I want to send an IDOC but get the following error message:
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_WRONG_INTF</SAP:Code>
      <SAP:P1>MYSEND</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>IDoc Interface MYINTERFACE konnte nicht interpretiert werden</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Another thread says that the problem is that the Inbound interface doesn't match the namespace urn:sap-com:document:sap:idoc:messages
    and that it would be necessary to name the interfaces the same as the IDOC type (here: COND_A.COND_A02). From which software component can I import the namespace???
    Any help will be appreciated, kind regards,
    Heiko
    PS: Is there a blog about this topic?

    IDOC -> XI -> File ....
    Points to note ...
    1. you dont need a DT, MT or a message interface for the IDOC as it itself acts as the Messg. Interface.
    2. You import the IDOC and use the same in your mapping.
    3. in the configuration note that you dont have a sender agreement as you dont have a sender IDOC adapter.
    ~~ ShabZ ~~
    Opps just noted that you need to sent an IDOC from XI (File to IDOC)
    Anyway in this case,
    points 1 and 2 will remain, but the 3 will not. you will need a sender agreement for the file and a receiver agreement for the IDOC.
    IDOC -> File scenario ref : /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    File -> IDOC -> /people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping (It concentrates on XSLT mapping but also gives an idea about the configuration part.Do go thru that, it might help you.)
    Message was edited by: Shabarish Vijayakumar

  • Sending  IDOC from XI to R/3

    Hi All,
    I have created an IDOC - XI side here i am sending IDOC  XI to R/3 it is showing Red Flag in SXMB_MONI but it is not showing any errors what will happend...? can any body suggest me the solution..?
    Thanks
    Sudheer

    I hope you followed these steps for posting the idoc out of r/3.....
    STEP 1:ALE SETTINGS TO POST IDOC OUT OF SAP R/3
    We need to do the following settings in XI
    1)   Create an RFC Destination to the Sending System in transaction code (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.Both should be succesful
    2) Create Port Using Transaction Code  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 Using transaction Using Transaction (IDX2)
    a)  Create new
    b)  IDOC Message Type
    c)  Enter port created in IDX1
                        SETTINGS IN SAP R/3
         We need to do the following settings in R/3
         Logon to Sap R/3 System
    1)   Create an RFC Destination to XI in transaction code  (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.Both must be succesful
    2)   Create communication Port for Idoc processing Using Transaction(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)
    d)   Enter the RFC Destination created in SAP R/3 towards other system.
    e)   Save
    3)   Create Partner Profile with Outbound Parameters (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
         Then Save
    e)   Select Partner no. and LS which were create above
    f)   Now we have to give some Outbound Parameters.So click on ADD TO Create Outbound Parameter
    g)   Select Message type
    h)   Double click on Message Type and Then Enter the details  for Receiving port, Pack size=1 and Basic type
    I)   save
    4)   In Transaction SALE, Create Logical System
    a).  Go to Basic Settings-> First Define logical systems
         and then assign logical systems
    b)   Double click on Define the logical systems
    c)   Give data for your Logicaal System and Name
    d)   Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
    e)   Assign the logical system name to the client
    5)   Create Customer Distribution model in the transaction code BD64
    1)   Click on the Create modal View button and enter the short text, Technical name etc as shown below
    2)   Now select the created model view and click on Add message type button .A pop up box appears, enter Sending system, receiving system and message type
    3)   Save the Distribution model
        Generate Partner Profiles
    Click on Menu Item ‘Generate Partner Profiles’
        It leads to the next transaction where in the selection screen you have to provide Model view name, Partner System logical system and execute
        Then, you will be intimated about the partners, port creation, and outbound parameters creation
    4)   Distribute Customer Distribution Model
        In the menu item  GO to Edit->Modal View-> ‘Distribute’ to the destination client
        Popup window appears ,press Enter
    You will be intimated about the the Modal View Distributed

  • Sending IDocs from R/3 to XI

    Hello,
    I try to connect a R/3 system to an XI system. I have made the SLD configuration, created RFC destinations, ports and so on. Sending IDoc from XI to R/3 was successful.
    No I would like to send IDocs from R/3 to XI. I did the necessary steps at R/3 as described in several blogs etc.:
    SM59 rfc dest to XI
    WE21 tRFC port
    I also read about this step: Create receiver sys as logical system in BD54. What is this for? I am not sure if this step was done in my case, cannot check it at the moment.
    I am trying to send an IDoc via transaction WE19 (Idoc Test tool). I think there is no need to create a partner profile?
    Now I am wondering: Which values must be set in the control record? I inserted the port pointing towards XI, but I am not sure about the other fields.
    I know there are several blogs on this topic but for me there are some details missing. I am also interested in some kind of explanation not just WHAT steps have to be done, but WHY they have to be done.
    Thanks in advance, point will be awarded.
    CHRIS

    > 1. The process is like this: The Logical system is
    > defined (as its name suggest ) just for Logical
    > definition of the communicting parties. The technical
    > details are not provided here.
    > 2. Then RFC Destination is maintained where actual
    > connection parameters r maintained.
    > 3. Port here act as the medium through which the
    > transmission is done.
    > 4. To identify ur particular message, Partner Profile
    > is maintained.
    >
    > Now in we19 test tool, the port provides the medium
    > where the data should be sent. Through this medium,
    > the connection to the receiver is checked via RFC
    > destination.
    Also thanks to you. I understand that the message is sent to a port, which points to a certain RFC destination. But still I don't get it: I thought thats exactly what WE19 is for: To send IDocs for testing purposes to ports, while there is no partner profile needed? I thought there is no partner profile necessary as I can set all fields manually in the control record (receiver port, sender port, message type, receiver type and so on).
    Kind regards
    CHRIS

  • Process Orders, send idoc (LOIPRO) when its released and saved.

    Hi ,
    Here is my requirement.
    For process Orders, send idoc (LOIPRO) when its released and saved. (COR2).
    Here are the options I have tried.
    - Create an enhancement spot after the commit statement, and submit RCCLORD
    For some strange reason Submit to RCCLORD isn't working. Even I have tried to execute it independently, It isn't working properly. It is working fine from POIT, but not independently...
    - Call CLOI_MASTERIDOC_CREATE_LOIPRO function module, but for this I have to get all the related data into proper tables, and I am not sure if it works either.
    I have searched here in SDN to for some help, the closest thread talks about creating a ZFM for IDOC creation, but I dont have much of the details of that.
    Re: Process Orders, send idoc (LOIPRO) while creation/modification(COR1+BADI)
    Need some help on this.
    Thanks & Regards,
    Kalyan Venigalla.

    Hi!
    not sure, but maybe it will help you:
    RCCLORD have code with check already sent orders
    Try add this code before submit RCCLORD
    *         -> free global table for collecting order numbers
              free memory id 'LOIAUFNRTAB'.                        "

  • Sending IDOCS through transaction PFAL

    Hi,
    We have a requirement to send idocs through transaction PFAL for a set of PERNRs for all infotypes.What is the way to go about this?
    Thanks ain Advance!
    Regards,
    Nejuma Iqbal

    hi
    you cannot send IDocs thru PFAL transaction.
    you can send HR Master Data thru PFAL.
    yes you can send the Pernrs as they are Components of Organizational Elements.
    Here is the Procedure to send Personal Numbers:
    1.Execute the transaction PFAL.
    2.Give the object type as P.
    3.Give the Pernr values in Object ID field
    4.Select the transfer mode as Update
    5.In the Receiving Partner give your receiver name
    6.Give the message type as HRMD_A in the Message Type field.
    7.Dont change the remaining values.Keep it as such.
    8.Execute the Program.
    Also keep in mind that while sending the HR data you need to follow the certain sequence
    unless otherwise your data wont be replicated successfully.
    Here is the sequence O,S,P and C.
    Means before sending P  you should send O and S.
    Cheers,
    Abdul Hakim
    Mark all useful answers..

  • Send IDocs to machines depending of the Organizational Units.

    hello,
    I want to know if there is a way to send IDocs to a determain machine depending of the organizational Unit or their sub-tree objects.
    Imagine, I have 10 organizational Units (10 countries), and I want to send to each country without sending the modification to the rest os the other countries.
    I there a way I can do it?
    Thank yu very much in advance...
    PM

    Hi David,
    This can be done in the Mapping.. For this Java Mapping will be easier.
    First you need to read input xml document, and search for the Geography/Region.. And then gorup the similar one into the list etc..
    After this Mapping, you will be having one message for each Geography . For this you required to use BPM and in the BPM you can split the messages(1:N) mapping.. But it is still based on the target Structure. If you have many geographies, then it is not an idle solution..
    If you want to make your scenario as an Independent, then you can go with some workaround solutions like this. Output all the files into one folder in XI. And from XI execute an Shell Script, which will read the data and tarnsfer into required Geograhy/Person etc.
    So in this case XI part is almost independent. Only you need to maintain the SHell script..
    This is just my views
    Use SAX parser for the Java Mapping here..about Java mapping
    Java Mapping
    Java Mappings for XI
    Mark helpful answers
    Hope this helps,
    Regards,
    Moorthy

Maybe you are looking for

  • 10.7.4 Hanging at Startup

    I don't often find the need for these forums, but I've got a tough one this time. Here's my issue: I was recently using my late 2008 MBP (6 Gig RAM, 500 Gig HD) without issue as I have done for the last several years. The other night, I was running m

  • Field RF05A-NEWBK. does not exist in the screen SAPMF05A 0100

    Hi, We are doing the intercompany account payable postings through SAP EDI.  The process following as below - Delivery -> Intercompany Billing -> Account Receivable                                               --> IDOC -> Account Payable While doing

  • Edit Cell Numeric Attributes may show strange default values

    Those values look a bit surprising... I did not type them myself... It happens if you change the data type let's say from unsigned char to double... But it's not a meaningless number: if you now type -1e1000 as a new minimum value, CVI 'corrects' it

  • Sort ArrayList by length

    I need to remove the string(s) with the least number of letters from an ArrayList. How can I sort the ArrayList by the length of the strings contained in it?

  • NO ADDRESS INPUT OPTION N97

    Hi all, I have just purchase an N97. I  have updated to the latest Nokia maps but I also cannot find any where to type in an address. I have deleted Nokia maps from the apps manager and the old version of Ovi maps is there and I can easily find the a