How To Fix 6A562 - Condition type & for target object not permitted

SAP Error Message - Details

• Message type: E = Error

• Message class: 6A - Real estate messages rent adjustment

• Message number: 562

• Message text: Condition type & for target object not permitted

What causes this issue?

You wish to copy condition type &V1& from a source object to a target
object (rental agreement to rental unit) during an amount transfer.
This condition type does not exist for the target object, but you have
indicated in the initial screen that new condition types should be
generated if necessary.
In this particular case, however, the system cannot generate new
condition types.

System Response

The condition type has not been generated for the target object.

How to fix this error?

Verify your entry and correct it if necessary.
However, if you still want to transfer condition type &V1&, contact
your system administrator.
Procedure for the system administrator
Change the Customizing settings to allow condition type &V1& also for
target object.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message 6A562 - Condition type & for target object not permitted ?

  The SAP error message 6A562 indicates that there is an issue with a condition type in the pricing procedure. Specifically, the message states that the condition type is not permitted for the target object in the context of the transaction you are trying to execute. This typically occurs in the Sales and Distribution (SD) module when dealing with pricing conditions.
  Causes:
  
  Incorrect Configuration: The condition type may not be configured correctly in the pricing procedure for the specific target object (e.g., sales order, quotation, etc.).
  Missing Condition Records: There may be no condition records maintained for the condition type in the relevant master data (e.g., customer master, material master).
  Incompatible Condition Type: The condition type may not be applicable for the specific transaction or document type you are working with.
  Pricing Procedure Assignment: The pricing procedure assigned to the sales document may not include the condition type in question.
  Access Sequence Issues: The access sequence for the condition type may not be set up correctly, leading to it being unavailable for the target object.
  
  Solutions:
  
  
  Check Pricing Procedure:
  
  Go to the transaction code V/08 to review the pricing procedure assigned to the sales document type.
  Ensure that the condition type in question is included in the pricing procedure.
  
  
  
  Review Condition Records:
  
  Use transaction code VK11 to check if condition records exist for the condition type and the relevant key (e.g., customer/material).
  If records are missing, create them using VK11.
  
  
  
  Verify Condition Type Configuration:
  
  Check the configuration of the condition type in transaction code V/06. Ensure that it is set up correctly for the intended use.
  
  
  
  Check Access Sequence:
  
  Review the access sequence assigned to the condition type in transaction code V/07. Ensure that it is correctly defined to allow access to the necessary data.
  
  
  
  Document Type Compatibility:
  
  Ensure that the condition type is compatible with the document type you are using. Some condition types may only be valid for specific document types.
  
  
  
  Consult SAP Notes:
  
  Check for any relevant SAP Notes that may address this specific error message or provide additional guidance.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  V/08: Pricing Procedure Configuration
  VK11: Create Condition Records
  VK12: Change Condition Records
  VK13: Display Condition Records
  V/06: Condition Type Configuration
  V/07: Access Sequence Configuration
  
  
  
  Documentation: Refer to SAP Help documentation for detailed information on pricing procedures and condition types.
  
  
  Testing: After making changes, test the pricing in a development or quality environment before moving to production to ensure that the issue is resolved.
  
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.