used in your project to clear few things in my mind?
The Change Request is that request when you do some thing new in customizing or configuration in the system. The system will automatically pop with the change request pop box , when you can give request name as defined by the system or can give your own request name with heading of what changes you have made while customization. The system will generate a request number and you save it. (e.g.:- VEDK-2785467) VEDK- means the Clients System name then followed by the system generated request number.
Now when you want to release the request you have to use the T-code SE10 where you can see the requests under the heading modifiable or released. Go to the modifiable option. Each request will have again an internal request number. First you have to release the internal request and then release the external request number. This will in turn released by the basis guys thru the T-code SM64 in a group when all the requests are pooled from different users.
The task which you have mentioned in your question is nothing but the what task you have performed while customizing the client system and the heading name which have given it for that task and generated a request for that task.
2. What is your client Number in the project? Like how we have 800 for IDES?
Generally like IDES client, when you are in the project, the client is also given a number called client number. So while implementing a project The entire implementation is done under phases and in different Client no Servers.
e.g.:-take a company called ABC which is implementing
SAP.
So the Client is given a number in the following
manner by the SAP Implementers at the site
291- Sand Box server (Initial Testing scenarios
Server)
292- Development Sever (With client data of minimum
15 days transactions)
294- Testing Server (the scenarios developed in
development server is tested here)
295- Golden Master Server (Quality cum Testing
Server) - checked finally before transferring to production server
296- Production Server (where the clients live
data is stored and daily business transactions are done)
3. Few client requirements for customer master, material master, Organization and Transactions.
The client requirements may be in the form of customized reports and queries which are supposed to be suited according to their business process. Generally the requirements would be coming from the BPO's (Business Process Owners) who will deputed for each module e.g.:- SD, PP QM FI) by the client as they would be expert in their areas and module who under the business processes as they clients Project Team members. They are whole and sole responsible to get the implementation done and meet the requirements raised by them and the other users from the client’s side.
Generally before starting the implementation the entire organization structure and the organizational elements are freezed and a skeleton structure is prepared and then along with BPO's requirements the system is 1st configured and then the customization is started to suit the Clients specified requirements.
Now as far as the transactions are concerned not all the users are allowed to run all the transactions. Here the user roles are defined as per the BPO's (i.e., the user is given authorization only to run certain transactions depending on the levels and stages in his area of specialization like in SD module the entry level user is only allowed to enter the data like creation of Sales orders or delivery and billing and the next level is give the authorization for changes to be made for that same data that is entered by the entry level users. The next higher level -Supervisor is given a few more transaction authorization which will be above these mentioned users)
Here the reports are segregated like Higher Management Reports, Middle Management Reports where by again authorization is given those heads(Head of the Depts. or the Plants heads or GM etc.,) to run certain transactions which allow to view reports that are needed daily by the management.
SAP SD Tips by : Moyin
4. How to restrict users for not changing some fields in T-code va02?
There are two ways to do this:
- Make a transaction variant thru SHD0 and assign it
to your sales doc. While creating the variant you can place non-changeability
ticks on specific fields. Next allow those users only to work with your
transaction variant but not with the original transaction.
- You could make use of user-exit FORM USEREXIT_FIELD_MODIFICATION
in include MV45AFZZ (via authorization objects, which you can assign in
role customizing).
The latter is more flexible but it is not feasible if
you want to place restrictions to a large amount of fields. *--
Sabir
5. How can we delete the Sales Orders?
How can an invoices
be cancelled or deleted?
You can very well delete sales order using transaction VA02, but with a constraint that no subsequent document is created against it.
Invoice can be cancelled using T cose VF11 and then you
can reverse the Goods Issue using VL09 and making the picking quantity
zero in the deivery document and delete the delivery order using VL02n
. You can then delete the sales order then.
*-- Vaibhav
You cannot delete an Invoice. You can only cancel it with (VF11) if the relevant accounting document is not been generated. Ask your FI guy to reverse the accounting doc. Only after the accounting doc is reversed and/or deleted, you can cancel your invoice. You also need to check if any TAX documents are generated with your Invoice. You need to reverse/delete those documents also. *-- Ganeshan.D
