How To Fix G3704 - Dimension &1, version &2: Properties of doc. type &3 cannot be determined

SAP Error Message - Details

• Message type: E = Error

• Message class: G3 - Messages for SAP Consolidation: Integration

• Message number: 704

• Message text: Dimension &1, version &2: Properties of doc. type &3 cannot be determined

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 G3704 - Dimension &1, version &2: Properties of doc. type &3 cannot be determined ?

  The SAP error message G3704 typically indicates that there is an issue with the properties of a document type in the context of a specific dimension and version. This error can occur in various scenarios, particularly when working with SAP Business Planning and Consolidation (BPC) or SAP Analytics Cloud (SAC).
  Cause:
  
  Missing Configuration: The document type specified in the error message may not be properly configured in the system. This could be due to missing entries in the configuration tables or incorrect settings.
  Dimension Issues: The dimension specified in the error message may not be correctly defined or may not exist in the system.
  Version Issues: The version specified may not be active or may not have the necessary properties defined.
  Authorization Issues: The user may not have the necessary authorizations to access the properties of the specified document type.
  Data Integrity Issues: There may be inconsistencies or missing data in the underlying tables that manage document types and their properties.
  
  Solution:
  
  Check Configuration: Verify that the document type specified in the error message is correctly configured in the system. This includes checking the relevant configuration tables and ensuring that all necessary entries are present.
  Validate Dimensions and Versions: Ensure that the dimension and version specified in the error message are correctly defined and active. You may need to check the dimension settings and version management in the system.
  Review Authorizations: Check the user’s authorizations to ensure they have the necessary permissions to access the document type properties.
  Data Consistency Check: Perform a data consistency check to identify any missing or inconsistent data related to the document type, dimension, or version.
  Consult Documentation: Refer to SAP documentation or notes related to the specific error message for additional troubleshooting steps or known issues.
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions for common errors.
  Transaction Codes: Use transaction codes like SE11 (Data Dictionary) or SE80 (Object Navigator) to investigate the underlying data structures and configurations.
  Support Community: Engage with the SAP Community or forums to see if other users have encountered similar issues and what solutions they have found.
  System Logs: Review system logs for additional error messages or warnings that may provide more context about the issue.
  
  If the problem persists after following these steps, it may be necessary to involve your SAP Basis or technical support team for further investigation.