How To Fix RSDS173 - &1: Packed numbers should have an odd number of digits

SAP Error Message - Details

• Message type: E = Error

• Message class: RSDS - New DataSource

• Message number: 173

• Message text: &1: Packed numbers should have an odd number of digits

What causes this issue?

Field &V1& has &V2& characters. This could cause conversion problems
between ABAP and the database if the data really has more than &V2& cha
racters. This is because in ABAP, an additional byte is available intern
ally for an even number of characters because of the sign.

System Response

The function continues.

How to fix this error?

Ensure that the data really has a maximum of &V2& characters, or increas
e the number of characters by one.

How can this happen?

4 characters were defined, internally in ABAP 5 characters are available
. On the database 4 characters are available. If there is a data record
that uses 5 characters, a short dump occurs upon inserting the data into
the database.
5 characters were defined, in ABAP and in the database 5 characters are
available. If there is a data record that uses 6 characters, the last
character is cut off and inserting into the database does not cause any
problems.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message RSDS173 - &1: Packed numbers should have an odd number of digits ?

  The SAP error message RSDS173 indicates that there is an issue with packed numbers in your data. Specifically, it states that packed numbers should have an odd number of digits. This error typically arises when dealing with data types that are expected to be in a packed decimal format, which is commonly used in ABAP programming and database storage.
  Cause:
  The error occurs when a packed number (which is a binary representation of decimal numbers) is defined or processed with an even number of digits. In SAP, packed numbers are stored in a format where the last digit is a sign digit (positive or negative), and thus the total number of digits must be odd. For example, a packed number with 3 digits (2 for the number and 1 for the sign) is valid, while a packed number with 4 digits is not.
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Data Definition: Review the data structure or field definitions in your ABAP program or database table. Ensure that any packed number fields are defined with an odd number of total digits.
  
  
  Adjust Data Length: If you are defining a packed number, make sure that the total length (including the sign) is odd. For example, if you need to store a number with 2 digits, define it as a packed number with 3 digits.
  
  
  Data Conversion: If you are converting data from one format to another, ensure that the conversion logic maintains the odd digit requirement for packed numbers.
  
  
  Debugging: If the error occurs during runtime, use debugging tools to trace the data flow and identify where the packed number is being incorrectly defined or processed.
  
  
  Consult Documentation: Refer to SAP documentation or help resources for specific guidelines on defining and using packed numbers in your context.
  
  
  Related Information:
  
  Packed Number Format: In SAP, packed numbers are typically defined using the P data type in ABAP. The syntax for defining a packed number is P(length, decimal places), where length should be odd.
  Data Types in ABAP: Familiarize yourself with different data types in ABAP, especially how packed numbers are used in calculations and data storage.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message, as there may be specific fixes or recommendations provided by SAP.
  
  By following these steps, you should be able to identify and correct the cause of the RSDS173 error in your SAP environment.