Do you have any question about this error?
Message type: E = Error
Message class: PSJ_CORE - PSJ Messages
Message number: 012
Message text: Category &1 entries are inconsistent
There is an inconsistency in the attributes for the aggregated process
activity log. The number of entries for the <DS:DE.PSJ_STEP_TYPE>
activity category</> &V1& with which the corresponding
<DS:DE.PSJ_ACTION>activity </> <LS>began </>does not match the number of
entries in for this activity category with which the activity <LS>ended.
</>You are only permitted to have a maximum of one more started entries
than completed entries.
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.
PSJ_CORE012
- Category &1 entries are inconsistent ?The SAP error message PSJ_CORE012 with the description "Category &1 entries are inconsistent" typically occurs in the context of Project System (PS) or related modules when there are inconsistencies in the data related to a specific category in the system. This can happen due to various reasons, such as data corruption, incorrect configuration, or issues during data entry.
Causes:
- Data Inconsistency: The entries for the specified category may not match the expected format or values in the database.
- Configuration Issues: Incorrect settings in the project structure or category configuration can lead to inconsistencies.
- Missing or Incorrect Master Data: Related master data (like cost elements, activity types, etc.) may be missing or incorrectly defined.
- Transport Issues: If changes were transported from one system to another, inconsistencies may arise if the transport was not executed correctly.
- User Input Errors: Manual data entry errors can lead to inconsistencies in the project data.
Solutions:
- Check Configuration: Review the configuration settings for the project categories in the Project System. Ensure that all necessary settings are correctly defined.
- Data Validation: Use transaction codes like SE16 or SE11 to check the relevant database tables for inconsistencies. Look for entries that do not conform to expected values.
- Master Data Review: Ensure that all related master data is correctly defined and available. This includes checking cost elements, activity types, and other relevant data.
- Recreate Entries: If specific entries are found to be corrupt or inconsistent, consider deleting and recreating them if feasible.
- Transport Check: If the issue arose after a transport, verify that all necessary objects were included in the transport request and that they were imported correctly.
- SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide patches or updates.
- Consult Documentation: Review SAP documentation or help resources for additional insights into the error and potential fixes.
Related Information:
By following these steps, you should be able to identify the root cause of the PSJ_CORE012 error and implement a suitable solution.
Get instant SAP help. Start your 7-day free trial now.
PSJ_CORE011
More than one category &1 entry is not permitted on sender/receiver side
What causes this issue? The plausibilty check performed during evaluation showed that the same service call was entered twice in the process activity...
PSJ_CORE010
Unable to find log entries for business process ID &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
PSJ_CORE013
Your entry contains invalid values
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
PSJ_CORE014
Transferred business process ID is not unique (not a UUID)
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.