ALE outbound error handling

Hi gurus,
I've implemented some ALE systems successfuly. I mean the distribution of information is alright but, now, I want to get some notification when any outbound error occurs.
I,ve filled the 'Post processing: permited agent' tab in the partner profile (both for partner and message type) but it doesn't work. I suppose I need to do something else.
Can anybody help me with this matter?
Thank you in advance.
JM Parra.

Hi,
Just an added information
Message Type : ALEAUD,is present which is used to give successful notification/confirmation  in case of the posting of the IDocs, this Message type should be configured on the inbound side( Partner Profile and the Distribution Model) after which an IDoc of ALEAUD Message Type would be generated and the segments in this IDoc would contains the details of the Message Type(Including IDoc no) for which the confirmation is generated.
Thanks
Krithika

Similar Messages

  • Task ALE/EDI: Error handl cannot be started immediately

    When an IDOC is being created in SAP(3.1I) from an external system(Gentran GIS), it is added with errors status 56. The error text states as 'Task ALE/EDI: Error handl cannot be started immediately
    'The task ALE/EDI: Error handl (no. TS00008068) cannot be started immediately by user GIS'.    
    Can anyone advise where the user 'GIS' need to be added to avoid getting that IDOC error

    Hi Bhaskara,
    This can be caused by several issues:
    1. The user GIS has NO authorization to run workflows or to run this specific workflow task (TS00008068).
    2. The user GIS has NO authorization to run function module EDI_ROLE_FOR_PROCESSING (or when running this function module it will return data in the ACTOR_TAB, which means that the workflow cannot be started by default users).
    3. Within the partnerprofile (transaction WE20) at the specific inbound parameters for the message on the tab "Post processing: permitted agent) an agent has been defined that will not resolve to the user GIS (and therefore this user is NOT allowed to do post processing).
    Most likely issue 3 is here at hand. If this is the case, REMOVE the entry for the agent (or consider to setup an organisational unit/work center and make GIS a member).
    The error, by the way, is an inbound processing error. It is possible that in the ALE layer something has not been defined properly.
    Within the partnerprofile (transaction WE20) at the specific inbound parameters for the message on the tab "Inbound options" and double-click on the entered Process code.
    You must now check the entries here.
    Example:
    If you use an own function module (named in the Identification field) you must set the radio buttons to Processing with ALE service AND Processing by function module. The little button behind the identification field will show some details.
    At least the detail fields (on tab IDoc) Object type, Start event and End event must be filled.
    Default values for these are: IDOCAPPL (=Object type), INPUTERROROCCURRED (=Start event) and ERRORPROCESSCOMPLETD (=End event).
    Of course within ALE you can define different types of process codes (what you like most for your specific handling).
    Hope this helps you a bit on your way.
    Regards,
    Rob.

  • 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

  • ALE Inbound Error Handling

    Hi
    Here I have problem in setting up Error handling in outbound/inbound processing of Idocs in ALE....
    Can any one please explain how to do it....
    My requirement is, if ever idoc goes in to error then the user has to be intimated by mail in SAP Inbox.As per my knowledge it can be done through partner profile...if specify user name in partner profiles/post processing agent place.
    My doubt is will it be same in outbound/Inbound?
    Do i need to do anything other than specifying usernames in partner profiles?
    What is the use of Idoc Administrator?
    Please explain how to do that....
    Awaiting your valuable answers...
    Thanks
    Suresh
    Message was edited by: Suresh Babu  Mannem

    I think you also need to specify the "post processing agent" in your Partner profile - Message Type.
    Check WE20.
    In case you don't want to use organizational assignment then leave the task as it is as general task.
    So only the user specified in "post processing agent" will be taken into consideration.
    Here are the steps that you need to do for a complete error handling procedure ( but you can avoid organizational assignment if you just need to use User Name as receipient ):
    I've taken it from F1 help on error handling:
    Error Handling
    In this section, you can make the settings for error handling:
    Create organizational units and assign standard tasks
    Maintain EDI administration ( Idoc administrator section on Xn OYEA or We40 )
    Maintain error process code ( Xn OYEA or We40 )
    Further you can check it using Verification Processing on OYEA / WE40 .
    Errors are processed in the system in which the error occurred.
    You can repost IDocs that were not posted (with status 51) using program RBDMANIN.
    Requirements
    ALE error handling uses workflow. A standard task is provided for each message type. Task TS20000051 is used for all BAPIs.
    Workflow functions as follows:
    A task (work item) is generated for the error handling and stored as a message in the inboxes of the employees responsible.
    If one of these employees processes the work item, the standard task method for error handling is started. The user can, for example, restart IDoc processing.
    If the IDoc is processed successfully, the work item is deleted from the inboxes of all the employees involved.
    For this procedure to function, the employees responsible for a particular message type and partner (sender or receiver) must be defined as follows:
    1. A hierarchy of organizational units (for example, "sales office") and positions (for example, "customer officer for customer X") is created and employees are assigned to it.
    2. The standard tasks for error handling (for example, an error related to an inbound sales order) are assigned to the relevant organizational units or positions (for example, "sales office").
    3. The organizational unit, position or employee responsible for dealing with the error are specified for each partner and message type in the partner profiles.
    If an error occurs, the system determines:
    1. The employees responsible using the staffing schedule of the organizational unit or position linked to the standard task.
    2. The employees defined in the partner profiles (using position, user ID, or organizational unit).
    3. The employees appearing in both groups represent those who will receive a work item in their inboxes.
    Activities
    Create organizational units and assign standard tasks
    Maintain EDI administration
    Maintain error process code
    If you used EDI communication in an earlier version, you can check the assignment of error process codes to the standard tasks.
    Check names of the employees responsible in the partner profiles.

  • ALE / IDOC Outbound Error Handling

    Hi Experts,
    I got an error in Outbound Process.
    An IDOC gets the status 36 - Timed out.
    Can anyone tell me how can i resolve this Error?.
    Thanks in advance,
    Sudhakar

    Hi ,
            Best option is to keep a sql trace on the outbound idoc which will tell you at which perform or functional module ,the performance is taking time to fetch .
    all check with basis in terms of timed out ,they would have set a paramater for time out in terms of mins or hrs.

  • 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

  • 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

  • For IDOC monitoring, analysis and error handling in  ALE & idoc

    Hello...experts..can u please tell me about idoc monitoring,analysis and error handling..and can u please tell as per interview  point of view in this area..if availble can u send material about this...
    thx
    Message was edited by:
            durga kottapalli

    Hi,
    Reprocessing IDocs with errors
    Outbound (BD88)
    Once the error has been determined and corrected it is not necessary to resend the IDoc again. You simply resend the IDocs that have already been generated.
    Using the IDoc overview screen you need to take note of the following for each IDoc that was not processed:
    Error number: 2, 4, 5, 25, 29
    Error number: 30 (Execute Check IDoc dispatch to process)
    IDoc number
    Using the Error number, the IDoc number and the transaction BD88 , with the required message type you can resend the IDoc. Match the error number with this transaction and execute the function for the IDocs incorrectly processed.
    Just check the below link, u will get all IDOC related Interview questions
    http://www.allsaplinks.com/idoc_sample.html
    http://www.allsaplinks.com/
    http://www.sappoint.com/abap.html
    http://www.sap-img.com/
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
    http://www.sappoint.com/abap.html
    http://sap.ittoolbox.com/documents/popular-q-and-a/extending-a-basic-idoc-type-2358
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://expertanswercenter.techtarget.com/eac/knowledgebaseCategory/0,295197,sid63_tax296858_idx0_off50,00.html
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
    http://help.sap.com/saphelp_47x200/helpdata/en/dc/6b7eee43d711d1893e0000e8323c4f/frameset.htm
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sap-img.com/
    http://www.allsaplinks.com/
    Regards,
    Suresh.
    Message was edited by:
            SureshKumar Ramamoorthy

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

  • Error handling problem with outbound idoc status 02 and  XML HTTP Port

    I set up an ALE scenario to send master data out of SAP via an XML HTTP port.  All goes well until the idoc receives error 02. 
    It looks like idocs in this error status with the use of an XML HTTP port can not be reprocessed via the standard SAP techniques.  Program RBDAGAIN takes them out of the list for reprocessing (even though the connection is back up and running).
    Is there any solution to still use the standard ALE error handling ?

    Hi Karin,
    Looks like based on note 701597, you can only reprocess these idocs manually via a workitem.  I qouted the relevant text below:
    3. Error handling with status '02':
    An HTTP IDoc in status '02' should not automatically be sent once again.
    Up to now, the RBDAGAIN report was used to resend incorrect IDocs.
    However, this report was adjusted and now deletes all IDocs in status 02
    to be routed to a HTTP port from the list of selected IDocs. IDocs to a
    HTTP port in status '02' should only be sent manually via a work item.
    Regards:
    Rex

  • Error Handling for Outbound IDOC - COSMAS (Cost Center Master)

    Hi,
    I need to trigger a mail to SAP inbox whenever a outbound idoc fails for any reason.
    I know how to do it for inbound or outbound transaction data, but not sure how to do error handling for outbound master data.
    Could one of you help me understand the same.
    Thanks in Advance,
    Vinoth

    Hey Vinoth,
    Do you want decide the recipient of the mail dynamically? am asking because if you give the USER NAME in the partner profile and when ever a IDOC fails a mail will automatically reach the user inbox automatically
    let me know if i answered ur question.
    Thanks,
    Santhosh

  • Re : How to Error Handling In Idoc /ALE.

    Hi This is Arief , 
                            I tranfer the Data  Through ALE  from One Client To Other Client some of Data not Posted ......how check other client wither Data Posted or not ....
    How to error Handling In IDocs.....pls Help me.......
    Kind Regards
    Arief .S

    Hi
    The exception handling for idocs
    http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7f1543d711d1893e0000e8323c4f/frameset.htm
    Exception handling in File to IDoc Scenario
    For RFCs
    Re: Passing SAP Exceptions to a sync SOAP Call
    Error Handling when using RFC
    Exception Handling while Calling RFC - BPM
    handle exceptions in remote function modules

  • ALE Error Handling with Workflow

    Hi All,
    I have some issues with using workflows with idocs:
    In our process codes , the business object , start event for error handling and success event has been configured.
    Now if the workflow_result is 0 then success event is triggered and if workflow_result = 99999 then start event is triggered.
    I have two qquestons:
    1. How are these events triggered as I did not find any code in the F.M> to triggerethem.
    2. What is the purpose of End event.
    Apart from this , is there any area where workflows can be used with IDOCS.
    Thanks and Regards
    Aman

    Hi,
    In case I am creating a custom F.M. to process idoc data then I can use the F>M> to create the event.
    However In case the standard F.M. is being used and workflow_result is set to 9999 in it and I have consigured the start event to it,in that case I will not be able to use thie F.M> to trigger the workflow.
    Thanks and Regards
    Aman

  • Idoc/ALE error handling, send to external email

    Hi all,
    I'm developing an IDoc inbound interface for purchase order create using PORDCR1. For the error handling functionality, I need to send an external email describing all of the validation error happened in user-exit EXIT_SAPFKCIM_002. Please kindly tell me how to cater the functionality. I won't use workflow because the error handling can't describe all the error, it just displaying the first error encountered. I also don't want to create any custom object since message type PORDCR1 is available. I think creating a custom FM is a possible way, but if there is another way, please tell me how.
    Thanks,
    Teddy

    Hi Teddy,
    A custom FM is the easiest and simple way.There may be other ways.
    Regards,
    Atish

  • Outbound error IDoc reprocessing

    I have a scenario like whenever an outbound idoc is in error status, should be able to correct the idoc n reprocess it.
    Suppose outbound idoc is in status 02. System process code will notify the agent assigned in partner profile. When i execute the workitem and corrected the port and try to reprocess, this status is set to 30. My requirement is once i correct the port status should become 03. How do we acheive this ? (not through report rseout00 )
    1. In general scenario how do we handle outbound error idocs?
    2. Is system process codes are used only for notifications or error processing?
    Inputs will be appreciated regd outbound error reprocessing .
    Thanks.

    Hi Indira,
    1. In general scenario how do we handle outbound error idocs?
    You can use transaction BD87 to monitor the IDoc statuses.
    and use the following programs to reprocess outbound and inbound error IDoc(s).
    RBDAGAI2 - Re-processing of IDocs after ALE Input Error
    RBDAGAIE - Reprocessing of Edited IDocs
    RBDAGAIN - Process Outbound IDocs with Errors Again
    RBDAGAIP - New Posting of Partially Posted IDocs
    RBDMANI2 - Manual Processing of IDocs: Post IDocs Not Yet Posted
    RBDINPUT
    2. Is system process codes are used only for notifications or error processing?
    The process code ise used in both ALE and EDI framework to identify the function module or API (Application Programming Interface) to be invoked for subsequent processing.  Inbound as well as outbound interfaces use process code but for different purposes. Outbound process codes are stored in table TEDE1, while inbound process codes are stored in TEDE2.
    Hoep this will help.
    Regards,
    Ferry Lianto

Maybe you are looking for

  • .DS_Store files on USB thumbdrives - a way to stop them from being created?

    Hello! Forgive me if this has been asked to death, but at school I need to copy homework files back and forth to the school's XP-based computers constantly. Because in any given day I usually update half a dozen files across the "homework" folder on

  • Designing the table grid in subscreen in a selection screen..

    Hi all, Actually my requirement is there is a check box in the selection screen,If its checked then we have to display a subscreen with the details "Emp type"      "Empname"        "Monthly"      "Yearly"    PM                Glen                 500

  • Attachments visible in all steps of GP

    Hello SDN Community, I have got a question concerning Attachments in GP: At the customer we implemented, that A user is able to add an attachment in the step, which has been assigned to him. In the next step another user should be able to have a look

  • Powerbook DIED. Target Disk Mode Failed.

    I did everything under the sun short of bringing it to a mac service store. My computer was left whirring all night (I was not home) and the next day I found all the programs frozen so I did a hard shutdown. I haven't been able to reboot it past the

  • When will Schoolsfirst federal credit union card be added?

    I Have a Master card ATM card from Schoolsfirst federal credit union and want to know if and when it will be added to Apple Pay. I would be nice to have a list of Banks Apple is currently working with or a sign up page for our banks.