HCM process & Forms - Need logic to handle the Error's when Infotype Update

Hi Experts,
Currently im working with HCM process and forms workflow's. I have ten HCM workflow's and everything is working fine.
Now the issue is, at the time of save, if there is any error like infotype lock or any other Master data error's, then the standard task responsible for save the data, returns the Status as Error.
Already the approval process for the request is carried out, and it can not be make it again. So I need to save the data without re execution of the process or without re-approval.
I searched in standard workflow also. There is no option to handle the Infotype update Error's.
So can any one give me some hint about this? Without the re-initiation i need to save the data's.
Thanks for your time and Suggestions.

If you are using the framework to update specific infotypes and they are locked for "no apparent" reason you'll want to open an SAP message.  I would highly discourage you from going down the path of calling that FM, from within workflow no less.  Workflow in the framework was not intended to do such operations, this is supposed to be handled in the decoupled infotype framework (through configuration)... not to mention you won't be using the dec. infty framework by calling that function.
While I've had to do this before, it was because of a limitation in the framework not something as trivial as a locked infotype.  Who knows, it might actually be locked for a legitimate reason?
Andy

Similar Messages

  • HCM & Process forms

    Hi Experts,
    I am new to HCM & Process forms could you please provide the information about HCM & Process forms, and how they are useful.
    In which requirements we have to use these HCM & Process forms.(Send me some important links regarding the HCM & Process forms).
    Thank you,
    B. Raghu Prasad.
    Moderator Message: Please search before posting.
    Edited by: Suhas Saha on Oct 5, 2011 3:52 PM

    Hi Aakash,
    Yes, in my case it was an authorization issue. Try assigning the role SAP_ASR_MANAGER to the manager in the ECC.
    Regards,
    Manish

  • Error 16 when I update my iPhone 5s showed me stuck on recovery mode and whenever I got error 16 Restore thing is the problem?

    Error 16 when I update my iPhone 5s showed me stuck on recovery mode and whenever I got error 16 Restore thing is the problem?

    Hello Meysam321,
    After reviewing your post, I have located an article that can help with your device. It contains a number of troubleshooting steps and helpful advice for the issue you are experiencing:
    Resolve iOS update and restore errors - Apple Support
    Check for hardware issues
    Related errors: 1, 3, 10, 11, 12, 13, 14, 16, 20, 21, 23, 26, 27, 28, 29, 34, 35, 36, 37, 40, 1000, 1002, 1004, 1011, 1012, 1014, 1667, or 1669.
    These errors mean that your device or computer may have a hardware issue that's preventing the update or restore from completing.
    Check that your security software and settings aren't preventing your device from communicating with the Apple update server.
    Then try to restore your iOS device two more times while connected with a cable, computer, and network you know are good.
    Confirm that your security software and settings are allowing communication between your device and update servers.
    If you still see the error message when you update or restore, contact Apple support.
    Thank you for contributing to Apple Support Communities.
    Cheers,
    BobbyD

  • HCM Processes & Forms Cost Assignments Defaults

    Hello Everyone,
    I have a question about making Cost Assignments for Infotyps like "Additional Payment" (0015) or "Employee Remuneration Info" (2010) within a Processes and Forms Scenario. This is really a huge requirement for us because the hole Company is split in several subsidiaries so we need to book the costs to different cost objects.
    In the Backend World (PA30/PA61) when creating a record for either one of the Infotypes I can choose the Option "Maintain cost assignment" so I can define a different cost object where the costs of the created record should be booked.
    I know the data of the cost assignment get's stored in the tables ASSHR & ASSOB. But as I'm using the SAP Backend Services SAP_PA and SAP_PT I can't make any DB update/insert statments after the records are created.
    Did anyone implemented a Scenario like this before?
    Would be awesome if someone could give me an advise.
    Best regards,
    Tobias

    If the infotypes in  question are standard PD infotypes you could use SAP_PD service to update them.
    For any other tables you will have to go with a advanced generic service or do the update in a background workflow task.
    Refer here to the post by Christopher Solomon's Profile | SCN: http://scn.sap.com/community/erp/hcm/blog/2012/08/20/hcm-processes-forms-when-all-else-failsadvanced-generic-services
    Hope this helps.
    Regards.

  • Error occured while sending a form in test in HCM Process & Forms

    Hi
    An error occured while testing my process in Design Time Tool. All the process, form, and workflow are consistent and activated, however when I send the form in test program available in Design Time Tool I get a Short Dump (as below) followed by the error "Workflow Item Not Found, Workflow Not Started."
    Category               ABAP Programming Error
    Runtime Errors         MESSAGE_TYPE_UNKNOWN
    ABAP Program           CL_POBJ_CASE==================CP
    Application Component  PA-AS
    Date and Time          23.02.2012 09:38:34
    Short text
    Message type " " is unknown.
    What happened?
    Error in the ABAP Application Program
    The current ABAP program "CL_POBJ_CASE==================CP" had to be
    terminated because it has
    come across a statement that unfortunately cannot be executed.
    What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
    Error analysis
    Only message types A, E, I, W, S, and X are allowed.
    How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "MESSAGE_TYPE_UNKNOWN" " "
    "CL_POBJ_CASE==================CP" or "CL_POBJ_CASE==================CM00D"
    "IF_POBJ_CASE~CREATE_CASE"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
    To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
    Display the system log by calling transaction SM21.
    Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
    In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
    Looking forward to your expert advice to resolve this error.
    Best regards
    Imran

    This can be a few things....
    1. Make sure you set up your number range for CASE Mgmt (t-code SCASE_NUMBERANGE)
    2. if the POBJ_MODEL is missing in your CASE Mgmt environment
    3. if the doc id for your object models (process, scenario, case) are somehow "out of whack" (not matching) between CASE mgmt, SCASE_CUSTOMIZING and SRMREGEDIT
    4. authorization issues (which it more likely is)... I know it sounds weird, but even giving you SAP_ALL will not do it (even it is missing some of the auth objects). You have to be able to read/write to CASE Mgmt (so the related auth objects are needed....look for ones with S_SRM* or S_SCM*). Also, WF-BATCH user needs this auth as well!
    This part can be a PAIN to get sorted out.

  • Error while editing standard HCM Processes & Forms

    Hi experts,
    I would Iike to test the standard HCM processes & Forms & for which I have imported the standard forms from Client 000. I have also configured the ADS & have tested the credentials as well. Everything is fine & new custom ADOBE interactive forms (Not HCM Forms) are working fine through WDA. When I test any of the standard processes using HR Administrator role in Portal, I am able to select the relevant standard process (e.g. TERMINATION) for a given employee, but when I click on the  Edi Process button, the system generates an error (short dump): "'WebDynpro Exception: ADS call failed ". I have checked OSS, but did not find any suitable note for it. I have the HR administrator role assigned in the back end & have confirmed that the ADS configuration as well as credential are working fine using the recommended reports. We are on EhP4 SP06.
    Appreciate if anyone has already experienced these probelms & can suggest any solutions. Thanks in advance.
    Best regards,
    Sameer

    Sameer,
    To me it appears that ADS is conencted to only backend ECC not to the portal system.
    Please try below:
    1. Launch WDA for HCMPF in SE80 with appropriate parameters and see if this displays interactive adobe form when you click in edit button.
    2. May be test the ADS connectivity to portal system.
    regards
    Sridhar Kandisetty

  • HCM Processes & Forms - Infotype 0008

    Hello,
    I am working on a scenario where a salary change is being done through HCM Processes & Forms. The salary that changes is in a wagetype (0001). There are other wage types that are also in infotype 8. How can I make sure that I can add more than 1 wage type in this scenario? Right now, if I only add one wagetype, it doesn't copy the wage types that are in the previous record (which is what I thought it would do).
    So, as an example:
    On date - 1 we have : 0001 - 4,000, 0100 - Indexed to full time salary, 0200 - indexed 12.50 %
    On date we have: 0001 - 4,200
    We want to have: 0001 - 4,200, 0100 and 0200 - 12.50%
    TIA
    Jaron Frenk

    Hi Chris,
    We have a similar requirement to update infotype 0041 records.
    I think you simply use the same field to pass to your service to different fields but you change the index for each time you use it. You can see this in the sample processes SAP provides.
    Could you explain a bit on the above ' index' ? What index are you referring to?
    Also, if possible could you reply with the sample processes in SAP which you were referring to?
    Thanks in advance,
    Deepa

  • HCM Processes & Forms PD Backend Service

    HCM Processes & Forms
    SAP_PD service (OM New Position Object IT1000, New Org. Unit Object(IT1000) and Relations between Position & Org. Unit(IT1001-A003 and/or A012 )
    --- OM Data Create Position Object and Create relation with already existing org. unit, process form shows u201CProcess Completedu201D.  When I check transaction log t-code : slg1 " The number indicated is not in any valid external interval" and " S 30117940 not found"
    This same case is working fine, if I removed the internal number range (just try), it is creating using SAP standard number range '5XXXXXXXX' , it has been created object  'S' and relation with 'S' - 'O'.
    I have created the process form with the following cases with internal number range is working fine.
    1) Create Position using SAP_PD standard OM service u2013only object
    2) Create Org. Unit using SAP_PD Service  -- only Object
    3) Using exisiting Org. Unit and Exisiting Position create relation  -- only relation.
    I am working a requirement same as Process: HR_PD_CREATE_POSITION but no hope.
    If anyone knows about the new object with relation, why internal number is not working or any configuration may I missed!!!
    Thanks & Regards
    SAMY
    Edited by: Ranganathan Pazhanisamy on Feb 1, 2011 8:35 AM

    Dear Sameer,
    The note 1098009 - Limitations for Web Dynpro ABAP doesn't say anything that you can't do.
    I made a brief analysis and didn't see any issue (regarding the note). Check it out in a more detailed manner to see if there isn't a limitation.
    I hope this has been useful.
    Kind Regards,
    Maurício.

  • Unable to test a FPM form based process in HCM Process & Forms ?

    Hi Experts,
    Am new to HCM Process & Forms, I created my first form on FPM and am trying to test it but am not able to do so.. can you all please help me figure out where I am going wrong.
    Here is what I am doing ...
    I have a build a FPM Form Scenario and Process. Now when I clicking on the Execute button in HRASR_DT and go the test screen I dont get the option for selecting the Web Dynpro Screen as Application Start Option.
    I also tried testing it through
    http://OURSERVER/sap/bc/webdynpro/sap/asr_process_execute_fpm?sap-language=EN&sap-wd-configId=ASR_EXECUTE_5_STEP_PA
    and
    http://OURSERVER/sap/bc/webdynpro/sap/asr_process_execute
    when I do this then I am getting an error message "No Internal Service Request scenario was specified".
    Please Advice.
    Thanks

    Hi Sahir,
    Yes, I had to Activate the business function HCM_ASR_CI_5 to get the "Option for Application Start" section in HRASR_DT.
    Thanks for the launchpad configuration link.
    The one think that I am still having issues is that if I goto se80 and selected the WD Application ASR_PROCESS_EXECUTE_OVP and using the Application configuration ASR_PROCESS_EXECUTE_OVP_CFG I execute it by clicking on Test....I get an error message saying
    "Process does not exist"
    Does this mean I can't test my process through se80 I will always have to go through portal and configure the launchpad to test my process ?
    Or am I missing some config or doing something wrong ?
    Regards
    Chayan

  • Need logic for calculate the balance quantity in open sales order

    hi all
    i need logic to calcuclate the balance quantity in open sales order ,
    where i am using VBAK header and VBAP item , and VBFA for document flow tables
    i need to have the balance quantity , for the open sales order
    especially taking with respect to  VBFA-VBTYP_N = M for invoice creation and N for canellation
    any one please help me

    thank you but i am clear abt it
    will you please anyother way to calucaluate the logic ,
    and i need to populate in bukets also for the terms of 5 years
    Edited by: sridhar loganathan on Nov 25, 2008 6:43 AM

  • How to Handle the error message?

    Hi,
    Can any one help me in handling the error messages in application,
    In my application, I am having 2 buttons, one is display button, and the other is reset button. When we enter wrong inputs, it prompts an error message and again we I click on reset button the application goes back to its normal stage i.e. the error message will be disappears. These things will happen in the same page. I have tryed to know the any Id/Name of error message.
    So please help to handle error and skip that error then continue execute raming code.
    Thanks
    Buntty

    A few problems with this question that need clarification:
    You're using a GUI, but we have no way of knowing which one -- Swing? AWT? SWT? other?
    You ask how to fix your program flow and logic but don't show us the current state. Most of us can't read minds so a bit of code would be nice here.
    You mention "Page". What context is this in?
    A great resource that has helped me and will probably help you is an article entitled [How To Ask Questions The Smart Way|http://www.catb.org/~esr/faqs/smart-questions.html] . It will tell you how to formulate your questions so that the folks here will be better able to answer them. Good luck.

  • BPEL Transaction Inactive : Instance terminated without handling the Error

    Hi All,
         I have a BPEL process which uses XA transaction to insert data in MS SQL Server table.
    When I try to insert "out of range date value", it errs out as expected, but the transaction terminates without proceeding for the error handling part. I even tried disabling the idempotent option for the DB adapter, still the process terminates without error handling.
    Kindly guide me how I can overcome transaction inactive issue and handle the error in the catch all block.
    Thanks in advance.
    The error message is as follows,
    "Error Message: {http://schemas.oracle.com/bpel/extension}runtimeFault
    Non Recoverable System Fault :
    < bpelFault><faultType>0</faultType><runtimeFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="summary"><summary>JTA transaction is not in active state. The transaction became inactive when executing activity "" for instance "130,047", bpel engine can not proceed further without an active transaction. please debug the invoked subsystem on why the transaction is not in active status. the transaction status is "MARKED_ROLLBACK". The reason was The execution of this instance "130047" for process "SyncAggregateSpendABCSImpl" is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK", the underlying exception is "BINDING.JCA-12563 Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'insert' failed due to: DBWriteInteractionSpec Execute Failed Exception. insert failed. Descriptor name: [LoadCmpAggSpendStage.SapTable]. Caused by java.sql.BatchUpdateException: The conversion of a datetime2 data type to a datetime data type resulted in an out-of-range value.. Please see the logs for the full DBAdapter logging output prior to this exception. This exception is considered not retriable, likely due to a modelling mistake. To classify it as retriable instead add property nonRetriableErrorCodes with value "-242" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. " . Consult the system administrator regarding this error.< /summary></part><part name="detail"><detail>ORABPEL-02199 JTA transaction is not in active state. The transaction became inactive when executing activity "" for instance "130,047", bpel engine can not proceed further without an active transaction. please debug the invoked subsystem on why the transaction is not in active status. the transaction status is "MARKED_ROLLBACK". The reason was The execution of this instance "130047" for process "SyncAggregateSpendABCSImpl" is supposed to be in an active jta transaction, the current transaction status is "MARKED_ROLLBACK", the underlying exception is "BINDING.JCA-12563 Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'insert' failed due to: DBWriteInteractionSpec Execute Failed Exception. insert failed. Descriptor name: [LoadCmpAggSpendStage.SapTable]. Caused by java.sql.BatchUpdateException: The conversion of a datetime2 data type to a datetime data type resulted in an out-of-range value.. Please see the logs for the full DBAdapter logging output prior to this exception. This exception is considered not retriable, likely due to a modelling mistake. To classify it as retriable instead add property nonRetriableErrorCodes with value "-242" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. " . Consult the system administrator regarding this error. at com.oracle.bpel.client.util.TransactionUtils.throwExceptionIfTxnNotActive(TransactionUtils.java:107) at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:356) at com.collaxa.cube.engine.ext.common.InvokeHandler.__invoke(InvokeHandler.java:1099) at com.collaxa.cube.engine.ext.common.InvokeHandler.handleNormalInvoke(InvokeHandler.java:594) at com.collaxa.cube.engine.ext.common.InvokeHandler.handle(InvokeHandler.java:132) at com.collaxa.cube.engine.ext.bpel.common.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:74) at com.collaxa.cube.engine.ext.bpel.common.wmp.BaseBPELActivityWMP.perform(BaseBPELActivityWMP.java:173) at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:2718) at com.collaxa.cube.engine.CubeEngine._handleWorkItem(CubeEngine.java:1197) at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1100) at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:76) at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:251) at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:330) at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:4652) at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:4583) at com.collaxa.cube.engine.CubeEngine._createAndInvoke(CubeEngine.java:714) at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:559) at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:531) at com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(CubeDeliveryBean.java:319) at sun.reflect.GeneratedMethodAccessor16515.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149) at com.oracle.pitchfork.intercept.MethodInvocationInvocationContext.proceed(MethodInvocationInvocationContext.java:103) at oracle.security.jps.ee.ejb.JpsAbsInterceptor$1.run(JpsAbsInterceptor.java:113) at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:324) at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:460) at oracle.security.jps.ee.ejb.JpsAbsInterceptor.runJaasMode(JpsAbsInterceptor.java:100) at oracle.security.jps.ee.ejb.JpsAbsInterceptor.intercept(JpsAbsInterceptor.java:154) at oracle.security.jps.ee.ejb.JpsInterceptor.intercept(JpsInterceptor.java:113) at sun.reflect.GeneratedMethodAccessor1671.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310) at com.oracle.pitchfork.intercept.JeeInterceptorInterceptor.invoke(JeeInterceptorInterceptor.java:68) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131) at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at com.oracle.pitchfork.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:34) at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:54) at com.oracle.pitchfork.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:42) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131) at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at $Proxy368.handleInvoke(Unknown Source) at com.collaxa.cube.engine.ejb.impl.bpel.BPELDeliveryBean_5k948i_ICubeDeliveryLocalBeanImpl.__WL_invoke(Unknown Source) at weblogic.ejb.container.internal.SessionLocalMethodInvoker.invoke(SessionLocalMethodInvoker.java:39) at com.collaxa.cube.engine.ejb.impl.bpel.BPELDeliveryBean_5k948i_ICubeDeliveryLocalBeanImpl.handleInvoke(Unknown Source) at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:30) at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:141) at com.collaxa.cube.engine.dispatch.BaseDispatchTask.process(BaseDispatchTask.java:89) at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:65) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at com.collaxa.cube.engine.dispatch.Dispatcher$ContextCapturingThreadFactory$2.run(Dispatcher.java:933) at java.lang.Thread.run(Thread.java:662) Caused by: oracle.fabric.common.FabricInvocationException: BINDING.JCA-12563 Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'insert' failed due to: DBWriteInteractionSpec Execute Failed Exception. insert failed. Descriptor name: [LoadCmpAggSpendStage.SapTable]. Caused by java.sql.BatchUpdateException: The conversion of a datetime2 data type to a datetime data type resulted in an out-of-range value.. Please see the logs for the full DBAdapter logging output prior to this exception. This exception is considered not retriable, likely due to a modelling mistake. To classify it as retriable instead add property nonRetriableErrorCodes with value "-242" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. at oracle.integration.platform.blocks.adapter.fw.jca.cci.EndpointInteractionException.getFabricInvocationException(EndpointInteractionException.java:75) at oracle.integration.platform.blocks.adapter.AdapterReference.getFabricInvocationException(AdapterReference.java:316) at oracle.integration.platform.blocks.adapter.AdapterReference.request(AdapterReference.java:219) at oracle.integration.platform.blocks.mesh.SynchronousMessageHandler.doRequest(SynchronousMessageHandler.java:139) at oracle.integration.platform.blocks.mesh.MessageRouter.request(MessageRouter.java:182) at oracle.integration.platform.blocks.mesh.MeshImpl.request(MeshImpl.java:190) at sun.reflect.GeneratedMethodAccessor2127.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149) at oracle.integration.platform.metrics.PhaseEventAspect.invoke(PhaseEventAspect.java:71) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at $Proxy386.request(Unknown Source) at oracle.fabric.CubeServiceEngine.requestToMesh(CubeServiceEngine.java:858) at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:267) ... 61 more Caused by: BINDING.JCA-12563 Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'insert' failed due to: DBWriteInteractionSpec Execute Failed Exception. insert failed. Descriptor name: [LoadCmpAggSpendStage.SapTable]. Caused by java.sql.BatchUpdateException: The conversion of a datetime2 data type to a datetime data type resulted in an out-of-range value.. Please see the logs for the full DBAdapter logging output prior to this exception. This exception is considered not retriable, likely due to a modelling mistake. To classify it as retriable instead add property nonRetriableErrorCodes with value "-242" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAInteractionInvoker.executeJcaInteraction(JCAInteractionInvoker.java:486) at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAInteractionInvoker.invokeJcaReference(JCAInteractionInvoker.java:572) at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAInteractionInvoker.invokeSyncJcaReference(JCAInteractionInvoker.java:545) at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAEndpointInteraction.performSynchronousInteraction(JCAEndpointInteraction.java:547) at oracle.integration.platform.blocks.adapter.AdapterReference.request(AdapterReference.java:179) ... 76 more Caused by: BINDING.JCA-11616 DBWriteInteractionSpec Execute Failed Exception. insert failed. Descriptor name: [LoadCmpAggSpendStage.SapTable]. Caused by java.sql.BatchUpdateException: The conversion of a datetime2 data type to a datetime data type resulted in an out-of-range value.. Please see the logs for the full DBAdapter logging output prior to this exception. This exception is considered not retriable, likely due to a modelling mistake. To classify it as retriable instead add property nonRetriableErrorCodes with value "-242" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers. at oracle.tip.adapter.db.exceptions.DBResourceException.createNonRetriableException(DBResourceException.java:698) at oracle.tip.adapter.db.exceptions.DBResourceException.createEISException(DBResourceException.java:664) at oracle.tip.adapter.db.exceptions.DBResourceException.outboundWriteException(DBResourceException.java:712) at oracle.tip.adapter.db.DBInteraction.executeOutboundWrite(DBInteraction.java:1117) at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:247) at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAInteractionInvoker.executeJcaInteraction(JCAInteractionInvoker.java:357) ... 80 more Caused by: java.sql.BatchUpdateException: The conversion of a datetime2 data type to a datetime data type resulted in an out-of-range value. at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeBatch(SQLServerPreparedStatement.java:1178) at weblogic.jdbc.wrapper.PreparedStatement.executeBatch(PreparedStatement.java:210) at org.eclipse.persistence.internal.databaseaccess.DatabasePlatform.executeBatch(DatabasePlatform.java:2101) at org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.executeBatchedStatements(ParameterizedSQLBatchWritingMechanism.java:144) at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeCall(DatabaseAccessor.java:535) at org.eclipse.persistence.internal.sessions.AbstractSession.basicExecuteCall(AbstractSession.java:1717) at org.eclipse.persistence.sessions.server.ClientSession.executeCall(ClientSession.java:253) at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:207) at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:193) at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeSelectCall(DatasourceCallQueryMechanism.java:264) at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.executeSelect(DatasourceCallQueryMechanism.java:246) at org.eclipse.persistence.queries.DataReadQuery.executeNonCursor(DataReadQuery.java:197) at org.eclipse.persistence.queries.DataReadQuery.executeDatabaseQuery(DataReadQuery.java:152) at org.eclipse.persistence.queries.DataReadQuery.execute(DataReadQuery.java:137) at org.eclipse.persistence.internal.sessions.AbstractSession.internalExecuteQuery(AbstractSession.java:2831) at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1516) at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1498) at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1449) at org.eclipse.persistence.sequencing.QuerySequence.select(QuerySequence.java:309) at org.eclipse.persistence.sequencing.QuerySequence.updateAndSelectSequence(QuerySequence.java:254) at org.eclipse.persistence.sequencing.StandardSequence.getGeneratedValue(StandardSequence.java:62) at org.eclipse.persistence.sequencing.DefaultSequence.getGeneratedValue(DefaultSequence.java:145) at org.eclipse.persistence.sequencing.Sequence.getGeneratedValue(Sequence.java:225) at org.eclipse.persistence.internal.sequencing.SequencingManager$NoPreallocation_State.getNextValue(SequencingManager.java:677) at org.eclipse.persistence.internal.sequencing.SequencingManager.getNextValue(SequencingManager.java:1067) at org.eclipse.persistence.internal.sequencing.ClientSessionSequencing.getNextValue(ClientSessionSequencing.java:70) at org.eclipse.persistence.internal.descriptors.ObjectBuilder.assignSequenceNumber(ObjectBuilder.java:355) at org.eclipse.persistence.internal.queries.DatasourceCallQueryMechanism.insertObject(DatasourceCallQueryMechanism.java:351) at org.eclipse.persistence.internal.queries.StatementQueryMechanism.insertObject(StatementQueryMechanism.java:163) at org.eclipse.persistence.internal.queries.StatementQueryMechanism.insertObject(StatementQueryMechanism.java:178) at org.eclipse.persistence.internal.queries.DatabaseQueryMechanism.insertObjectForWrite(DatabaseQueryMechanism.java:475) at org.eclipse.persistence.queries.InsertObjectQuery.executeCommit(InsertObjectQuery.java:80) at org.eclipse.persistence.queries.InsertObjectQuery.executeCommitWithChangeSet(InsertObjectQuery.java:91) at org.eclipse.persistence.internal.queries.DatabaseQueryMechanism.executeWriteWithChangeSet(DatabaseQueryMechanism.java:287) at org.eclipse.persistence.queries.WriteObjectQuery.executeDatabaseQuery(WriteObjectQuery.java:58) at org.eclipse.persistence.queries.DatabaseQuery.execute(DatabaseQuery.java:844) at org.eclipse.persistence.queries.DatabaseQuery.executeInUnitOfWork(DatabaseQuery.java:743) at org.eclipse.persistence.queries.ObjectLevelModifyQuery.executeInUnitOfWorkObjectLevelModifyQuery(ObjectLevelModifyQuery.java:108) at org.eclipse.persistence.queries.ObjectLevelModifyQuery.executeInUnitOfWork(ObjectLevelModifyQuery.java:85) at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.internalExecuteQuery(UnitOfWorkImpl.java:2871) at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1516) at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1498) at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1449) at org.eclipse.persistence.internal.sessions.CommitManager.commitNewObjectsForClassWithChangeSet(CommitManager.java:224) at org.eclipse.persistence.internal.sessions.CommitManager.commitAllObjectsWithChangeSet(CommitManager.java:123) at org.eclipse.persistence.internal.sessions.AbstractSession.writeAllObjectsWithChangeSet(AbstractSession.java:3800) at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitToDatabase(UnitOfWorkImpl.java:1416) at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitToDatabaseWithChangeSet(UnitOfWorkImpl.java:1505) at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.writeChanges(UnitOfWorkImpl.java:5502) at oracle.tip.adapter.db.DBInteraction.executeOutboundWrite(DBInteraction.java:927) at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:247) at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAInteractionInvoker.executeJcaInteraction(JCAInteractionInvoker.java:357) at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAInteractionInvoker.invokeJcaReference(JCAInteractionInvoker.java:572) at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAInteractionInvoker.invokeSyncJcaReference(JCAInteractionInvoker.java:545) at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAEndpointInteraction.performSynchronousInteraction(JCAEndpointInteraction.java:547) at oracle.integration.platform.blocks.adapter.AdapterReference.request(AdapterReference.java:179) at oracle.integration.platform.blocks.mesh.SynchronousMessageHandler.doRequest(SynchronousMessageHandler.java:139) at oracle.integration.platform.blocks.mesh.MessageRouter.request(MessageRouter.java:182) at oracle.integration.platform.blocks.mesh.MeshImpl.request(MeshImpl.java:190) at sun.reflect.GeneratedMethodAccessor2127.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149) at oracle.integration.platform.metrics.PhaseEventAspect.invoke(PhaseEventAspect.java:71) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at $Proxy386.request(Unknown Source) at oracle.fabric.CubeServiceEngine.requestToMesh(CubeServiceEngine.java:862) at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:267) at com.collaxa.cube.engine.ext.common.InvokeHandler.__invoke(InvokeHandler.java:1099) at com.collaxa.cube.engine.ext.common.InvokeHandler.handleNormalInvoke(InvokeHandler.java:594) at com.collaxa.cube.engine.ext.common.InvokeHandler.handle(InvokeHandler.java:132) at com.collaxa.cube.engine.ext.bpel.common.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:75) at com.collaxa.cube.engine.ext.bpel.common.wmp.BaseBPELActivityWMP.perform(BaseBPELActivityWMP.java:173) at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:2718) at com.collaxa.cube.engine.CubeEngine._handleWorkItem(CubeEngine.java:1197) at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1100) at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:78) at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:251) at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:330) at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:4652) at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:4584) at com.collaxa.cube.engine.CubeEngine._createAndInvoke(CubeEngine.java:714) at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:559) at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:531) at com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(CubeDeliveryBean.java:319) at sun.reflect.GeneratedMethodAccessor16515.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149) at com.oracle.pitchfork.intercept.MethodInvocationInvocationContext.proceed(MethodInvocationInvocationContext.java:103) at oracle.security.jps.ee.ejb.JpsAbsInterceptor$1.run(JpsAbsInterceptor.java:113) at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:324) at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:460) at oracle.security.jps.ee.ejb.JpsAbsInterceptor.runJaasMode(JpsAbsInterceptor.java:100) at oracle.security.jps.ee.ejb.JpsAbsInterceptor.intercept(JpsAbsInterceptor.java:154) at oracle.security.jps.ee.ejb.JpsInterceptor.intercept(JpsInterceptor.java:113) at sun.reflect.GeneratedMethodAccessor1671.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310) at com.oracle.pitchfork.intercept.JeeInterceptorInterceptor.invoke(JeeInterceptorInterceptor.java:68) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131) at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at com.oracle.pitchfork.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:34) at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:54) at com.oracle.pitchfork.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:42) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131) at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119) at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at $Proxy368.handleInvoke(Unknown Source) at com.collaxa.cube.engine.ejb.impl.bpel.BPELDeliveryBean_5k948i_ICubeDeliveryLocalBeanImpl.__WL_invoke(Unknown Source) at weblogic.ejb.container.internal.SessionLocalMethodInvoker.invoke(SessionLocalMethodInvoker.java:39) at com.collaxa.cube.engine.ejb.impl.bpel.BPELDeliveryBean_5k948i_ICubeDeliveryLocalBeanImpl.handleInvoke(Unknown Source) at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:30) at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:141) at com.collaxa.cube.engine.dispatch.BaseDispatchTask.process(BaseDispatchTask.java:89) at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:66) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:909) ... 2 more< /detail></part><part name="code"><code>com.collaxa.cube.engine.EngineException</code></part></runtimeFault></bpelFault>"

    Hello,
    You can't catch the roll back exception directly. It will rollback your transaction and because of that it will not get in the catch block.
    To solve this you can create a new BPEL to do the DB insert. Invoke that BPEL with a new transaction. Catch the Database error in the first BPEL
    Example:
      <component name="InsertData" version="2.0">
        <implementation.bpel src="InsertData.bpel"/>
        <property name="bpel.config.transaction">requiresNew</property>
        <property name="bpel.config.inMemoryOptimization">false</property>
        <property name="bpel.config.completionPersistPolicy">On</property>
      </component>
    In this example I have all my logic in the "SyncSypplierMaster" and then I invoke the BPEL "InsertData" (with the property <property name="bpel.config.transaction">requiresNew</property>) to insert in the database. I catch the error in the "SyncSypplierMaster" BPEL where I have the "InsertData" invocation.
    This works because SyncSypplierMaster" is in a different transaction.
    Note: If you are inserting in multiple tables and the error is in a child table you will not catch the DB error message also. If this is your case, I recommend you to investigate what is the patch required to solve this problem.
    Best Regards,
    Daniel Dias

  • How to run 3 job(a,b,c) parallel in unix shells script and after will complete d will start  and we have to handle the error also

    how to run 3 job(a,b,c) parallel in unix shells script and after will complete d will start  and we have to handle the error also

    032ee1bf-8007-4d76-930e-f77ec0dc7e54 wrote:
    how to run 3 job(a,b,c) parallel in unix shells script and after will complete d will start  and we have to handle the error also
    Please don't overwhelm us with so many details!  
    Just off the top of my head ... as a general approach ... something like
    nohup proca
    nohup procb
    nohup procc
    while (some condition checking that all three procs are still running ... maybe a ps -ef |grep  )
    do
    sleep 2
    done
    procd
    But, we'd really need to know what it is you are really trying to accomplish, instead of your pre-conceived solution.

  • Is there any blog or examples to handle the errors without using ESB tool kit.

    Hello,
    I have been trying to work with error handling since last week but I dont understand how to construct the error message. Is there any blog or examples to explain handle the errors step by step from scratch without using ESB tool kit.Can anybody help me out.
    Thanks in advance.

    You can use option 3 to construct the error message inside orchestration.
    Before using a BizTalk XML Message inside an orchestration, it must first be constructed. In fact this is just populating the message with XML. If there is an attempt to use this message before it is constructed, the above error will come. Some messages
    come pre-constructed, such as messages that originate from a send port
    There are several ways to construct a message inside an orchestration:
    Create a new message from an existing message using BizTalk map
    Assign one message to other(i.e. creating a copy of an existing message)
    Creating a message with the help of a System.XML.XMLDocument variable
    We have to first declare an orchestration variable of type XmlDocument. Then in a message assignment shape, we need to do something like this:
    myxmlDoc = new XmlDocument();
    myxmlDoc.LoadXML("<somexmlhere></somexmlhere>")
    myMsgBeingConstructed = myxmlDoc;
    Abhijit Mahato - Microsoft Community Contributor 2011 - MCTS BizTalk Server blog: http://abhijitmahato.wordpress.com/ Please "Mark as Answer" if Post has Answered the Question

  • How to handle the #error in ssrs expression

    hi 
    Please any one help me to resolve this #error ,
    I have a calculated filed in that expression i given a if condition like below 
    data of column is coming like this 0 , 0.0 
    =IIF(Fields!Column1.Value=0,0,((Fields!Column2.Value - Fields!Column1.Value)/( Fields!Column1.Value)))
    how to handle the #error 
    Please let me know any one 

    Hi deepuk23,
    According to your description, when you use the IIF() function in the report you got some error,right?
    The issue can be caused by the column1 and column2 have different datatype, I assumed that one is integer and another is float, when the Column1 is 0 or null,  because IIF() function always evaluates both the true part and the false part, even
    though it returns only one of them, it will throw out the error. 
    To resolve the issue, you should use a nested IIF() function to avoid the zero-divisor in any rate like below:
    =IIF(Fields!Column1.Value=0,0,((Fields!Column2.Value - Fields!Column1.Value)/(IIF(Fields!Column1.Value=0,1,Fields!Column1.Value))))
    For more information, please refer to this article:
    FAQ: Why does the “Attempted to divide by zero” error still happen?
    If you still have any problem, please feel free to ask.
    Regards,
    Vicky Liu
    Vicky Liu
    TechNet Community Support

Maybe you are looking for