Handling Tickets Is Called Issue Tracking System.: Sap SD
Handling Tickets Is Called Issue Tracking System.: Sap SD
Handling Tickets Is Called Issue Tracking System.: Sap SD
To begin with , we should give "TICKET" to you for not knowing it.
Here is an e.g. of a ticket raise:
End user is not able to
1. Create Sales order for a customer from a New plant , since shipping point determination is not
happened . (Without Shipping point the document becomes INCOMPLETE and he will not be
able to proceed further like DELIVERY, BILLING).
He raises a ticket and the priority is set in one of the below:
1. Low 2. Medium 3. High.
Now you need to solve this ticket. You would analyze the problem and identify that the SP
configuration has to be done for the new plant.
You would request a transport for DEV CLIENT to BASIS. You do the change and Request one
more Transport to BASIS for QA client. The End user will test the same by creating a sales order
for the new plant and approve it.
Finally, you request a transport to move the changes to PRODUCTION. Once the change is
deployed in production the TICKET is closed. What I have given is a small example. You would
get some real issues with severity HIGH in your day-day support.
Common errors encountered while executing F110 (APP) and resolutions are
listed out here, hope these are helpful to troubleshoot the errors.
2) Company codes XXXX do not appear in proposal XX.XX.2011 XXXX( Run date & Identification)
Please check if you have any open items for the vendors or not for the dates you are running proposal. Check with
FBL1N report for the chosen vendor. This is telling you that F110 could not find any records that meet those criteria.
As it is a generic message and the error can be because of any reasons or combination of multiple reasons.
A review of the additional log should help you to identify exact reason for not selecting a particular invoice.
4) Account XXXXXX XXXX (Vendor Account number and Company code) blocked by Payment proposal
XX.XX.2011 XXXX (Run Date & Id)
Once you make a proposal for a vendor, you cannot create another proposal for the same vendor unless and until
first one is completed i.e. payment run is over. Unless payment run is over, vendor is locked for another proposal
Option1: complete the earlier proposal and continue the current proposal
Option2: Delete the earlier proposal and continue the current proposal
8) No pymt possible because items with a debit bal.still exist; see job log ( Contributed by Godavari
SAP Ravi Sankar Venna)
If a vendor has debit balance, it will be shown under exception list with this message. Automatic payment program will
pay a vendor with credit balance only.
If there is a debit balance on vendor due to any down payment, that needs to be adjusted while making the payment
for invoice. Otherwise, only making payment to invoices would be incorrect and the down payment would remains the
same on the account.
Therefore, it needs to be configured in FBZP.
==> All Company Codes
Include the special G/L indicators to be paid. Then they will also be selected within the payment and the invoice
amount would be adjusted accordingly.
9) Withholding tax information missing from line items ( Contributed by Aniruddha B Mahalle )
This error is because, if we update some with-holding tax parameters in vendor master after posting some vendor
transactions.
Delete the payment proposal in F110 transaction in which the aforesaid error occurred.
2.
3.
In the next screen, mention the affected vendor or range, mention your company code,
mention the date specifications, select following options as per your requirement
4.
5.
6.
Also down payment and partial payments with with holding tax codes
7.
8.
Project Preparation (Phase 1): This is the part where only the top line of the team, like project manager,
Project architect etc. come into picture. In this phase they decide, how to move in for the project, how many
consultants of which all modules and of what seniority level will be required. Secondly the timelines i.e for
Blueprint how much time and so on and so forth..
Blue Print
(Phase 2): This is the most critical phase as of the entire project is concerned. In this Phase the consultants
get in touch or have the initial one to one with the Client. They discuss about the project, how to proceed.
Two important words or terminology come into picture that is AS IS and TO BE. AS IS nothing but how the
organizational process is running currently , for this the Consultants prepare a questionnaire , gives it to the
company in concern and thereby gather information. After that they show the client , the TO BE process or
what will happen when SAP is installed and what and how will be the outcome will differ from before.
Depending on this AS IS and TO BE, consultants find out the gap underlying and on this the GAP ANALYSIS is
done. In this part most of the functional specs are done or what new Z Reports will be created. And after all
has been shorted out, the practical work starts , in the next pahse.
Realiazation