Do you have any question about this error?
Message type: E = Error
Message class: FKKINV - Invoicing in Contract Accounts Receivable and Payable
Message number: 118
Message text: Source document category &1 is uknown
Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.
To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.
Unfortunately, there isn't any extra information in this error notice.
First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).
Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.
You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.
FKKINV118
- Source document category &1 is uknown ?The SAP error message FKKINV118, which states "Source document category &1 is unknown," typically occurs in the context of the SAP Contract Accounts Receivable and Payable (FI-CA) module. This error indicates that the system is unable to recognize the source document category specified in the transaction or process you are attempting to execute.
Cause:
- Incorrect Document Category: The source document category specified in the transaction does not exist in the system. This could be due to a typo or an incorrect configuration.
- Missing Configuration: The document category may not have been defined in the system configuration, leading to the error when the system tries to process it.
- Data Migration Issues: If data has been migrated from another system, there may be inconsistencies or missing entries in the document category definitions.
- Custom Development: If there are custom developments or enhancements in the system, they may not be correctly handling the document categories.
Solution:
- Check Document Category: Verify the document category being used in the transaction. Ensure that it is correctly spelled and corresponds to a valid entry in the system.
- Configuration Check: Go to the configuration settings in SAP (Transaction SPRO) and navigate to the relevant section for defining document categories. Ensure that the document category in question is defined and configured correctly.
- Transaction Code: Use transaction code OBA7 to check the document categories and ensure that the one you are trying to use is listed.
- Data Consistency: If the error occurred after a data migration, check for data consistency and ensure that all necessary document categories have been migrated correctly.
- Consult Documentation: Review SAP documentation or notes related to the specific version of SAP you are using for any known issues or additional configuration steps.
- Contact Support: If the issue persists after checking the above points, consider reaching out to SAP support for further assistance.
Related Information:
By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.
Get instant SAP help. Start your 7-day free trial now.
FKKINV117
Source document no. &1 for source document type &2 cannot be interpreted
trados = fiWhat causes this issue? The <DS:DE.SRCDOCNO_KK>source document number</> contains a link to the source document of source doc...
FKKINV116
Tax on sales and purchases code could not be determined from table &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FKKINV119
Contract account &1 is blocked for invoicing from &2 to &3
trdos = fiWhat causes this issue? You cannot currently issue an invoice for the contract account since it is excluded from processing due to an invo...
FKKINV120
Billing document &1 (source document category &2) already invoiced
trados = fiWhat causes this issue? The source document specified is to be invoiced. According to the invoicing history, this document has already be...
Click on this link to search all SAP messages.