Do you have any question about this error?
Message type: E = Error
Message class: /ISDFPS/OM_PROXY -
Message number: 058
Message text: Interval '&1'-'&2' for interval boundary typecode '&3' 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.
/ISDFPS/OM_PROXY058
- Interval '&1'-'&2' for interval boundary typecode '&3' not allowed ?The SAP error message
/ISDFPS/OM_PROXY058
indicates that there is an issue with the interval boundaries defined for a specific interval boundary type code in the context of SAP's Integrated Business Planning (IBP) or similar applications. This error typically arises when the defined intervals do not conform to the expected rules or constraints set by the system.Cause:
- Invalid Interval Definition: The intervals defined for a specific boundary type code are not valid. This could be due to overlapping intervals, gaps, or intervals that do not meet the required criteria.
- Configuration Issues: There may be a misconfiguration in the settings related to the interval boundaries in the system.
- Data Entry Errors: Incorrect data entry when defining the intervals can lead to this error. For example, the start date of an interval may be after the end date.
- Business Rules Violation: The defined intervals may violate specific business rules or constraints that are enforced by the system.
Solution:
- Review Interval Definitions: Check the intervals defined for the boundary type code specified in the error message. Ensure that they are correctly defined without overlaps or gaps.
- Correct Data Entry: Verify that the start and end dates of the intervals are correctly entered and that the start date is always before the end date.
- Check Configuration Settings: Review the configuration settings related to interval boundaries in the system. Ensure that they align with the business requirements and rules.
- Consult Documentation: Refer to SAP documentation or help resources for guidance on the specific boundary type code and its requirements.
- Test Changes: After making corrections, test the changes in a development or test environment before applying them to production to ensure that the error is resolved.
Related Information:
/ISDFPS/OM
for operational management.If the problem persists after following these steps, it may be beneficial to reach out to SAP support for further assistance.
Get instant SAP help. Start your 7-day free trial now.
/ISDFPS/OM_PROXY057
For interval boundary typecode '&1' an end date is not allowed
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
/ISDFPS/OM_PROXY056
Relationship '&1' cannot be converted
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
/ISDFPS/OM_PROXY059
Interval boundary typecode '&1' not allowed
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
/ISDFPS/OM_PROXY060
Error during call of internal BAdI for retrieval of node "&1"
What causes this issue? Internal BAdI for the named node has no or multiple active implementations.System Response The system issues an error messag...
Click on this link to search all SAP messages.