How To Fix HRESS_PTARQ201 - Document type &1 is not configured

SAP Error Message - Details

• Message type: E = Error

• Message class: HRESS_PTARQ - Leave Request Applications (ESS WDA)

• Message number: 201

• Message text: Document type &1 is not configured

What causes this issue?

The document type of the attachment is not configured in the table of
<ZK> Global Document Types</>. A document type is used to group similar
documents together, for example, <ZK>Leave Request Attachment</>. Each
document type has a document class, which determines the file type of
the document, for example PDF.

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

System Response

The <ZK>Leave Request </>application fails to upload the document.

How to fix this error?

Contact your system administrator.

Procedure for System Administrators

The document type table can be configured in the Customizing for
<LS>Edit Document Types</> under -><LS>SAP NetWeaver</> -> <LS>
Application Server</> -> <LS>Basis Services</> -> <LS>ArchiveLink</>.
The document type used for <ZK>leave request</> attachment is:
HRLRQATTCH. If an arbitrary file type is allowed, then you can use the
character '*'.
The correct table entry is as follows:
Document Type Description
Document Class
HRLRQATTCH Leave Request Attachment *

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message HRESS_PTARQ201 - Document type &1 is not configured ?

  The SAP error message HRESS_PTARQ201 indicates that the document type specified in the request is not configured in the system. This error typically occurs in the context of SAP's Employee Self-Service (ESS) or Manager Self-Service (MSS) applications, particularly when dealing with personnel requests or workflows.
  Cause:
  
  Missing Configuration: The document type referenced in the error message has not been set up in the system. This could be due to a missing entry in the configuration tables.
  Incorrect Document Type: The document type being used in the request may be incorrect or not valid for the current context.
  Transport Issues: If the configuration was recently transported from another system (e.g., from a development to a production environment), the transport may not have included the necessary configurations for the document type.
  
  Solution:
  
  
  Check Configuration:
  
  Go to the configuration settings for the relevant application (e.g., Personnel Administration or Organizational Management).
  Verify that the document type in question is configured correctly. This can typically be done in transaction codes like SPRO (SAP Project Reference Object) and navigating to the relevant section for document types.
  
  
  
  Create/Modify Document Type:
  
  If the document type does not exist, you may need to create it. This involves defining the document type in the relevant configuration area.
  If it exists but is not configured correctly, you may need to modify its settings to ensure it meets the requirements of your business processes.
  
  
  
  Check Authorization:
  
  Ensure that the user attempting to perform the action has the necessary authorizations to access the document type.
  
  
  
  Review Transport Requests:
  
  If the issue arose after a transport, check the transport logs to ensure that all necessary configurations were included and successfully imported.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for specific guidance on configuring document types related to your version of SAP.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SPRO for configuration, SE11 for data dictionary, and SE80 for development objects.
  SAP Notes: Check SAP Notes for any known issues or patches related to the error message. You can search for the error message number or related keywords in the SAP Support Portal.
  Community Forums: Engage with SAP community forums or user groups for insights from other users who may have encountered similar issues.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.