Message type: E = Error
Message class: /ACCGO/CAS_MSG -
Message number: 228
Message text: Use of condition type &1 in pricing procedure &2 must be statistical
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.
The SAP error message
/ACCGO/CAS_MSG228
indicates that there is an issue with the configuration of a condition type in a pricing procedure. Specifically, it states that the condition type specified (denoted as&1
) in the pricing procedure (denoted as&2
) must be set as statistical.Cause:
This error typically arises when:
- A condition type that is intended to be used for statistical purposes (e.g., to track costs or for reporting) is not configured as a statistical condition type in the pricing procedure.
- The pricing procedure is expecting a condition type to be statistical, but it has been defined as a regular condition type.
Solution:
To resolve this error, you need to ensure that the condition type in question is correctly configured as a statistical condition type. Here are the steps to do this:
Access the Pricing Procedure Configuration:
- Go to the SAP Easy Access screen.
- Navigate to
SPRO
(Customizing) >Sales and Distribution
>Basic Functions
>Pricing
>Pricing Control
>Define Pricing Procedures
.Locate the Pricing Procedure:
- Find the pricing procedure that is causing the error (identified as
&2
in the error message).- Select the pricing procedure and click on "Details" to view its configuration.
Check the Condition Type:
- In the pricing procedure, locate the condition type that is causing the issue (identified as
&1
).- Check the settings for this condition type.
Set as Statistical:
- Ensure that the condition type is marked as statistical. This is usually done by checking the "Statistical" checkbox in the condition type settings.
- If it is not marked as statistical, change the setting accordingly.
Save Changes:
- After making the necessary changes, save the configuration.
Test the Changes:
- Perform a test transaction to ensure that the error no longer occurs and that the pricing procedure works as expected.
Related Information:
By following these steps, you should be able to resolve the error message and ensure that the pricing procedure is configured correctly.
/ACCGO/CAS_MSG227 Sales order &1 is tracked using event registry; see long text
What causes this issue? Sales order &v1& is tracked in event registry.S...
/ACCGO/CAS_MSG226 Data saved
Self-Explanatory Message Since SAP believes that this specific error message is ...
/ACCGO/CAS_MSG229 Cannot process sales order &1 using /ACCGO/APPLICATION
Self-Explanatory Message Since SAP believes that this specific error message is ...
/ACCGO/CAS_MSG230 Expenses consumed by settlement unit &1 are reset
Self-Explanatory Message Since SAP believes that this specific error message is ...
SAP messages fall into 3 different categories: Error messages
(message type = E), Warnings (W) or Informational (I) messages.
An error message will prevent you from continuing your work - it is a hard stop and you need to fix the error before you can proceed. A warning message will stop your work, however, you can then bypass the warning by pressing the Enter key on your keyboard. That said, it is still good practice to investigate the cause of the warning message and address it. An information message will not stop your work and is truly just for informational purposes.
Click on this link to search all SAP messages.