Display detail exception message in af:messages

Hi!
I'm using ADF BC 10.1.3.3. I've created a backing bean event that calls Row.validate() method since before I call commit I want to ensure all the validation is passed or else the user is redirected to another page without committing the changes. Well, after the Row.validate call I'm catching the exception. But the problem I'm facing is that I'd like to display the detailed message of the exception caught which holds the actual validation message I defined on the model layer. If I use only Exception.getMessage() I receive the JBO-27024: Failed to validate a row with... message.
But using the Exception.printStackTrace I can see in JDeveloper output console something like this:
oracle.jbo.RowValException: JBO-27024:
+...+
+     at java.lang.Thread.run(Thread.java:595)+
+## Detail 0 ##+
oracle.jbo.RowValException: THE ACTUAL VALIDATION MESSAGE I DEFINED ON MODEL LAYER
+     at oracle.jbo.rules.RulesBeanUtils.raiseException(RulesBeanUtils.java:206)+
+...+
Is there a way I could get the message from Detail 0 in my Catch block in the backing bean? I thought that using getStackTrace could help but there are only records to "+at java.lang.Thread.run(Thread.java:595)+" and not from Detail 0 part.
I hope my question is clear and maybe there is another approach to achieve this.
I'm doing it this way since the jspx opened doesn't consists of all the attributes from the VO's row but the validation on the Model layer is executed on those attributes anyway. So I need to display a massage that the process can't be completed and it would be very nice to display the actual problem instead of the JBO-27024 message.
Thank you in advance,
regards!
BB

Thanks John,
I was catching all exceptions and Exception class doesn't have any appropriate methods. Catching RowValException I'm able to get reference to all detail exceptions.
Regards!

Similar Messages

  • User exit/BAdI to manipulate display (MRP) Exception messages

    Dear,
    I wonder if there is a user exit/BAdI or implicit enhancement with which I can manipulate the display (or not) of (MRP) Exception messages in MD04/MD07.
    In customizing of the Exception messages (table V458A) there is the indicator No exception message (V485A-ASNOT) but if this indicator is ticked, the Exception message is never displayed;
    My client wants this message only not to be displayed in case the Material is of a certain Material group.
    In all other cases, the Exception message should be displayed.
    Thanks for any clues!
    Kind regards,
    Bart

    Hi Bart
    There is no exit or BAdI to manipulate exception messages in MRP. See the following note:
    1697703
    MD04/MD05: Change or create new exception messages
    You can find a list of the most relevant BAdIs available for MRP on the following document:
    BAdIs for MRP
    BR
    Caetano

  • TFS Build Error - Exception Message: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters

    I am trying to set-up CI of Orchard CMS and deploy it on Azure using TF service. I am stuck at following error for path being
    longer than 260 characters. However, when counted the total characters in path are 235. Please see the below error :
    Other Errors and Warnings
    1 error(s), 1 warning(s)
    Exception Message: TF400889: The following path contains more than the allowed 259 characters: drop/_PublishedWebsites/Orchard.Web_Package/Archive/Content/C_C/a/src/projects/Orchard/dev/DevAltaf/Orchard/src/Orchard.Web/obj/Debug/Package/PackageTmp/Modules/BrentApart.BannerManager/Scripts/controllers/bannerAssignmentController.js. Specify a shorter path. (type VssServiceException)
    Exception Stack Trace: at Microsoft.TeamFoundation.Build.Workflow.Activities.FileContainerDropProvider.EndCopyDirectory(IAsyncResult result)
    at Microsoft.TeamFoundation.Build.Workflow.Activities.CopyDirectory.EndExecute(AsyncCodeActivityContext context, IAsyncResult result)
    at System.Activities.AsyncCodeActivity.CompleteAsyncCodeActivityData.CompleteAsyncCodeActivityWorkItem.Execute(ActivityExecutor executor, BookmarkManager bookmarkManager)
    Inner Exception Details:
    Exception Message: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters. (type PathTooLongException)
    Did anyone came across such issue while deploying Orchard on Azure with TF service? If yes, how did you sort this freaking error?
    Thanks,
    Altaf B.

    Hi AltafB,
    For your situation, you can short the path for the source code. Or use a short path for build agent folder in your build definition. You can refer to the links below to solve your problem:
    http://blogs.msdn.com/b/aaronhallberg/archive/2007/06/20/team-build-and-260-character-paths.aspx
    https://social.msdn.microsoft.com/Forums/vstudio/en-US/1638a5f0-9321-4ff9-9ee7-6d347badb972/please-some-solution-to-the-specified-path-file-name-or-both-are-too-long?forum=tfsbuild
    Besides, since you deploy Orchard to Azure, you can also publish it directly using publish profile in Visual Stduio or WebMatrix directly.
    Best regards,
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • How to show exception messages in Terminal

    Hi all,
    I use clang-3.1 in C++11 mode, with -stdlib=libc++, without any IDE, just on the command line.
    My problem is: my c++ code is expected to throw exceptions (I'm testing it), but the Terminal does not print out the exception messages. Instead of my nice exception messages (which I see with clang-3.1 on linux), I have things like: "terminate called throwing an exceptionAbort trap:"
    How should I act on the environment of the code to display those exception messages? I don't want to change the code.
    Many thanks,
    Best regards,
    Romain

    You are posting in a user forum. Probably the vast majority of the people here don't have the foggiest idea what you are talking about. Post in the Developer forum.

  • Exception Message Numner in transaction MD04

    Hello,
    There is a field Exception Message Number on screen of transaction MD04.
    On my report i need to display the exception message number for corresponding MRP data element.
    Which tables do i need to access and the flow?
    regards
    Nishant
    PS : points would be awarded for helpful answers

    Hi,
    Just a modification to Mr. DB49's input. Increase the stock of the account assigned material to the needed qty & system will put an exception message '26' for the production order.
    Eg:
    Date               MRP ele       MRP element data                                    Mrp excep      receipt         av. qty
    2010/01/05     ProjSt     20xx.0001.02               15      15         
    2010/01/25     PrdOrd     0000129365/PP01          26     15      30      
    2010/01/25     IndReq     VSFB                                     15-               15         
    Regards,
    Vivek

  • MRP exception message configuration in SPRO

    Hi all,
    Please advise where we can do configuration settings of exception message in SPRO.

    Please check the first link of my post. Path and usefull info is mentioned there:
    MRP exception message:
    spro -> pp -> mrp -> evaluation -> exception messages -> define & group exception messages.
    Define and Group Exception Messages
    In this step, you define the following parameters for exception messages:
    Whether exception messages are displayed for particular exception situations
    If a particular exception message is not relevant to your company, select the field No exception message. In the planning run, this exception message is then no longer created for this situation.
    The priority in which exception messages are to be displayed
    If several exception messages exist for one MRP element, you can assign priorities to determine which exception message is to be displayed in the MRP evaluations. The system always displays the exception message with the highest priority directly in the list. The exception message selected with the next highest priority can be displayed in the list by accessing the additional data.
    You enter the priority of the exception messages in the field entitled Excep.mssge priority.
    You can see the sequence of priorities by selecting the possible entries pushbutton on the input field. Thus, you can gain an overview of the previous sequence of the exception messages. The exception messages with the higher number also has higher priority.
    How exception messages are grouped to exception groups
    For the collective display of the MRP list and the stock/requirements list, as well as for all material lists created as a result of the single-item, multi-level planning run, exception messages are grouped into exception groups. In the standard system, a grouping exists that you can change, if necessary, in the field entitled Selection group. You can adapt the long text of the exception group in the step Check Exception Group Texts.
    Depending on which exception messages MRP lists are created
    In the initial screen of the planning run as well as in in the MRP group, you can define that the system is only to create an MRP list if certain exceptional situations exist (creation indicator "Create MRP list - depending on exception messages"). The exception messages that lead to the creation of the MRP list are selected in the field entitled Create MRP list.
    Actions
    1. Define whether the exception message is set.
    2. Define the priority of the exception message.
    3. If necessary, change the exception groups.
    4. If necessary, select the exception for the creation of the MRP lists depending on the exception messages.
    Edited by: Afshad Irani on Jun 3, 2010 4:27 PM

  • PFCG display details No technical details available

    Hi abbapers,
    I want view the transaccions of menu,
    In t-code PFCG go to tab Menu, right button on t-code and obtain message error No technical details available
    Can you help me, please?
    Cordial greetings.

    thank at all for your attention,
    Sabyasachi Rudra, is possible that change the node text by other name, I´m not sure.
    I want view the t-code associated to menu, then when right button on several when push display details, obtain message error No technical details available.
    In this case, I execute the option, then go to system ... status. Then with the name t-code, go to table TSTC (se16), and search name program corresponding of the t-code.
    If I view in the field text that it is IMG Activity. Is this the reason when appear the message error No technical details available. ?
    In this case if go to the se80 with the name program SAPLS_CUS_IMG_ACTIVITY (FunctionPool) that is the same that others options of the menu too.
    If go to left window on Dictionary Structures, Are used others names tables in the IMG ACTIVITY ?
    I want obtain name of tables that are used in t-code Can you help me please?
    Thank you very much.
    Cordial greetings.

  • Exception Message: TF270015: 'MSBuild.exe' returned an unexpected exit code. Expected '0'; actual '1'. See the build logs for more details. (type UnexpectedExitCodeException)

    Hi all,
    I have TFS2012 and run several projects.
    We encounterwed with such an error while using Build server.
    Overall Build Process
    Initial Property Values
    AgentSettings = Use agent where Name=* and Tags is empty; Max Wait Time: 04:00:00
    BinariesSubdirectory = 
    ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
    DoNotDownloadBuildType = False
    LogFilePerProject = False
    MSBuildArguments = 
    MSBuildPlatform = Auto
    RecursionType = OneLevel
    SourcesSubdirectory = 
    TestResultsSubdirectory = 
    Verbosity = Diagnostic
    00:00
    Get the Build
    00:00
    Update Build Number
    Initial Property Values
    BuildNumberFormat = $(BuildDefinitionName)_$(Date:yyyyMMdd)$(Rev:.r)
    Final Property Values
    BuildNumberFormat = $(BuildDefinitionName)_$(Date:yyyyMMdd)$(Rev:.r)
    Result = Ephone_DIT_Deploy_20150424.1
    01:56
    Run On Agent (reserved build agent U4VMDWODBDEV03 - Agent1)
    Initial Property Values
    MaxExecutionTime = 00:00:00
    MaxWaitTime = 04:00:00
    ReservationSpec = Name=*, Tags=
    00:00
    Get the Build Directory
    Initial Property Values
    Result = d:\temp\217\CTI\Ephone_DIT_Deploy
    01:53
    If Not String.IsNullOrEmpty(ConfigurationFolderPath)
    Initial Property Values
    Condition = True
    01:53
    Run TfsBuild for Configuration Folder
    Initial Property Values
    BinariesSubdirectory = 
    BuildDirectory = d:\temp\217\CTI\Ephone_DIT_Deploy
    CommandLineArguments = 
    ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
    DoNotDownloadBuildType = False
    LogFilePerProject = False
    MaxProcesses = 1
    NodeReuse = False
    RecursionType = OneLevel
    SourcesSubdirectory = 
    TargetsNotLogged = 
    TestResultsSubdirectory = 
    ToolPath = 
    ToolPlatform = Auto
    Verbosity = Diagnostic
    C:\Windows\Microsoft.NET\Framework64\v4.0.30319\MSBuild.exe /nologo /noconsolelogger "d:\temp\217\CTI\Ephone_DIT_Deploy\BuildType\TFSBuild.proj" /m:1 /nr:False "@d:\temp\217\CTI\Ephone_DIT_Deploy\BuildType\TfsBuild.rsp" 
    00:08
    Getting sources
    00:02
    Labeling sources
    00:19
    Built $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT/TFSBuild.proj for target(s) CompileConfiguration.
    00:19
    Built $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT/TFSBuild.proj for target(s) CompileSolution.
    00:19
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.sln for default targets.
    00:05
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
    00:01
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:10
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:01
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.Proxy/Communications.Protocol.Proxy.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS/Communications.Protocol.CTIOS.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone.DelphiCallConn/Communications.Protocol.DelphiCallConn.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
    00:05
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:02
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
     CSC: Assembly generation -- Referenced assembly 'System.EnterpriseServices.dll' targets a different processor
     CSC: Assembly generation -- Referenced assembly 'System.Web.dll' targets a different processor
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
     CSC: Assembly generation -- Referenced assembly 'System.EnterpriseServices.dll' targets a different processor
     CSC: Assembly generation -- Referenced assembly 'System.Web.dll' targets a different processor
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
     C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll",
    "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
    a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
    00:02
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Workflow/EPhone.Workflow.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
    00:01
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneReporting/EPhoneReporting.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
     C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.DataModel.dll",
    "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
    a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
     C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll",
    "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
    a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
     C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.DataModel.dll",
    "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
    a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
     C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll",
    "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
    a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
     C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Workflow.Targets (121): Compilation failed. Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneReporting/EPhoneReporting.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneCallback/EPhoneCallback.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Workflow/EPhone.Workflow.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS/Communications.Protocol.CTIOS.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone.DelphiCallConn/Communications.Protocol.DelphiCallConn.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.Proxy/Communications.Protocol.Proxy.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneReporting/EPhoneReporting.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Workflow/EPhone.Workflow.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneCallback/EPhoneCallback.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneUserControl/EPhoneUserControl.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneMarcomApplication/EPhoneMarcomApplication.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneUserControl/EPhoneUserControl.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneCallbackApplication/EPhoneCallbackApplication.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneUserControl/EPhoneUserControl.csproj for default targets.
    00:02
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneQueView/EPhoneQueView.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
     C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.DataModel.dll",
    "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
    a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
     C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll",
    "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
    a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests/Ephone.Tests.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests.CallGenerator/EPhone.Tests.CallGenerator.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS.TestRunner/Communications.Protocol.CTIOS.TestRunner.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS.TestRunner/Communications.Protocol.CTIOS.TestRunner.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests.CallGenerator/EPhone.Tests.CallGenerator.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests.Runner/Ephone.Tests.Runner.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests/Ephone.Tests.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneIDD/EPhoneIDD.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegratorTest/ChannelIntegratorTest.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
    MSBuild Log File
    00:08
    Generating list of changesets
    00:20
    Built Skins\SkinEPhone.cs for default targets.
     Skins\SkinEPhone.cs (3838): The member 'EPhone.SkinEPhone._txtOrderNumber_TextChanged(object, System.EventArgs)' does not hide an inherited member. The new keyword is not required. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneUserControl\EPhoneUserControl.csproj]
     C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "microsoft.vbe.interop". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
     C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "stdole". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
     C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (4513): Item 'Microsoft.Net.Framework.3.5' could not be located in 'C:\Program Files (x86)\Microsoft SDKs\Windows\v8.0A\Bootstrapper\'. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
     Skins\SkinEPhone.cs (3838): The member 'EPhone.SkinEPhone._txtOrderNumber_TextChanged(object, System.EventArgs)' does not hide an inherited member. The new keyword is not required. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneUserControl\EPhoneUserControl.csproj]
     C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "microsoft.vbe.interop". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
     C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "stdole". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
     C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (4513): Item 'Microsoft.Net.Framework.3.5' could not be located in 'C:\Program Files (x86)\Microsoft SDKs\Windows\v8.0A\Bootstrapper\'. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
     C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets (1740): TF201077: The work item type Bug cannot be found. It may have been renamed or destroyed.
     C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets (1740): The "CreateNewWorkItem" task failed unexpectedly.
    Microsoft.TeamFoundation.WorkItemTracking.Client.WorkItemTypeDeniedOrNotExistException: TF201077: The work item type Bug cannot be found. It may have been renamed or destroyed.
       at System.Activities.WorkflowApplication.Invoke(Activity activity, IDictionary`2 inputs, WorkflowInstanceExtensionManager extensions, TimeSpan timeout)
       at System.Activities.WorkflowInvoker.Invoke(Activity workflow, IDictionary`2 inputs, TimeSpan timeout, WorkflowInstanceExtensionManager extensions)
       at Microsoft.TeamFoundation.Build.Tasks.WorkflowTask.ExecuteInternal()
       at Microsoft.TeamFoundation.Build.Tasks.Task.Execute()
       at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
       at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__20.MoveNext()
    00:03
    Creating work item
     Exception Message: TF270015: 'MSBuild.exe' returned an unexpected exit code. Expected '0'; actual '1'. See the build logs for more details. (type UnexpectedExitCodeException)
    Exception Stack Trace:    at System.Activities.Statements.Throw.Execute(CodeActivityContext context)
       at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager)
       at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)
    Final Property Values
    BinariesSubdirectory = 
    BuildDirectory = d:\temp\217\CTI\Ephone_DIT_Deploy
    CommandLineArguments = 
    ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
    DoNotDownloadBuildType = False
    LogFilePerProject = False
    MaxProcesses = 1
    NodeReuse = False
    RecursionType = OneLevel
    SourcesSubdirectory = 
    TargetsNotLogged = 
    TestResultsSubdirectory = 
    ToolPath = 
    ToolPlatform = Auto
    Verbosity = Diagnostic
    Final Property Values
    Condition = True
    Final Property Values
    MaxExecutionTime = 00:00:00
    MaxWaitTime = 04:00:00
    ReservationSpec = Name=*, Tags=
    Result = U4VMDWODBDEV03 - Agent1 (vstfs:///Build/Agent/217)
    Final Property Values
    AgentSettings = Use agent where Name=* and Tags is empty; Max Wait Time: 04:00:00
    BinariesSubdirectory = 
    ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
    DoNotDownloadBuildType = False
    LogFilePerProject = False
    MSBuildArguments = 
    MSBuildPlatform = Auto
    RecursionType = OneLevel
    SourcesSubdirectory = 
    TestResultsSubdirectory = 
    Verbosity = Diagnostic
    Please have a look and guide where to find a problem
    Thanks ahead

    Hi Hooi,
    I'd like to know whether you can build successfully in your local machine with MSBuild. You have to build succeed with MSBuild beore you can build with TFS Build since TFS build use MSBuild as its default compiler.
    From the error message, you might build with wrong platform for your project. Please check if the build platfrom is proper. If you have customization of your build process template, it would be better to elaborate the reproduce steps and customization details.
    Best regards,

  • Transaction code to display exception messages by material and plant

    Hi,
    Is there a transaction code or standard report in SAP  to display exception messages by material and plant? I see the exception messages by individual material and plant in MD04 but I need to see a collective view. I tried Collective access in MD04 and MD46 but they are not giving me exception groups but I need exceptions listed out by material and plant.
    Thanks.

    Visu,
    I have never seen such a report.
    MD06 does support fine tuning the output display, once the list has been generated.  If you use this feature, the resulting display is the entire list as created by selecting the initial parameters (such as exception group), but with the specific items that contain your selected message highlighted.  If you are addressing the messages interactively, you can select the review (glasses)  screens, and scroll through just the ones which contain your  selected exception message(s).
    To try this, execute MD06.  Select the groups as necessary.  Execute.  Wait for the list.  Now, immediately, select 'search' (binoculars).  Experiment with the output.
    As mentioned in the previous post, if MD06 does not meet your needs, you will need to have a custom report written.
    Rgds,
    DB49

  • How to get detailed fault message in business process when exception?

    In bp, I use "catch all exception" to handle exception. When exception, I get fault message from all of component and write them into log files. But no matter which component throw exception, I cannot get any detailed message, the string writed into log is always null. Why? server.xml has all detailed message and printstack and why cannot I get?

    Hi,
    As far as I know, it's not possible to get the exception message with a catch all. You need to catch each exception separately, and the you will be able to get each message.
    Regards
    Gustavo

  • Data Quality vendor-specific error: An error occurred when calling function 'sdq_init_connector ()' in connector ": "(-8) Exception!." Detailed error message: Exception thrown by Java: java.lang.UnsatisfiedLinkError: nio (Not found in com.ibm.oti.vm.boots

    When attempting to create a new Account in siebel integrated with OEDQ the following error occurs.
    ERROR
    Data Quality vendor-specific error: An error occurred when calling function 'sdq_init_connector ()' in connector ": "(-8) Exception!." Detailed error message: Exception thrown by Java: java.lang.UnsatisfiedLinkError: nio (Not found in com.ibm.oti.vm.bootstrap.library.path)(SBL-APS-00118)
    STEPS
    The issue can be reproduced at will with the following steps:
    1) from EDQ director we have imported the EDQ_CDS,EDQ-REFERENCE DATA & EDQ_HISTORICAl DATA packages sucessfully.
    2) Created dnd.param file in SIebel server SDQCOnnector folder.
    3) Copied the libdnd.so file to siebsrvr lib directory(32 bit)
    3) In dnd.param file we have mentioned the javalib file and instllation directory path(<Siebsrvr roo>/dnd/install)
    4) Unzipped the EDQ-Siebel Connector files in dnd/install folder
    5) Copied the dnd.properties file in dnd/install directory and modified it accordingly to point to installed EDQ instance.
    6) Configured the Siebel components for EDQ integration.
    7) Realtime EDQ jobs are running.
    8) Create a new Account
    Env details are
    On : 8.2.2.14 [IP2014] version, Client Functionality
    EDQ 11.1.1.7.4
    IBM JDK 1.7 32 bit
    Using Open UI
    Any Champ have faced this issue and overcame it please let me know the resolution steps. your help is
    Regards
    Monoj Dey
    9007554589

    Hi Monoj,
    A few questions:
    - What OS is Siebel running on?
    - What version of the Siebel connector are you using?
    - Which libdnd.so file are you using?
    - What's the contents of your dnd.parms file?
    thanks,
    Nick

  • Throw Exception message is displayed twice.

    Hi all,
    In my java class based on a condition, I am throwing an exception. In runtime the exception message is displayed twice. I am sure that my code is gettign executed only once.
    Anyones help is greatly appreciated.
    Thanks in advance
    prabhakar

    Hi all,
    In my java class based on a condition, I am throwing
    an exception. In runtime the exception message is
    displayed twice. I am sure that my code is gettign
    executed only once.
    Anyones help is greatly appreciated.
    Thanks in advance
    prabhakarPlease be a little more explicit about what you're doing, what you expect to happen, and what you actually observe.
    Please post a short, concise, executable example of what you're trying to do. This does not have to be the actual code you are using. Write a small example that demonstrates your intent, and only that. Wrap the code in a class and give it a main method that runs it - if we can just copy and paste the code into a text file, compile it and run it without any changes, then we can be sure that we haven't made incorrect assumptions about how you are using it.
    Post your code between [code] and [/code] tags as described in Formatting Help on the message entry page. Cut and paste the code, rather than re-typing it (re-typing often introduces subtle errors that make your problem difficult to troubleshoot). Please preview your post when posting code.
    Please assume that we only have the core API. We have no idea what SomeCustomClass is, and neither does our collective compiler.
    Help us help you solve your problem.

  • How to display the error message during the web dynpro application runtime

    hi,
        I'm a java developer,During i 'deploy and run ' a web dynpro application on server-1,if the application have some runtime errors. there are displayed many infomation about the runtime error,such as exception track,etc.
        But when i do the same on server-2,there just show something like:
                500   Internal Server Error
                                    SAP NetWeaver Application Server 7.00/Java AS 7.00
                Failed to process request. Please contact your system administrator.
    but the server-1 will stop the j2ee engine. 
    how can do i make server-2 show detail error message as server-1. when i debug web dynpro application need these infomation.
    Appreciate your inputs...
    (Note:server-1 and server-2 have same software version)
    Edited by: BingLin Zhong on Feb 18, 2008 2:13 AM

    The Sap-Notes 962319:
    1. Check in the Visual Administrator, "Licensing Adapter" -> "General" -> "SystemType" !
    If it is set to "DEVELOPMENT_MODE", verbose error messages are shown.
    If it is undefined, proceed with the next step.
    If it is set to something else, only exception IDs are shown. In this case the only chance is to search for this exception ID in the default traces.
    2. If the system type is undefined, then in the Config Tool "Configurations" -> "webdynpro" -> "sap.com" -> "tcwddispwda" -> "Propertysheet default" -> "DevelopmentMode" is evaluated. If it is "true", verbose error messages are shown.
    3. If verbose error messages are required but still the short version is shown, you probably face an error message that is not raised by Web Dynpro but by other components of the NetWeaver. In the Visual Administrator set "Properties" -> "HTTP Provider" -> "DetailedErrorResponse" to "true".
    4. In addition to the error page shown in the browser or client, important messages - including error messages and stack traces - are written to the log and trace files, e.g. to the default traces usr\sap\<SID>\<instance>\j2ee\cluster\server<number>\log\defaulttrace.trc.<number>.
    a) In some cases, when an exception ID is included in the error message, the detailed error message can easily be retrieved in the log file.
    b) When no exception ID is given, you have to search for the detailed error message in the log specifying time stamp and/or user ID.
    Always consider restarting the system after making changes on the settings.
    It is not recommended to switch the "SystemType" to an inappropriate value just for viewing verbose error messages. The system type potentially affects framework, applications and licensing in an perhaps unintended way.
    In the past there was no distinction between different system types regarding error messages. For security reasons this distiction has been introduced. It is not intended to show stack traces in non-development systems in the future. SAP does not provide workarounds or patches to enable such a behaviour again.

  • How to get only current exception message from tables

    Hi
    In my sceanario , I want to have the list of Current MRP exception messages list from table
    I understand that MRP detailed lists, including all exception messages, are stored in transparent table MDKP and cluster table MDTC.
    I can tell ABAPer to write a report for me , to read the data from these tables , but I guess these tables contain old exception message also , which are not currently appearing in MRP list
    How to get only current exception message
    Rgds,
    sandeep

    Sandeep,
    MDTC contains only data from the most recent MRP run.  So, all messages you see are those which are currently valid.
    The messages might have first appeared during a previous run, but they still need to be addressed.
    Before you invest a lot of time and effort into writing and debugging a custom report, you should probably try to use the standard SAP functionality found in MD06.  On the Processing indicator tab, you can select "Only with new exceptions".  Here you can tag a material/plant as 'processed', and thereafter, the exceptions that existed there before you tagged the part will not be re-displayed.
    Best Regards,
    DB49

  • MD04 exception message 26 & 10

    Hi to every one,
    Could you  please tell,  In which cases exception message 26  & 10 will be displayed in MD04.
    Thanks & Regards
    Vikrant Hande

    Hi
    Below are circustances defined in Std. SAP where we can see these exceptions..Please ignore if you have allready know this..You need to compare with your stock/requirement situation in MD04..
    26: Excess in individual segment 
    Diagnosis
    In the individual segment (make-to-order planning, individual project planning, or direct production or direct procurement), the total of stock and receipts is greater than the requirements.
    The reason for this is, for example, that the sales order quantity has been reduced.
    System Response
    The exception message is set by the system as follows:
    If stock alone is greater than the requirements in the individual segment, the exception is displayed in the stock line.
    If receipts are scheduled, the exception message is displayed for the receipts that lie furthest in the future. Here, an exception message is given to all receipts whose quantities (also partially) exceed the requirements quantity.
    On the details screen for the receipts, the system also displays the required quantity, not needed to cover the requirement.
    The exception message is displayed in the MRP list and in the stock/requirements list.
    Procedure
    Either the stock is to be reduced by stock transfer or the receipts should be reduced.
    10: Reschedule in       
    Diagnosis
    In the rescheduling check, the system calculated a date to which the receipt is to be brought forward (rescheduled in) to avoid a material shortage.
    The rescheduling date displayed is the date on which the receipt is to be available for MRP. This includes the goods receipt processing time. If this is not zero, this information is displayed as well as the required goods receipt date.
    System Response
    This exception is displayed in the MRP list, and in the stock/requirements list.
    Procedure
    Check whether the receipt can be brought forward.
    Cheers
    Ravi

Maybe you are looking for

  • Java seems to be having a buffer error....

    Ok let me start by saying I do not know any JAVA programming. I just trying to fix something that some dump programmer charged me a ton of money for and it does not work right... The program reads a XML stream and creates XML files... The read works

  • Export and import LineGroups in CUCM 6.1

    Hello, I need to modify Linegroups in a CUCM 6.1, and like many, I need to do it through BAT, but I have not got the option in CUCM 6.1 (I have fount it in newer versions: 7.X, 8.X and 9.X) In the help in the CUCM webpage you can found info that you

  • Basic CFC not binding to s:DataGrid

    Installed "FB Burrito". OK. Following this tutorial. http://www.adobe.com/devnet/flex/articles/fcf_getting_started_coldfusion_flex.html  (but with default hero 4.5 sdk) CFC introspects fine defined return datatype. OK. Drag a DataGrid to design-view

  • MOV files on Autorun Windows CD with or without Quicktime on Target Machine

    Hi. I wonder if anyone can help me. I have a family Quicktime MOV file of our trip to Mexico. Problem is they all have Windows PCs and I have no clue if they have Quicktime installed or not. A couple people are out of state so I can't help them insta

  • Repositories for 32bit BO/DS  with 64bit SQL supported?

    We are planning to move our CMS, Audit and DS repositories of 32-bit Business Objects Enterprise XI 3.1 SP3 and Data Services 3.2 to Microsoft SQL Server 2008 R2 (64-bit) database. I was looking at the respective Supported Platform documents for both