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: PT_REQ -
Message number: 004
Message text: Archiving run was interrupted
The <DS:GLOS.3526B453AFAB52B9E10000009B38F974>archiving session</> was
interrupted. This was caused either manually by the user or by the
parameter specified for the interruption (for example, the maximum
runtime or the maximum volume of data to be written was exceeded).
This enables you to react to runtime restrictions or limited available
memory during archiving. You can continue and complete interrupted
archiving sessions at a later point when the restrictions have been
removed.
The system interrupted the archiving session before the next
<DS:GLOS.F2484B01DD71D411A4950060B03C3B0E>data object</> was processed.
In <LS>Archive Management</> this archiving session is indicated as <LS>
Interrupted</>.
After the archiving session has been interrupted, the system stops
further archiving.
It is possible that the system has not completely deleted the data that
was archived before the archiving session was interrupted.
You can continue an interrupted archiving session. The data objects that
need to be archived according to the selection criteria are then written
to archive files.
The following prerequisites must be met:
The archiving session was interrupted according to the set parameter or
manually. You cannot continue archiving sessions that were interrupted
for other reasons or by <LS>Archive Management</>.
The deletion phase needs to have been completed for the data that was
archived up until the point of interruption, meaning that the archiving
session needs to have the status <LS>Complete</>.
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.
PT_REQ004
- Archiving run was interrupted ?The SAP error message PT_REQ004, which states "Archiving run was interrupted," typically occurs during the archiving process in the SAP system, particularly in the context of personnel time management or payroll data. This error indicates that the archiving process could not be completed successfully due to some issues.
Causes:
- Database Locking Issues: The archiving process may be interrupted due to database locks on the tables being archived.
- Insufficient Authorizations: The user executing the archiving process may not have the necessary authorizations to perform the operation.
- Configuration Issues: Incorrect configuration settings in the archiving object or related settings can lead to interruptions.
- System Errors: There may be underlying system errors, such as memory issues or other resource constraints.
- Data Consistency Issues: Inconsistent or corrupt data in the tables being archived can cause the process to fail.
- Job Scheduling Conflicts: Conflicts with other scheduled jobs that access the same data can lead to interruptions.
Solutions:
- Check Logs: Review the application logs (transaction SLG1) and the job logs (transaction SM37) for detailed error messages that can provide insights into why the archiving run was interrupted.
- Database Locks: Use transaction SM12 to check for any locks on the relevant database tables. If locks are found, they may need to be released.
- Authorization Check: Ensure that the user executing the archiving process has the necessary authorizations. You can check this using transaction SU53 or by reviewing the user's roles and authorizations.
- Configuration Review: Verify the configuration settings for the archiving object in transaction SARA. Ensure that all settings are correct and that the archiving object is properly defined.
- System Resources: Check system resources (memory, CPU, etc.) to ensure that the system is not under heavy load. You can use transaction ST02 to monitor memory usage.
- Data Consistency: Run consistency checks on the data to ensure there are no corrupt records. This may involve using specific SAP reports or tools designed for data consistency checks.
- Retry the Archiving Run: After addressing the issues, you can retry the archiving run. Make sure to monitor it closely to ensure it completes successfully.
Related Information:
By following these steps, you should be able to identify the cause of the PT_REQ004 error and implement a solution to successfully complete the archiving run.
Get instant SAP help. Sign up for our Free Essentials Plan.
PT_REQ003
&1% (&2 of &3) of the requests processed
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
PT_REQ002
Request data archived for data destruction
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
PT_REQ005
Personnel number &1 does not belong to country &2
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
PT_REQ006
Request (ID &1) has the status &2 and cannot be archived
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.