How To Fix PSRM_SOA079 - AccessPermissionTypeCode: "&" is not customized in the application

SAP Error Message - Details

• Message type: E = Error

• Message class: PSRM_SOA - Messages for Service Enterprises in PublicSectorRecordsMgnmt

• Message number: 079

• Message text: AccessPermissionTypeCode: "&" is not customized in the application

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 PSRM_SOA079 - AccessPermissionTypeCode: "&" is not customized in the application ?

  The SAP error message PSRM_SOA079 indicates that there is an issue with the access permission type code in the SAP system. Specifically, the message states that the access permission type code represented by "&" is not customized in the application. This typically occurs in the context of SAP's Supplier Relationship Management (SRM) or similar applications where access permissions are defined.
  
  Cause:
  
  Missing Customization: The access permission type code that is being referenced has not been defined or customized in the system. This could be due to a configuration oversight or a missing entry in the relevant customizing tables.
  Incorrect Configuration: The system may be looking for a specific access permission type that has not been set up correctly or is not available in the current environment.
  Transport Issues: If the system has recently undergone a transport of changes, it is possible that the necessary configurations were not included in the transport request.
  
  
  Solution:
  
  
  Check Customizing Settings:
  
  Navigate