IDOC Error handling using workflow for Inbound process.

I have a custom idoc which I am processing using a custom inbound function module with the help of a custom process code. I have made the config in BD51/bd67/We42/We57and doing the coding in the inbound function module to handle workflow. But i am still unable to get the workflow item in my inbox. I have set my userid in the partner profile as the agent to receieve the workflow.
Is there any other config that needs to be done vis-a-vis workflow ? like..assignement of some standard task,etc etc ? The message type I am using for the IDoc is zWMMBXY .
Pls advice..thanks

Seetha,
I have this already..
IDOCPACKET                                                           
Object type                         IDPKWMMBXY             
End event                           MASSINPUTFINISHED      
IDOC                                                          
Object type                         IDOCWMMBXY             
Start event                         INPUTERROROCCURRED     
End event                           INPUTFINISHED          
Application object                                                                      
Object type                         BUS2017                           
Start event

Similar Messages

  • IDoc error handling using workflows

    Hi,
    I have a requirement to generate IDocs in the Source system and process them in the target system. The IDoc message type is HRMD_ABA. And I am using standard processes to generate them and post them using PFAL and RBDAPP01 program respectively.
    All this is working fine. But now I need to include error handling in the source and the target systems which would send mails to a User's Outlook mailbox whenever there is an error. I mean to say, we need more functionality than just monitor them through WE05 transaction.
    Can any one tell me how this can be achieved. I have been looking into the program RSEIDOCA which would send workflows to SAP Inbox, but I need to send it to Outlook Inbox.
    And I have heard that there is a workflow process which would help me to do this.
    All your answers would be highly appreciated.
    Thank you in advance,
    Sid.

    Hi,
    First Step:
    You have to maintain the e-mail-address in SU01 for required users.
    Second Step:
    SCOT Configuration
    Third Step:
    Depends on your SAP Version do configuration SWNADMIN
    Or  excuting the report RSWUWFML2 as the background job.
    Thanks and Regards,
    Prabhakar Dharmala

  • OUTBOUND- ERROR HANDLING USING WORKFLOW

    Hi Gurus,
                   Can any one tell me about workflow & how to do error handling using WORKFLOW in OUTBOUND IDOC.Below are the points , Please check it & send me reply.
    1.Value not found for Custom IDoc fields.
    2. Partner Profile not maintained correctly.
    3. Syntax error in IDoc.
    4. IDoc ready for dispatch (ALE Service).
    Regards,
    Chiranjeevi.

    Hi,
    FOr most of your requirements, there is already std. SAP IDOC error Single-step tasks.
    Have a look at WE46 transaction.
    Also, if you go to SWO1 and search with "IDOC*", you will get all the BO's even.
    It's pretty straightfwd. Also, in Partner Profiles, WE20, for each of the IDOC type, there is one "Post.Processing AGent", whom if you set up correctly, will be the person receiving this Errored IDOC mails.
    Hope this helps
    venu

  • Outbound Idoc error handling through workflow

    Hi,
    I am trying to set up the workflow for outbound error handling. I found that there is a task TS00007989 which need to set up.
    How this task can be triggered when outbound idoc error occurs in the system?
    Kr,
    Vithalprasad
    Edited by: Vittalprasad on Jun 9, 2010 11:52 AM

    Hi,
          Have a look
    Outbound IDoc Error Handling via Workflow
    Outbound idoc error handling through workflow

  • Steps for ALE/EDI error handling using workflow

    Hi
    I need to handle errors in outbound IDoc generation using workflow. Can you please let me know the steps to be used for this. Step-by-step answer would be appreciated.
    Thanks

    Seetha,
    I have this already..
    IDOCPACKET                                                           
    Object type                         IDPKWMMBXY             
    End event                           MASSINPUTFINISHED      
    IDOC                                                          
    Object type                         IDOCWMMBXY             
    Start event                         INPUTERROROCCURRED     
    End event                           INPUTFINISHED          
    Application object                                                                      
    Object type                         BUS2017                           
    Start event

  • Idoc Error Handling through workflow

    Hi all,
      I want to send the Error Notification for a particular person for whom the task orders is assigned in the organization chart.
    What all the things I need to do.
      I have created the org chart and I have assigned the task to a user under a position.
      I have linked the Idoc error event in Tcode SWETYPV .
      What  all the things I am supposed to do.
    Regards
    Kumar

    Please go to transction WE20, pick the Partner / Idoc that you would like to assign the Org. chart to.
    Then you should configure "post processing :permitted agent" Tab with the Organizational unit.
    Then double click the process code associated with the Idoc Type and click the button next to the Function Module associated with this process code.
    Check  IDoc Tab and see if Stanard Event INPUTERROROCCURRED is present in the field called start event.

  • IDoc error handling via WorkFlow. What is missing?

    Hi All,
    My problem is when an error occured I don't receive anything in the Workplace.
    I did the following:
    When I created the process code I gave an object type(based on IDOCAPPL) for the function module's IDoc part. For the start event I gave the INPUTERROROCCURED event and for the end event the INPUTFINISHED.
    I created a standard task where the triggering event is the object type->inputerroroccured and the terminating event is object type->inputfinished and the object method is the object type->inputforeground. I use a standard role with a "Z" function module to determine the agent.
    I tested the role with an IDoc number and it worked. It gave me back a position where is my userid is the only id. The concistency check shows me 2 red line: the missing IDoc Packet section (I think it's not needed) and at the Role assignment (I think it's good so I don't understand this). 
    So, Do you have any idea what is wrong?
    Thanks for your help in advance.
    Regards,
    Gyula

    Hi Gyula
    Can you tell how you are actually raising that event .?
    I assume that you have created a process code and attached it to some function module and therein wherever you are getting error(when you want to trigger workflow) you are raising an event for your object type and its event .
    Since i cant check out your code , it guess you can try setting your task as General Task first to just get sure whether the event linkage is active for event or not and your workflow if at all is really getting triggered or not . If these things work fine with out then certainly your role determination function module needs to be checked.
    Kind Regards
    Shovit

  • Problem related to error handling in Proxy for Inbound

    Hi All,
    I have a requirement to process the inbound interface , which internally updates the HR Infotypes.
    I need to handle all possible erorrs and store it in the custom table.
    Can anyone please guide, as to how to catch the errors and wht type of errors can be there.
    How to do that?
    Any help will be gr8.
    Regards,
    Heena

    Hi Heena,
    the thread has been moved to ERP - Payroll as the application experts my be able to provide the list of error codes.
    Regards
      Kenny Scott
      XI/PI Forum Moderator

  • Idoc error handling for error status 51

    hi all,
    I am trying to set up inbound idoc error handling. For that I have activated task TS00008068.
    This task gets triggered for all error statuses except error status 51.
    Could you please help me understand why it doesn't trigger the task for error status 51?
    KR,
    Vithal

    Standard task 8068 is triggered for IDOC syntax, partner profile issues etc. The error message 51 is probably coming in from an inbound function module.
    Firstly there isn't a single standard task that will be triggered for all errors. Each IDOC error, depending on the events triggered, will fire a predefined standard task. For example, you're trying to process an order inbound and the IDOC is successfully created and passed on to application. Then the inbound FM will attempt to create an order and probably fail at determining a sales order or a ship to etc due to a missing setup. Then a different event is triggered which is attached to standard task 8046. That is different from 8068.
    Here is small subset of error 'vs' tasks:
    Message       Workflow Task
    SHPCON      TS20000051
    INVOIC      TS00008057
    ORDERS      TS00008046
    SDPICK       TS00008031
    WMMBXY TS00008009
    So you have to choose the IDOC which you want to activate WF task. Then look at the event that is associated with it. Then make sure the event is linked to the message type and routing is active.

  • User Exit  for Inbound Process - Changing IDOC control record

    Hi,
    I want to utilize the identification field (under details tab) of the IDOC Control Record. What is the suitable user exit for inbound process that i can use to change the IDOC control record?

    It's been a long time since I have done any IDOC processing. 
    Go to SE37 and enter the function module IDOC_INPUT_ORDERS.  Display the source code.  Search for "CALL CUSTOMER".  You should see several "CALL CUSTOMER-FUNCTION" lines.  These are enhancements where you can manipulate the IDOC data.  If you locate the correct one (where the data is read from the IDOC but not yet validated), you should be able to map the partner function value.  Double-clicking on the number in quotes will bring you to an "EXIT_" function module.  A "ZX" INCLUDE program is referenced.  If you haven't used the exit yet, double-clicking on the ZX INCLUDE will create it.  The values passed into the function module are available in the INCLUDE.
    Ideally, you should create a project in transaction CMOD that references the chosen enhancement.  This way you can activate/deactivate without commenting/uncommenting the code in the INCLUDE.

  • About ale error handling in workflow?

    Hi,
    can any one explian in detail ale error handling through workflow,its urgent for me.
    Regards,
    phani

    Hi Srikanth,
    follw the steps it will helpful u,
    Pre-requisites. 
    It is assumed that the reader of this article has some knowledge in SAP workflow BOR objects and ALE Idoc process like process code, Partner Profile etc. 
    Description 
    Here, we will be discussing in details the Error handling of an Inbound Idoc through triggering an event, which in turn will be triggering a workflow attached to the workflow. 
    Steps:-
    1.     Create custom BOR object with the events, Start and Stop event
    2.     Create a workflow for the error handling, like generating a notification whenever an error occurred in the Inbound Idoc.
    3.     Creation of Function Module and attachment with the Process Code
    4.     Create the settings for the Inbound Process of the Idoc through the Process Code.
    Creation of BOR objects. Go to the[http://www.****************/Tutorials/ALE/ErrorHandling/page3.htm] transaction SWO1. 
    Enter a name for the Object type and click ‘CREATE’ button for creating the custom BOR object. 
    Enter the details required for creating the BOR objects... 
    Create the Key fields and events of the BOR object.
    For creating the Key fields place the cursor on the Key fields and Click on the Create Button
    Create events for triggering the workflow and stopping the workflow.
    For creating the event place the cursor on the EVENTS and Click the create button like Key fields.
    Create two events.
    Enter the event name description etc and proceed further to create it. 
    Similarly create another event for ending the Workflow in the similar manner like that created earlier. 
    Now, Generate the BOR object through the generate button
    Release the EVENTS and subsequently release the BOR object. 
    After the creation of BOR object
    Create a workflow for the generation of notification whenever an error is reached in the Inbound Idoc.
    Execute the transaction SWDD. 
    Click on the CREATE button for creating the workflow for error handling. 
    Choose the Step type to be inserted for the notification like here we are using Send Mail option for sending a mail to the user whenever any error occurred.
    Activate the Workflow and test it whether it is working as per the requirement.
    After the successful completion it is required to attach the workflow with the event.
    Go to the Header section (Denoted by CAP).
    Go to the Start Events TAB.        
    Enter the details of the event with which the workflow should be linked like the category, BOR object type and the event with which that should be linked.
    Enter here the BOR object that has been created and give the name of event created for starting the workflow.
    Click on the Binding Button for generating the binding between the event and the workflow.
    Click on the Binding Button for generating the binding between the event and the workflow.
    Generate the binding and click OK button to save the binding.
    Click on Activate / deactivate button for activating the linkage.
    After the successful linkage the following sign will appear on the workflow..... 
    This shows that the workflow has been linked to the event and it will be triggered whenever that particular event will be triggered. 
    After the creation and successful linkage of workflow with the event it is required it is required to generate a function module and attached it to the process code. 
    Go to SE37 transaction and copy a standard process code function module to a custom one. Do no delete any parameters from the function module as the SAP standard program itself is calling this. 
    In that function module do the required validation and whenever the validation fails set a standard parameter ‘WORKFLOW_RESULT’ to 9999 from within the function module, otherwise normally proceed to set the status to 53.
    After the creation of function module it is required to attach it to the process code and corresponding attached to the message type at the Partner Profile stage.
    The process code is being created through the transaction WE42
    Go to the change mode and click the New Entries button for creating new process code. 
    Enter the Process Code Name, description and choose the processing type as Processing by function module. Click on the extension button of Identification.
    The details for the of the Process Code after clicking the identification button will be  
    Whenever idoc arrives into the Destination system then the standard SAP triggers the Process code attached to the Message type in the partner profile. The partner profile is being maintained in the transaction WE20. 
    Since, it is and inbound scenario so the message type and the corresponding process code will be maintained for the Inbound Parameters. 
    Click on Create Inbound Parameters button for creating new Inbound Message type and the corresponding message type. 
    Enter the process code for the corresponding message type. 
    Click SAVE button for saving the changes. 
    Whenever the IDOC arrives into the target system, it checks the partner profile and finds the corresponding process code. The process code is being linked with the function module through which the IDOC is required to be processed.
    Regards,
    Phani.

  • Can we use MASTER_IDOC_DISTRIBUTE  for inbound

    im using the custom idoc method to create a customer by uploading data from text file..can we use the above function module for inbound processing.. i have set the direction to 2 in control record.but when the idoc is generated it is triggered as outbound idoc and direction in the control record is showed as 1..can any one suggest the correct procedure..
    Thanks
    vidya sagar.

    Hi,
    MASTER_IDOC_DISTRIBUTE  is to generate Idocs....either Inbound or Outbound. But generally it uses for Outbound.
    In your scenario you will be getting data in file and your prog has to generate Inbound Idocs.
    fill all the relevent data in Idoc segments and in Control record pass '2' to Direction field which means Idoc Inbound.
    and in Partner profilev -> Inbound parameters  for message type if you select trigger by background prog option..idoc will be in generate and it wil be in 64 status ( Ready to transfer to application).
    Rest all same as Inbound idoc processing....means...it will trigger processcode that will pick the FM attached to it to create Customer.
    Regards,
    Bhavana

  • Regarding idocs error handling

    HI . i want to learn idoc error handling on sap xi side because  my current project is in PRODUCTION They implemented lot of idocs so is there any documents(guides ) regarding error handling of idocs  for both sender and receiver side.

    Hi
    Please refer File to IDOC Scenario..
    the 2nd post (Troubleshooting IDOC scenario) from Swarup Sawant  , you will get a very good understanding
    as lots of reference links are attached with different scenarios.
    Regards,
    Srinivas

  • Using FIDCC1 for Inbound FI docs

    Hey All,
    Im trying to suggest to our clients that a 3rd party interface into SAP 4.7B using flat files / BDC sessions, can be replaced by using IDOC Type FIDCC1. However, I'm told that this is a very difficult thing to do and basically when we try to post FB01 Docs, the system automatically determines a lot of fields which are not available with FIDCC1.
    Can anyone support/counter these claims? Have anyone used FIDCC1 for inbound FI docs? Please pass me on any reading material that you might have on this object.
    Cheers,
    KK

    thanq. yes, i hv gone thru this thread, i got the below difficulties,
    1) i did not see any file created on my system with name test_document.txt, either on SM35........so, itired to give my own path of my D drive, its not accepting!!
    2) and also i need other tx like FBB1, FBV1, FBS1......for these, am getting ABEND message in german, i did not wht it is?
    (so, i went to SXDA......here i hv only choice of giving BKPF, not BBKPF, which is slightly differes from BKPF!! but, i can manipulate the created file manually)
    thanq

  • Error handling return code for Provide Statement

    Hi Experts,
    For select statement we have error handling return code sy-subrc.
    What is the error handling return code for provide.. end provide statement.
    Thanks,
    Ragu

    Ragu,
    Same thing.
    Check sy-subrc.
    sy-subrc is the return code for all ABAP statements as far as I know.
    Regards,
    Dilek

Maybe you are looking for