Error In inbound Processing IDoc

Dear All,
I am facing error while inbound processing of IDoc
In status record of IDoc following errors are occuring
Status 60 : EDI: Syntax error in IDoc (mandatory segment missing)
The segment E1MAKTM has the attribute 'Mandatory' in the syntax description of the basic type MATMAS05 (customer enhancement ). However, the segment is missing in the IDoc
Status 51: Application Document not posted
Log details :
Error : Material Number should be filled.
When i checked IDoc all 4 fields in E1MAKTM have the values in inbound IDoc.
Please guide me how to resolve these issues so that IDoc will be posted and Material Master will get created in reciever system.
Thanks

Hi Praveen,
I checked the data in IDoc for this segment.
It is ok as required in basic message type.
e.g. the error says that mandetory segment E1MAKTM is missing.
when i check basic type
MSGFN : Function
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
SPRAS : Language Key
internal data type : LANG
Internal length : 000001 characters
Position in segment : 002, Offset : 0066. external length : 000001
MAKTX : Material Description (Short Text)
internal data type : CHAR
Internal length : 000040 characters
Position in segment : 003, Offset : 0067. external length : 000040
SPRAS_ISO : Language according to ISO 639
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 004, Offset : 0107. external length : 000002
is information.
and data in segment of IDoc is
MSGFN     005
SPRAS     E
MAKTX     MANATA2000 TEST ALE
SPRAS_ISO     EN
which i think is ok.
I have no clue why this syntax error is coming.
Thanks
Niketan

Similar Messages

  • Permanant Error in Inbound Processing in BPM

    Hi All,
    i have done a File1->JDBC(Synch)->File2 scenario using BPM.
    It works fine when i have data in input file ie File1. However when my input file empty my scenario shows green flag in "OutboundStatus" and in queue gives error "Permanant error in Inbound Processing".  When i tried to see the error in details got exception in START_PROCESS....
    After deleting this entry from queue and sending file with data it works fine.....
    I just want to know why it happens....? My input file can be empty as i am using it for triggering the scenario.
    Do i need to do any settings in BPM or scenario to handle this?
    Thanks,
    Atul

    hi atul,
    in the rec step where u set the start process check box, you give the message. it is this message that is used to start the BPM process and not ur input file... the input file is used to trigger ur scenario not ur process. therefore u have exception in 'start process'.
    hope it helps.
    regards,
    latika.

  • Error message when processing IDoc

    Hi there,
    Greetings from Buenos Aires, Argentina.
    I'm trying to use the Migration Workbench in order to transfer to SAP the material master data.
    I have created an LSMW Objet and selected, under Mantain Object Attributes >> Object Type and Import Method, the IDoc option. The message type will be MATMAS and the Basic Type will be MATMAS05.
    I have maitained the IDoc Inbound processing, created the LSMW Port and the Partner Profile. In the latter, under Inbound Parameteres, I have created and inbound parameter with the MATMAS Message Type and MATM Process Code.
    I have created structure relationships for the following target structures: EDI_DC40, E1MARAM, E1MAKTM, E1MARCM and E1BEWM.
    After being one or two couple of hours going and coming over the application log after running over and over again the step 14. IDoc Processing, and having filled with '/' the obligatory fields, I still am not able to generate it successfully.
    The problem I'm having is, it keeps asking the DISMM (I think the name is MRP Type) field, and since I have not created a conversion rule or source field for it, I recieve the error message 72 from the M3 message class
    I understand that though the MM01 transaction, if the MRP View isn't activated, this field stops being mandatory. So I need to know, if any, the way to make the IDoc processing not to ask this field, since the MM consultant has said it's not necessary to introduce it.
    Thanks in advance.

    in the step 5 Maintain Field Mapping and Conversion Rules
    in the strcture E1BPMATHEAD   put the below condtion
    E1BPMATHEAD                    Header Segment with Control Information
    for the MRP veiw  WERKS and DISMM is mandatory fileds if you are not getting the any one of the value from the file ,skip the MRP view using below condtion.
    MRP_VIEW                     Material Requirements Planning (MRP) View
                        Code:    * Target Field: E1BPMATHEAD-MRP_VIEW Material Requirements Plann
                                 IF NOT matmas-werks IS INITIAL AND "
                                    NOT matmas-dismm IS INITIAL.
                                   e1bpmathead-mrp_view ='X'.
                                 ENDIF.

  • Sending Inbound application log error in inbound processing through email

    Hello all,
    My client wants application log for failed idoc through E-mail.(The application log found in we05 for failed idocs).
    Please guide me how to get/fetch the error log in inbound processing.
    Thank you.
    Edited by: Sanjay_lnt on Feb 9, 2010 5:32 AM

    Hi,
    Query EDIDS table with the relevant selection criteria like date.
    Here field STATXT will give you the message text. REPLACE the place holders(&) with STAPA1, STAPA2, STAPA3 and STAPA4 to build the complete message.
    Make sure that you read the message for the latest counter(Check Max counter in field COUNTER). Because same IDOC can have multiple messages.
    Once you get the message, you can use normal mail sending code for sendingout the mails.
    Thanks,
    Vinod.
    Edited by: Vinod Vemuru on Feb 9, 2010 11:21 AM

  • Error in Inbound Customer IDOC (WE19)

    Hi All
    I am creating Inbound Customer IDOC
    Message Type : DEBMAS
    & FM : IDOC_INPUT_DEBITOR.
    But getting error(51) : "No batch input data for screen SAPMF02D 0340".
    According to previous threads, I have seen this screen for Mandatory fields but I didnt found any.
    Could anyone tell me what mandatory fields to enter in DEBMAS or  the Solution for this Error.
    Regards.

    Hi Nikhil I am getting this error which you got it before but this time I am getting it in LSMW when creating customer master screen."No batch input data for screen SAPMF02D 0340"
    what am i supposed to check?
    Can u plz send me ur mail ID.

  • Did you meet error AM840 when processing IDocs of BP?

    Hi,
    When I process IDocs of BP, there is a popup which said "Database error deleting from table ADRCOMC MessageNo:AM840". I have searched Notes, but no useful information founded.
    Do you know the cause of that error? How to solve it?
    Thanks!
    Best regards,
    Long

    hi,
    do you delete any address data for your business partner ?
    try to check address adata from you IDOC
    to see if it's correct
    you can send an IDOC from your BP and check
    if you populate the address data in the same way
    Regards,
    michal

  • Did you meet error AM840 when processing IDocs?

    Hi,
    When I process IDocs of BP, there is a popup which said "Database error deleting from table ADRCOMC MessageNo:AM840". I have searched Notes, but no useful information founded.
    Do you know the cause of that error? How to solve it?
    Thanks!
    Best regards,
    Long

    Hi Sudheer,
    Sorry, I made a mistake. You are right. The problem is because that some records of communication type are missing in table ADRCOMC.
    Then I firstly check if it has missing data, then do processing.
    Another question, currently when I usd Tcode: BD87 and select some IDocs when are not processed. If I click "Process" button, the program "RBDAPP01" should be executed and select the IDocs to be processed firstly. But at this step it often run exceed timeout. I looked at process via SM51 and found that when executing "Select * from BUT0TP...." statement, it needs very long time and then execeed timeout.  Do you know why?
    Thank you very much for your help!
    Best regards,
    Long

  • AS2 adapter error during inbound processing

    Hello,
    We have upgraded PI to version 7.1 and now we are testing the Seeburger AS2 adapter.
    We have received a testmessage from an AS2 partner and it is shown in the message monitoring of the Seeburger adapter workbench, with status succesfull.
    Only the message is not on the integration server. The message is not shown in sxmb_moni or the message monitor of the RWB.
    In the RWB the communication channel (CC_AS2_Sender) gives the following error:
    "Message inititiation failed: Processing error"
    The message itself gives the following error:
    "Inbound message processing failed! performing rollback
    Can anyone help us with this?
    Thanks in advance.
    Regards,
    Marco

    Hi Marco,
    the message is not forwarded to the intergration egine because there might be an error in your communication channel.
    Are there any other modules in the module chain of this communication channel?
    Can you check "default_trace" and "application_log" for exceptions (/j2ee/cluster/serverXX/log)?
    Did you also restart the Java Stack after the Upgrade?
    regards,
    Daniel
    Edited by: Daniel Rexter on Jun 30, 2010 2:59 PM

  • Error in inbound processing: EDI message - XML Gateway

    Hello!
    I've setup a DELFOR transaction in B2B and modified XML Gateway settings for internal delivery channel in order to send the message to EBS, but I'm getting weird errors in b2b.log. (XML Gateway in EBS is not setup yet, but it should't be an issue since incoming errors are handled in EBS, and I would just see an inbound transaction with processing errors in Transaction Monitor.)
    In the beginning of b2b.log I see this:
    2009.07.07 at 15:26:31:897: B2BStarter thread: BusinessLogicLayer - (DEBUG) Push Stack: queryInternalDeliveryChannel
    2009.07.07 at 15:26:31:897: B2BStarter thread: BusinessLogicLayer - (DEBUG) Pop Stack: queryInternalDeliveryChannel
    2009.07.07 at 15:26:31:897: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:31 CEST 2009 inbound initialize
    2009.07.07 at 15:26:31:897: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:31 CEST 2009 Obtaining inbound connection...
    2009.07.07 at 15:26:31:897: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:31 CEST 2009 inbound connect string: jdbc:oracle:thin:@server64.xa.si:1521:test2
    2009.07.07 at 15:26:31:897: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:31 CEST 2009 inbound username: apps
    2009.07.07 at 15:26:32:522: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:32 CEST 2009 inbound initialize exit
    2009.07.07 at 15:26:32:522: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:startListen Enter
    2009.07.07 at 15:26:32:538: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:startListen Exit
    2009.07.07 at 15:26:32:538: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:run Thread start
    2009.07.07 at 15:26:32:538: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:initialize Exit
    2009.07.07 at 15:26:32:538: B2BStarter thread: B2B - (DEBUG) B2BStarter - B2B initialized
    After I copy the edi file to the incoming directory B2B starts processing the file:
    2009.07.07 at 15:30:01:878: Thread-10: B2B - (DEBUG)
    Protocol = File
    Version = 1.0
    Transport Header
    filename:00003442_23.CMS
    filesize:12345
    file_ext:CMS
    fullpath:C:\xa_endpoint\00003442_23.CMS
    timestamp:2009-07-06T16:14:29.393+01:00
    As I see in the log: B2B finds the trading partner and agreement and all looks fine. But later comes this:
    2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:deliverMessageToDestination Enter
    2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:deliverMessageToDestination deliver message to destination. protocol is XMLGateway Queues
    2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:deliverMessageToDestination deliver message to XMLGW
    2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : Tue Jul 07 15:30:05 CEST 2009 Converting B2B message to ECX message..
    2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : Tue Jul 07 15:30:05 CEST 2009 Inbound - B2BtoECX - Enter
    2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : Tue Jul 07 15:30:05 CEST 2009 B2B Message -
    2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : COLLABORATION_NAME : null
    2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : ACTION_NAME : DELFOR
    2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : DOCUMENT_TYPE : DELFOR
    2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : DOCUMENT_TYPE_REVISION : D97A
    2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : SOURCE_NAME : tpartner
    2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : DESTINATION_NAME : Xa d.d.
    2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : PAYLOAD : UNB+UNOA.............. edi message continues here
    2009.07.07 at 15:30:05:925: Thread-9: B2B - (DEBUG) : PAYLOAD : <?xml version="1.0" ?><Transaction-DELFOR............... xml continues here
    2009.07.07 at 15:30:05:925: Thread-9: B2B - (DEBUG) : Tue Jul 07 15:30:05 CEST 2009 ECX Message -
    2009.07.07 at 15:30:05:925: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:handleAppMessageRetry Could not deliver the message; exception message is null
    2009.07.07 at 15:30:05:925: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:handleAppMessageRetry No application side retry
    2009.07.07 at 15:30:06:081: Thread-9: B2B - (ERROR) Error -: AIP-50903: Message "0A14011912255682A58000003257C600-1" retry count is zero
         at oracle.tip.adapter.b2b.msgproc.MessageHandler.handleAppMessageRetry(MessageHandler.java:394)
         at oracle.tip.adapter.b2b.msgproc.MessageHandler.deliverMessageToDestination(MessageHandler.java:344)
         at oracle.tip.adapter.b2b.msgproc.Request.putMsg(Request.java:657)
         at oracle.tip.adapter.b2b.msgproc.Request.continueRequest(Request.java:481)
         at oracle.tip.adapter.b2b.msgproc.Request.incomingRequest(Request.java:410)
         at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:2062)
         at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2574)
         at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2444)
         at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2399)
         at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:527)
         at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:374)
         at java.lang.Thread.run(Thread.java:534)
    Last message repeats once more and then:
    2009.07.07 at 15:30:06:081: Thread-9: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
    2009.07.07 at 15:30:06:081: Thread-9: BusinessLogicLayer - (DEBUG) Push Stack: updateBusinessMessage
    2009.07.07 at 15:30:06:096: Thread-9: BusinessLogicLayer - (DEBUG) Pop Stack: updateBusinessMessage
    2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:updateMsgError(3 params) Exit
    2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) DBContext commit: Enter
    2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) DBContext commit: Transaction.commit()
    2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) DBContext commit: Leave
    2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:deliverMessageToDestination Exit
    2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:incomingRequest Exit
    2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: processIncomingMessage setting seq numbers
    2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Call Incoming Request Processor
    2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:incomingRequest Enter
    2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:incomingRequest TransportBindings created
    2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:incomingRequest Create a Message Table Row for Request message with message state Continue Processing
    2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow Enter
    2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
    2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Push Stack: queryExchangeProtocolRevision
    2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Pop Stack: queryExchangeProtocolRevision
    2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
    2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Push Stack: queryDocumentProtocolRevision
    2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Pop Stack: queryDocumentProtocolRevision
    2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (ERROR) Error -: AIP-13115: Not in an active transaction
         at oracle.tip.repos.core.persistency.BaseObject.prologue(BaseObject.java:1408)
         at oracle.tip.repos.core.persistency.BaseObject.createObject(BaseObject.java:913)
         at oracle.tip.model.instance.DataStorage.create(DataStorage.java:794)
         at oracle.tip.adapter.b2b.message.MessageStorage.create(MessageStorage.java:145)
         at oracle.tip.adapter.b2b.msgproc.DbAccess.insertMsgTblRow(DbAccess.java:953)
         at oracle.tip.adapter.b2b.msgproc.Request.incomingRequest(Request.java:397)
         at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:2062)
         at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2574)
         at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2444)
         at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2399)
         at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:527)
         at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:374)
         at java.lang.Thread.run(Thread.java:534)
    2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) setRuntimeActiveandQuiescing()
    2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage General Exception ERROR
    Error repeats a few times.
    Wire message stays in Processing status, Business message is errored and an exception message is created in ip_in_queue.
    Both remote and host delivery channels have retry set to 1. Agreement was re-deployed + all B2B restared, but the problem remained.
    Could anyone help with this? What could be wrong?
    Thanks in advance.
    Kind regards,
    Wanda
    PS. I've checked all threads that might have anything to do with this, but found nothing useful.

    Hi Anuj,
    thanks for taking the time to examine the file.
    Answers to your questions:
    1. Yes, this is the 1st time for B2B, but the EBS I'm trying to connect to is up and running for approx. 2 years (it's a test instance).
    2. Patching was done by the customer's sysadmin, so I don't really have an overview on what and how he did. Result of opatch:
    Installed Patch List:
    =====================
    1) Patch 8298731 applied on Sat Jun 13 09:23:42 CEST 2009
    2) Patch 5907304 applied on Thu Jul 17 14:26:55 CEST 2008
    3. In theory the sysadmin should have run it, but how could I double-check this?
    I know he had problems while applying patch 8298731, but he said it was solved later. (Customer is using windows os, which is making a lot of troubles otherwise.)
    Regarding IDC log there is no success. I've restared B2B at least 5 times plus once the database, but still nothing. In tip.properties:
    oracle.tip.adapter.b2b.transportTrace = C:\APPS\OAS\ip\log/transport.trc
    also I tried the following values:
    C:\\APPS\\OAS\\ip\\log/transport.trc (since there is a similar entry: oracle.tip.LogDirectory = C:\\APPS\\OAS\\ip\\log)
    C:\\\\\\\\\\\\\\\\APPS\\\\\\\\\\\\\\\\OAS\\\\\\\\\\\\\\\\ip\\\\\\\\\\\\\\\\log/transport.trc (this was commented before; maybe it comes from some default)
    true (I had no other idea)
    Result is the same for all the cases: b2b_idc_transport.log file is 0 bytes, but b2b_dc_transport.log has initial data+writes log when processing.
    If I remove or comment the above line from tip.properties, then no transport log files are created.
    I've updated the agreement to have B2B inbound for the internal delivery channel, re-deployed it and it worked fine -> transaction(s) appeared in IP_IN_QUEUE.
    Changing it back to XML Gateway (and re-deploying) causes all original problems.
    Regards,
    Wanda

  • Error in Inbound IDoc processing

    Hi all,
    While processing Inbound delivery IDocs(Status 64), we are getting an error "Cannot convert Dimensionless Units".
    Please help.
    Regards,
    SP.

    Hi Vijay,
    The IDoc is a Delivery IDoc. The OSS Note that you have sent is for a similar error but is related to APO systems and hence I don't think it is related.
    Has anyone encountered this error before...?
    It says 'Conversion of dimensionless units is not possible'....
    Regards,
    SP.

  • Error : Pre Settings for IDoc inbound processing are missing error

    Hi Experts,
    There is a CRM job which executes LSMW and I am facing a strange problem during the IDOC posting the error "Pre Settings for IDoc inbound processing are missing error". Can anyone please tell me how to correct this error?
    Thanks in advance.
    Madhurima.

    I'd start with the following document, with one modification. At step 12 after typing GEARAspiWDM press the Enter/Return key once prior to clicking OK. (Pressing Return adds a carriage return in the field and is important.)
    [iTunes for Windows: "Registry settings" warning when opening iTunes|http://support.apple.com/kb/TS3299]

  • 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.

  • Error in re-processing inbound idocs of status 51

    Hi
    We are facing problems in reprocessing inbound idoc from BD87 transaction
    We have an inbound process code 'STA1' which is pointing to a standard task 'TS30000206'.  we have an errored inbound idoc(status 51) of message type 'STATUS' ( standard status change idoc pointing to process code STA1 for a valid port. Whenever we try to process it using BD87 transaction, we are getting errors B1033-'No function module for input process code STA1'.
    We dont understand what we were missing. When we try the same for a process code which points to a function module, BD87 reprocesses it correctly.
    We tried adding an entry in BD67 with an inbound function module 'APPL_IDOC_INPUT1'. Note that we still had the process code pointing to the same task. This time BD87 reprocessed idoc, but gave 51 again saying that 'Function module not allowed: APPL_IDOC_INPUT1'.
    Any pointers or help in this regard will be highly appreciated.

    Hi,
            Please check IDOC TYPE, MESSAGE TYPE & PROCESS CODE  and also check the we30, we42. & try BD87 reprocess of an IDOC.

  • IDOCs - create new inbound process code   Error

    Hi
    Regarding Zprocess Code in WE42..
    Que-1
    I have already mainted in BD51 . then
    In we42 , When I provide the Zprocess Code and Enter , the following mesages/information I am getting-
    -> The ALE table is not yet maintained for process code ZPUR !
    -> For entry, access 'Function module for ALE-EDI inbound processing'
    Ques-2
    When I was proving OBJECT TYPE : blank  , I was getting the error as " APPLICATION OBJECT TYPE  is not planned ".
    Does it means to maintain anywhere..?
    Please help in this regard.
    Thanks
    Kalpesh

    Hi KALPESH,
    check the below things and try..
    Process code <give ur zprocess code>
    Description test
    Identification <give ur functionmodule>
    Option ALE
    click on radio button Processing with ALE service
    processing type
    click on radio button Processing by function module
    Now press enter button,now u will get transport request,create the transport request nad then u will get the information message
    'Function module for ALE-EDI inbound processing'.Now press enter ,
    u will get a new screen..now from the drop down list select ur zfucnction module..
    give the application object and press on save button..
    now ur zprocess code will be created.
    HOPE THIS HELPS

  • Error while creating inbound process code

    Hi gurus,Iam creating a custom idoc.
    800 -> sender
    810 -> Receiver
    i have completed outbound processing on 800.
    On 810, completed following steps for inbound processing.
    1.) I have added my Inbound FM in BD51.
    2 ) Assigned my FM to Message type and Idoc type in WE57.
    3 ) When adding my FM to process code in BD67, it is showing error that
    “Entry ZSATPC does not exist in TEDE2 - check your entry”.
    { zsatpc is my custom process code }.
    4) While Creating Process Code in WE42 with options [processing with ale service / Processing
    by FM] and saving it is giving error that
    " " is not a valid language.
    And when I saw help (?) regarding this error, the following text appeared in a window.
    Diagnosis
    A key with language "" "" was specified for table "EDE2T". This is not a valid language.
    This applies to field "LANGUA"
    System Response
    The system rejects the key.
    Procedure
    Enter a valid language. This is usually the language you logged on in.
    You logged on in language "EN".
    Table T002 contains a list of valid languages.
    Please solve this error. Give me steps to create inbound process code.
    thanx in advance. Hoping replies soon........
    Satish.

    Dear Satish,
    Very peculiar. The language should come from your log on language. Try to login into the system again. Call we42 again and see if it works.
    Regards, Rakesh

Maybe you are looking for