on 08-05-2013 6:42 AM
Dear All,
We have recently upgraded our production system from ECC6 to EHP5.
There is a new future of Service Tax in EHP5.
But in J1ILN - T-Code - "Service Tax" node is not visible.
Before production, we have upgraded DEV and QAS. In both DEV and QAS "Service Tax" tab is visible.
Same download queue we have used to upgrade PRD, but in PRD "Service Tax" tab is not visible
Is there any thing need to do to activate the same ?
Thanks and Regards,
Nirav
Hi NIrav,
For service tax node to appear in SPRO your system should be in below
SPs-
SAP_APPL 605 SP02
SAP_APPL 604 SP08
SAP_APPL 603 SP07
SAP_APPL 602 SP08
SAP_APPL 600 SP18
SAP_APPL 500 SP24
SAP_APPL 470 SP35
notes- 1393460 and 1391485 also need to be present in your
system.
Also check the role applied is - sap role SAP_CIN
Here you can see all the menu path for CIN in J1ILN
Regards,
Anushya
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Nirav,
India localisation settings are supplied with the 000 client. If and when
you want to use the India localisation functionality you can copy the standard/default settings from your 000 client to your customising client.
The country specific details will by default be available in 000 client.
Could you check the client 000 has this node or not?
The above mentioned are the settings necessary for service tax node, there are no additional settings, and if you have them all in place, then you should definitely get the node.
Also refer note - 1391485 for some more details on this node.
Regards,
Anushya
Dear Anushya,
SAP has taken too much time to analyze problem.
Finally SAP has replied as :
************************
I have analyzed the issue comparing both PRD and QAS. Though SP levels
of both system are same the node 'Service tax' seem to be missing in PRDNode is not attached to any switch/enhancement, so i can only say that
this is due to some inconsistency which may have happend during
upgrade but i am afraid it is difficult to analyze this inconsistency.
I can only suggest you can create a transport request in Development
system and then release and import in production system. We have
seen such issue once in while but root cause cannot be analyzed in
such case.
****************************
Thanks and Regards,
Nirav
User | Count |
---|---|
98 | |
11 | |
11 | |
6 | |
6 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.