SUP 2.2.5 + Offline BAPI Error Handling

Dear All,
Following is my Offline Transaction scenario where I require help.
Use Case:
MBO created on a Z BAPI that is Creating a GR (Goods Receipt) in SAP ERP. BAPI output contains Error Return Table as well that helps us in finding any error that is thrown from SAP.
Successful Scenario:
We create one GR in offline mode and call create() and submitPending() method of the MBO. When connected again and SYNC, it successfully CREATE the GR if there is no Error and I will get a new Document Number. Also, it returns error in Error Return Table if there is any error. We get it by calling the findAll() method on the MBO.
Problem Scenario:
We create two or more GRs in offline Mode and call create() and submitPending(). Now Sybase Unwired Platform has two pending Items. When connected again and SYNC, it only returns the LAST successful OR unsuccessful GR record in the findAll(). We lost the other items statuses. We might get the successful items from GR_LIST MBO but any pending items that has ERROR will be lost.
Is there any way in SUP that I can individually Sync pending items OR get the status of all Pending items after Sync?
Is this a default behavior of SUP that it flushes all the pending Items at once and ONLY returns the last item status in the Original MBO?
Looking forward for a quick and favorable response.

The MBO operations output is is not supported in SUP. Given below discussions gives more information , SUP operations cant get return / output parameter for HWC ?
How to create SUP native application
An alternative solution that I can give you:
Create an MBO using the BAPI used for operation, do not create an operation.
Keep the input and output of MBO/BAPI as tables (stuctures).
Call synchronize("sync_grp"); whenever you want to do operation, hence the operation RFC will be called. Make sure you are keeping this MBO in a separate sync group. Pass the input of the operation to the table using personalization keys. ie create PK of table/structure type and fill PK before sync from  mobile.
Before making a sync call check whether device has internet connectivity. If there is no connectivity store the user entered values locally in device (ex. in SQLite). Keep a button to sync pending operations when the device comes online by the user.
If the device is online do the sync. After successful sync make a findall query to get the output of operations. Since the output is a table all operations output messages can be found. In the BAPI output table keep a column for success/failure, based on that operation results can be identified.
Midhun VP

Similar Messages

  • ADF Custom error handler not working.

    Hi All,
    i am using jdev version 11.1.1.5.0. i have created one custom error handler class in model layer which extend DcErrorHandlerImpl class.
    and do the entry in Databinding.cpx file
    *<Application ErrorHandlerClass="mypackage.classname"/>*
    i have override getDisplayMessage(BindingContext ctx, Exception ex) method to show SQL Exception which comes from database table trigger.
    code is following-
    package com.in.jagran.view.services;
        import java.sql.SQLException;
        import oracle.adf.model.BindingContext;
        import oracle.adf.model.binding.DCErrorHandlerImpl;
        import oracle.jbo.JboException;
        public class AclasErrorHandler extends DCErrorHandlerImpl {
          public AclasErrorHandler(boolean setToThrow) {
            super(setToThrow);
            System.out.println("Inside Error Handler class");
          public AclasErrorHandler() {
              super(true);
           // this(true);
           * Returns the message that will be reported to JSF for each error that occurs.
           * Returning "null" is the way the custom error handler signals that a given exception
           * should not be reported to the client.
          @Override
          public String getDisplayMessage(BindingContext ctx, Exception ex)
            if (ex instanceof oracle.jbo.ValidationException) {
              return super.getDisplayMessage(ctx, ex);
            else {
              // Extract and return the error message that has to be displayed
              Exception exception = ex;
              String message = "";
              // If this exception is an instance of JboException,
              // try to find the cause by recursing over the eventual causing exceptions
              if (exception instanceof JboException)
                Throwable[] exceptionList = ((JboException)exception).getExceptions();
                while (exception instanceof JboException
                        && exceptionList != null && exceptionList.length > 0)
                  exception = (Exception)exceptionList[0];
                  if (exception instanceof JboException) {
                    exceptionList = ((JboException)exception).getExceptions();
              // *** Special processing of SQLExceptions
              if (exception instanceof SQLException) {
                message = exception.getMessage();
                // Ignore the lines in the error message that indicate the line number in the PLSQL code that the error resulted on.
                int ind = message.indexOf("ORA-06512");
                if (ind > 0)
                  message = message.substring(0, ind);
              // *** If the the reason for the JboException was data creation exception then display the message
              // of the top JboException (i.e. JBO-*****: Invalid numeric value, date format or time format)
              else if (exception instanceof NumberFormatException || exception instanceof IllegalArgumentException) {
                // Report the top exception
                message = ex.getMessage();
              // Otherwise report the message of the lowest exception in the hierarchy
              else {
                message = exception.getMessage();
              return message;
        }but it is not working for me.
    thanks in Advance.

    yes i have used dubugger.
    i have set break point to following line-
    return super.getDisplayMessage(ctx, ex);
    if (ex instanceof oracle.jbo.ValidationException) {
            return super.getDisplayMessage(ctx, ex);   
    }when atttribute validation done like i have attribute of type number and i have done the validation "must be greater than 0" now when i have given negative value control go to above line.
    and i have added following code also in handler class
            @Override
               public void reportException(DCBindingContainer dCBindingContainer,
                                           Exception exception) {
    System.out.println(exception.getMessage());
                       super.reportException(dCBindingContainer, exception);
                   }now when i have done commit operation control go to here and println statement print follwoing error on log window.
    JBO-26041: Failed to post data to database during "Rollback to Savepoint": SQL Statement "null".

  • Error Handling for BAPI MB_COUNT_POST_WITHOUT_INV_DOC for MI10 Transaction

    Hi,
    Can any one suggest me, how to handle the errors for the BAPI MB_COUNT_POST_WITHOUT_INV_DOC, because this bapi does not have any return table for errors handling? And also suggest any other BAPI which fits for MI10 transaction.
    <removed by moderator>
    Thanks&Regards,
    Damuan.
    Edited by: Thomas Zloch on Feb 2, 2012

    Hi Dear,
    Your answer is very helpful, thanks..!!
    But when  i am testing with the EIKPF structure, neither error is populating in EIKPF  nor the records are  posting in MI10. Could you please guess what would be the problem?
    Below are the fields that i am passing through this BAPI
    1)Document date 2)count date 3)plant 4)storage location 5)item number 6)material code 7) entry quantity
    Thanks&Regards,
    Damuan.

  • Error handling in bapi

    hi all,
          how to handle errors in bapis,and also can anyone send faqs on bapis.

    Hi
    A BAPI should be able to record and classify all possible errors that may occur a function Module BAPI_MESSAGE_GETDETAIL is used to Handle the Error Messages..
    You have to create a parameter named Return for every BAPI. This parameter returns exception messages or success messages to the calling program.
    BAPIs themselves must not trigger any messages (such as MESSAGE xnnn) in the coding. In particular they must not generate terminations or display dialog boxes. Instead, all messages must be intercepted internally and reported back to the calling program in the Return parameter. Otherwise the BAPI will not be processed correctly and control may not be given back to the calling program.
    All error messages or indeed any message that may be returned by the BAPI, must be defined in message table (Tools ® ABAP Workbench ® Development ® Programming environment ® Messages) and described in the documentation for the return parameter. This also applies to the most important or most likely error messages generated by other programs that can be indirectly passed via the BAPI to the application program.
    You must not use exceptions in BAPI interfaces.
    When a termination message (message type A) is triggered, a database rollback is executed in the standard programming model, that is, all tasks performed since the last COMMIT WORK are canceled. When you program BAPIs, we recommend that you also execute a database rollback in the return parameter for termination messages. You must describe this process in the documentation for the Return parameter. For messages of type E (error), the calling program performs the error handling.
    Application developers are provided with two service BAPIs to diagnose and process error messages from BAPI calls:
    BapiService.MessageGetDetail() displays the short and long texts of BAPI error messages.
    BapiService.ApplicationLogGetDetail(), with which information in application logs can be displayed.
    Features
    The export parameter Return can be implemented as follows:
    As a structure, whereby it must be defined in the function module as an export parameter, as well as in the method in the BOR.
    As a table, whereby it must be defined in the function module as a table parameter, as well as in the method in the BOR as an export parameter.
    Before filling the Return parameter you should either initialize the structure with CLEAR or the table with REFRESH and CLEAR.
    If the return parameter is not set or is set to an initial value this means that no error has occurred.
    The Return parameter may be based on the following reference structures:
    BAPIRET2
    You must use this reference structure when developing new BAPIS.
    BAPIRET1, BAPIRETURN
    These reference structures are still partly used in old BAPIs.
    Both structures must be filled in the logon language.
    Reward if Helpfull,
    Naresh.

  • BAPI Error Message Handling

    Hi Group,
    I am using BAPI ,How to display the BAPI  Error Message (eg:BAPIRET1) which is returning by BAPI

    HI ,
    ITS SIMPLE TRY THIS CODE
    AWARD PTS
    DATA: gt_ret     TYPE TABLE OF bapiret2,
               ls_ret    TYPE bapiret2,
    CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
        EXPORTING
          salesdocument     = p_vbeln
          order_header_in   = gt_hdr
          order_header_inx  = gt_hdrx
        TABLES
          return            = gt_ret -
    >>>>.<b>IMPORTANT</b>
          order_item_in     = gt_itm
          order_item_inx    = gt_itmx
          schedule_lines    = gt_sched
          schedule_linesx   = gs_schedx
          order_text        = gs_stdtxt.
          PARTNERS          = gs_partner
      CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
      LOOP AT gt_ret INTO ls_ret.
        WRITE:/ ls_ret-type.
        WRITE:/ ls_ret-message.
      ENDLOOP.

  • Maintenance Order using BAPI error

    Hi,
    While creating Maintenance Order using BAPI.. getting error no E-121  “ Error reading the order 10004009 in the document tables”
    Orders are getting created but, still the error is generated.
    Kindly suggest how to rectify this error.
    Thanks
    Mona

    Hope you are using BAPI_ALM_ORDER_MAINTAIN & BAPI_COMMIT_TRANSACTION in sequence.
    If not, try the sequence.
    You might have referred below thread. If not, please.
    BAPI_TRANSACTION_COMMIT - return error handling
    Is it possible to create orders in SE37 without any error?? If so, try above thread's solution.

  • /SAPSRM/CL_OFFLINEAPP_INBOUND error handling

    Hello gurus,
    I hope someone may enlighten me with a question I have on the Offline Approval inbound process...
    We're running SRM 7.0 SP9, and in order to configure the inbound processing of the offline approval we have to go to SO50, add the exit /SAPSRM/CL_OFFLINEAPP_INBOUND etc. All good so far!
    The question: how is the error handling done, and most importantly how may we add our custom logic? I see there is a method called HANDLE_ERROR (where I could add an enhancement implementation) - which seems to not be called anywhere and doesn't have any import/export parameters! Therefore this is no good for me I guess (unless someone proves me wrong?)
    Basically my client wants to add an entry to RZ20 alert / or a normal log in SLG1 whenever an offline approval fails (if immediate processing fails for any other reason). By standard I think it forwards the reply e-mail to the SAP Business Workplace inbox of the user. 
    Has anyone done something similar? I have checked the forums and done several xSearches on the SAP Marketplace, however just hitting dead ends...
    Many thanks!
    Adi

    Hi Adi Abu-Taha Zitawi,
    Hope all is well.
    I actually have the same question as you.  The standard error handling functionality seems to send a message back to the "wf-batch" user if there is an error.  Also, this message is pretty useless since it does not even contain the shopping cart #.  This is also not an ideal solution because a business user has no visibility of these messages.
    What / how did you end up resolving this business requirement?  Did you implement the solution mentioned above?
    cheers,

  • JDev 11.1.1.2.0 - Error while providing Error Handler Class in Databindings

    I get this exception as soon as I provide a reference to ErrorHandlerClass in DataBindings.cpx
    Error 500--Internal Server Error
    oracle.jbo.JboException: JBO-29000: Unexpected exception caught: java.lang.InstantiationException, msg=empexceptions.model.EmpDCErrorHandler
         at oracle.jbo.common.JBOClass.newInstance(JBOClass.java:253)
         at oracle.jbo.uicli.mom.JUApplicationDefImpl.initializeBindingContext(JUApplicationDefImpl.java:1242)
         at oracle.jbo.uicli.mom.JUApplicationDefImpl.populateContext(JUApplicationDefImpl.java:1215)
         at oracle.jbo.uicli.mom.JUMetaObjectManager.loadCpx(JUMetaObjectManager.java:713)
         at oracle.adf.model.BindingRequestHandler.initializeBindingContext(BindingRequestHandler.java:399)
         at oracle.adf.model.BindingRequestHandler.beginRequest(BindingRequestHandler.java:182)
         at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:189)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:97)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:420)
         at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:420)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:247)
         at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:157)
         at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:94)
         at java.security.AccessController.doPrivileged(Native Method)
         at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
         at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
         at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:138)
         at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:70)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:326)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: java.lang.InstantiationException: empexceptions.model.EmpDCErrorHandler
         at java.lang.Class.newInstance0(Class.java:340)
         at java.lang.Class.newInstance(Class.java:308)
         at oracle.jbo.common.JBOClass.newInstance(JBOClass.java:245)
         ... 34 more
    DataBindings.cpx looks like this
    <?xml version="1.0" encoding="UTF-8" ?>
    <Application xmlns="http://xmlns.oracle.com/adfm/application"
                 version="11.1.1.55.36" id="DataBindings" SeparateXMLFiles="false"
                 Package="empexceptions.view" ClientType="Generic"
                ErrorHandlerClass="empexceptions.model.EmpDCErrorHandler">and my error handler class looks like this
    package empexceptions.model;
    import oracle.adf.model.binding.DCBindingContainer;
    import oracle.adf.model.binding.DCErrorHandlerImpl;
    public class EmpDCErrorHandler extends DCErrorHandlerImpl {
        public EmpDCErrorHandler(boolean b) {
            super(false);
        @Override
        public void reportException(DCBindingContainer dCBindingContainer,
                                    Exception exception) {
            super.reportException(dCBindingContainer, exception);
    }Am I doing anything wrong here?

    hi Harry
    See "28.10 Customizing Error Handling"
    at http://download.oracle.com/docs/cd/E14571_01/web.1111/b31974/web_adv.htm#ADFFD1398
    that says "... The exception error handler must have a default constructor, as shown in Example 28-27. ...".
    success
    Jan Vervecken

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

  • Forward Error Handling - File interfaces?

    Hello Experts,
    Can we use Forward Error Handling (FEH) for implementing error handling in File Interfaces ?
    Like for simple Application Server file interfaces, if something goes wrong during the process of writing/reading a file on App Server, can we use FEH for showing the log?
    I know it is a concept used for PI...so we want to know if it can be used for file interfaces as well? Just want to keep similar approach for error handling and logging (for both PI and File Interfaces).
    Thanks.

    Edit 1 May 2015: Added inbound
    Just a slight correction.
    FEH is used in the ABAP backend systems and are only for asynchronous inbound proxy interfaces. It is not available for sync proxies, IDocs, BAPIs. Neither is it available for any error handling on the PI system itself.
    PI/XI: Forward Error Handling (FEH) for asynchronous proxy calls with the use of Error and Conflict Handler (ECH)
    Message was edited by: Eng Swee Yeoh

  • Error in custom error handler class

    Hiii...
    i got some error s when i create error handler class
    i use the following code for creating that class
    package view.controller.fwkext;
    import java.util.ArrayList;
    import java.util.List;
    import oracle.adf.model.binding.DCBindingContainer;
    import oracle.adf.model.binding.DCErrorHandlerImpl;
    import oracle.jbo.CSMessageBundle;
    import oracle.jbo.DMLConstraintException;
    import oracle.jbo.JboException;
    public class CustomErrorHandler extends DCErrorHandlerImpl {
    List<ExceptionMapper> exceptionMapperList = new
    ArrayList<ExceptionMapper>();
    public CustomErrorHandler() {
    this(true);
    public CustomErrorHandler(boolean setToThrow) {
    super(setToThrow);
    exceptionMapperList.add(new DisableJboExceptionCodesMapper());
    public void reportException(DCBindingContainer bc, Exception ex) {
    for (ExceptionMapper mapper : exceptionMapperList) {
    if (mapper.canMapException(ex)) {
    ex = mapper.mapException(ex);
    super.reportException(bc, ex);
    I got errors
    DisableJboExceptionCodesMapper not fount
    canMapException not fount
    mapException not fount

    Abhilashs01,
    Yes, that example from the docs appears to be missing a few things, to-wit: the ExceptionMapper class and the DisableJboExceptionCodesMapper class. Without the ExceptionMapper class, JDeveloper's import assistance is finding one in com.sun.jndi somewhere, which is obviously the wrong one. So, yes, the docs are good, but they appear to be missing some key things, making it kind of hard...
    Another place to find an example error handler class is in the Fusion Order Demo: http://www.oracle.com/technology/products/jdev/samples/fod/index.html
    John

  • General error handling operation

    Hi,
    I did not find a comprehensive explanation how error handling works in TestStand, only bits and pieces about the callbacks (perhaps I looked at the wrong places).
    Anyway, I made some experiments with SequenceFilePostStepRuntimeError and StationPostStepRuntimeError - intentionally leaving out ProcessModelPostStepRuntimeError to reduce complexity - and came up with the attached flow chart. I would like to know:
    if that shows the correct operation of TestStand error handling (we are currently using 4.1, about to switch to 2010 or 2012, so it would also be interesting to know if anything changes with the new versions)
    if it is always the case that the combination of ErrorReported=True und Error.Occurred=True after the error handler leads to termination of the execution? I could not find any setting governing that (the "goto cleanup immediately" setting of the sequence was off;
    Best regards
    Peter
    Attachments:
    TestStand_ErrorHandling.png ‏36 KB

    Hi Peter,
    1) Every step has :
    error.code   - to set the error code
    error.occured - boolen if set true displays a popup error message to the user
    error.message - the popup contains this message
    when you set error.occured=true it will bring up a popup message with the error.message and error.code.
    Please note that this may not be acceptable in the manufacturing environment where operators may not be trained to check for errors.
    The general practice in manufacturing is to fail all important steps that errors out so that the final result is failed.Then do a offline analysis.This is done by step.results.status = "Failed".You can also populate step.results.ReportText with proper values so that your test report reflects the type of error/failure.
    2) Regarding the  SequenceFilePostStepRuntimeError and StationPostStepRuntimeError - they are optional error handling methods if you want to act on errors.
    3)Every step has an option ( look for properties-->post actions).On Pass or On fail destinations can be set for each step.Cleanup is always executed except in cases of abort.
    4) In the menu configure-->Station options-->execution there is an option for runtime errors ( one of them is run cleanup).
    Hope the above information helps.

  • How to take control back from service error handler in osb

    I am using osb to send data to multiple services at the same time.since x query is a procedural language if any single operation fails the flow goes to service error handler which calls a BPEL webservice and logs the error in a database but the control doesnt comes back to my code I have tried everything including RESUME,REPLY operations but all in vain similarly i cannot use service callout call to my business service because its not allowing to select my BPEL wsdl operation

    If your statement "the control doesnt comes back to my code" means you expect that your xquery will continue in processing than your expectations are just too high. :-)
    Resume action is supposed to resume the next action in the message flow. It means the action that follows the action which caused an error.

  • Report and Alert don't executed in the error handler with a JMS proxy service

    Hi,
    I'm working with OSB 11.1.1.4.0 and I'm facing a problem with the error handler of my JMS proxy service.
    My error handler contains two main elements :
    - a Report action
    - an Alert with a JMS destination defined
    When the business service failed the message remain in the queue. It's the expected behavior.
    The problem is :
    - the report is missing
    - the alert is raised but missing in the JMS destination defined in the Alert setting.
    I've noticed if I add a Reply with Failure or Success, Report and Alert are successfully executed.
    Unfortunately the message don't remain in the JMS queue.
    What can I do in order to have my report/alert done and the JMS transaction rollback in order to keep the message in the queue ?
    I've already met this problem in the past with alsb v3 and my solution was to add Service Callout in the error handler in order to externalize these actions.
    This solution is not convenient and I hope another solution is possible.

    Inventorying workgroups can be difficult, especially when it comes to remote access and network security. Because workgroups are not centrally managed, some of the items discussed in this
    wiki article on preparing your workgroup environment may require you to visit each machine individually.
    For non-domain credentials, you do not use the <systemname>\<user> format, you simply enter the user name. Regarding how to enter the credentials, if you have an account that uses the same username and password on all machines and is an administrator
    on all of those machines, then you can enter that in the All computers credentials page of the wizard. You can also do this if they are different user names. However, if some machines have an account with the same user name, such as Administrator,
    but different passwords on each machine, you will need to use the Manually enter computer names discovery method, and then enter the information for each group or each machine.
    As you can tell, workgroup environments can quickly negate any benefit that the agentless inventory nature of MAP provides.
    Please remember to click "Mark as Answer" on the post that helps you, and to click
    "Unmark as Answer" if a marked post does not actually answer your question. Please
    VOTE as HELPFUL if the post helps you. This can be beneficial to other community members reading the thread.

  • Database Connection Error:BAPI Error #0

    I have a problem when I preview a report in Crystal Reports 2008 using BW MDX Query I had recieved the following messages:
    1.Failed to retrieve data from database
    and then when I click ok
    2.Database Connection Error:BAPI Error #0
    Error occurred  when starting the parser:timeout during allocate / CPIC-CALL'ThSAPCMRCV'
    I copied the query of crystal report and I execute it inside the transaction of mdxtest
    SELECT  NON EMPTY EXCEPT([0CALMONTH].MEMBERS, {[0CALMONTH].[All]}) ON ROWS FROM [USD_SD_C0/RPT_1] SAP VARIABLES [!V000001] INCLUDING [0CALMONTH].[200401]
    I found the debugger had stopped in the line Break when I click on F8
    I recieve the following error
    Error occurred when starting the parser: timeout
    during allocate / CPIC-CALL: 'ThSAPCMRCV'
    Please anybody can help me

    Dear Ingo
    I had read this note
    I applied the following:
    1.I didn't found the lrfc32.dll in the windows/system32 in my BW server so I asked my basis administrator to upgrade the kernel
    2.after this step I didn't find it again so I had copied the file from the new kernel and copied it to system32 and sysWow
    3.I register successfuly the lrfc32.dll using the commanf regsvr c:/windows/system32/lfrc32.dll
    (note: this step didn't succeed until I had installed SAP GUI in BW server because as I observed that there is a need for C++ compiler which is installed by default when you install GUI)
    after all of this I cannot run any crystal report based on any BW query
    So Please anyboday can help

Maybe you are looking for

  • SSRS 2012 service application error in sharepoint 2010

    Hi,  I have installed MS SQL SERVER 2012 enterprise edition and sharepoint 2010 SP2 standalone as i want to learn a few things. Everyting went smooth upto the point when i wanted to configure a Create the Reporting Services Service application in sha

  • In serious need of some guidance.

    If you look at my post history, you'll see I've been complaining about my Early-2008 iMac recently and how it crashes after waking up from sleep. It use to do this about once every couple of months. No it's getting to the point where I can't use it w

  • How can you tell if software is legit?

    Hey everyone. I'm looking around different websites trying to find a cheap version of a suite and am noticing that ALOT of deals are obviously not legal. But at the same time there are some the seem legit but I don't want to take a chance. What are s

  • Production order Basic start date calculation

    Hello PP Sapperu2019s, I have an production order for total qty - 865,00.This production order created on 11.08.2011 and I could able to see the Basic start date as 26.06.2011.Please let me know how this basic start date gets calculated. I mean what

  • Overriding createToolTip?

    I am trying to override createToolTip in order to get a multi-line tooltip. It works fine for JButton but it does not work for my DefaultTableCellRenderer. Does anybody know why? public class MyDefaultCellRenderer extends DefaultTableCellRenderer {