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: EK - IS-U Accounts Receivable and Payable
Message number: 279
Message text: Entry &1 still used in P/L account determination, deletion not permitted
The selected entry is still being used in the account determination for
for the revenue accounts for at least one account determination ID.
The system cannot continue processing.
If the entries are no longer needed in the account determination, then
delete them. You can subsequently delete the entry in the transaction
table.
Error message extract from SAP system. Copyright SAP SE.
EK279
- Entry &1 still used in P/L account determination, deletion not permitted ?The SAP error message EK279 ("Entry &1 still used in P/L account determination, deletion not permitted") typically occurs when you attempt to delete a record in the system that is still being referenced in the Profit and Loss (P/L) account determination settings. This can happen in various contexts, such as when trying to delete a condition record or a configuration entry that is linked to financial postings.
Cause:
The error is caused by the following reasons:
- Active References: The entry you are trying to delete is still being used in the P/L account determination process. This means that there are existing configurations or transactions that reference this entry.
- Data Integrity: SAP enforces data integrity rules to prevent the deletion of entries that are still in use, which could lead to inconsistencies in financial reporting.
Solution:
To resolve this error, you can follow these steps:
Check References: Identify where the entry is being used. You can do this by:
- Using transaction codes like
OBYC
(for account determination) to check the configuration settings.- Reviewing the relevant configuration tables (e.g., T030, T003) to see if the entry is linked to any active settings.
Remove Dependencies: If you find that the entry is being referenced:
- Modify or delete the dependent entries that are using the P/L account determination.
- Ensure that no transactions or configurations are currently using the entry.
Consult Documentation: Review SAP documentation or help files related to account determination to understand the implications of deleting the entry.
Use Transaction Codes: If applicable, use transaction codes like
OBYC
to navigate to the account determination settings and make necessary adjustments.Seek Help: If you are unsure about the dependencies or the impact of deleting the entry, consult with your SAP functional consultant or a colleague who has experience with financial configurations in SAP.
Related Information:
Transaction Codes: Familiarize yourself with relevant transaction codes such as:
OBYC
: Configuration of automatic postings.SPRO
: Access to the SAP Reference IMG for configuration settings.SAP Notes: Check SAP Notes for any specific guidance or patches related to this error message. You can search for the error message number in the SAP Support Portal.
Testing: After making changes, ensure to test the configuration in a development or quality environment before applying it to production.
By following these steps, you should be able to resolve the EK279 error and successfully manage your P/L account determination settings in SAP.
Get instant SAP help. Sign up for our Free Essentials Plan.
EK278
No entry for key & found in table &
What causes this issue? There is no entry for the displayed key in table T880.System Response The system issues an error message and will not allow ...
EK277
Error reading returns activity table &1 key &2
What causes this issue? The Customizing table for returns activities &V1& could not be read using the specified key &V2& (company cod...
EK280
Entry &1 still used for BB account determination, do not delete
What causes this issue? The selected entry is still being used in the account determination for budget billing postings for at least one account dete...
EK281
No entry found in table TFKHVOT
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.