Do you have any question about this error?
Message type: E = Error
Message class: PSB_API_MSGCL -
Message number: 136
Message text: Collective PR maintenance for multiple project is not allowed
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.
PSB_API_MSGCL136
- Collective PR maintenance for multiple project is not allowed ?The SAP error message PSB_API_MSGCL136 indicates that collective purchase requisition (PR) maintenance for multiple projects is not allowed. This typically occurs when you are trying to create or modify purchase requisitions that are associated with different projects in a single transaction, which is not permitted in the SAP system.
Cause:
- Multiple Projects: The primary cause of this error is that the purchase requisitions you are trying to maintain are linked to different projects. SAP does not allow collective processing of requisitions that belong to different project structures.
- Configuration Settings: There may be specific configuration settings in your SAP system that restrict collective maintenance for requisitions across multiple projects.
Solution:
- Single Project Maintenance: Ensure that you are only working with purchase requisitions that are associated with a single project. If you need to maintain requisitions for multiple projects, you will have to do this in separate transactions for each project.
- Check Project Assignment: Review the project assignments of the purchase requisitions you are trying to maintain. Make sure they all belong to the same project.
- Use Transaction Codes: If you are using a transaction code that allows collective processing (like ME5A for PRs), ensure that you filter the requisitions by project to avoid mixing them.
- Consult Documentation: Refer to SAP documentation or your organization's SAP support team for any specific configurations or restrictions that may apply to your system.
Related Information:
If the problem persists after following these steps, it may be beneficial to consult with your SAP support team or a functional consultant who specializes in procurement processes within SAP.
Get instant SAP help. Start your 7-day free trial now.
PSB_API_MSGCL135
Authorization cannot be inherited by at least one subobject
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
PSB_API_MSGCL134
Duration cannot be changed if the calculation key is "Calculate Duration"
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
PSB_API_MSGCL999
Operation not supported for locked objects
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
PSB_CONFIG_MSGCL001
Configuration with &1 &2 exists
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.