Do you have any question about this error?
Message type: E = Error
Message class: FKKCOLL - Submission to Ext.Collection Agency/Legal Dunning Procedure
Message number: 116
Message text: No data record found with doc. number &1 in submission table DFKKCOLL
Information has been sent for collection unit &V2&. However, no data
record with document number &V1& could be found in submission table
DFKKCOLL.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Check the payload and check with the collection agency. Determine if the
document may have already been archived.
Error message extract from SAP system. Copyright SAP SE.
FKKCOLL116
- No data record found with doc. number &1 in submission table DFKKCOLL ?The SAP error message FKKCOLL116 indicates that there is no data record found with the specified document number in the submission table DFKKCOLL. This error typically occurs in the context of contract accounts receivable and payable (FI-CA) when trying to process a collection or submission that references a document number that does not exist in the system.
Causes:
- Incorrect Document Number: The document number provided may be incorrect or mistyped.
- Data Deletion: The record may have been deleted or archived, which means it is no longer available in the submission table.
- Incorrect Submission Process: The submission process may not have been executed correctly, leading to missing records.
- Timing Issues: The document may not have been created or posted yet, leading to a temporary absence in the table.
- Authorization Issues: The user may not have the necessary authorizations to view the document.
Solutions:
- Verify Document Number: Double-check the document number for accuracy. Ensure that it is the correct number and format.
- Check Data Availability: Use transaction codes like SARA (Archive Administration) to check if the document has been archived or deleted.
- Review Submission Process: Ensure that the submission process was completed successfully. You may need to re-run the submission or check for any errors in the process.
- Check Timing: If the document was recently created, wait a moment and try again, as there may be a delay in data availability.
- Authorization Check: Ensure that the user has the necessary permissions to access the document. Consult with your SAP security team if needed.
- Consult Logs: Check the application logs (transaction SLG1) for any related error messages that might provide more context on the issue.
Related Information:
If the issue persists after trying the above solutions, it may be necessary to involve your SAP support team or consult with SAP directly for further assistance.
Get instant SAP help. Start your 7-day free trial now.
FKKCOLL115
Grouping level of coll. unit &1 missing for assignment of coll.pmt &2
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FKKCOLL114
ID of collection unit missing for assignment of collection payment &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FKKCOLL117
ID for business object not correct: different business partner number
What causes this issue? The ID for the business object <LS>CommissionedOutstandingCollections</> is composed of the collection agency ID ...
FKKCOLL118
Collection unit ID &1 is already being used for another business partner
What causes this issue? The collection unit ID cannot be used for multiple business partners. The ID &V1& must be used for business partner &...
Click on this link to search all SAP messages.