When performing division with BigDecimal, the operation requires explicit instructions for handling non-terminating decimal expansions. To extract only the integer portion of a quotient, you must specify a scale of 0 alongside an appropriate RoundingMode.

The most direct approach involves passing the scale and rounding strategy directly to the divide method. This eliminates the need for a secondary setScale call and prevents ArithmeticException errors that occur when exact division is impossible.

import java.math.BigDecimal;
import java.math.RoundingMode;

public class DecimalTruncation {
    public static void main(String[] args) {
        BigDecimal numerator = new BigDecimal("17.85");
        BigDecimal denominator = new BigDecimal("3.2");

        // Calculate quotient, forcing scale to 0 for integer output
        BigDecimal quotient = numerator.divide(denominator, 0, RoundingMode.DOWN);

        System.out.println("Integer portion: " + quotient);
    }
}

The second parameter in the divide method defines the number of decimal places. Setting it to 0 instructs the JVM to discard fractional digits. The third parameter dictates how the discarded fraction affects the final value:

• RoundingMode.DOWN: Truncates toward zero. Both 5.9 and -5.9 become 5 and -5 respectively.
• RoundingMode.FLOOR: Rounds toward negative infinity. 5.9 becomes 5, but -5.9 becomes -6.
• RoundingMode.HALF_UP: Standard mathematical rounding. Values of .5 or higher round away from zero.

If the divisor might be zero, wrap the operation in a conditional check or a try-catch block to handle ArithmeticException. For financial calculations where precisionn rules are strict, HALF_UP is typically preferred, while DOWN or FLOOR suits scenarios requiring strict truncation of the fractional component.