How To Fix RSDS_ACCESS038 - &1: External format not supported; Data type is not 'CURR'

SAP Error Message - Details

• Message type: E = Error

• Message class: RSDS_ACCESS - Access Messages

• Message number: 038

• Message text: &1: External format not supported; Data type is not 'CURR'

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 RSDS_ACCESS038 - &1: External format not supported; Data type is not 'CURR' ?

  The SAP error message RSDS_ACCESS038 indicates that there is an issue with the data type being used in a DataSource, specifically that the external format is not supported because the data type is not 'CURR' (currency). This error typically arises when trying to extract or load data from a source that has a data type that is incompatible with the expected format in SAP.
  Cause:
  
  Data Type Mismatch: The data type of the field in the source system does not match the expected data type in the SAP system. For example, if the source field is a character or string type instead of a currency type, this error may occur.
  Incorrect DataSource Configuration: The DataSource may not be configured correctly to handle the data types being extracted.
  Unsupported External Format: The external format of the data being processed is not supported by SAP, particularly for fields that are expected to be in currency format.
  
  Solution:
  
  
  Check DataSource Configuration:
  
  Go to the DataSource in the SAP system and verify the field mappings. Ensure that the data types are correctly defined and match the source system.
  If necessary, adjust the DataSource to ensure that the fields are defined as 'CURR' where applicable.
  
  
  
  Modify Source Data:
  
  If you have control over the source data, ensure that the fields intended to be treated as currency are formatted correctly in the source system.
  Convert the data type in the source system to a compatible format if possible.
  
  
  
  Update Transformation Logic:
  
  If you are using a transformation to load data, check the transformation logic to ensure that it correctly handles the data types and formats.
  You may need to add logic to convert or cast the data types appropriately.
  
  
  
  Consult Documentation:
  
  Review SAP documentation for the specific DataSource and the expected data types. This can provide insights into what formats are supported and how to configure them correctly.
  
  
  
  Testing:
  
  After making changes, perform a test extraction to ensure that the error is resolved and that data is being loaded correctly.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance on handling data type issues.
  DataSource Documentation: Review the documentation for the specific DataSource you are working with to understand its requirements and limitations.
  Community Forums: Consider searching or posting in SAP community forums for additional insights from other users who may have encountered similar issues.
  
  By following these steps, you should be able to identify the root cause of the RSDS_ACCESS038 error and implement a solution to resolve it.