Error RFC Idoc Inbound: Message E0(285)

This is a message into trx SM21:
While reading the first record to process the input file  IDoc & & v1, there was an error.
Check the file & & v1.
Also check the meter protocol that allows the state of processing the file in question. The error may in fact be
due to an inconsistency of the counter.
What is the problem?
What is the inconsistency of the counter ?
Thanks.
Unga00

Hi,
I think you are trying to make it as an R/3 system connection. The 3rd party programs should be connected as TCP/IP connection. This function module will be looked upon in SAP systems for ALE. Please check.
Cheers
Suresh

Similar Messages

  • Error in IDOC processing - Message no. VU 014

    Hi All,
    I got error while processing IDOC manually as:
    " Incompletion: Vendor : Account number of vendor or creditor (VBPA -LIFNR ), error group: 08"
    Details of Error message are as below:
    Message no. VU 014
    Diagnosis: The incompletion check reveals, for analysis purposes, any incomplete documents.
    The message contains:
    1. A description of the incomplete document
    2. A technical entry, telling you which table field has been checked
    3. A the error groups in the transaction from Customizing for Incompletion Log.
    Procedure
    One solution is to deliver the affected document in the screen (Create delivery with reference to order), and to edit and save the delivery following the menu path: Edit -> Incompletion.
    In certain circumstances, you can change Customizing so that
    the checked field is no longer assigned to the error group
    or
    assign another error group to the document type /item category
    or
    permit the delivery as a subsequent function.
    I am confused about what could be the root cause of the error and how to solve it.
    The Important thing is, when IDoc is run in Automatically(batch run), then it is successful with no any error but it gives this error when i run it manually.
    Pl. guide me to solve this problem.
    Thanks,
    Jai.

    Hi Bernd,
    Thank you for your mail.
    The Note 991410 is related to the IDoc status 53. I stucked with the IDoc status 51.
    IDoc error message is in status 51. But still I am looking all other alternative inculding one you suggested.
    Thanks you very much.
    Jai.

  • Error in IDOC-inbound processing

    HI All,
    while Posting a IDOC in Batch , i am getting an
    errot Status - 51. The Error Message is Field LFA1-SPERQ . is not an input field.But While Processing in
    WE19 i am able to Load it.
    Regards,
    Hazam

    Hi,
    Go thru this links
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400365
    http://www.thespot4sap.com/Articles/SAP_ALE_IDOCS.asp
    Check whether you are using exact  FM.
    Thanks
    Sunil

  • Error receiving AS2 message from partner: B2B-50037:  B2B inbound message processing error

    B2B/SOA 11.1.1.6.0
    We are setting a new trading partner and when we started document transmissions we are getting errors on the inbound messages: B2B-50037:  B2B inbound message processing error.
    The attachment shows the relevant lines from the soa log and diagnostic log files.  Here is the error detail that shows:
    [URI: /b2b/httpreceiver] Error -:  B2B-50037:  B2B inbound message processing error[[
    Error -:  B2B-50037:  B2B inbound message processing error
            at oracle.tip.b2b.engine.Engine.processIncomingMessageImpl(Engine.java:3143)
            at oracle.tip.b2b.engine.Engine.processIncomingMessage(Engine.java:1650)
            at oracle.tip.b2b.transport.InterfaceListener.onMessageLocal(InterfaceListener.java:403)
            at oracle.tip.b2b.transport.InterfaceListener.onMessage(InterfaceListener.java:214)
            at oracle.tip.b2b.transport.basic.TransportServlet.doPost(TransportServlet.java:754)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
            at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
            at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
            at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
            at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
            at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
            at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
            at java.security.AccessController.doPrivileged(Native Method)
            at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
            at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
            at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
            at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
            at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
            at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
            at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
            at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
            at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
            at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
            at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
            at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
            at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
            at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
            at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
            at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
            at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    From the b2b_wire_message we get these Protocol_Transport_BINDINGS:
    ChannelName=TransportServlet
    Reverse-Via=LIN-ISA1
    AS2-To=accobra.....
    Date=Fri, 26 Sep 2014 05:46:17 +0000
    AS2-Version=1.2
    AS2-From=K.......
    Disposition-Notification-Options=signed-receipt-protocol=optional, pkcs7-signature; signed-receipt-micalg=optional, sha1
    Disposition-Notification-To=http://<ip&port>/as2in
    Message-ID=<[email protected]>
    MSG_RECEIVED_TIME=Fri Sep 26 00:46:17 CDT 2014
    ECID-Context=1.0050z5j^buc6yGn6wnZf6G0002f60007bt;kXjE1ZDLIPGIj2QCYV8QoKSSmLRO_PQT_IS
    Content-Type=application/pkcs7-mime; smime-type=enveloped-data; name=smime.p7m
    Proxy-Client-IP=172.17.25.101
    MIME-Version=1.0
    User-Agent=e-integration AS2 Server V 6.1.8
    X-Forwarded-For=172.17.25.101
    Content-Length=3602
    Host=nalinsoa05.abd.ad.acco.com
    x-weblogic-cluster-hash=QoZzGUzdcjBD5fGIE8Uos5abiHI
    EDIINT-Features=multiple-attachments, CEM
    Connection=Keep-Alive
    X-WebLogic-KeepAliveSecs=30
    X-WebLogic-Request-ClusterInfo=true
    The message creates a wire message, business message, and an application message.
    What doesn't happen is no MDN gets sent back to the partner.  It should be a synchronous MDN.
    We have double checked the certificates on both ends and they are OK.
    The document and Agreement get recognized OK:
    Refer To Message
    Refer To Message
    Sender Type
    AS2 Identifier
    Sender Value
    K. . .
    Receiver Type
    AS2 Identifier
    Receiver Value
    accobr. . .
    Sender
    K. . . l
    Receiver
    ACCO . . .
    Agreement Id
    K. . .l_EDI_X12_4010_856_856Def_Inbound
    Agreement
    K. . .l_EDI_X12_4010_856_856Def_Inbound
    Document Type
    856
    Document Protocol
    EDI_X12
    Document Version
    4010
    Message Type
    REQ
    Direction
    INBOUND
    State
    MSG_ERROR
    Acknowledgement Mode
    SYNC
    Response Mode
    ASYNC
    Send Time Stamp
    09/26/2014 12:46:17 AM
    Receive Time Stamp
    09/26/2014 12:46:17 AM
    The error is vague enough to provide little or no help in locating the root cause of the issue.
    Any assistance in providing information on how to get this working would be greatly appreciated.
    We do have dozens of other AS2 partners working in this instance just foe reference.  We are just having issues with this new partner setup.
    Thank you.
    Regards,
    Ken

    Ken,
    I am observing the Ack Mode is set as "SYNC" . This is selected by default. This option is available in the channel configuration section
    If the usecase is not SYNC, please change as ASYNC and test. It should work.

  • Error while trying to post inbound idoc of message type COND_A

    Hi,
    I am getting error while trying to post inbound idoc of message type COND_A.
    If I left Usage & Condition field of segment E1KOMG then 'Table not available' idoc message is coming
    and if providing value in above fields then dump is coming.
    How to solve ?
    Plz do reply
    Thanks
    Mohit

    I do not see any reason why you would need to use COND_A04  if COND_A01 is working.
    What if you could get COND_A04 to post and you would face the same result as in COND_A01?
    If SAP does not check wrong values, then you have to do it yourself, or you report an incident at SAP (after you have searched for OSS notes that may have fixed this error already)
    For example OSS Note 1169998 - IDoc: KONP-LIFNR values not checked
    fixed a situation where the vendor number was not validated.

  • Error in IDOC creation of Inbound Delivery (VL31N) with  Error Message Number VL561

    H,
      I'm getting an error message when generating a test IDOC of Message type DESADV and IDOC type DELVRY03 to create Inbound delivery with reference to a standard purchase order.
    Essential transfer parameters are missing in record: PO Number and Item
    Could you one help me out in solving this.
    Thanks,
    Raj

    Hi ,
    Goto SM13 .
    Find the terminations based on user and creation date.
    Get the same analysed by ur ABAP team.
    Also check the confirmations in PO at Item level.
    Regards
    Ramesh Ch

  • 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

  • BD87 idoc inbound error for message type HRMD_A

    Hello there,
    I am getting below error  while fetching Inbound idoc in tcode BD87, see log below from ST22
    Short text
        An SQL error occurred when executing Native SQL.
    What happened?
        The error "-10328" occurred in the current database connection "LCA".
    What can you do?
        Note down which actions and inputs caused the error.
        To process the problem further, contact you SAP system
        administrator.
        Using Transaction ST22 for ABAP Dump Analysis, you can look
        at and manage termination messages, and you can also
        keep them for a long time.
    How to correct the error
        Database error text........: "Mismatch of number of stream members for
         parameter (3) (application 6, database 9)."
        Database error code........: "-10328"
        Triggering SQL statement...: "EXECUTE PROCEDURE "SIM_SIMSESSION_CONTROL""
        Internal call code.........: "[DBDS/NEW DSQL]"
        Please check the entries in the system log (Transaction SM21).
        If the error occures in a non-modified SAP program, you may be able to
        find an interim solution in an SAP Note.
        If you have access to SAP Notes, carry out a search with the following
        keywords:
        "DBIF_DSQL2_SQL_ERROR" "CX_SY_NATIVE_SQL_ERROR"
        "/SAPAPO/SAPLOM_CORE" or "/SAPAPO/LOM_COREU07"
        "SIMSCTRL_EXEC_COM"
        If you cannot solve the problem yourself and want to send an error
        notification to SAP, include the following information:
        1. The description of the current problem (short dump)
           To save the description, choose "System->List->Save->Local File
        (Unconverted)".
        2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
    The exception must either be prevented, caught within proedure
    "SIMSCTRL_EXEC_COM" "(FORM)", or its possible occurrence must be declared in
    the
    Do we need SAP_APO in order to install LiveCache?
    We have below landsacpe
    - SAP ECC 6 EHP4 with SQL server 2005 S BACKEND
    -LCAPPS Component release 2005_700 with SP
    SAPKIBHD05.
    - We dont have SAP_APO component
    -SAP LiveCache system have MAXDB 7.7.04.29 as backend.
    - Live cache client is installed on same SAP ECC system where we have SAP ECC EHP4 system.
    any suggestion how to resolve it?
    Mani

    >
    Mani wrote:
    > I installed a standalone server and i need it only for SAP HR (specifically Idoc processing in SAP HR Human capital management module). But i am getting error while running ibound idoc process.
    > So Do i still need SAP_APO component?
    I never heard of this specific scenario for liveCache usage in the past 7 years working in SAP support on the liveCache component.
    Might be useful if you provide some more details (documentation, notes, links) that describe this usage scenario.
    In any case you will need to have a liveCache version that is compatible to your application ABAP coding.
    The error message you posted indicates that your liveCache version does not fit your application version (or vice versa).
    > I installed SAP MAxDB and LiveCache buid using Installation master DVD for SAP ERP. So i think i followed the right method as specified in installation guide.
    Be precise, please. Which installation guide? There are hundreds of them - not THE installation guide.
    > Secondly can you help me something specific to my problem in coding form?
    Already did.
    > i tried in LC10, using LCA monitoring i am not able to run SQLDBC trace under
    > LCA >> LiveCache Monitoring >> Tools
    > but i am not able to execute the same, is it a error or we need to configure something?
    Well, the liveCache needs to be integrated into the LC10. You'd do this in transaction SM59 - but as you've followed an installation guide, this would have been covered in it...
    > Operational status is active green light, below is file status.
    >
    >
    KNLMSG     KnlMsg     1.098.697     28.01.2011     06:59:55     Database Messages     ASCII
    > KNLMSGARC     KnlMsgArchive     8.192     28.01.2011     06:59:50     Database Errors     ASCII
    > KNLMSGOLD     KnlMsg.old     342.663     28.01.2011     06:59:50     Database Messages (OLD)     ASCII
    > KNLTRC     knltrace     6.209.536     28.01.2011     06:59:56     Database Trace (Raw/Binary)     BINARY
    > BACKHIST     dbm.knl     570     10.01.2011     06:18:41     Backup History     ASCII
    > DBMPRT     dbm.prt     133.843     29.01.2011     11:41:27     Database Manager Log File     ASCII
    > DBMPAHI     L00.pah     214.225     10.01.2011     06:18:16     Database Parameter History     ASCII
    > LCINIT     lcinit.log     15.299     28.01.2011     07:00:00     LiveCache Initialisation     ASCII
    > LCINITCMD     lcinit.bat     3.047     28.10.2008     14:45:51     LiveCache Initialisation Script     ASCII
    > LCINITHIS     lcinit.his     46.742     28.01.2011     07:00:00     LiveCache Initialisation History     ASCII
    > INSTPRT     dbm.ins     863.981     10.01.2011     06:18:47     Installation Log File     ASCII
    > DIAGDIR     File     0     10.01.2011     06:18:18     Diagnose History     DIRECTORY
    > ANALYZER     analyzer     0     29.01.2011     00:00:36     DB Analyzer File     DIRECTORY
    > LCTRC#init.his     lcinit.his     46.742     28.01.2011     07:00:00     LiveCache Trace (ASCII)     ASCII
    > LCTRC#init.log     lcinit.log     15.299     28.01.2011     07:00:00     LiveCache Trace (ASCII)     ASCII
    > LCTRC#_apo_version.txt     lc_apo_version.txt     164     28.01.2011     07:00:00     LiveCache Trace (ASCII)     ASCII
    >
    > any clue whats wrong?
    > Mani
    The only thing this tells us is: the liveCache instance itself apparently comes up and writes out the standard log files.
    That's it.
    As I already tried to explain, the problem seems to be the dependence between your application and the liveCache version.
    Usually I'd recommend to open a support message for this, but the colleagues would (hopefully) ask the same questions as I did.
    regards,
    Lars

  • Workflow Ends in Error " No auth to send IDocs with message type ORDRSP"

    Hello All,
    I have created an RFC user with limited Authoprizations including WE* tciodes and a few ME* transactons for an ALE Set up. I want to make sure i would not be giving more authorizations (extensive) to this RFC user and assign Just required authorizations. So i started testing testing and the inbound IDOC ended in error with a message " No auth to send IDocs with message type ORDRSP" Message no. SR053. Is there any way to find out what is the missing authorization object for the User. Any inputs would be really apprecaited.
    Br,
    Sri

    Hi !
    Becaus alle this happens in beckgound, things are a bit difficult but solvable....
    What you should do is a "Authority trace" ... as follows....:
      - Go to the ST01
      - Mark "Authorisation Check"
      - Swich the trace on for your Workflow user
      - Execute the Workflow until the error uccurs
      - Go back to the ST01
      - Press the "Analyze" button and see what error occurs
    Dont forget to swicht the trace off... otherwise the tracefiles become realle BIG !
    Regards
    rainer
    Some Reward poins would be nice if that helped....

  • IDoc to Soap, with BPM - Permanent error in BPE inbound processing

    Hi Experts,
    IDoc to Soap, with BPM - > Permanent error in BPE inbound processing
    How to rectify this any issue???
    Thanks-
    sk

    Hi,
    The inbound processing encountered a permanent error and the queue therefore stopped.
    The error message "Permanent error in BPE inbound processing" may be caused by the following:
    - At the start or when you process a process instance, the inbound processing encounters an exception that was not handled. This exception is triggered, for example, by a transformation step, a synchronous send step or a control step but it was not caught in an exception handler branch. If the exception that was not handled occurs in the first transaction of the started process instance, the system does not write the process instance to the database but it sets the queue that has this error message to the error status.
    Refer to the help in Note 1082099
    - The inbound processing triggers this error if the correlation evaluation shows that a message should be delivered to a process instance that has the status "error". Since delivery to process instances that contain errors is not permitted, the queue is stopped.
    Use the simulation of the message delivery in the detail view of the relevant queue LUW to determine the relevant process instance for the affected message and use transaction SXMB_MONI_BPE "Continue Process Following Error" (or transaction SWF_XI_SWPR) to continue. If you cannot continue the process instance, check whether you can logically delete the instance. In this case, use the method that is described in Note 807906 to logically delete a process instance.
    Check whether your system contains other process instances that have errors in order to detect similar problems. Use transaction SXMB_MONI_BPE "Continue Process Following Error" or transaction SWF_XI_SWPR.
    Use the report RSWF_CRL_MAINTAIN to check all of the correlation instances in question or the relevant process instances that you can reach using "Display Work Item".
    - Messages that cannot be delivered because no correlation instance can be found may lead to the error that is mentioned here. Check whether the causes that are outlined in Note 1094028 affect your case.
    Hope this will help you.
    Regards
    Aashish Sinha
    PS : reward points if helpful.

  • Inbound Processing of iDoc Status Message

    Silly me - I thought this would be simple ...
    I am currently changing our bank interface from a customized ABAP solution to use more standard SAP utilities (particularly iDocs).  I have the configuration set up to use the PAYEXT message type sending PEXR2002 iDocs to a file port.  Our bank is receiving these documents and is returning an iDoc status message containing the status of each payment iDoc that they received from us.
    My problem is that I can't figure out how to get these status iDocs to update the status of the corresponding PEXR2002 iDoc.
    I am trying to execute an RFC interface to apply these status messages to my system using the following OS command:
    D:\usr\sap\VPR\SYS\exe\uc\NTAMD64\startrfc.exe -3 -d RT2 -u xxxxxx -p xxxxxx -c 220 -h SPR32K36 -s 00 -F EDI_STATUS_INCOMING -E PORT=ZFI_INT003
    The error message that I receive when this is run is:
    RFC Call/Exception: SYSTEM_FAILURE
    Group             Error Group 104
    Key                RFC_ERROR_SYSTEM_FAILURE
    Message        Status record 1 is invalid (TABNAM: 'EDI_DC40')
    The port (ZFI_INT003) is the file port that is configured for the outbound file.  in WE20, this port has the "Status File" tab set to use the logical file name where the status file is being stored on the server.  the startrfc command is connecting to the SAP system and opening the status file.  I'm not sure where I'm going wrong here. 
    Can someone please help get me pointed in the right direction?  I've obviously missed something here.
    Thanks,
    Glen

    Hi,
    call function modules:
    EDI_DOCUMENT_OPEN_FOR_PROCESS
       EDI_DOCUMENT_STATUS_SET
       EDI_DOCUMENT_CLOSE_PROCESS
    kind regards,
    HP

  • Error : No authorization to send IDocs with message type MATMAS

    Hi All,
    My scenario is FILE-XI-IDOC.
    I am getting chequered flag in SXMB_MONI,but in that under outbound status I am getting red flag.
    When I check in SM58 I am getting message as "No authorization to send IDocs with message type MATMAS".
    Do I need to give any authorizations on XI side or on R/3 side?
    If so, what is the authorization required?
    I could not find the note :837595.

    <i>You use the IDoc Adapter in the Exchange Infrastructure and you try to use the IDocs to receive or send data. For these IDocs, an attempt is made to load the IDoc metadata from an R/3 reference system with an SAP NetWeaver Release lower than 6.20.
    This occurs either at runtime, whereby the relevant messages run into 'System error' status, or when you use transaction IDX2 during manual loading of the metadata. In this case, the reference ystem is called by RFC and the logon user of the RFC destination does not have the necessary authorizations for determining the metadata.
    Solution
    In transaction PFCG, extend the role of the logon user by adding the following authorizations:
    Authorization object S_RFC
          Field name RFC_TYPE value FUGR
          Field name RFC_NAME value EDIMEXT, SDTX
          Field name ACTVT    value 16
    Authorization object S_IDOCDEFT
          Field name ACTVT  value 03
          Field name EDI_CIM value ' '
          Field name EDI_DOC value TXTRAW01
          Field name EDI_TCD value WE30
    Authorization object S_CTS_ADMI
          Field name CTS_ADMFCT  value TABL
    Authorization object S_TABU_DIS
          Field name ACTVT      value 03
          Field name DICBERCLS  value</i>
    from the note mentioned above.
    Regards
    Bhavesh

  • IDOC inbound Posting Error no 51

    Hi Friends,
      I am triggering Inbound error using XI.
    I am getting Error no 51(Application document notposted), when i am checking in WE05.
    Can any one guide me how to trace further error???
    Cause of Error????
    If data is incorrect in IDOC how can i check, that error is due which field record????
    Please guide me and give some T.Codes to trace error in inbound IDOCs
    Thanks & Regards
    Umesh

    the hint with the status record is correct: If you double-click it, you may have a button 'application log' - but only if the inbound processing creates a log.
    SAP knows thousands of IDOC basic types, message types, process codes and almost nothing is handled the same way.
    So first get the details about Idoc and message types, find out how the inbound IDOC is processed, get the function modules name, use the debugger to see where what error is issued.
    You may also have a look at the IDOC's segments contents and see if some data is obviously wrong.
    Or just tell the readers here what business process you try to handle using what IDOC - experience may be just one click away.
    regards,
    Clemens

  • Error importing RFC / idoc despite following note 769356

    We have been experiencing a number of problems where we cannot import RFC / idocs in the integration repository.  The BASIS team have followed note 769356 and originally this solved the problem but meant that we reverted back to old screens in the Integration Builder and some German texts in the Integration Repository.
    Current patch version is Support Stack 4
    To get to this point the following steps were followed:
    Undeployed com.sap.xi.repository
    Deployed the install version of com.sap.xi.repository.
    In order to correct the problems with the incorrect screens etc.. The following steps were carried out:
    Undeployed com.sap.xi.repository
    Deployed the Support Stack 4 version of XITOOLS (includes com.sap.xi.repository)
    Applied Support Stack 5 for the Abap kernel
    Applied SAPXIAFC04P_1-20000272 and SAPXITOOL04P_1-20000274 via SDM
    This fixed all of the problems with German texts etc.. but now we cannot import RFC / idocs again.  In the Java Web Start Log (attached) we still get the error message
    mentioned in note 769356.  We have deleted the Web Start Cache on the client hosts (several restarts of the machine and deletions of the cache).  The BASIS guys are going to undeploy and redeploy the repository again but failing that we are running out of ideas.
    Does anyone have any suggestions?
    Here is the entry in the log file:
    java.lang.AbstractMethodError: com.sap.aii.ibrep.sbeans.upload.UploadServiceRemote_Stub.openSAPSource(Lcom/sap/aii/utilxi/misc/r3Connect/SAPConnectionData;Lcom/sap/aii/utilxi/misc/r3Connect/SAPLoginData;Lcom/sap/aii/ib/bom/gen/VersionContext;)Lcom/sap/aii/ibrep/sbeans/upload/SourceID;at com.sap.aii.ibrep.clsif.upload.RemoteUploadClient$ConnectionImpl.connectBean(RemoteUploadClient.java:107)at com.sap.aii.ibrep.clsif.upload.RemoteUploadClient$ConnectionImpl.<init>(RemoteUploadClient.java:91)at com.sap.aii.ibrep.clsif.upload.RemoteUploadClient.getSAPUploadConnection(RemoteUploadClient.java:66)at com.sap.aii.ibrep.gui.tools.r3import.wizard.SAPLogonPage.connect(SAPLogonPage.java:94)at com.sap.aii.ibrep.gui.tools.r3import.wizard.R3ImportWizard$LoginTask.run(R3ImportWizard.java:456)at com.sap.aii.utilxi.misc.thread.ThreadPool$ThreadPoolThread.run(ThreadPool.java:321)

    Dan,
    you are almost there!
    If you religiously follow note 769356, you should not have this problem.
    Just do the following as the note suggests:
    - From SDM, undeploy only the com.sap.xi.repository
    - Unzip SAPXITOOL04P_1-20000274.SCA.zip 
    - The file ExchangeRepository.sda will be one of the extracted files
    - Only import the ExchangeRepository.sda.  Do not import the entire ZIP package.
    - Restart the J2EE engine.
    - Delete Webstart Cache
    - From the XI admin page:
    http://XIhost:50000/rep/support/admin/status.html
    Re-Initialize the Jars for resigning.
    - Wait for 5 minutes for the jar signing to finish. Sometimes, the jar signing gets interrupted, you have to let it finish.
    The above steps worked for me.
    thanks,
    Manish

  • ERROR: "The IDoc interface is not complete for message type DELINF"

    Dear All,
    The ERROR happens when I use IDoc inbound test tool:
    -  Basic type used: DELVRY06         
    -  Basicallly this IDoc is supposed to create inbound PGI of a DO. I just put the DO number in WE19. 
    But ended up with the error mentioned. Let me know if oyu need more details.
    Thanks and regards,
    Will.

    Hi,
    Please check whether the partner profile configuration is done completely such as any message control parameters are fine or not.
    Regards
    Archanaa

Maybe you are looking for