Do you have any question about this error?
Message type: E = Error
Message class: FQ - Payment Requests and Payment Program
Message number: 808
Message text: No control entry found for doc.: Request : & CCode: & Fisc.Year: &
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.
FQ808
- No control entry found for doc.: Request : & CCode: & Fisc.Year: & ?The SAP error message FQ808 indicates that there is no control entry found for a specific document in the context of financial accounting. This error typically arises in the context of document processing in SAP, particularly when dealing with financial transactions that require specific control settings.
Cause:
The error message FQ808 can occur due to several reasons:
Missing Control Data: The control data for the specified document type, company code, and fiscal year is not maintained in the system. This could happen if the configuration for the financial document type is incomplete.
Incorrect Document Type: The document type used in the transaction may not be correctly configured or may not exist in the system.
Fiscal Year Settings: The fiscal year settings may not be properly defined for the company code or the document type being used.
Data Inconsistency: There may be inconsistencies in the data, such as missing entries in the relevant tables that manage control data.
Solution:
To resolve the FQ808 error, you can take the following steps:
Check Control Data:
- Go to the transaction code OBY6 (or OBY1 depending on your version) to check the control data for the company code and fiscal year.
- Ensure that the necessary entries exist for the document type you are trying to process.
Verify Document Type Configuration:
- Use transaction code OBA7 to check the configuration of the document type.
- Ensure that the document type is correctly defined and linked to the appropriate company code and fiscal year.
Review Fiscal Year Settings:
- Check the fiscal year variant assigned to the company code and ensure that it is correctly set up.
- Use transaction code OB29 to review and adjust fiscal year settings if necessary.
Check for Data Inconsistencies:
- Use transaction codes like SE16 or SE11 to check the relevant tables (e.g., T001, T003) for any missing or inconsistent entries.
- If necessary, consult with your SAP Basis or technical team to perform data consistency checks.
Consult Documentation:
- Review SAP documentation or notes related to the specific error message for any additional guidance or updates.
Contact SAP 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 and resolve the cause of the FQ808 error in your SAP system.
Get instant SAP help. Start your 7-day free trial now.
FQ807
No transaction is assigned to the request category/activity: &/&
What causes this issue? The specified commitment item &V1& is a revenue item. In the current transaction you are processing a payment request...
FQ806
Read error in internal table &1 line &2
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FQ809
Coding block not possible: G/L account not filled
What causes this issue? To be able to display the coding block, you need a G/L account. The corresponding field, however, does not have an entry in ...
FQ810
New item added to request
What causes this issue? You have extended the request by a new item. An additional item was generated. Possible default values are taken into consid...
Click on this link to search all SAP messages.