Do you have any question about this error?
Message type: E = Error
Message class: FIPT_SAFT - Messages for SAFT - Specfic for Portugal
Message number: 002
Message text: No Taxonomy Code defined for G/L Account &1
There is no Taxonomy code defined for G/L Account &V1&
No values are found for G/L Account &V1&
You must make settings<LS> </>in <LS>Assign Taxonomy Codes to G/L
Accounts </>(table FIPTC_TAXOACC) for G/L Account &V1&, from date &V2&
to &V3&, for company code &V4&.
Error message extract from SAP system. Copyright SAP SE.
FIPT_SAFT002
- No Taxonomy Code defined for G/L Account &1 ?The SAP error message FIPT_SAFT002 indicates that there is no taxonomy code defined for a specific General Ledger (G/L) account in the context of the Standard Audit File for Tax (SAFT) reporting. This error typically arises when you are trying to generate a SAFT file, which is required for tax reporting in certain jurisdictions, and the system cannot find the necessary taxonomy code associated with the G/L account.
Cause:
- Missing Taxonomy Code: The G/L account referenced in the error does not have a corresponding taxonomy code defined in the system.
- Configuration Issues: The configuration for the SAFT reporting may not be complete or correctly set up.
- Incorrect G/L Account: The G/L account being used may not be intended for the type of transaction being reported.
Solution:
To resolve this error, you can follow these steps:
Define Taxonomy Code:
- Go to the SAP transaction code OBD2 (or the relevant configuration transaction for your version).
- Navigate to the section where you can define taxonomy codes for G/L accounts.
- Assign the appropriate taxonomy code to the G/L account that is causing the error.
Check Configuration:
- Ensure that the SAFT configuration is correctly set up in your system.
- Verify that all necessary mappings between G/L accounts and taxonomy codes are in place.
Review G/L Account:
- Check if the G/L account is correctly set up and is intended for the type of transactions you are processing.
- If the G/L account is not meant for tax reporting, consider using a different account that has the appropriate taxonomy code.
Consult Documentation:
- Refer to SAP documentation or your local tax authority's guidelines to ensure that you are using the correct taxonomy codes for your jurisdiction.
Testing:
- After making the necessary changes, test the SAFT file generation again to ensure that the error has been resolved.
Related Information:
If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or a consultant who specializes in SAP financial reporting.
Get instant SAP help. Start your 7-day free trial now.
FIPT_SAFT001
No data on FIPTC_TAXOACC for Company &1 between dates &2 and &3
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FIPR511
IVA and RBD field cannot be active at the same time
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FIPT_SAFT003
More than one Taxonomy Code defined for G/L Account &1
What causes this issue? There is more than one Taxonomy Code defined for G/L Account &V1&System Response More than one value found for G/L A...
FIPT_SAFT004
Partner function is not of type Customer (KU)
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.