Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: SPROJECT - General Project Management Messages
Message number: 358
Message text: Planned end & is before the higher-level planned start &
You have specified a plan end before the higher-level plan start &V2&,
but it must be after &V2&. This plan start is specified by higher-level
activites in the hierarchy.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Specify a plan end after &V2&.
Error message extract from SAP system. Copyright SAP SE.
SPROJECT358
- Planned end & is before the higher-level planned start & ?The SAP error message SPROJECT358 indicates that there is a conflict in the scheduling of a project or a work breakdown structure (WBS) element. Specifically, it means that the planned end date of a lower-level project or task is set before the planned start date of its higher-level project or task. This creates a logical inconsistency in the project scheduling.
Cause:
- Incorrect Date Entries: The planned end date for a lower-level task or project has been entered incorrectly, making it earlier than the planned start date of its parent project or task.
- Changes in Project Schedule: If the higher-level project’s start date has been changed after the lower-level task was created, it may lead to this error.
- Data Migration Issues: If data has been migrated from another system, there may be inconsistencies in the date fields.
Solution:
- Review Dates: Check the planned start and end dates of both the higher-level and lower-level projects or tasks. Ensure that the planned end date of the lower-level task is after the planned start date of the higher-level task.
- Adjust Dates: If the planned end date of the lower-level task is incorrect, update it to a date that is after the planned start date of the higher-level task.
- Check Dependencies: Ensure that any dependencies or relationships between tasks are correctly defined and that they reflect the intended project timeline.
- Re-evaluate Project Structure: If necessary, re-evaluate the project structure to ensure that the hierarchy and scheduling make sense.
- Consult Documentation: If you are unsure about the correct dates or project structure, consult project documentation or speak with project stakeholders.
Related Information:
CJ20N
(Project Builder) or CJ02
(Change Project) to view and edit project details.By addressing the date discrepancies and ensuring that the project hierarchy is logically consistent, you should be able to resolve the SPROJECT358 error.
Get instant SAP help. Sign up for our Free Essentials Plan.
SPROJECT357
Planned end & is after the higher-level planned end &
What causes this issue? You have specified a plan end after the higher-level plan end date &V2& , but it must be on or before &V2&. T...
SPROJECT356
Planned start & is after the higher-level planned end &
What causes this issue? You have specified a plan start which is after the higher-level plan end date &V2&, but it must be earlier. This plan...
SPROJECT359
You are not authorized to assign team members to nodes
What causes this issue? You are not authorized for the action. You need the value <ZH>78</> for the field <ZH>ACTVT</> in the...
SM808
No data was selected
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.