Create Accounting Error in AR module

I have one AR invoice for which i have done one adjustment and after that while trying to do ceate accounting i am getting the following error :
*" The subledger journal entry does not balance in the entered currency. Please verify the entered amounts on the journal entry lines."*
So anyone can you help me with this issue .
Thanks and Regards
Edited by: user12991008 on Jul 22, 2011 3:03 PM

Hi Vamsi
Yes i have checked the accounting entries which are ggiven below
Line     Accounting Class     Account     Entered     Accounted
               Currency     Debit     Credit     Debit     Credit
1     Receivable     C7.AIS.A166.2249REC.999.9S.01     AUD     7,709.43          7,709.43     
               Journal Entry Total     7,709.43     0.00
Line     Error Number     Error Message
     0     The subledger journal entry does not balance in the entered currency. Please verify the entered amounts on the journal entry lines.
Also its not a foreign currency.
Thanks and Regards
Ritwik

Similar Messages

  • AP - Create Accounting Error

    Hi All,
    We are running the create accounting process from  AP , I am getting the below error . Need assistance since i have to fix this issue ASAP.
    The subledger journal entry does not balance in the entered currency.  Please verify the entered amounts on the journal entry lines.
    Please help
    Regards

    See this note:
    Create Accounting Error "The accounted amount and entered amount for the subledger jounral entry line have different sign" [ID 1165264.1]

  • Create Accounting error for receipt reversal

    Hi
    Hope every one is well and upbeat over here. I am facing an issue in the receivables module and some expert's kind assistance is required.
    A client entered a Miscellaneous receipt, the customer made the payment through credit card. The receipt was later reversed, When the client runs the create accounting report, it gives the following error
    Line     Error Number     Error Message
         0     The accounted amount and entered amount for the subledger jounral entry line have different sign. Please inform your system administrator or support representative that:
    The sources assigned to the accounting attributes Accounted Amount and Entered Amount have different sign for extract line number 738414. Please make sure the sources assigned to the two accounting attributes have same sign, or assign different sources to these accounting attributes.
    there is another error message which is:
    The subledger journal entry does not balance in the entered currency. Please verify the entered amounts on the journal entry lines.
    Please provide me with a solution to this problem.
    Regards
    Salman Tariq

    Please see these docs.
    Invoice Apparoval Throws Error App-Sqlap-10000 Ap_etax_services_pkg.Synchronize_for_doc_seq [ID 1158523.1]
    When Cancelling An Invoice User Receives Error APPSQLAP-10000 ORA-00000 normal, successful completion occured in AP_INVOICES_PKG.UPDATE_ROW [ID 886316.1]
    Error When Canceling Invoices APP-SQLAP-10000 AP_ETAX_SERVICES_PKG [ID 974712.1]
    Thanks,
    Hussein

  • Create accounting error :APP-SQLAP-100000,  ora-00000

    afer validate the AP credit memo. create accounting occured the error as below
    the first form 'NOTE :create accounting successfully'
    the secone form 'ERROR APP-SQLAP-10000:.........(x_rowid=AAAAHTUAAXAABIDYAA,X_invoice_id= 34345 ,ap_in:normal, successful completion : after callling AP_ETAK_SERVERICE_PKG,sysnchronize_for_doc_sep ()))'

    Please see these docs.
    Invoice Apparoval Throws Error App-Sqlap-10000 Ap_etax_services_pkg.Synchronize_for_doc_seq [ID 1158523.1]
    When Cancelling An Invoice User Receives Error APPSQLAP-10000 ORA-00000 normal, successful completion occured in AP_INVOICES_PKG.UPDATE_ROW [ID 886316.1]
    Error When Canceling Invoices APP-SQLAP-10000 AP_ETAX_SERVICES_PKG [ID 974712.1]
    Thanks,
    Hussein

  • AR Transaction Create Accounting Error APP-AR-96282

    HI Everyone,
    I need some urgent help.
    I can't create online accounting of AR transaction because of Error: APP-AR-96282.
    Autoaccounting has generated distributions for invoice properly & invoice is complete. Online Create accounting & even Accounting process is not able to generate accounting.
    I couldn't find any related material on metalink as well. Can anyone provide help ?
    Regards,
    Fahd
    Edited by: Fahd Khan on Aug 17, 2010 5:06 AM

    also doesn't produce any output or list any error.Check http://www.orafaq.com/node/2245
    Even it doesn't pick the transactions for accounting. Just receipts are getting accounted by Create Accounting program.Have you passed 'Receipts' for the Process Category parameter? If yes, leave it blank.
    Get AR Diagnostics Test Collection for that transaction and check whether the xla_transaction_entities / xla_events are proper.
    What is the event_status_code and process_status_code for event in xla_events?
    By
    Vamsi

  • AP Create Accounting - Error ORA-06512, XLA-95103, ORA-20001, ORA-20100

    *Hello all you patient Oracle Champs - I know issues like this are floating around the forum and web but I still can't seem to fine a match.*
    *> OA R12.1.3*
    *> Orcale Database Server 11.2.0.2*
    [010613_011550898][][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.
    Please inform your system administrator or support representative that:
    An internal error has occurred in the program XLA_CREATE_ACCT_RPT_PVT.print_logfile.
    ORA-20100: Error: FND_FILE failure. Unable to create file, o0104058.tmp in the directory, /usr/tm
    ORA-06512: at "APPS.APP_EXCEPTION", line 72
    *> Note the directory path cited: +/usr/tm+*
    *> A later error:*
    Oracle error 20100: java.sql.SQLException: ORA-20100: Error: FND_FILE failure.
    Unable to create file, o0104058.tmp in the directory, /usr/tmp.
    *> Note the directory: +/usr/tmp+*
    SQL> show parameter utl_file_dir
    utl_file_dir
    string /usr/tmp, /usr/tmp, /Develop_DB/DEV/11.2.0.2/appsutil/outbound/DEV_orcl-dev-db, /usr/tmp
    $ echo $APPLTMP
    /Develop_Appl/DEV/inst/apps/DEV_orcl-dev-appl/appltmp
    *> has read/write permissions (777)*
    $ echo $APPLPTMP
    /usr/tmp
    *> has read/write permissions (777)*
    *> There is plenty of space in /usr, /Develop_Appl*
    *> Patch 10131305 already applied per note: 1392267.1*
    *> SLA: Enable Diagnostics set to a null value (blank)*
    *> the file o0104058.tmp does not exist in either $APPLTMP or $APPLPTMP (i.e. note 460643.1)*
    *> I confirmed that note 749491.1 was not an issue*
    *> note 261693.1 did not seem to apply*
    *> note 148262.1 did not seem to apply*
    I can provide the concurrent & FND debug output if needed.
    Thank you all*
    Zippy the P

    Zippy242 wrote:
    Hi Hussein,
    checked 1252703.1 - it doesn't appear applicable:
    SQL> show parameter utl_file_dir
    utl_file_dir
    string /usr/tmp, /usr/tmp, /Develop_DB/DEV/11.2.0.2/appsutil/outbound/DEV_orcl-dev-db, /usr/tmp
    $ echo $APPLTMP
    /Develop_Appl/DEV/inst/apps/DEV_orcl-dev-appl/appltmp
    *> has read/write permissions (777)*
    $ echo $APPLPTMP
    /usr/tmp
    *> has read/write permissions (777)*
    checked 760614.1 - not the case:
    no invalid XLA%
    FUN_SEQ_BATCH both package and body are valid.
    Please Advise
    thanks,
    ZipAre you running all the application/database services on one server or multiple ones?
    Thanks,
    Hussein

  • 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

  • Error while trying to create a Universe on Function Module in IDT

    Hi,
    We are using BO 4.1 Support Pack 2. I am trying to create a Universe on Function Module. I created data foundation layer, but when I right click on the table and click on 'Show table values' it doesn't bring any data (and there is data available in that table). When I click on 'Check Integrity' it says 'Missing Primary key'. Please see the screen shot. Please let me know if any has any idea and I am doing something wrong? I really appreciate it.
    Thanks,
    Charvi.

    Hi Charvi,
    What type of database/application are you trying to connect? Are you getting any error message?
    Missing primary key message is just a warning and is not related to the issue.
    Cheers
    Mohan

  • Getting error when creating a RFQ in MM module" create rfq item overview"

    Hi,
    i am a beginer in SAP administration, users are getting this error message and i have done all my research and not able to resolve this issue.
    This error i am getting when creating a RFQ in MM module and when trying to save the screen "create rfq item overview" then it gives me a pop up box message " SAP SYSTEM MANAGER: WORK PROCESS RESTARTED, SESSION TERMINATED".
    Here are the details of teh system
    SAP Version :ideas 4.7
    Database :Oracle
    OS : windows 2003
    Module user is working on MM
    user working on it is a Super user with all the permissions
    SAP is configure to run under the  European date and decimal format.
    I have never done any database administration on it, it is a new install and has been rarely used.
    User creates a RFQ and when he tries saving it , seems like for the first time after either restarting the macine or restarting the service it might work and at time it might not, this is a very sporadic error and most of the times it crashes out with the message "sap system manager:work process restarted, session terminated" and kicks the user out of the session.
    Below are the details of the error message from ST22 :
    name of the runtime error : system_core_dumped
    below are the details of the error message and its resoltion as suggested by sap help :
    ========
    Runtime Errors         SYSTEM_CORE_DUMPED           
           Occurred on     01.02.2008 at 07:52:19
    Process terminated by signal " ".                                             
    What happened?
    The current ABAP program had to be terminated because the                     
    ABAP processor detected an internal system error.                             
    The current ABAP program "SAPLCLSC" had to be terminated because the ABAP     
    processor discovered an invalid system state.                                 
    What can you do?
                                                                                    Make a note of the actions and input which caused the error.                                                                               
    To resolve the problem, contact your SAP system administrator.                                                                               
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer      
    termination messages, especially those beyond their normal deletion           
    date.                                                                               
    Error analysis
    An SAP System process was terminated by an operating system signal.           
                                                                                    Possible reasons for this are:                                                
    1. Internal SAP System error.                                                 
    2. Process was terminated externally (by the system administrator).           
               Last error logged in SAP kernel                                    
                                                                                    Component............ "Taskhandler"                                           
    Place................ "SAP-Server server1_DEV_00 on host server1 (wp 1)"      
    Version.............. 1                                                       
    Error code........... 11                                                      
    Error text........... "ThSigHandler: signal"                                  
    Description.......... " "                                                     
    System call.......... " "                                                     
    Module............... "thxxhead.c"                                            
    Line................. 9555                                                                               
    How to correct the error
    The SAP System work directory (e.g. /usr/sap/c11/D00/work ) often             
    contains a file called 'core'.                                                                               
    Save this file under another name.                                                                               
    If you cannot solve the problem yourself, please send the                     
    following documents to SAP:                                                                               
    1. A hard copy print describing the problem.                                  
       To obtain this, select the "Print" function on the current screen.         
                                                                                    2. A suitable hardcopy prinout of the system log.                             
       To obtain this, call the system log with Transaction SM21                  
       and select the "Print" function to print out the relevant                  
       part.                                                                               
    3. If the programs are your own programs or modified SAP programs,            
       supply the source code.                                                    
       To do this, you can either use the "PRINT" command in the editor or        
       print the programs using the report RSINCL00.                                                                               
    4. Details regarding the conditions under which the error occurred            
       or which actions and input led to the error.                                                                               
    System environment
    SAP Release.............. " "                                                                               
    Application server....... " "                                                 
    Network address.......... " "                                                 
    Operating system......... " "                                                 
    Release.................. " "                                                 
    Hardware type............ " "                                                 
    Character length......... " " Bits                                            
    Pointer length........... " " Bits                                            
    Work process number...... " "                                                 
    Short dump setting....... " "                                                                               
    Database server.......... " "                                                 
    Database type............ " "                                                 
    Database name............ " "                                                 
    Database owner........... " "                                                                               
    Character set............ " "                                                                               
    SAP kernel............... " "                                                 
    Created on............... " "                                                 
    Created in............... " "                                                 
    Database version......... " "                                                                               
    Patch level.............. " "                                                 
    Patch text............... " "                                                                               
    Supported environment....                                                     
    Database................. " "                                                 
    SAP database version..... " "                                                 
    Operating system......... " "                                                 
    User, transaction...
    Client.............. " "                                                      
    User................ " "                                                      
    Language key........ " "                                                      
    Transaction......... "ME41 "                                                  
    Program............. "SAPLCLSC"                                               
    Screen.............. "SAPMM06E 0320"                                          
    Screen line......... 71                                                       
    Information on where termination occurred
    The termination occurred in the ABAP program "SAPLCLSC" in "EXECUTE_SELECT".  
    The main program was "SAPMM06E ".                                                                               
    The termination occurred in line 131 of the source code of the (Include)      
    program "LCLSCF2G"                                                           
    of the source code of program "LCLSCF2G" (when calling the editor 1310).      
    =============
    i even tried increasing the dialog processes but with no use.The same error occurs.
    I appreciate every one of help i can get, i am working on a deadline which is tomorrow evening to resovle this issue, any kind of help is highly appreciated.
    thanks
    mudessir.

    Hi Mudessir,
    With the help of ABAP'er try the following.
    1. open the program 'LCLSCF2G' from SE38.
    2. Keep a break point at line no: 131.
    There is 'END SELECT' statement which is getting failed at line no 131 in the program.
    Try to analyse the SY-SUBRC at that point.
    If your technical consultant can't solve this, write to SAP OSS (service.sap.com).
    I have searched SAP OSS, there are other situations, but your case is not there. So write to SAP if technical consultant can't solve it by debugging the program.
    Regards,
    Madhu.

  • Error creating accounting document for a credit note

    Hi All,
    I am facing an issue while creating an accounting document for the credit note created.
    The scenario is as follows:
    Created a credit memo --> created credit note --> create accounting document
    While creating accounting document, i'm getting an error message as 'The G/L account XXXXXXXX requires an assignement to CO object'.
    Please let me know why i'm getting this error and how to overcome this issue.
    Thanks,
    Anil Kumar

    While creating accounting document,
      i'm getting an error message
    First of all, I am not clear on your above statement as in normal circumstances, once you generate a credit memo, in bacground an accounting document will also be generated.
    In your case, I believe while saving the credit memo, system throws the error to maintain CO object in which case, do the following:-
    Go to TCode KA02 enter the controlling area, give the G/L acoount No and click on Master data tab.  There  select  "Default Acc Assgmnt" tab  and enter Cost centr and save.
    Next Go to FS00, input the G/L Account and click on Edit Cost Element on top.  There click on Basic Data and for the field CElem category, maintain the required numeric value.  Now select the tab Default Acct Assgnmt and there maintain the required cost center and save.
    thanks
    G. Lakshmipathi

  • Can someone tell me how to create accounting entries with the account status as error

    Hi,
    Can someone tell me how to create accounting entries with the
    account status as error?
    Thanks!!
    Danny

    It's call fixed/static background, and it is NOT directly support by iweb, you will need post processing either in html or javascript.
    Varkgirl (you need to search the previous forum) and I did it since iweb1:
    try Safari, and scroll: http://www.geocities.com/[email protected]/Links.html
    invisible link? roddy, fishing for info again?

  • Get message "Error creating account: Incoming server already exists."

    trying to set up new IMAP account and get message "Error creating account: Incoming server already exists." Changed settings manually, but same error message.

    ''ScottNH [[#question-1040338|said]]''
    <blockquote>
    trying to set up new IMAP account and get message "Error creating account: Incoming server already exists." Changed settings manually, but same error message.
    </blockquote>
    I have been getting this too (for the last two days - on at least a dozen tries).
    I am Running Win7 and already have three POP accounts.
    All definitely have the incoming server pop.googlemail.com
    I wanted to add a new IMAP account, so in T'Bird
    Tools.... Account Settings
    Account Actions ..... Add Mail Account
    Filled in
    my name,
    the email address ([email protected] - and in gmail this mail account
    was created as IMAP),
    password (with a tick to remember this)
    ... continue
    and it then detected the mail setup as IMAP,
    Incoming : IMAP, imap.googlemail.com , SSL
    Outgoing : SMTP, smtp.googlemail.com , SSL
    Username: [email protected]
    but when I then clicked on Done
    it said Error Creating Account - Incoming server already exists.
    And if I then clicked on OK followed by Manual Config, it then showed
    in the Mail Account Setup
    Incoming: IMAP imap.googlemail.com 993 SSL/TLS Normal Password
    and again if I then clicked Done it gave the same error message as before.
    (and I have screenshots to support all of this).
    But I do not know if someone has been working on a fix to T'Bird or googlemail, because just now when I did it yet again in order to make a final check that what I have been writing here is correct , this time I did NOT get the error message and the new account has been setup!!!!!
    So do others find this has now been cleared too?

  • HT4872 I have not been able to import contacts from google or my android to my new I-phone 5. This article helps to a point until error message "cannot create account" already exist is received. Please help.

    I have not been able to import contacts from google or my android to my new I-phone 5. This article helps to a point until error message "cannot create account ... already exist" is received. Please help.

    -Reece,
    We only have 1 single domain, 1 domain forest, no subdomains, only alias. I had replied to the other post as well. But I am happy to paste it here in case anyone want to read it.
    So, after a few months of testing, capture and sending logs back and forth to Apple Engineers, we found out there is a setting in AD, under User Account that prevent us to log into AD from Mountain Lion. If you would go to your AD server, open up a user account properties, then go to Account tab, the "Do not require Kerberos preauthentication" option is checked. As soon as I uncheck that option, immediately I was able to log into AD on the Mac client. Apple engineers copied all my AD settings and setup a test environment on their end and match exact mine AD environment. They was able to reproduce this issue.
    The bad part about this is... our environment required the "Do not require Kerberos preauthentication" is checked in AD, in order for our users to login into some of our Unix and Linux services. Which mean that it is impossible for us to remove that check mark because most, if not all of them some way or another require to login into applications that run on Unix and Linux. Apple is working to see if they can come up with a fix. Apparently, no one has report this issue except us. I believe most of you out there don't have that check mark checked in your environment... Anyone out there have any suggestion to by pass or have a work around for this?

  • Function Module/BAPI to create Account Hierarchies in CRM.

    Hi Experts,
    Is there any standard function module to create account hierarchy in SAP, from the data we receive from the legacy system.
    Please let me know BAPI/FM name
    Can we use LSMW for uploading the account hierarchies?
    Moderator Please i have done enough research before posting this thread.
    Thanks.
    Vikki

    Hi,
    I got the FM name .
    I am using F.M. BUHI_EXT_INTERFACE_SAVE  for this purpose.
    Special Thanks to AJIT PAWAR for his help.
    Regards
    Vikash
    Edited by: vikashsingh1234 on Apr 18, 2011 7:46 AM

  • Azure mobile services error cannot find module 'azure-storage'

    this is driving me nuts for past five days now and still no solution. After asking the questing at StackOverflow and azure-storage npm, I thought of now posting the same question here so that it reaches to more targeted 'microsoft azure' experts. 
    in my AzureMobileService, I am using azure-storage npm module in one of my custom API. I have been using this for past couple of months and it was all working great, I was very happy. Until last moday it started throwing the error - 'cannot find module
    'azure-storage'. It was strange, the code that was working till morning , started failing when I came back from work, with no change of a bit in the code. I get this error where I call 'require' for 'azure-module':
    var azure = require('azure-storage');
    var retryOperationFilter = new azure.ExponentialRetryPolicyFilter();
    var tableService= azure.createTableService().withFilter(retryOperationFilter);
    and in package.json, I have
    "dependencies": {"tracer": "0.7.3", "colors" : "1.0.3", "lodash" :"2.4.1", "azure-storage": "0.4.1"},
    Today, I also tried creating a new Mobile service from scratch in my azure account. Then I created the custom API and wrote the code again from scratch. Updated package.json to include azure-storage, updated my client code(HTML/JS) to use this new service
    URL etc. and tested again, everything worked fine till it reached the same line (require('azure-storage') ) and failed again there with
    same error.
    I am at my wits end. please help. 

    ok, got it working.
    I did an npm install 'azure-storage'  to my mobile service's service directory and then it started working. 
    As I remember reading, if I just include the npm module I want to use in my mobile service's package.json, it gets taken care, installed and I don't to install myself manually.
    And thats what has been happening when my code was working till last week. 
    Also, its feels odd because the other node modules I use - like tracer or lodash - work with no manual npm install. 
    anyways, its working for now, but now I am thinking about the azure mobile's reliability

Maybe you are looking for