Do you have any question about this error?
Message type: E = Error
Message class: /PM0/ABJ_MSG -
Message number: 035
Message text: Persist access and IF_ONLY_BO_DATA = ABAP_TRUE are 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.
/PM0/ABJ_MSG035
- Persist access and IF_ONLY_BO_DATA = ABAP_TRUE are not allowed ?The SAP error message
/PM0/ABJ_MSG035 Persist access and IF_ONLY_BO_DATA = ABAP_TRUE are not allowed
typically occurs in the context of using the Business Object (BO) framework in SAP, particularly when dealing with persistence access in a scenario where theIF_ONLY_BO_DATA
flag is set toABAP_TRUE
.Cause:
This error arises when there is an attempt to perform a persistent access operation (like reading or writing data) while the system is configured to only allow access to Business Object data. The
IF_ONLY_BO_DATA
flag indicates that the operation should only deal with Business Object data, and not with persistent data. When both conditions are set, the system raises this error to prevent conflicting operations.Solution:
To resolve this error, you can consider the following approaches:
Check Configuration: Review the configuration settings for the Business Object and ensure that the
IF_ONLY_BO_DATA
flag is set appropriately based on your requirements. If you need to perform persistent access, you may need to setIF_ONLY_BO_DATA
toABAP_FALSE
.Modify Code Logic: If you are developing or maintaining custom code, ensure that the logic does not attempt to mix persistent access with Business Object data access. You may need to refactor the code to separate these operations.
Consult Documentation: Refer to the SAP documentation for the specific Business Object framework you are using. There may be guidelines or best practices regarding the use of persistent access and Business Object data.
Debugging: If you have access to the development environment, you can debug the code to identify where the conflicting access is being attempted. This can help you pinpoint the exact location in the code that needs to be modified.
SAP Notes: Check the SAP Support Portal for any relevant SAP Notes or updates that might address this specific error. There may be patches or updates that resolve known issues related to this error message.
Related Information:
If the problem persists after trying the above solutions, consider reaching out to SAP support for further assistance.
Get instant SAP help. Start your 7-day free trial now.
/PM0/ABJ_MSG034
IR_BOEC is not a top object
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
/PM0/ABJ_MSG033
An unsaved business object or journal object exists
What causes this issue? A <DS:GLOS.5F721CD0CA16AD458F254922CAB762E3>change option</> cannot be created if business objects exist. This me...
/PM0/ABJ_MSG036
Entities: &1 was changed since last 'Finish'
What causes this issue? The BO has been amended since the last <ZK>Finish</>. The process dispatcher, however, does not expect this.Syste...
/PM0/ABJ_MSG037
Current journal object is an application journal
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.