Problem in Customer hierarchy configuration

Hello All,
I would like to configure customer hierarchy for 3 levels, can any one explain me in detail step by step configuration i have to follow,
Thanks &Regards,
Sundu

Dear Sundu
Check this link
[Customer Hierarchies |http://help.sap.com/saphelp_47x200/helpdata/en/dd/55f4d9545a11d1a7020000e829fd11/frameset.htm]
thanks
G. Lakshmipathi

Similar Messages

  • Problem in Customer Hierarchy

    Hi all,
      I have a problem in creating customer hierarchy in CRM.
    According to SAP HELP:
    Before you create a CRM account hierarchy from an ERP customer hierarchy, you first have to:
    ●      Perform an initial load of the necessary Customizing settings from SAP ECC to SAP CRM.
    Use the initial load in CRM (transaction R3AS) in CRM Middleware and the Customizing object DNL_CUST_THIT.
    ●      Map the ERP customer hierarchy categories to the CRM account hierarchies.
    For more information about mapping, see in the Implementation Guide (IMG) Customer Relationship Management ® Master Data ® Business Partner ® Account Hierarchy ® Data Exchange of ERP Customer Hierarchies with SAP CRM ® Assign ERP Customer Hierarchy Type to CRM Hierarchy Category.
    My problem stuck here where in the R/3 Hierarchy Type, the F4 help value does not show any value. I checked in R3, there is a standard entry A for customer hierarchy. Could any one help me on this?
    ●      Download the ERP table KNVH (customer hierarchies) to SAP CRM.
    Use the initial load in SAP CRM (transaction R3AS) with the business object DNL_BUPA_KNVH. A copy of the ERP table KNVH is replicated to SAP CRM to create the account hierarchy from it.
    cheers,
    ginnie

    Hello Ginnie,
    Reason might be that initial download of DNL_CUST_THIT  was not complete.
    Check SM58 to see if there's an error, when the system was trying to download the hierarchy. Please go also to trx. st22 to see if there is a TIMEOUT dump related to this download. If so, you can try to increase the parameter rdisp/max_wprun_time and start again the download of the hierarchy.
    Also some of the attached OSS Note 522815 might help for more details. Check also Note 516725 it might be helpful.
    Thanks
    Raja Pamireddy
    CRM Marketing Forum Moderator

  • BW Problem Extracting Custom Hierarchy

    Hello Experts,
    I have built a completely new hierarchy of new custom master data in R3. I then have used BW07 to create a datasource to extract the hierarchy data with no problems.
    I have then created a new infoobject in BW and I have successfully loaded the master data. However when I assign the new Hierarchy datasource it shows the transfer structure with my infobject but with length 0 rather than the correct 8. 
    When I then perform a data load I get error the error "Syntax error in generated program, row 33". Looking at the code it has indeed got a data element defined with length 0.
    What am I doing wrong? Everything seems to be generated, replicated and active. Any help will be greatly appreciated. I cant find anything similar on OSS and I would have thought this was basic functionality.

    I have found the answer to this problem.
    If the data element the hierarchy datasource is based on does not have a domain BW07 will not pick up the length of the field.
    I here by award myself 2 Gold stars

  • Customer hierarchy-Discount not flowing through

    I am facing problem in customer hierarchy in pricing.
    I have assigned account group 0012 to 001 all customer. 0012 is Main company who is not issuing orders. I think this may be due to Partner determination settings. However, I have set 3 levels 1D mai n office which is not issuing sales orders act group 0012 Set partner determination at customer master level and  sales document header TA. In sales order in Partners tab I am getting 1D but not getting other like 1C nor 1B nor 1A.
    Assigned sales area as well to hiegher level sales area, order type to "A" cust. hierarchy, VDH1N well maitnined 0012 act grp to lower level 2 company which both are 001 act group.
    In VK11 maintained HI01 % discount different for head office & two branch office with same sales org, Distr Channel and division.
    Here HO is given 2% discount and one branch office 5% and another 7%
    When I am creating sales order for 7% branch, in pricing procedure it shows only 2% (HO) discount but not 7% for branch office. I have also tick marked in XD02 at billing tab price determination. In pricing analysis hirearchy 02 is having Exclaimation in Customer field. So why I am missing this customer field even though I have maintained that customer in VK11. Hope I have summarized all details. If any questions please feel free.
    I shall appreciate if you know the resolution.

    This is now resolved by proper settings in Customer Hierarchy

  • Problem Configuring a Compound Customer Hierarchy

    Hello,
    My company is trying to set up our customer hierarchy in BW.  On the R/3 side we are using 0cust_sales (or the compound of customer and sales area) as our basis for the hierarchy such that there can be 5 levels of 0cust_sales.
    We want to display this hierarchy in our Sales Overview cube which has several customer objects (Ship-To Party, Sold-To Party, etc) but no cust_sales objects.
    Does anyone have any ideas how we can pull this off?

    Sure,
    Can u send a test mail to this user id
    [email protected]...will look into ur issue.
    Thanks

  • Customer Hierarchy Partner determination in a Sales Order using Payer ?

    Dear SD Experts/Gurus
    We use Customer Hierarchies extensively in Sales Orders for Pricing & Rebates and it all works fine.
    The Hierarchy structure consists at the bottom level of a SoldTo linked to a Hierarchy Customer and many SoldTos can have the same Hierarchy Customer.
    We set price conditions at the Hierarchy Customer and that all works fine.
    We would like to change our Customer Hierarchy to link the Hierarchy Customer to the Payer rather than to all the individual SoldTos.
    This is because we have many SoldTos linked to 1 Payer and this will allow us to have simpler Customer Hierarchy structures making it easier to setup and maintain.
    I have changed the SAP configuration to do this and I can certainly maintain the Customer Hierarchy without any problem using transaction VDH1N.
    But when I create a Sales Order, the Hierarchy Customer does not get pulled through to the Sales Order Header Partners based on the Order Payer and hence no Hierarchy Customer price conditions are pulled through.
    Is what I'm trying to do possible in SAP ?
    If so please advise how this can be achieved.
    Thanks David
    Edited by: David Steele on Apr 15, 2008 1:57 PM

    Hello,
    I have a similar requirement, although we are building the hierarchies directly in CRM (as we are with BP's in general), and I am using hierarchy category 01 - PRICING.
    What I have found is that a sold-to BP must:
    1. be assigned to a hierarchy node
    2. appear TWICE (!!!) in the document part.det.procedure, once in partner function 000001 (sold to) and again in partner function 00000121 (Authorized partner: sold to).
    When the sold to customer exists in both functions within the document, I am able to determine the hierarchy node properly.
    Now, my question is, can anyone guess why the main partner (sold to) must appear twice??? or, is this an error in my customizing?
    Thank you in advance for your help, and I do hope my observation can help others find a solution.
    Regards,
    Allon
    PS in terms of customizing, I used the following:
    partner function 00000001 - sold to
    partner function 00000121 - Auth. Partner: Sold-to Party
    access for Auth. Partner: 0017 - current partner: sold to *this copies the sold to partner into this partner*
    partner function 00000076 - Hierarchy Node Partner
    access for hier.node partner: CRM_PARTNER_G Pricing hierarchy
    The last bit presupposes that the hierarchy is set up using hierarchy category '01 - pricing'.
    Message was edited by:
            Allon Riczker - Added configuration steps

  • Use of customer hierarchy in CO-PA

    I'm new in FI CO-PA modules, but I have to configure CO (cost analysis). We actually used customer hierarchy in SD fully with success but we encoutered a problem with our Customer hierarchy in KE30.
    When we try to analyse the sales by the customer hierarchy we have a message saying that the hierarchy is not unique.
    Actually we have defined the hierarchy as follow:
    first node
    customer        480000
    sales org        1040
    distr chanel    F1
    division           F1
    customer        480000
    sales org        1040
    distr chanel    F1
    division           F2
    customer        480000
    sales org        1040
    distr chanel    F1
    division           F3
    We have used this structure because we have different conditions depending of the division
    My first question is: Is it this structure that provoque the message in KE30?
    The second one is: How I must have structured the hirarchy in order to be able to have different condition on each division for the node 480000?
    Thanks for your help on that topic.

    Hi,
         The data structures of the hierarchy in SD and CO-PA are not quite the same. In SD, there is a dependency between the customer number and the sales organisation. So you can have the same customer number several times in the hierarchy. However, in CO-PA the dependency with the sales organisation does not exist.  A check is performed only on the customer
    number.
        We recommend that you create a new hierarchy in CO-PA (transaction KES3). If you use SD customer hierarchy in COPA then there will also be problems in reporting (KE30).
         Check the SAP referenced characteristics CustomerHierarchy01,CustomerHierarchy02 and CustomerHierarchy03 ? (tcode KES1).
    regards
    Waman

  • Date Dim Custom Hierarchy

    In my custom hierarchies below, we have Year --> Quarter --> Month.
    I noticed that the custom hierarchies in the Microsoft sample Adventure Works that the custom Calendar Hierarchy is Year --> Quarter --> Month --> Date (key).
    What is the impact of our custom hierarchy not going all the was down to the Date (key)?
    Ryan P. Casey • <a href="http://www.R-P-C-Group.com">www.R-P-C-Group.com</a>

    Hi Ryan,
    as Saurabh said, it's not a problem. Configure attribute relationships correctly and you can create a lot of hierarchies with various levels, such as
    Year - Date, Year - Week, Quarter - Date, Year - Month etc.
    Best regards.

  • Customer Hierarchy download in CRM7.0 Web UI

    Hi Experts
    Need your expert advice on the below issue:
    We are using customer hierarchy from ECC to SAP CRM7.0 for one of our client. I have performed the below steps to bring ECC customer hierarchy to CRM.
    SAP ECC System:
    1.Hierarchy node is created thru tcode- v-12
    2.Customer hierarchy is created thru tcode- VDH1N
    Replication steps in CRM:
    1.Replicate Customer Hierarchy Customizing thru TCode- R3AS, download object DNL_CUST_THIT .
    2.Assign ERP Customer Hier. to CRM hierarchy category in SPRO .
    3.Replicate Customer Hier thru Tcode u2013R3AS , download object DNL_BUPA_KNVH.
    4.Create account hierarchy thru Tcode- BPH_DNL , we need to create the hierarchy only for the sales area 0001,01,01.  So I have selected sales the required sales area only.
    5.I checked in web ui  and found the result for account hierarchies.
    Current Result:
    a.ECC hierarchy downloaded, however descriptions for the hierarchy nodes are missing in CRM web ui.
    b.Customer assigned to ECC hierarchy can be seen in the u201CAccount Hierarchy Detailsu201D assignment block , however I could not see the customers in u201C Assigned Accountsu201D assignment block.
    6.Expected Result :
    a.ECC hierarchy display with description in u201C Account Hierarchy Detailsu201D assignment block.
    b.Display customeru2019s information in u201C Assigned Accountsu201D assignment block.
    Can anybody support and provide the information if we are missing any configuration step ? or the result is the correct behavior of standard system ?
    I would really appreciate your help on this.
    Regards
    Satish Rikhi

    Hi Tanya
    My issue is got sovled with SAP note 1398619 .However, for the second issue there is no finding.
    I am assuming ,that is standard SAP CRM behaviour , if we assign any account in crm , that will be shown in the assignment block.
    Regards
    Satish

  • Problem in custom fields in mm02/mm03

    Hi folks,
    i want to add the custom fields in mm01.iam able to add and update database.but iam facing problem in when iam checking the particular material in mm02/mm03.the custom field data is not correctly.for every material the last custom field data is showing. in database it is updating correctly but in mm02/mm03 it is displaying incorrectly.
    By the following code i can able to display the data in mm02/mm03.but my problem is the last created custom field(model) data is showing for all the materials when iam checking in mm02/mm03.
    here my custom field is "MODEL"
    for eg matnr-10 model -xx.
    matnr-20 model-yy.
    if iam checking in mm02/mm03 for matnr-10 model-yy it is displaying.in database it is updating correctly.
    can u please tell me how can i write a code to select the custom data(model data) for that particular material.
    Module get_data.
    if sy-tcode = 'MM02'.
    select single model into mara-model from mara
    where matnr = mara-matnr.
    elseif sy-tcode = 'MM03'.
    select single model into mara-model from mara
    where matnr = mara-matnr.
    loop at screen.
    if screen-name = 'MARA-MODEL'.
    screen-input = 0.
    modify screen.
    ENDIF.
    endloop.
    endmodule.
    Thanks in advance,
    Neelu.

    Just read the OSS note mentioned earlier.
    Symptom
    You want to integrate customer-specific fields in material master maintenance.
    Other terms
    SAPLMGMM, RMDATIND, ALE, CI_MMH1, EXIT_SAPLMGMU_001
    Solution
    To add customer-specific fields to an existing material master table (such as MARA or MARC) , you can proceed as follows as of Release 3.0C:
          1. Use an append structure to add the fields to the required table in the Dictionary (this is not a modification; for details, see the SAP document "ABAP/4 Dictionary"). In Release 3.x, the length of the field names must be the same as  the standard five character fields. This is necessary because of dynamic assignments. As of Release 4.0A, the lengths of the field names can be longer than five characters. If the changes of the fields should be recorded in the change document and taken into account during ALE distribution, set the 'Change document-relevant' indicator for the corresponding data elements. For table MARA in Release 3.x, you must also enhance the database view MARU because the database changes are carried out using this view. This small modification is no longer necessary as of Release 4.0A because the database view MARU is enhanced automatically when you enhance table MARA or the include EMARA (which is the data part of table MARA).
          2. Enhancing online maintenance in customized material master maintenance:
          Define a subscreen with your customer-specific fields in a customer-specific function group created as a copy of the standard function group MGD1.
          In Customizing, assign this subscreen to a maintenance screen using the "Copy customized material master" function. For details, see the Implementation Guide (IMG). As of Release 4.0A, program COPYMGD1 is available. You can use this program to create customer-specific function groups as required. This program is also incorporated in the Customizing function 'Configure customized material master'. Ensure that each field of the subscreen has a field statement in the flow logic, otherwise the data is not transported correctly. You can use subscreen SAPLMGD1 2002 as an example.
          If you want these fields to be subject to standard field selection, you must add new entries for them to the central field table for material master maintenance (T130F):
          Application examples for standard field selection:
          The field is mandatory and is to be flagged with a "?".
          The field belongs exclusively to the purchasing user department. Purchasing data and MRP data are both contained on one screen. However, the MRP controller is not to see the purchasing data.
          The following data is required for each field:
                a) Field name        (T130F-FNAME)
                b) Field selection group (T130F-FGRUP)
                Here, you should use a standard field group if the customer field is subject to the same field selection as the standard fields of the standard field group. If it is not, use a customer-specific field group.
                You must then check and, if necessary, modify the attribute of the field group using the function "Maintain field selection for data screens" in Customizing under "Logistics Basic Data -> Material Master".
                Field groups 111 through 120 that are not used in the standard system are reserved as customer-specific field groups. As of Release 3.0F, additional customer field groups are available. (For details, see the IMG).
                c) Maintenance status (T130F-PSTAT)
                List of the user departments that may maintain the field. You can display possible values by using the input help for the maintenance status field in the Customizing activity "Configure Material Master" when maintaining logical screens.
                d) Reference        (T130F-KZREF)
                This indicator must be set if the field from the reference material should be proposed during creation with reference.
    Note: You cannot yet use Customizing to enhance table T130F; you can use only transaction SE16 (Data Browser) or transaction SM31. Future releases will include a separate Customizing function for maintaining customer-specific fields. See Note 306966. By implementing this note you can add entries to table T130F within Customizing. This type of maintenance is possible as of Release 4.5B.
    You may change the entries for standard fields only with regard to the reference data and field selection group. Changing other data for standard fields constitutes a modification. Therefore, you cannot use the Customizing function "Assign Fields to Field Groups" to change this data.
    In addition, you must not add new standard fields to table T130F.
          3. If you want to maintain customer-specific fields using data transfer by direct input or via ALE distribution, proceed as follows:
          Add the fields to central field table T130F (see above).
          Add the customer-specific fields to the data structures for the data transfer (for example, BMMH1 for the main data).
          Also, add the customer-specific fields to the tables in which the incorrect data is stored during direct input. These tables have the same name as the corresponding master data table and also have the suffix _TMP.
          For example: If you add customer-specific fields to table MARA, you should add the same fields to table MARA_TMP.
          If you use ALE, you must also add fields to the IDoc. To process enhanced IDocs, you can use enhancement MGV00001 with customer exit EXIT_SAPLMV01_002 for creating the IDocs and customer exit EXIT_SAPLMV02_002 for posting the IDocs.
          Prior to Release 3.0E, enhancing structure BMMH1 constitutes a modification. In this case, you must add the new fields tot the end of the structure before the last field (SENDE = record end indicator).
          As of Release 3.0F, structure BMMH1 contains the customer include CI_MMH1, which is part of the enhancement MGA0001. Here, you must proceed as follows:
                a) Add the customer-specific fields to include CI_MMH1.
                The names of the fields in CI_MMH1 must be identical to those of the corresponding fields in material master tables MARA, MARC and so on.
                Important: The fields must be CHAR type fields. Therefore, create CHAR type data elements whose lengths are identical to the output length of your fields in  table MARA and so on. Use these data elements in include CI_MMH1, but use the field names from table MARA and so on.
                b) Activate include CI_MMH1.
                c) If you have not used customer structure ZMMH1 before, create it as a copy of structure BMMH1 and delete the standard fields that you do not require. You are not permitted to delete field STYPE and include CI_MMH1 when doing this. If you have already used structure ZMMH1, add include CI_MMH1 to it.
                d) Activate structure ZMMH1. This also adds the customer-specific fields to ZMMH1.
    Run program RMDATING. This program generates routines which are supplied to your customer-specific fields from the input file. As of Release 4.5A, you also need to activate the routines/function modules generated by program RMDATING (especially, the MAT_MOVE_BMMH1_XXXX modules). Details about this subject (especially the procedure when using customer structure ZMMH1) are described in the IMG for transferring the material data under item 'Maintain Transfer Structure'. Also, check the declaration of structure WA in program RMMMBIMC to see whether it is declared with sufficient length. If necessary, enhance the declaration (for the time being, this still constitutes a minor modification).
    In addition, lengthen domain DI_DATA with CHAR 5000. As of Release 3.1H, this has already been done.
    Important: When using customer-specific fields, you can use only structure ZMMH1 to transfer the data. Otherwise, after the next SAP upgrade which contains new standard fields in structure BMMH1, the input files no longer match. If you want these new standard fields to be transferred, add them after your customer-specific fields (the order of the fields in structure ZMMH1 does not need to be the same as the order of the fields in BMMH1).
    If you want foreign key dependencies or fixed domain values to be checked, or another check for a customer field, this is possible up to and including Release 3.0D only by modifying the corresponding check function modules. As of Release 3.0E, you can use function exit EXIT_SAPLMGMU_001 (SAP enhancement MGA00001) for these purposes.
    If you want to use engineering change management to schedule future changes for your customer-specific fields or you want to use the 'Display at Key Date' function, execute program GENERATE in addition. This program generates the necessary assignments for interpreting the change documents. With regard to engineering change management, you must read Notes 60281, 60973, and 48962.
    To date, it is not possible to integrate customer-specific tables in material master maintenance without making a modification. However, you can create customer-specific development objects containing the essential additional logic. You can then integrate these development objects in your system as part of only a minor modification.
    Regards

  • Problem with Customer Interaction Module in Web Channel Builder

    Hello Everyone,
    Facing an issue with Web Channel Builder Customer Interaction Module.
    In Web channel builder we have done all the required configuration changes, but still we are not able to get the reviews and rating part in the product detail page.
    We have created a new application and all the other module are working fine ,but the only module that is causing problem is Customer Interaction module. Every time we are activating this module rest modules stops working.
    Can anyone please let us know what could be the root cause of this problem.
    Are  there any setting that has to be done ...that we are missing in?
    I have studied that Product Catalogue is integrated with this module. Are there any setting that are to be done in the Product Catalogue module in Web channel builder?
    Thanks in advance!
    Regards,
    PB

    Hi PB,
    Did you please get any proper error / exception in log file? Did you please check the web.xml as well that there is no same application name defined.
    Can you please also copy paste the log please.
    Thanks,
    Hamendra

  • Customer Hierarchy and Contract

    Hi Friends,
    I have a requirement - where my client has a customer who is globally located .....every year the Customer Head office gives a contract to my client and the contract is valid across his offices located globally...say one office in UK,one in US,one in Australia.....Referring to the same contracts orders have to be created for the UK ,US customer like wise.
    And every time a slaes order is created based on the order from the UK/US customers the qty has to get decreased from the same contract.
    Pl share some idea on how to go with this.
    Cheers
    Ivy

    Hi,
    As per info. given in the question,There are two levels in Customer's org as far as
    Global Head quarter of customer  is SP for Contract and it's country branches are  SH
    or
    Global Head quarter of customer  is SP for Contract and it's country branches are  SP for release order.
    [Authorized partners to release the contract|http://help.sap.com/saphelp_erp60_sp/helpdata/en/dd/55fdbb545a11d1a7020000e829fd11/content.htm]
    Depending on the scenario you can configure.
    In T-code V0V8 you need to select appropriate partner authorization rule in contract section of contract doc.type.
    You need to define partner determination procedure for contract.-In customizing  Sales-Basic function-Partner determination-set up partner determination.
    You need to maintain customer hierarchy master data.V-12
    Thanks,
    Vrajesh

  • Customer Hierarchy details in SAP ERP BP transaction

    Dear All,
    Currently we are using BP transaction in SAP ERP and also using customer hierarchy transaction VDH1N.
    Now the problem is we cannot see customer hierarchy in BP transaction, we have any option that we can create relationship in the BP transaction, however its a double effort.  Is there any option that we can see the Customer Hierarchy details in SAP ERP BP transaction?
    Regards,
    Murali

    Hello Murali,
    With BP transaction, do you mean business partners in XD03 / VD03?
    >> we cannot see customer hierarchy in BP transaction
    No, you can't see the customer hierarchy in XD03. That's correct.
    In XD03 you have sold-to, payers, bill-to and ship-to.
    You also have hierarchy nodes (012).
    In my opinion, the customer hierarchy should only have relations between hierarchy nodes and sold-to(s).
    Therefore these are different information segments => No need to see the hierarchy from the BP transaction.
    Hint: Maybe that is the reason why the functionality is not available in the standard system!

  • Allocations at customer Hierarchy level

    Hi Gurus,
    I have a requirement from client to allocate stock of restricted products at customer hierarchy level. For example: Material ABC is a restricted product and there are 500 CV available in the plant, Client would like to allocate 100 CV to customer-1, 200 CV to customer-2 and 200 CV to customer-3.
    Also Material ABC can be allocated to one of the nodes of customer hierarchy and automatically this stock should be available to all the customers with in that hierarchy to consume. If there is a chain customer like SAMS, stock is assigned to highest node of SAMS at state level and this stock should be available for all SAMS clubs with in the state to consume.
    I am using Quotations to reserve stock at customer level. The problem is with allocating stock at customer hierarchy level. Please suggest me some solutions to achieve this requirement.
    Thank You in advance,
    Samatha.
    Edited by: Samatha on Oct 11, 2011 10:04 PM

    Hi,
    That particular product and customer groups combination cvcs delete. It means that the particular combination of cvcs deleted. so there is no chance to  see the forecast.
    regards,
    sivaram2411
    Edited by: sivaram2411 on Apr 19, 2011 9:03 AM

  • Find contract (outl. agreem.) at order item level by customer hierarchy

    Hi Everyone,
    I've a requirment for the next functionality is SAP.
    <b>Find contract</b> (outl. agreem.) <b>at order item level by customer hierarchie</b>.
    Standard SAP can only use the customer hierarchy to find a contract at <u>order header level</u>. This has not the result we want, beceause all or a selected group of items will be copied to the order and this process is not usefull with EDI order input.
    Does somebody know how this functionality can be created in SAP? Build the functionality with ABAP is no problem for me.
    Thx.

    Hi !
    I know its quite late for the answer but I just saw your question.
    In the customising of the Sales doc type (VOV8), in the 'Transaction flow' section, in the first field for Outline agrmt mess. entry of either  B or D or F should help.
    Reward if helpful.
    Regards,
    PATHIK

Maybe you are looking for

  • Problem with month to month subscription of Illustrator

    Hi - I have the month to month subscription of Illustrator on my computer. Today it won't open and says I am missing certain plug-ins? Like "round corners"? How do I fix this?

  • Connecting to the DI from MS Excel

    This code snippet works fine from vb.net, however, I can't get a connection from Excel.  I added a reference to SAPbobsCOM.  Everything is fine up until I call .connect. Sub MyMacro()     Dim vCompany As SAPbobsCOM.Company     Set vCompany = New SAPb

  • Hook Up

    When I attach my ipad2 I get a pop up that says, This iPad cannot be used because the Apple Mobile Device service is not started.......  How do I start it?     

  • Questions about my MSI R5770 Hawk Radeon HD 5770 and my Dell Studio 7100

    Ok, I have had this card installed for about a year now. From the beginning Catalyst Control Center had given me error messages, "Catalyst Control Centre: Host application has stopped working. Windows is checking for solutions" every time I start the

  • Safari keeps asking giving me a pop-up box asking for a password, which it does not accept.  Help!

    I can't get the pop up box for that asks for passwords to stop popping up.  Simply trying to get on the Internet.  I tried reseating the main password using the OS X Install disc and I don't think the keychain has the same password.  Am very confused