Track Leave Request which is not processed

Hi,
When an employee applies a leave, a work item will go to his superior's ESS Inbox. After Superior approves, Absence will be updated into table PA2006.
But before it gets approved, I need to know how many Leave Requests have been applied ?
Thanks.
jey

ok, then forget what i have said about transaction ptarq
i am assuming you are using workflow template 04200009 or a copy of it? Then your request data is only stored in a workflow container until it gets approved and your infotype 2001 gets updated.
check transaction swi1 after you have submitted a leave request. You should see a workflow instance with all the required data. So until the workflow is completed, your leave request is pending.

Similar Messages

  • ESS/MSS: Approve Leave Request in UWL - not working

    Hi to all,
    we are using web dynpro ESS/ MSS (SAPESS07_12/ SAPMSS07_4) in portal NW04s for mySAP ERP2005 and are using UWL in order to approve leave requests. If employees are creating leave requests, everything works fine. After that the manager opens the leave request in UWL, the web dynpro application is openening succesfully and after some clicks he reaches the buttons to approve or reject the leave request. But by pushing one of them the following messages occures :
    <b>Workitem 000000000000 Cannot be read</b>
    After pushing the button again, another message comes up:
    <b>No Customizing for status typ ARQ, Status approved...</b>
    By the way, the same errors also come up when the employee wants to delete his leave request which is not approved.
    Any ideas, what can be the reason?
    Regards,
    Frank

    Hi Ashutosh,
    I have found the reason. The user <b>WF - Batch</b> in sap erp, which is using the RFC Destination for workflow, was locked. Well, it is a a little bit strange for a cummunication user that he becomes locked. Unlocked him, now all works.
    Thanks for your support.
    Regards,
    Frank

  • Deletion of Request which are not updated to data target

    hi,
    I want to all PSA data whether it is updated or not In our project this is being done by Using a Process chain, But it is not deleting the request which are not updated to any data target or failed, I have selected both the check boxes
    Only successfully booked requests
    Only requests with errors, not updated in any data target
    but even after selecting this check box it is not deleting the failed request, can any one tell me why it is so.
    Any help in this would be highly appreciated.

    Try to do it without checking any of the checkboxes...
    Regards,
    Luis

  • ESS Leave Request Workflow 12300111 not being triggered

    Hi Experts,
    I am implementing ESS 1.0for ERP05. The Leave Request (EP) is not trigerring the standard wokflow 12300111.
    I performed the following steps:
    1. Configured inbackend SPRO: Processing process for types of Leave to point to 12300111
    2. Changed the taskes under WF12300111 to General Tasks and activated the WF
    On submitting the Leave Request (EP), the table PTREQ_HEADER gets updated but theWorflow is still not triggered.
    Can someone please help.
    Thanks,
    Shobhit

    Hello Shobhit,
    could you solve it ?

  • HT4995 i lost my iphone 4 last night and its not reachable assuming someone took out the sim.. so can i or my network company track the iphone which is not reachable through assuming location services and find my phone apps are enabled?

    i lost my iphone 4 last night and its not reachable assuming someone took out the sim.. so can i or my network company track the iphone which is not reachable through assuming location services and find my phone apps are enabled?

    No. Find My Phone is the only way to locate any lost iPhone. However, this requires that Find My Phone be turned on/activated before the phone was lost, and the phone must have an Internet connection. If your phone is turned off, does not have an Internet connection, or has been restored, there is no way to locate it.

  • Leave request Workflow  WS12300111 not working

    Hello All,
    We have ESS/MSS portal and ECC6.0. I have started with pilot ESS leave request project
    When i create the leave request from ESS, i am getting message '  The leave request has been sent.'
    Evne i am able to the see the task in UWL(MSS) in tracking tab. But if log in as a manager to approve the leave request, its not displaying the task. I have checked the workflow, its getting stuck. Then i have checked leave process(test application) in R/3 alone in transaction PTARQ. I have given my person number and mode 'R'. Its throwing error message " No document created : HRTIM_ABS_REQ 124 conflict with absences/relocation (IT2001/0330)
    But i have customized workflow properly in 1. SWU3 ; all are green except guided procedures
                                                                          2. Maintained the WS12300111 in workflow template for all
                                                                          3. Request have to approved
                                                                          4. task is generated
                                                                          5. line manager as agent (OM maintained properly)
    Kindly help .
    Regards,
    Venkat

    Hi ,
    I have changed the pernr ,date and working fine now.Moreover task is  also general. But the workflow started but stuck in the step 'Approvel Process.
    Its stops at Node number 38 . I have checeked the step history :
    Green  (Sub)workflow created
    Green  Background Processing Started
    Green Execution started
    Green Error Message Created for Admin
    Red    Exception occurred  Error handling for work item 000000390153
    I just want to execute the leave request workflow  from PTARQ, keeping as me as requestor and approver. If its success , i want to test with ESS. But now its stuck in R/3 test itself. Please help.
    Regards,
    Venkat

  • ESS Leave Request in UWL not launching

    Hello,
    We are trying to configure ESS\MSS, and currently stuck at the step of Leave Request\UWL configuration. 
    u2022     We have configured UWL with the backend system (WebFlow Connector).  We can register the system successfully.
    u2022     In IMG, we have set the u201CProcess Request Using Workflow: u201C: 12300111
    Once a user fills out a leave request, We see the following in the UWL ([SEE IMAGE|http://www11.speedyshare.com/files/21590441/download/LeaveRequest.jpg])?  We do not see any option to launch WebDynpro? And why does the item text states u201CGeneral Workflow for Documentsu201D instead of u201CLeave Requestu201D?
    Thanks,
    Rob

    Hello,
    I donu2019t see any items in the Tasks tab, the way Iu2019m testing is on the u201CTracking" Tab of the person that have made the Leave Request.  When I click on the item in UWL, it does not open up any Web Dynpro.  I've checked the Tasks in TCode SWFVISU, and WDynpro Java is defined.
    Below is a part of my UWL definition file:
    =================================================================
    <ItemType name="uwl.task.webflow.TS12300116.SBX" connector="WebFlowConnector" defaultView="DefaultView" defaultAction="launchWebDynPro" executionMode="default">
          <ItemTypeCriteria systemId="SBX" externalType="TS12300116" connector="WebFlowConnector"/>
          <Actions>
            <Action name="launchWebDynPro" groupAction="" handler="SAPWebDynproLauncher" returnToDetailViewAllowed="yes" launchInNewWindow="yes" launchNewWindowFeatures="resizable=yes,scrollbars=yes,status=yes,toolbar=no,menubar=no,location=no,directories=no">
              <Properties>
                <Property name="WebDynproApplication" value="LeaveRequest"/>
                <Property name="WebDynproDeployableObject" value="com.sap/ess~lea"/>
                <Property name="newWindowFeatures" value="resizable=yes,scrollbars=yes,status=yes,toolbar=no,menubar=no,location=no,directories=no"/>
                <Property name="DynamicParameter" value="wi_id=${item.externalId}"/>
                <Property name="openInNewWindow" value="yes"/>
                <Property name="display_order_priority" value="5"/>
              </Properties>
              <Descriptions default=""/>
            </Action>
          </Actions>
        </ItemType>
    =========================================================================
    Thanks,
    Rob

  • Fiori leave request error "Could not start the app due to an internal error"

    Hi,
    I'm getting this error "Could not start the app due to an internal error" when accessing leave request application.
    I don't get this error when I login and launch the app for the first time. when I go back to the home screen and select "My Leave Requests" app again, I get this error.
    If I close the error message and do a browser refresh, everything is fine again for the first time, if I access the LR app again- same error .
    Other apps are working fine.
    I don't see any error in gateway or App logs.
    below is the Request URI
    /sap/opu/odata/UI2/INTEROP/ResolveLink?linkId=%27LeaveRequest-createLeaveRequest%27&shellType=%27FLP%27&formFactor=%27desktop%27
    Service call info
    Anyone with similar issue? any SAP notes?
    we are on
    UI2_731        100    0009    SAPK-10009INUI2731        SAP UI2 IMPL. FOR NW 7.31
    UI2_FND        100    0009    SAPK-10009INUI2FND        SAP UI2 FOUNDATION
    UI2_SRVC    100    0009    SAPK-10009INUI2SRVC        SAP UI INTEGRATION SERVICES
    UI5_731        100    0009    SAPK-10009INUI5731        SAP UI5 TEAM PROVIDER ON 731
    UISAPUI5    100    0009    SAPK-10009INUISAPUI5    SAP UI5
    UI_INFRA    100    0009    SAPK-10009INUIINFRA        SAP UI INTEGRATION INFRASTRUCTURE
    UIX01HCM    100    0003    SAPK-10003INUIX01HCM    UI for HCM Application
    Tags edited by: Michael Appleby

    Hi Masa,
    We have required SAP notes now, we are on version 1.22.5.
    It is still the same, working the first time I access the App, but subsequent access wont work until i refresh browser.
    I've include the response and lpd/tile screens.
    Thanks,
    Phani

  • In ESS-Leave Request -A critical error has occured.

    In ESS when tried to enter the Leave which is under Leave request the below error occured:
    Critical Error
    A critical error has occured. Processing of the service had to be terminated. Unsaved data has been lost.
    Please contact your system administrator.
    CREATE OBJECT: The class  was not found., error key: RFC_ERROR_SYSTEM_FAILURE  
    com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: CREATE OBJECT: The class  was not found., error key: RFC_ERROR_SYSTEM_FAILURE
         at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
         at com.sap.xss.hr.lea.blockcale.FcBlockCale.getBcData(FcBlockCale.java:232)
         at com.sap.xss.hr.lea.blockcale.wdp.InternalFcBlockCale.getBcData(InternalFcBlockCale.java:250)
         at com.sap.xss.hr.lea.blockcale.FcBlockCaleInterface.getBcData(FcBlockCaleInterface.java:135)
         at com.sap.xss.hr.lea.blockcale.wdp.InternalFcBlockCaleInterface.getBcData(InternalFcBlockCaleInterface.java:224)
         at com.sap.xss.hr.lea.blockcale.wdp.InternalFcBlockCaleInterface$External.getBcData(InternalFcBlockCaleInterface.java:276)
         at com.sap.xss.hr.lea.blockcale.VcBlockCale.onInit(VcBlockCale.java:261)
         at com.sap.xss.hr.lea.blockcale.wdp.InternalVcBlockCale.onInit(InternalVcBlockCale.java:275)
         at com.sap.xss.hr.lea.blockcale.VcBlockCaleInterface.onInit(VcBlockCaleInterface.java:163)
         at com.sap.xss.hr.lea.blockcale.wdp.InternalVcBlockCaleInterface.onInit(InternalVcBlockCaleInterface.java:144)
         at com.sap.xss.hr.lea.blockcale.wdp.InternalVcBlockCaleInterface$External.onInit(InternalVcBlockCaleInterface.java:220)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:196)
         at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:756)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:291)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:733)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:668)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)
         at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
         at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:860)
         at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220)
         at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1246)
         at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:354)
         at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:547)
         at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:591)
         at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:822)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:684)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(AccessController.java:219)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sap.aii.proxy.framework.core.BaseProxyException: CREATE OBJECT: The class  was not found., error key: RFC_ERROR_SYSTEM_FAILURE
         at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
         at com.sap.xss.hr.lea.model.LeaveRequestAdaptiveModel.pt_Arq_Eecale_Get(LeaveRequestAdaptiveModel.java:434)
         at com.sap.xss.hr.lea.model.Pt_Arq_Eecale_Get_Input.doExecute(Pt_Arq_Eecale_Get_Input.java:137)
         at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)
         ... 60 more

    I found out the solution and solved this issue.
    Deleted the leave request which was created with error i.e: from the custom table zxx_vacr noted down the id initiater ( which had error) and in the Test Environment for Leave request (PTARQ) gave the PERNR and deleted the documents ( gave the id iniater in the document status ).
    To check the error work flow go to SWIA and check for that Workflow (Leave) raised by the PERNR at that duration ( check in IT2001 for the duration) and give it here.
    After deleting it check in the portal for the leave request.

  • ESS leave request

    Dear friends
    in ESS leave request workflow , in approval process task i am maintaining 10 days deadline , after that by using process control i am making the workitem to be obselete , then same leave request is going to supervisor's supervisor . this is properly working, my problems are
    when the first supervisor opens some other leave request still the escalated leave request is showning in the table , still system is allow him approve . and also in the supervisor's supervisor  inbox then workitem remains if he opens the workitem there is no any leave for approval in that table , so deadline mointerting is not working propely for ess leave request , and also in supervisor's supervisor  inbox workitem is not going out from uwl .
    how to do deadline mointering for ESS leave request workflow ,
    can any one help on this
    reason which i could identify is details are picking from the document database based on the approver .

    You should check the forum, I think I saw a thread in the last two days which stated that deadline monitoring is not working for the leave request. (it could be the HCM forum). So this would be why the handling is not working as expected.
    The problem of no leave to be approved for the manager could be prevented if you set a terminating event on the task which will be triggered when the leave is approved.
    Regards,
    Martin

  • ESS - Leave Request - Workflow

    Our requirement was for the leave request process to be a simple approval process that only includes the option for the employee to u2018changeu2019 or u2018deleteu2019 a request if the manager hasnu2019t approved it yet.
    In line with this, we have configured to switched off the u2018changeu2019 and u2018deleteu2019 buttons.
    This still allows the u2018changeu2019 and u2018deleteu2019 buttons before a leave request has been approved. (which we wanted)
    And these buttons disappear once the leave request has been approved. (which we wanted)
    However, for leave requests that have been rejected, we still get these buttons. (which we donu2019t want)
    After a Leave Request has been Approved or Rejected by the manager, the "Approve another Absence" link on results page doesn't work. Can we do anything about this?
    Also, when a manager is rejecting a leave request he is not forced to enter a rejection reason.Is there a way we can force the manager to enter a rejection reason?
    Thanks
    WB

    Hi
    No your right, you shouldn't transport from IDES to DEV, What kind of development system do you have ?
    A quick way to check if it exist is to check the HR Tables e.g. HRS1205.
    And just to cover the security issue, verify that your not using structural authorization, ar at least that your having full access to the PD Object in question. You can check this in OOSB - If your not using structural authorization you will only have one entry in here - SAP* with full access. If this user is missing in this transaction, or if your user is in the table with less authorization, you wont have access to the workflow templates
    Regards
    Morten Nielsen

  • Problem with ESS Leave Request Workflow

    We had configured ESS Leave request, which is working fine with Leave request approval.
    1)     Cancellation of Leave Request using the workflow WS12400005.  
                                  Workflow is not getting triggered when we try to delete the leave request.
    2)     Quota Overview
    While displaying the Casual Leaves (CL) I need to deduct the Paternity leaves (PL) also.
         Remaining CLu2019s = quota CLu2019s u2013 ( used CLu2019s + used PLu2019s).

    hi kishore. how did you resolve the issue of workflow not being triggered?

  • Create Z service for leave request

    Hi All,
    with reference to "ESS in MSS"
    Leave request :
    "In a similar fashion you can create a Z service for leave request and attach the resource of Leave request which is standard one to it
    EMPLOYEE_WORKTIME_LEAVEREQUEST05 to the Sub Area MSS_HCM_SUB_RELATEDACTIVITY_ESS. "
    how do i create a z service for leave request?
    Regards

    I think you wish to use ESS Leave Request in MSS.......
    Tcode SPRO...
    Cross-Application Components -> Homepage Framework -> Services
    Define Services
    Copy existing and create your own....
    EMPLOYEE_WORKTIME_LEAVEREQUEST
    to
    ZXXX_EMPLOYEE_WORKTIME_LEAVEREQUEST
    EMPLOYEE_WORKTIME_LEAVEOVERVIEW
    to
    ZXXX_EMPLOYEE_WORKTIME_LEAVEOVERVIEW
    Associate a Z resource or existing resource with it....
    Then map this Z service with Sub area
    "Assign Services to Subareas"
    Do not forget to give "Position"
    Revert back if you face any issue......
    Edited by: Saurabh Agarwal on Jul 20, 2011 12:32 PM

  • Changing of iBase in Change Requests and Corrections being processed

    Good day!
    After going SP18 with Solution Manager our iBase component system has gone "mad": number for productive ERP-system has changed several times.
    Because of this change, a number of already approved change requests and corrections in processing can't be modified correctly. I can't change their status by regular operations from system document. Multiple correction/ change request change also won't work. And I can't change the iBase component in this documents, because the field is read only.
    How can I close all Change Requests and corrections with old iBase component number?
    Is there a way to change the iBase number in already approved Change Requests and Corrections, so i can perform operations with this system documents.

    Hello Raguraman!
    Thank you for your answer.
    Anyway I implemented the note to which you refer, and still can't change iBase component in corrections and change requests which are in process. The "iBase/Component" field is still read only and contains components which do not exist anymore.
    Do you know how can I change this values?

  • ESS: Leave Request - How to use a custom Leave Workflow?

    Hi Experts,
    I am implementing ESS 1.0 for mySAP ERP05. I have a custom workflow for Leave Request which I want to use for the ESS Leave Request. Can someone tell me what are the configuration steps required for this?
    I have already performed the following activity:
    SPRO --> Personnel Information --> ESS --> Service Specific Settings --> Working Time --> Leave Request --> Specify Processing Processes for Types of Leave
    Here I have defined the WF ID of New Request as the custom Workflow ID.
    Now when I trigger the Leave Request from EP-ESS, the message comes that the request was sent successfully.
    But in the backend no workflow gets triggered. I even tried to write an implementation for the BADI PT_ABS_REQ to trigger the custom workflow event, but still no activity in the ECC workflow upon submitting thwe portal request.
    Can some one please advise.
    Thanks,
    Shobhit

    Ohh.. So the standard WF also doesnt get triggered??
    Are you sure u have done SWU3 config??
    If u have, Try using SWU_OBUF to refersh the workflow buffer.
    Try swi1 to check what is happening with ur WF.
    Try login to requesters login ... SBWP ... check the outbox. Is there a WF with Error here.
    Cheers!!
    Ashutosh

Maybe you are looking for

  • Windows PC not recognising iPod Touch / ipad

    Recently I've run into this intermittent problem. Sometimes when I connect my iPod or iPad to my PC Windows simply fails to recognise that my devices are connected. To the point where the iPod won't charge because the connection is not there. There a

  • PC Laptops connect to Airport but not Internet

    I've got a DSL connection coming into my Airport Extreme Base Station (AEBS). I have my MacBook connected through Wi-Fi and a XP PC connected through Ethernet. Both can connect fine to internet and AEBS. However, when I try and connect my work laptop

  • Outlook 2007 now requires administrator password to open

    I have been using office 2007 since 2007 and this has never occurred. Now when I open Outlook, as a Standard User it asks for my Administrator Password. When I am logged on to my other account which has Administrator privileges and a password, Outloo

  • Tables for Catalog details...

    Hi, I'm new to CCM. Can any one let me know the details of the tables or reports where I can find the following details: 1. Catalogue Number 2. Date on which catalogue was created 3. Who had created the catalog. 4 Whether any changes were done for th

  • Sound distortion - Pavilion DV6-3040sa

    Hi,  When i was at university, i had to connect my laptop via ethernet to gain internet access as there was no wi-fi connection in student halls. The sound distortion was quite bad. I couldn't even listen to music or watch video's as the sound would