Supporting activities

hi
  would u plz send about supporting daily activities,monthend activities&yearend activities (fico supporting).
how many members will be there .what is help desk,schedule manager & solution manager.what is his role.what is his work.what is ticket flow.
thanks &regards
nagesh

*SAP BO reports on SAP BI:*
As we are creating OLAP cubes/Infocubes in SAP BI, same way BO has Universe.
Universe is based on direct Infocube/ Multiprovider/DSO(ods) and BEx query.
Universe Designer:
Only thing is one has to establish connection to access SAP BI system. To do this job, while choosing datasource, you have to select SAP Business Intelligence 3.x -- Client. And next screens it will prompt for User logon credentials to access SAP BI system. Once, connection is tested OK. Click next and it will list out all the OLAP Cubes available in SAP BI system and select the relavant one and click on next - next -- Finish.
Now you have created Universe on top of SAP BI system. Then Export the Universe to Server.
Open Infoview to start Web Intelligence report(s) and choose the Universe from the list of universes then it will take you to WebI Query panel , in that drag the Objects(Dimension/Detail/Measure) to result objects pane to see them in BO Report and to filter data use Query filters pane or do it in Report level.
Once you are in WebI report level , you will get lots of options to see your reports in different styles.
For better customizations: Use BEx queries based on Infocube. (In BEx query properties, one has to Check Allow OLAP access enabled)
BODI -->> BODS
After SAP aquiring BO and the latest version released with BODS(Data Services), It's basically ETL process, do the job same as what we exactly do to create Infocube. (Extraction of data , transformations and loading) and with additional transformations introduced.
Thank You!!

Similar Messages

  • Portal Support Activities

    Dears,
    I am Basis Consultant and planning to learn portal Administration.
    So I want to know what are daliy portal Support activities from admin prospective.
    Please suggest.
    Deepak

    It depends on portal to portal.
    I can tell you some importan activities
    1) Transport activities like pcd content transport, KM transport, System Config transport, transport of par, ear files... ..
    2) user Administration activities like creating users/groups and assigning these to roles etc...
    3) Integration with SAP Applications like R3, BW etc....
    4) checking proper permissions in pcd content and KM content if exists
    5) Portal mointoring activities like checking the logs in NWA, you can also use portal activity report iviews for monitoring.
    Go for EP100, EP200 trainining which is useful for portal system administration.
    Raghu

  • ABAP Production Support Activities

    Hi All,
    can someone post me any checklist related to ABAP support? or else can draft the activites involved in ABAP support?
    Thanks for your time.
    Regards,
    Chandrasekhar.
    Edited by: Venkat Chandrasekhar Nalla on May 21, 2008 9:31 AM

    Hi,
    support Activities,
    1. Handling tickets
    system and customer Generated ticktes
    2. Monitoring Process Chains
    3. Enhancements
    4. Checking System Performance
    5. Performance tuning Activites
    1. creating aggregates
    2. Compression
    3. Indexes
    and so on
    Check this threads for more info..
    support issues
    tickets in production
    Regards,
    Raj.

  • Daily activities of a support consultant

    Hello Masters,
    What would be the daily activities of a support consultant?
    I am bound to give points
    Thanks and Best wishes,
    I-BI

    HI
    These are the Daily Support processes & related links,
    ***From SDN
    Normally the production support activities include
    Scheduling
    R/3 Job Monitoring
    B/W Job Monitoring
    Taking corrective action for failed data loads.
    Working on some tickets with small changes in reports or in AWB objects.
    The activities in a typical Production Support would be as follows:
    1. Data Loading - could be using process chains or manual loads.
    2. Resolving urgent user issues - helpline activities
    3. Modifying BW reports as per the need of the user.
    4. Creating aggregates in Prod system
    5. Regression testing when version/patch upgrade is done.
    6. Creating adhoc hierarchies.
    Also refer these posts:
    Re: In production Support , how i can acquire the knowledge
    Re: How to resolve tickets  its urgent
    Re: production support issues
    production support
    we can perform the daily activitiesin Production
    1. monitoring Dataload failures thru RSMO
    2. Monitoring Process Chains Daily/weekly/monthly
    3. Perform Change run Hirerachy
    4. Check Aggr's Rollup
    To add to the above
    1) check data targets are ready for reporting,
    2) No failed or cancelled jobs in sm37 monitors and Bw Monitor.
    3) All requests are loaded for day, monthly and yearly also.
    4) Also to note down time taken for loading of critical infocubes which are used for reporting
    5) Is there any break in any schedules from your process chains.
    It's totally a client specific tool.
    The common features here can be
    A ticket Id,
    Priority,
    Consultant ID/Name,
    User ID/Name,
    Date of Post,
    Resolving Time etc.
    There ideally is also a knowledge repository to search for a similar problem and solutions given if it had occurred earlier.
    You can also have training manuals (with screen shots) for simple transactions like viewing a query, saving a workbook etc so that such queried can be addressed by using them.
    When the problem is logged on to you as a consultant, you need to analyse the problem, check if you have a similar problem occurred earlier and use ready solutions, find out the exact server on which this has occured etc.
    You have to solve the problem (assuming you will have access to the dev system) and post the solution and ask the user to test after the preliminary testing from your side.
    Get it transported to production once tested and posts it as closed i.e. the ticket has to be closed.
    ---If there is a dataload failure, what steps/checks do i need to follow. Etc.
    it means thats depends upon the failure we need to monitor and take corrective action ..
    generally we do in load failures...
    ST22 for any shortdumps
    sm21 for log entries and
    TRF entries
    sm12 for any locks
    we need to analyze from these t-codes.
    Changing query/object
    -change ticket from open to working.
    -get additional details if any required.
    -create transport request in dev.
    -make the change and save in transport.
    -check that transport goes through OK.
    -do testing in QA system.
    -after testing is OK,get change transported to prod.
    -update ticket and resolve it.
    -usually helpdesk closes ticket after confirmation with user who raised ticket.
    data load failure
    -regularly check rsmo(monitor) for data load failures.
    -if load fails,get details from details tab of monitor.
    -usual errors are:master data missing,special characters in data,datasource not replicated,delta load issues etc.
    -get root cause of error,and fix data load manually.
    -check that manually updated data is GREEN and available for reporting in data target.
    -update ticket and resolve it.

  • Cutover Activities for Upgrade Project

    Experts
    What are the cutover support activities for the administration of the ECC 6.0 (SAP) upgrade project. Also please do let me know how to prepare cutover strategy , and how do we develp cutover plans.
    Regards,
    Mahesh

    Hi,
    Check this thread.
    CutOver activities in BI7.0 while doing  production upgrade BI7.0 FromBW3.x
    Regards.

  • XI Support Material Required

    Hi,
    Can anyone provide me with documents related to xi support activities explaining error handling steps in detail?

    Hi,
    Support activity and error handling depends upon the object which are developed in ur project.
    U might face any of the following problems and find their resolution as well.
    Refer the below link for more information:
    Some errors in an XI production environment
    /people/prashanth.azharuddin/blog/2006/11/24/some-errors-in-an-xi-production-environment
    XI Error - Unable to convert the sender service to an ALE logical system
    /people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
    File to Idoc error
    Unable to convert the sender service to an ALE logical system... Urgent..!!
    SLD:
    How To…Handle the SLD for SAP XI
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9e76e511-0d01-0010-5c9d-9f768d644808
    How To…Handle Caches in SAP XI 3.0
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/1a69ea11-0d01-0010-fa80-b47a79301290
    Unable to open Integration Builder…checklist
    https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1688 [original link is broken] [original link is broken] [original link is broken]
    XI: Timeouts, timeouts, timeouts....
    /people/michal.krawczyk2/blog/2006/06/08/xi-timeouts-timeouts-timeouts
    Display button grey up
    /people/michal.krawczyk2/blog/2005/05/25/xi-how-to-add-authorizations-to-repository-objects
    ICM_HTTP_TIMEOUT
    /people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
    Refer the XI troubleshooting guide this will help you.
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/bd5950ff-0701-0010-a5bc-86d45fd52283
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/108ba391-e826-2a10-608f-c1769c51dc29
    Cache:
    /people/sravya.talanki2/blog/2005/12/02/sxicache--ripped-off
    For support activity:
    Refer the XI troubleshooting guide this will help you.
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/bd5950ff-0701-0010-a5bc-86d45fd52283
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/108ba391-e826-2a10-608f-c1769c51dc29
    SLD guide:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/652b1f46-0a01-0010-25ae-e7cb07b55414
    HTTP error debugging:
    /people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi
    Troubleshooting File-to-IDOC Scenario in XI.
    /people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
    troubleshooting SOAP:
    /people/varadharajan.krishnasamy/blog/2007/01/09/troubleshooting-soap-message--xi
    Proxy:
    Debugging Inbound Proxy:
    /people/stefan.grube/blog/2006/07/28/xi-debug-your-inbound-abap-proxy-implementation
    SPROXY not working:
    /people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
    Thnx
    Chirag

  • Issues in production support

    hi,
    can any one  send me documents related to Production support issues and how to fix them.
    you can mail me at [email protected]
    thanks,
    ram.

    Hi,
    Normally the production support activities include
    Scheduling
    R/3 Job Monitoring
    B/W Job Monitoring
    Taking corrective action for failed data loads.
    Working on some tickets with small changes in reports or in AWB objects.
    The activities in a typical Production Support would be as follows:
    1. Data Loading - could be using process chains or manual loads.
    2. Resolving urgent user issues - helpline activities
    3. Modifying BW reports as per the need of the user.
    4. Creating aggregates in Prod system
    5. Regression testing when version/patch upgrade is done.
    6. Creating adhoc hierarchies.
    Also refer these posts:
    Re: In production Support , how i can acquire the knowledge
    Re: How to resolve tickets  its urgent
    Re: production support issues
    production support
    frequent load failures during extractions and how to analyse them?
    If these failures are related to Data, there might be data inconsistency in source system. Though we are handling properly in transfer rules. We can monitor these issues in T-code -> RSMO and PSA (failed records) and update.
    If we are talking about whole extraction process, there might be issues of work process scheduling and IDoc transfer to target system from source system. These issues can be re-initiated by canceling that specific data load and ( usually by changing Request color from Yellow - > Red in RSMO). and restart the extraction.
    As to frequent failures and errors , there is no fixed reason for the load to be fail , if you want it for the interview perspective I would answer it in this way.
    a) Loads can be failed due to the invalid characters
    b) Can be because of the deadlock in the system
    c) Can be because of previous load failure , if the load is dependant on other loads
    d) Can be because of erroneous records
    e) Can be because of RFC connections
    These are some of the reasons for the load failures.
    ****Assign Points If Helpful****
    Thanks,
    Amith

  • Main Tcodes used in Production support

    Hi Gurus,
         Can anyone give me the "main Tcodes" we use during different production support activities.
         I recently got job as a BW support consultant and am bit worried about what kind of work I will be alloted? and how to do it ?
         If any body has got real-time production support experience please guide me how should I get prepared before I join the company and give me an overview of what kind of work I am gonna do in prod supp.
    Cheers,
    Noodles
    PS: point will be awarded generously

    RSA1 - Administrator Workbench
    RSPC - Proess chain maintenance
    RSPCM -  Process chain Maintenance
    DB6COCKPIT- DiagnosticsL Single System Check
    SM37 - Job overview
    SM66 - Global Work process overview
    ST22 - Short dumps
    SM51 - System wide work process overview
    SM50 - Process overview
    DB02 - Spave: History - Overview
    SE38 - ABAP Editor
    RSA3 - Extract Checker
    RSA7 - Delta Queue
    SMQ1 - Outbound Queue
    SMQ2 - Inbound Queue
    RSA6 - Postprocess DataSources and Hierarchy
    RSMO - Monitor all loads
    Also, see the following link....you will get T-Codes which you want.
    Transaction Codes for BW Developers
    Message was edited by:
            SAI KONKA

  • BW SUPPORT  RELATED QUESTIONS

    Dear All,
    I am a BW fresher and currently attending an interview for BW support role.
    Could anyone please send me some interview questions mainly focusing on BW SUPPORT related issues??
    Thanking you
    RAO

    HI Rao,
    These are the Daily Support processes & related links,
    ***From SDN
    Normally the production support activities include
    Scheduling
    R/3 Job Monitoring
    B/W Job Monitoring
    Taking corrective action for failed data loads.
    Working on some tickets with small changes in reports or in AWB objects.
    The activities in a typical Production Support would be as follows:
    1. Data Loading - could be using process chains or manual loads.
    2. Resolving urgent user issues - helpline activities
    3. Modifying BW reports as per the need of the user.
    4. Creating aggregates in Prod system
    5. Regression testing when version/patch upgrade is done.
    6. Creating adhoc hierarchies.
    Also refer these posts:
    Re: In production Support , how i can acquire the knowledge
    Re: How to resolve tickets  its urgent
    Re: production support issues
    production support
    we can perform the daily activitiesin Production
    1. monitoring Dataload failures thru RSMO
    2. Monitoring Process Chains Daily/weekly/monthly
    3. Perform Change run Hirerachy
    4. Check Aggr's Rollup
    To add to the above
    1)check data targets are ready for reporting,
    2) No failed or cancelled jobs in sm37 monitors and Bw Monitor.
    3) All requests are loaded for day,monthly and yearly also.
    4) Also to note down time taken for loading of critical infocubes which are used for reporting.
    5) Is there any break in any schedules from your process chains.
    It's totally a client specific tool.
    The common features here can be
    A ticket Id,
    Priority,
    Consultant ID/Name,
    User ID/Name,
    Date of Post,
    Resolving Time etc.
    There ideally is also a knowledge repositary to search for a similar problem and solutions given if it had occured earlier.
    You can also have traning manuals (with screen shots) for simple transactions like viewing a query, saving a workbook etc so that such queried can be addressed by using them.
    When the problem is logged on to you as a consultant, you need to analyse the problem, check if you have a smilar problm occured earlier and use ready solutions, find out the exact server on which this has occured etc.
    you have to solve the problem(assuming you will have access to the dev sytem) and post the solution and ask the user to test after the preliminary testing from your side.
    Get it transported to production once tested and post it as closed i.e the ticket has to be closed.
    ---If there is a dataload failure, what steps/checks do i need to follow. etc.
    it means thats depends upon the failure we need to monitor and take corrective action ..
    generally we do in load failures...
    ST22 for any shortdumps
    sm21 for log entries and
    TRF entries
    sm12 for any locks
    we need to analyze from these t-codes.
    changing query/object
    -change ticket from open to working.
    -get additional details if any required.
    -create transport request in dev.
    -make the change and save in transport.
    -check that transport goes through OK.
    -do testing in QA system.
    -after testing is OK,get change transported to prod.
    -update ticket and resolve it.
    -usually helpdesk closes ticket after confirmation with user who raised ticket.
    data load failure
    -regularly check rsmo(monitor) for data load failures.
    -if load fails,get details from details tab of monitor.
    -usual errors are:master data missing,special characters in data,datasource not replicated,delta load issues etc.
    -get root cause of error,and fix data load manually.
    -check that manually updated data is GREEN and available for reporting in data target.
    -update ticket and resolve it.
    Siggi's weblogs for data load error and how to restart process chain
    /people/siegfried.szameitat/blog/2005/07/28/data-load-errors--basic-checks
    /people/siegfried.szameitat/blog/2006/02/26/restarting-processchains
    1. Why there is frequent load failures during extractions? and how to analyse them?
    If these failures are related to Data, there might be data inconsistency in source system. Though we are handling properly in transfer rules. We can monitor these issues in T-code -> RSMO and PSA (failed records) and update.
    If we are talking about whole extraction process, there might be issues of work process scheduling and IDoc transfer to target system from source system. These issues can be re-initiated by canceling that specific data load and ( usually by changing Request color from Yellow - > Red in RSMO). and restart the extraction.
    2. Explain briefly about 0record modes in ODS?
    ORECORDMODE is SAP Delivered object and will be added to ODS object while activating. Using this ODS will be updated during DELTA loads.. This has three possible values ( X D R).. D & R is for deleting and removing records and X is for skipping records during delta load.
    3. What is reconciliation in bw? What the procedure to do reconciliation?
    Reconcilation is the process of comparing the data after it is transferred to the BW system with the source system. The procedure to do reconcilation is either you can check the data from the SE16 if the data is coming from a particular table only or if the datasource is any std datasource then the data is coming from the many tables in that scenario what I used to do ask the R/3 consultant to report on that particular selections and used to get the data in the excel sheet and then used to reconcile with the data in BW . If you are familiar with the reports of R/3 then you are good to go meaning you need not be dependant on the R/3 consultant ( its better to know which reports to run to check the data ).
    4. What is the daily task we do in production support.How many times we will extract the data at what times.
    It depends... Data load timings are in the range of 30 mins to 8 hrs. This time is depends in number of records and kind of transfer rules you have provided. If transfer rules have some kind of round about transfer rules and updates rules has calculations for customized key figures... long times are expected..
    Usually You need to work on RSMO and see what records are failing.. and update from PSA.
    5. What are some of the frequent failures and errors?
    As the frequent failures and errors , there is no fixed reason for the load to be fail , if you want it for the interview perspective I would answer it in this way.
    a) Loads can be failed due to the invalid characters
    b) Can be because of the deadlock in the system
    c) Can be becuase of previuos load failure , if the load is dependant on other loads
    d) Can be because of erreneous records
    e) Can be because of RFC connections
    These are some of the reasons for the load failures.
    suresh

  • Support project  (more details)

    Hi Guys,
       I am fresher in BW, I have client round in support project 
      What type off question they will ask, I need more details about tickets,
       How many types off ticket? Anybody Immediately I need answer me
    Regards
    Ravi

    Hi Ravi,
    Normally the production support activities include
    Scheduling
    R/3 Job Monitoring
    B/W Job Monitoring
    Taking corrective action for failed data loads.
    Working on some tickets with small changes in reports or in AWB objects.
    The activities in a typical Production Support would be as follows:
    1. Data Loading - could be using process chains or manual loads.
    2. Resolving urgent user issues - helpline activities
    3. Modifying BW reports as per the need of the user.
    4. Creating aggregates in Prod system
    5. Regression testing when version/patch upgrade is done.
    6. Creating adhoc hierarchies.
    Also refer these posts:
    Re: In production Support , how i can acquire the knowledge
    Re: How to resolve tickets  its urgent
    Re: production support issues
    production support
    we can perform the daily activities in Production
    1. Monitoring Data load failures thru RSMO
    2. Monitoring Process Chains Daily/weekly/monthly
    3. Perform Change run Hierarchy
    4. Check Aggr's Rollup
    To add to the above
    1)check data targets are ready for reporting,
    2) No failed or cancelled jobs in sm37 monitors and Bw Monitor.
    3) All requests are loaded for day, monthly and yearly also.
    4) Also to note down time taken for loading of critical info cubes which are used for reporting.
    5) Is there any break in any schedules from your process chains.
    Siggi's weblogs for data load error and how to restart process chain
    /people/siegfried.szameitat/blog/2005/07/28/data-load-errors--basic-checks
    /people/siegfried.szameitat/blog/2006/02/26/restarting-processchains
    As the frequent failures and errors , there is no fixed reason for the load to be fail , if you want it for the interview perspective I would answer it in this way.
    a) Loads can be failed due to the invalid characters
    b) Can be because of the deadlock in the system
    c) Can be because of previous load failure , if the load is dependant on other loads
    d) Can be because of erroneous records
    e) Can be because of RFC connections
    These are some of the reasons for the load failures.
    1. Why there is frequent load failures during extractions? and how to analyse them?
    If these failures are related to Data, there might be data inconsistency in source system. Though we are handling properly in transfer rules. We can monitor these issues in T-code -> RSMO and PSA (failed records) and update.
    If we are talking about whole extraction process, there might be issues of work process scheduling and IDoc transfer to target system from source system. These issues can be re-initiated by canceling that specific data load and ( usually by changing Request color from Yellow - > Red in RSMO). and restart the extraction.
    What is the daily task we do in production support.How many times we will extract the data at what times.
    It depends... Data load timings are in the range of 30 mins to 8 hrs. This time is depends in number of records and kind of transfer rules you have provided. If transfer rules have some kind of round about transfer rules and updates rules has calculations for customized key figures... long times are expected..
    Usually You need to work on RSMO and see what records are failing.. and update from PSA.
    What are some of the frequent failures and errors?
    As the frequent failures and errors , there is no fixed reason for the load to be fail , if you want it for the interview perspective I would answer it in this way.
    a) Loads can be failed due to the invalid characters
    b) Can be because of the deadlock in the system
    c) Can be because of previous load failure , if the load is dependant on other loads
    d) Can be because of erroneous records
    e) Can be because of RFC connections
    These are some of the reasons for the load failures.
    for Rfc connections:
    We use SM59 for creating RFC destinations.
    Refer the help on creating source system:
    http://help.sap.com/saphelp_nw2004s/helpdata/en/ac/4a4e38493e4774e10000009b38f889/frameset.htm
    http://help.sap.com/bestpractices/crossindustry/businessintelligence/v131/BBLibrary/documentation/B84_BB_ConfigGuide_EN_DE.doc
    Data Validation:
    In BW any extraction we have to do Data Validation ..i.e.. data comparision between BW side and Source System side (Ex..R/3). Normally we do it in Unit Testing.
    Pls do check the link below
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/8c92d590-0201-0010-5aa0-ee7a993f295c
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/968dab90-0201-0010-c093-9d2a326969f1
    upgrade
    Check the INSTGUIDES from market place related to 04S upgrade:
    https://websmp106.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000659945&_SCENARIO=01100035870000000202&
    Also:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/2e8e5288-0b01-0010-2ea8-bcd4df5084a7
    Release notes for 04s:
    http://help.sap.com/saphelp_nw2004s/helpdata/en/57/a21f407b402402e10000000a1550b0/frameset.htm
    take a look in:
    www.service.sap.com/bi --> Product Information Previous Releases --> Media Library --> HOW TO... Guides --> Guide List SAP BW3.5 - Part of NW 04 --> Business Intelligence --> How to… SAP BW 3.5 upgrade prep & postupgrade checklist.
    Here you will find all necessary steps for an Upgrade.
    Source system
    http://help.sap.com/saphelp_nw04/helpdata/en/7a/27bcf087c7464db8b95eaa717b6e6a/content.htm
    Dead Locks
    Refer the lniks:
    Re: cube lock when multi-request insert at same time
    Re: Dataloading Shortdump
    ****Assign Points if Helpful****
    Regards,
    Ravikanth

  • Business scenarios for Production support !!!

    Dear experts,
    i have conceptual knowledge on Production support so can any body tell about some Business scenarios for Production support like frequent failures of infopackages, loads..etc.
    can any body tell the regular activities of Production support people.
    Thanks
    Regards,
    srikanth.ch

    Hi,
    Please search the forum. You'll get a lot of good material on Production Support activities. This topic has been discussed in detail on the forums.
    Cheers,
    Kedar

  • Support Tickets

    Hi Experts,
    Could you please let me know what are the typical Support Tickets and its solutions probably faced in a project.
    Points will be awarded.
    Krishna

    Krishna,
    Normally the production support activities include
    1.Scheduling
    2.R/3 Job Monitoring
    3.B/W Job Monitoring
    4.Taking corrective action for failed data loads.
    5.Working on some tickets with small changes in reports or in AWB objects.
    6 Data Loading - could be using process chains or manual loads.
    7. Resolving urgent user issues - helpline activities
    8. Modifying BW reports as per the need of the user.
    9. Creating aggregates in Prod system
    10. Regression testing when version/patch upgrade is done.
    11. Creating adhoc hierarchies.
    12. Any plans for upgrade?
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d0c8e590-0201-0010-d281-a54336883a5e
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/documents/a1-8-4/effective%20sap%20bw%20system%20management.pdf
    Hope it helps you...
    Assign Points if it helps...
    Regards,
    Gattu

  • Transaction List for SRM Support

    Hello Experts,
    We are going live very soon on my project and for support activites basis guy will create a custom role, So we need to list down all standard t-codes in SRM to solve future problems and we need to provide that list for creating a custom role.I try to create one list but if you experts provide me  then i ll be sure of it
    Thanks!!
    Sunny Sharma

    Hi Sunny,
    I thoucht you only need administration roles.
    If you also would like to use the application transactions as well, please see the the following roles:
    /SAPSRM/BIDDER
    SAP_BC_WEBSERVICE_DEBUGGER
    SAP_BW_DEVELOPER
    SAP_CFX_USER
    SAP_SLD_DEVELOPER
    SAP_SRM60_BIDDER
    SAP_SRM70_BIDDER
    /SAPSRM/EMPLOYEE
    /SAPSRM/OP_PURCHASER
    /SAPSRM/ST_PURCHASER
    SAP_EC_BBP_PURCHASER
    /SAPSRM/MANAGER
    SAP_BBP_STAL_PURCHASE_MANAGER
    SAP_BC_BMT_WFM_UWL_END_USER
    SAP_BC_UWL_END_USER
    SAP_QAP_DEBUG_AUTH
    SAP_SRM70_MANAGER
    /SAPSRM/ACCOUNTANT
    SAP_SRM70_ACCOUNTANT
    in case something is missing, use the SU53 for finding the object/activity.
    Reagrds,
    Peter

  • Bw support documentation

    Is there any documentation for bw support projects....totally from support point of view and not development.....

    Hi
    Normally the production support activities include
    1.Scheduling
    2.R/3 Job Monitoring
    3.B/W Job Monitoring
    4.Taking corrective action for failed data loads.
    5.Working on some tickets with small changes in reports or in AWB objects.
    6 Data Loading - could be using process chains or manual loads.
    7. Resolving urgent user issues - helpline activities
    8. Modifying BW reports as per the need of the user.
    9. Creating aggregates in Prod system
    10. Regression testing when version/patch upgrade is done.
    Refer thz links
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/documents/a1-8-4/effective%20sap%20bw%20system%20management.pdf
    (https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d0c8e590-0201-0010-d281-a54336883a5e)
    Production support issues
    Production Support
    ERRORS IN BW PRODUCTION SUPPORT
    Production support???? urgent

  • Golive and support

    Hi gurus
    pale give me beef explaine the golive scenario in the r/3 system in real time
    ple give the answer in the above  it is helpfull to me
    Thank you

    Hi,
    the following are the go live and support activities :
    Read it as Key Activities /     Deliverables
    formatting not really good, please adjust.
    1)Provide Production Support (Help Desk)/Production Support (Help Desk) Established
    2)Execute Daily Operation Support and Administration
    •     Optimize System Tuning     /Production-Ready Systems Environment
    3)Validate Live Business Process Results /     Business Process Results
    4)Monitor Transactions, Interfaces and Procedures /     System tuning and Procedural Updates
    5)Execute Ongoing Security Administration /     Security Administration
    6)Provide Ongoing Training Support / Execute Ongoing Training Support
    7)Develop Continuous Improvement Plan /     Continuous Improvement Plan
    8)Produce and Deliver Program Management Status Reports     /     Completed Status Report and Updated Issues Log
    9)Post Implementation Review /     Post Implementation Findings Reports
    Thanks
    Sadhu Kishore

Maybe you are looking for