Tuesday, May 6, 2008

TAX/ TASK Request

To distinguish between global changes in the system and client-specific Customizing settings, modified objects are divided into different categories. Change requests and tasks are also assigned to these categories, depending on the objects they contain. There are two request categories:Customizing requestsCustomizing requests record client-specific Customizing settings made in a single client (the source client of the request). Change requestsChange requests contain Repository objects and cross-client Customizing objects. Change requests can also be mixed. This means that they may contain client-specific Customizing. However, as above, all the client-specific objects must only originate from one client (the source client of the request). 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 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. A request may contain more than one task, so when you want to move it, first all the indidual tasks should be released so that you can move the request.



Following are the conditions which you need to assign in your export pricing procedurePR00UTXJ 100%JMOD 16% BEDJEX2 100% of BEDJECS 2% CessJECX 100% of JECSJA1X 1% SCessJA1Y 100% of JA1XThe above conditions may be maintained as "Statistical". Also in VK11, UTXJ can be maintained for the combination of Country/Country/Tax Class.Mtrl/Tax Class.CustDepending upon the process, we may have to have some additional conditions in exports like discount, tool cost amortization etc., and all those needs to be considered before condition type JMOD

No comments: