Error when i create a BP - Person in IC Web CLient

Hi,
In Our Business Process: When call comes to Contact center, the agent can create a new customer (Person and Organization) in through ICWeb client.
We configurated our account identification profile assigning  z grouping to  z default role in the account creation and Role BUP001 for creation of contact person.
When we create a organization in IC WebClient  is created correctly  but when you want to create a Person, the systems shows a dump
"Source type \CLASS=CL_CRM_BOL_ENTITY is not compatible, for the purposes of assignment, with target type \CLASS=CL_BSP_WD_VALUE_NODE"
Doing this also i am not able to create new customer person.
Does anybody know about how can i resolve this problem?
Regards
Laura

Hello Laura,
The error ""Source type \CLASS=CL_CRM_BOL_ENTITY is not compatible, for the purposes of assignment, with target type \CLASS=CL_BSP_WD_VALUE_NODE" is casting error.
When we create person / account it is value node untill mandatory fields are entered in account details screen. When "Grouping" value can be changed it is value node, when it is disabled it is model node. So if there is a variable declared CL_CRM_BOL_ENTITY and it want to get value node there can be type casting error.
Please check in ST22 with more details, there can be custom coding.
Thanks
Krish

Similar Messages

  • Error when comiling formula in OFA 6.3.4 web client

    When using OFA 6.3.4 for web we get the following error message displayed :
    The formula, xxx, could not be compiled. It will be removed from status
    Pleas contact your database administrator.
    It is no error number displayed, just the error message above. The error message is showing up first time
    we access OFA web client in the browser, please let me know if you know something about this error conditon.
    Regards
    Jon Trxstheim (STI AS)
    Norway
    email: [email protected]

    In OFA, If we creat a new formula, we must compile it.
    Your error messge is showing that your new formula hasn't been compiled.
    What you need to do is that loging on as an administrator and compile it.

  • Allocation error when I create production order

    Hi guys:
       I met allocation error when I created production order with CO01.could you help me out?urgent!

    hi
    What is the excatly the error so that we can tell u the reason
    regards
    ramakant

  • Error when I create the New material Master (MM01) for New Plant.

    Dear experts,
    I got the error when I create the New material Master (MM01) for New Plant.
    Error:  Valuation Area 2800 Not yet productive with Material Ledger.
    So Pl send me the solution asap.
    Venkata Raju Khottari

    Hi,
    Have u assinged Plant to Company code?
    If u say no, use T.code OX18.
    Regards,
    Murali
    Assign points if it is useful.

  • Error while creating return order(Complaint) in IC web client

    Hi SAP Experts,
    I am getting following Error while creating return order(Complaint) in IC web client.
    Error when processing your request
    What has happened?
    The URL http://sapcrd.comfort.com:8000/sap/bc/bsp/sap/crm_ic/default_delta.do was not called due to an error.
    Note
    The following error text was processed in the system CRD : Exception condition "NON_EXISTING_HANDLE" raised.
    The error occurred on the application server sapcrd_CRD_00 and in the work process 2 .
    The termination type was: RABAX_STATE
    The ABAP call stack was:
    Function: PRC_PD_HEAD_ADD_COND of program SAPLPRC_PRICING_API
    Function: CRM_PRIDOC_UPDATE_EC of program SAPLCRM_PRIDOC_COM_EC
    Form: EXECUTE_CALLBACKS_PLANNED of program SAPLCRM_EVENT_OW
    Function: CRM_EVENT_SET_EXETIME_OW of program SAPLCRM_EVENT_OW
    Function: CRM_ORDER_COMPLETE_SINGLE_OW of program SAPLCRM_ORDER_OW
    Function: CRM_ORDER_MAINTAIN_SINGLE_OW of program SAPLCRM_ORDER_OW
    Function: CRM_ORDER_MAINTAIN_MULTI_OW of program SAPLCRM_ORDER_OW
    Function: CRM_ORDER_MAINTAIN of program SAPLCRM_ORDER_API
    Method: IF_EX_ORDER_SAVE~PREPARE of program ZCL_IM_PRICE_ADJUSTMENT=======CP
    Method: IF_EX_ORDER_SAVE~PREPARE of program CL_EX_ORDER_SAVE==============CP
    What can I do?
    If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system CRD in transaction ST22.
    If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server sapcrd_CRD_00 in transaction SM21.
    If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 2 in transaction ST11 on the application server sapcrd_CRD_00 . In some situations, you may also need to analyze the trace files of other work processes.
    If you do not yet have a user ID, contact your system administrator.
    Error code: ICF-IE-http -c: 330 -u: VORUSX -l: E -s: CRD -i: sapcrd_CRD_00 -w: 2 -d: 20080324 -t: 021723 -v: RABAX_STATE -e: RAISE_EXCEPTION
    HTTP 500 - Internal Server Error
    Your SAP Internet Communication Framework Team
    Maximum points will be awarded for useful information.
    Thanks,
    Rony

    Hi,
    I notice there is a Z class being called.
    Method: IF_EX_ORDER_SAVE~PREPARE of program ZCL_IM_PRICE_ADJUSTMENT=======CP
    You should check this customized class.
    Cheers,
    cady.

  • General Error" when I create pdf of web site

    Using Acrobat XI
    I get a "General Error" error code when I am creating a pdf of a web site. It always happens after page 4 has been converted.  (the Web site has several hundred pages and I have plenty of memory).
    How do I avoid this?

    Hello Laura,
    The error ""Source type \CLASS=CL_CRM_BOL_ENTITY is not compatible, for the purposes of assignment, with target type \CLASS=CL_BSP_WD_VALUE_NODE" is casting error.
    When we create person / account it is value node untill mandatory fields are entered in account details screen. When "Grouping" value can be changed it is value node, when it is disabled it is model node. So if there is a variable declared CL_CRM_BOL_ENTITY and it want to get value node there can be type casting error.
    Please check in ST22 with more details, there can be custom coding.
    Thanks
    Krish

  • Error when i create accounting

    frist of all sorry if i put this message in wrong subject or wrong thread.this is my frist time in forum
    dear all,
    i use ebs r12 12.1.2 os Linux x86-64
    when i create accounting i meet error this log :
    Application Object Library: Version : 12.0.0
    Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
    FNDWFBG module: Workflow Background Process
    Current system time is 15-APR-2011 01:39:37
    **Starts**15-APR-2011 01:39:37
    **Ends**15-APR-2011 01:39:37
    Start of log messages from FND_FILE
    End of log messages from FND_FILE
    Successfully resubmitted concurrent program FNDWFBG with request ID 450126 to start at 15-APR-2011 01:53:18 (ROUTINE=AFPSRS)
    Executing request completion options...
    Output is not being printed because:
    The print option has been disabled for this report.
    ------------- 1) PRINT   -------------
    Finished executing request completion options.
    Concurrent request completed successfully
    Current system time is 15-APR-2011 01:39:37
    Subledger Accounting: Version : 12.0.0
    Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
    XLAACCPB module: Create Accounting
    Current system time is 16-JAN-2012 12:43:15
    XDO Data Engine Version No: 5.6.3
    Resp: 20639
    Org ID : 81
    Request ID: 450125
    All Parameters: P_APPLICATION_ID=200:P_SOURCE_APPLICATION_ID=200:P_DUMMY=Y:P_LEDGER_ID=2023:P_PROCESS_CATEGORY_CODE=PAYMENTS:P_END_DATE="2012/01/10 00:00:00":P_CREATE_ACCOUNTING_FLAG=Y:P_DUMMY_PARAM_1=Y:P_ACCOUNTING_MODE=D:P_DUMMY_PARAM_2=:P_ERRORS_ONLY_FLAG=N:P_REPORT_STYLE=D:P_TRANSFER_TO_GL_FLAG=:P_DUMMY_PARAM_3=:P_POST_IN_GL_FLAG=:P_GL_BATCH_NAME=test11:P_MIN_PRECISION=:P_INCLUDE_ZERO_AMOUNT_LINES=N:P_REQUEST_ID=:P_ENTITY_ID=:P_SOURCE_APPLICATION_NAME=Payables:P_APPLICATION_NAME=Payables:P_LEDGER_NAME=SMI_PL:P_PROCESS_CATEGORY_NAME=Payments:P_CREATE_ACCOUNTING=Yes:P_ACCOUNTING_MODE_NAME=Draft:P_ERRORS_ONLY=No:P_ACCOUNTING_REPORT_LEVEL=Detail:P_TRANSFER_TO_GL=:P_POST_IN_GL=:P_INCLUDE_ZERO_AMT_LINES=No:P_VALUATION_METHOD_CODE=:P_SECURITY_INT_1=:P_SECURITY_INT_2=:P_SECURITY_INT_3=:P_SECURITY_CHAR_1=:P_SECURITY_CHAR_2=:P_SECURITY_CHAR_3=:P_CONC_REQUEST_ID=:P_INCLUDE_USER_TRX_ID_FLAG=N:P_INCLUDE_USER_TRX_IDENTIFIERS=No:DebugFlag=Y:P_USER_ID=1110
    Data Template Code: XLAACCPB
    Data Template Application Short Name: XLA
    Debug Flag: Y
    {P_ACCOUNTING_REPORT_LEVEL=Detail, P_DUMMY=Y, P_ACCOUNTING_MODE_NAME=Draft, P_ERRORS_ONLY_FLAG=N, P_REPORT_STYLE=D, P_GL_BATCH_NAME=test11, P_END_DATE=2012/01/10 00:00:00, P_SECURITY_INT_3=, P_SECURITY_INT_2=, P_SECURITY_INT_1=, P_VALUATION_METHOD_CODE=, P_POST_IN_GL=, P_TRANSFER_TO_GL=, P_TRANSFER_TO_GL_FLAG=, P_INCLUDE_USER_TRX_IDENTIFIERS=No, P_USER_ID=1110, P_PROCESS_CATEGORY_NAME=Payments, P_ERRORS_ONLY=No, P_DUMMY_PARAM_3=, P_SECURITY_CHAR_3=, P_DUMMY_PARAM_2=, P_SECURITY_CHAR_2=, P_DUMMY_PARAM_1=Y, P_SECURITY_CHAR_1=, P_ENTITY_ID=, P_PROCESS_CATEGORY_CODE=PAYMENTS, P_INCLUDE_ZERO_AMT_LINES=No, P_LEDGER_ID=2023, P_POST_IN_GL_FLAG=, P_APPLICATION_ID=200, P_INCLUDE_USER_TRX_ID_FLAG=N, P_APPLICATION_NAME=Payables, P_REQUEST_ID=, P_CONC_REQUEST_ID=, P_LEDGER_NAME=SMI_PL, P_SOURCE_APPLICATION_ID=200, P_CREATE_ACCOUNTING=Yes, P_CREATE_ACCOUNTING_FLAG=Y, P_MIN_PRECISION=, P_SOURCE_APPLICATION_NAME=Payables, P_INCLUDE_ZERO_AMOUNT_LINES=N, P_ACCOUNTING_MODE=D}
    Calling XDO Data Engine...
    [011612_124319140][][STATEMENT] oracle.jdbc.driver.OracleBlobInputStream@179f36b
    [011612_124319242][][STATEMENT] Logger.init(): *** DEBUG MODE IS OFF. ***
    [011612_124319244][][STATEMENT] DataTemplate.getTmpDir(): system-temp-dir property value from DATABASE: /usr/temp
    [011612_124319246][][STATEMENT] Template parsing started...
    [011612_124319389][][STATEMENT] Data Template ......
    [011612_124319389][][STATEMENT] oracle.xml.parser.v2.XMLDocument@19fdbcb
    [011612_124319525][][STATEMENT] Inside properties Parser...
    [011612_124319525][][STATEMENT] db_fetch_size=20
    [011612_124319526][][STATEMENT] Inside parameterParser...
    [011612_124319527][][STATEMENT] Parameter:P_REQUEST_ID Default value:
    [011612_124319527][][STATEMENT] Parameter:P_ENTITY_ID Default value:
    [011612_124319527][][STATEMENT] Parameter:P_SOURCE_APPLICATION_ID Default value:
    [011612_124319527][][STATEMENT] Parameter:P_SOURCE_APPLICATION_NAME Default value:
    [011612_124319527][][STATEMENT] Parameter:P_APPLICATION_ID Default value:
    [011612_124319527][][STATEMENT] Parameter:P_APPLICATION_NAME Default value:
    [011612_124319527][][STATEMENT] Parameter:P_DUMMY Default value:
    [011612_124319527][][STATEMENT] Parameter:P_LEDGER_ID Default value:
    [011612_124319527][][STATEMENT] Parameter:P_LEDGER_NAME Default value:
    [011612_124319527][][STATEMENT] Parameter:P_PROCESS_CATEGORY_CODE Default value:
    [011612_124319528][][STATEMENT] Parameter:P_PROCESS_CATEGORY_NAME Default value:
    [011612_124319528][][STATEMENT] Parameter:P_END_DATE Default value:
    [011612_124319528][][STATEMENT] Parameter:P_CREATE_ACCOUNTING_FLAG Default value:
    [011612_124319528][][STATEMENT] Parameter:P_CREATE_ACCOUNTING Default value:
    [011612_124319528][][STATEMENT] Parameter:P_DUMMY_PARAM_1 Default value:
    [011612_124319528][][STATEMENT] Parameter:P_ACCOUNTING_MODE Default value:
    [011612_124319528][][STATEMENT] Parameter:P_DUMMY_PARAM_2 Default value:
    [011612_124319528][][STATEMENT] Parameter:P_ERRORS_ONLY_FLAG Default value:
    [011612_124319528][][STATEMENT] Parameter:P_REPORT_STYLE Default value:
    [011612_124319528][][STATEMENT] Parameter:P_ACCOUNTING_MODE_NAME Default value:
    [011612_124319528][][STATEMENT] Parameter:P_ERRORS_ONLY Default value:
    [011612_124319528][][STATEMENT] Parameter:P_ACCOUNTING_REPORT_LEVEL Default value:
    [011612_124319529][][STATEMENT] Parameter:P_TRANSFER_TO_GL_FLAG Default value:
    [011612_124319529][][STATEMENT] Parameter:P_TRANSFER_TO_GL Default value:
    [011612_124319529][][STATEMENT] Parameter:P_DUMMY_PARAM_3 Default value:
    [011612_124319529][][STATEMENT] Parameter:P_POST_IN_GL_FLAG Default value:
    [011612_124319529][][STATEMENT] Parameter:P_POST_IN_GL Default value:
    [011612_124319529][][STATEMENT] Parameter:P_GL_BATCH_NAME Default value:
    [011612_124319529][][STATEMENT] Parameter:P_MIN_PRECISION Default value:
    [011612_124319529][][STATEMENT] Parameter:P_INCLUDE_ZERO_AMOUNT_LINES Default value:
    [011612_124319529][][STATEMENT] Parameter:P_INCLUDE_ZERO_AMT_LINES Default value:
    [011612_124319530][][STATEMENT] Parameter:P_VALUATION_METHOD_CODE Default value:
    [011612_124319530][][STATEMENT] Parameter:P_SECURITY_INT_1 Default value:
    [011612_124319530][][STATEMENT] Parameter:P_SECURITY_INT_2 Default value:
    [011612_124319530][][STATEMENT] Parameter:P_SECURITY_INT_3 Default value:
    [011612_124319530][][STATEMENT] Parameter:P_SECURITY_CHAR_1 Default value:
    [011612_124319530][][STATEMENT] Parameter:P_SECURITY_CHAR_2 Default value:
    [011612_124319530][][STATEMENT] Parameter:P_SECURITY_CHAR_3 Default value:
    [011612_124319530][][STATEMENT] Parameter:P_CONC_REQUEST_ID Default value:
    [011612_124319531][][STATEMENT] Parameter:P_INCLUDE_USER_TRX_ID_FLAG Default value:
    [011612_124319531][][STATEMENT] Parameter:P_INCLUDE_USER_TRX_IDENTIFIERS Default value:
    [011612_124319531][][STATEMENT] Parameter:P_USER_ID Default value:
    [011612_124319531][][STATEMENT] Inside dataQueryParser...
    [011612_124319535][][STATEMENT] Inside dataStructureParser...
    [011612_124319540][][STATEMENT] Group ...report
    [011612_124319541][][STATEMENT] Group ...APPLICATION
    [011612_124319542][][STATEMENT] Group ...APPLICATION_FLAG
    [011612_124319543][][STATEMENT] Group ...NO_ACTION_EVT
    [011612_124319544][][STATEMENT] Group ...ACCT_PROG_ERRORS
    [011612_124319545][][STATEMENT] Group ...EVENT_CLASS_S
    [011612_124319545][][STATEMENT] Group ...LEDGER_S
    [011612_124319546][][STATEMENT] Group ...BALANCE_TYPE_S
    [011612_124319547][][STATEMENT] Group ...EVENT
    [011612_124319548][][STATEMENT] Group ...AE_HEADERS
    [011612_124319550][][STATEMENT] Group ...AE_LINES
    [011612_124319551][][STATEMENT] Group ...AE_ERRORS
    [011612_124319552][][STATEMENT] Group ...NO_ENTRY_EVENTS
    [011612_124319553][][STATEMENT] Template parsing completed...
    [011612_124319553][][STATEMENT] Setting Data Template
    [011612_124319553][][STATEMENT] Setting JDBC Connection
    [011612_124319576][][STATEMENT] Paramter :P_REQUEST_ID Value :
    [011612_124319642][][STATEMENT] Paramter :P_ENTITY_ID Value :
    [011612_124319642][][STATEMENT] Paramter :P_SOURCE_APPLICATION_ID Value :200
    [011612_124319642][][STATEMENT] Paramter :P_SOURCE_APPLICATION_NAME Value :Payables
    [011612_124319642][][STATEMENT] Paramter :P_APPLICATION_ID Value :200
    [011612_124319642][][STATEMENT] Paramter :P_APPLICATION_NAME Value :Payables
    [011612_124319642][][STATEMENT] Paramter :P_DUMMY Value :Y
    [011612_124319642][][STATEMENT] Paramter :P_LEDGER_ID Value :2023
    [011612_124319642][][STATEMENT] Paramter :P_LEDGER_NAME Value :SMI_PL
    [011612_124319643][][STATEMENT] Paramter :P_PROCESS_CATEGORY_CODE Value :PAYMENTS
    [011612_124319643][][STATEMENT] Paramter :P_PROCESS_CATEGORY_NAME Value :Payments
    [011612_124319658][][STATEMENT] Paramter :P_END_DATE Value :2012/01/10 00:00:00
    [011612_124319658][][STATEMENT] Paramter :P_CREATE_ACCOUNTING_FLAG Value :Y
    [011612_124319658][][STATEMENT] Paramter :P_CREATE_ACCOUNTING Value :Yes
    [011612_124319658][][STATEMENT] Paramter :P_DUMMY_PARAM_1 Value :Y
    [011612_124319658][][STATEMENT] Paramter :P_ACCOUNTING_MODE Value :D
    [011612_124319658][][STATEMENT] Paramter :P_DUMMY_PARAM_2 Value :
    [011612_124319658][][STATEMENT] Paramter :P_ERRORS_ONLY_FLAG Value :N
    [011612_124319658][][STATEMENT] Paramter :P_REPORT_STYLE Value :D
    [011612_124319658][][STATEMENT] Paramter :P_ACCOUNTING_MODE_NAME Value :Draft
    [011612_124319658][][STATEMENT] Paramter :P_ERRORS_ONLY Value :No
    [011612_124319658][][STATEMENT] Paramter :P_ACCOUNTING_REPORT_LEVEL Value :Detail
    [011612_124319658][][STATEMENT] Paramter :P_TRANSFER_TO_GL_FLAG Value :
    [011612_124319658][][STATEMENT] Paramter :P_TRANSFER_TO_GL Value :
    [011612_124319659][][STATEMENT] Paramter :P_DUMMY_PARAM_3 Value :
    [011612_124319659][][STATEMENT] Paramter :P_POST_IN_GL_FLAG Value :
    [011612_124319659][][STATEMENT] Paramter :P_POST_IN_GL Value :
    [011612_124319659][][STATEMENT] Paramter :P_GL_BATCH_NAME Value :test11
    [011612_124319750][][STATEMENT] Paramter :P_MIN_PRECISION Value :
    [011612_124319751][][STATEMENT] Paramter :P_INCLUDE_ZERO_AMOUNT_LINES Value :N
    [011612_124319751][][STATEMENT] Paramter :P_INCLUDE_ZERO_AMT_LINES Value :No
    [011612_124319751][][STATEMENT] Paramter :P_VALUATION_METHOD_CODE Value :
    [011612_124319772][][STATEMENT] Paramter :P_SECURITY_INT_1 Value :
    [011612_124319837][][STATEMENT] Paramter :P_SECURITY_INT_2 Value :
    [011612_124319891][][STATEMENT] Paramter :P_SECURITY_INT_3 Value :
    [011612_124319891][][STATEMENT] Paramter :P_SECURITY_CHAR_1 Value :
    [011612_124319891][][STATEMENT] Paramter :P_SECURITY_CHAR_2 Value :
    [011612_124319892][][STATEMENT] Paramter :P_SECURITY_CHAR_3 Value :
    [011612_124319958][][STATEMENT] Paramter :P_CONC_REQUEST_ID Value :
    [011612_124319958][][STATEMENT] Paramter :P_INCLUDE_USER_TRX_ID_FLAG Value :N
    [011612_124319958][][STATEMENT] Paramter :P_INCLUDE_USER_TRX_IDENTIFIERS Value :No
    [011612_124319958][][STATEMENT] Paramter :P_USER_ID Value :1110
    [011612_124319958][][STATEMENT] Setting Parameters
    [011612_124319958][][STATEMENT] Setting Parameters
    [011612_124319960][][STATEMENT] Start process Data
    [011612_124319960][][STATEMENT] Process Data ...
    [011612_124319966][][STATEMENT] Executing data triggers...
    [011612_124319966][][STATEMENT] BEGIN
    XLA_CREATE_ACCT_RPT_PVT.P_REQUEST_ID := :P_REQUEST_ID ;
    XLA_CREATE_ACCT_RPT_PVT.P_ENTITY_ID := :P_ENTITY_ID ;
    XLA_CREATE_ACCT_RPT_PVT.P_SOURCE_APPLICATION_ID := :P_SOURCE_APPLICATION_ID ;
    XLA_CREATE_ACCT_RPT_PVT.P_SOURCE_APPLICATION_NAME := :P_SOURCE_APPLICATION_NAME ;
    XLA_CREATE_ACCT_RPT_PVT.P_APPLICATION_ID := :P_APPLICATION_ID ;
    XLA_CREATE_ACCT_RPT_PVT.P_APPLICATION_NAME := :P_APPLICATION_NAME ;
    XLA_CREATE_ACCT_RPT_PVT.P_DUMMY := :P_DUMMY ;
    XLA_CREATE_ACCT_RPT_PVT.P_LEDGER_ID := :P_LEDGER_ID ;
    XLA_CREATE_ACCT_RPT_PVT.P_LEDGER_NAME := :P_LEDGER_NAME ;
    XLA_CREATE_ACCT_RPT_PVT.P_PROCESS_CATEGORY_CODE := :P_PROCESS_CATEGORY_CODE ;
    XLA_CREATE_ACCT_RPT_PVT.P_PROCESS_CATEGORY_NAME := :P_PROCESS_CATEGORY_NAME ;
    XLA_CREATE_ACCT_RPT_PVT.P_END_DATE := :P_END_DATE ;
    XLA_CREATE_ACCT_RPT_PVT.P_CREATE_ACCOUNTING_FLAG := :P_CREATE_ACCOUNTING_FLAG ;
    XLA_CREATE_ACCT_RPT_PVT.P_CREATE_ACCOUNTING := :P_CREATE_ACCOUNTING ;
    XLA_CREATE_ACCT_RPT_PVT.P_DUMMY_PARAM_1 := :P_DUMMY_PARAM_1 ;
    XLA_CREATE_ACCT_RPT_PVT.P_ACCOUNTING_MODE := :P_ACCOUNTING_MODE ;
    XLA_CREATE_ACCT_RPT_PVT.P_DUMMY_PARAM_2 := :P_DUMMY_PARAM_2 ;
    XLA_CREATE_ACCT_RPT_PVT.P_ERRORS_ONLY_FLAG := :P_ERRORS_ONLY_FLAG ;
    XLA_CREATE_ACCT_RPT_PVT.P_REPORT_STYLE := :P_REPORT_STYLE ;
    XLA_CREATE_ACCT_RPT_PVT.P_ACCOUNTING_MODE_NAME := :P_ACCOUNTING_MODE_NAME ;
    XLA_CREATE_ACCT_RPT_PVT.P_ERRORS_ONLY := :P_ERRORS_ONLY ;
    XLA_CREATE_ACCT_RPT_PVT.P_ACCOUNTING_REPORT_LEVEL := :P_ACCOUNTING_REPORT_LEVEL ;
    XLA_CREATE_ACCT_RPT_PVT.P_TRANSFER_TO_GL_FLAG := :P_TRANSFER_TO_GL_FLAG ;
    XLA_CREATE_ACCT_RPT_PVT.P_TRANSFER_TO_GL := :P_TRANSFER_TO_GL ;
    XLA_CREATE_ACCT_RPT_PVT.P_DUMMY_PARAM_3 := :P_DUMMY_PARAM_3 ;
    XLA_CREATE_ACCT_RPT_PVT.P_POST_IN_GL_FLAG := :P_POST_IN_GL_FLAG ;
    XLA_CREATE_ACCT_RPT_PVT.P_POST_IN_GL := :P_POST_IN_GL ;
    XLA_CREATE_ACCT_RPT_PVT.P_GL_BATCH_NAME := :P_GL_BATCH_NAME ;
    XLA_CREATE_ACCT_RPT_PVT.P_MIN_PRECISION := :P_MIN_PRECISION ;
    XLA_CREATE_ACCT_RPT_PVT.P_INCLUDE_ZERO_AMOUNT_LINES := :P_INCLUDE_ZERO_AMOUNT_LINES ;
    XLA_CREATE_ACCT_RPT_PVT.P_INCLUDE_ZERO_AMT_LINES := :P_INCLUDE_ZERO_AMT_LINES ;
    XLA_CREATE_ACCT_RPT_PVT.P_VALUATION_METHOD_CODE := :P_VALUATION_METHOD_CODE ;
    XLA_CREATE_ACCT_RPT_PVT.P_SECURITY_INT_1 := :P_SECURITY_INT_1 ;
    XLA_CREATE_ACCT_RPT_PVT.P_SECURITY_INT_2 := :P_SECURITY_INT_2 ;
    XLA_CREATE_ACCT_RPT_PVT.P_SECURITY_INT_3 := :P_SECURITY_INT_3 ;
    XLA_CREATE_ACCT_RPT_PVT.P_SECURITY_CHAR_1 := :P_SECURITY_CHAR_1 ;
    XLA_CREATE_ACCT_RPT_PVT.P_SECURITY_CHAR_2 := :P_SECURITY_CHAR_2 ;
    XLA_CREATE_ACCT_RPT_PVT.P_SECURITY_CHAR_3 := :P_SECURITY_CHAR_3 ;
    XLA_CREATE_ACCT_RPT_PVT.P_CONC_REQUEST_ID := :P_CONC_REQUEST_ID ;
    XLA_CREATE_ACCT_RPT_PVT.P_INCLUDE_USER_TRX_ID_FLAG := :P_INCLUDE_USER_TRX_ID_FLAG ;
    XLA_CREATE_ACCT_RPT_PVT.P_INCLUDE_USER_TRX_IDENTIFIERS := :P_INCLUDE_USER_TRX_IDENTIFIERS ;
    XLA_CREATE_ACCT_RPT_PVT.P_USER_ID := :P_USER_ID ;
    :XDO_OUT_PARAMETER := 1;
    END;
    [011612_124319966][][STATEMENT] 1:null :
    [011612_124319966][][STATEMENT] 2:null :
    [011612_124319967][][STATEMENT] 3:200 :
    [011612_124319967][][STATEMENT] 4:Payables :
    [011612_124319967][][STATEMENT] 5:200 :
    [011612_124319967][][STATEMENT] 6:Payables :
    [011612_124319967][][STATEMENT] 7:Y :
    [011612_124319967][][STATEMENT] 8:2023 :
    [011612_124319967][][STATEMENT] 9:SMI_PL :
    [011612_124319967][][STATEMENT] 10:PAYMENTS :
    [011612_124319967][][STATEMENT] 11:Payments :
    [011612_124319968][][STATEMENT] 12:2012-01-10 00:00:00.0 :
    [011612_124319968][][STATEMENT] 13:Y :
    [011612_124319968][][STATEMENT] 14:Yes :
    [011612_124319968][][STATEMENT] 15:Y :
    [011612_124319968][][STATEMENT] 16:D :
    [011612_124319968][][STATEMENT] 17: :
    [011612_124319968][][STATEMENT] 18:N :
    [011612_124319968][][STATEMENT] 19:D :
    [011612_124319968][][STATEMENT] 20:Draft :
    [011612_124319968][][STATEMENT] 21:No :
    [011612_124319968][][STATEMENT] 22:Detail :
    [011612_124319968][][STATEMENT] 23: :
    [011612_124319968][][STATEMENT] 24: :
    [011612_124319968][][STATEMENT] 25: :
    [011612_124319968][][STATEMENT] 26: :
    [011612_124319968][][STATEMENT] 27: :
    [011612_124319968][][STATEMENT] 28:test11 :
    [011612_124319969][][STATEMENT] 29:null :
    [011612_124319969][][STATEMENT] 30:N :
    [011612_124319969][][STATEMENT] 31:No :
    [011612_124319969][][STATEMENT] 32: :
    [011612_124319969][][STATEMENT] 33:null :
    [011612_124319969][][STATEMENT] 34:null :
    [011612_124319969][][STATEMENT] 35:null :
    [011612_124319969][][STATEMENT] 36: :
    [011612_124319969][][STATEMENT] 37: :
    [011612_124319969][][STATEMENT] 38: :
    [011612_124319969][][STATEMENT] 39:null :
    [011612_124319969][][STATEMENT] 40:N :
    [011612_124319969][][STATEMENT] 41:No :
    [011612_124319969][][STATEMENT] 42:1110 :
    [011612_124319971][][STATEMENT] Executing data triggers...
    [011612_124319971][][STATEMENT] Declare
    l_flag Boolean;
    BEGIN
    l_flag := XLA_CREATE_ACCT_RPT_PVT.BeforeReport ;
    if (l_flag) then
    :XDO_OUT_PARAMETER := 1;
    end if;
    end;
    [011612_124319994][][EXCEPTION] SQLException encounter while executing data trigger....
    java.sql.SQLException: ORA-20001: -: XLA-95103: An internal error occurred. Please inform your system administrator or support representative that:
    An internal error has occurred in the program xla_create_acct_rpt_pvt.BeforeReport . ORA-20001: -: XLA-95103: An internal error occurred.
    ORA-06512: at "APPS.APP_EXCEPTION", line 72
    ORA-06512: at "APPS.XLA_EXCEPTIONS_PKG", line 110
    ORA-06512: at "APPS.XLA_EXCEPTIONS_PKG", line 289
    ORA-06512: at "APPS.XLA_EXCEPTIONS_PKG", line 162
    ORA-06512: at "APPS.XLA_CREATE_ACCT_RPT_PVT", line 275
    ORA-06512: at line 4
         at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:70)
         at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:133)
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:206)
         at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:455)
         at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:413)
         at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:1034)
         at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:191)
         at oracle.jdbc.driver.T4CCallableStatement.executeForRows(T4CCallableStatement.java:950)
         at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1225)
         at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3387)
         at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3488)
         at oracle.jdbc.driver.OracleCallableStatement.execute(OracleCallableStatement.java:3857)
         at oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(OraclePreparedStatementWrapper.java:1374)
         at oracle.apps.xdo.dataengine.XMLPGEN.executeTriggers(XMLPGEN.java:650)
         at oracle.apps.xdo.dataengine.XMLPGEN.processData(XMLPGEN.java:263)
         at oracle.apps.xdo.dataengine.XMLPGEN.processXML(XMLPGEN.java:215)
         at oracle.apps.xdo.dataengine.XMLPGEN.writeXML(XMLPGEN.java:254)
         at oracle.apps.xdo.dataengine.DataProcessor.processDataStructre(DataProcessor.java:390)
         at oracle.apps.xdo.dataengine.DataProcessor.processData(DataProcessor.java:355)
         at oracle.apps.xdo.oa.util.DataTemplate.processData(DataTemplate.java:334)
         at oracle.apps.xdo.oa.cp.JCP4XDODataEngine.runProgram(JCP4XDODataEngine.java:294)
         at oracle.apps.fnd.cp.request.Run.main(Run.java:157)
    Oracle error 20100: java.sql.SQLException: ORA-20100: Error: FND_FILE failure. Unable to create file, o0010400.tmp in the directory, /usr/tmp.
    You will find more information in the request log.
    ORA-06512: at "APPS.FND_FILE", line 417
    ORA-06512: at "APPS.FND_FILE", line 526
    ORA-06512: at "APPS.FND_CONCURRENT", line 1328
    ORA-06512: at line 1
    has been detected in FND_CONCURRENT.SET_INTERIM_STATUS.+---------------------------------------------------------------------------+
    Start of log messages from FND_FILE
    End of log messages from FND_FILE
    Executing request completion options...
    ------------- 1) PUBLISH -------------
    Beginning post-processing of request 450125 on node ORAAPPS at 16-JAN-2012 12:43:20.
    Post-processing of request 450125 failed at 16-JAN-2012 12:43:21 with the error message:
    One or more post-processing actions failed. Consult the OPP service log for details.
    Finished executing request completion options.
    Concurrent request completed
    Current system time is 16-JAN-2012 12:43:21
    anyone have same problem and already solving ??
    Thanks,
    Mahardika

    [011612_124319994][][EXCEPTION] SQLException encounter while executing data trigger....
    java.sql.SQLException: ORA-20001: -: XLA-95103: An internal error occurred. Please inform your system administrator or support representative that:
    An internal error has occurred in the program xla_create_acct_rpt_pvt.BeforeReport . ORA-20001: -: XLA-95103: An internal error occurred.
    ORA-06512: at "APPS.APP_EXCEPTION", line 72
    ORA-06512: at "APPS.XLA_EXCEPTIONS_PKG", line 110
    ORA-06512: at "APPS.XLA_EXCEPTIONS_PKG", line 289
    ORA-06512: at "APPS.XLA_EXCEPTIONS_PKG", line 162
    ORA-06512: at "APPS.XLA_CREATE_ACCT_RPT_PVT", line 275
    ORA-06512: at line 4Please make sure you have no invalid objects.
    Please also see these docs.
    R12: Ap Invoice Online Accounting with Final Post Ends With Errors ORA-20001 XLA-95103 [ID 853424.1]
    FAACCPB Create Accounting Internal Error xla_create_acct_rpt_pvt.BeforeReport [ID 783493.1]
    CSTCRACC Create Accounting Err ORA-20001 Xla-95103 Internal Error Occurred ORA-01400 [ID 1309124.1]
    CSTCRACC - Create Accounting - Cost Management Completes With Errors: java.sql.SQLException, ORA-20001, XLA-95103 [ID 1252703.1]
    Create Accounting Concurrent Program Errors - ORA-20001 XLA-95103 [ID 1392267.1]
    Create Accounting Error Due To Invalid Package Apps.Ap_payment_extract_details_v [ID 1366269.1]
    ------------- 1) PUBLISH -------------
    Beginning post-processing of request 450125 on node ORAAPPS at 16-JAN-2012 12:43:20.
    Post-processing of request 450125 failed at 16-JAN-2012 12:43:21 with the error message:
    One or more post-processing actions failed. Consult the OPP service log for details.
    Also check OPP log file ($APPLCSF/$APPLLOG/FNDOPP* file).
    Thanks,
    Hussein

  • -6502 ORA-06502: PL/SQL: numeric or value error when using 'Create CAPI Definition'

    I get an error when I try to create a CAPI definition with Headstart untilities (6i). I use HSU_CAPI revision 6.5.2.0
    The detailed information says the following:
    Message
    BLAPI.OPEN_ACTIVITY
    Start HSU_CAPI.run
    Number of Tables to create CAPI for 1
    Initial checks for table KCS_TENDERS with id 692754610572409851363604771392473242
    HSU_CAPT.initial_checks for table KCS_TENDERS
    HSU_CAPF.initial_checks for table KCS_TENDERS
    HSU_CAPC.initial_checks Custom Services for table KCS_TENDERS
    HSU_CAPB.initial_checks BRDD for table KCS_TENDERS
    bltext.get_lines_from_repository, p_text_type=CDINOT
    bltext.get_line_containing
    bltext.get_line_containing
    bltext.get_lines_from_repository, p_text_type=CDIPLS
    bltext.get_line_containing
    bltext.get_line_containing
    bltext.get_line_containing
    bltext.get_line_containing
    bltext.get_line_containing
    bltext.get_line_containing
    KCS_TENDERS Business Rule Design Definition BR_TNR001_CEV does not have any Trigger Columns. Rule will fire when any column is updated.
    bltext.get_lines_from_repository, p_text_type=CDINOT
    bltext.get_line_containing
    bltext.get_line_containing
    bltext.get_lines_from_repository, p_text_type=CDIPLS
    bltext.get_line_containing
    bltext.get_line_containing
    bltext.get_line_containing
    bltext.get_line_containing
    bltext.get_line_containing
    bltext.get_line_containing
    Creating CAPI for table KCS_TENDERS with id 692754610572409851363604771392473242
    Recreating KCS_TENDERS Table API/Trigger Logic - Event: Pre-Before-Insert-stmt, Open transaction.
    Write Text for element type APPLOG with id 753236628580304413262318236391196826 - Text type: ALCODE number of text lines = 6 - REPLACE
    Deleted old text
    Write Text for element type APPLOG with id 753236628580304413262318236391196826 - Text type: ALCMNT number of text lines = 1 - REPLACE
    Deleted old text
    Recreating KCS_TENDERS Table API/Trigger Logic - Event: Pre-Before-Update-stmt, Open transaction.
    Write Text for element type APPLOG with id 753236628580332747461215454262479002 - Text type: ALCODE number of text lines = 6 - REPLACE
    Deleted old text
    Write Text for element type APPLOG with id 753236628580332747461215454262479002 - Text type: ALCMNT number of text lines = 1 - REPLACE
    Deleted old text
    Recreating KCS_TENDERS Table API/Trigger Logic - Event: Pre-Before-Delete-stmt, Open transaction.
    Write Text for element type APPLOG with id 753236628580361081660112672133761178 - Text type: ALCODE number of text lines = 6 - REPLACE
    Deleted old text
    Write Text for element type APPLOG with id 753236628580361081660112672133761178 - Text type: ALCMNT number of text lines = 1 - REPLACE
    Deleted old text
    Recreating KCS_TENDERS Table API/Trigger Logic - Event: Post-After-Insert-stmt, Close transaction.
    Write Text for element type APPLOG with id 753236628580389415859009890005043354 - Text type: ALCODE number of text lines = 6 - REPLACE
    Deleted old text
    Write Text for element type APPLOG with id 753236628580389415859009890005043354 - Text type: ALCMNT number of text lines = 1 - REPLACE
    Deleted old text
    Recreating KCS_TENDERS Table API/Trigger Logic - Event: Post-After-Update-stmt, Close transaction.
    Write Text for element type APPLOG with id 753236628580417750057907107876325530 - Text type: ALCODE number of text lines = 6 - REPLACE
    Deleted old text
    Write Text for element type APPLOG with id 753236628580417750057907107876325530 - Text type: ALCMNT number of text lines = 1 - REPLACE
    Deleted old text
    Recreating KCS_TENDERS Table API/Trigger Logic - Event: Post-After-Delete-stmt, Close transaction.
    Write Text for element type APPLOG with id 753236628580446084256804325747607706 - Text type: ALCODE number of text lines = 6 - REPLACE
    Deleted old text
    Write Text for element type APPLOG with id 753236628580446084256804325747607706 - Text type: ALCMNT number of text lines = 1 - REPLACE
    Deleted old text
    Recreating KCS_TENDERS Table API/Trigger Logic - Event: Pre-Before-Delete-row, Save old data.
    Write Text for element type APPLOG with id 753236628580474418455701543618889882 - Text type: ALCODE number of text lines = 404 - REPLACE
    Deleted old text
    Write Text for element type APPLOG with id 753236628580474418455701543618889882 - Text type: ALCMNT number of text lines = 1 - REPLACE
    Deleted old text
    Recreating KCS_TENDERS Table API/Trigger Logic - Event: Pre-Insert, Call CAPI.
    Write Text for element type APPLOG with id 753236628580568865785358936523163802 - Text type: ALCODE number of text lines = 4 - REPLACE
    Deleted old text
    Write Text for element type APPLOG with id 753236628580568865785358936523163802 - Text type: ALCMNT number of text lines = 1 - REPLACE
    Deleted old text
    Recreating KCS_TENDERS Table API/Trigger Logic - Event: Pre-Update, Call CAPI.
    Write Text for element type APPLOG with id 753236628580597199984256154394445978 - Text type: ALCODE number of text lines = 4 - REPLACE
    Deleted old text
    Write Text for element type APPLOG with id 753236628580597199984256154394445978 - Text type: ALCMNT number of text lines = 1 - REPLACE
    Deleted old text
    Recreating KCS_TENDERS Table API/Trigger Logic - Event: Pre-Delete, Call CAPI.
    Write Text for element type APPLOG with id 753236628580625534183153372265728154 - Text type: ALCODE number of text lines = 17 - REPLACE
    Deleted old text
    Write Text for element type APPLOG with id 753236628580625534183153372265728154 - Text type: ALCMNT number of text lines = 1 - REPLACE
    Deleted old text
    Recreating KCS_TENDERS Table API/Trigger Logic - Event: Post-Insert, Call CAPI.
    Write Text for element type APPLOG with id 753236628580653868382050590137010330 - Text type: ALCODE number of text lines = 7 - REPLACE
    Deleted old text
    Write Text for element type APPLOG with id 753236628580653868382050590137010330 - Text type: ALCMNT number of text lines = 1 - REPLACE
    Deleted old text
    Recreating KCS_TENDERS Table API/Trigger Logic - Event: Post-Update, Call CAPI.
    Write Text for element type APPLOG with id 753236628580682202580947808008292506 - Text type: ALCODE number of text lines = 144 - REPLACE
    Deleted old text
    Write Text for element type APPLOG with id 753236628580682202580947808008292506 - Text type: ALCMNT number of text lines = 1 - REPLACE
    Deleted old text
    Recreating KCS_TENDERS Table API/Trigger Logic - Event: Post-Delete, Call CAPI.
    Write Text for element type APPLOG with id 753236628580767205177639461622139034 - Text type: ALCODE number of text lines = 282 - REPLACE
    Deleted old text
    Write Text for element type APPLOG with id 753236628580767205177639461622139034 - Text type: ALCMNT number of text lines = 1 - REPLACE
    Deleted old text
    HSU_CAPF.create_or_find_capi_pack
    hsu_capi.find_plm (kcs_tnr_capi, 692754610572409851363604771392473242, CAPI).
    capi package found in the context folder
    BLPLM.UPD
    FREE_FORMAT_TEXT_FLAG......... = Y
    IMPLEMENTATION_NAME........... = kcs_tnr_capi
    PLSQL_MODULE_TYPE............. = PACKAGE
    SCOPE......................... = PUBLIC
    COMPLETION_STATUS............. = COMPLETED
    NAME.......................... = kcs_tnr_capi
    PURPOSE....................... = Custom API package for implementing Business Rules and supporting TAPI
    Recreated Package KCS/ KCS_TNR_CAPI, preserving only the Revision History.
    HSU_CAPF.add_tags_er_av
    bltext.get_lines_from_repository, p_text_type=CDINOT
    bltext.get_line_containing
    bltext.get_line_containing
    bltext.get_lines_from_repository, p_text_type=CDINOT
    bltext.get_line_containing
    bltext.get_line_containing
    bltext.get_lines_from_repository, p_text_type=CDINOT
    bltext.get_line_containing
    bltext.get_line_containing
    bltext.get_lines_from_repository, p_text_type=CDINOT
    bltext.get_line_containing
    bltext.get_line_containing
    HSU_CAPF.create_specification
    HSU_CAPF.create_c_tabalias
    HSU_CAPF.create_c_tabalias_all
    HSU_CAPF.create_aggregate_value
    HSU_CAPF.create_aggregate_value
    HSU_CAPF.create_aggregate_value
    Activity aborted with ORACLE internal errors.
    -6502 ORA-06502: PL/SQL: numeric or value error: character string buffer too small
    What can I do about it???
    Thanks in advance.
    Menno Hoogsteen

    Working on the same project as Menno, I had the time to look into the problem.
    The problem is caused by the creation of the capi-function agregate_char_value in the packages hsu_capf. While creating this function the following code is executed:
    add(' -- allowable values:');
    add(' -- '||l_col_name_list);
    This last statement causes the problem because this table is very big. L_col_name_list contains 2391 characters wich is 393 characters to long. So i changed this code into:
    add(' -- allowable values:');
    add(' -- '||substr(l_col_name_list,1,1990));
    add(' -- '||substr(l_col_name_list,1990));
    and everything works fine. Perhaps something for a patch?
    Kind regards,
    Ruben Spekle

  • Error when generating create table script

    Hi,
    I am trying to generate create table script from an existing table. But I get the following error when doing so,
    ORA-20001: Rem Unable to generate DDL for ORA-06502: PL/SQL: numeric or value error ORA-31605: the following was returned from LpxXSLResetAllVars in routine kuxslResetParams: LPX-1: NULL pointer ORA-22921: length of input buffer is smaller than amount requested .
    Any suggestions on what could be wrong?
    Thanks.
    -B

    this is my bad, i should have updated this thread when we originally troubleshot this issue...
    that error you're getting on htmldb.oracle.com when you try to generate ddl for tables and such is a manifestation of a database bug (#3372908) that's recently been filed. checking the worklog for that bug suggests that those guys are still working out the issue. unfortunately, there's no current work-around on htmldb.oracle.com at the moment. if you want to generate ddl for your objects, you'd have to query the appropriate data dictionary views to get the info you need.
    ...i'll update the htmldb.oracle.com interface in a bit to prevent other users from hitting this issue. so you know, this is only an issue on db versions 9.2.0.3 and 9.2.0.4 running on some platforms and only (as far as i know) those using the AL32UTF8 characterset ...which does include our hosted site for now.
    hope this helps,
    raj

  • Error when workflow created from Function Module

    Hi All,
    I am trying to implement leave module workflow for one of my requirement.
    when i create a leave from PTARQ transaction workflow it is being triggered, but when i tried to do the same from a custom function Module using the same FMs used in PTARQ, workflow initiated but stopped at initial stage( at switch branch )
    i went to SWI1 transaction and executed it manually, it end up with error saying ' Error when starting a SWITCH branch'
    what should i do to move it forward.
    Thanks,
    Krish.

    Hi Kishore,
    For leave workflow, SAP has the separate frame work. They called the FM SAP_WAPI_START_WORKFLOW and pass all necessary data's to Process the leave workflow.
    Its not advisable to overwrite the standard behavior. Please check your 'REQ' workflow container in the log. There will be a no data or Some data's might be Missed.
    Before Call the FM, make sure that all data's are passed to the Table parameter, SImple_Container.
    The reason for the Error in your workflow is, there is no data stored in REQ.STATUS container.
    please check the Workflow log.
    Thanks.

  • Error when I created a New DataSet on BI Publisher

    When I create a Dataset and i used a Query Builder.
    I used the database of SH. When I used only one table like Products I can see the results. But when I used more tables like Products and Sales and I created their joins with product_id and when I want to view the results. I have the next error.
    500 Internal Server Error
    Servlet error: An exception occurred. The current application deployment descriptors do not allow for including it in this response. Please consult the application log for details.
    What it's the reason of this problem?
    Thank you for your help.

    What does the application log show?
    root part of your install\oc4j_bi\j2ee\home\application-deployments\xmlpserver\application.log

  • Validation errors when execute create method

    i have two pages, list.jsff and edit.jsff there is a create button in list.jsff, when click the button ,execute a taskflow ,go through a create method to edit.jsff,
    in tp3 ,it goes ok,but in tp4, it prompt many validate errors.how can i block the validate when i execute create method?

    I have resolved the issue. It had to do with the autocommit settings for the database connections. By default autocommit is true when we create the database connection. The autocommit can be turned off by appending relaxAutoCommit=true in the url for the connection.

  • Error when calling create and update functions on logical data service

    Hi There,
    I receive the following error when trying to call the createCustomerDetailResponse method from our dataservice. Note that the operation referenced in the error is createCustomerDetail rather than the actual method name 'createCustomerDetailResponse'. I've attached a stack trace as well as a copy of our .ds & code. Thanks, any help would be greatly appreciated!
    mlns:bea_fault="http://www.bea.com/servers/wls70/webservice/fault/1.0.0">javax.xml.rpc.JAXRPCException: Can not
    locate the operation: {ld:CustomerMaster/Logical/CustomerDetail_ws}createCustomerDetail
         at com.bea.dsp.ws.WssInboundHandler.operationLookup(WssInboundHandler.java:252)

    I think there is a definitely a problem with my ALDSP webservice. I deleted and regenerated my .ws file, and when I test the createCustomerDetailResponse webservice operation directly through the ALDSP IDE I get the same error.
    createCustomerDetailResponse Request Summary
    Arguments: [complex type]
    Fault: Failed to process inbound requestFailed to retrieve operation from SOAP bodyCan not locate the operation: {ld:CustomerMaster/Logical/CustomerDetail_ws}createCustomerDetail
    Submitted: Wed Mar 05 16:37:53 EST 2008
    Duration: 9 ms

  • Error when trying to deploy crystal reports to a web site

    I'm using VS 2008.  When I add a Crystal Report page to my application I get the following error.
    Can anyone help be resolve this problem?
    Server Error in '/' Application.
    Configuration Error
    Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.
    Parser Error Message: Could not load file or assembly 'CrystalDecisions.Web, Version=10.5.3700.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' or one of its dependencies. The system cannot find the file specified.
    Source Error:
    Line 110:               <add path="ScriptResource.axd" verb="GET,HEAD" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" validate="false"/>
    Line 111:               <add path="Reserved.ReportViewerWebControl.axd" verb="*" type="Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" validate="false"/>
    Line 112:               <add verb="GET" path="CrystalImageHandler.aspx" type="CrystalDecisions.Web.CrystalImageHandler, CrystalDecisions.Web, Version=10.5.3700.0, Culture=neutral, PublicKeyToken=692fbea5521e1304"/></httpHandlers>
    Line 113:          <httpModules>
    Line 114:               <add name="ScriptModule" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
    Source File: C:\InetPub\Websites\church-site_org\web.config    Line: 112
    Assembly Load Trace: The following information can be helpful to determine why the assembly 'CrystalDecisions.Web, Version=10.5.3700.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' could not be loaded.
    WRN: Assembly binding logging is turned OFF.
    To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
    Note: There is some performance penalty associated with assembly bind failure logging.
    To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
    Version Information: Microsoft .NET Framework Version:2.0.50727.1433; ASP.NET Version:2.0.50727.1433

    Hi,
    I also encountered problem: Could not load file or assembly 'CrystalDecisions.Web, Version=10.5.3700.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' or one of its dependencies. The system cannot find the file specified.
    I try to install the CRRedist2008_x64.msi in our web server. And its ok. But my problem now is the report i created in VS 2003. The error now is:
    Parser Error Message: File or assembly name CrystalDecisions.CrystalReports.Engine, or one of its dependencies, was not found.
    Source Error:
    Line 22:           debugging ASP.NET files.
    Line 23:     -->
    Line 24:     <compilation defaultLanguage="vb" debug="true"><assemblies><add assembly="CrystalDecisions.CrystalReports.Engine, Version=9.1.5000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304"/><add assembly="CrystalDecisions.ReportSource, Version=9.1.5000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304"/><add assembly="CrystalDecisions.Shared, Version=9.1.5000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304"/><add assembly="CrystalDecisions.Web, Version=9.1.5000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304"/></assemblies></compilation>
    Line 25:
    Line 26:     <!--  CUSTOM ERROR MESSAGES
    Source File: E:\INETPUB\WWWROOT\DTS\web.config    Line: 24
    Assembly Load Trace: The following information can be helpful to determine why the assembly 'CrystalDecisions.CrystalReports.Engine' could not be loaded.
    === Pre-bind state information ===
    LOG: DisplayName = CrystalDecisions.CrystalReports.Engine, Version=9.1.5000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304
    (Fully-specified)
    LOG: Appbase = file:///E:/INETPUB/WWWROOT/DTS
    LOG: Initial PrivatePath = bin
    Calling assembly : (Unknown).
    Please need your help.
    thanks

  • Error when Posting a Captivate 5 Aggregator Project on Web Server

    I created a 3 module aggregator project with a preloader jpg file using Captivate 5 and published as both a zip and html file.  When I play the html on my local machine, it plays fine.  But, when I have one of the web developers upload the zip files to the server she says that she gets a flash player error when she tries to test it. I've used the aggregator in Captivate 4 with no problems (when using AS2) so I'm not sure what could be causing this error.  Does anyone have any ideas?

    Hi Marion,
    I asked her to try again and here's what she said she did:
    I unzip the online library folder, double click the onlinelibrary.swf file(the  standard.js file is in the same folder), got the popup window as  follows
    After  I click ok, it play the movie. Then I upload the file to server, but it does not  work(frozen the server). So can you remake it again as the rest of all video  works just fine. BTW, I use flash player 9.
    Apparently, she tried it first on her machine which has flash player 9 and then only uploaded the single .swf file to the server.  I was told by another developer that she needs to add the standard.js code to the html file.  It appears she doesn't want to do this so I have to compile all the .cptx files into one. So, it looks like you were right about her testing locally, but she's also not uploading the files correctly on the server.
    Judy

Maybe you are looking for