How To Fix /CCIS/TAX128 - You are not authorized for tax hierarchy transport

SAP Error Message - Details

• Message type: E = Error

• Message class: /CCIS/TAX -

• Message number: 128

• Message text: You are not authorized for tax hierarchy transport

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message /CCIS/TAX128 - You are not authorized for tax hierarchy transport ?

  The SAP error message /CCIS/TAX128 You are not authorized for tax hierarchy transport typically indicates that the user attempting to perform a transport of tax hierarchy data does not have the necessary authorizations to do so. This error is related to the transport of tax-related configurations in the SAP system, particularly in the context of the SAP Convergent Charging (CC) or similar modules.
  Cause:
  
  Authorization Issues: The user lacks the required authorization objects to perform the transport of tax hierarchy data.
  Role Configuration: The user's role may not include the necessary permissions for the specific transaction or action they are trying to execute.
  Transport Request Settings: The transport request may not be correctly set up or may not include the necessary objects for the tax hierarchy.
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after the error occurs to check which authorization checks failed. This will provide insight into what specific authorizations are missing.
  Review the user's roles and profiles in transaction SU01 or PFCG to ensure that the necessary authorizations are included.
  
  
  
  Add Required Authorizations:
  
  If you identify missing authorizations, you may need to add them to the user's role. Common authorization objects related to transport and tax hierarchy might include:
  
  S_TRANSPRT (Transport Organizer)
  S_TAX_HIER (Tax Hierarchy)
  
  
  Consult with your SAP security team to ensure that the user is granted the appropriate permissions.
  
  
  
  Role Adjustment:
  
  If the user is part of a specific role that should have these authorizations, ensure that the role is correctly configured and that the changes are transported to the relevant systems.
  
  
  
  Testing:
  
  After making changes to the authorizations, have the user log out and log back in, then attempt the transport again to see if the issue is resolved.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to tax hierarchy transport for any additional requirements or considerations.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional context.
  Transport Management: Familiarize yourself with the SAP Transport Management System (TMS) to understand how transports work and what authorizations are typically required.
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  
  If the problem persists after checking authorizations and roles, it may be necessary to involve your SAP Basis team or SAP support for further investigation.