How To Fix SPXN070 - Referred type &1 &2 not found

SAP Error Message - Details

• Message type: E = Error

• Message class: SPXN - Proxy Generation

• Message number: 070

• Message text: Referred type &1 &2 not found

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 SPXN070 - Referred type &1 &2 not found ?

  The SAP error message SPXN070 indicates that a referred type (such as a data type, structure, or class) is not found in the system. This error typically occurs during the activation of an ABAP program, function module, or class when the system cannot locate a specified type.
  Cause:
  
  Missing Object: The referred type may not exist in the system. This could be due to it not being created, deleted, or not transported correctly.
  Transport Issues: If the type was supposed to be transported from another system (like a development system to a production system), it may not have been included in the transport request.
  Namespace Issues: The type may exist in a different namespace or package that is not accessible in the current context.
  Incorrect References: The code may have incorrect references to the type, such as typos in the name or incorrect case sensitivity.
  
  Solution:
  
  Check Existence: Verify if the referred type exists in the system. You can do this by using transaction SE11 (Data Dictionary) or SE80 (Object Navigator) to search for the type.
  Transport Check: If the type is supposed to be in the system but is missing, check the transport requests to ensure that it was included and successfully imported.
  Correct References: Review the code where the error occurs and ensure that the type is referenced correctly. Check for typos or case sensitivity issues.
  Recreate the Type: If the type is missing and you have the definition, you may need to recreate it in the system.
  Check Authorizations: Ensure that you have the necessary authorizations to access the type, especially if it is in a different package or namespace.
  
  Related Information:
  
  Transaction Codes: SE11 (Data Dictionary), SE80 (Object Navigator), SE37 (Function Modules), SE24 (Class Builder).
  ABAP Development: Familiarity with ABAP programming and the Data Dictionary is essential for troubleshooting this error.
  SAP Notes: Check SAP Notes for any known issues related to this error message, as there may be specific patches or updates that address the problem.
  
  If the issue persists after following these steps, consider reaching out to your SAP Basis or development team for further assistance.