Do you have any question about this error?
Message type: E = Error
Message class: 64 - Treasury Management: Securities
Message number: 073
Message text: Price type not permitted
Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.
To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.
Unfortunately, there isn't any extra information in this error notice.
First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).
Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.
You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.
64073
- Price type not permitted ?The SAP error message 64073, "Price type not permitted," typically occurs in the context of pricing in sales documents, such as sales orders or quotations. This error indicates that the price type being used is not allowed for the specific transaction or configuration in the system.
Causes:
- Configuration Issues: The price type may not be configured correctly in the pricing procedure. This can happen if the price type is not assigned to the relevant condition types in the pricing procedure.
- Condition Records: There may be no valid condition records for the specified price type in the system.
- Document Type Restrictions: Certain document types may have restrictions on which price types can be used.
- User Authorizations: The user may not have the necessary authorizations to access or use the specified price type.
Solutions:
Check Pricing Procedure:
- Go to the configuration settings for the pricing procedure (Transaction code: SPRO).
- Navigate to Sales and Distribution > Basic Functions > Pricing > Pricing Control.
- Ensure that the price type is correctly assigned to the relevant condition types in the pricing procedure.
Review Condition Records:
- Use transaction code VK11 to check if there are valid condition records for the price type in question.
- If no records exist, create the necessary condition records.
Verify Document Type Settings:
- Check the settings for the document type being used (e.g., sales order, quotation) to ensure that it allows the specified price type.
- This can be done in the configuration settings under Sales and Distribution > Sales > Sales Document > Define Sales Document Types.
User Authorizations:
- Ensure that the user has the necessary authorizations to access the price type. This can be checked with the help of your SAP security team.
Consult SAP Notes:
- Check for any relevant SAP Notes that may address this specific error message or provide additional guidance.
Related Information:
If the issue persists after following these steps, it may be beneficial to consult with an SAP functional consultant or support team for further assistance.
Get instant SAP help. Start your 7-day free trial now.
64072
Final mat.date cannot be before oblig.to offer for sale/right to offer
What causes this issue? The final maturity date (condition header): &V1& cannot be before the obligation to offer for sale- or right to offer...
64071
Issue start date cannot be after oblig.to offer for sale/right to offer
What causes this issue? The issue start date (condition header): &V1& cannot be after the obligation to offer for sale- or right to offer dat...
64074
Final maturity date cannot be earlier than conversion period from/to
What causes this issue? The final maturity date (condition header): &V1& cannot be before the conversion period from / to date (basic data): ...
64075
Final maturity date cannot be before date of notice
What causes this issue? The final maturity date (condition header): &V1& cannot be before the bond holder/issuer notice date (basic data): &a...
Click on this link to search all SAP messages.