Error in executing transaction

Hi all,
        I created a transaction. While I am trying to executing the transaction, I got the error message as " org.apache.xerces.dom.TextImpl  " - Action failed. ( I got this error in normalization action).
What has to be done to rectify this error?
Thanks & Regards,
P.S.Kishore kumar

Hi Kishore,
            In normalize action block, your input is a XML variable with multiple rowsets having a common column name. And it should also contain the same number of rows in each rowset.
            I hope this will help to solve your problem.
Thanks,
Rajesh

Similar Messages

  • Error while executing transaction in logic editor

    Hi all,
    When i try to execute a transaction in logic editor in my system i get the following error.
    [DEBUG]: Transaction Complete.
    [ERROR]: Error executing transaction Status (403):ok
    But when i try to exectue the same in a different system,the transaction is sucessfully executed.could anyone help me out with is issue!

    U better try to clear the cache enteries and try this.it may help

  • Runtime error while executing transaction BDLS

    Hello,
    While executing BDLS transaction for converting logical system names I am getting following error
    Runtime Errors         CONVT_NO_NUMBER
    Except.                CX_SY_CONVERSION_NO_NUMBER
    Short text
         Unable to interpret "7,160 " as a number.
    How to resolve the above problem?

    Hi Rachel,
    BDLS creates an ABAP program SBDLS* which includes all the tables possibly including logical system names as of the domain behind the table fields. This program firstly    
    lives in runtime only and is checked by syntax checker.                 
    Now, sometimes tables have inconsistencies associated with them and you 
    will get this dump when a syntax check is performed on them.            
    So please check this and regenerate the culprit tables.                                                                               
    So please redo the steps for BDLS and check. There are     
    probably some tables which could be determined by you (syntax           
    check - in case program has already been saved only)                                                                               
    An easy way to check this is to run RBDLS2LS program (old BDLS) and     
    afterwards performing a syntax check on generated RBDLS*** (RBDLS<(>    
    <<)>(>                                                                  
    <<(><<)>)>ClientName>) program. 
    Known tables which caused such dumps in the past are:
    DFKKCOLFILE_P_W
    DFKKKO         
    DFKKMKO        
    DFKKREP06      
    DFKKREP06_S    
    DFKKREP07      
    DFKKREV06      
    DFKKREV07 
    Simply reactivate the tables you find out in SE11.                                                                               
    Another thing which has lead to this dump in the past is                
    in your R/3-System the value ' x ' is                                   
    additionally added to the value of your current release in the basis    
    release table SVERS.                                                    
    The table RSBASIDOC takes the release value from the table SVERS.       
    If you change value 'x' to your release in both tables (SVERS and       
    RSBASIDOC) and                                                          
    and activate again your source system connection. This could solve the 
    dump too.   
    I hope, this helps-if not, pls open a message with SAP.(component: BC-MID-ALE)
    b.rgds, Bernhard

  • Error While Executing Transaction Through SSO

    Hi Guys,
    I am trying SSO between Portal 6.0 and BW 3.5
    I have added my BW system into Portal, RFC as well as JCo is working fine.
    While executing any transaction its giving me following error.
    http://<host_name>:<Port>/sap/bc/gui/sap/its/webgui call was terminated because the corresponding service is not available.
    The termination occurred in system <SID> with error code 403 and for the reason Forbidden.*
    The selected virtual host was 0 .*
    ErrorCode:ICF-NF-http-c:000-u:SAPSYS-l:E-i:<host_name>_<SID>_<nr>-v:0-s:403-r:Forbidden
    Appretiate your response
    Regards,
    Sachin

    Sachin,
    Please refer to these links, you can have a look at the check list to figure out if you might have forgotten or missed a step while configuring the SSO.
    Single Sign On between EP6.0 and BW 3.5
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/ep/sso%2bchecklist
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6535e690-0201-0010-6989-9e27386e1f24
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/ep/portal+implementation&
    http://help.sap.com/saphelp_nw2004s/helpdata/en/d3/41c8ecb31d11d5993800508b6b8b11/content.htm
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/21eb036a-0a01-0010-25a3-b2224432640a
    Reward points if handy!
    Cheers,
    Sandeep

  • Runtime error when executing transaction 'PPOME'

    Hi all,
    <br>
    <br>
    <br>I 'm new to SAP and would like to beg a helping hand.
    <br>I had tired the 'free search' function in PPOME.
    <br>and I m not sure what mistake I make. When I execute t-code PPOME again, it is getting the runtime error.
    <br>
    <br>the following are the descritpion of exception by T-code ST22.
    <br>the error is related to u201CSAP_IN_ITAB_ILLEGAL_OPTIONu201D and I read the its SAP NOTE(1256059).
    <br>However, I don't how to do so that fix this problem.
    <br>May anyone help me~
    <br>
    <br>----
    <br><b>Short text</b>                                                                        
    <br>Invalid value in OPTION field of value table for IN itab operator.                           
    <br>
    <br><b>What happened?</b>                                                                               
    <br>    Error in the ABAP Application Program                                                        
    <br>                                                                               
    <br>    The current ABAP program "%_T0DQG0" had to be terminated because it has                   
    <br>    come across a statement that unfortunately cannot be executed.
    <br>
    <br><b>Error analysis</b>                                                                               
    <br>    The current ABAP/4 program attempted to execute an ABAP/4 Open SQL                           
    <br>    statement in which the WHERE condition contains an IN itab operator.                         
    <br>                                                                               
    <br>    The IN itab operator is used with internal tables which                                      
    <br>    have the following structure:                                                                
    <br>                                                                               
    <br>       SIGN(1)   OPTION(2)   LOW LIKE db_field   HIGH LIKE db_field                              
    <br>                                                                               
    <br>    The OPTION column should contain only one of the following values:                           
    <br>                                                                               
    <br>       "EQ LE GE CP BT NE LT GT NP NB"                                                           
    <br>                                                                               
    <br>    The value " " is not allowed here.                                                           
    <br>
    <br><b>How to correct the error</b>                                                                        
    <br>    Use only one of the permitted values in the OPTION column.                                   
    <br>                                                                               
    <br>    If the error occures in a non-modified SAP program, you may be able to                       
    <br>    find an interim solution in an SAP Note.                                                     
    <br>    If you have access to SAP Notes, carry out a search with the following                       
    <br>    keywords:                                                                               
    <br>                                                                               
    <br>    "SAPSQL_IN_ITAB_ILLEGAL_OPTION" " "                                                          
    <br>    "%_T0DQG0" or "%_T0DQG0"                                                                     
    <br>    "GET_OBJECTS"                                                                               
    <br>                                                                               
    <br>    If you cannot solve the problem yourself and want to send an error                           
    <br>    notification to SAP, include the following information:                                      
    <br>                                                                               
    <br>    1. The description of the current problem (short dump)                                       
    <br>                                                                               
    <br>       To save the description, choose "System->List->Save->Local File                           
    <br>    (Unconverted)".                                                                               
    <br>                                                                               
    <br>    2. Corresponding system log                                                                  
    <br>                                                                               
    <br>       Display the system log by calling transaction SM21.                                       
    <br>       Restrict the time interval to 10 minutes before and five minutes                          
    <br>    after the short dump. Then choose "System->List->Save->Local File                            
    <br>    (Unconverted)".                                                                               
    <br>                                                                               
    <br>    3. If the problem occurs in a problem of your own or a modified SAP                          
    <br>    program: The source code of the program                                                      
    <br>       In the editor, choose "Utilities->More                                                    
    <br>    Utilities->Upload/Download->Download".                                                       
    <br>                                                                               
    <br>    4. Details about the conditions under which the error occurred or which                      
    <br>    actions and input led to the error.                                                          
    <br>
    <br><b>User and Transaction</b>                                                                            
    <br>                                                                               
    <br>    Client.............. 300                                                                     
    <br>    User................ "xxxxxxxx"                                                             
    <br>    Language key........ "E"                                                                     
    <br>    Transaction......... "PPOME "                                                                
    <br>    Transactions ID..... "26F031E14FDBF1E0BB3500155D7F2106"                                      
    <br>                                                                               
    <br>    Program............. "%_T0DQG0"                                                              
    <br>    Screen.............. "SAPMSSY0 1000"                                                         
    <br>    Screen line......... 6                                                                       
    <br>
    <br>
    <br><b>Information on where terminated</b>                                                                 
    <br>    The termination occurred in the temporary subroutine pool "%_T0DQG0" in                      
    <br>    "GET_OBJECTS".                                                                               
    <br>    The main program was "OM_START_NF ".                                                         
    <br>                                                                               
    <br>    The point of termination in the source code is in line 69 of                                 
    <br>    the temporary subroutine pool "%_T0DQG0".
    <br>
    <br>Edited by: jack22000011 on Dec 29, 2011 9:05 AM
    Edited by: jack22000011 on Dec 29, 2011 9:11 AM

    Hi all,
    I am getting the exact same dump.
    And in my case, I am not providing any input.
    I have made a non-obligatory selection screen  parameter, and then appended that to a table type of the local structure of select options that i made.
    Then i am passing this to a fm as an importing parameter.
    And it is giving dump on the first query in the fm.
    If I don't use the fm, then in that case, it is working fine, and if the field is blank it fetches all records,
    but why it is not working now..., any ideas???

  • Error while executing Transaction S_ALR_87012043

    Hi All,
    I am getting the following error while running the Transaction S_ALR_87012043 - G/L Account Balances.
    *Error Message: 'Variant SAP&001 of program RFSSLD00 is not the current version'
    the long text says*
    Variant SAP&001 of program RFSSLD00 is not the current version
    Message no. DB634
    Diagnosis
    You attempted to start report RFSSLD00 using variant SAP&001. Since this variant was generated, the report SELECT-OPTIONS or PARAMETERs have changed considerably, i.e. the type or length no longer match and PARAMETERs have become SELECT-OPTIONS or vice versa. Many of these changes are so serious that even attempting to import the variant results in runtime errors.
    Procedure
    Adjust or delete the variant.
    Is there any OSS notes available for this error??
    Regards
    Andrew

    Thank You Ravi.
    I got the OSS Notes specifically for that Error.
    Note:1066048 -  RFSSLD00: Variants obsolete.
    Once again Thanks for your immediate reply.
    Problem Solved.
    Cheers
    Andrew

  • Runtime Errors: CONVT_OVERFLOW while executing transaction sm66

    Hello Everyone,
    There are two Application serevrs out of which I am getting the following error while executing transaction SM66 only in one i.eCI server but if i remote login to other system and try SM66 its working fine.
    Please suggest
    Runtime Errors         CONVT_OVERFLOW
    Exception              CX_SY_CONVERSION_OVERFLOW
    Date and Time          02.04.2011 00:41:01
    Short text
         Overflow when converting from "2.90113e+09"
    Error analysis
         An exception occurred that is explained in detail below.
         The exception, which is assigned to class 'CX_SY_CONVERSION_OVERFLOW', was not
          caught in
         procedure "TH_WP_DETAIL_INFO" "(FUNCTION)", nor was it propagated by a RAISING
          clause.
         Since the caller of the procedure could not have anticipated that the
         exception would occur, the current program is terminated.
         The reason for the exception is:
         When attempting to convert the value "2.90113e+09",
         an overflow occurred.
         There is probably an error in the program
         "SAPLTHFB".
    How to correct the error
         Probably the only way to eliminate the error is to correct the program.
         You may able to find an interim solution to the problem
         in the SAP note system. If you have access to the note system yourself,
         please use the following search criteria:
         "SAPLTHFB" "CONVT_OVERFLOW"
    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.
    The exception must either be prevented, caught within proedure
    "TH_WP_DETAIL_INFO" "(FUNCTION)", or its possible occurrence must be declared
      in the
    RAISING clause of the procedure.
    To prevent the exception, note the following:
    tem environment
    SAP-Release 700
    Application server... "POSDMCI"
    Network address...... ""
    Operating system..... "SunOS"
    Release.............. "5.10"
    Hardware type........ "sun4u"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 1
    Shortdump setting.... "full"
    Database server... "POSDMDB"
    Database type..... "ORACLE"
    Database name..... "BP2"
    Database user ID.. "SAPSR3"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Apr 2 2006 21:14:52"
    create on........ "SunOS 5.9 Generic_117171-13
    Database version. "OCI_101 "
    Patch level. 52
    Patch text.. " "
    Database............. "ORACLE 9.2.0.., ORACLE
    SAP database version. 700
    Operating system..... "SunOS 5.9, SunOS 5.10"
    Memory consumption
    Roll.... 16192
    EM...... 8379696
    Heap.... 0
    Page.... 40960
    MM Used. 720912
    MM Free. 3466336
    Information on where terminated
        Termination occurred in the ABAP program "SAPLTHFB" - in "TH_WP_DETAIL_INFO".
        The main program was "SAPMSM66 ".
        In the source code you have the termination point in line 82
        of the (Include) program "LTHFBU26".
        The termination is caused because exception "CX_SY_CONVERSION_OVERFLOW"
         occurred in
        procedure "TH_WP_DETAIL_INFO" "(FUNCTION)", but it was neither handled locally
         nor declared
        in the RAISING clause of its signature.
        The procedure is in program "SAPLTHFB "; its source code begins in line
        1 of the (Include program "LTHFBU26 ".

    Hello Everyone,
    There are two Application serevrs out of which I am getting the following error while executing transaction SM66 only in one i.eCI server but if i remote login to other system and try SM66 its working fine.
    Please suggest
    Runtime Errors         CONVT_OVERFLOW
    Exception              CX_SY_CONVERSION_OVERFLOW
    Date and Time          02.04.2011 00:41:01
    Short text
         Overflow when converting from "2.90113e+09"
    Error analysis
         An exception occurred that is explained in detail below.
         The exception, which is assigned to class 'CX_SY_CONVERSION_OVERFLOW', was not
          caught in
         procedure "TH_WP_DETAIL_INFO" "(FUNCTION)", nor was it propagated by a RAISING
          clause.
         Since the caller of the procedure could not have anticipated that the
         exception would occur, the current program is terminated.
         The reason for the exception is:
         When attempting to convert the value "2.90113e+09",
         an overflow occurred.
         There is probably an error in the program
         "SAPLTHFB".
    How to correct the error
         Probably the only way to eliminate the error is to correct the program.
         You may able to find an interim solution to the problem
         in the SAP note system. If you have access to the note system yourself,
         please use the following search criteria:
         "SAPLTHFB" "CONVT_OVERFLOW"
    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.
    The exception must either be prevented, caught within proedure
    "TH_WP_DETAIL_INFO" "(FUNCTION)", or its possible occurrence must be declared
      in the
    RAISING clause of the procedure.
    To prevent the exception, note the following:
    tem environment
    SAP-Release 700
    Application server... "POSDMCI"
    Network address...... ""
    Operating system..... "SunOS"
    Release.............. "5.10"
    Hardware type........ "sun4u"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 1
    Shortdump setting.... "full"
    Database server... "POSDMDB"
    Database type..... "ORACLE"
    Database name..... "BP2"
    Database user ID.. "SAPSR3"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Apr 2 2006 21:14:52"
    create on........ "SunOS 5.9 Generic_117171-13
    Database version. "OCI_101 "
    Patch level. 52
    Patch text.. " "
    Database............. "ORACLE 9.2.0.., ORACLE
    SAP database version. 700
    Operating system..... "SunOS 5.9, SunOS 5.10"
    Memory consumption
    Roll.... 16192
    EM...... 8379696
    Heap.... 0
    Page.... 40960
    MM Used. 720912
    MM Free. 3466336
    Information on where terminated
        Termination occurred in the ABAP program "SAPLTHFB" - in "TH_WP_DETAIL_INFO".
        The main program was "SAPMSM66 ".
        In the source code you have the termination point in line 82
        of the (Include) program "LTHFBU26".
        The termination is caused because exception "CX_SY_CONVERSION_OVERFLOW"
         occurred in
        procedure "TH_WP_DETAIL_INFO" "(FUNCTION)", but it was neither handled locally
         nor declared
        in the RAISING clause of its signature.
        The procedure is in program "SAPLTHFB "; its source code begins in line
        1 of the (Include program "LTHFBU26 ".

  • Runtime error when executing ME2B/ME3B if condition recs 160

    Dear all,
    I have created a vendor rebate agreement and entered condition records for a vendor/material combination.
    Since for this vendor there are 170 materials for which he provides rebate I have created 170 condition records.
    When I am trying to change or display the rebate agreement by executing transaction codes ME2B and ME3B respectively the following run time error occurs (Runtime error when executing transaction codes ME2B/ME3B for condition recrds >160):
    Runtime Errors: DBIF_RSQL_INVALID_RSQL
    Except. CX_SY_OPEN_SQL_DB
    The error is in function module SELECT_TEXT at line 120 "select * from stxh client specified into table stxh_buffer".
    When I debug or test/execute the function module SELECT_TEXT, I find that there are no relevant entries in table STXH for the vendor rebate agreements.
    Please note that if the condition records of the rebate agreement are 160 and less then there is no problem.
    I would appreciate if I could have your expert oppinion on what is causing this runtime error and if it is possible on how to resolve it.
    Thanks in advance.
    Regards,
    Mimis
    Edited by: Mimis1973 on Jan 26, 2011 11:18 AM
    Edited by: Mimis1973 on Jan 26, 2011 11:20 AM
    Edited by: Mimis1973 on Jan 26, 2011 11:23 AM

    There's something similar in OSS note 1002788. Is it relevant to your system?

  • Error while executing the CKMLCP (Actual Costing) Transaction

    Hi Expert,
    I am getting the following Error while executing the CKMLCP (Actual Costing) Transaction through my User ID in system. If we execute the same transaction  with other user id then there is no Error. same role is assign to both user. Try to check SU53 screen shot but it show no error
    See the below error for referance:-
    Internal error in program SAPLCKML_RUN_COCKPIT_ACT
    Message no. CKMLRUN004
    Diagnosis
    An unexpected situation has appeared in program SAPLCKML_RUN_COCKPIT_ACT.
    The problem has to do with a program error - the indirect result of a program error or an inconsistency in Customizing.
    System Response
    Processing had to be terminated.
    Procedure
    Inform your system administrator
    Thanks
    Dinesh

    Hi Shyam,
    Thanks Shyam,
    I check this note this is not applicable for my system, In mention note Correction delivered in Support Package 600.
    but support Package in my system SAP_APPL 603 SAPKH60303,
    Is there any other note or solution for 603 SP
    Thanks
    Dinesh

  • [Execute SQL Task] Error: Executing the query failed with error: "The COMMIT TRANSACTION request has no corresponding BEGIN TRANSACTION."

    I have an package with source , data flow and destination to execute on begin and commit.
    in the below i have just used for questioning purpose with diagram removing my Data Flow task explaining my problem
    on execution, i get error as
    [Execute SQL Task] Error: Executing the query "COMMIT TRAN DimCompanyCode" failed with the following error: "The COMMIT TRANSACTION request has no corresponding BEGIN TRANSACTION.". Possible failure reasons: Problems with the query, "ResultSet"
    property not set correctly, parameters not set correctly, or connection not established correctly.
    as mentioned , i have checked the ResultSet, parameters , connection establish.. all are fine.
    Kindly advice on what has to be done.
    ShanmugaRaj

    To avoid this error, the RetainSameConnection property should set to 'True' for the Connection Manager - Application_DB.
    Narsimha

  • Error executing transaction: org/apache/xpath/XPathAPI

    I have imported one transaction from 12.0.5 MII verstion to 12.1 version and got the following error while running. I think this error is related to some java class. Could you please tell me where to pu the jar for solving this error.
    In case this error comes due to some other problem please let me know
    Transaction Complete.
    Error executing transaction: org/apache/xpath/XPathAPI

    Hi,
            Now I understood the problem and it is related to the dependency jar files.  For running my custom actions I have the
    dependency of 2 jar files . One is sqljdbc.jar and second is xalan.jar.  sqljdbc.jar I have added in the following way. Can anyone tell me how can I add the xalan.jar in catalog.xml file
    <?xml version="1.0" encoding="UTF-8"?>
    <ComponentCatalog >
         <Category Name="My Functions" Description="My Custom Objects">
              <Component Type="Action" Name="XAController12" Description="" Label="XA Controller" ClassName="com.my.xacute.actions.XAController12" AssemblyName="my.jar" Dependencies="sqljdbc.jar"/>
         </Category>
    </ComponentCatalog>
    Thanks
    Shaji

  • Error SG 105 when executing transaction KKAK

    Hi,
    When executing transaction KKAK (Results Analysis) for month end processing we get the following error for a especific sales order:
    "E SG105 Enter rate CAD/USD rate type P for 01/01/2010 in the system settings"
    My question will be: why is the system asking to enter that rate which we never use. We use rate M but not P. Is that really necessary?
    We are using release 470, level 003, Support Package SAPKH47031.
    Thanks for your help.

    HI,
    in the year-depending parameters of the controlling area version definition, the ex.rate type (P) and the valid-from-date is defined, thats why P is used.
    Best regards, Christian

  • Runtime error in KEFC Transaction while uploading CSV format file

    Hi Experts,
    This is regarding Runtime Error while executing the KEFC transaction in R3D.
    It is working successfully while uploading the file in Text format. But there is run time error while uploading in CSV format.
    It showing "The transfer was terminated.However,content errors occured" .
    Please provide the solution.
    Thanks in advance.
    Regards,
    Priya.

    Hi,
    To upload a CSV file it is used FM:
    CALL FUNCTION 'TEXT_CONVERT_CSV_TO_SAP'
    EXPORTING
    i_field_seperator = ';'
    I_LINE_HEADER =
    i_tab_raw_data = lt_file
    i_filename = p_filename
    TABLES
    i_tab_converted_data = p_table
    EXCEPTIONS
    conversion_failed = 1
    OTHERS = 2
    Please check what separetor this fm and your file are using. It should be the same.
    Regards,
    Fernando

  • Error while executing the function module BAPI_RE_CN_CREATE

    Dear All
    I was using the the function module BAPI_RE_CN_CREATE.  When I am trying to execute the function module I am getting the error message u201CBusiness transaction RECN doest existu201D. While inputting the parameters for the function module I have given RECN   In the input field TRANS. Requesting you to please kindly suggest.
    Regards.
    Varaprasad

    Hi Varaprasad,
    please try the following.
    1. Create a contract manually in the system
    2. Use BAPI_RE_CN_GET_DETAIL to show how the fields and structures are filled.
    3. Check and change the parameters for BAPI_RE_CN_CREATE accordingly.
    Hope that helps.
    Regards, Franz

  • Error while executing the application

    Hi Friends,
    I am getting error while executing the application.The error is
    "javax.ejb.EJBException: Transaction aborted; nested exception is: javax.transaction.RollbackException: Transaction marked for rollback."
    Can anybody help me..
    Thanks in advance.

    You need to step through a debugger and find the source of your problem as something is clearly going wrong and causing the transaction to roll back. That is all that message tells us.
    m

Maybe you are looking for

  • Only first plot of waveform chart has run-time menu

    Hello again all you helpful forum-goers! My multi-plot waveform chart is working decently well, but now for some reason only the first plot in the plot legend displays a run-time customization menu when I click on it while the VI is running (allowing

  • External Display Causing MacBook Screen Edge Darkening?

    I recently purchased a Dell 2209WA monitor (rotated to portrait) and since using it I've noticed that my MacBook screen has a shadow down the right hand side. Now I'm assuming that some part of this new monitor isn't suitably shielded and is affectin

  • Concept between FI-CA, FI-AR, and FI-AP

    Dear FI-CA gurus Please help me to understand the concept of relationship between FI-CA, FI-AR, and FI-AP. Our customer is in utility industry. They have both of corporate customer and personal customer. So, in this case, all customers and suppliers

  • I changed my apple ID, now I can't download my purchases

    After changing my apple ID, I can no longer download anything I originally purchased like movies or apps.

  • LO - Delivery without reference

    Hi , whats the puprpose of LO and in which scenario do we use this? What are the pre and post document for LO? Thanks, Ivy