Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: GP - FI-SL and CO planning
Message number: 711
Message text: Price unit & is not supported
You entered the invalid price unit &V1& in period &V2& for cost center/
activity type &V3&/&V4&. Only the values 1, 10, 100, 1000 or 10000 are
valid for price units.
The value for the price unit was not accepted.
Enter only the above specified values for the price unit.
Error message extract from SAP system. Copyright SAP SE.
GP711
- Price unit & is not supported ?The SAP error message GP711 "Price unit & is not supported" typically occurs in the context of pricing and conditions in SAP, particularly when dealing with pricing procedures in the Sales and Distribution (SD) module or similar areas. This error indicates that the price unit specified in the transaction is not valid or not supported by the system configuration.
Causes:
- Invalid Price Unit: The price unit specified in the transaction does not exist in the system or is not defined for the material or service being processed.
- Configuration Issues: The pricing procedure may not be configured to handle the specified price unit.
- Master Data Issues: The material master or condition records may not have the necessary settings for the specified price unit.
- Unit of Measure (UoM) Issues: There may be a mismatch between the unit of measure used in the transaction and the units defined in the material master or pricing conditions.
Solutions:
- Check Price Unit: Verify the price unit being used in the transaction. Ensure that it is a valid unit of measure that is defined in the system.
- Review Configuration: Check the pricing procedure configuration in the SAP system. Ensure that the pricing procedure supports the specified price unit.
- Navigate to the configuration settings for pricing procedures in SPRO (Transaction Code).
- Update Master Data: Ensure that the material master and condition records are correctly set up to include the necessary price units.
- Check the material master data (Transaction Code MM03) for the relevant material.
- Check condition records (Transaction Code VK11) for the pricing conditions.
- Unit of Measure Settings: Ensure that the unit of measure settings are consistent across the relevant master data and transaction data.
- Consult Documentation: Refer to SAP documentation or help resources for specific details on pricing procedures and supported price units.
Related Information:
If the problem persists after checking these areas, it may be beneficial to consult with your SAP support team or a functional consultant who specializes in the SD module for further assistance.
Get instant SAP help. Sign up for our Free Essentials Plan.
GP710
Activity price indicator & is not supported
What causes this issue? You entered an invalid value in the field 'Planned activity price indicator'. Only the following values are valid f...
GP709
Activity input &/& cannot be planned manually for cost ctr/act.type &/&
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
GP712
Plan the fixed and variable costs with the same sign
What causes this issue? You have transferred total costs to object &V1& and cost element &V2& the amounts of which are smaller than t...
GP713
The planning record already exists
What causes this issue? The CO interface has been preconfigured so that existing plan records are not overwritten. &v1& with the key &v2&...
Click on this link to search all SAP messages.