How To Fix VT636 - Enter calculation type (condition type has calc. type &2, period &3)

VT636 - Overview

• Message type: E = Error

• Message class: VT - Vertriebstabellen

• Message number: 636

• Message text: Enter calculation type (condition type has calc. type &2, period &3)

What causes this issue?

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

System Response

How to fix this error?

Please enter a calculation type.
The following is valid for deferred settlement condition types in
purchasing:
Condition records which are not for periodic agreement or the main
condition records which are for periodic agreement have the calculation
type &V2&. Period-specific conditions and agreements for periodic
settlement can have a different calculation type. The recommended value
for periodic-specific conditions is likewise &V2&. However, you can
also use other calculation types (manual entry).

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message VT636 - Enter calculation type (condition type has calc. type &2, period &3) ?

  The SAP error message VT636 indicates that there is an issue with the calculation type associated with a condition type in the context of pricing or conditions in the SAP system. This error typically arises when the system expects a calculation type to be specified for a particular condition type, but it is either missing or incorrectly configured.
  
  Cause:
  
  Missing Calculation Type: The condition type being used does not have a calculation type assigned to it.
  Incorrect Configuration: The configuration for the condition type may not be set up correctly in the pricing procedure.
  Period Specification: The error message also mentions a period, which could indicate that the calculation type is expected to be defined for a specific period, but it is not.
  Custom Development: If there are custom developments or enhancements in the pricing logic, they might not be handling the calculation types correctly.
  
  
  Solution:
  
  
  Check Condition Type Configuration:
  
  Go to the transaction code V/06 (for condition