How To Fix FKKDK_MSG013 - You are not authorized to change CPR/CVR number maintenance

FKKDK_MSG013 - Overview

• Message type: E = Error

• Message class: FKKDK_MSG - Messages for Denmark FI-CA Localization

• Message number: 013

• Message text: You are not authorized to change CPR/CVR number maintenance

What causes this issue?

You are not authorized to <ZH>change</> content with the
<DS:TRAN.FPDKCPR>Denmark: Maintenance of CPR/CVR Numbers</> transaction.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Ask your system administrator to grant you authorization for the <ZK>02:
Create, change, or delete table entries</> activity using the
authorization object <DS:UO.S_TABU_DIS>S_TABU_DIS</> and table group
<ZH>FKDK</>.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FKKDK_MSG013 - You are not authorized to change CPR/CVR number maintenance ?

  The SAP error message FKKDK_MSG013 indicates that a user is not authorized to change the CPR (Customer Payment Request) or CVR (Customer Value Request) number maintenance. This typically occurs in the context of SAP Convergent Charging or SAP Convergent Invoicing, where specific authorizations are required to perform certain actions related to payment requests or value requests.
  
  Cause:
  The error is primarily caused by insufficient authorization for the user attempting to perform the action. This can happen due to:
  
  Missing Authorization Roles: The user does not have the necessary roles assigned that allow them to change CPR/CVR numbers.
  Authorization Object Restrictions: The authorization objects related to the specific transaction or function may not include the required permissions for the user.
  
  Configuration Issues: There may be configuration settings in the SAP system that restrict access to certain functionalities based on user roles.
  
  
  Solution:
  To resolve this issue, you can take the following steps:
  
  
  Check User Roles:
  
  Verify the roles assigned to