Do you have any question about this error?
Message type: E = Error
Message class: BP - Budgeting and planning
Message number: 787
Message text: Entry is invalid; &1 / &2 must be eligible for cover
You want to stipulate that a combination of budget type and budget
subtype is not eligible for cover. However, this is not possible, as it
is stipulated in the Customizing of <LS>Funds Management Government</>
that the combination is eligible for cover.
For further information about combinations eligible for cover, refer to
step <DS:SIMG._ISPSFM_V_TBP4B>"Enter settings for budget subtypes"</>
in the <LS>Funds Management Government</> Implementation Guide.
You must not make an entry for this combination of budget type and
budget subtype.
If, nevertheless, you still want to make an entry, you must flag this
combination of budget type and budget subtype as eligible for cover in
the payment budget and the commitment budget.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
BP787
- Entry is invalid; &1 / &2 must be eligible for cover ?The SAP error message BP787 ("Entry is invalid; &1 / &2 must be eligible for cover") typically occurs in the context of business partner (BP) management, particularly when dealing with insurance or financial transactions where certain entries must meet specific eligibility criteria for coverage.
Cause:
- Ineligible Business Partner: The business partner (BP) you are trying to process may not meet the criteria for coverage. This could be due to missing or incorrect data in the business partner's master data.
- Invalid Data: The specific fields referenced by &1 and &2 in the error message may contain invalid or incomplete information. This could include fields like insurance type, coverage limits, or other relevant attributes.
- Configuration Issues: There may be configuration settings in the system that define eligibility criteria for coverage that are not being met by the current entry.
Solution:
- Check Business Partner Data: Review the business partner's master data to ensure that all required fields are filled out correctly. Pay special attention to any fields related to eligibility for coverage.
- Verify Eligibility Criteria: Consult the configuration settings related to coverage eligibility. Ensure that the business partner meets all the necessary criteria defined in the system.
- Correct Invalid Entries: If the error message specifies particular fields (e.g., &1 and &2), check those fields for validity and correct any discrepancies.
- Consult Documentation: Refer to SAP documentation or your organization's guidelines for specific eligibility requirements related to the business partner and the type of coverage being processed.
- Contact Support: If the issue persists after checking the above points, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
Related Information:
By following these steps, you should be able to identify the cause of the BP787 error and implement a solution to resolve it.
Get instant SAP help. Start your 7-day free trial now.
BP786
Deleting cover eligibility profile &1 not allowed
What causes this issue? You want to delete cover eligibility profile &V1&. However, this is not possible, as it is still assigned to at least...
BP785
Cover eligibility relationships are being demanded
What causes this issue? When posting cover eligibility relationships are used, that is cross assignments are generated on other elements.Error messag...
BP788
Functional area and cover eligibility can not be used simultaneously
What causes this issue? In FM area &V1&, the functional area and cover eligibility are activated for fiscal year &V2&. The simultaneo...
BP789
Entry is not valid; Cover eligibility must be the same in PB and CB
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.