Critical tickets &  scenarios

Can anyone forward critical scenarios and critical tickets in SAP FICO to my mail ID  [email protected]
Thanks
Shravan

Link: http://help.sap.com/
Path: SAP Best Practices --> Baseline Packages --> Based on SAP ECC 5.00 --> Select Country: for eg, Localized for India --> Technical Information --> Building Blocks --> Select Country for eg, India --> List of Basic Configuration & scenarios will be listed.
Select the required basic configuration / <b>scenario</b>. These will consist of overview, configuration guide, business process, master data &so on ...........
Regards,
Rajesh Banka
Reward suitable points.
How to give points: Mark your thread as a question while creating it. In the answers you get, you can assign the points by clicking on the stars to the left. You also get a point yourself for rewarding (one per thread).

Similar Messages

  • Service ticket  scenario

    Hello experts,
               Am very new to CRM & ICWC.
    Can anyone please tell me the steps or provide me a link to set up a simple demo Service ticket scenario?
    Your response in appreciated,will also reward points .Please help!
    the scenario could be as follows
    Customer Request(complaint) -
    > Handle Request(by IC represntative) -
    >Create Ticket and forward complaint to back office---->Process complaint->Inform Customer.-->End process
    Regards,
    Sandeep

    Hi Sandeep,
    This scenario is given in best practices C78, link for C78 http://help.sap.com/bp_crmv250/CRM_DE/BBLibrary/html/BBlibrary.htm
    Cheers,
    Madhu.

  • Critical Tickets in MM

    Dear Gurus
    I need some business critical tickets related mm. I goan thru sdn maximum querys. but, i am not able to finding the same tickets. Honestly, i don't have idea about critical tickets. if any body aware of this tickets pls give me reply urgent. full points rewarded and thanks in advance.
    Regards
    Laxman

    Hi,
    Critical tickets means the Priority 1 tickets, you need to solve this tickets immediatly as this effects the business of the client on the day.
    for eg:
    Client is preparing the Invoice for the Customer, Material is ready for shipping with Truck. When the user is doing the Outbound delivery against Sales order then system is throwing the error that some materials is not in the stocks, because the Stores person is not yet done the GR for that materials. Because he is facing some problem in price, so at this time the consultant should check the details and provide the solution immediately so that GR can be done & delveiry is created and invoice can be posted so material goes with truck.
    This critical issues can be solved once you are through with the Modules so that you can pick up the issue immediately and provide the solution.
    Like this there are so many critical issues will be comming everyday  and you need to solve with in the time or as per SLA with client.So be prepare for this in your real time otherwise it will reflect the bad impression on the consulting partner.
    rgds
    Chidanand

  • Insert into duplicate entries--exception in service ticket scenario

    Hi All,
      I am facing small problem..
    1. I have property field in service ticket component ICCMP_BTSHEAD.
    2.I put some validations based on property .
    3.when user clicks on create service ticket it will create service ticket with PROPERTY field filled up with some value.
      if user clear that value and clicks enter
      again if user enters the some value in field and click on save  it leads to exceptions that is of type insert duplicates array..like that..
        when i checked in debug....for the above procedure the service ticket guid is there in some internal table twice..
      if i did nt dne the steps like above,..i.e with out making property field blank..then no duplicates..
    can any body through some light on this?

    OSS note resolved it

  • Critical issue in MM??

    hi
    Cam somebody share their real time MM issues with explanation about the issues and the solution??
    In real time exp , anybody explain with critical tickets .. and solutions for the same ??
    Like example we have to solve the tickets within 24 hours , 12 hrs , 2 hrs ..etc
    Thanks

    Usually this error I anticipated were either related to printer message not configured properly, or accounting document not updating correctly. Check either or and see where the problem is. Check this blog I wrote on this error: I came across one problem at one of my projects which I would like to share for everyone's experience. The problem was when client was doing MIGO and when he was saving the document, it was making the MM document, but when you hit back button or go for display it came up with this error 'UPDATE WAS TERMINATED'. This problem came up in both MIGO and SD billing document posting. Now I had to jott down what the problem really was, so I started closing up on problem, by creating many PO's and doing MIGO'S against them with different document types, all went great and those documents got posted, but when I used the same GL'S as client was using as he was charging it to cost center and the GL'S used there were consumption GL'S,those GL'S were causing the problem. How I found out that GL was causing problem, as I used another GL which was not for consumption and the document got posted. Now as the problem got cornered, now we had to figure out how to solve it. Here at client we have two plants, one for Pakistan and one for Philippines, so I checked the same scenario on Pakistan and the document got posted with consumption GL as well. So now its more clear that problem is with client Philippines posting. So I sat down with (ABAP) consultant to check out the problem. He went through his checking and pointed out that one document No. 40000400 was not getting updated. Now the question came what document this number is assigned to. Suddenly it clicked my mind to check the client Pk document which was posted with same Gl, so when we displayed that document we came to know that this number range was getting assigned to CONTROLLING DOCUMENT. So we went back in customizing, and found out that CONTROLLING DOCUMENT current number was stuck on 40000100, whereas the last number recorded in table was 40000400, so we updated the current number there and thats the end PROBLEM SOLVED. This controlling document Number was causing this problem on both MIGO and SD billing document. Another solution which came to our mind was to clear the Buffer, so that the number ranges of the clients gets updated and we notified our basis person as well but in mean time we solved the issue

  • Real time tickets

    Hi friends
    Can any one who are in the support project can give me some of the real time problems from end users-tickets-any critical tickets with solution please
    thanks & Regards
    maunami

    Real Time Issue:
    Billing Document not released to accounting / Accounts determination:
    To resolve the error, you can analyze account determination in the billing document. Process:
    Goto T.Code: VF02 & Enter Invoice number
    Next (On the top most strip) goto Environment
    Next (Select Environment) go to Account determination
    Next (In Account Determination) select Revenue Account Determination (first option)
    This will list all the condition types in the Billing document & analyze each condition & check for which G/L accounts is not determined.
    Possible errors:
    1. VKOA not maintained for required combination
    Solution: Maintain the combination in VKOA.
    2. Account Assignment of Customer / material not maintained in Customer / Material Master (If maintained in combination in VKOA).
    Solution:
    Option 1 (Standard solution):
    step 1: Cancel Billing Document --> Reverse PGI --> cancel Delivery --> Cancel Sales Order
    step 2: Maintain Customer master / Material Master correctly.
    step 3: Recreate sales Order --> Delivery --> PGI --> Invoicing.
    Option 2:
    Force the Account Assignment Group of Customer / Material through Debug in change mode of Billing document, which will release Billing Document to Accounting.
    3. Account Key not maintained in Pricing Procedure:
    Impact: This may create accounting document, but if condition type, which are to be posted to account, but do not have account key maintained in pricing procedure, it will not be post the relevant condition type to G/L account.
    4. Billing Document not being released to accounting --
    In Material Master, there is some link between Profit Centre & MRP Type. If one of it is not maintained, erratically few documents get stuck while releasing Billing Document to accounting. Few of course get posted.
    Solution1: Cancel Billing Document --> Reverse PGI --> Cancel Delivery --> Block the sales Order & Create new sales Cycle all over again after rectifying Material master.
    Solution 2: (Temporary Solution) In Debug mode in Billing, force the Profit Center in Billing Document with the help of Abaper. But ensure Material master is rectified.
    From FI Side, you require to check that all the G/L account has been maintained through T.Code: FS00. G/L account being Master data has to be created in each client to upload through LSMW / SCATT / BDC.
    In Billing Document in change mode (in the first screen where we enter Billing Document number), on the top most left hand corner, take a dropdown on Billing Document & select Release to accounting. Here you can get the under mentioned possible message:
    1. G/L account not found
    2. Cost Element not maintained for G/L account.
    In both the above cases, FI consultant requires to take corrective action.
    Pricing:
    This is very specific & differs from client to client & may also differ based on scenario.
    Write-up on Pricing -
    In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
    In SD, the steps to configure Pricing procedure are as under:
    Step 1:
    Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).
    Step 2:
    Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
    Step 3:
    Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the necessary changes. Here we assign Access sequence to Condition type.
    Step 4:
    a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the necessary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
    b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
    5. Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.
    It is assumed that document pricing procedure, customer pricing procedure , ... are in place.
    Sales Document not assigned to Sales Area:
    SPRO --> Sales & Distribution --> Sales --> Sales Documents --> Sales Document Header --> Assign Sales Area To Sales Document Types --> Assign sales order types permitted for sales areas (do ensure to maintain combined Sales organization, combined Distribution channel & combined division. for eg: Sales org 1000 & sales org 1000, Sales org 2000 & sales org 2000, & so on ....
    similarly for distribution channel & Division, so that the Sales area combination is available for assignment to Sales Document Type.)
    Issues related to Customer Master data:
    1. what is the impact of leaving customer pricing procedure & customer statistic group blank in customer master --> sales area data --> sales tab:
    If Customer Pricing Procedure is left blank, Pricing will not be determined.
    If customer statistic group is left blank, then data will not flow to standard reports.
    2. Who maintains reconciliation account in customer master?
    Ideally, reconciliation account is maintained by FI person, but if SD person is authorized & has the knowledge of which reconciliation account to be maintained, then even SD person can maintain the same.
    3. Terms of payment appear in Company Code Data & sales Area Data. What is the impact of each? why is it not populated automatically, once it is maintained at either field?
    Terms of payment from company code data is for reporting purpose & it is from sales area data that it flows to sales order.
    It is a standard feature of SAP that it is not populated automatically if maintained at either of the field, but it is a must in sales area data & can be skipped in company code data.
    4. Unable to select Sales Area for Customer Master Creation?
    Most Probably either sales area is not defined or customization not done for common Sales Org & Common Distribution Channel. To maintain this configuration: SPRO --> Sales & Distribution --> Master Data --> Define Common Distribution Channels / Define Common Divisions
    The above are few examples.
    /message/3690162#3690162 [original link is broken]
    Regards,
    Rajesh Banka
    Reward suitable points.
    How to give points: Mark your thread as a question while creating it. In the answers you get, you can assign the points by clicking on the stars to the left. You also get a point yourself for rewarding (one per thread).

  • Tickets, partitionin

    Hi,
      It is a two-part questtion,
    first off what is our interaction with
    end user in tickets and plz name a few
    ticketing scenarios in relation to priority levels.
    this is regarding partitioning of an IC is partioning
    implemented in implementation or
    in production support...
    thanks all,
    due points will be assigned

    Hi,
    tickets are nothing but just a issues or problems faced by the user which i can say. This comes basically if you are in a Support project. When user faces a problem(means for e.g.he is getting an error and he can't proceed with that process) he log a request with his team(client) and client team also are the experts and if they are not able to find a solution they will raise a TICKET with the solution provider and the support/maintainence persons will work on that and gives the solutions..
    Tickets are WORK REQUESTS in production support,to keep track of issues and their solutions . Create ticket and assign it to some on so that you trck the status of the ticket and issues related to that ticket .
    In future same problem occured refer to that ticket and solve the problem with out investigation etc ..
    Ticket is a request in production support.Reg the no.of types of tickets it depends on the SLA(service level agreement) between you and your client.They can be module specific in order to route the ticket to the respective person and reduce the processing time.Prioritisation of the tickets like high,medium,low are based on the needs of the client.
    these are the different types of tickets with example
    1. Loading any of the missing master data attributes/texts - This would be done by scheduling the infopackages for the attributes/texts mentioned by the client.
    2. Create ADHOC hierarchies. - Create hierarchies in RSA1 for the info-object.
    3. Validating the data in Cubes/ODS. - By using the Validation reports or by comparing BW data with R/3.
    4. If any of the load runs into errors then resolve it. - Analyse the error and take suitable action.
    5. Add/remove fields in any of the master data/ODS/Cube. - Depends upon the requirement
    6. Datasource Enhancement.
    7. Create ADHOC reports. - Create some new reports based on the requirement of client.
    handle tickets with tools
    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.
    Generally 'Vantive' is used for tracking user requests and tickets.
    It has a vantive ticket ID,field for description of problem,severity for the business,priority for the user,group assigned etc.
    Different technical groups will have different group ID's.
    User talks to Level 1 helpdesk and they raise ticket.
    If they can solve issue for the issue,fine..else helpdesk assigns ticket to the Level 2 technical group.
    ticket status keeps changing from open,working,resolved,on hold,back from hold,closed etc.
    the way we handle the tickets vary depending on the client. some companies use SAP CS to handle the tickets, we have been using Vantive to handle the tickets.
    the ticket is handled with a change request, when you get the ticket you will have the priority level with which it is to be handled. it comes with a ticket id and all.
    It depends on what tool the client is using to keep track of requests/tickets raised by users. The tools used for this purpose varies from client to client and with them varies the way of informing about the new request, way of responding it et
    -Shreya

  • Five Recovery Scenarios

    Hi,
    Please tell me five critical recovery scenarios and steps to recover those scenarios.
    Thanks,
    Suresh Bommalata..

    Suresh Bommalata wrote:
    Hi,
    Please tell me five critical recovery scenarios and steps to recover those scenarios.
    Thanks,
    Suresh Bommalata..Dear Suresh
    As Aman has suggested, you need to read the Backup and Recovery guide from http://tahiti.oracle.com
    Read the documentation and practice all scenarios on your own

  • Tickets from mm

    dsp gurus
    can u pl post me some critical tickets in mm with the solution

    Venkatesh,
    keep watching all the threads,
    These all are real time tickets with solutions. as well as learning doubts.
    Using Filter(above all the threads) Select Answered questions. and check the issues.

  • MSS Workflow: Display Form: Connection from R/3 to Portal.

    Scenario and Description:
    User is in R/3 Workflow Inbox. They have a MSS related "Change Notification: PAR with Approval" such as a Salary Change, etc. When they click on "Display Form" link their MS IE Browser opens and they are prompted to logon to the Portal prior to the form displaying.
    The issue is that they are forced to log into the Portal even if they are already logged onto the Portal.
    Is this the way it needs to work or can we set some parameter to have it so users don't have to log into Portal again when they are already logged in to Portal?
    Thank you for your response,
    Glenn

    I do have SSO configured and I have even used SSO Wizard to set the R/3 system as trusted on the J2EE server side. We currently have EP 7.0 but have been using Portal since v.5.0.  We have never had this problem in the past. All R/3 ids match network/portal ids. If we open an IE browser and logon to portal and then open another IE browser from start menu we also have to log into Portal again. This is typical session based behavior but what I would like to know is, should we be expecting this behavior from R/3 to Portal or should the whole SSO/logon ticket scenario free us from having to login to the Portal more than one time (if we are still logged in)?
    PS: I see nothing in the link you sent me that we have not already done.
    Thanks,
    Glenn

  • Conversion of large unit of measures

    Dear Experts,
    To implement a critical business scenario i need to implement following conversion -
    245 X = 1000000 Y, but due to limitation of numerical digits to 5 i am notable to do this, if anybody can suggest for the same please.
    I shall be greatfull to all
    thanks in advance. point will be rewarded please.
    Regards,
    Pawan Khurana

    Further digging leads me to believe that the issue is that iOS 7 uses more RAM, and on the iPad 2, this doens't leave quite enough memory to open these 36MP RAW images.
    If I close all background apps, I have been able to get Filterstorm Neue to open and edit these RAW images, while having any app still running in the background will cause a crash. No such luck with Snapseed as I'm guessing it uses a bit more memory than Filterstorm. This would account for why PhotoRaw can open and edit these files -  it uses a virtual memory approach to load large files.
    So unless iOS 7 becomes better optimised for RAM usage, or these apps are updated to use virtual memory, looks like I'm limited in which apps can open 36MP RAW images on an iPad 2.  Wonder if a newer retina iPad would manage? They have more RAM I believe, but probably need more to run the display...

  • Service Request Building Block

    Hello everyone,
    We are currently evaluating the use of the Service Request for a incident/'alarm" tracking scenario.
    In this regard, does anyone know if there is a building block configuration guide for this? I was looking in the Best Practices but i was unable to find a specific one for Service Request. I would appreciate any help, or extra info.
    Many thanks in advance,
    Pedro

    Hi Pedro,
    You can go through this help document to know more about Service Ticket scenario in IC WebClient:
    http://help.sap.com/saphelp_crm70/helpdata/EN/46/23dafbc17b5872e10000000a11466f/frameset.htm
    Also you can have a look into the CRM best practice document "E-Service: Service Request Management (C76)", which gives the process flow.
    Hope this helps!
    Regards,
    Chethan

  • Subject Profile & MultiLevel Categorization

    Hi All,
    Can Anyone throw some light on these topics,
    1. Subject Profile
    2. Mulitilevel Categorization
    3. Categorization Schema
    4. How they are related & used in Service Ticket Scenario
    Any Help/Hint will be highly Appreciated
    Thanks, Sudeep..

    Hi Sudeep,
    For Categorization we need to create Catalogs, Codes and Profiles and assign to subject Profile in SAP GUI.Then assign this Subject profile to Transaction.
    In Multilevel Categorization we Define Application Areas for Categorization ( i.e COMPLAINT ) and the Subject Profile is assigned here to the Application Area thru Parameter.
    Categorization Schema helps you create and define different categories and sub-categories via Category Hierarchy
    So this way the selection options of one field is depdent on the selection option of the previous field.
    Let me try to explain you with an example could be a silly one.
    Suppose you have a 2 fields *** and Names. In the field *** you have option Male and Female as drop down. IF you select male then the names field should show only male names where as if you select Female then in the Name field you should have options to select only female names.
    Regards
    Arup

  • Loan Management Configuration

    Hi All,
    In our new implementation project the scope of the project includes the Loan management. It is not banking industry company. Still there is a requirement of Loan management configuration. I have seen the loan management under SAP Banking menu. Is it possible to configure loan management alone with out having any other areas in Banking? If so where can i get the concerned configuration and BPP documents? I have made a search in Building block docouments but could not find.
    Thanks in advance
    shankar
    Edited by: Shankar on Sep 29, 2009 3:51 PM

    Hi Shankar,
    Yes, we can implement Loans Management which is under SAP Banking without implementing other sub-modules.  There is no such documentation available under Building blocks, probably you can search under IS Banking, I am not sure on this.  The course on Loans Management is "FS210 - Loan Managementfor finanancial services".  Try your luck if you can find any link to get this material.
    There  is another way to handle loans in SAP, i.e. under FSCM - Treasury & Risk Management.  Here we can map loans to some money market instruments (interest rate instrument, etc.). 
    The decision to implement the module depends on the criticality of scenario (loan types, terms, etc.) and also the number of transactions, etc.  Both these are separate modules and will have lot of configuration and procedures to process in SAP.  If you have loans taken as well as loans given I suggest Loans Management.  Else, if you have implemented Treasury & Risk Management it is better to go with the same.
    Hope this information will help.
    thanks,
    Kumar

  • "Ticket authentication failed" error in Principal Propagation scenario

    Hi All,
    I am working on Principal Propagation, where the scenario is sync RFC-PI-RFC. I have followed all steps mentioned in the below blog. When I execute the scenario (with Principal propagation box checked in the sender agreement) I get dump while executing the RFC from sender system. The dump is:
    "Ticket authentication failed"
    Scenario works fine if I don't check Principal propagation check box in the sender agreement.
    Principal Propagation blog: /people/alexander.bundschuh/blog/2007/01/16/principal-propagation-in-sap-xi
    Can anyone suggest what can be the reason for this dump?
    Thanks,
    Shweta.

    Hi All,
    Any inputs on this?
    Thanks,
    Shweta.

Maybe you are looking for