Error receiving IDOC in BPM

hi all
I'm doing a BPM scenario in which i want to receive an IDOC.
The scenario goes like this:
an IDOC is sent from source(from SWCV1) and an interface mapping(done in SWCV2) is done before the IDOC is received in the BPM.I have made an abstract async interface(done is SWCV2) for the IDOC which receives the IDOC in BPM.
The source is sending the IDOC successfully and the Interface mapping also happens properly.
My problem is that the IDOC is not entering the BPM.'Permanent error in BPE inbound processing' is shown.
Simulate message delivery shows:Result of simulation: Message starts a new process
I have no clue what the error is.Please help.

Hi,
You can go to the message in SXMB_MONI and from there go to engine column of the displayed message. In case of BPM, you will have PE there instead of IE or AE. Now click on PE and it will take you to the actual BPM. There you can drill down and try to figure out if the BPM instance has started correctly or what exactly the error is.
Thanks and Regards,
Sarath.

Similar Messages

  • Error in IDoc AAE (Receiver) PI 7.3

    Dear Experts,
    I have a SOAP - IDoc scenario where I am using IDoc AAE reciver adapter for posting IDoc to SAP ECC system.
    Message is successful in SXMB_MONI,however getting an error as below in receiver IDoc adapter.
    Message processing failed. Cause: com.sap.aii.af.idoc.exception.IDOCAdapterException: com.sap.sql.log.OpenSQLException: Failed to set the parameter 9 of the statement >>INSERT INTO XI_IDOC_OUT_MSG ( IDOC_NUMBER , XI_MSG_NO , REF_NUMBER , ORIGINAL_IDOC_NO , IN_TIME , MESSAGING_TYPE , IDOC_TYPE , CIM_TYPE , SEND_PORT , SEND_PRTNR_NO , SEND_PRTNR_TYPE , CLIENT , STATUS , CONTROL_RECORD , CHANNEL_ID , ACK_NEEDED , ACK_RECEIVED , ARCHIVE ) values ( ?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,? ) <<: Cannot assign an empty string to a parameter with JDBC type >>VARCHAR<<.
    My payload for this message is --
    <HU_CREATE01>
                   <IDOC BEGIN='1'>
                        <EDI_DC40 SEGMENT='1'>
                             <TABNAM>EDI_DC40</TABNAM>
                             <MANDT>120</MANDT>
                             <IDOCTYP>HU_CREATE01</IDOCTYP>
                             <MESTYP>HU_CREATE</MESTYP>
                             <SNDPOR>SAPPID</SNDPOR>
                             <SNDPRT>LS</SNDPRT>
                             <SNDPRN>BS_ORIWIN</SNDPRN>
                             <RCVPOR>SAPD3S</RCVPOR>
                             <RCVPRT>LS</RCVPRT>
                             <RCVPRN>D3SCLNT300</RCVPRN>
                        </EDI_DC40>
                        <E1BPHUHDRPROPOSAL SEGMENT='1'>
                             <HU_STATUS_INIT>A</HU_STATUS_INIT>
                             <PACK_MAT>000000000002001755</PACK_MAT>
                             <HU_EXID>00340042312419076037</HU_EXID>
                             <TOTAL_WGHT>11.123</TOTAL_WGHT>
                             <UNIT_OF_WT_ISO>KGM</UNIT_OF_WT_ISO>
                             <CONTENT>00002059911110071031</CONTENT>
                             <PLANT>9610</PLANT>
                             <STGE_LOC>2000</STGE_LOC>
                        </E1BPHUHDRPROPOSAL>
                        <E1BPHUITMPROPOSAL SEGMENT='1'>
                             <HU_ITEM_TYPE>1</HU_ITEM_TYPE>
                             <LOWER_LEVEL_EXID>00000000000000000000_Test</LOWER_LEVEL_EXID>
                             <PACK_QTY>12</PACK_QTY>
                             <BASE_UNIT_QTY_ISO>ZCP</BASE_UNIT_QTY_ISO>
                             <BASE_UNIT_QTY>ZCP</BASE_UNIT_QTY>
                             <MATERIAL>000000000000205991</MATERIAL>
                        </E1BPHUITMPROPOSAL>
                   </IDOC>
              </HU_CREATE01>
    Could you please give me your valuable input for the same.
    Waiting for a reply.
    Thanks in advance.
    Best Regards,
    Sugeet.

    Hello
    Note #1688780 IDoc AAE Adapter fails to insert empty strings in database, has been created to resolve this error. The fix is still being tested, so the note is not available for download just yet. Once the fix is released, the note will be available for download.
    Here are some further details on the cause of the error:
    The issue occurs if the persistency of the IDoc_AAE adapter is enabled
    via the 'Persistance' property for the 'JavaIdocAdapter' resource
    adapter and one or more of the IDoc relevant properties (for example
    sender/receiver port, partner number or type) of the XI message is/are
    empty strings. As empty string insertion into database is not supported
    by the persictency framework the above OpenSQLException exception is
    thrown and the XI message processing fails.
    Regards
    Mark

  • SP14 Multi-mapping - error in receiver idoc adapter

    Hi,
    I have a scenario where a business service should send some XML to SAP CRM. I get the file via a sender JMS adapter and try to post it to CRM via a receiver IDOC adapter.
    I have created a multimapping (1:N - 1 XML file to many Idocs) as should in the repository.
    In the configuration under Interface Determination, I have chosen 'RB_SPLIT' and selected the interface multimapping.
    It should be pointed out, that when testing both interface and message mapping i get no error. All idocs seem to be created as they should.
    When testing the setup 'real life' the message fails. The error message in the monitor says:
    - <!--  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_WRONG_INTF</SAP:Code>
      <SAP:P1>InterfaceCollection</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Unable to interpret IDoc interface InterfaceCollection</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Notice that the above error is when trying to send only 1 record, which in turn then should result in only 1 idoc.
    If trying to send multiple XML records, i get the following error:
    - <!--  Technical Routing
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="OUTBINDING">MMF_ENGINETYPE</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>A system error occurred in the outbound binding</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    In the monitor in the payload of 'Request message mapping' I see as many Maindocument, Submaindocument pairs as should be Idocs.
    Now i really don't know how to interpret the error messages in both cases, so I'm a little lost here...
    It should be pointed out that the idoc being used everywhere in this scenario, has not been modified - from all places it is being used (and only exists) in the 'Imported objects | Idocs' place.
    Also the Idoc is also being used as Inbound interface - so no mistakes here either.
    I really hope someone can help me here, as I'm otherwise pretty stuck in this case.
    Best regards,
    Daniel

    Hi Daniel,
    I have exactly the same type of scenario (under SPS14 and now also SPS15), sending an XML message over JMS to XI and trying a multi-mapping to many IDocs (actually a list of orders in XML is mapped to n ORDERS Idocs).
    I also face problems doing so, when I use the IDoc Adapter as outbound in the Receiver Agreement. I receive the following error:
    <i>CO_TXT_MMF_ENGINETYPE
    Messages in multi message format can be sent to one adapter engine only</i>
    However, I tested the same scenario by just changing the Receiver Agreement to a File Communication Channel and - surprise, surprise - it works. One file per IDoc is created.
    Of course, this is not what we want to accomplish, but when I checked this piece of documentation (sorry another link
    http://help.sap.com/saphelp_nw04/helpdata/en/42/ed364cf8593eebe10000000a1553f7/content.htm
    the IDoc adapter is not listed in the list of Adapters that are supported. Does that mean, that this feature is not supported for generating IDocs? Maybe that's a question for a SAP OSS Message?
    I hope that helped you a little further - if you find out more I'd be happy to learn about it.
    regards,
    Peter

  • Hi, In  a IDOC --- XI(BPM)--- SOAP Sync Scenario failrure.

    Hi, In  an IDOC ->XI(BPM)->SOAP Sync Scenario I observed recently messages are failing in SXMB_MONI with an error as:
    com.sap.aii.af.ra.ms.api.DeliveryException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: System.Web.Services.Protocols.SoapException: Server did not recognize the value of HTTP Header SOAPAction: http://172.16.209.162/esdryrun/ContractData_Push. at System.Web.Services.Protocols.Soap11ServerProtocolHelper.RouteRequest() at System.Web.Services.Protocols.SoapServerProtocol.Initialize() at System.Web.Services.Protocols.ServerProtocol.SetContext(Type type, HttpContext context, HttpRequest request, HttpResponse response) at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing)
    friends, could  u plz help on this.
    Thanks,
    satya.

    Hello,
    This indicates a configuration issue with this SOAP receiver adapter. Please check the on line help for the configuration of the SOAP adapter (the link is below). Please set the indicator in the "SOAP Action" field.
    Configuring the Receiver SOAP Adapter
    http://help.sap.com/saphelp_nw70/helpdata/EN/29/5bd93f130f9215e10000000a155106/frameset.htm
    (Below is the extract from the link)
    SOAP Action
    Specify the SOAP action. The action specifies the value for the
    SOAPAction in Web service messages; set the indicator.
    Regards,
    Sarah

  • Receiver Determination in BPM, SP16

    hi,
    I was able to configure multiple receivers succesfully with all your help. Thanks.
    Now i have to switch this to BPM beacuse i need to add some error handling logic, so i have to switch to BPM.
    In this process will i be able to use my old configuration(cofiguring multiple receivers without BPM)?
    If so how? If not should i have to redo this completely using BPM. There are 13 Suppliers now. So will there be that many receiver determinants in BPM?
    Any tips would greatly help.
    Thanks,
    Tirumal

    Udo and Vijaya -
    In the receiver determination in Integration builder:configuration earlier i used to have IDOC to XML.
    So the Receiver Determination for different receivers was configured based on the conditions.
    Now i have created a BS where in i convert the IDOC -> Abstract IDOC, Abstract IDOC -> Abstract XML.
    In the Integration Process i have the Start, Receive (Abs IDOC), Transform(Abs IDOC to Abs XML), Send(Abs XML), Stop.
    The first receiver determinant, i have IDOC to abstract(BPM) configured correctly.
    But while i select the BPM as the sender, i should be able to select the Abs IDOC but i can select the Abs XML here.
    Any clue why i am not seeing abstract.
    Thanks,
    Tirumal

  • Collection of IDOCs using BPM

    Hi Experts,
    I am trying collection of IDOCs by using BPM.
    I ran into problems and In moni,  the error is
    <SAP:Code area="BPE_ADAPTER">SYSTEM_FAILURE_INTERNAL</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>An internal error has occurred</SAP:Stack>
    Details of above error in trace is : 
    <Trace level="1" type="T">--start sender interface action determination</Trace>
      <Trace level="1" type="T">select interface BLAORD.BLAORD03*</Trace>
      <Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:idoc:messages</Trace>
      <Trace level="1" type="T">no interface found</Trace>
      <Trace level="1" type="T">--start receiver interface action determination</Trace>
      <Trace level="1" type="T">Loop 0000000001</Trace>
      <Trace level="1" type="T">select interface UpdatedContracts_abs_idocs*</Trace>
      <Trace level="1" type="T">select interface namespace http://com/UpdatedContracts/</Trace>
      <Trace level="1" type="T">no interface found</Trace>
      <Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
      <Trace level="1" type="T">Hence set action to DEL</Trace>
      <Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-GETBLOBDATA" />
      <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
    Here i am trying to collect IDOCs for 5 minutes and i need to send them in XML format. Here i have mapping logic and that logic is working perfectly.
    What i am dong is
    1. I am sending IDOCs from R3 system to BPM in XI. ( Here to push IDOCs from R3 system to BPM, do we need to do extra ALE settings. Actually With out BPM simple IDOC to File is working fine, With BPM only i am having error. )
    2. How to reslove above problem. AS per my understanding everthing is fine.
    Thanks,
    Subbu

    Hi Rama Subbarao,
        Error: Check with your loop condition and process steps.
           Collecting of IDOCS using BPM is good, If u want to send the 100 IDOCS per one hour with single BPM it will takes times , Some performs issues and hardware issues are raising.
    Suppose if u send 1000 Idocs per one hour it will takes much time.
    Other Process:
      The collecting of IDOCS it will be downloaded into FILE System.Once IDOCS is downloaded into FILE, it will be not changed the IDOCS.
    Using FILE Adapter we send the flatfiles data from FILE System to XI. if  u using this process performance wise its very good.
    Regards,
    Sateesh N

  • Receiving IDocs from non-SAP system ...

    Hello guys,
    I have problem with implementing IDoc-XI-IDoc scenario. The sender system is a subsystem (non-SAP system) sending IDocs but XI is not able to receive them. I thing the IDoc metadata can not be found.
    Logical system name of the sender is IF6020DEV. I registered the system in SLD. In Integration Directory I imported the Bussines System IF6020DEV to my scenario and I created communication channel of type Sender IDoc Adapter in it.
    In IDX2 I created new port called IF6020DEV and I copied needed metadata into the port. But it doesn't work. Probably I don't do it right because I'm beginner with SAP XI.
    Could you give me any advice how to configure XI for receiving IDocs from non-SAP system?
    Thank you in advance!
    Regards
    Zbynek

    Thank you very much. The issue described in refered discussion is almost same issue what I'm solving. Unfortunetally the described solution dosn't work for me.
    The sender system still returns following error. I know you probably won't understand it because you don't know the subsystem, but maybe you could get some idea what is wrong.
    05/29/09 16:09:19.482 idoup2 Logon...
    05/29/09 16:09:19.482 idoup2 RfcOpenEx (TRACE=1 CLIENT=110 USER=xxxxxx LANG=D LCHECK=1 GWHOST=xxxxxx GWSERV=3361 ASHOST=xxxxxxx SYSNR=61 PASSWD=<password>)
    05/29/09 16:09:19.529 idoup2 Logon RfcOpenEx result=1
    05/29/09 16:09:19.607 idoup2 Call to (IDOC_INBOUND_ASYNCHRONOUS) failed (3)
    05/29/09 16:09:19.607 idoup2 Handle=1
    05/29/09 16:09:19.607 idoup2 key............:
    05/29/09 16:09:19.607 idoup2 status.........:
    05/29/09 16:09:19.607 idoup2 message........:IDoc-Adapter Eingang: Der Absenderport ist initial
    05/29/09 16:09:19.607 idoup2 internal status:
    05/29/09 16:09:19.607 idoup2 idoc_upload failed with rc=(3), try(2)
    05/29/09 16:09:20.607 idoup2 key............:IDoc-Adapter Eingang: Der Absend
    05/29/09 16:09:20.607 idoup2 status.........:EXCEPTION SYSTEM_FAILURE RAISED
    05/29/09 16:09:20.607 idoup2 message........:IDoc-Adapter Eingang: Der Absenderport ist initial
    05/29/09 16:09:20.607 idoup2 internal status:
    05/29/09 16:09:20.607 idoup2 idoc_upload failed with rc=(18), try(1)
    05/29/09 16:09:21.607 idoup2 Logoff...

  • Getting Error in Idoc.

    Hi all,
    I m getting this error  in idoc..
        Entry in outbound table not found.
    I doc number is generated..
    also giving Program code ..check and tell me whr can i do change..
    Following is program for idoc...
    REPORT ZNA_IDOC .
    *TABLES: CRMD_ORDERADM_I,CRMD_ORDERADM_H,CRMD_SCHEDLIN.
    TABLES : ZNA_ID.
    DATA : S_CTRL_REC LIKE EDIDC OCCURS 0 WITH HEADER LINE,"Idoc Control
    *Record
    KUNNR TYPE ZNA_ID-KUNNR, " SEGMENT ORDER DATA
    VBELN TYPE ZNA_ID-VBELN.
    *QUANTITY TYPE CRMT_SCHEDLIN_QUAN VALUE '1.000'.
    DATA : ZORDER LIKE ZNA_ID OCCURS 0 WITH HEADER LINE.
    DATA : T_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE. "Data Records
    DATA : T_COMM_IDOC LIKE EDIDC OCCURS 0 WITH HEADER LINE. "Generated
    "Communication IDOc
    CONSTANTS :
    C_ZRZSEG1 LIKE EDIDD-SEGNAM VALUE 'ZNA_I'.
    PARAMETERS : ZID LIKE EDIDC-MESTYP DEFAULT 'ZID', "Message  Type
    C_RCVPRT LIKE EDIDC-RCVPRT DEFAULT 'LS', "Partner type of receiver
    C_LOGSYS LIKE EDIDC-RCVPRN DEFAULT 'D11CLNT100',
    C_RCVPOR LIKE EDIDC-RCVPOR DEFAULT 'A000000009',
    C_SNDPOR LIKE EDIDC-SNDPOR DEFAULT 'A000000008',
    C_SNDPRN LIKE EDIDC-SNDPRN DEFAULT 'D11CLNT210',
    C_IDOCTP LIKE EDIDC-IDOCTP DEFAULT 'ZNA_IT',
    C_SNDPRT LIKE EDIDC-SNDPRT DEFAULT 'LS'. "Destination System
    ***START-OF-SELECTION
    START-OF-SELECTION.
    PERFORM GENERATE_CONTROL_RECORD.
    PERFORM SEND_IDOC.
    *& Form generate_control_record
    FORM GENERATE_CONTROL_RECORD .
    S_CTRL_REC-RCVPOR = C_RCVPOR. "Receiver Port
    S_CTRL_REC-MESTYP = ZID. "Message type
    S_CTRL_REC-IDOCTP = C_IDOCTP. "Basic IDOC type
    S_CTRL_REC-RCVPRT = C_RCVPRT. "Partner type of receiver
    S_CTRL_REC-SNDPOR = C_SNDPOR. "SENDER PORT
    S_CTRL_REC-RCVPRN = C_LOGSYS. "Partner number of receiver
    S_CTRL_REC-SNDPRT = C_SNDPRT. "Sender Partner type
    S_CTRL_REC-SNDPRN = C_SNDPRN. "Sender Partner Number
    APPEND S_CTRL_REC.
    ENDFORM. " generate_control_record
    *& Form send_idoc
    FORM SEND_IDOC.
    *SELECT * FROM ZNA_ID INTO TABLE ZORDER.
    ZORDER-KUNNR = '1'.
    ZORDER-VBELN = '101'.
    **ZORDER-QUANTITY = QUANTITY.
    APPEND ZORDER.
    T_EDIDD-SEGNAM = C_ZRZSEG1.
    T_EDIDD-SDATA = ZORDER.
    APPEND T_EDIDD.
    CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
    EXPORTING
      MASTER_IDOC_CONTROL = S_CTRL_REC
    TABLES
      COMMUNICATION_IDOC_CONTROL = T_COMM_IDOC
      MASTER_IDOC_DATA = T_EDIDD
    EXCEPTIONS
      ERROR_IN_IDOC_CONTROL = 1
      ERROR_WRITING_IDOC_STATUS = 2
      ERROR_IN_IDOC_DATA = 3
      SENDING_LOGICAL_SYSTEM_UNKNOWN = 4
      OTHERS = 5.
    IF SY-SUBRC = 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ELSE.
    COMMIT WORK.
    LOOP AT T_COMM_IDOC.
    WRITE:/ 'IDoc Generated - ', T_COMM_IDOC-DOCNUM.
    ENDLOOP.
    ENDIF.
    ENDFORM. " send_idoc
    thx...

    The program is probably correct, however, it seems that you haven't completed the 'customizing' just yet. The parameters entered in S_CTRL_REC contains entries which have not yet been maintained in the settings.
    Have a look at the settings. I have no SAP system available right now, so I can't tell you what transaction is needed, but first have look at WE20 (use transaction menu WEDI).

  • Issue with Receive step of BPM

    Hi all,
    I have an BPM scenario in which I send a file to the target system and then receive an acknowledgement from the system. I have used correlation in the BPM for the send and the next receive step .
    When a wrong acknowledgement is placed , the message goes to the queue with the error message "Active correlation Not Found".
    But when an right acknowledgement is placed then also the message goes to the queue with the message "Error in delivery of message to receive step of BPM ".
    The acknowledgement is received and then interface mapping is used which sends the Filename to the Integration Process which is used for the correlation.
    Please give your suggestions .
    Regards,
    Srivatsan M

    When a wrong acknowledgement is placed , the message goes to the queue with the error
    message "Active correlation Not Found".
    when there is wrong ack then there seems to be no value coming in the field which you have used for correlation....or it seems that the field itself is not coming in the wrong ack message
    But when an right acknowledgement is placed then also the message goes to the queue with the
    message "Error in delivery of message to receive step of BPM ".
    Now in right correlation the value that is coming in the correlation field is not  matching with the field for correlation of the send step...
    So the reason for both the errors is wrong correlation configuration.

  • IDOC to BPM to File

    Hi Gurus,
      I have a scenario where by i will need to collect idocs from an R3 system, perform a transformation and output the results into a flat file.
      I looked at various blogs but am still pretty confused.
      For my scenario, do i need to configure a receiver determination to pass the idocs into BPM?
        ( If the answer is no, how does the idoc get pass into the BPM? )
      or do i just need 1 receiver determination to output my result from the BPM into a flat file?
    Thanks in advance.

    Hi,
      At the moment i have 2 receiver determination
      1. from R3 Outbound async to abstract async of BPM
      2. from BPM abstract async to inbound async
      1 receiver agreement
      BPM to a service with a file adapter
      I've also configured another simple scenario without BPM, just sending a IDOC from R/3 to XI with a simple transformation and exporting the output into a flat file. Its working fine and im able to see the XML messages in SXMB_MONI.
    However, for the BPM, when i try to click on the process view via SXMB_MONI, it says no message found. I'm suspecting that somehow the idoc is not even passed to the BPM but i am unable to see where have i gone wrong.
    Any help will be much appreciated.
    THanks in advance.

  • Receiver IDOC adapter - RFC_NO_Authority

    Scenario:
    EDI (Sender File adapter)-->PI7.11-(Receiver IDOC adapter)---->ECC
    Went thru receiver determination, Interface determination, message split, request message mapping, Technical routing and then got stuck at call Adapter stage.  Below is the error:
    xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
      <SAP:P1>Runtime error RFC_NO_AUTHORITY has occurred</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Error: Runtime error RFC_NO_AUTHORITY has occurred</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Is there any step that I may have missed after I  created the receiver IDOC Channel?
    Could you please shed some light here?

    Please, search SDN before posting....
    check these link: Runtime error RFC_NO_AUTHORITY has occurred in SM58
    What its error?

  • Receiver IDoc Adapter - Outbound IDocs in IDX5 but stucked in SM58

    Hi Gurus,
    I have a Receiver IDoc issue with the above error.
    My message is successful in the IE pipeline (but with error on outbound side)
    I can even view the generated IDoc numbers for those messages in IDX5,   but when double-clicking on those IDX5 entries SM58 is called and there I see the error as follows:
    Caller:  PIAFUSER
    FM:  IDOC_INBOUND_ASYNCHRONOUS
    Status Text: No Authorization to send IDocs with Message Type 0
    The weird thing is why is the caller showing as PIAFUSER, when my RFC destination is using a custom RFC user id.
    Shouldn't it be that the Caller be my custom RFC user id since this is the user used by the RFC destination i specified in the receiver idoc comm channel?
    Would anyone of you know how to resolve this?
    I have already implemented Note 837595 for (a) my custom RFC user id in the target system (b) PIAFUSER and PIISUSER in my Integration Server;  and assigned SAP_XI_APPL_SERV_USER role to PIISUSER also as specified in  http://help.sap.com/saphelp_nwpi711/helpdata/en/d4/d12940cbf2195de10000000a1550b0/content.htm
    I am aware that IDoc should be sent to the receiving system by using the IDoc adapter and NOT by using the IDoc Interface (tRFC port)
    Thanks in advance

    Hi All,
    I resolved this on my own.
    The steps i specified in my 1st post (Note implementation & Role assignment) was not enough, we had to assign SAP_ALL & SAP_NEW to the rfc user.    The Note implementation & role assignment should have solved this problem, but strangely it was not enough.
    As for the question on why PIAFUSER is showing up as the caller and not the RFC user id used in the rfc destination used by the port, it's because the original caller is what gets recorded in SM58, in this case Receiver IDoc adapter on the AE so PIAFUSER,   and not the RFC user id.   you can verify this in table ARFCSSTATE
    Thanks to all answers

  • Receiver Idoc adapter - issue

    Hi,
    I need to send an IDoc (CRMXIF_ORDER_SAVE_M01) to SAP CRM. The trouble occur when having/wanting to use/send only the segments that apply to release 620.
    In order to do that I have in my receiver IDoc adapter specified the value '620' in the Segment Version part.
    As soon as having done this my IDocs fail in the adapter giving me the following error:
    - <!--  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>Segment 'E101CRMXIF_ACTIVITY_X', segmentnumber '000001' not correct in structure CRMXIF_ORDER_SAVE_M01</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error: Segment 'E101CRMXIF_ACTIVITY_X', segmentnumber '000001' not correct in structure CRMXIF_ORDER_SAVE_M01</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    The segment specified in the above corresponds to the very fist sub-segment to the main segment (BUSTRANS). So if removing that segment the error jumps to the next segment (which would then be the first sub-segment).
    Should be noted that I have no trouble sending IDocs if I've either not specified a Segment version (meaning latest version is automatically used) or if I explicitly request the latest by entering the latest segment release (700 in my case).
    <Trace level="1" type="T">Convert one IDoc</Trace>
      <Trace level="2" type="T">Convert Control Record</Trace>
      <Trace level="2" type="T">Convert Data Records</Trace>
      <Trace level="3" type="T">Segment= E101CRMXIF_BUSTRANS</Trace>
      <Trace level="2" type="T">Ignore unknown Segment E101CRMXIF_BUSTRANS</Trace>
      <Trace level="2" type="T">Ignore segment field: APPL_SNAME</Trace>
      <Trace level="2" type="T">Ignore segment field: OBJECT_TASK</Trace>
      <Trace level="2" type="T">Ignore segment field: OBJECT_GUID</Trace>
      <Trace level="2" type="T">Ignore segment field: OBJECT_ID</Trace>
      <Trace level="2" type="T">Ignore segment field: PROCESS_TYPE</Trace>
      <Trace level="2" type="T">Ignore segment field: OBJECT_TYPE</Trace>
      <Trace level="2" type="T">Ignore segment field: POSTING_DATE</Trace>
      <Trace level="2" type="T">Ignore segment field: DESCR_LANGUAGE</Trace>
      <Trace level="2" type="T">Ignore segment field: DESCR_LANGUAGE_ISO</Trace>
      <Trace level="2" type="T">Ignore segment field: LOGICAL_SYSTEM</Trace>
      <Trace level="2" type="T">Ignore segment field: CRM_RELEASE</Trace>
      <Trace level="2" type="T">Ignore segment field: CLIENT</Trace>
      <Trace level="2" type="T">Ignore segment field: CREATED_AT</Trace>
      <Trace level="2" type="T">Ignore segment field: CREATED_BY</Trace>
      <Trace level="2" type="T">Ignore segment field: CHANGED_AT</Trace>
      <Trace level="2" type="T">Ignore segment field: CHANGED_BY</Trace>
      <Trace level="2" type="T">Ignore segment field: LOCAL_TIMEZONE</Trace>
      <Trace level="2" type="T">Ignore segment field: OBJECT_ID_OK</Trace>
      <Trace level="2" type="T">Ignore segment field: HIGHEST_ITEM_NO</Trace>
      <Trace level="2" type="T">Ignore segment field: CRM_CHANGED_AT</Trace>
      <Trace level="2" type="T">Ignore segment field: CALC_SCHEMA</Trace>
      <Trace level="2" type="T">Ignore segment field: SCENARIO</Trace>
      <Trace level="2" type="T">Ignore segment field: VALID_FROM_EXT</Trace>
      <Trace level="2" type="T">Ignore segment field: VERIFY_DATE</Trace>
      <Trace level="3" type="T">Segment= E101CRMXIF_ACTIVITY_X</Trace>
      <Trace level="3" type="T">Segment= E101CRMXIF_ACTIVITY</Trace>
      <Trace level="3" type="T">Segment= E101CRMXIF_ADDRESS</Trace>
      <Trace level="3" type="T">Segment= E103CRMXIF_ADDRESS</Trace>
      <Trace level="3" type="T">Segment= E107CRMXIF_ADDRESS</Trace>
      <Trace level="2" type="T">Ignore unknown Segment E107CRMXIF_ADDRESS</Trace>
      <Trace level="3" type="T">Segment= E101CRMXIF_ADDRESS_F</Trace>
      <Trace level="3" type="T">Segment= E101CRMXIF_ACT_REASON</Trace>
      <Trace level="3" type="T">Segment= E101CRMXIF_ACT_REASON_F</Trace>
    Hope someone can help me so that I can succesfully limit the segment version used when sending Idocs.
    Best regards,
    Daniel

    Hi,
    Thanks for your quick reply.
    The funny thing is that even if a try to post the exact same idoc (except for the EDI part) that I have received from CRM it still fails in XI with the before mentioned error.
    But to answer your questions:
    1. I'm not using java mapping but traditional message mapping (meta-data are up-to-date and structure is newly loaded).
    2. No blank segments are being created
    3. All segments have value 1 or blank (using blank works fine for me, that is when not trying to limit Segment version. But using 1 makes no difference)
    Best Regards,
    Daniel

  • Receiver IDOC adapter - IDOC_ADAPTER" ATTRIBUTE_IDOC_METADATA

    Scenario:
    EDI (Sender File adapter)-->PI7.11-(Receiver IDOC adapter)---->ECC
    I'm getting an error (below) at the Call Adapter stage:
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error SOAP:mustUnderstand="" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <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:Stack>Error: I::000</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Then I went to IDX2 and deleted the IDOC (in this case, ORDERS05) and tried to create the IDOC again, but I get a pop up window with
    I::000
    and thus the IDOC can't get recreated.
    Need to mention that both PI and ECC enviroments that I'm working in are sandboxes (XS1400 and RS1400) that are copies of our Development environment (XD1400 and RD1400).
    Can someone please shed some light?

    Hi,
    Addition to the above
    Check the port name you are mentioned in the receiver idoc adapter it should not be with client no...
    it should be only SAPSID..(SID is your system name..)
    HTH
    Rajesh

  • Monitoring receiver idoc communication channel

    Hi All
    I have an idoc to idoc scenario.
    I am unable to see my receiving idoc communication channel in communication channel monitoring of RWB. It is not available in the dropdown list.
    I want to have a look at the audit log to see if the idoc is delivered to the receiving system.
    How can i monitor receiver idoc communication channel?
    How can i ensure that the idoc is delivered to the receiving system?
    In sxmb_moni, status is checkered flag.
    Many Thanks
    Chandra Sekhar

    Hi,
    IDOC is on ABAP stack hence u can not monitor IDOC.
    For testing purpose
    1) GO to SXMB_MONI check the status of message.
    2) Go to R3 and enter Tcode WE02 and check the IDOC which is send from XI. enter the idoc name and see the status of IDOC it should be in green status if it is posted successful or else see the status record for checking the error message.
    chirag

Maybe you are looking for