Do you have any question about this error?
Message type: E = Error
Message class: RSDD - Message class for data manager
Message number: 028
Message text: Editing of aggregate &1; background job &2; start time &3
The aggregate &V1& is being process in background job &V2&. You can find
details about this job in the job overview (transaction SM37). Note that
the start time specified here may deviate from the time displayed in the
job log by a few seconds.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
RSDD028
- Editing of aggregate &1; background job &2; start time &3 ?The SAP error message RSDD028 typically relates to issues with the editing of aggregates in the context of SAP BW (Business Warehouse). This error can occur when there is a problem with a background job that is trying to process or edit an aggregate.
Cause:
- Background Job Conflict: The error often arises when there is an active background job that is currently processing the aggregate. If you attempt to edit the aggregate while it is being processed, you will encounter this error.
- Locking Issues: SAP uses locks to prevent simultaneous changes to the same object. If a lock is held by another process, you will not be able to edit the aggregate.
- Job Scheduling: The job might be scheduled to run at a specific time, and if you try to edit the aggregate during that time, it will lead to this error.
Solution:
- Check Background Jobs: Use transaction code
SM37
to check the status of background jobs. Look for any jobs that are currently running and related to the aggregate you are trying to edit.- Wait for Completion: If you find that a job is running, you may need to wait for it to complete before attempting to edit the aggregate again.
- Cancel the Job: If the job is stuck or taking too long, you may consider canceling it (if appropriate) and then try editing the aggregate again.
- Check Locks: Use transaction code
SM12
to check for any locks on the aggregate. If you find any locks that are preventing you from editing, you may need to release them (ensure you understand the implications of doing so).- Review Job Scheduling: If the job is scheduled to run at a specific time, consider rescheduling it to avoid conflicts with aggregate editing.
Related Information:
SM37
: Monitor background jobs.SM12
: Display and manage locks.RSA1
: Access the Data Warehousing Workbench, where you can manage aggregates.If the problem persists after trying the above solutions, it may be beneficial to consult with your SAP Basis team or SAP support for further assistance.
Get instant SAP help. Start your 7-day free trial now.
RSDD027
Roll-up not necessary. InfoCube data is already rolled up completely
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
RSDD026
Characteristic & is inconsistent
What causes this issue? The realignment run had to be terminated since characteristic &V1& is not consistent. The description of the active v...
RSDD029
Error when structuring the index of aggregate & for InfoCube &
What causes this issue? For performance reasons the database indices were deleted before new data was written in the aggregate &V1&. An error...
RSDD030
Error when saving aggregate &1 (&2) in table RSDDAGGRDIR
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.